Trent W. Buck wrote: > Package: vmware-package > Version: 0.22 > Severity: normal > > I built vmware-server-console thusly: > > # make sure contrib is in your sources.list > aptitude install vmware-package unzip && > cd `mktemp -d` && > # From http://register.vmware.com/content/download.html > wget > http://download3.vmware.com/software/vmserver/VMware-server-linux-client-1.0.5-80187.zip > && > unzip *.zip VMware-server-console-1.0.5-80187.tar.gz && > rm *.zip && > make-vmpkg VMware-server-console-1.0.5-80187.tar.gz && > dpkg -i vmware-server-console/*deb > > Attempting to then run vmware-server-console results in it crashing: > > $ vmware-server-console > /usr/lib/vmware-server-console/bin/vmware-server-console: > /usr/lib/vmware-server-console/lib/libgcc_s.so.1/libgcc_s.so.1: version > `GCC_4.2.0' not found (required by /usr/lib/libstdc++.so.6) > /usr/lib/vmware-server-console/bin/vmware-server-console: > /usr/lib/vmware-server-console/lib/libgcc_s.so.1/libgcc_s.so.1: version > `GCC_4.2.0' not found (required by /usr/lib/libstdc++.so.6) > /usr/lib/vmware-server-console/bin/vmware-server-console: > /usr/lib/vmware-server-console/lib/libgcc_s.so.1/libgcc_s.so.1: version > `GCC_4.2.0' not found (required by /usr/lib/libstdc++.so.6) > $
This looks like a problem with mixing Debian's libstdc++6 with vmware's
libgcc_s.
> However, looking at other bug reports I found this environment
> variable, which fixes things.
>
> $ VMWARE_USE_SHIPPED_GTK=force vmware-server-console
>
> I suspect this indicates that the vmware-server-console package should
> Depend or Recommend on an obsolete version of GTK and/or should
> default to using the "real" GTK rather than the hokey one that VMware
> ship.
Well, Debian ships libgtk2.0-0 and libgtk1.2...
VMWARE_USE_SHIPPED_GTK=force happens to "force" the wrapper script to
use VMware's "hokey" libs, not the systems. From wrapper-gtk24.sh,
# When environment variable VMWARE_USE_SHIPPED_GTK is set to "force", we
# forcefully use the 32-bit GTK+ 2.4 runtime environment (libraries + their
# configuration files) that we ship.
#
# When environment variable VMWARE_USE_SHIPPED_GTK is set to "yes", we
# thoughtfully use the 32-bit GTK+ 2.4 runtime environment (libraries +
their
# configuration files) that we ship. This works for all but the most broken
# environments, so if we're guessing we try this.
#
# When environment variable VMWARE_USE_SHIPPED_GTK is set to "no", we use
# the system's 32-bit GTK+ 2.4 runtime environment.
#
# When environment variable VMWARE_USE_SHIPPED_GTK is not set (the
default), we
# try to make an educated guess.
If you could, could you please unset VMWARE_USE_SHIPPED_GTK, but make a
modification to /usr/lib/vmware-server-console/lib/wrapper-gtk24.sh?
Comment out line 246,
vm_append_lib 'libgcc_s.so.1'
Does vmware-server-console now start up?
It also might be helpful when reporting problems like this if you could
attach the output of
pmap `pidof /usr/lib/vmware-server-console/bin/vmware-server-console`
when vmware-server-console starts up correctly. Thanks.
--
Robert Edmonds
[EMAIL PROTECTED]
signature.asc
Description: Digital signature
