rozpakowalem, zainstalowalem i konfiguruje zgodnie z opisem kaki http://kaka.ovh.org/howto/vmware/
Jednek w pewnym momencie kofigruacja zwraca mi cos takiego:
Your kernel was built with "gcc" version "4.1.3", while you are trying to use
"/usr/bin/gcc" version "4.2.3". This configuration is not recommended and
VMware Server may crash if you'll continue. Please try to use exactly same
compiler as one used for building your kernel. Do you want to go with compiler
"/usr/bin/gcc" version "4.2.3" anyway? [no] yes
What is the location of the directory of C header files that match your running
kernel? [/lib/modules/2.6.22-2-amd64/build/include]
Extracting the sources of the vmmon module.
Building the vmmon module.
Building for VMware Server 1.0.0.
Using 2.6.x kernel build system.
make: Wejście do katalogu `/tmp/vmware-config0/vmmon-only'
make -C /lib/modules/2.6.22-2-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Wejście do katalogu `/usr/src/linux-headers-2.6.22-2-amd64'
/tmp/vmware-config0/vmmon-only/Makefile:127: *** Inappropriate build environment: you wanted to use gcc version 4.2.3 while kernel attempts to use gcc version 4.1.3.
/tmp/vmware-config0/vmmon-only/Makefile:129: *** For proper build you'll have to replace gcc-4.1 with symbolic link to /usr/bin/gcc. Stop.
make[1]: *** [_module_/tmp/vmware-config0/vmmon-only] Błąd 2
make[1]: Opuszczenie katalogu `/usr/src/linux-headers-2.6.22-2-amd64'
make: *** [vmmon.ko] Błąd 2
make: Opuszczenie katalogu `/tmp/vmware-config0/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.
lanceroot:/vmware/vmware-any-any-update114#
Domyslam sie, ze to przez to ze najpierw mialem etcha ktory uzywal gcc 4.1.3 ale po przejsciu na lenny mam teraz 4.2.3, jak jednak moge to rozwiazac?
Moj system:
Linux lanceroot 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 UTC 2007 x86_64 GNU/Linux
//edit
poprawiłem tytuł tematu - nie dodajemy [solved], ale [+] na początku
mlyczek
Beynar pisze:Domyslam sie, ze to przez to ze najpierw mialem etcha ktory uzywal gcc 4.1.3 ale po przejsciu na lenny mam teraz 4.2.3, jak jednak moge to rozwiazac?
Bardzo prosto.. system nawet podał ci rozwiązanie
Beynar pisze:*** For proper build you'll have to replace gcc-4.1 with symbolic link to /usr/bin/gcc. Stop.
Po prostu musisz zastąpić symlinka /usr/bin/gcc (teraz pokazuje na /usr/bin/gcc-4.2) tak aby wskazywał na starszą wersję (/usr/bin/gcc-4.1)
Building for VMware Server 1.0.0.
Using 2.6.x kernel build system.
make: Wejście do katalogu `/tmp/vmware-config0/vmmon-only'
make -C /lib/modules/2.6.22-2-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Wejście do katalogu `/usr/src/linux-headers-2.6.22-2-amd64'
CC [M] /tmp/vmware-config0/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-config0/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-config0/vmmon-only/common/comport.o
CC [M] /tmp/vmware-config0/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-config0/vmmon-only/common/hash.o
CC [M] /tmp/vmware-config0/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-config0/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-config0/vmmon-only/common/task.o
gcc-4.1: error trying to exec 'cc1plus': execvp: Nie ma takiego pliku ani katalogu
make[2]: *** [/tmp/vmware-config0/vmmon-only/common/task.o] Błąd 1
make[1]: *** [_module_/tmp/vmware-config0/vmmon-only] Błąd 2
make[1]: Opuszczenie katalogu `/usr/src/linux-headers-2.6.22-2-amd64'
make: *** [vmmon.ko] Błąd 2
make: Opuszczenie katalogu `/tmp/vmware-config0/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.
Dowiazanie jest zrobione napewno dobrze wiec czemu ma taki problem jeszcze?
Mam zainstalowane
ale na wszelki wypadek go usunalem i zainstalowalem jeszcze raz
Jako, ze usunal tez headersy to i je zainstalowalem ponownie
Niestety wciaz ten sam blad jak powyzej