Date: Mon, 10 Jul 2000 20:20:35 -0500 From: Richard Wackerbarth <rkw@dataplex.net> To: Greg Lehey <grog@lemis.com> Cc: Kris Kennaway <kris@FreeBSD.ORG>, stable@FreeBSD.ORG Subject: Re: HEADS UP! Always use the 'make buildkernel' target to make yer kernels Message-ID: <00071020203500.18574@nomad.dataplex.net> In-Reply-To: <20000711103710.B21954@wantadilla.lemis.com> References: <Pine.BSF.4.21.0007092043510.33246-100000@freefall.freebsd.org> <14697.55301.614418.390096@onceler.kcilink.com> <20000711103710.B21954@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 10 Jul 2000, Greg Lehey wrote: > Agreed. I tried it out and found a number of things I didn't like > about it. Basically, it's a completely different build process: > > 1. Before building, it removes the existing kernel build tree. > There's no good reason for this. Agreed > 2. It builds in a different tree (/usr/obj instead of > /usr/src/sys/compile). These two points mean that if you later > want to go back and tune your kernel (change a driver parameter, > say), you can't just do a config; cd ../../compile/FOO; make, you > have to go the whole nine yards. I've argued (to no avail) that the whole kernel build was always "wrong" and that kernels should be treated in the same structure that is used to build userland programs. In particular, each kernel should get its own source directory just like each each user program does. The kernel has one primary source file. This file gets "compiled" by "config" (just as "foo.y") would get processed by "yacc" before calling "gcc" to actually do the compile. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00071020203500.18574>