From owner-freebsd-ports@FreeBSD.ORG Fri Oct 10 05:24:34 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 5556016A4C0; Fri, 10 Oct 2003 05:24:34 -0700 (PDT) Received: from mx2.fillmore-labs.com (lima.fillmore-labs.com [62.138.193.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3E7443F93; Fri, 10 Oct 2003 05:24:32 -0700 (PDT) (envelope-from eikemeier@fillmore-labs.com) Received: from pd951aee5.dip.t-dialin.net ([217.81.174.229] helo=fillmore-labs.com ident=tf0kfs5iqsff5es1) by mx2.fillmore-labs.com with asmtp (TLSv1:AES256-SHA:256) (Exim 4.24; FreeBSD 4.9) id 1A7wJq-000Ojh-DB; Fri, 10 Oct 2003 14:24:30 +0200 Message-ID: <3F86A4FB.7060508@fillmore-labs.com> Date: Fri, 10 Oct 2003 14:24:27 +0200 From: Oliver Eikemeier MIME-Version: 1.0 To: Michael Nottebrock References: <22159707417.20031010130423@serebryakov.spb.ru> <3F868513.4030607@gmx.net> In-Reply-To: <3F868513.4030607@gmx.net> 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 12:24:34 -0000 Michael Nottebrock wrote: > Lev Serebryakov wrote: > >> Hello ports, >> >> 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. > > AFAIK libiberty is actually indeed forked across all those projects and > CONFLICTS would be correct. It all usually works out, but there's no > guarantee... The conflicting files are only sample files, listing all files for all ports would make the list too complex. Conflicting files include: devel/*-binutils include/ansidecl.h include/bfd.h include/bfdlink.h lib/libbfd.a lib/libbfd.la lib/libiberty.a lib/libopcodes.a lib/libopcodes.la devel/*-gcc: bin/cpp bin/gcov lib/libiberty.a and I would be surprised if I install devel/m6811-gcc to play around a bit, deinstall it because I don't use it any longer and devel/mingw32-gcc stops working. The same is true for include/ansidecl.h... If I were willing to accept this I could install the ports with DISABLE_CONFLICTS=yes