Incorrect behaviour RE: /lib/cpp fails due to missing kernelincludes!!!

[Ranitha Mapatuna]

Sorry I meant symlinking of /usr/include/linux to point to
/usr/src/linux. only read what I wrote after I had sent it on its way.

Ranitha

-----Original Message-----
From: lunar-bounces at lunar-linux.org
[mailto:lunar-bounces at lunar-linux.org] On Behalf Of Ranitha Mapatuna
Sent: Friday, 11 April 2003 7:20 PM
To: 'Lunar Linux Mailing List! (all are welcome)'
Subject: Incorrect behaviour RE: /lib/cpp fails due to missing
kernelincludes!!!

Hey,
	FYI, this symlinking of the linux header files of the current
kernel from /usr/src/linux or /usr/include/linux is incorrect strictly
speaking. The includes in /usr/include/linux should be from the kernel
that glibc was built against which is not necessarily the current one.

Ranitha

-----Original Message-----
From: lunar-bounces at lunar-linux.org
[mailto:lunar-bounces at lunar-linux.org] On Behalf Of Auke Kok
Sent: Friday, 11 April 2003 2:34 AM
To: Lunar Linux Mailing List! (all are welcome)
Subject: /lib/cpp fails due to missing kernel includes!!!


PLEASE READ:

SYMPTOM:
> configure: error: C preprocessor "/lib/cpp" fails sanity check

REASON:
the sole reason is that the kernel includes are not available. In lunar
we tend to keep the kernel includes in /usr/src/linux/include, and there
are appropriate symlinks in /usr/include/linux that point there.


CAUSE:
if the chain of symlinks to the right include dir is broken, cpp cannot
even include the basic set of includes, and therefore will break
completely.

FIX:
untar your kernel sources in /usr/src/ and symlink the correct kernel
version directory to /usr/src/linux (or lin linux to do it
automatically).

greetz,

sofar

-- 
Auke Kok <auke.kok at planet.nl>

_______________________________________________
Lunar mailing list
Lunar at lunar-linux.org
http://lunar-linux.org/mailman/listinfo/lunar