The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Work I've done with a PDP-11 simulator
Date: Sun, 11 May 2014 13:21:39 -0400	[thread overview]
Message-ID: <6E54FFD0-B049-4168-B119-B54F835F3C12@ccc.com> (raw)
In-Reply-To: <20140511020618.8E98E18C0BB@mercury.lcs.mit.edu>

Noel

I wonder if that is the so called "Typesetter C" compiler which was released independently of the system -  you needed it compile the new troff and support for other typesetters besides the CAT.   my memory which is hazy now was that typesetter C was what Mashey used for what would become PWB.   we should ask him

Clem

On May 10, 2014, at 10:06 PM, jnc at mercury.lcs.mit.edu (Noel Chiappa) wrote:

>> From: Larry McVoy <lm at bitmover.com>
> 
>> have you gotten to a point where you can rebuild the world and install
>> your newly built stuff?
> 
> Well, I haven't tried to do that (it's not something that I'm that interested
> in), but it _should_ be possible, since the 'vanilla' V6 distribution does
> include the source for pretty much everything (including the C compiler,
> assembler, loader, etc).
> 
> 
> (This does not include the stuff from the Shoppa disk, like the new C
> compiler, where I don't have the source. [The PWB distribution, which
> includes a C compiler from 1977, is probably pretty close. Looking into
> the PWB stuff is one of my next projects; we have 17 different versions
> of that stuff, and I'd like to see what the differences among them are,
> and maybe create a 'canonical' PWB.]
> 
> Also, per the 'Improvements' page, I have source for the Standard I/O
> Library, but I'm using the binary library from the Shoppa disk, which may or
> may not correspond to that source.)
> 
>    Noel
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs



  parent reply	other threads:[~2014-05-11 17:21 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-11  2:06 Noel Chiappa
2014-05-11  2:31 ` Gregg Levine
2014-05-11  2:34   ` Gregg Levine
2014-05-11 17:21 ` Clem Cole [this message]
2014-05-11 17:24   ` Clem Cole
2014-05-11 18:50   ` Ronald Natalie
  -- strict thread matches above, loose matches on Subject: below --
2014-05-12 19:10 Noel Chiappa
2014-05-12 20:59 ` SPC
2014-05-12 17:06 Noel Chiappa
2014-05-12 17:20 ` SPC
2014-05-12 19:50 ` John Cowan
2014-05-12 14:49 Noel Chiappa
2014-05-11 23:13 Norman Wilson
2014-05-12  5:29 ` John Cowan
2014-05-11 16:16 Norman Wilson
2014-05-11 16:45 ` John Cowan
2014-05-11 22:19   ` pechter
2014-05-11  3:26 Noel Chiappa
2014-05-11  3:13 Noel Chiappa
2014-05-11  4:20 ` John Cowan
2014-05-11  0:51 Noel Chiappa
2014-05-11  0:57 ` Larry McVoy
2014-05-11  1:27   ` John Cowan
2014-05-11  1:58     ` Larry McVoy
2014-05-11  2:40       ` John Cowan
2014-05-05 15:32 Noel Chiappa
2014-05-04 23:54 Noel Chiappa
2014-05-05  1:53 ` John Cowan
2014-05-05  8:10   ` SPC
2014-04-30  2:19 Noel Chiappa
2014-05-03 22:14 ` SPC
2014-05-03 22:20   ` Gregg Levine
2014-05-03 22:22     ` Larry McVoy
2014-05-05 13:50 ` Kurt H Maier

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=6E54FFD0-B049-4168-B119-B54F835F3C12@ccc.com \
    --to=clemc@ccc.com \
    /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).