Date: Thu, 06 Mar 2008 11:32:40 +0100 From: Kris Kennaway <kris@FreeBSD.org> To: jau@iki.fi Cc: Remko Lodder <remko@FreeBSD.org>, freebsd-bugs@FreeBSD.org Subject: Re: kern/121292: FreeBSD-7.0 kernel build fails on FreeBSD-6.3 Message-ID: <47CFC848.9060300@FreeBSD.org> In-Reply-To: <200803060509.m2659N0C085966@jau.iki.fi> References: <200803060509.m2659N0C085966@jau.iki.fi>
next in thread | previous in thread | raw e-mail | index | archive | help
Jukka A. Ukkonen wrote: > Quoting Remko Lodder: >> Kris is not wrong here, you are confused ;) > > Entirely correct. I was confused. > > Anyhow my custom kernels have always been (and probably always > will be) based on generic and almost invariably only adding > things which are not default parts of generic. > The problem was a missing "device wlan_amrr" line which I had > skipped by accident while merging my older 6.3 custom config > and 7.0 generic. > > Previously parallel make has not let the potential error > messages roll several hundreds of lines out of a 50 line > xterm window but given up very quickly after an error. I guess you've been lucky, it's always worked this way. > For some reason this time any alleged error messages managed > to speed out of the xterm buffer completely. > Recording the whole build to a typescript file will apparently > be necessary in the future. > > This experience anyhow raised a question as well. > Should there be some sort of dependency checking added to > kernel builds such that any missing features were implicitly > included if other explicitly configured features depend on > them? > Such an extension could also make a point of informing the > poor fool building the kernel - in this case that would have > been me - of the features that need to be implicitly included > as dependencies. People occasionally float the idea of doing this, but no-one has come up with a suitable implementation. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47CFC848.9060300>