From owner-cvs-all Wed Jul 19 8: 9:15 2000 Delivered-To: cvs-all@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id 8271937B835; Wed, 19 Jul 2000 08:09:11 -0700 (PDT) (envelope-from marcel@cup.hp.com) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel1.hp.com (Postfix) with ESMTP id E542A31D; Wed, 19 Jul 2000 08:09:06 -0700 (PDT) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.02) with ESMTP id IAA03368; Wed, 19 Jul 2000 08:09:05 -0700 (PDT) Message-ID: <3975C491.70D86E0B@cup.hp.com> Date: Wed, 19 Jul 2000 08:09:05 -0700 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Ruslan Ermilov Cc: Marcel Moolenaar , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src Makefile.inc1 References: <200007190441.VAA77617@freefall.freebsd.org> <20000719121321.A54935@sunbay.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ruslan Ermilov wrote: > > The log message is incomplete. Actually (and this is great) we now > use bootstrap-tools first and only then saved binaries. We now do > not use installed binaries during installworld at all. You're right. I wasn't completely clear. > Question. What if we just expand the list of bootstrap-tools with > tools needed for installworld (the ones we now save)? The point here > is that (potentially) every tool that we use during installworld > could have bootstrapping problems. Correct, but there's a different incompatibility I'm trying not to hit upon: source incompatibility. It is not guaranteed that we can build all the tools in the first place. Currently, it seems that upgrading from 2.2.8 cannot be done as-is, because we have gperf in the bootstrap-tools and the native 2.2.8 C++ compiler doesn't grok its source. Building gcc in the bootstrap-tools might solve this, but makes it all a bit more hairy (we need certain tools in bootstrap-tools because we need to be able to build gcc in the cross-tools). The bottomline: Use what we can and rebuild only when necessary. > Particularly, I don't see why we need to save /usr/bin/install-info. > It is already built and will be preffered as bootstrap-tools's tool. Oops. I forgot that we now build install-info... I'll fix it ASAP. Thanks, -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message