Date: Fri, 10 Oct 2003 14:24:27 +0200 From: Oliver Eikemeier <eikemeier@fillmore-labs.com> To: Michael Nottebrock <michaelnottebrock@gmx.net> Cc: Lev Serebryakov <lev@FreeBSD.org> Subject: Re: Ports conflicts: `lib/libiberty.a' Message-ID: <3F86A4FB.7060508@fillmore-labs.com> 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
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F86A4FB.7060508>