FAQ system list

FAQ system list

[Alan Watson]

As part of the FAQ list, I would like a table of architectures, OSes,
and compilers with which rc is known to work.  If you've managed to
compile rc on a system which you do not see on this list, please drop
me a line.  

Replies from RS/6000 and HP users would be especially welcome.  Has
anyone managed to get rc to compile on a VAX?  I spent a frustrating
hour battling vcc and pcc with unproto as my excalibur before retiring
from the field, but we don't have gcc on our VAXen.

Thanks to everyone who responded to this first time around.

Alan.

1.4     Can I compile rc on a ... machine with ... operating system and
        ... compiler?

        rc is written in portable ANSI C, but it can be compiled by many
        older C compilers after passing the sources through unproto (get
        /pub/unix/unproto4.shar.Z by anonymous FTP from ftp.win.tue.nl).

        If you use gcc, make sure it is at least as new as v1.39.

        rc has been successfully compiled on systems with the following
        combinations of architectures, operating systems, and compilers:

            DEC MIPS       Ultrix v4.[23]      gcc v2
            DEC MIPS       Ultrix v4.3         cc        [a][b]
            DEC Alpha      OSF/1 v1.2          cc        [a][b][n]
            DEC Alpha      OSF/1 v1.2          cc -std1  [a][n]

            Sun SPARC      Solaris v2          gcc v2    [c][n]
            Sun SPARC                          acc       [c][d][n]
            Sun SPARC      SunOS v4.1.3        cc        [a][b][c][n]
            Sun SPARC      SunOS v4.1.[123]    gcc v2    [c][n]
            Sun SPARC      BSD                           [c][n]
            Sun 68K        SunOS 3.5           gcc v1    [c][n]
            Sun 68K        SunOS v4.0.3        lcc       [c][e][n]

            SGI Iris       Irix v[45].x        gcc v2

            Apollo 68K     DomainOS v10.4      cc        [a][f][m]
            Apollo 10000   DomainOS v10.4      cc        [a][f][m]

            Convex C1      ConvexOS v10.1      cc        [a]

            Pyramid 9810   OSx 5.1a            cc -Xa    [a][f][g]

            IBM RS/6000                        cc

            i386/i486      SCO-ODT SVR3        gcc v2    [h][i]
            i386/i486      SCO-ODT SVR3        cc        [h][i]
            i386           Minix v1.5                    [h]

            Cray Y-MP      Unicos 6.1.7        scc       [j][k]

            NeXT           NeXT OS v2.x        gcc v2    [l]
            NeXT           NeXT OS v3.0        gcc v2    [l]

        Notes:

            [a] The native C compiler.
            [b] Sources pre-processed with unproto.
            [c] Sun's yacc has a memory leak -- use another
                implementation such as GNU bison (see 7.4).
            [d] The unbundled ANSI compiler.
            [e] rc v1.2.
            [f] BSD universe.
            [g] This compiler has no stdarg.h, but vararg.h sufficed.
            [h] Requires intervention by hand to get mksignal to work,
                because of deficient sh, awk, etc.
            [i] See 4.13.
            [j] Minor modifications required to prototypes.
            [k] See 4.13.
            [l] See 5.6.
            [m] See 5.5.
            [n] See 1.5.

FAQ system list

[mycroft]

Here are the environments I'm running it in which you didn't list:

	       Sun 68k	      SunOS v4.1.1_U1     gcc
	       i386/i486      NetBSD		  cc (which is gcc v1.39)
	       i386/i486      NetBSD		  gcc (v2)
	       RS/6000	      AIX 3.2.1		  cc

rc on Linux?

[Dave Mason]

I built it, after hacking some include file stuff for mksignal, but it
consistently exits on an intr signal.

Please!!! I'm desperate!! I can't take much more of this bash stuff...

Thanks	../Dave

Re: FAQ system list

[Tom Culliton x2278]

>          i386/i486      SCO-ODT SVR3        gcc v2    [h][i]
>          i386/i486      SCO-ODT SVR3        cc        [h][i]
>
>          [h] Requires intervention by hand to get mksignal to work,
>              because of deficient sh, awk, etc.
>          [i] See 4.13.

While I'm the first one to throw stones at SCO-ODT this needs to be
clarified.  The problem is not a deficiency in SCO the utilities, but
rather a very complicated /usr/include/sys/signal.h with preprocessor
conditionals that end up defeating the scripts assumptions.  If the
problem was with the utilities using gnu substitutes should fix it and
they don't.

Tom

BTW - attached is the hacked version of SCO's sys/signal.h that I use to
build a good rc.

------------------------------signal.hacked------------------------------
/* This is a hacked down version of /usr/include/sys/signal.h needed
 * because mksignal has problems with preprocessor conditionals.
 */

