From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1LbqIP-0007EX-CO for garchives@archives.gentoo.org; Tue, 24 Feb 2009 05:57:33 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2C5DEE030E; Tue, 24 Feb 2009 05:57:32 +0000 (UTC) Received: from mail.trelane.net (mail.trelane.net [66.93.203.104]) by pigeon.gentoo.org (Postfix) with ESMTP id 0D4C1E030E for ; Tue, 24 Feb 2009 05:57:32 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.trelane.net (Postfix) with ESMTP id 99FE5186648 for ; Tue, 24 Feb 2009 00:57:24 -0500 (EST) X-Virus-Scanned: amavisd-new at trelane.net Received: from mail.trelane.net ([127.0.0.1]) by localhost (master.trelane.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kPHx4ZX8k8Po for ; Tue, 24 Feb 2009 00:57:23 -0500 (EST) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.trelane.net (Postfix) with ESMTP id E135A186677 for ; Tue, 24 Feb 2009 00:57:22 -0500 (EST) Received: from [172.16.1.99] (router.trelane.net [66.93.203.152]) by mail.trelane.net (Postfix) with ESMTP id A0F0E186648 for ; Tue, 24 Feb 2009 00:57:22 -0500 (EST) Message-ID: <49A38C45.5080301@trelane.net> Date: Tue, 24 Feb 2009 00:57:25 -0500 From: Andrew D Kirch User-Agent: Thunderbird 2.0.0.19 (X11/20090112) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: [gentoo-dev] http://bugs.gentoo.org/show_bug.cgi?id=232084 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: f80a68ce-1bcb-42b1-b086-fff3e3374e6b X-Archives-Hash: 5ae9dd36297d7f103d302aa3b981d002 I was looking to do a workaround on a per compiler basis. I'm looking at toolchain-funcs.eclass, and specifically ${gcc-fullversion}. I've got a broken ebuild (dhcdbd) which requires -U_FORTIFY_SOURCE to compile correctly with GCC 4.3.3. But reading tells me that I should not use this eclass to set compiler settings directly. Will this work, and other than the merit of the fix is there a more desirable structure for such a solution? inherit flag-o-matic toolchain-funcs if [ "${gcc-fullversion}" -eq "4.3.3" ] #(or whatever the 4.3.3 $gcc-fullversion} outputs) then append-flags -U_FORTIFY_SOURCE fi Thanks for the help.