Wine and glibc 3.2.x
dank at kegel.com
Fri Mar 21 15:44:51 CST 2003
davide.giannotti at itsplanet.com wrote:
> Ok, i recently compiled and upgraded to glibc 3.2.1 and there's no way to make
> wine work. There's thread related bug.
> New Red Hat, Suse and Mandrake will be shipped with this new version of glibc,
> so i think that's a serious bug.
We were all quite concerned about it until somebody reported a workaround; see
The workaround is to give the command
before running Wine (and probably before running configure, too).
(This is documented in each distro's beta release notes, e.g.
Have you tried this yet?
What CPU and OS are you using?
> Configure cannot even check that libc are reentrant, i'm not a glibc expert
> but there's some error with _errno and _errno_location.
> I tried to apply a patch i found in the patch mailing list, but it didn't work
> ( http://www.winehq.com/hypermail/wine-patches/2003/01/0338.html )
That patch was bogus, it is not the right fix. The right fix is
for Wine to adapt to the new threading model in glibc2.3 (not 3.2, I think),
which is far superior to the old one. See http://www.kegel.com/c10k.html#threads.nptl
> So, consider that every linux distribution will be shipped with the new glibc,
> and that there will be really a few windows programs that can work without
> thread support.... well... i'd think about give priority to solve this one.
The changes needed are deep. Alexandre has started on them, but
given the workaround, it can probably wait a bit.
More information about the wine-devel