From owner-freebsd-ports@FreeBSD.ORG Fri Oct 10 06:16:45 2003 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 0051D16A4B3; Fri, 10 Oct 2003 06:16:45 -0700 (PDT) Received: from mx2.fillmore-labs.com (lima.fillmore-labs.com [62.138.193.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AA6943FAF; Fri, 10 Oct 2003 06:16:43 -0700 (PDT) (envelope-from eikemeier@fillmore-labs.com) Received: from pd951aee5.dip.t-dialin.net ([217.81.174.229] helo=fillmore-labs.com ident=hc6uaoczxuggle7g) by mx2.fillmore-labs.com with asmtp (TLSv1:AES256-SHA:256) (Exim 4.24; FreeBSD 4.9) id 1A7x8J-000OnO-4b; Fri, 10 Oct 2003 15:16:39 +0200 Message-ID: <3F86B135.5050001@fillmore-labs.com> Date: Fri, 10 Oct 2003 15:16:37 +0200 From: Oliver Eikemeier MIME-Version: 1.0 To: Lev Serebryakov References: <22159707417.20031010130423@serebryakov.spb.ru> <3F868513.4030607@gmx.net> <179171965963.20031010162842@serebryakov.spb.ru> In-Reply-To: <179171965963.20031010162842@serebryakov.spb.ru> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-Sender: eikemeier@fillmore-labs.com User-Agent: KMail/1.5.9 Organization: Fillmore Labs GmbH X-Complaints-To: abuse@fillmore-labs.com cc: ports@FreeBSD.org cc: Lev Serebryakov Subject: Re: Ports conflicts: `lib/libiberty.a' 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: Fri, 10 Oct 2003 13:16:45 -0000 Lev Serebryakov wrote: > Hello Michael, > > Friday, October 10, 2003, 2:08:19 PM, you wrote: > > >>> Many my ports have conflicts with other ones. >>> And conflicting file is one: `lib/libiberty.a'. >>> This file is installed by many variants of gvv, binutils & gdb. >>> But I don't think, that this library is ever used after instllation. >>> Each port build it again and again. >>> >>> I don't think, it is good idea to "CONFLICTS=" all these binutils & >>> gcc. > > MN> AFAIK libiberty is actually indeed forked across all those projects and > MN> CONFLICTS would be correct. It all usually works out, but there's no guarantee... > > It is STATIC library! It could not be used by ALREADY compiled & > installed ports! And ALL these ports compile this library by > itself and use OWN version on build stage, and DON'T use installed > library! Then perhaps it shouldn't be installed anyway? > And, If I write CONFLICTS=, based on `lib/libiberty.a', IT WILL BE > IMPOSIIBLE to install cross-binutils & cross-gcc EVENT for one platform > together! It is very strange situation, IMHO. If you don't care, you could install them with DISABLE_CONFLICTS=yes.