On Wed, 2005-11-30 at 09:04 +0800, Edward Dekkers wrote: > Below a log of vmware building the vmnet module and failing. This has > worked up until my latest update. Don't bother with the URL links, as > I've tried them and one is a page not found the other has no > troubleshooting. Does one of the programmers on this list know what this > is? The newsgroup link from the page seems to be broken also. > > --- > > Building the vmnet module. > > Using 2.6.x kernel build system. > make: Entering directory `/tmp/vmware-config0/vmnet-only' > make -C /lib/modules/2.6.14-1.1637_FC4smp/build/include/.. SUBDIRS=$PWD > SRCROOT=$PWD/. modules > make[1]: Entering directory `/usr/src/kernels/2.6.14-1.1637_FC4-smp-i686' > CC [M] /tmp/vmware-config0/vmnet-only/driver.o > In file included from /tmp/vmware-config0/vmnet-only/vnet.h:14, > from /tmp/vmware-config0/vmnet-only/vnetInt.h:10, > from /tmp/vmware-config0/vmnet-only/driver.c:40: > /tmp/vmware-config0/vmnet-only/vm_atomic.h:54:5: warning: "_MSC_VER" is > not defined > In file included from /tmp/vmware-config0/vmnet-only/vm_oui.h:13, > from /tmp/vmware-config0/vmnet-only/vnetInt.h:11, > from /tmp/vmware-config0/vmnet-only/driver.c:40: > /tmp/vmware-config0/vmnet-only/vm_basic_asm.h:48:5: warning: "_MSC_VER" > is not defined > /tmp/vmware-config0/vmnet-only/driver.c: In function ˜VNetProcessOwnsPort: > /tmp/vmware-config0/vmnet-only/driver.c:1698: error: struct files_struct > has no member named max_fds > make[2]: *** [/tmp/vmware-config0/vmnet-only/driver.o] Error 1 > make[1]: *** [_module_/tmp/vmware-config0/vmnet-only] Error 2 > make[1]: Leaving directory `/usr/src/kernels/2.6.14-1.1637_FC4-smp-i686' > make: *** [vmnet.ko] Error 2 > make: Leaving directory `/tmp/vmware-config0/vmnet-only' > Unable to build the vmnet module. > > For more information on how to troubleshoot module-related problems, please > visit our Web site at > "http://www.vmware.com/download/modules/modules.html"; and > "http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html";. > > Execution aborted. > OK, I'll ask the obvious questions... What version of VMWare? I had no problem building VMWare Workstation 5.0 on both that kernel 1637 and the newer 1644. So next obvious check, are you using the latest vmware-any-any-update96? Appears to be needed particularly if you are using VMWare 4.5.2.... If using the released today 5.5, I have no idea yet as I haven't had a chance to build those yet. The only difference in my environment that I can see is that I am not smp - using the UP kernel... Other thought as to a difference. I noticed a gcc update announcement today that I have yet to get so perhaps that is different - I am still running: gcc-4.0.1-4.fc4.... --Rob
