[Dana Lacoste] > Essentially, whatever solution is implemented MUST ensure : > > 1 - glibc will work properly (the headers in /usr/include/* don't > change in an incompatible manner) > > 2 - programs that need to compile against the current kernel MUST > be able to do so in a quasi-predictable manner. (2) is bogus. NO program needs to compile against the current kernel headers. The only things that need to compile against the current kernel headers are kernel modules and perhaps libc itself. As I put it a few days ago-- http://marc.theaimsgroup.com/?l=linux-kernel&m=97658613604208&w=2 So for your external modules, let me suggest the lovely /lib/modules/{version}/build/include/. Recent-ish modutils required. Peter - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Re: Linus's include file strategy redux Miquel van Smoorenburg
- Re: Linus's include file strategy redux Alan Cox
- Re: Linus's include file strategy redux Alexander Viro
- Re: Linus's include file strategy redu... David Riley
- Re: Linus's include file strategy ... Alexander Viro
- Re: Linus's include file strategy redux Marcus Sundberg
- Re: Linus's include file strategy redux Kurt Roeckx
- Re: Linus's include file strategy redux Dana Lacoste
- Re: Linus's include file strategy redu... Alex Buell
- Re: Linus's include file strategy redu... Peter Samuelson
- Re: Linus's include file strategy ... Dana Lacoste
- Re: Linus's include file stra... Peter Samuelson
- Re: Linus's include file stra... David Schleef
- Re: Linus's include file strategy redu... richard offer
- Re: Linus's include file strategy ... Peter Samuelson
- Re: Linus's include file strategy redux Alexander Viro
- RE: Linus's include file strategy redux LA Walsh
- Re: Linus's include file strategy redux Chmouel Boudjnah
- Re: Linus's include file strategy redux Werner Almesberger