Messages in this thread | | | Date | Fri, 15 Dec 2000 10:16:02 -0600 | From | Eli Carter <> |
| |
Dana Lacoste wrote: > > > 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)? > > 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/linux to point to > /usr/src/linux-2.2.18) > > I personally wouldn't like some programs to do a `uname -r` > check because it won't do what I want it to :)
And don't forget cross-compiling... (No, I don't know how all that is supposed to work. *sigh*)
^C-ya,
Eli --------------------. "To the systems programmer, users and applications Eli Carter | serve only to provide a test load." eli.carter@inet.com `---------------------------------- (random fortune) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
| |