VMware Breaks!

[Lane P. Lester]

If you use VMware, I'd be interested if you've had any problem with it
as a result of upgrading xfce.  Although I used it a lot yesterday, this
morning VMware refused to start. It said it needed to be re-configured
for my Linux kernel. I can't imagine what I did to screw the thing up. I
installed some software yesterday, mostly connected with the new release
of Xfce, but I don't see how that could have affected it... but I guess
it did.

Even worse, when I ran vmware-config.pl, I got some weird errors, but
then it said everything was OK... only it wasn't. Here's an early error:
Argument "gcc (GCC) 3" isn't numeric in numeric ge (>=) at
/usr/bin/vmware-config.pl line 1493, <STDIN> line 1.

Isn't that weird? Then I got lots of warnings, of which the
following are a good representation:
 /usr/src/linux/include/asm/system.h: In function `__set_64bit_var':
/usr/src/linux/include/asm/system.h:190: warning: dereferencing
type-punned pointer will break strict-aliasing
rules/usr/src/linux/include/asm/system.h:190: warning: dereferencing
type-punned pointer will break strict-aliasing rules../include/vm_asm.h:
In function `Vmx86_SetStartTime':../include/vm_asm.h:1033: warning: use
of memory input without lvalue in asm operand 4 is
deprecated../include/vm_asm.h: In function
`Vmx86_GetMHzEstimate':../include/vm_asm.h:1033: warning: use of memory
input without lvalue in asm operand 4 is deprecated../include/vm_asm.h:
In function `Div643264':../include/vm_asm.h:1033: warning: use of memory
input without lvalue in asm operand 4 is deprecated`-m486' is
deprecated. Use `-march=i486' or `-mcpu=i486' instead. cc1: warning:
-malign-loops is obsolete, use -falign-loops cc1: warning: -malign-jumps
is obsolete, use -falign-jumps cc1: warning: -malign-functions is
obsolete, use -falign-functions../include/vm_asm.h: In function
`Div643264':../include/vm_asm.h:1033: warning: use of memory input
without lvalue in asm operand 4 is deprecated`-m486' is deprecated. Use
`-march=i486' or `-mcpu=i486' instead. cc1: warning: -malign-loops is
obsolete, use -falign-loops cc1: warning: -malign-jumps is obsolete, use
-falign-jumps cc1: warning: -malign-functions is obsolete, use
-falign-functions`-m486' is deprecated. Use `-march=i486' or
`-mcpu=i486' instead. cc1: warning: -malign-loops is obsolete, use
-falign-loops cc1: warning: -malign-jumps is obsolete, use -falign-jumps
cc1: warning: -malign-functions is obsolete, use -falign-functions
`-m486' is deprecated. Use `-march=i486' or `-mcpu=i486' instead.
cc1: warning: -malign-loops is obsolete, use -falign-loops
cc1: warning: -malign-jumps is obsolete, use -falign-jumps
cc1: warning: -malign-functions is obsolete, use -falign-functions
make[2]: Leaving directory
`/tmp/vmware-config0/vmmon-only/driver-2.4.20' make[1]: Leaving
directory `/tmp/vmware-config0/vmmon-only' make: Leaving directory
`/tmp/vmware-config0/vmmon-only' 
The module loads perfectly in the running kernel.

But look at that last line!

The only thing I know to do right now is to unpack the VMware distro and
reinstall it. I hate being dependent on that program, but one of the
few things I can do to make any extra money depends on it.

Do you have any suggestions on how I can restore my ability to use
VMware?

Lane
____
Lane P. Lester / Madison County, Georgia
**Running Linux more and Windows less**