From owner-freebsd-stable Fri Oct 11 10: 1:46 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E33BE37B401 for ; Fri, 11 Oct 2002 10:01:44 -0700 (PDT) Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [24.147.188.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1BE843E8A for ; Fri, 11 Oct 2002 10:01:43 -0700 (PDT) (envelope-from freebsd-stable-local@be-well.no-ip.com) Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [24.147.188.198] (may be forged)) by be-well.ilk.org (8.12.6/8.12.5) with ESMTP id g9BH1a8s002497; Fri, 11 Oct 2002 13:01:36 -0400 (EDT) (envelope-from freebsd-stable-local@be-well.no-ip.com) Received: (from lowell@localhost) by be-well.ilk.org (8.12.6/8.12.6/Submit) id g9BH1aot002494; Fri, 11 Oct 2002 13:01:36 -0400 (EDT) X-Authentication-Warning: be-well.ilk.org: lowell set sender to freebsd-stable-local@be-well.ilk.org using -f To: "Kevin Oberman" , "Jamie Heckford" , freebsd-stable@FreeBSD.ORG Subject: Re: Compiling a New Kernel References: <20021011152433.6CE075D04@ptavv.es.net> From: Lowell Gilbert Date: 11 Oct 2002 13:01:36 -0400 In-Reply-To: <20021011152433.6CE075D04@ptavv.es.net> Message-ID: <44bs60gb9r.fsf@be-well.ilk.org> Lines: 39 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Kevin Oberman" writes: > > From: "Jamie Heckford" > > Date: Fri, 11 Oct 2002 10:11:30 +0100 > > Sender: owner-freebsd-stable@FreeBSD.ORG > > > > Bizarre.... how could it be different/not work if you have cvsup'd all of your sources including sys/ tree at exactly the same time, > > and compile your kernel just after the installworld? > > > > There has to be something im missing here, feel free to humiliate me with an in depth explanation ;) > > > > J > > > > > Jamie, > > Please do not top post! > > When you build a new world (make buildworld), none of the new tools > that have been built are installed. So any kernel built with this > system will attempt to use the existing tools. > > If something critical to building the kernel, say the .mk files or > compiler, have been updated and the kernel Makefile has been modified > to work with the new .mk files, any attempt to build the kernel with > existing, installed tools is doomed to failure. > > The magic of make in /usr/src is that make will modify its environment > to use the new, uninstalled tools and .mk files. So changes in the > tools used to build the kernel can break the "old" style of kernel > build, but the "make kernel" method will always work. The other thing that Jamie Heckford seems to have missed is that one should be building your new kernel *before* the installworld. In fact, the approved upgrade procedure is to *reboot* under the *new* kernel *before* doing the installworld. After you have installed both the new kernel and the new userland, it *is* safe to use the "old method" of building kernels. As long as the sources don't get touched, anyway. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message