Conflitto tra due versioni di gcc installate su Debian Lenny

[marietto2008]

Ciao pinguini,

sto provando ad installare le open vmware tools per debian lenny,ma avendo due versioni di gcc installate (la 4.1 e la 4.3),ho qualche problemuccio :

marietto2009:/home/marietto/Downloads/vmware-tools-distrib/bin# cd /usr/src

marietto2009:/usr/src# ls

gcc-4.1 linux-headers-2.6.26-1-common-vserver
gcc-4.3 linux-headers-2.6.26-1-common-xen
linux linux-headers-2.6.26-1-openvz-686
linux-headers-2.6.26-1-486 linux-headers-2.6.26-1-vserver-686
linux-headers-2.6.26-1-686 linux-headers-2.6.26-1-vserver-686-bigmem
linux-headers-2.6.26-1-686-bigmem linux-headers-2.6.26-1-xen-686
linux-headers-2.6.26-1-amd64 linux-kbuild-2.6.26
linux-headers-2.6.26-1-common linux-source-2.6.26.tar.bz2
linux-headers-2.6.26-1-common-openvz open-vm.tar.bz2

marietto2009:/usr/src# tar -jxf open-vm.tar.bz2

marietto2009:/usr/src# cd /usr/src/modules/open-vm

marietto2009:/usr/src/modules/open-vm# ls

debian Makefile modules

marietto2009:/usr/src/modules/open-vm# make

make -C modules/linux/pvscsi
Using 2.6.x kernel build system.
make[1]: Entering directory `/usr/src/modules/open-vm/modules/linux/pvscsi'
make -C /lib/modules/2.6.26-1-686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[2]: Entering directory `/usr/src/linux-headers-2.6.26-1-686'
/usr/src/modules/open-vm/modules/linux/pvscsi/Makefile:115: *** Inappropriate build environment: you wanted to use gcc version 4.3.2 while kernel attempts to use gcc version 4.1.3.
/usr/src/modules/open-vm/modules/linux/pvscsi/Makefile:117: *** For proper build you'll have to replace gcc-4.1 with symbolic link to cc. Stop.
make[2]: *** [_module_/usr/src/modules/open-vm/modules/linux/pvscsi] Error 2
make[2]: Leaving directory `/usr/src/linux-headers-2.6.26-1-686'
make[1]: *** [pvscsi.ko] Error 2
make[1]: Leaving directory `/usr/src/modules/open-vm/modules/linux/pvscsi'
make: *** [build] Error 2

come risolvo ?

grazie.

[marietto2008]

Risolto. Ora ho un altro tipo di problema :

marietto2009: cd /usr/bin
marietto2009: rm gcc
marietto2009: ln -s /usr/bin/gcc-4.1 /usr/bin/gcc
marietto2009: /usr/src/modules/open-vm# make

make -C modules/linux/pvscsi
Using 2.6.x kernel build system.
make[1]: Entering directory `/usr/src/modules/open-vm/modules/linux/pvscsi'
make -C /lib/modules/2.6.26-1-686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[2]: Entering directory `/usr/src/linux-headers-2.6.26-1-686'
Building modules, stage 2.
MODPOST 1 modules
make[2]: Leaving directory `/usr/src/linux-headers-2.6.26-1-686'
make -C $PWD SRCROOT=$PWD/. postbuild
make[2]: Entering directory `/usr/src/modules/open-vm/modules/linux/pvscsi'
make[2]: `postbuild' is up to date.
make[2]: Leaving directory `/usr/src/modules/open-vm/modules/linux/pvscsi'
cp -f pvscsi.ko ./../pvscsi.o
make[1]: Leaving directory `/usr/src/modules/open-vm/modules/linux/pvscsi'
make -C modules/linux/vmblock
Using standalone build system.
./autoconf/geninclude.c:19:28: error: linux/autoconf.h: No such file or directory
make[1]: Entering directory `/usr/src/modules/open-vm/modules/linux/vmblock'
.././autoconf/geninclude.c:19:28: error: linux/autoconf.h: No such file or directory
make[2]: Entering directory `/usr/src/modules/open-vm/modules/linux/vmblock/driver-'
Dependencies for .././linux/super.c
In file included from .././linux/super.c:26:
.././include/driver-config.h:42:5: error: #error "No Module support in this kernel. Please configure with CONFIG_MODULES"
make[2]: *** [super.d] Error 1
make[2]: Leaving directory `/usr/src/modules/open-vm/modules/linux/vmblock/driver-'
make[1]: *** [deps] Error 2
make[1]: Leaving directory `/usr/src/modules/open-vm/modules/linux/vmblock'
make: *** [build] Error 2

[marietto2008]

dopo aver fatto :

marietto2009: cd /usr/bin
marietto2009: rm gcc
marietto2009: ln -s /usr/bin/gcc-4.1 /usr/bin/gcc

ho provato a riconfigurare i tools di vmware :

marietto2009:/home/marietto/Downloads/vmware-tools-distrib/bin# ./vmware-config-tools.pl

Stopping VMware Tools services in the virtual machine:
Guest operating system daemon: done
Virtual Printing daemon: done
None of the pre-built vmmemctl modules for VMware Tools is suitable for your
running kernel. Do you want this program to try to build the vmmemctl module
for your system (you need to have a C compiler installed on your system)?
[yes]

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
kernel? [/lib/modules/2.6.26-1-686/build/include]

Extracting the sources of the vmmemctl module.

Building the vmmemctl module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmmemctl-only'
make -C /lib/modules/2.6.26-1-686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.26-1-686'
CC [M] /tmp/vmware-config0/vmmemctl-only/backdoorGcc32.o
CC [M] /tmp/vmware-config0/vmmemctl-only/os.o
CC [M] /tmp/vmware-config0/vmmemctl-only/vmballoon.o
LD [M] /tmp/vmware-config0/vmmemctl-only/vmmemctl.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config0/vmmemctl-only/vmmemctl.mod.o
LD [M] /tmp/vmware-config0/vmmemctl-only/vmmemctl.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.26-1-686'
cp -f vmmemctl.ko ./../vmmemctl.o
make: Leaving directory `/tmp/vmware-config0/vmmemctl-only'
The vmmemctl module loads perfectly into the running kernel.

