> On Friday 04 April 2003 09:39 pm, James P. Roberts wrote:
> > Dear Seawolf Users:
> >
> > I have a question regarding the kernel-headers package.
> >
> > When RHN issues kernel updates, they no longer include any updates for
> > the kernel-headers rpm. The last one issued was something like version
> > 2.4.9-blah-blah.
> >
> > The files provided by that kernel-headers package are the *.h files in
> > the /usr/include/asm and /usr/include/linux directories. OK. I can
> > see that most of them are the same as in /usr/src/linux-2.4/include/asm
> > and ../linux; but clearly, some of those files have since been
> > updated/added/deleted (compared to the /usr/include files) by newer
> > versions of kernel-source rpm.
> >
> > It would seem reasonable to uninstall the kernel-headers package, and
> > put symlinks in place of /usr/include/asm and ../linux to point
> > directly to the latest and greatest kernel header files. BUT, I cannot
> > uninstall kernel-headers, because it is required by glibc-devel, which
> > is required by gcc. ARRRGH.
>
> You _really_ don't want to do this.
Fair enough. I will not do that. Thanks.
>
> > So, now that I have upgraded to a newer kernel version
> > 2.4.18-blah-blah, and the source contains different header files, am I
> > totally screwed if I try to compile things with gcc and run them under
> > this new kernel? (Only if the code uses an obsolete header file, I
> > suppose, but trying to determine that reliably could be a nightmare.)
> >
> > 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.
>
> The kernel-headers package is not upgraded when the kernel is upgraded.
Why not? It used to be... Hence my confusion, of course.
> 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?
>
> Things should compile fine just the way they are.
>
> - --
> - -Michael
>
I am grateful to know that. Thank you for your help!
Jim
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
