Date: Sat, 22 Mar 2008 17:14:00 +0100 From: "Dmitry RCL Rekman" <dmitry.rekman@gmail.com> To: "Kris Kennaway" <kris@freebsd.org> Cc: freebsd-questions@freebsd.org Subject: Re: "Mutex unlock failure" when compiling KDE (upgrade from 6.x) Message-ID: <d9895e060803220914l53b5b413t86ab268d3446fba9@mail.gmail.com> In-Reply-To: <47E51D4B.5050008@FreeBSD.org> References: <d9895e060803212221g1d0698cbw78f06ef260f68a20@mail.gmail.com> <47E51D4B.5050008@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Sat, Mar 22, 2008 at 3:52 PM, Kris Kennaway <kris@freebsd.org> wrote: > RCL wrote: > > Hi, > > > > I'm having the same troubles as Leslie Jensen when compiling KDE (or > > anything that uses uic, e.g. amarok): > > compile process stucks with the following message: > > > > Mutex unlock failure: Operation not permitted > > > > I found out that the problem was already being investigated here on > > the list, but no solution has yet been proposed :( > > If it helps, I performed the steps that Mel asked to perform and > > here's the log file of Qt build process: > > > > http://rcl.mine.nu/outbound/freebsd/qt-copy-3.3.8_6.log.tar.gz > > > > The actual command that is used to link uic is: > > c++ -fno-exceptions -Wl,-rpath,/usr/local/lib > > -Wl,-rpath,/usr/local/lib -pthread -o ../../../bin/uic > > .obj/release-shared-mt/main. > > o .obj/release-shared-mt/uic.o .obj/release-shared-mt/form.o > > .obj/release-shared-mt/object.o .obj/release-shared-mt/subclassing > > .o .obj/release-shared-mt/embed.o > > .obj/release-shared-mt/widgetdatabase.o > > .obj/release-shared-mt/domtool.o .obj/release-shared- > > mt/parser.o -L/usr/local/lib > > -L/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/lib > > -L/usr/local/lib -lqt-mt -lmng -ljpeg -lp > > ng -lz -lXi -lXrender -lXrandr -lXcursor -lXinerama -lXft -lfreetype > > -lfontconfig -lXext -lX11 -lm -lSM -lICE > > > > There's no file libpthread.* in /usr/local/lib. These are > > libpthread.so/a files I have: > > > > # ls -la `locate libpthread.{a,so}` > > lrwxrwxrwx 1 root wheel 19 Feb 29 13:57 > > /usr/compat/linux/lib/libpthread.so.0 -> libpthread-2.3.6.so > > lrwxrwxrwx 1 root wheel 18 Feb 29 13:57 > > /usr/compat/linux/lib/obsolete/linuxthreads/libpthread.so.0 -> > > libpthread-0.10.so > > lrwxr-xr-x 1 root wheel 8 Feb 29 12:21 /usr/lib/libpthread.a -> > libthr.a > > -r--r--r-- 1 root wheel 136020 Feb 29 16:16 > > /usr/local/lib/compat/libpthread.so.1 > > -r-xr-xr-x 1 root wheel 43284 Oct 17 00:52 > > /usr/local/lib/valgrind/libpthread.so > > lrwxr-xr-x 1 root wheel 13 Oct 17 00:52 > > /usr/local/lib/valgrind/libpthread.so.2 -> libpthread.so > > > > I upgraded the system nearly a month ago (On 29th Feb) and since then > > I cannot build any KDE application (not even rebuild kde base/lib > > ports themselves). > > Upgrade procedure I used is described here: > > > http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.html > > > > I hope the information provided will help further investigate the > > problem. I don't want to reinstall the system, that feels like a > > solution from Windows world :-) > > Are you certain that your portupgrade -af completed successfully after > you upgraded the base OS? If this was not completed it will cause > problems along these lines. > Well, it actually did not rebuild the KDE & friends (because of aforementioned problem with unlocking the mutex), so I had to interrupt that, leaving some ports alone. I admit that is a deviation from upgrade procedure, but it is not perhaps the reason of mutex problem, because it appeared while rebuilding the ports for the first time. > Kris > Best regards, Dmitry RCL Rekman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d9895e060803220914l53b5b413t86ab268d3446fba9>