Date: Mon, 2 Mar 2009 10:43:37 +0100 From: Polytropon <freebsd@edvax.de> To: Paige Thompson <erratic@devel.ws> Cc: nightrecon@verizon.net, freebsd-questions@freebsd.org Subject: Re: Kernel Compile issue Message-ID: <20090302104337.d06b2b63.freebsd@edvax.de> In-Reply-To: <5061b39c0903020128i63f81812ne7699dedb4e4b8a5@mail.gmail.com> References: <5061b39c0903020021t311f69c8va16b425e13f80eeb@mail.gmail.com> <5061b39c0903020026u7ad4d422w8f572f35bb27f9d1@mail.gmail.com> <gog805$qrh$1@ger.gmane.org> <5061b39c0903020128i63f81812ne7699dedb4e4b8a5@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2 Mar 2009 01:28:59 -0800, Paige Thompson <erratic@devel.ws> wrote: > Mike, > > I think you misread what I sent, however I noticed that you used > 'KERNELCONF' instead of 'config' (as I noted) but I still get the same > error. Correct is KERNCONF=<name of config file> as parameter for buildkernel and installkernel targets. Allthough the "old way" using config <kernel> && make depend && make is still supported. Don't miss the "make depend". > I want to say the issue must have something to do with the fact that > there's no environment variables that specify the include directories. As far as I know, there are system defaults that apply. When building from updated sources, the files within the source tree are used (in /usr/src). There's nothing that should be in the env output. I'd suggest to follow the already given advice to work exactly "by manual", at least for the first time. Have a look at the comments /usr/src/Makefile, they're explaining the most obvious mistakes one could make. -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090302104337.d06b2b63.freebsd>