Has anyone else seen this? I merrily upgraded from 5.5.4 to 5.5.5 (VMwareWorkstation-5.5.5-56455) - and when trying to run the config script, I get this? Prior to everything seems to occur just peachy. Installed from the RPM,all ran w/o errors.
I'm running Fedora Core 7, with a custom compiled kernel, 2.6.23-1.
uname -a
Linux wanderer 2.6.23.1 #1 SMP Mon Oct 15 14:37:48 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
I get the same error if I "roll back" to 5.5.4.
Using compiler "/usr/bin/gcc". Use environment variable CC to override.
What is the location of the directory of C header files that match your running
Extracting the sources of the vmmon module.
Building the vmmon module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config8/vmmon-only'
make -C /lib/modules/2.6.23.1/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/linux-2.6.23.1'
CC /tmp/vmware-config8/vmmon-only/linux/driver.o
In file included from /tmp/vmware-config8/vmmon-only/linux/driver.c:80:
/tmp/vmware-config8/vmmon-only/./include/compat_kernel.h:21: error: expected declaration specifiers or ‘...’ before ‘compat_exit’
/tmp/vmware-config8/vmmon-only/./include/compat_kernel.h:21: error: expected declaration specifiers or ‘...’ before ‘exit_code’
/tmp/vmware-config8/vmmon-only/./include/compat_kernel.h:21: warning: type defaults to ‘int’ in declaration of ‘_syscall1’
/tmp/vmware-config8/vmmon-only/linux/driver.c: In function ‘LinuxDriver_Ioctl’:
/tmp/vmware-config8/vmmon-only/linux/driver.c:1661: error: ‘struct mm_struct’ has no member named ‘dumpable’
make[1]: Leaving directory `/usr/src/kernels/linux-2.6.23.1'
make: *** http://vmmon.ko Error 2
make: Leaving directory `/tmp/vmware-config8/vmmon-only'
Unable to build the vmmon 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.
--Geff
I think I answered it - cleaned out all vestiges of vmware, installed WS 5.5.5 and applied vmware-any-any-update113.
and, now it works again?
--Geff