"Mutex unlock failure" when compiling KDE (upgrade from 6.x)

Kris Kennaway kris at FreeBSD.org
Sat Mar 22 10:40:41 PDT 2008

Dmitry RCL Rekman wrote:
> Hi,
> On Sat, Mar 22, 2008 at 6:14 PM, Kris Kennaway <kris at freebsd.org 
> <mailto:kris at freebsd.org>> wrote:
>      > Actually, the problem was tracked down to be inside uic. When
>     built on my
>      > (and Leslie's) 7.0 "upgraded" from 6.x system, uic does not link to
>      > libthr.so, while in a newly-installed 7.0 it does.
>     It should not be linking (directly) to libthr at all, it should be
>     linking to libpthread (which is a symlink to it).
> Yes, it does link to -lpthread, but ldd tells different things on newly 
> installed 7.0 and 7.0 upgraded from 6.2... I don't know if it's the 
> reason, that was Mel's guess ( 
> http://docs.freebsd.org/cgi/mid.cgi?200803141208.57610.fbsd.questions ).
>      > So one of people here (Mel) asked to provide the actual
>     commandline used to
>      > link uic (see this for reference:
>      >
>      http://docs.freebsd.org/cgi/mid.cgi?200803161912.18248.fbsd.questions
>     ),
>      > which is what I did.
>     It links to libqt-mt and presumably gets its thread library from there,
>     so the question extends there.
> Well, the commandline used to build libqt-mt is included in the log and 
> it also links to -pthread...

Yes, also uic (correctly) links directly to -pthread (I missed this on 
first read).  The only way I can see this failing is if your /lib is not 
correctly populated.  What is the output of

ls -l /lib/libthr* /usr/lib/libpthr*


More information about the freebsd-questions mailing list