In article <[EMAIL PROTECTED]> you write:
>In article <[EMAIL PROTECTED]>,
>Jordan K. Hubbard <[EMAIL PROTECTED]> wrote:
>> > The other possibility would be to fix the wine port so it calls
>> > dllockinit() to set up locking. I don't know for sure how hard that
>> > would be, but it's probably a feasible solution.
>>
>> To be honest, I'd be the most comfortable with this solution
>...
>As far as I know, Wine is the only port that has problems with the
>version of the dynamic linker that's in -current at present. I've
>looked into adding the dllockinit() stuff to Wine, but could use
>some help from somebody who knows its internals better.
Hm you could ask over in comp.emulators.ms-windows.wine...
> I found
>the threads primitives, etc., but am not so sure where to place the
>dllockinit() call.
When does it need to be called, just when starting a new thread?
(i have looked at the wine source before but never at ld-elf.so...)
And would this be the same on -stable and 4.0? Currently you
should be able to build a wine on a -stable box and it would still
run on 4.0 (well it wouldn't run _worse_ than on -stable), at least
thats the idea.
Anyway if it should be called before a new thread becomes
runnable for the first the i think it could go in THREAD_Create
(in scheduler/thread.c), if it needs to be called from within
the new thread itself it looks like it should go in THREAD_Start
in the same source.
HTH,
--
Juergen Lock <[EMAIL PROTECTED]>
(remove dot foo from address to reply)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
