Date: Fri, 10 Oct 2003 15:16:37 +0200 From: Oliver Eikemeier <eikemeier@fillmore-labs.com> To: Lev Serebryakov <lev@serebryakov.spb.ru> Cc: Lev Serebryakov <lev@FreeBSD.org> Subject: Re: Ports conflicts: `lib/libiberty.a' Message-ID: <3F86B135.5050001@fillmore-labs.com> In-Reply-To: <179171965963.20031010162842@serebryakov.spb.ru> References: <22159707417.20031010130423@serebryakov.spb.ru> <3F868513.4030607@gmx.net> <179171965963.20031010162842@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F86B135.5050001>