rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Stefan Dalibor <dalibor@immd3.informatik.uni-erlangen.de>
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: FAQ system list
Date: Fri, 18 Jun 1993 06:57:17 -0400	[thread overview]
Message-ID: <9306181057.AA03915@faui33.informatik.uni-erlangen.de> (raw)


> 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)



             reply	other threads:[~1993-06-18 10:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1993-06-18 10:57 Stefan Dalibor [this message]
     [not found] <alan@oldp.astro.wisc.edu>
1993-06-16 17:38 ` malte
1993-06-16 17:41   ` Chris Siebenmann
  -- strict thread matches above, loose matches on Subject: below --
1993-06-16 15:02 Alan Watson
1993-06-16 16:52 ` mycroft
1993-06-16  7:34 noel
1993-06-16  2:27 Tom Culliton x2278
1993-06-15 23:18 Alan Watson
1993-06-15 23:25 ` mycroft

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9306181057.AA03915@faui33.informatik.uni-erlangen.de \
    --to=dalibor@immd3.informatik.uni-erlangen.de \
    --cc=rc@hawkwind.utcs.toronto.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).