On Mon, 6 May 2002 14:06:04 +0200, 
"Arnd Bergmann" <[EMAIL PROTECTED]> wrote:
>IIRC, you have to specify the kernel include path when configure'ing glibc
>as well as (cross) gcc. They are copied when installing those. Usually, you
>would do something like
>./configure --with-kernel-header=$HOME/linux-current/include
>
>The two problems when using kbuild-2.5 are the 'asm' symlink and
>autoconf.h,
>which are not generated in the source tree but in the object tree.

Good point.  I will add an optional variable KBUILD_INCLUDETREE and a
target to build the include tree in that directory, including autoconf
and the asm subtree.  The nice thing is that it will finally put paid
to the "glibc points to kernel source tree" mess, glibc and everybody
else will be forced to use a copy.  Added to my to do list for after
kbuild 2.5 goes into the kernel.


_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel

Reply via email to