From owner-freebsd-current Mon Jan 29 15:21:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA20646 for current-outgoing; Mon, 29 Jan 1996 15:21:44 -0800 (PST) Received: from eel.dataplex.net (EEL.DATAPLEX.NET [199.183.109.245]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA20603 for ; Mon, 29 Jan 1996 15:21:18 -0800 (PST) Received: from [199.183.109.242] (cod [199.183.109.242]) by eel.dataplex.net (8.6.11/8.6.9) with SMTP id RAA03696; Mon, 29 Jan 1996 17:20:46 -0600 X-Sender: rkw@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 29 Jan 1996 17:20:50 -0600 To: Julian Elischer From: Richard Wackerbarth Subject: Re: I'm rather annoyed with -current. Cc: nate@sri.MT.net, current@FreeBSD.org Sender: owner-current@FreeBSD.org Precedence: bulk >> >> Unfortunately, we *have* to use them. You can't build a c-compiler >> w/out a C-compiler. Obviously, all of the support tools that go along >> with are also important. >> >> >> > First we make the tools into the object tree and then we turn around and >> > make the target binaries using those tools. > >When I make OSF1 >it starts off with some stashed away binaries of cc >then remakes them using the sources.. >then it remakes the libs with the new compilers >then it remakes the compilers with the new libs and then old new compilers >then compiles the rest of the tree using the new libs and new new compilers > >It doesn't touch what's on the host system for anything.. >it even looks in the source tree for the /usr/share/mk stuff >which BTW is based on the BSD stuff. And that is just the idea that I am proposing. OSF1 isn't the only system to do this. And we should do so also. ---- Richard Wackerbarth rkw@dataplex.net