Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 19692 - VMWare Workstation 4.0 LIBC issues (vmnet-natd does not start) with USE=nptl
Summary: VMWare Workstation 4.0 LIBC issues (vmnet-natd does not start) with USE=nptl
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 All
: High normal
Assignee: Preston A. Elder (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-20 16:22 UTC by Mike Jones
Modified: 2004-03-29 05:54 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Jones 2003-04-20 16:22:12 UTC
Hi there.  VMWare Workstation 4.0.xxxx works fine under glibc >2.3, with one
exception: vmnet-natd fails to start (complaining about lacking GLIBC_2.0
symbols in libc) when USE includes nptl.

[root@ashmodai:~]# /opt/vmware/bin/vmnet-natd
/opt/vmware/bin/vmnet-natd: relocation error: /opt/vmware/bin/vmnet-natd: symbol
errno, version GLIBC_2.0 not defined in file libc.so.6 with link time reference
[root@ashmodai:~]# /lib/libc.so.6 | egrep -i "(c library|nptl)"
GNU C Library stable release version 2.3.2, by Roland McGrath et al.
NPTL 0.29 by Ulrich Drepper

Works fine on my non-NPTL (read: nvidia card installed :-) boxes.

Reproducible: Always
Steps to Reproduce:
1. USE=nptl
2. /etc/init.d/vmware start
3. watch networking bomb

Actual Results:  
vmnet-natd didn't start

Expected Results:  
...it should have started :-)

Yea yea, I know that NPTL is experimental, don't shoot me :-)
Comment 1 Seth Chandler 2003-04-22 03:08:34 UTC
ahh...you're really going to have to take this up with the nvidia folks i think...
Comment 2 Brad Laue (RETIRED) gentoo-dev 2003-05-03 18:27:45 UTC
Marking this one invalid for two reasons:

1) The conditions are highly experimental

2) The resolution would have to come from upstream
Comment 3 Tibor Gemes 2004-03-29 05:54:54 UTC
Upgrading to vmware-workstation 4.5.1.7568 eliminated this problem for me.