Thanks, putting CC into env did work, now I know where the 3.4 exe is! However I have another problem now with VMware - the script fails again with the kernel headers (which I have installed).
I've taken a look at the k-headers tree and symlinks, and I think I know what's wrong, but wanted a 2nd opinion..... stat'd /usr/src/linux (shows symlink as expected) File: `linux' -> `kernel-headers-2.6.8-11-amd64-k8-smp' stat'd /usr/src/linux/include/asm (shows symlink to non-smp, non-k8 kernel tree which is not present) File: `asm' -> `../../kernel-headers-2.6.8-11/include/asm' The non-present vanilla kernel tree which is being symlinked to is what the vmware install script can't read. Should I have both the k8-smp kernel headers and the vanilla headers installed, or are the current kernel-headers faulty?? On Thu, 2005-06-09 at 05:57 -0500, Mark Nipper wrote: > On 09 Jun 2005, Rupert Heesom wrote: > > I was running the install script for vmware5, it complained that my > > kernel was compiled using gcc 3.4 and my current gcc is version 3.3.5. > > You might try specifying CC=gcc-3.4 in your environment > or on the same line as your vmware configure command: > --- > CC=gcc-3.4 /usr/local/vmware/bin/vmware-config.pl > > I would imagine either one will work. > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]