Date: Fri, 10 Oct 2003 16:28:42 +0400 From: Lev Serebryakov <lev@serebryakov.spb.ru> To: Michael Nottebrock <michaelnottebrock@gmx.net> Cc: Lev Serebryakov <lev@FreeBSD.org> Subject: Re[2]: Ports conflicts: `lib/libiberty.a' Message-ID: <179171965963.20031010162842@serebryakov.spb.ru> In-Reply-To: <3F868513.4030607@gmx.net> References: <22159707417.20031010130423@serebryakov.spb.ru> <3F868513.4030607@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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! 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. -- Best regards, Lev mailto:lev@serebryakov.spb.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?179171965963.20031010162842>