On Tue, 6 Nov 2001 15:33:37 -0600,
Peter Samuelson <[EMAIL PROTECTED]> wrote:
>[Bill Hay]
>> How does one build glibc with a kbuild 2.5 kernel? Glibc expects to
>> be pointed at a single directory containing the kernel header files
>> but when using kbuild the generated header files (eg version.h) end
>> up in a different directory to those distributed with the kernel.
>
>Then glibc will have to adapt. (This might sound glib [no pun
>intended] but it's true. glibc has always had to track specific new
>kernel features.)
On my todo list is adding a script that takes all the source files,
including the generated include files and creates a single source tree.
There will not be any make rules to run that script, I don't want the
makefiles polluted by lots of special case rules. The makefiles do a
standard build of the kernels, not support special build requirements.
Anybody with special build requirements should use the the ADDn
entries, see Documentation/kbuild/kbuild-2.5.txt under Additional
Targets and Commands.
make ADD0=single_source \
ADD0_DEP=$KBUILD_OBJTREE/.tmp_global/makefile \
ADD0_CMD='$KBUILD_SRCTREE_000/scripts/single_source.pl target_directory' \
single_source
The single_source.pl script (once written) will delete and create
target_directory containing a merged copy of all the sources.
>> This also caused me problems when trying to build the lvm utilities.
>
>Userland utilities should use the glibc copies of kernel headers - thus
>reducing the problem to one already solved ("glibc will have to
>adapt"). If you need a separate kernel header not distributed with (or
>newer than) glibc, you should include a copy in your source tar.
>That's long-standing policy - Linus took a stand on this back in '98 or
>so, IIRC. Nobody (except those distributing kernel-mode code) should
>ever need anything directly from /usr/src/linux.
Absolutely agree. If kbuild 2.5 breaks user space code that is
including kernel headers then I consider that to be a bug in the user
space code, not kbuild.
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel
