From owner-freebsd-stable Mon Jul 10 23:25:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id E774337BC9D; Mon, 10 Jul 2000 23:25:26 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id XAA75429; Mon, 10 Jul 2000 23:25:26 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 10 Jul 2000 23:25:26 -0700 (PDT) From: Kris Kennaway To: Francisco Reyes Cc: "stable@FreeBSD.ORG" 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 On Tue, 11 Jul 2000, Francisco Reyes wrote: > On Mon, 10 Jul 2000 05:34:10 -0700 (PDT), Jeff Wyman wrote: > > >The buildkernel process is used _during_ an upgrade. After the > >new 4.0 kernel has been booted and appropriate changes have been made to > >the system, kernels may be built successfully in the traditional way. > > 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? From time to time the kernel build may depend on tools which are not yet installed on the system, for example new versions of the compiler or assembler (as was the case recently, which sparked this discussion). You can either try and identify and install all of the new bits by hand prior to building your kernel, or use buildkernel which uses the correct tools automatically. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message