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:
>
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 o
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 t
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 w
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
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
> versi
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
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 installe
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 t
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
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.
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
> wond
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
> 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 n
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
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
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
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:
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.
I did not compile my current kernel, I installed it (smp version)
through apt-get, so the error msg could well be true.
I tried to install an updated gcc, but
19 matches
Mail list logo
