Shouldn't glibc-devel r: kernel-headers?

Jakub Bogusz qboosh at
Tue Oct 15 20:58:54 CEST 2002

On Sat, Oct 12, 2002 at 09:21:54PM +0200, Andrzej Krzysztofowicz wrote:
> > There are some situations when you should recompile
> > your glibc, but they are rare.
> Kernel 2.4+ headers are no longer intended to be used in userspace.
> Eg., you must hack them in some places to use them with C++.

Where? I didn't change anything in 2.4 headers and don't see such
problems (after recompiling glibc on those headers).
But I did see strange type conflicts when I tried to use fresh kernel
headers with glibc compiled on older headers (that was in 2.2.1x era).
Those problems dissapeared after recompiling glibc.

> So providing own copy of hacked kernel-headers included into glibc-devel
> seems to be the only choice when we switch into 2.4/2.6.

I agree - kernel headers in /usr/include/{asm,linux}, in glibc-devel
package for user space programs, and headers in %{_kernelsrcdir}/include
in kernel-headers package for distro kernel modules development.

I don't like the "kernel-fake package" idea - I used something like
this on RH (5.x ;)), and I don't want anymore.

Jakub Bogusz

More information about the pld-devel-en mailing list