Linus's include file strategy redux
Quoted 8 lines · Dana Lacoste
Quoted 4 lines
Maybe you did not notice, but for months we have
/lib/modules/uname -r/build/include, which points to kernel headers, and which should be used for compiling out-of-tree kernel modules (i.e. latest vmware uses this).What about the case where I'm compiling for a kernel that I'm not running (yet)?
Quoted 7 lines
lm_sensors, for example, told me yesterday when I compiled it that I was running 2.2.17, but it was compiling for 2.2.18 (because I moved the symlink in/usr/src/linuxto point to/usr/src/linux-2.2.18)I personally wouldn't like some programs to do a
uname -rcheck because it won't do what I want it to :)
You can list /lib/modules/*/build/include and present user with list of possible kernels. You should check whether version.h contents matches directory name, but it is just an additional check against users which compile all kernels in /usr/src/linux.
For lmsensors, you just have to compile kernel first, and lm_sensors after that. But intervening reboot is not required as long as configure does not use 'uname -r' (ok, I'm filling vmware bugreport just now).
Best regards,
Petr Vandrovec [email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/