From owner-freebsd-gnome@FreeBSD.ORG Wed May 5 22:03:47 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 5B8621065670 for ; Wed, 5 May 2010 22:03:47 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id E69788FC0C for ; Wed, 5 May 2010 22:03:46 +0000 (UTC) Received: by wyf23 with SMTP id 23so1232486wyf.13 for ; Wed, 05 May 2010 15:03:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:reply-to:date :message-id:subject:from:to:content-type; bh=qU1RyqnLJEHRqmiRcxp5Aaf7hJPtDiJEHgZDzxJ+jXc=; b=c2BdER0V8yylD/grOYHq5PETCecZL5/YWv/moUkX9pHOSw8J5LephNxvy197VwYLq9 xKU0yiiYwJv6urC0mSOEMAAkC3LPhWJciqW9chuVwABfnoPgpguL5+VMTaamVjQdLLHg ufMk1E2vrhOpGTmrblhtnokxFq6+P7L6auIvw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; b=MHjvZI8+t0zcFG62E6eluBs0OTNos0ddKDyHAQOnz8A+AZgKPMtknFWZqB57SaxeDR Z2xvHHsHscVDwy+2qm2uSt8GnAPKauMRRaBo97ncFDoNXjPqwbPwO4niFspK4cGI+lI2 1sjxfMXDQ4rz/z2Q13bU9xcwBKNmynpAge4e4= MIME-Version: 1.0 Received: by 10.216.88.16 with SMTP id z16mr6755044wee.126.1273097021741; Wed, 05 May 2010 15:03:41 -0700 (PDT) Received: by 10.216.166.71 with HTTP; Wed, 5 May 2010 15:03:41 -0700 (PDT) Date: Wed, 5 May 2010 18:03:41 -0400 Message-ID: From: "b. f." To: freebsd-gnome@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: Re: Grandfather dependencies completely out of control X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bf1783@gmail.com List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 May 2010 22:03:47 -0000 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 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.