From owner-freebsd-questions@FreeBSD.ORG Fri Nov 26 14:34:11 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0959616A4CE for ; Fri, 26 Nov 2004 14:34:11 +0000 (GMT) Received: from fep7.cogeco.net (smtp.cogeco.net [216.221.81.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id C425243D6E for ; Fri, 26 Nov 2004 14:34:10 +0000 (GMT) (envelope-from bbobowski@cogeco.ca) Received: from [24.150.215.98] (d150-215-98.home.cgocable.net [24.150.215.98]) by fep7.cogeco.net (Postfix) with ESMTP id D10731164; Fri, 26 Nov 2004 09:34:09 -0500 (EST) Message-ID: <41A73E68.9020509@cogeco.ca> Date: Fri, 26 Nov 2004 09:32:08 -0500 From: Brian Bobowski User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040626 Thunderbird/0.7.1 Mnenhy/0.6.0.104 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Joshua Lokken References: <001101c4d37d$38b3d9a0$1200a8c0@gsicomp.on.ca> <41A6D558.8070007@yahoo.com> <20041126085255.GA87702@xor.obsecurity.org> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Rob cc: FreeBSD cc: Kris Kennaway Subject: Re: kernel compile error X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2004 14:34:11 -0000 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