From: Chet Ramey <chet.ramey@case.edu>
To: Dan Cross <crossd@gmail.com>, Ronald Natalie <ron@ronnatalie.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Any Bell 8-bit UNIX Efforts?
Date: Wed, 1 Mar 2023 09:12:02 -0500 [thread overview]
Message-ID: <31604b56-d527-bfc1-3d33-8c9e4a3b117c@case.edu> (raw)
In-Reply-To: <CAEoi9W7kjOZUBYB2fy1+=s111PS6K1V7Uzg2++QTD1gGF0arQQ@mail.gmail.com>
On 2/28/23 9:35 PM, Dan Cross wrote:
> On Tue, Feb 28, 2023 at 9:07 PM Ronald Natalie <ron@ronnatalie.com> wrote:
>> [snip]
>> At least it didn’t come with a prayer book like the Metalware compiler (which really needed all the divine intervention that it could get).
>
> Was that the one that shipped with the IBM RT? Is it just my
> imagination or did some of the error messages contain biblical
> references?
Yes! High C from Metaware. I wrestled with that compiling bash a lot; I
did a ton of development on AOS.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
next prev parent reply other threads:[~2023-03-01 14:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 19:48 [TUHS] " segaloco via TUHS
2023-02-27 3:55 ` [TUHS] " Warner Losh
2023-02-27 10:57 ` Jonathan Gray
2023-02-28 18:59 ` segaloco via TUHS
2023-02-28 19:03 ` Larry McVoy
2023-02-28 19:42 ` Clem Cole
2023-02-28 19:57 ` Bakul Shah
2023-02-28 23:31 ` Dave Horsfall
2023-03-01 0:39 ` Larry McVoy
2023-03-01 1:21 ` Rich Salz
2023-03-01 1:27 ` Warner Losh
2023-03-01 2:07 ` Ronald Natalie
2023-03-01 2:35 ` Dan Cross
2023-03-01 2:38 ` Ronald Natalie
2023-03-01 3:02 ` [TUHS] IBM RT/PC compilers [was " Charles H. Sauer
2023-03-01 4:02 ` [TUHS] " George Michaelson
2023-03-01 14:12 ` Chet Ramey [this message]
2023-03-02 9:05 ` [TUHS] " Jaap Akkerhuis via TUHS
2023-03-02 19:26 ` Clem Cole
2023-03-01 2:50 ` Jonathan Gray
2023-03-01 0:31 ` Jonathan Gray
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=31604b56-d527-bfc1-3d33-8c9e4a3b117c@case.edu \
--to=chet.ramey@case.edu \
--cc=crossd@gmail.com \
--cc=ron@ronnatalie.com \
--cc=tuhs@tuhs.org \
/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).