From owner-freebsd-gnome@FreeBSD.ORG Thu May 6 03:03:13 2010 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B73A5106566B for ; Thu, 6 May 2010 03:03:13 +0000 (UTC) (envelope-from mezz7@cox.net) Received: from eastrmmtao105.cox.net (eastrmmtao105.cox.net [68.230.240.47]) by mx1.freebsd.org (Postfix) with ESMTP id 5D5668FC13 for ; Thu, 6 May 2010 03:03:12 +0000 (UTC) Received: from eastrmimpo03.cox.net ([68.1.16.126]) by eastrmmtao105.cox.net (InterMail vM.8.00.01.00 201-2244-105-20090324) with ESMTP id <20100506030312.MKWN16574.eastrmmtao105.cox.net@eastrmimpo03.cox.net>; Wed, 5 May 2010 23:03:12 -0400 Received: from localhost ([68.103.37.153]) by eastrmimpo03.cox.net with bizsmtp id E33B1e00C3JFCbG0233CyN; Wed, 05 May 2010 23:03:12 -0400 X-VR-Score: -100.00 X-Authority-Analysis: v=1.1 cv=ATnAe3Z8cB68w/tlXoJHcUhYOhVhDtHgFT5GRCYUfLQ= c=1 sm=1 a=xWfbe-9NfXEA:10 a=IkcTkHD0fZMA:10 a=N4x68aYdfVlkKDflYggXRA==:17 a=mK_AVkanAAAA:8 a=kviXuzpPAAAA:8 a=6I5d2MoRAAAA:8 a=p7vD2IfxiqeXhUgsOhAA:9 a=C5Obzl9ZyreuQQxvy40A:7 a=Cfrj3EqQKCJbt0KAC759Wt_fCuYA:4 a=QEXdDO2ut3YA:10 a=9xyTavCNlvEA:10 a=4vB-4DCPJfMA:10 a=SV7veod9ZcQA:10 a=N4x68aYdfVlkKDflYggXRA==:117 X-CM-Score: 0.00 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: bf1783@gmail.com, freebsd-gnome@freebsd.org References: Date: Wed, 05 May 2010 22:07:47 -0500 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: "Jeremy Messenger" Message-ID: In-Reply-To: User-Agent: Opera Mail/10.10 (Linux) Cc: Subject: Re: Grandfather dependencies completely out of control X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 May 2010 03:03:13 -0000 On Wed, 05 May 2010 17:03:41 -0500, b. f. wrote: > Alexander Leidinger wrote: > ,,, >> Because of the libtool/pkg-config problem all childs of a >> "problematic" lib will contain a reference to the lib, even if the >> particular lib is just a dependency of a lib which the current port >> uses. To make this description more explicit: if your port uses >> libGRAPH (I made upt this name) and libGRAPH is linked to libjpeg and >> libpng via libtool (at least 1.x), but your port is not directly using >> symbols from libjpeg or libpng, the binaries of your port will have >> libpng *and* libjpeg hardcoded. > > Use of > > LDFLAGS+= -Wl,--as-needed > > can help with this problem. But of course a lot of ports don't now See ltasneededhack in ports/Mk/bsd.gnome.mk (ie: USE_GNOME=ltasneededhack), we are using on evolution and a few others to help speed up. The libtool2 was supposed to get rid of *.la files by default, but the developers have changed mind. Too bad for all of us. Cheers, Mezz > respect LDFLAGS (many gnome ports offend in this regard). Because a > lot of people want to use alternative compilers/toolchains for ports, > and because of new gcc features like -flto, -fwhopr, and > -fstack-protector* (the last has been enabled by default in the base > system for some time now, but still cannot be properly used for a > large number of ports which don't respect LDFLAGS), there needs to be > a cleanup to ensure that as many ports as possible respect the > toolchain (ADDR2LINE, AR, AS, CPPFILT, LD, NM, OBJCOPY, OBJDUMP, > RANLIB, READELF, SIZE, STRINGS, STRIP) and compiler-related variables > ( CC, CPP, CXX, CFLAGS, CPPFLAGS, CXXFLAGS, and LDFLAGS). > > b. -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org