public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrew D Kirch <trelane@trelane.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] http://bugs.gentoo.org/show_bug.cgi?id=232084
Date: Tue, 24 Feb 2009 00:57:25 -0500	[thread overview]
Message-ID: <49A38C45.5080301@trelane.net> (raw)

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.




             reply	other threads:[~2009-02-24  5:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-24  5:57 Andrew D Kirch [this message]
2009-02-24  7:27 ` [gentoo-dev] http://bugs.gentoo.org/show_bug.cgi?id=232084 Mike Frysinger
2009-02-26  7:04 ` Caleb Cushing

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49A38C45.5080301@trelane.net \
    --to=trelane@trelane.net \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox