module: glibc

Jasper Huijsmans jasper at lunar-linux.org
Fri May 20 19:33:16 UTC 2005


Jerry Lundström wrote:

>Jasper Huijsmans wrote:
>  
>
>>The _whole_ point of the kernel-headers package (at least for 2.6, 
>>because there isn't any for 2.4) is that glibc should NOT be compiled 
>>against raw kernel headers.
>>    
>>
>
>We will never be able to escape this since some programs do that.
>
>  
>
>>So, either we don't do kernel-header packages and compile against 
>>current kernel sources -- note this is not recommended by Linus -- or we 
>>have a userspace header package with sanitized headers for 2.6 with a 
>>fallback home-made solution for 2.4.
>>    
>>
>
>Hmm, that doesnt make sense, why should you use your kernel versions 
>headers?
>For the 2.4 vs 2.6 I can see a point to let programs catch up to 2.6 .
>
>  
>
>>Building against kernel sources _and_ having a kernel-header package 
>>doesn't really make sense.
>>    
>>
>
>Well, my situations is my own since I don't use the kernel package or 
>the kernel-headers package, I just didnt want lunar to mess up my own 
>headers when there was no point.
>
>  
>
Yeah, I think that's what we should support. Install a kernel-header 
package from lunar or fix your own headers in whatever way you like. 
Either way, glibc should build against userspace headers in 
/usr/include/linux, never to any kernel source tree directly.

    Jasper


More information about the Lunar-dev mailing list