From owner-freebsd-current Mon Jan 29 14:56:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA18271 for current-outgoing; Mon, 29 Jan 1996 14:56:47 -0800 (PST) Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA18263 for ; Mon, 29 Jan 1996 14:56:41 -0800 (PST) Received: (from julian@localhost) by ref.tfs.com (8.6.12/8.6.9) id OAA06769; Mon, 29 Jan 1996 14:55:51 -0800 From: Julian Elischer Message-Id: <199601292255.OAA06769@ref.tfs.com> Subject: Re: I'm rather annoyed with -current. To: nate@sri.MT.net (Nate Williams) Date: Mon, 29 Jan 1996 14:55:51 -0800 (PST) Cc: rkw@dataplex.net, nate@sri.MT.net, current@FreeBSD.org In-Reply-To: <199601292111.OAA09260@rocky.sri.MT.net> from "Nate Williams" at Jan 29, 96 02:11:39 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text 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.