Date: Mon, 22 Jan 2001 02:47:45 -0500 From: "Donald J . Maddox" <dmaddox@sc.rr.com> To: John Baldwin <jhb@FreeBSD.ORG> Cc: Peter Wemm <peter@netplex.com.au>, The Hermit Hacker <scrappy@hub.org>, freebsd-current@FreeBSD.ORG Subject: Re: lastest kernel from cvs ( sh exists with signal 8 ) Message-ID: <20010122024745.A19253@cae88-102-101.sc.rr.com> In-Reply-To: <XFMail.010121233549.jhb@FreeBSD.org>; from jhb@FreeBSD.ORG on Sun, Jan 21, 2001 at 11:35:49PM -0800 References: <20010122022757.B18935@cae88-102-101.sc.rr.com> <XFMail.010121233549.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jan 21, 2001 at 11:35:49PM -0800, John Baldwin wrote: > > On 22-Jan-01 Donald J . Maddox wrote: > > > > 1) rm -r /usr/include; cd /usr/src; make includes > > I just do 'make includes' w/o the rm of /usr/include when I do this.. I used to do 'make -DCLOBBER includes' to make sure no old stuff survived, but somebody decided that was just too convenient, I guess. No CLOBBER in the Makefiles anymore... <SNIP> > This should work, except that buildkernel has a few problems: > > 1) It (ab)uses the KERNEL make variable so that it now has 2 conflicting > meanings. Simply using KERNCONF for the buildkernel case instead can fix this, > however. > > 2) It hides the output from config(8). config(8) prints out all sorts of > useful warnings when options are deprecated, etc., but buildkernel hides these > from the user. The problem is that config(8) is by design an interactive tool, > which buildkernel fails to take into account. The hack now is to have > config(8) treat warnings as errors instead. :-/ I think this is a good policy :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010122024745.A19253>