The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Ron Natalie" <ron@ronnatalie.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Typesetter C Compiler and Troff (Re: Re: v6 Unix Documents)
Date: Sun, 01 Dec 2024 15:40:58 +0000	[thread overview]
Message-ID: <em34270a18-fa36-4c8a-9e4a-ff312a7c2682@2719b2c1.com> (raw)
In-Reply-To: <20241201042131.E7DD318C075@mercury.lcs.mit.edu>

Agreed, the typesetter C ran on a virgin V6 system.   That was the whole 
point.   It came out before most of us got real V7s.



------ Original Message ------
From "Noel Chiappa" <jnc@mercury.lcs.mit.edu>
To tuhs@tuhs.org
Cc jnc@mercury.lcs.mit.edu
Date 11/30/2024 11:21:31 PM
Subject [TUHS] Re: Typesetter C Compiler and Troff (Re: Re: v6 Unix 
Documents)

>     > From:
>
>     > I was able to rebuild both the UNSW and the native PWB compiler on PWB
>     > 1.0, but not to backport either to vanilla v6.
>
>Any idea what the problem was? I'm curious, because we ran a version of the
>Typesetter compiler on the MIT systems, which ran an enhanced V6.
>
>	   Noel
>

  reply	other threads:[~2024-12-01 15:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-01  4:21 Noel Chiappa
2024-12-01 15:40 ` Ron Natalie [this message]
2024-12-01 17:24   ` Clem Cole
2024-12-01 17:27     ` Clem Cole
2024-12-05  6:38 ` Dan Plassche
  -- strict thread matches above, loose matches on Subject: below --
2024-10-18  2:19 [TUHS] v6 Unix Documents Dan Plassche
2024-10-18 13:58 ` [TUHS] " G. Branden Robinson
2024-10-19  3:36   ` Jonathan Gray
     [not found]     ` <f4e18bf1-98bb-8844-c102-2a1b00fbab15@gmail.com>
2024-10-20  9:39       ` Jonathan Gray
2024-10-21  0:30         ` [TUHS] Typesetter C Compiler and Troff (Re: Re: v6 Unix Documents) Dan Plassche
2024-10-21  2:47           ` [TUHS] " Jonathan Gray
2024-12-01  3:28             ` Dan Plassche

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=em34270a18-fa36-4c8a-9e4a-ff312a7c2682@2719b2c1.com \
    --to=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).