Date: Sat, 22 Mar 2008 18:40:45 +0100 From: Kris Kennaway <kris@FreeBSD.org> To: Dmitry RCL Rekman <dmitry.rekman@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: "Mutex unlock failure" when compiling KDE (upgrade from 6.x) Message-ID: <47E5449D.40503@FreeBSD.org> In-Reply-To: <d9895e060803221032ofca3505je0cf877beb5411c2@mail.gmail.com> References: <d9895e060803212221g1d0698cbw78f06ef260f68a20@mail.gmail.com> <47E51D4B.5050008@FreeBSD.org> <d9895e060803220914l53b5b413t86ab268d3446fba9@mail.gmail.com> <47E53826.4070503@FreeBSD.org> <d9895e060803221003o858ab58jf0bc3efff8918df8@mail.gmail.com> <47E53E73.1010205@FreeBSD.org> <d9895e060803221032ofca3505je0cf877beb5411c2@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Dmitry RCL Rekman wrote: > Hi, > > On Sat, Mar 22, 2008 at 6:14 PM, Kris Kennaway <kris@freebsd.org > <mailto:kris@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* Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47E5449D.40503>