[email protected] wrote:
>
> In article <[email protected]> you [email protected] wrote:
> >Let's get this straight: #include <linux/*> and #include <asm/*> are
> >*expected* to be the kernel headers. This is a completely different
> >issue from the fact that glibc headers shouldn't #include these
> >headers like libc5 did.
>
> And IMHO to be able to do this, one should have to provide an explicit
> -I/usr/src/my-kernel/linux/include, it should not be the default.
>
I disagree. It makes life far too painful for the end user, for really no gain.
-hpa
--
<[email protected]> at work, <[email protected]> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
In article <[email protected]> you [email protected] writes:
>[email protected] wrote:
>> And IMHO to be able to do this, one should have to provide an explicit
>> -I/usr/src/my-kernel/linux/include, it should not be the default.
>
>I disagree. It makes life far too painful for the end user, for really no gain.
The idea was to make a point, that #include <linux/xxx.h> really is
a kernel/kernel aware application thing only. It ought to reduce the
number of people who try to include kernel only stuff without knowing
that it is a nono most of the time.
It isn't all that hard to add the following lines to the Makefiles
for an application that needs the kernel includes:
KERNELDIR=/usr/src/linux
CFLAGS+=$(KERNELDIR)/include
And then standardise on /usr/src/linux as the directory where the kernel
includes for the current kernel reside on a distribution. Those who
compile multiple kernels on the same system should be savvy enough to
do "KERNELDIR=/usr/src/my-kernel/linux make" or modify the Makefile.
/Christer
--
"Just how much can I get away with and still go to heaven?"