From owner-freebsd-stable Tue Jul 11 1:41: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wysoft.tzo.com (c481444-a.bremtn1.wa.home.com [24.12.235.202]) by hub.freebsd.org (Postfix) with ESMTP id 1A7A737B5A0; Tue, 11 Jul 2000 01:40:57 -0700 (PDT) (envelope-from wysoft@wysoft.tzo.com) Received: from localhost (wysoft@localhost) by wysoft.tzo.com (8.10.1/8.10.1) with ESMTP id e6B8al803023; Tue, 11 Jul 2000 01:36:47 -0700 (PDT) Date: Tue, 11 Jul 2000 01:36:47 -0700 (PDT) From: Jeff Wyman To: Francisco Reyes Cc: Vivek Khera , "stable@FreeBSD.ORG" , Kris Kennaway Subject: Re: why new buildkernel (was HEADS UP! Always use the 'make buildkernel' ..." In-Reply-To: <200007110601.CAA36394@vulcan.addy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Why is this new procedure necessary. > I recall reading is because of some new additions, but what were > these additions (I have seen the name, but have no clue what > they are.. binutils?) and why the new, more cumbersome, > procedure? > francisco > Moderator of the Corporate BSD list > http://www.egroups.com/group/BSD_Corporate If you missed one of Kris Kennaway's previous messages about this, this is how he described it: --SNIP-- Buildkernel internally handles tool dependency problems, where the kernel build depends on tools which were built by make installworld, but not yet installed on the system. The alternative is to post a detailed list of which bits must be installed before you can build your new kernel, each time it happens, which is error-prone and subject to people not reading their mail (oops, which is exactly what happened this time around). --SNIP-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message