Topic: Solved: VMware 2.0 on SME7.4 libstdc++.so.6 clash

[compsos]

Hi
We have installed on a fresh installation of SME 7.4 VMware-server-2.0.0-122956. Encounted problems with the libstdc++.so.6 file used by VMware and the installed libstdc++.so.6.0.3. Vmware would not configure fully until a link was made from /usr/lib to /usr/lib/vmware/lib/libstdc++.so.6/libstdc++.so.6. Not sure what will break using the older VMware file?

Is there a way to "path" to each for the individual programs?

Sme File in /usr/lib
-rwxr-xr-x  1 root root 792856 Jul 25  2008 libstdc++.so.6.0.3
VMware File /usr/lib/vmware/lib/libstdc++.so.6/
-rwxr-xr-x  1 root root 904900 Oct 13 08:25 vmware/lib/libstdc++.so.6/libstdc++.so.6

Not sure if this is related but are having trouble with bride mode in the guest OS. Otherwise all appears to be working etc Guest networking. TIA

[David Harper]

RHEL 4.5 is on the supported OS list, but RHEL 4.7 is not; perhaps these issues will be resolved by VMWare in a future release?

[compsos]

Thanks David
No I have a running VMware2 on 7.4 although it was 7.3 and upgraded. Comparing files so far has not shown any differences.

/usr/lib/vmware/bin/vmware-hostd: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.5' not found (required by /usr/lib/vmware/bin/vmware-hostd)

This is in the /etc/rc.d/init.d/vmware file. I imagine it should reeturn the vmware path and not /usr/lib?
  # Convert -'s in component name to _ and lookup its libdir
  local component=`echo $component | tr '-' '_'`
  local libdir="vmdb_$component_libdir"

  exec "$libdir"'/bin/launcher.sh'              \
       "$libdir"'/lib'                          \
       "$libdir"'/bin/'"$binary"                \
       "$libdir"'/libconf' "$args"
  return 1
}

[compsos]

Ok 2 things

• copied a the vmware libstdc++.so.6 to the /usr/lib directory. This downgraded slightly from 6.0.3 to 6. So far no ill effects
• The bridge did not work as it needed a cable and a switch (physical) to work against. As we were in setup mode were not concerned about the LAN side. Note it did work if NAT or host only was set
  This may be a clue for anyone else having Bridge mode problems in VMWare