I have been looking around for a way to install Kernel headers and either it doesnt work or they refer to commands for debian (apt-get install), so how can I install a kernel header in a freshly built kernel?
FIXED thank you all!

hello
well, the kernel headers file for kernel 2.6 in slackware 10.2 disk don't work for issues related to gcc compilier version. i remember after installing them ALSA was off. i suggest that you don't install the headers file, the old ones will do fine for kernel upgrade and compilation.

isnt the gcc compiler just pointing to the kernel source in /usr/src/linux in slackware?so if you followed the "this is how i do it all" topic ya dont need to extra install the headers

as I know the only issue with kernel headers is that you can't use kernel header versions different from the one used to compile glibc: pat compiles glibc against both headers of 2.4.x and 2.6.x shipped with slack. also the given header version is usable with every kernel older as or more than headers (you can use headers of 2.4.31 to compile every kernel of 2.4 series till the 2.4.31!).
instead is not sure that a newer kernel will work (you must try).

Personally I've installed *.c files and headers of 2.6.13 and I've compiled it with the gcc shipped with slack 10.2 and all went right! no problem with glibc or alsa... (I've just used alsa drivers avaible inside the kernel source).

my 2 cents,
M

The 2.4.31 headers installed in /usr/include (and sub-directories) are the ones to use in Slackware 10.2 for building 2.6 kernels. There is a warning file in the package which explains this.

Please, could you tell:
1) If I compiled 2.6 kernel, and installed it, will 2.4.31 headers stay
where they were? Installing new kernel doesn't install new kernel headers ?

2) Why do I need 2.4.31 headers to compile 2.6 kernel? I though that kernel source contains headers too, which will be then used.

If you unpack a new kernel source either from the Slackware site or from www.kernel.org, your 2.4.31 headers in /usr/include will remain intact and untouched.
I cannot personally explain this, but it has been explained in many places on this forum. If you really need to know, then do some forum searching.

You don't need 2.4 kernel headers to compile 2.6 kernel (2.6 will use it own headers), but to compile programs.

Some posts about this: http://www.linuxquestions.org/questi...76#post1721076
A more detailed one: http://www.linuxquestions.org/questi...61#post1723561

yes: you are completely right, but reading an old post of linus seems that the only trouble is the version used to compile glibc.. and it seems that pat uses both 2.4 and 2.6... so I really don't understend completely this warning... can you explain the thing better?

M

Well I dunno whats going on in this thread... but hey I fixed the problem, turns out the program was spitting out an error due to a bug wasn't actually having to do with the headers (turns out I had them already ), thanks a bunch though!

Gbonvehi, thanks for the links on previous discussions about kernel headers!
Really illuminating!