VMware Communities
sumanc
Contributor
Contributor
Jump to solution

Compilation error in Fedora Core 5 after updating kernel

On running vmware-config.pl I am getting the following error message at the end of the compilation (before it is aborted) ....

Similar error is found while installing vmware server and player (free versions).

This problem has started since I have updated my kernel-smp to last few versions. Latest version is 2.6.20-1.2300.fc5smp. I have appropriate devel package installed.

Any help/suggestion will be highly appreciated.

==========================================================================

Building for VMware Player 1.0.x or VMware Workstation 5.5.x.

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config6/vmmon-only'

make -C /lib/modules/2.6.20-1.2300.fc5smp/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.20-1.2300.fc5-smp-i686'

CC /tmp/vmware-config6/vmmon-only/linux/driver.o

In file included from /tmp/vmware-config6/vmmon-only/linux/driver.c:85:

/tmp/vmware-config6/vmmon-only/./include/compat_kernel.h:21: error: expected declaration specifiers or ‘...’ before ‘compat_exit’

/tmp/vmware-config6/vmmon-only/./include/compat_kernel.h:21: error: expected declaration specifiers or ‘...’ before ‘exit_code’

/tmp/vmware-config6/vmmon-only/./include/compat_kernel.h:21: warning: type defaults to ‘int’ in declaration of ‘_syscall1’

make[2]: *** Error 1

make[1]: *** \[_module_/tmp/vmware-config6/vmmon-only] Error 2

make[1]: Leaving directory `/usr/src/kernels/2.6.20-1.2300.fc5-smp-i686'

make: *** \[vmmon.ko] Error 2

make: Leaving directory `/tmp/vmware-config6/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.

Reply
0 Kudos
1 Solution

Accepted Solutions
KevinG
Immortal
Immortal
Jump to solution

You will most likely need to apply Petr's unofficial patch to be able to use that kernel version

Petr's unofficial vmware-any-any-update108.tar.gz can be found here

http://knihovny.cvut.cz/ftp/pub/vmware/

View solution in original post

Reply
0 Kudos
4 Replies
KevinG
Immortal
Immortal
Jump to solution

You will most likely need to apply Petr's unofficial patch to be able to use that kernel version

Petr's unofficial vmware-any-any-update108.tar.gz can be found here

http://knihovny.cvut.cz/ftp/pub/vmware/

Reply
0 Kudos
sumanc
Contributor
Contributor
Jump to solution

Thank you very much ! I should have used the latest version of the patch. I had a copy of vmware-any-any-update101.tar.gz with me and I kept trying with that. Thanks for the suggestion. Smiley Happy

Regards,

Suman.

Reply
0 Kudos
KevinG
Immortal
Immortal
Jump to solution

Hi Suman,

Glad to hear that it worked Smiley Happy

Reply
0 Kudos
vmwdavidr
Contributor
Contributor
Jump to solution

I had similar issue with kernel 2300, and the patch worked, but what did it do?

Reply
0 Kudos