#define	SIGHUP	1	/* hangup */
#define	SIGINT	2	/* interrupt (rubout) */
#define	SIGQUIT	3	/* quit (ASCII FS) */
#define	SIGILL	4	/* illegal instruction (not reset when caught)*/
#define	SIGTRAP	5	/* trace trap (not reset when caught) */
#define	SIGIOT	6	/* IOT instruction */
#define SIGABRT 6	/* used by abort, replace SIGIOT in the  future */
#define	SIGEMT	7	/* EMT instruction */
#define	SIGFPE	8	/* floating point exception */
#define	SIGKILL	9	/* kill (cannot be caught or ignored) */
#define	SIGBUS	10	/* bus error */
#define	SIGSEGV	11	/* segmentation violation */
#define	SIGSYS	12	/* bad argument to system call */
#define	SIGPIPE	13	/* write on a pipe with no one to read it */
#define	SIGALRM	14	/* alarm clock */
#define	SIGTERM	15	/* software termination signal from kill */
#define	SIGUSR1	16	/* user defined signal 1 */
#define	SIGUSR2	17	/* user defined signal 2 */
#define	SIGCLD	18	/* death of a child */
#define	SIGPWR	19	/* power-fail restart */
#define SIGWINCH 20	/* window change */

			/* SIGPHONE only used in UNIX/PC */
/*#define SIGPHONE 21*/	/* handset, line status change */

#define SIGPOLL 22	/* pollable event occured */
#define SIGCHLD SIGCLD  /* compatibility */

#define SIGSTOP 23      /* sendable stop signal not from tty */
#define SIGTSTP 24      /* stop signal from tty */
#define SIGCONT 25      /* continue a stopped process */
#define SIGTTIN 26      /* to readers pgrp upon background tty read */
#define SIGTTOU 27      /* like TTIN for output if (tp->t_local&TOSTOP) */

#define	SIGALL          (~(sigset_t)0L)		/* new for POSIX */

#define	NSIG	28	/* The valid signal number is from 1 to NSIG-1 */
#define MAXSIG	32	/* size of u_signal[], NSIG-1 <= MAXSIG*/
			/* MAXSIG is larger than we need now. */
			/* In the future, we can add more signal */
			/* number without changing user.h */

FAQ system list

[noel]

I have had rc running in the following environments:

	RS6000	AIX 3.1.5	cc
	RS6000	AIX 3.2		cc
	RS6000	AIX 3.2.3	cc
	Sun4c	SunOS 4.1.2	cc/unproto

Re: FAQ system list

[Alan Watson]

Some people have asked what the following footnotes refer to:

            [i] See 4.13.
            [k] See 4.13.
            [l] See 5.6.
            [m] See 5.5.
            [n] See 1.5.

1.5 recommends that rc should be statically linked on systems including
those running SunOS, Solaris, and OSF/1.  

4.13 mentions the deficient test in SCO Unix and the complete absence
of /bin/test in Unicos (took me a while to figure out why trip.rc
wasn't working...).

5.5 mentions that Apollos require a real binary for the login shell, not
a script (and I though /etc/shells was bad to start with).

5.6 describes the NeXT window manager brain damage.

FAQ system list

[mycroft]

   4.13 mentions the deficient test in SCO Unix and the complete absence
   of /bin/test in Unicos (took me a while to figure out why trip.rc
   wasn't working...).

Oh, I forgot about this.  HP/UX 8.0 doesn't have /bin/test; 9.0 does.
Also, any shell not listed in /etc/shells or beginning with `r' is
considered `restricted', and any invocation of shell(3) will fail.
This breaks a *lot* of things--even xrdb.

Re: FAQ system list

[malte]

	1.5 recommends that rc should be statically linked on systems including
	those running SunOS, Solaris, and OSF/1.  

What does this mean? Have I been running rc for about 1 1/2 years without
problems just by lucky chance ???

Malte

Re: FAQ system list

[Chris Siebenmann]

| What does this mean? Have I been running rc for about 1 1/2 years without
| problems just by lucky chance ???

 At least on Solaris and SunOS, if you static-link rc it will run much
faster (generally when forking programs).
 In fact, if you static-link everything that forks programs, your system
performance will probably suddenly jump. It's quite remarkable.

	- cks

Re: FAQ system list

[Stefan Dalibor]

> As part of the FAQ list, I would like a table of architectures, OSes,
> and compilers with which rc is known to work.  If you've managed to
> compile rc on a system which you do not see on this list, please drop
> me a line.  

You can add Motorola m88k on SYSTEM V/88 R32V3 to your list; I compiled
rc-1.4 ok and it passed trip.rc successful. The following definitions in
config.h were required:

#define NOLIMITS		/* SYSTEM V/88 is a rather dumb SysV R3 */
#define DEFAULTINTERP "/bin/sh"	/* it is so dumb that even /bin/{true,false}
				 * don't start with `#!/bin/sh'...
				 */
#define PROTECT_ENV		/* trip.rc fails without that
				 */

Compilation was done with gcc (version 2.2.2) and Green Hills cc (version
1.8.5). To use the latter, unproto (version later than 1.4) is needed -
but you should really try to avoid Green Hills cc if possible (it's the
worst cc I ever saw); if you must, be sure ALL optimization flags are
turned off.

Stefan Dalibor (dalibor@immd3.uni-erlangen.de)