From owner-freebsd-threads@FreeBSD.ORG Mon Mar 15 16:21:25 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7995416A4CF for ; Mon, 15 Mar 2004 16:21:25 -0800 (PST) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id F130543D2F for ; Mon, 15 Mar 2004 16:21:24 -0800 (PST) (envelope-from silby@silby.com) Received: (qmail 49473 invoked from network); 16 Mar 2004 00:21:23 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 16 Mar 2004 00:21:23 -0000 X-pair-Authenticated: 209.68.2.70 Date: Mon, 15 Mar 2004 18:21:22 -0600 (CST) From: Mike Silbersack To: Daniel Eischen In-Reply-To: <20040314223946.R81769@odysseus.silby.com> Message-ID: <20040315182024.U89848@odysseus.silby.com> References: <20040314223946.R81769@odysseus.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: threads@freebsd.org Subject: Re: Mutex unlock failure: ? X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Mar 2004 00:21:25 -0000 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 >