[Wylug-help] When my kernel sources are in a non-standard place...

[Thomas, Nicholas]

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]

Hi,

As part of an automated build process, we checkout a copy of kernel sources
from our Source Code repository, and proceed to do some building.
There are no kernel sources in the usual /usr/src/linux directory.
The kernel sources are put somewhere relative to the `pwd` of the build
script.

The problem is that when I see the #include <linux/limits.h> statement, the
compiler is trying to get the headers from
/usr/include/linux/limits.h
Unfortunately the /usr/include/linux is a symbolic link to
/usr/src/linux/include/linux which doesn't exist on my build system :(
So, the build fails.

I can solve some of my problems using the C_INCLUDE_PATH env var. But, I
cannot find a way of influencing where to get the
/usr/include/linux headers.

I know I can mess about with the /usr/src/linux symbolic link from within
the build script, but I want to build this stuff as a regular user - not
root.
I was also hoping to find an easy solution like C_INCLUDE_PATH.

Any ideas?

Regards

Nick

_________________________
Nick Thomas
Leading Software Engineer
Eldon Technology Limited
Park House
College Road
Bingley
West Yorkshire, UK
BD16 4UD
Tel: +44 1274 568432
Fax: +44 1274 551561
Email: nick.thomas at eldon.co.uk


--