wine & -current & notes & networkaccess
Brian Rogers
burpmaster at truffula.net
Sun May 9 23:55:57 PDT 2004
Michael Reifenberger wrote:
>Hi,
>running the notes-client with wine under -current (after some changes to our
>pthreads some months ago) gives me when accessing a database over the network:
>
>...
>Fatal error 'Uninitialized mutex in pthread_mutex_trylock_basic' at line 474 in
>file /usr/src/lib/libpthread/thread/thr_mutex.c (errno = 0)
>wine: Unhandled exception (thread 000c), starting debugger...
>fixme:ntdll:NtQueryVolumeInformationFile device info not properly supported on
>this platform
>WineDbg starting on pid 8
>...
>
>Is wine missing something or is libpthread doing something wrong?
>
>my /etc/libmap.conf BTW:
>
># default
>libc_r.so.5 libpthread.so.1
>libc_r.so libpthread.so
>libkse.so.1 libpthread.so.1
>libkse.so libpthread.so
>...
>
>
I see this also. There are two wine binaries, wine-kthread and
wine-pthread. On FreeBSD, just wine-kthread is built and it is
installed as /usr/local/bin/wine. wine-kthread doesn't seem to like
being linked with libpthread, but that will happen through the arts
sound driver or any .dll.so file that links to the OpenGL library.
If you build wine from CVS, you can configure it with --without-opengl.
Then if you're not using the arts sound driver, wine-kthread will work
just fine. I also found that you can cd into wine/loader and do "gmake
wine-pthread" to build the pthread version of wine. It can handle
libpthread just fine, but it has its own problems. (I don't think the
wine people even realize that wine-pthread works on FreeBSD)
More information about the freebsd-threads
mailing list