Date: Mon, 15 Mar 2004 18:21:22 -0600 (CST) From: Mike Silbersack <silby@silby.com> To: Daniel Eischen <eischen@vigrid.com> Cc: threads@freebsd.org Subject: Re: Mutex unlock failure: ? Message-ID: <20040315182024.U89848@odysseus.silby.com> In-Reply-To: <20040314223946.R81769@odysseus.silby.com> References: <Pine.GSO.4.10.10403142335020.12209-100000@pcnet5.pcnet.com> <20040314223946.R81769@odysseus.silby.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ugh, it's probably all OK, I'll report back if there is still a problem. My libmap still contained this: libc_r.so.5 libkse.so.1 libc_r.so libkse.so Which, of course, means that I was using old libraries... Sorry, Mike "Silby" Silbersack On Sun, 14 Mar 2004, Mike Silbersack wrote: > > On Sun, 14 Mar 2004, Daniel Eischen wrote: > > > > Hrm, looks like uic is part of qt, not X11. So that rules out libc_r > > > interference. > > > > > > Can someone else try building kdepim with libpthread and see what happens? > > > > I built kdepim-3.2.0_1 a week or two ago and it built fine (libc_r -> > > libpthread). > > > > -- > > Dan Eischen > > That was last week. :) > > We're now up to qt 3.3 and kdepim 3.2.1. I had no problems with kde 3.2.0 > either. :( > > I tried a different kde port, and that failed to build in the exact same > way; there must be a bug or incompatibility in qt 3.3's uic. > > Mike "Silby" Silbersack >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040315182024.U89848>