Subject: Re: libpthread busted?
To: Bill Studenmund <email@example.com>
From: Peter Seebach <firstname.lastname@example.org>
Date: 02/28/2003 18:10:49
In message <Pine.NEB.email@example.com>
, Bill Studenmund writes:
>The reason Jason thinks it doesn't work is that you've bound to a libc
>mutex operation, which only happens if NetBSD's libpthread isn't around at
>dynamic link time.
Okay. I'm not sure how I'd... ldd!
-lm.0 => /usr/lib/libm387.so.0
-lm.0 => /usr/lib/libm.so.0
-lcrypt.0 => /usr/lib/libcrypt.so.0
-lc.12 => /usr/lib/libc.so.12
>> crash seems to happen *before* the pth stuff gets involved, although I can't
>> be sure.
>If that's not a typo, that's a problem. With -current pthreads, you can
>ONLY use -current pthreads. You can't mix different thread libraries
Or I could just be easily confused; I vaguely recall pthreads and "pth" being
Oh! I have several packages which claim they "need" pth. So, let me guess, I
should delete *those*, too, and nuke the pth package?
>What MIGHT be happening is that a program's using pth, not NetBSD's
>libpthread. That will be a problem as we have expectations of what
>-lpthread does (overrides some weak symbols in libc) that the pth package
>mightn't be doing.
Oh-ho! Perfect, logical, explanation. I will try that.