Re: wine/pthread broken in netbsd 4 beta

Brian de Alwis <bsdcs.ubc.ca> writes:
> On 2007.01.14 23:37:51 +0000, Simon Truss wrote:
>> If you know more than the PRs are you saying that
the Q3 and Q4 branches 
>> are broken for NetBSD then? If so I will try
patching an old pkgsrc/wine 
>> into Q4 and see how far I get. Then there is
something that I can 
>> compare against to find the cause.
>
> I know little more about the causes than stated in the
PRs.  From
> perusing the Wine mailing lists and FreeBSD and OpenBSD
chatter,
> the problems seems to be related to both threading and
the expected
> memory layouts.

I don't think this is really the reason, or if it is,
somehow we had
things working better before. At one point I was able to get
Wine
working quite well with many apps, and that stopped. I don't
think the
threading stuff etc. explains why it broke.

Perry

> As posted to the Wine mailing list (in 2005!):
>
------------------------------------------------------------
----------
> Win32 threading is broken or semi-functional on every
OS except Linux.  The
> work that needs to be done requires an extremely deep
understanding of the
> threading implementation on those operating systems:
only somebody with a
> lot of expertise can do it. I would not expect this
situation to improve
> anytime soon. For now I think FreeBSD is the closest
you'll get to working
> threading on BSD.
>
------------------------------------------------------------
----------
>
> <http://www.winehq.com/pipermail/wine-use
rs/2005-February/016839.html>

Has anyone fix for the problem? I replied to another thread
sorry, but it
looks like problem exists for a long time and nobody has an
advice.

Maybe someone has already fixed in his local computer and
didnt update the
list.

Regards,




Perry E. Metzger wrote:
> 
> 
> Brian de Alwis <bsdcs.ubc.ca> writes:
>> On 2007.01.14 23:37:51 +0000, Simon Truss wrote:
>>> If you know more than the PRs are you saying
that the Q3 and Q4 branches 
>>> are broken for NetBSD then? If so I will try
patching an old pkgsrc/wine 
>>> into Q4 and see how far I get. Then there is
something that I can 
>>> compare against to find the cause.
>>
>> I know little more about the causes than stated in
the PRs.  From
>> perusing the Wine mailing lists and FreeBSD and
OpenBSD chatter,
>> the problems seems to be related to both threading
and the expected
>> memory layouts.
> 
> I don't think this is really the reason, or if it is,
somehow we had
> things working better before. At one point I was able
to get Wine
> working quite well with many apps, and that stopped. I
don't think the
> threading stuff etc. explains why it broke.
> 
> Perry
> 
>> As posted to the Wine mailing list (in 2005!):
>>
------------------------------------------------------------
----------
>> Win32 threading is broken or semi-functional on
every OS except Linux. 
>> The
>> work that needs to be done requires an extremely
deep understanding of
>> the
>> threading implementation on those operating
systems: only somebody with a
>> lot of expertise can do it. I would not expect this
situation to improve
>> anytime soon. For now I think FreeBSD is the
closest you'll get to
>> working
>> threading on BSD.
>>
------------------------------------------------------------
----------
>>
>> <http://www.winehq.com/pipermail/wine-use
rs/2005-February/016839.html>
> 
> 

-- 
View this message in context: http://www.nabble.com/wine-pt
hread-broken-in-netbsd-4-beta-tf2971852.html#a11044010
Sent from the netbsd-help mailing list archive at
Nabble.com.