i've rebuilt my kernel 2.6.19 using gcc version 4.1.2 but when i try to
update the vmware module, it gives me an error telling me i built my kernel
using 3.4.6 but i'm trying to build the module using 4.1.2. i'm pretty sure
the kernel was built with 4.1.2.

anyways, i'm running some strange combo of current and 11.0. i've had some
problems and had to roll back, then tried again.. so i'm sure some programs
i have are a littled screwed up. because of this, i imagine that the vmware
message is a little off and its probably telling me that some other library
is compiled with a different version of gcc. maybe i didn't update
something to current that i should have? any ideas?

this is the exact message i'm getting:

Your kernel was built with "gcc" version "3.4.6", while you are trying to
use "/usr/bin/gcc" version "4.1.2". This configuration is not supported and
VMware Workstation cannot work in such configuration. Please either
recompile your kernel with "/usr/bin/gcc" version "4.1.2", or
restart /usr/bin/vmware-config.pl with CC environment variable pointing to
the "gcc" version "3.4.6".


thanks,
miguel de anda


--
Posted via a free Usenet account from http://www.teranews.com

On Sat, 28 Apr 2007 14:12:49 -0700, Miguel De Anda <miguel@thedeanda.com> wrote:

>i've rebuilt my kernel 2.6.19 using gcc version 4.1.2 but when i try to
>update the vmware module, it gives me an error telling me i built my kernel
>using 3.4.6 but i'm trying to build the module using 4.1.2. i'm pretty sure
>the kernel was built with 4.1.2.

One way to make sure?
>
>anyways, i'm running some strange combo of current and 11.0. i've had some
>problems and had to roll back, then tried again.. so i'm sure some programs
>i have are a littled screwed up. because of this, i imagine that the vmware
>message is a little off and its probably telling me that some other library
>is compiled with a different version of gcc. maybe i didn't update
>something to current that i should have? any ideas?

slack-current, kernel 2.6.20.7 and vmware beta build 44426 work fine here

Grant.
--
http://bugsplatter.mine.nu/

On Sat, 28 Apr 2007 14:12:49 -0700, Miguel De Anda wrote:

> i've rebuilt my kernel 2.6.19 using gcc version 4.1.2 but when i try to
> update the vmware module, it gives me an error telling me i built my
> kernel using 3.4.6 but i'm trying to build the module using 4.1.2. i'm
> pretty sure the kernel was built with 4.1.2.
>
> anyways, i'm running some strange combo of current and 11.0. i've had
> some problems and had to roll back, then tried again.. so i'm sure some
> programs i have are a littled screwed up. because of this, i imagine
> that the vmware message is a little off and its probably telling me that
> some other library is compiled with a different version of gcc. maybe i
> didn't update something to current that i should have? any ideas?
>
> this is the exact message i'm getting:
>
> Your kernel was built with "gcc" version "3.4.6", while you are trying
> to use "/usr/bin/gcc" version "4.1.2". This configuration is not
> supported and VMware Workstation cannot work in such configuration.
> Please either recompile your kernel with "/usr/bin/gcc" version "4.1.2",
> or restart /usr/bin/vmware-config.pl with CC environment variable
> pointing to the "gcc" version "3.4.6".
>
>
> thanks,
> miguel de anda

Upgrading the toolchain is a messy business. There's a lot to recompile,
not just the kernel when you update the compiler. glibc key among them.
On the obvious side, while you may have compiled your kernel with 4.1.2,
did you install it? Did you boot it?

--
Peter

Hello,

On Sat, 28 Apr 2007 14:12:49 -0700, Miguel De Anda wrote:

> i've rebuilt my kernel 2.6.19 using gcc version 4.1.2 but when i try to
> update the vmware module, it gives me an error telling me i built my
> kernel using 3.4.6 but i'm trying to build the module using 4.1.2. i'm
> pretty sure the kernel was built with 4.1.2.
>
cat /proc/version will show you if you are right.

