From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1GaUdT-0006pz-13 for garchives@archives.gentoo.org; Thu, 19 Oct 2006 09:56:23 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k9J9sYlJ017418; Thu, 19 Oct 2006 09:54:34 GMT Received: from windmuehlgasse.getdesigned.at (chello062178000135.1.11.univie.teleweb.at [62.178.0.135]) by robin.gentoo.org (8.13.8/8.13.6) with ESMTP id k9J9sXOH031612 for ; Thu, 19 Oct 2006 09:54:33 GMT Received: (qmail 25586 invoked from network); 19 Oct 2006 13:20:39 +0200 Received: from watson64.local (HELO ?192.168.1.5?) (192.168.1.5) by tuxserver.local with SMTP; 19 Oct 2006 13:20:39 +0200 Message-ID: <45374B67.6010901@getdesigned.at> Date: Thu, 19 Oct 2006 11:54:47 +0200 From: Sebastian Redl User-Agent: Thunderbird 1.5.0.7 (X11/20061009) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org MIME-Version: 1.0 To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] Re: -fPIC - Toolchain broken? References: <45364363.3010601@getdesigned.at> In-Reply-To: X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: f9047820-b9fe-4e11-8560-a75863969682 X-Archives-Hash: c755ff0216c2fdb37a0302bd96176c8c Duncan wrote: > So... anytime I see this error, the first thing I try is flipping some > CFLAGS on and off, and see if there's a reasonable combination that works. > Only if that fails do I try -fPIC and bug it as necessary. > But wouldn't that apply only to errors that occur during the configuration step? Or have you observed a situation where a compilation change triggered by a failing non-essential test caused an error later? > -fPIC is an interesting beast. It's required on amd64 for all shared > objects (*.so*), but isn't recommended (except for hardened) for > application binaries, both due to occasional unexpected complications and > because it's slower. Thus, putting it in CFLAGS is NOT a good thing, > unless it's for a specific library package only, to get it to merge while > you are waiting for the bug you filed on it (right?) to get > researched/fixed/tested. > Speaking of which, is there any way to configure flags per package? Something like /etc/portage/package.flags, where I can configure CFLAGS, CXXFLAGS and LDFLAGS? Sebastian Redl -- gentoo-amd64@gentoo.org mailing list