Re: kernel headers

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 05 April 2003 01:01 pm, James P. Roberts wrote:

> > > Can anyone explain the correct procedure at this point?
> >
> > The kernel-headers package contains the headers used to build glibc.
> > The .h files live in /usr/include/{asm,linux}.
>
> And therefore when I compile with gcc, which uses glibc, it wants to
> include the same headers as were used to compile the glibc libs?  Is
> that the idea? And that's why I don't want to have
> /usr/include/{asm,linux} point to the same headers used to compile the
> kernel, because it might conflict with the glibc headers?  I think I
> see.

Correct.

> > The kernel-headers package is not upgraded when the kernel is
> > upgraded.
>
> Why not?  It used to be...  Hence my confusion, of course.

Yes, I do remember that the kernel-headers were often upgraded in the 
past. I really don't know why, to be honest.

> > The headers used for the current kernel are in
> > /usr/src/linux-{kernel-version}/include/
> > (A symlink should exist, /lib/modules/`uname -r`/build, which points
> > to the installed kernel-source.)
>
> Yes.  So, the only thing that gets compiled with the kernel-source
> headers, is the kernel itself?  Anything else should be compiled
> against the glibc headers, right?  And just because something is
> compiled and linked using headers different from the kernel, that's OK.
>  It must be, or else compiled code would not be portable, and
> everything would break upon kernel upgrade... Have I reached
> understanding, yet?

Yes, the kernel and kernel modules rely on the headers for the running 
kernel. User space apps rely on the glibc headers.

> I am grateful to know that.  Thank you for your help!

You're welcome.

- -- 
- -Michael

pgp key:  http://www.tuxfan.homeip.net:8080/gpgkey.txt
Red Hat Linux 7.{2,3}|8.0 in 8M of RAM: http://www.rule-project.org/
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+j11xn/07WoAb/SsRAuPyAKCUkRfFLKLGkrdbYpZKiSc//kYA4ACgoN1k
zc0wy6LE+6gxOs6EY2eViZw=
=e3Cg
-----END PGP SIGNATURE-----