Thanks, that seemed to fix it.
Jeremy Shaw.
On Nov 16, 2003 12:42 PM, Alexandre Julliard <[EMAIL PROTECTED]> wrote:
> Jeremy Shaw <[EMAIL PROTECTED]> writes:
>
> > Hopefully someone who understands linker magic better than me can come
> > up with a better fix...
>
> I think adding --expor
Jeremy Shaw <[EMAIL PROTECTED]> writes:
> Hopefully someone who understands linker magic better than me can come
> up with a better fix...
I think adding --export-dynamic to the link should be
enough. Something like this should do the trick:
Index: configure.ac
==
Hello,
I have a work-around -- I put loader/kthread.c in its own shared library and things
work again:
I changed:
distcc -c -I. -I. -I../include -I../include-Wall -mpreferred-stack-boundary=2
-fno-strict-aliasing -gstabs+ -Wpointer-arith -O2 -g -o kthread.o kthread.c
to:
distcc -shared
Hello,
I did some experiments, and I believe that something did get broken in
the recent changes -- specifically, libjack is now calling the real
pthread functions instead of the wine emulated functions.
In cvs head, in loader/kthread.c, in pthread_create() I added a
P_OUTPUT. I never see 'pthrea
Jeremy Shaw <[EMAIL PROTECTED]> writes:
> So, if winejack.drv.so requires libjack which is linked against
> libpthread -- should it work with wine-kthread? And, if it does work,
> will libjack be calling the real pthread functions in libpthread or
> the emulated pthread functions in wine?
Yes it
Hello,
So, if winejack.drv.so requires libjack which is linked against
libpthread -- should it work with wine-kthread? And, if it does work,
will libjack be calling the real pthread functions in libpthread or
the emulated pthread functions in wine?
Jeremy Shaw.
At Sat, 15 Nov 2003 22:42:27 +0100
> From reading some of the other messages sent today, I gather wine-pthreads requires
> nptl and the new (2.5.x/2.6.x) kernel?
Yes.
> 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
Hello,
>From reading some of the other messages sent today, I gather wine-pthreads requires
>nptl and the new (2.5.x/2.6.x) kernel?
Currently, the winejack driver itself (winejack.drv.so), is not explicitly linked
against libjack or libpthread. Instead, winejack uses some function pointer and
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 Win
Hello,
I was trying to run wine-pthread, but it hangs immediately after
startup -- I can't even hit cntl-c to exit. If I try to run it under
gdb, it seg faults. A backtrace looks like:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 14857)]
0x40040fd9 in __er
10 matches
Mail list logo
