http://bugs.winehq.com/show_bug.cgi?id=1090
------- Additional Comments From z_god@wanadoo.nl 2003-25-06 15:09 ------- Bug comments restored from Gmane.org:
Whenever wine is launched with any arguments the following is displayed:
/usr/bin/wine.bin: relocation error: /usr/bin/../lib/libntdll.dll.so: symbol __libc_fork, version GLIBC_2.1.2 not defined in file libc.so.6 with link time reference Wine failed with return code 127
Please fix this - I can't run ANYTHING through wine - I really do not want to have to reboot into Windoze!
------- Additional Comments From dragon_sdc <at> hotmail.com 2002-10-20 16:32 ------- Additional info:
It appears the problem is the result of me upgrading libc6 and/or libc6-dev to version 2.3.1-1 (Debian package). I have just downgraded to 2.2.5-15 and the problem disappeared.
Therefore it might well a problem with libc6 not wine in which case apologies, but I'll leave it to you to find out - I have no clue...
------- Additional Comments From marcus <at> jet.franken.de 2002-10-20 16:41 ------- user error (bad glibc upgrade)
------- Additional Comments From depanofsky97 <at> alumni.amherst.edu 2002-10-21 22:06 ------- This is not a problem with a bad glibc version. Although this problem will go away when wine is re-compiled with the new glibc installed, the problem is in the wine source, not in glibc. From the glibc FAQ 3.12:
ISO C states that identifiers beginning with an underscore are internal to the libc. An application program normally shouldn't use those internal interfaces (there are exceptions, e.g. __ivaliduser). If a program uses these interfaces, it's broken. These internal interfaces might change between glibc releases or dropped completely.
The problem with a wine linked with glibc-2.2 not running with glibc-2.3 is because wine uses __libc_fork in scheduler/pthread.c and apparently, this interface has finally been dropped. I immagine that since __libc_fork is only used if (__GLIBC__ == 2) && (__GLIBC_MINOR__ >= 1) && defined(HAVE___LIBC_FORK) that wine can do without this hack.
------- Additional Comments From dpaun <at> rogers.com 2003-03-25 17:40 ------- Looks like it's ready to be CLOSED.
------- Additional Comments From mike <at> theoretic.com 2003-03-27 04:30 ------- Closing, the bug is old with no updates. Also the threading stuff is changing lately, presumably the use of internal functions will be removed as well.