Date: Sat, 11 Oct 2003 00:39:19 +0400 From: Lev Serebryakov <lev@FreeBSD.org> To: Oliver Eikemeier <eikemeier@fillmore-labs.com> Cc: ports@FreeBSD.org Subject: Re[2]: Ports conflicts: `lib/libiberty.a' Message-ID: <76414324.20031011003919@serebryakov.spb.ru> In-Reply-To: <3F86B072.5000305@fillmore-labs.com> References: <22159707417.20031010130423@serebryakov.spb.ru> <3F868513.4030607@gmx.net> <3F86A4FB.7060508@fillmore-labs.com> <150173441255.20031010165317@serebryakov.spb.ru> <3F86B072.5000305@fillmore-labs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Oliver!
Friday, October 10, 2003, 5:13:22 PM, you wrote:
>> OE> devel/*-binutils
>> OE> include/ansidecl.h
>> OE> include/bfd.h
>> OE> include/bfdlink.h
>> OE> lib/libbfd.a
>> OE> lib/libbfd.la
>> OE> lib/libiberty.a
>> OE> lib/libopcodes.a
>> OE> lib/libopcodes.la
>> This is not a problem. Really, they are not used after installation.
OE> They why do you install them in the first place?
Because ports doesn't have custom `make install'. And makefiles from
binutils' authors install these files in case some other util could
want to use them for standard disassemble operations, for example.
But I don't know such utils. We have problem like this with `*.la'
files from libtool. And we have special option for ports system to
fix makefiles after libtool to disable `*.la' installation (it
doesn't work in some cases, but works in MOST cases).
I don't know how to properly prevent installation of these files
except creating personal patch for every binutils port.
>> OE> devel/*-gcc:
>> OE> bin/cpp
>> OE> bin/gcov
>> It is a problem, of course, but proper ports installs
>> bin/%%TARGET%%-cpp and bin/%%TARGET%%-gcov. mingw32-gcc & msp430-gcc
>> does exactly this.
OE> So we have some non-proper ports?
Like so. Any modern versions of binutils & gcc adds target prefix for
these files.
Lev Serebryakov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?76414324.20031011003919>