On 8/23/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
The directory of kernel headers (version 2.6.11) does not match your running kernel (version 2.6.17.3). Even if the module were to compile successfully, it would not load into the running kernel. What is the location of the directory of C header files that match your running kernel? [/usr/src/linux/include]
Unlike userspace tools that need kernel headers, building an external kernel module needs the source from the kernel you're running. So, if you build glibc, you want it to use the sanitized kernel headers in /usr/include. But, if you're building a module to run in your current kernel, it needs the raw headers that correspond to that kernel. So, if you still have the source tree from when you built linux-2.6.17.3, point the vmware script there. Otherwise, rebuild the kernel tree. In that case, you might as well grab the most current kernel (2.6.17.10). Build the kernel and reboot into it (this will satisfy the vmware script that thinks you would only want to build against the running kernel). Don't delete the linux kernel tree. Rerun the vmware script, and point it to where you did the linux build. Possibly /usr/src/linux-2.6.17.10/include. If you haven't moved the kernel tree, /lib/modules/2.6.17.10/build is a symlink to this location. Another option is to build the external vmware module during the linux build. But that's more complex and would require a greater understanding of how the vmware source is organized. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
