Re: gcc version issue trying to install vmware5
Goswin von Brederlow wrote:
> The vmware-config.pl script does care about the environment:
>
> sub get_cc {
> $gHelper{'gcc'} = '';
> if (defined($ENV{'CC'}) && (not ($ENV{'CC'} eq ''))) {
> $gHelper{'gcc'} = internal_which($ENV{'CC'});
>
> If CC is set it will be used. It even says:
>
> print wrap('Using compiler "' . $gHelper{'gcc'}
> . '". Use environment variable CC to override.' . "\n\n", 0);
Well, it cares about it, but setting CC still doesn't work. I removed the
symlink I hand-libbed onto the box for gcc-3.4 and then did "apt-get install
--reinstall gcc" to make sure that things are setup the Debian way, exported
CC, and tried to compile:
$ export CC=gcc-3.4
$ sudo vmware-config.pl
Making sure services for VMware Workstation are stopped.
Stopping VMware services:
Trying to find a suitable vmmon module for your running kernel.
None of the pre-built vmmon modules for VMware Workstation is suitable for
your running kernel. Do you want this program to try to build the vmmon
module for your system (you need to have a C compiler installed on your
system)? [yes]
Using compiler "/usr/bin/gcc-3.4". 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.11.11/build/include]
Extracting the sources of the vmmon module.
Building the vmmon module.
Using 2.6.x kernel build system.
...
make[1]: Entering directory `/usr/src/linux-2.6.11.11'
/tmp/vmware-config0/vmmon-only/Makefile:87: *** Inappropriate build
environment you wanted to use gcc version 3.4.5 while kernel attempts to use
gcc version 3.3.6.
/tmp/vmware-config0/vmmon-only/Makefile:89: *** For proper build you'll have
to replace gcc with symbolic link to /usr/bin/gcc-3.4. Stop.
make[1]: *** [_module_/tmp/vmware-config0/vmmon-only] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.11.11'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-config0/vmmon-only'
Unable to build the vmmon module.
Just to be damn sure that the kernel build system wouldn't "remember" that I
had previously used gcc and was now trying to use gcc-3.4, I rebuilt my
kernel using:
make CC=gcc-3.4 HOSTCC=gcc-3.4
And the results are the same, (as someone previously on this thread
indicated they would be).
vmware-config.pl overwrites the PATH (line 7746 in the current vmware5), so
dropping a symlink for gcc into /usr/local/bin/ doesn't help (without
modifying the script). Exporting CC to be /usr/local/bin/gcc also fails
with the same errors listed above.
However, with the symlink in place and /usr/local/bin/ in my PATH, I was
able to use module-assistant to build the nvidia kernel module, and the
build system for the ivtv modules also works, so I imagine other stuff does
as well. So, in summary, the gcc symlink in /usr/local/bin/ works pretty
well (at least for me, YMMV), and vmware-config.pl is not going to work
without either placing something in /usr/bin (e.g. /usr/bin/vmwarecc ->
/usr/bin/gcc-3.4) or modifying the script to not muck with the PATH.
Thanks,
tony
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gcc version issue trying to install vmware5
Ernest jw ter Kuile <[EMAIL PROTECTED]> writes:
> On Monday 13 June 2005 09:25, Goswin von Brederlow wrote:
>>
>> Changing the link breaks your debian system.
>
> this is not true.
>
> I've had this link pointing to gcc-3.4 since quite a while. Every time gcc
> must be reinstalled (which is not often) i simply replace the link.
>
> everything works, nothing is broken.
>
> Beside, wat could this break ?
>
>> If you must then create a /usr/local/bin/gcc. Debian won't overwrite that.
>
> in what way would this be different ? if changing the link breaks Debian, why
> would this not ? it has the same effect (hint : no packages use /usr/bin/gcc,
> and they shouldn't) .
System accounts are unlikely to have /usr/local/ in their path before
/usr/bin:
[EMAIL PROTECTED]:~% echo $PATH
/home/mrvn/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games
[EMAIL PROTECTED]:~% su -
Password:
[EMAIL PROTECTED]:~# echo $PATH
/root/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/bin/X11:/usr/local/sbin:/usr/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games
See the difference. My user would get /usr/local/bin/gcc while root
still gets /usr/bin/gcc.
>>> "gcc" package insists that gcc -> gcc-3.3.
>>
>>And rightly so.
>
> Wrong. It should guard the (current) default, and not prevent people from
> changing it.
>
> Beside, when setting this default, it should use the "alternative" method
> Debian has perfected, and which is used by most other packages specifically
> for this purpose.
No. gcc specificaly does not use the alternative system because
different gcc versions are incompatible. You can't just switch between
them. They are not alternatives to produce object files but each one
has its own kind of object files.
Even gcc 3.3 and 3.4 on amd64 have slight differences in their abi
that can cause programs to break if you mix. g++ 3.3 and 3.4 are so
different nearly everything fails when mixing the two.
The exact same reason kernel modules want the same gcc version is the
reason gcc can't be an alternative.
> Even so, I do agree that on upgrade, package gcc should want to restore the
> current gcc to the default version Debian is using. It most definitly should
> _ask_ before doing so.
Since it is not an alternative and not configurable at all it (dpkg)
is right to not ask. dpkg just unpacks the link contained in the deb.
>>> I'd much prefer to set an environment variable as well, but it's going to
>>> require a deeper understanding of the module compilation subsystem of the
>>> 2.6 kernel. Both CC and HOSTCC seem to be ignored.
>>
>> Did you export it?
>
> that doesn't help.
>
> The Makefile that comes with the kernel.org source clobbers any existing CC
> and HOSTCC.
> I don't think Debian has changed that behavior.
The vmware-config.pl script does care about the environment:
sub get_cc {
$gHelper{'gcc'} = '';
if (defined($ENV{'CC'}) && (not ($ENV{'CC'} eq ''))) {
$gHelper{'gcc'} = internal_which($ENV{'CC'});
If CC is set it will be used. It even says:
print wrap('Using compiler "' . $gHelper{'gcc'}
. '". Use environment variable CC to override.' . "\n\n", 0);
>>> I think that the kernel doesn't and the nvidia modules
>>> _need_ the 3.4 version.
>
>>The kernel doesn't use gcc. It uses gcc-3.4 because that is the
>>only one that can build 64bit kernels on i386.
>
> 1) the kernel build system as provided by kernel.org uses gcc. Not a specific
> gcc, just any available gcc (nearly, it does check for really old gccs).
> 2) using gcc-3.3 to build a amd64 kernel is not efficient, but the resulting
> kernel will boot without any trouble, even if a bit slow. It is not broken in
> anyway (try it!).
I actualy use gcc-3.3 for my kernel because I was to lazy / forgot to
use a different one. Never had a problem with it.
>>Any kernel modules you build also have to use gcc-3.4 and not gcc.
>
> All kernel modules should be compiled using the exact same gcc as the
> one used to compile the kernel. if you use gcc-3.3 for the kernel, modules
> should use that too.
> If one module (nvidia) requires gcc version 3.4 or higher, then the kernel
> and
> all other modules must be recompiled to use that same gcc.
>
> Just for the record : changing the kernel Makefile (as Debian apparently did)
> to force a specific gcc is IMNSHO dumb.
The kernel Makefile isn't changed to force a gcc version afaik. The
Debian system ships a gcc link (or script on some archs) that garanties
calling gcc will use a gcc version compatible with the existing
binaries and libs.
>>But that doesn't mean gcc-3.4 should be THE gcc.
>>
>
> Goswin, nobody claimed that. They just want easy choice.
>
> what about changing package gcc to check available versions of gcc, and
> asking
> the user the one they want to ?
Can't work. The C/C++ ABI to use is not a users/admins choice but must
be made by debian prior to compiling all packages.
> Don't worry, I'm sti
Re: gcc version issue trying to install vmware5
Lennart Sorensen wrote: > On Thu, Jun 16, 2005 at 01:10:08PM +0200, Ernest jw ter Kuile wrote: > >>that doesn't help. >> >>The Makefile that comes with the kernel.org source clobbers any existing CC >>and HOSTCC. >>I don't think Debian has changed that behavior. > > > The kernel makefile does the same as all other makefiles and works fine. > It does NOT use the env, since make generally doesn't. it does work > this way though: > > make HOSTCC=gcc-3.4 CC=gcc-3.4 menuconfig > > Add V=1 if you want to see what commands it is running. > > That is the _correct_ way to pass parameters to make and also how > make-kpkg does it (through the variable MAKEFLAGS it uses for exactly that > purpose) Thanks to everyone who has responded to this thread. I like Goswin's idea about putting the symlink in /usr/local/bin/, since this rules out the possibility of a later gcc package install resulting in something unintended. Anyway, I'm going to undo the symlink I have in place and see if the issue can't be solved by passing the correct variables when invoking make, and then I'll report back to the list. tony -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gcc version issue trying to install vmware5
On Thu, Jun 16, 2005 at 01:10:08PM +0200, Ernest jw ter Kuile wrote: > that doesn't help. > > The Makefile that comes with the kernel.org source clobbers any existing CC > and HOSTCC. > I don't think Debian has changed that behavior. The kernel makefile does the same as all other makefiles and works fine. It does NOT use the env, since make generally doesn't. it does work this way though: make HOSTCC=gcc-3.4 CC=gcc-3.4 menuconfig Add V=1 if you want to see what commands it is running. That is the _correct_ way to pass parameters to make and also how make-kpkg does it (through the variable MAKEFLAGS it uses for exactly that purpose) Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gcc version issue trying to install vmware5
On Monday 13 June 2005 09:25, Goswin von Brederlow wrote: > > Changing the link breaks your debian system. this is not true. I've had this link pointing to gcc-3.4 since quite a while. Every time gcc must be reinstalled (which is not often) i simply replace the link. everything works, nothing is broken. Beside, wat could this break ? > If you must then create a /usr/local/bin/gcc. Debian won't overwrite that. in what way would this be different ? if changing the link breaks Debian, why would this not ? it has the same effect (hint : no packages use /usr/bin/gcc, and they shouldn't) . >> "gcc" package insists that gcc -> gcc-3.3. > >And rightly so. Wrong. It should guard the (current) default, and not prevent people from changing it. Beside, when setting this default, it should use the "alternative" method Debian has perfected, and which is used by most other packages specifically for this purpose. Even so, I do agree that on upgrade, package gcc should want to restore the current gcc to the default version Debian is using. It most definitly should _ask_ before doing so. >> I'd much prefer to set an environment variable as well, but it's going to >> require a deeper understanding of the module compilation subsystem of the >> 2.6 kernel. Both CC and HOSTCC seem to be ignored. > > Did you export it? that doesn't help. The Makefile that comes with the kernel.org source clobbers any existing CC and HOSTCC. I don't think Debian has changed that behavior. >> I think that the kernel doesn't and the nvidia modules >> _need_ the 3.4 version. >The kernel doesn't use gcc. It uses gcc-3.4 because that is the >only one that can build 64bit kernels on i386. 1) the kernel build system as provided by kernel.org uses gcc. Not a specific gcc, just any available gcc (nearly, it does check for really old gccs). 2) using gcc-3.3 to build a amd64 kernel is not efficient, but the resulting kernel will boot without any trouble, even if a bit slow. It is not broken in anyway (try it!). >Any kernel modules you build also have to use gcc-3.4 and not gcc. All kernel modules should be compiled using the exact same gcc as the one used to compile the kernel. if you use gcc-3.3 for the kernel, modules should use that too. If one module (nvidia) requires gcc version 3.4 or higher, then the kernel and all other modules must be recompiled to use that same gcc. Just for the record : changing the kernel Makefile (as Debian apparently did) to force a specific gcc is IMNSHO dumb. > >But that doesn't mean gcc-3.4 should be THE gcc. > Goswin, nobody claimed that. They just want easy choice. what about changing package gcc to check available versions of gcc, and asking the user the one they want to ? Don't worry, I'm still using Debian, and I don't plan to change. Ernest ter Kuile. a developer. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gcc version issue trying to install vmware5
Leopold Palomo-Avellaneda <[EMAIL PROTECTED]> writes: > A Dimarts 14 Juny 2005 11:20, Goswin von Brederlow va escriure: > [] > >> The default compiler is gcc-3.3 and everything in debian uses that. > > Sure? > I think that the kernel doesn't and the nvidia modules _need_ the 3.4 > version. The gernel doesn't use gcc. It uses gcc-3.4 because that is the only one that can build 64bit kernels on i386. Any kernel modules you build also have to use gcc-3.4 and not gcc. But that doesn't mean gcc-3.4 should be THE gcc. > It's a bit confuss to have in this platform two versions of the compiler and > choose the best for each circumstance. Maybe, if the 3.3 and the 3.4 versions > have problems in _our_ platform, we should think again to make some effort in > the a 4.x version of the dist to have only one compiler for _ALL_ the distro. Debian already defines one gcc version to be used for a release, that is what gcc links to. Gcc-3.4 is only used in special circumstances where it is needed and where it doesn't affect the rest of the system. The choice was to use gcc-3.4 or to not have a kernel-image-2.6-amd64 in debian sarge. Same for mozilla and derivates. I think everyone agrees that using gcc-3.4 was the better alternative. For etch the plan is to switch to gcc-3.4 (or later) completly. All c++ libraries need to be recompiled for that. > And I'm writing this with good sense, the last think I want is a flame. I > would like to make just a reflexion. Maybe, I'm wrong. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gcc version issue trying to install vmware5
A Dimarts 14 Juny 2005 11:20, Goswin von Brederlow va escriure: [] > The default compiler is gcc-3.3 and everything in debian uses that. Sure? I think that the kernel doesn't and the nvidia modules _need_ the 3.4 version. It's a bit confuss to have in this platform two versions of the compiler and choose the best for each circumstance. Maybe, if the 3.3 and the 3.4 versions have problems in _our_ platform, we should think again to make some effort in the a 4.x version of the dist to have only one compiler for _ALL_ the distro. And I'm writing this with good sense, the last think I want is a flame. I would like to make just a reflexion. Maybe, I'm wrong. Regards, Leo -- -- Linux User 152692 Catalonia -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gcc version issue trying to install vmware5
tony mancill <[EMAIL PROTECTED]> writes: > Goswin von Brederlow wrote: >> Rupert Heesom <[EMAIL PROTECTED]> writes: >> >> >>>On Sun, 2005-06-12 at 21:45 +0200, Goswin von Brederlow wrote: >>> Rupert Heesom <[EMAIL PROTECTED]> writes: >Just a note to let you know that I installed the vanilla kernel headers, >and I had to redo the soft link of /usr/bin/gcc to /usr/bin/gcc-3.4. No you don't. You should set CC. >>> >>>I did that to start with (kept it that way), but the vmware compile >>>didn't like that, a very good error msg told me to change the s-link, so >>>I did. It then worked. >>> >>>Setting env CC probably works for most things. >> >> >> Changing the link breaks your debian system. > > Perhaps you could elaborate on this. What specifically is broken about the > system if gcc -> gcc-3.4? My system has been setup this way for over 2 > months and there haven't been any adverse side-effects that I'm aware of. The default compiler is gcc-3.3 and everything in debian uses that. If you use anything that needs gcc then you end up with the wrong compiler. Not everything checks like vmware does to make sure it has the right one. > I tried updating it using alternatives, but seemed to lose the preference > everytime I did an apt-get upgrade, I'm pretty certain this is because the > "gcc" package insists that gcc -> gcc-3.3. And rightly so. If you must then create a /usr/local/bin/gcc. Debian won't overwrite that. Or create a /usr/local/bin/kernel/gcc and add /usr/local/bin/kernel/ first to your path only when building kernel modules. > I'd much prefer to set an environment variable as well, but it's going to > require a deeper understanding of the module compilation subsystem of the > 2.6 kernel. Both CC and HOSTCC seem to be ignored. Did you export it? MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gcc version issue trying to install vmware5
Goswin von Brederlow wrote: > Rupert Heesom <[EMAIL PROTECTED]> writes: > > >>On Sun, 2005-06-12 at 21:45 +0200, Goswin von Brederlow wrote: >> >>>Rupert Heesom <[EMAIL PROTECTED]> writes: >>> >>> Just a note to let you know that I installed the vanilla kernel headers, and I had to redo the soft link of /usr/bin/gcc to /usr/bin/gcc-3.4. >>> >>>No you don't. You should set CC. >> >>I did that to start with (kept it that way), but the vmware compile >>didn't like that, a very good error msg told me to change the s-link, so >>I did. It then worked. >> >>Setting env CC probably works for most things. > > > Changing the link breaks your debian system. Perhaps you could elaborate on this. What specifically is broken about the system if gcc -> gcc-3.4? My system has been setup this way for over 2 months and there haven't been any adverse side-effects that I'm aware of. I tried updating it using alternatives, but seemed to lose the preference everytime I did an apt-get upgrade, I'm pretty certain this is because the "gcc" package insists that gcc -> gcc-3.3. I'd much prefer to set an environment variable as well, but it's going to require a deeper understanding of the module compilation subsystem of the 2.6 kernel. Both CC and HOSTCC seem to be ignored. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gcc version issue trying to install vmware5
Rupert Heesom <[EMAIL PROTECTED]> writes: > On Sun, 2005-06-12 at 21:45 +0200, Goswin von Brederlow wrote: >> Rupert Heesom <[EMAIL PROTECTED]> writes: >> >> > Just a note to let you know that I installed the vanilla kernel headers, >> > and I had to redo the soft link of /usr/bin/gcc to /usr/bin/gcc-3.4. >> >> No you don't. You should set CC. > > I did that to start with (kept it that way), but the vmware compile > didn't like that, a very good error msg told me to change the s-link, so > I did. It then worked. > > Setting env CC probably works for most things. Changing the link breaks your debian system. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gcc version issue trying to install vmware5
On Sun, 2005-06-12 at 21:45 +0200, Goswin von Brederlow wrote: > Rupert Heesom <[EMAIL PROTECTED]> writes: > > > Just a note to let you know that I installed the vanilla kernel headers, > > and I had to redo the soft link of /usr/bin/gcc to /usr/bin/gcc-3.4. > > No you don't. You should set CC. I did that to start with (kept it that way), but the vmware compile didn't like that, a very good error msg told me to change the s-link, so I did. It then worked. Setting env CC probably works for most things. -- Rupert Heesom [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gcc version issue trying to install vmware5
Rupert Heesom <[EMAIL PROTECTED]> writes: > Just a note to let you know that I installed the vanilla kernel headers, > and I had to redo the soft link of /usr/bin/gcc to /usr/bin/gcc-3.4. No you don't. You should set CC. > I think I might have previously deleted the vanilla headers when I > wondered what they were doing next to the smp tree! Won't delete them > again! > > VMware has now compiled and running (taking lots of ram!). > > Thanks for your support! MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gcc version issue trying to install vmware5
Just a note to let you know that I installed the vanilla kernel headers, and I had to redo the soft link of /usr/bin/gcc to /usr/bin/gcc-3.4. I think I might have previously deleted the vanilla headers when I wondered what they were doing next to the smp tree! Won't delete them again! VMware has now compiled and running (taking lots of ram!). Thanks for your support! On Thu, 2005-06-09 at 07:01 -0500, Mark Nipper wrote: > On 09 Jun 2005, Rupert Heesom wrote: > I thought all of the derivative kernel-header packages > were suppose to include the vanilla kernel-header-x.y.z-r package > also? Just testing a few in dselect seems to select the base > version also for me on my current system (x86 though, not > x86_64). > > Anyway, yes, installing the kernel-headers-2.6.8-11 > package itself will probably fix your problem. I'm not sure if > it's just kernel-headers-2.6.8-11 off the top of my head or > whether the -amd64 will be on the end also. > -- Rupert Heesom [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gcc version issue trying to install vmware5
> I installed vanilla headers (2.6.8-11) and all is fine now re compiling. > > Thinking back, I seem to remember actually deleting the vanilla headers > since I didn't think they should be there! Shouldn't be so trigger > happy! > > Now on to creating a chroot-ia32 I had same problem (but not for kernel smp) and vmware 5.0 now works perfectly for me. probably: ls -l /usr/bin/gcc -> /usr/bin/gcc-3.3.5 just remove /usr/bin/gcc link and remake a new: ln -s /usr/bin/gcc-3.4 /usr/bin/gcc Giulio
Re: gcc version issue trying to install vmware5
I installed vanilla headers (2.6.8-11) and all is fine now re compiling. Thinking back, I seem to remember actually deleting the vanilla headers since I didn't think they should be there! Shouldn't be so trigger happy! Now on to creating a chroot-ia32 On Thu, 2005-06-09 at 07:01 -0500, Mark Nipper wrote: > On 09 Jun 2005, Rupert Heesom wrote: > I thought all of the derivative kernel-header packages > were suppose to include the vanilla kernel-header-x.y.z-r package > also? Just testing a few in dselect seems to select the base > version also for me on my current system (x86 though, not > x86_64). > > Anyway, yes, installing the kernel-headers-2.6.8-11 > package itself will probably fix your problem. I'm not sure if > it's just kernel-headers-2.6.8-11 off the top of my head or > whether the -amd64 will be on the end also. > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gcc version issue trying to install vmware5
On 09 Jun 2005, Rupert Heesom wrote: > 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?? I thought all of the derivative kernel-header packages were suppose to include the vanilla kernel-header-x.y.z-r package also? Just testing a few in dselect seems to select the base version also for me on my current system (x86 though, not x86_64). Anyway, yes, installing the kernel-headers-2.6.8-11 package itself will probably fix your problem. I'm not sure if it's just kernel-headers-2.6.8-11 off the top of my head or whether the -amd64 will be on the end also. -- Mark Nippere-contacts: 4475 Carter Creek Parkway [EMAIL PROTECTED] Apartment 724 http://nipsy.bitgnome.net/ Bryan, Texas, 77802-4481 AIM/Yahoo: texasnipsy ICQ: 66971617 (979)575-3193 MSN: [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- Version: 3.1 GG/IT d- s++:+ a- C++$ UBL$ P--->+++ L+++$ !E--- W++(--) N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--) Y+ PGP t+ 5 X R tv b+++@ DI+(++) D+ G e h r++ y+(**) --END GEEK CODE BLOCK-- ---begin random quote of the moment--- "...now I am become Death [Shiva]. the destroyer of worlds..." -- J. Robert Oppenheimer on 16 July 1945 at 0529 Mountain War Time in the Jornada del Muerto desert near the Trinity site in the White Sands Missile Range quoting from the Bhagavad-Gita upon witnessing the first atomic detonation by mankind. The quote from the Bhagavad-Gita: If the radiance of a thousand suns Were to burst at once in the sky That would be like the splendor of the Mighty one... I am become Death, The shatterer of Worlds. end random quote of the moment -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gcc version issue trying to install vmware5
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]
Re: gcc version issue trying to install vmware5
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. -- Mark Nippere-contacts: 4475 Carter Creek Parkway [EMAIL PROTECTED] Apartment 724 http://nipsy.bitgnome.net/ Bryan, Texas, 77802-4481 AIM/Yahoo: texasnipsy ICQ: 66971617 (979)575-3193 MSN: [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- Version: 3.1 GG/IT d- s++:+ a- C++$ UBL$ P--->+++ L+++$ !E--- W++(--) N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--) Y+ PGP t+ 5 X R tv b+++@ DI+(++) D+ G e h r++ y+(**) --END GEEK CODE BLOCK-- ---begin random quote of the moment--- I cannot tolerate intolerant people. end random quote of the moment -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
