Date: Fri, 26 Nov 2004 09:32:08 -0500 From: Brian Bobowski <bbobowski@cogeco.ca> To: Joshua Lokken <joshua.lokken@gmail.com> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: kernel compile error Message-ID: <41A73E68.9020509@cogeco.ca> In-Reply-To: <bc5b638504112606273f80a71@mail.gmail.com> References: <ef60af09041125215877bb0fbb@mail.gmail.com> <001101c4d37d$38b3d9a0$1200a8c0@gsicomp.on.ca> <41A6D558.8070007@yahoo.com> <20041126085255.GA87702@xor.obsecurity.org> <bc5b638504112606273f80a71@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Joshua Lokken wrote: >>On Fri, Nov 26, 2004 at 04:03:52PM +0900, Rob wrote: >> >> >>>Matt Emmerton wrote: >>> >>> >>>Having such a mechanism, would prevent lots of beginners in the >>>kernel compiling stuff, to get frustrated with errors like above. >>> >>> >Also, as you see, it's well-documented in the kernel config file ;) > > While this is true, it's also easy enough for someone to snip the directions when slicing things out of the config file. Assuming that the user won't do things the wrong way is a sure way to succumb to Murphy's Law(the real one). The main barrier I can see to this is getting whatever parses the config file to recognise such dependencies; as it is, it's the compiler that runs into the problem, not the program that calls the compiler. The compiler doesn't know where the relevant source is if not told to include it, after all. -BB
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41A73E68.9020509>