> anyways, i'm running some strange combo of current and 11.0. i've had
> some problems and had to roll back, then tried again.. so i'm sure some
> programs i have are a littled screwed up. because of this, i imagine
> that the vmware message is a little off and its probably telling me that
> some other library is compiled with a different version of gcc. maybe i
> didn't update something to current that i should have? any ideas?
>
> this is the exact message i'm getting:
>
> Your kernel was built with "gcc" version "3.4.6", while you are trying
> to use "/usr/bin/gcc" version "4.1.2". This configuration is not
> supported and VMware Workstation cannot work in such configuration.
> Please either recompile your kernel with "/usr/bin/gcc" version "4.1.2",
> or restart /usr/bin/vmware-config.pl with CC environment variable
> pointing to the "gcc" version "3.4.6".
>
Perhaps you will have problems further since the environment is not fully
gcc-4.1.2 compiled.
But it is not forbidden to try

I had some compilation error issues for vmware on a 2.6.19 (and 2.6.20)
kernel a while ago. I hope they are corrected in the latest version.

>
> thanks,
> miguel de anda


Regards,
Thierry

Thierry MERLE wrote:

> Hello,
>
> On Sat, 28 Apr 2007 14:12:49 -0700, Miguel De Anda wrote:
>
>> i've rebuilt my kernel 2.6.19 using gcc version 4.1.2 but when i try to
>> update the vmware module, it gives me an error telling me i built my
>> kernel using 3.4.6 but i'm trying to build the module using 4.1.2. i'm
>> pretty sure the kernel was built with 4.1.2.
>>
> cat /proc/version will show you if you are right.
>

$cat /proc/version
Linux version 2.6.19 (my email address) (gcc version 3.4.6) #6 SMP PREEMPT
Fri Jan 12 00:25:49 PST 2007


Odd, how did this happen? I basically upgraded everything to
slackware-current, then rebuilt my kernel. I suppose I can try with a
different version of the kernel, just to make sure all the files are new.


--
Posted via a free Usenet account from http://www.teranews.com

Peter wrote:

> On Sat, 28 Apr 2007 14:12:49 -0700, Miguel De Anda wrote:
>
>> i've rebuilt my kernel 2.6.19 using gcc version 4.1.2 but when i try to
>> update the vmware module, it gives me an error telling me i built my
>> kernel using 3.4.6 but i'm trying to build the module using 4.1.2. i'm
>> pretty sure the kernel was built with 4.1.2.
>>
>> anyways, i'm running some strange combo of current and 11.0. i've had
>> some problems and had to roll back, then tried again.. so i'm sure some
>> programs i have are a littled screwed up. because of this, i imagine
>> that the vmware message is a little off and its probably telling me that
>> some other library is compiled with a different version of gcc. maybe i
>> didn't update something to current that i should have? any ideas?
>>
>> this is the exact message i'm getting:
>>
>> Your kernel was built with "gcc" version "3.4.6", while you are trying
>> to use "/usr/bin/gcc" version "4.1.2". This configuration is not
>> supported and VMware Workstation cannot work in such configuration.
>> Please either recompile your kernel with "/usr/bin/gcc" version "4.1.2",
>> or restart /usr/bin/vmware-config.pl with CC environment variable
>> pointing to the "gcc" version "3.4.6".
>>
>>
>> thanks,
>> miguel de anda
>
> Upgrading the toolchain is a messy business. There's a lot to recompile,
> not just the kernel when you update the compiler. glibc key among them.
> On the obvious side, while you may have compiled your kernel with 4.1.2,
> did you install it? Did you boot it?
>

I figured I'd have problems, but I assume that updating all packages to
slackware-current would also update my toolchain with everything
compatible. Was that a bad assumption?



--
Posted via a free Usenet account from http://www.teranews.com

On 2007-05-04, Miguel De Anda <miguel@thedeanda.com> wrote:
>
> I figured I'd have problems, but I assume that updating all packages to
> slackware-current would also update my toolchain with everything
> compatible. Was that a bad assumption?


That depends on how you updated. If you followed the instructions given
in UPGRADE.TXT, then everything should have been updated properly.

RW