None of the pre-built vmhgfs modules for VMware Tools is suitable for your
running kernel. Do you want this program to try to build the vmhgfs module for
your system (you need to have a C compiler installed on your system)? [yes]

Extracting the sources of the vmhgfs module.

Building the vmhgfs module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmhgfs-only'
make -C /lib/modules/2.6.26-1-686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.26-1-686'
CC [M] /tmp/vmware-config0/vmhgfs-only/backdoor.o
LD [M] /tmp/vmware-config0/vmhgfs-only/vmhgfs.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config0/vmhgfs-only/vmhgfs.mod.o
LD [M] /tmp/vmware-config0/vmhgfs-only/vmhgfs.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.26-1-686'
cp -f vmhgfs.ko ./../vmhgfs.o
make: Leaving directory `/tmp/vmware-config0/vmhgfs-only'
The vmhgfs module loads perfectly into the running kernel.

None of the pre-built vmxnet modules for VMware Tools is suitable for your
running kernel. Do you want this program to try to build the vmxnet module for
your system (you need to have a C compiler installed on your system)? [yes]

Extracting the sources of the vmxnet module.

Building the vmxnet module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmxnet-only'
make -C /lib/modules/2.6.26-1-686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.26-1-686'
CC [M] /tmp/vmware-config0/vmxnet-only/vmxnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config0/vmxnet-only/vmxnet.mod.o
LD [M] /tmp/vmware-config0/vmxnet-only/vmxnet.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.26-1-686'
cp -f vmxnet.ko ./../vmxnet.o
make: Leaving directory `/tmp/vmware-config0/vmxnet-only'
The vmxnet module loads perfectly into the running kernel.

update-initramfs: Generating /boot/initrd.img-2.6.26-1-686
None of the pre-built vmblock modules for VMware Tools is suitable for your
running kernel. Do you want this program to try to build the vmblock module
for your system (you need to have a C compiler installed on your system)?
[yes]

Extracting the sources of the vmblock module.

Building the vmblock module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmblock-only'
make -C /lib/modules/2.6.26-1-686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.26-1-686'
CC [M] /tmp/vmware-config0/vmblock-only/linux/block.o
LD [M] /tmp/vmware-config0/vmblock-only/vmblock.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config0/vmblock-only/vmblock.mod.o
LD [M] /tmp/vmware-config0/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.26-1-686'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/vmware-config0/vmblock-only'
The vmblock module loads perfectly into the running kernel.

[EXPERIMENTAL] The VMware FileSystem Sync Driver (vmsync) is a new feature that
creates backups of virtual machines. Please refer to the VMware Knowledge Base
for more details on this capability. Do you wish to enable this feature?
[no]

None of the pre-built vmci modules for VMware Tools is suitable for your
running kernel. Do you want this program to try to build the vmci module for
your system (you need to have a C compiler installed on your system)? [yes]

Extracting the sources of the vmci module.

Building the vmci module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmci-only'
make -C /lib/modules/2.6.26-1-686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.26-1-686'
CC [M] /tmp/vmware-config0/vmci-only/kernelStubsLinux.o
LD [M] /tmp/vmware-config0/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config0/vmci-only/vmci.mod.o
LD [M] /tmp/vmware-config0/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.26-1-686'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-config0/vmci-only'
The vmci module loads perfectly into the running kernel.

