public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-dev] http://bugs.gentoo.org/show_bug.cgi?id=232084
@ 2009-02-24  5:57 Andrew D Kirch
  2009-02-24  7:27 ` Mike Frysinger
  2009-02-26  7:04 ` Caleb Cushing
  0 siblings, 2 replies; 3+ messages in thread
From: Andrew D Kirch @ 2009-02-24  5:57 UTC (permalink / raw
  To: gentoo-dev

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.




^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [gentoo-dev] http://bugs.gentoo.org/show_bug.cgi?id=232084
  2009-02-24  5:57 [gentoo-dev] http://bugs.gentoo.org/show_bug.cgi?id=232084 Andrew D Kirch
@ 2009-02-24  7:27 ` Mike Frysinger
  2009-02-26  7:04 ` Caleb Cushing
  1 sibling, 0 replies; 3+ messages in thread
From: Mike Frysinger @ 2009-02-24  7:27 UTC (permalink / raw
  To: gentoo-dev; +Cc: Andrew D Kirch

[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]

On Tuesday 24 February 2009 00:57:25 Andrew D Kirch wrote:
> 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.

it's broken whenever fortify source is used, but gcc-4.3.3 is more of an issue 
because it's on by default.  however, this flag should not go in any dhcdbd 
ebuild considering the fix posted by Magnus to that bug is clearly correct.

> 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

i'll just address style/usage issues here rather than "is this change even 
correct" ...

-eq is for numeric values, not strings.  so you'd want:
[[ $(gcc-fullversion) == "4.3.3" ]] && append-cppflags -U_FORTIFY_SOURCE
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [gentoo-dev] http://bugs.gentoo.org/show_bug.cgi?id=232084
  2009-02-24  5:57 [gentoo-dev] http://bugs.gentoo.org/show_bug.cgi?id=232084 Andrew D Kirch
  2009-02-24  7:27 ` Mike Frysinger
@ 2009-02-26  7:04 ` Caleb Cushing
  1 sibling, 0 replies; 3+ messages in thread
From: Caleb Cushing @ 2009-02-26  7:04 UTC (permalink / raw
  To: gentoo-dev

fyi my email client doesn't recognize urls in the subject line, don't
know about anyone elses... but it'd be nice to click the link to the
bug, and you know have some clue what this is about without reading
the bug (e.g. a useful subject line). </endrant> sorry I can't be of
any further help here.

On Tue, Feb 24, 2009 at 12:57 AM, Andrew D Kirch <trelane@trelane.net> wrote:
> Thanks for the help.



-- 
Caleb Cushing

http://xenoterracide.blogspot.com



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2009-02-26  7:04 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-02-24  5:57 [gentoo-dev] http://bugs.gentoo.org/show_bug.cgi?id=232084 Andrew D Kirch
2009-02-24  7:27 ` Mike Frysinger
2009-02-26  7:04 ` Caleb Cushing

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox