Skip to contentSkip to conversation

Set gcc to kernel header path

DISCUSSION Tibor Kendl 2 participants 2 messages Feb 27, 2004

lore
Share & tools
lore
#0 lore raw

Dear mailing list members!

I'd like to know, how do you solve this problem on your own systems. I've installed a linux distribution with a 2.2.18 kernel, than i've downloaded, compiled and installed a 2.6.2 kernel. How can i make, if i want to compile any application ( like Samba, Apache, KDE, etc...), the gcc compiler use the '/usr/src/linux-2.6.2/include' header path instaead of the '/usr/include' for such include directories like 'linux', 'asm', 'asm-generic', etc...?

Yours
Tibor Kendl

#1 lore raw
Quoted 10 lines · Tibor Kendl

Dear mailing list members!

I'd like to know, how do you solve this problem on your own systems. I've installed a linux distribution with a 2.2.18 kernel, than i've downloaded, compiled and installed a 2.6.2 kernel. How can i make, if i want to compile any application ( like Samba, Apache, KDE, etc...), the gcc compiler use the '/usr/src/linux-2.6.2/include' header path instaead of the '/usr/include' for such include directories like 'linux', 'asm', 'asm-generic', etc...?

Quoted 3 lines

Yours
Tibor Kendl

	gcc -I/usr/src/linux-2.6.2/include

... if you are sure that's what you want. Normally, you use the headers that your 'C' runtime library was compiled with, i.e., what's in /usr/include.

gcc will search the -I/path first, then do the other ones unless you use -nostdinc on the command-line as well. If you use -nostdinc, you need to also put -Igcc -print-file-name=include on the command line, also or else gcc won't find stddef.h, etc., which are not in one of the "standard places".

Cheers,
Dick Johnson
Penguin : Linux version 2.4.24 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.