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.
The easy solution is to document the fact that you need to use
KBUILD_OBJTREE=$KBUILD_SRCTREE_000 when bootstrapping your system and that
you have to be careful with shadow trees that mess with /include/...
Fixing cross-gcc is almost hopeless (someone might need to bootstrap
gcc 2.95.2 with kernel 2.6 and we can't change every compiler source), but
I
suppose that there will be a new glibc for kernel 2.6 that can learn about
kbuild.
However, a clean solution would require to get rid of user space (read:
glibc)
access to autoconf.h and that could be a major task (e.g. we want to have
only
one set of headers for both s390 and s390x in the future, depending on
CONFIG_ARCH_S390X). Still, this would leave a problem for 3rd party kernel
modules that don't use shadow trees.
Arnd <><
|---------+---------------------------------------->
| | Giacomo Catenazzi |
| | <[EMAIL PROTECTED]> |
| | Sent by: |
| | [EMAIL PROTECTED]|
| | ceforge.net |
| | |
| | |
| | 05/06/02 08:53 AM |
| | Please respond to Giacomo |
| | Catenazzi |
| | |
|---------+---------------------------------------->
>---------------------------------------------------------------------------------------------------------+------------------------|
|
| |
| To: [EMAIL PROTECTED]
| |
| cc: kbuild-devel <[EMAIL PROTECTED]>
| |
| Subject: Re: [kbuild-devel] Re: installing header files
| |
>---------------------------------------------------------------------------------------------------------+------------------------|
Brendan J Simon wrote:
>
>
> Keith Owens wrote:
> Does anyone know how Linux distros (debian, redhat, etc) populate the
> linux header files in /usr/include/linux ? Is a crude copy or is it
> done via a make target ?
According FHS (and Debian, RH,... follow FHS), /usr/include/linux
is created by glibc. Thus ask glibc people about how they to do that.
Anyway it would be nice to have some infrastructure in kbuild-2.5
to generated headers files. I.e. for external modules and other
*strict* kernel related programs.
giacomo
_______________________________________________________________
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
_______________________________________________________________
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
