From owner-freebsd-ports@FreeBSD.ORG Mon Jan 17 14:01:14 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D66A16A4CE for ; Mon, 17 Jan 2005 14:01:14 +0000 (GMT) Received: from main.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id B206A43D2D for ; Mon, 17 Jan 2005 14:01:13 +0000 (GMT) (envelope-from freebsd-ports@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1CqXRQ-0000Iq-00 for ; Mon, 17 Jan 2005 15:01:12 +0100 Received: from kvip88.kvi.nl ([129.125.15.152]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 17 Jan 2005 15:01:12 +0100 Received: from A.S.Usov by kvip88.kvi.nl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 17 Jan 2005 15:01:12 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-ports@freebsd.org From: "Alexander S. Usov" Date: Mon, 17 Jan 2005 15:00:58 +0100 Organization: KVI Lines: 14 Message-ID: References: <41CAAA60.2080001@freebsd.org> <20041226171434.GA2658@aoi.wolfpond.org> <41E532C6.20703@freebsd.org> <20050112203810.GA1892@aoi.wolfpond.org> <41E76E5E.1050804@gmx.net> <20050115164238.GA38678@aoi.wolfpond.org> <41E98914.7000106@gmx.net> <41EA977F.2010707@freebsd.org> <41EB80BB.30007@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: kvip88.kvi.nl User-Agent: KNode/0.8.2 Sender: news Subject: Re: Digikam broken? Mutex lock failure X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 14:01:14 -0000 Mark Ovens wrote: > Thanks Alexander. The PR is > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/74899 which includes a > workround (manually copy the files) Does anybody knows if there are some plans on correcting this? I can try to write some workaround for this specific port and submit it, but it would be better if somebody with a knowledge of libtool ports magic implemented a knob for this. -- Best regards, Alexander.