Tue Aug 30 17:20:58 CDT 2005
Currently, the winejack driver itself (winejack.drv.so), is not explicitly linked against libjack or libpthread. Instead, winejack uses some function pointer and wine_dlsym tricks to load libjack at runtime. libjack (which is part of the jackit source, not wine), IS explicitly linked against libpthread.
Is there any chance this is going to work with wine-kthread? Is the function pointer/wine_dlsym tricks some work around related to the fact that libjack is linked against pthread, but wine can't be? For example, it is my understanding that wine-kthread provides pthread emulation -- is this method of loading libjack with wine_dlsym a way to get libjack to uses wine's pthread emulation instead of /lib/libpthread?
On Nov 15, 2003 5:11 AM, Mike Hearn <mike at theoretic.com> wrote:
> On Sat, 2003-11-15 at 03:06, Jeremy Shaw wrote:
> > I am trying to use wine-pthread because I want to use the winejack
> > driver. The winejack driver does not work correctly with wine-kthread,
> > because in libjack, there is a call to pthread_create which never
> > returns.
> That sounds like a bug in Wine. My understanding is that when using
> kthreads, we emulate pthreads - hence Wine must NOT be linked against
> the system pthreads lib.
> > According to usenet, this could happen because wine-kthread
> > is not linked against libpthread explicitly. I tried adding an
> > explicit -lpthread to wine-kthread, but this just cause wine-kthread
> > to hang (similar to wine-pthread, but in a different location).
> Yes, I don't think that will work.
> The main wine binary should now detect which version (kthread or
> pthread) you need, and select it for you at runtime. You need latest CVS
> for that though. If you think it's choosing the wrong one, then that
> also is a bug, but you should not need to override its choice.
More information about the wine-devel