None of the pre-built vsock modules for VMware Tools is suitable for your
running kernel. Do you want this program to try to build the vsock module for
your system (you need to have a C compiler installed on your system)? [yes]

Extracting the sources of the vsock module.

Building the vsock module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vsock-only'
make -C /lib/modules/2.6.26-1-686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.26-1-686'
CC [M] /tmp/vmware-config0/vsock-only/linux/af_vsock.o
CC [M] /tmp/vmware-config0/vsock-only/linux/driverLog.o
CC [M] /tmp/vmware-config0/vsock-only/linux/util.o
CC [M] /tmp/vmware-config0/vsock-only/linux/vsockAddr.o
LD [M] /tmp/vmware-config0/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
WARNING: "VMCIDatagram_CreateHnd" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIDatagram_DestroyHnd" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIEvent_Subscribe" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCI_DeviceGet" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIMemcpyFromQueueV" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIQueuePair_Detach" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCI_GetContextID" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIDatagram_Send" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIQueuePair_Alloc" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIEvent_Unsubscribe" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIMemcpyToQueueV" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
CC /tmp/vmware-config0/vsock-only/vsock.mod.o
LD [M] /tmp/vmware-config0/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.26-1-686'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/vmware-config0/vsock-only'
Unable to make a vsock module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config0/vsock.o': -1 Unknown symbol in module
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.

The VM communication interface socket family is used in conjunction with the VM
communication interface to provide a new communication path among guests and
host. The rest of this software provided by VMware Tools is designed to work
independently of this feature. If you wish to have the VSOCK feature you can
install the driver by running vmware-config-tools.pl again after making sure
that gcc, binutils, make and the kernel sources for your running kernel are
installed on your machine. These packages are available on your distribution's
installation CD.
[ Press the Enter key to continue.]



Detected X.org version 7.3.2.



Do you want to change the starting screen display size? (yes/no) [no]


X.Org X Server 1.4.2
Release Date: 11 June 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux Debian (xorg-server 2:1.4.2-10)
Current Operating System: Linux marietto2009 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686
Build Date: 09 January 2009 02:57:16AM

Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/vmware-config1/XF86ConfigLog.6717", Time: Wed Feb 18 17:04:17 2009
(++) Using config file: "/tmp/vmware-config1/XF86Config.6717"
(II) Module "ramdac" already built-in
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server

X is running fine with the new config file.

FreeFontPath: FPE "/usr/share/fonts/X11/misc" refcount is 2, should be 1; fixing.
Checking acpi hot plug done
Starting VMware Tools services in the virtual machine:
Switching to guest configuration: done
Guest filesystem driver: done
Mounting HGFS shares: failed
Guest memory manager: done
Guest vmxnet fast network device: done
VM communication interface: done
Blocking file system: done
VMware User Agent (vmware-user): done
Guest operating system daemon: done
Virtual Printing daemon: done

The configuration of VMware Tools 6.5.0 build-118166 for Linux for this running
kernel completed successfully.

You must restart your X session before any mouse or graphics changes take
effect.

You can now run VMware Tools by invoking the following command:
"/usr/bin/vmware-toolbox" during an X server session.

To enable advanced X features (e.g., guest resolution fit, drag and drop, and
file and text copy/paste), you will need to do one (or more) of the following:
1. Manually start /usr/bin/vmware-user
2. Log out and log back into your desktop session; and,
3. Restart your X session.

To use the vmxnet driver, restart networking using the following commands:
/etc/init.d/networking stop
rmmod pcnet32
rmmod vmxnet
modprobe vmxnet
/etc/init.d/networking start

If the virtual printer feature is enabled, you will need to restart the CUPS
service to make use of this feature.

Enjoy,

--the VMware team

ma il mouse continua a non uscire automaticamente dalla macchina virtuale.

[detroit]

mi sa che ti sei complicato la vita in modo assurdo perchè almeno a quello che ho fatto io, i vmware tools te li installa quasi automaticamente nella macchina virtuale quando quest'ultima è attiva.

[marietto2008]

anche a me faceva cosi' con la ubuntu,ma NON e' successo con la debian lenny.

[detroit]

io ho installato i tool sono un wincozza virtualizzato,sinceramente su un linux virtuale non sono così necessari,voglio dire,i driver ecc li carica tranquillamente senza bisogno dei tool,poi se ti serve per altri motivi è diverso

[marietto2008]

E' una vera rottura di scatole dover premere ogni volta CTRL + ALT per tornare a Windows mentre stai lavorando con Linux dentro la macchina virtuale. Far funzionare (forse questo modulo ?) e' importantissimo.

CC /tmp/vmware-config0/vsock-only/vsock.mod.o
LD [M] /tmp/vmware-config0/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.26-1-686'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/vmware-config0/vsock-only'
Unable to make a vsock module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config0/vsock.o': -1 Unknown symbol in module
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.