Sjoerd Hiemstra wrote:
On Fri, 20 Mar 2009 21:53 +0100, Sven Joachim wrote:
On 2009-03-20 21:43 +0100, Sjoerd Hiemstra wrote:
The older gcc 4.1.3 is not available in debian.snapshot.net .
But it is available from the Debian mirrors in the gcc-4.1 package:
,----
| % LANG=C gcc-4.1 --version
| gcc-4.1 (GCC) 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)
...
Please install gcc-4.1 and retry.
Ahh - but I do have gcc-4.1 installed.
If you still have problems, you may need to set "CC=gcc-4.1" for the
vmware modules build.
Did that and it solved the problem. Thanks (again! ;-) ) a lot!
For those who may not know why this worked...
~$ ls -l /usr/bin/gcc
lrwxrwxrwx 1 root root 7 2009-02-18 01:03 /usr/bin/gcc -> gcc-4.3
~$ ls -l /usr/bin/gcc*
lrwxrwxrwx 1 root root 7 2009-02-18 01:03 /usr/bin/gcc -> gcc-4.3
-rwxr-xr-x 1 root root 90712 2008-10-25 02:38 /usr/bin/gcc-3.4
-rwxr-xr-x 1 root root 226568 2009-01-18 10:44 /usr/bin/gcc-4.1
-rwxr-xr-x 1 root root 239000 2009-01-02 03:16 /usr/bin/gcc-4.3
Lenny AMD64
As I understand it, specifying CC=/usr/bin/gcc-4.1 forces the build
environment to use the chosen version of GCC, ignoring the default of
/usr/bin/gcc.
This got me as well when I was experimenting with VMWare Server/Client
Tools and Lenny, still does on occasion. *grin*
One other thing, the client tools for VM 2.0... One of the more
important modules won't compile with the kernel shipped with Lenny
(vsock = VM communication interface socket). Search around (I don't
recall the exact URL where I found it, I think it was on the Ubuntu
forums) for vmware-config.pl.patch and vmware-config-tools.pl.patch, you
will need them to get that module compiled. The VM will run without it,
but it won't run as well.
And if you find a better way to access the server under Linux that that
$%#$^%! web UI crap, please let me know!!!
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
