From owner-freebsd-ports@FreeBSD.ORG Fri Oct 10 13:36:04 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 F414E16A4E4 for ; Fri, 10 Oct 2003 13:36:03 -0700 (PDT) Received: from ftp.translate.ru (ftp.translate.ru [195.131.4.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C78E43F3F for ; Fri, 10 Oct 2003 13:36:00 -0700 (PDT) (envelope-from lev@FreeBSD.org) Received: from ip121-248.dialup.wplus.net (ip121-248.dialup.wplus.net [195.131.121.248]) (authenticated bits=0) by ftp.translate.ru (8.12.9/8.12.9) with ESMTP id h9AKXV7R074702; Sat, 11 Oct 2003 00:33:37 +0400 (MSD) (envelope-from lev@FreeBSD.org) Date: Sat, 11 Oct 2003 00:39:19 +0400 From: Lev Serebryakov X-Mailer: The Bat! (v1.62r) Personal Organization: Home X-Priority: 3 (Normal) Message-ID: <76414324.20031011003919@serebryakov.spb.ru> To: Oliver Eikemeier 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: ports@FreeBSD.org Subject: Re[2]: Ports conflicts: `lib/libiberty.a' X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Lev Serebryakov List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Oct 2003 20:36:04 -0000 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