Date: 21 Dec 1997 00:30:39 +0100 From: Eivind Eklund <perhaps@yes.no> To: freebsd-hackers@FreeBSD.ORG, Karl Pielorz <kpielorz@caladan.tdx.co.uk> Subject: Re: Compiling Kernels on remote machine & using 'wrong' versions Message-ID: <86u3c3vbhc.fsf@bitbox.follo.net> In-Reply-To: j@uriah.heep.sax.de's message of Sat, 20 Dec 1997 11:15:55 %2B0100 (MET) References: <Pine.BSF.3.96.971216191332.1252A-100000@caladan.tdx.co.uk> <199712162123.WAA03783@rvc1.informatik.ba-stuttgart.de> <199712201015.LAA29341@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
j@uriah.heep.sax.de (J Wunsch) writes: > Wolfgang Helbig <helbig@Informatik.BA-Stuttgart.DE> wrote: > > > Just build the kernel in > > /home/phoenix/usr/src/sys/compile/<KERNELNAME>. AFAIK, the sources > > below the usr/src/sys directory are used exclusively for the kernel, > > regardless of the pathname of this directory. > > There might be some minor things like the inclusion of standard > (non-kenel) header files in `genassym' or `aicasm'. I've always been > able to resolve these issues at least manually (i.e.. by building those > two tools on the slow machine, aborting the `make' there, and > continuing the process on the fast machine in the NFS directory). The easiest way to solve this is to just extract the include directory, too. You want it like this: src/sys/<kernel source tree> src/include/<userland include tree> A directory named 'include' in the same directory as your sys directory will always be preferred over the includes installed on the machine. Eivind.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86u3c3vbhc.fsf>