From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031114 Description of problem: When building VMware 4.0.1 modules for 2.6.1-1.138 kernel (http://kerneltrap.org/node/view/1804) runme.pl shows error (see additional info). Version-Release number of selected component (if applicable): kernel-2.6.1-1.138 How reproducible: Always Steps to Reproduce: 1. Install kernel, kernel-source 2.6.1-1.138 from arjanv. 2. Follow instructions on http://kerneltrap.org/node/view/1804 Actual Results: Error above. Expected Results: Everything should compile as in 2.6.0. Additional info: ==== What is the location of the directory of C header files that match your running kernel? [/usr/src/linux/include] /usr/src/linux-2.6.1-1.138/include The path "/usr/src/linux-2.6.1-1.138/include" is a kernel header file directory,but it does not contain the file "linux/version.h" as expected. This can happenif the kernel has never been built, or if you have invoked the "make mrproper" command in your kernel directory. In any case, you may want to rebuild your kernel. ==== Previous kernel-2.6.0 was OK.
kernel? [/usr/src/linux/include] /usr/src/linux-2.6.1-1.138/include You lied to vmware there. The location of the header files is and has been for the past 3 years: /lib/modules/<version/build/include kernel-source is (no longer with 2.6) for building modules against.
Running runme.pl from vmware-any-any patch (see url above) ==== What is the location of the directory of C header files that match your running kernel? [/usr/src/linux/include] /lib/modules/2.6.1-1.138/build/include The kernel defined by this directory of header files does not have the same address space size as your running kernel. What is the location of the directory of C header files that match your running kernel? [/usr/src/linux/include] ^C [root@localhost vmware-any-any-update43]# uname -a Linux localhost.localdomain 2.6.1-1.138 #1 Sat Jan 17 15:14:40 EST 2004 i686 athlon i386 GNU/Linux ==== And in 2.6.0 it all worked without asking path, the path was autodetected and I just pressed Enter. Something has changed in 2.6.1 that has broken stuff.
sounds like a broken check by vmware to me... assinging to tbarr; he's the vmware liason
NOTE: THIS IS COMPLETELY UNSUPPORTED ADVICE, USE AT YOUR OWN RISK. http://ftp.cvut.cz/vmware/ I personally use the unofficial vmware-any-any* toolkit from here with VMWare WS 4.51 on FC2 development. The latest version of vmware-any-any* has always managed to get the latest FC2 2.6 kernel to work for me. Your mileage may vary, and I heard something about VMWare 4.0.1 not working, but this I am not sure.