Ove Kaaven <[EMAIL PROTECTED]> writes:
> On Fri, 24 Mar 2000, Jeremy White wrote:
> > So, my basic question is:
> > What is wrong with Ove's patch, and why can't it be part of the
> > main Wine release?
>
> That is explained at the beginning of the patch - it is currently quite
> glibc-specific (Alexandre calls in unportable, although I wouldn't myself
> consider it impossible to port to other systems, like FreeBSD), and
> Alexandre really wants to see a portable fix for libc threadsafety before
> slipping in system-specific workarounds that ~90% of the developers would
> consider "good enough" (and the rest wouldn't know how to fix).
Yes, the theory is that if it's broken for everybody, it's more likely
to get fixed than if it only breaks on "exotic" platforms. Since it
still hasn't been fixed it seems I'll have to revise my theory...
I think at this point we have two possibilities: one is to provide our
own complete libpthread implementation to override the libc one,
i.e. the extended version of Ove's patch.
The other solution is to try to use the existing libpthread to create
our threads; if we can work around the %gs register problem, this
would have the advantage of better integrating with the native
libraries (for instance gdb would then be able to understand what's
going on with threads). This is IMO a more elegant solution, but the
big question is: can it be made to work?
--
Alexandre Julliard
[EMAIL PROTECTED]