Désolé, je n'avais pas vu pour gcc++.
Je vais un peu plus loin, mintenant:
/tmp/vmware-config8/vmmon-only/common/task_compat.h:1713: attention : 'sysenterState.SysenterStateV45::rip' may be used uninitialized in this function
CC [M] /tmp/vmware-config8/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-config8/vmmon-only/vmcore/compat.o
CC [M] /tmp/vmware-config8/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/vmware-config8/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config8/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-config8/vmmon-only/vmmon.ko
make[1]: quittant le répertoire « /usr/src/kernels/2.6.20-1.2948.fc6-i686 »
cp -f vmmon.ko ./../vmmon.o
make: quittant le répertoire « /tmp/vmware-config8/vmmon-only »
Unable to make a vmmon module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config8/vmmon.o': -1 Invalid module format
There is probably a slight difference in the kernel configuration between the
set of C header files you specified and your running kernel. You may want to
rebuild a kernel based on that directory, or specify another directory.
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.
[root@localhost vmware-any-any-update110]#
J'ai l'impression que c'est un probleme entre le kernel et les C headers.
J'ai essayé de faire la meme manip pour les headers que pour le kernel, mais on dirait qu'il n'y a pas de header i686.
