> In article <cistron.Pine.GSO.4.05.9904221152180.22491-100000@holmes.calvin.edu>,
> Jon Niehof <jnieho38@calvin.edu> wrote:
> >If we're supposed to leave those directories alone, what
> >about the kernel structures which differ between 2.0 and
> >2.2?
>
> That's only an issue if you compile admin-level programs that use
> special linux only and linux-2.2.x only features. And then you'd
> just use -I/usr/src/linux/include
>
> No userlevel program should ever include <linux/....>
IMHO it's a broken concept that every `admin-level' programs
has to hard-wire a path to kernel includes in configure/makefile.
is it real that GLIBC [authors] care that less for `admin-level' stuff ?
and even if most/all admin-level authors would do so, compiling their
code still breaks on systems where admin-level includes and kernel sources
are _not_ located in /usr/src/linux/ (like on my PC;)
Harald
--
All SCSI disks will from now on ___ _____
be required to send an email notice 0--,| /OOOOOOO\
24 hours prior to complete hardware failure! <_/ / /OOOOOOOOOOO\
\ \/OOOOOOOOOOOOOOO\
\ OOOOOOOOOOOOOOOOO|//
Harald Koenig, \/\/\/\/\/\/\/\/\/
Inst.f.Theoret.Astrophysik // / \\ \
koenig@tat.physik.uni-tuebingen.de ^^^^^ ^^^^^
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/