On Sunday 23 May 2004 22.27, Vince Littler wrote:
Having read the reference, I agree with the argument. But section 10.2 of the Administrators Guide for 9.1 argues that the -/linux directory should be a symlink to the current kernel and says YaST should do this for you.
I see that. That only proves that even suse can be wrong
I am a tad confused by this. If I do my own kernel, in the -/linuxMyWay directory, I actually use headers from the -/linux directory?
No, not at all. When you compile a kernel in directory /foo, you use include files from /foo/include
This seems fine for linking library functions, but for linking concurrently compiled kernel modules, this seems wrong.
Are we actually talking here about the difference between #include <SomeLibraryHeader> and #include "SomeConcurrentlyCompiledModuleHeader"?
The kernel doesn't use 'normal' include files. It compiles with (among other things) the gcc flag -nostdinc. Everything it uses comes from the kernel directory
I am not so far into kernel hacking yet, but my Long Delay before Kernel Boots problem is forcing the matter, and this discussion seems to be providing some possible answers as to why I can't compile kernel.org kernels before 2.6.4 on 9.1.
I haven't tried. 9.1 uses some kind of version of gcc 3.3 with several features in it that have been back ported from 3.4. gcc 3.4 changed a few things that broke several apps, for example mplayer had to be updated to compile with 3.4, so it is possible that earlier kernels just aren't compatible with gcc 3.4