From owner-freebsd-questions@FreeBSD.ORG Sat Mar 22 17:03:48 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF8C0106564A for ; Sat, 22 Mar 2008 17:03:48 +0000 (UTC) (envelope-from dmitry.rekman@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.240]) by mx1.freebsd.org (Postfix) with ESMTP id 6F09F8FC1D for ; Sat, 22 Mar 2008 17:03:48 +0000 (UTC) (envelope-from dmitry.rekman@gmail.com) Received: by an-out-0708.google.com with SMTP id c14so676633anc.13 for ; Sat, 22 Mar 2008 10:03:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=V2ebj3CyUy90cX6lQeFSt4FtxjIzuELylI3jQiiVAKU=; b=s9LQ5O/Q9zybHPfnptAEK1j+2XlJ1VbHEjmL0gxqqRVDlb4jBggZkY7XQsM/1CozdcB0lt19Ri6DPGzYZ+IoIS0JlJiXBhj1L7m9pmwp3uBa89aU+sXbeUtvIaJwzMuW6sLkJ2nbyQ5366NCmddj3gzRRT1Cm/ue3ASKwVS+kp8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=hb8VIP9N12mn3jDqPY7k9KpHMdT7xFHE0GWcTphBMyWoj9wdgeqKjp+5kz7zufjJ8ndWsj860wdl6wC0gKP5GtrI3JIVFDswWzD0gMuD/Sfx97UVNTwjwAuneauwbZJq7hDkq6VVLwUJQRcFO6yybABeRIfLss2eeXgI8r9FpzQ= Received: by 10.100.14.2 with SMTP id 2mr12641076ann.16.1206205427763; Sat, 22 Mar 2008 10:03:47 -0700 (PDT) Received: by 10.101.67.17 with HTTP; Sat, 22 Mar 2008 10:03:47 -0700 (PDT) Message-ID: Date: Sat, 22 Mar 2008 18:03:47 +0100 From: "Dmitry RCL Rekman" To: freebsd-questions@freebsd.org In-Reply-To: <47E53826.4070503@FreeBSD.org> MIME-Version: 1.0 References: <47E51D4B.5050008@FreeBSD.org> <47E53826.4070503@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: "Mutex unlock failure" when compiling KDE (upgrade from 6.x) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Mar 2008 17:03:48 -0000 Hi, On Sat, Mar 22, 2008 at 5:47 PM, Kris Kennaway wrote: > Dmitry RCL Rekman wrote: > > Hi, > > > > On Sat, Mar 22, 2008 at 3:52 PM, Kris Kennaway 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 > > > 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. > > There is no reference in your log file to "Mutex unlock failure". > It does not appear when building Qt, but when building e.g. kdebase3 (when uic is used). 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. 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. Log of the actual "mutex unlock failure" error was already posted in this list, it's here: http://docs.freebsd.org/cgi/mid.cgi?47D8DBC0.3010106 > > Kris > Best regards, Dmitry RCL Rekman