Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 442784 - =sys-libs/libstdc++-v3-3.3.6 fails at configure due to unrecognized gcc option
Summary: =sys-libs/libstdc++-v3-3.3.6 fails at configure due to unrecognized gcc option
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: Normal enhancement (vote)
Assignee: Gentoo Toolchain Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-11 17:13 UTC by Vicente Olivert Riera (RETIRED)
Modified: 2013-04-10 18:26 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vicente Olivert Riera (RETIRED) gentoo-dev 2012-11-11 17:13:00 UTC
I was trying to install =sys-libs/libstdc++-v3-3.3.6 and it failed because I was using a gcc option not available for gcc-3.3.6. This option is very common because it's used to check if CFLAGS and CXXFLAGS are mixed: https://bugs.gentoo.org/show_bug.cgi?id=234011#c0

I'm talking about "-Wno-pointer-sign"

Adding "filter-flags -Wno-pointer-sign" in the ebuild fixes the problem.

I'm not sure, but I think that option was added to gcc in the version 4.0: http://gcc.gnu.org/ml/gcc-patches/2005-01/msg00505.html

Maybe it would be a good idea to collect what options has been added after 3.3.6 and filter all of them. Or maybe not..., you choose :-P
Comment 1 Vicente Olivert Riera (RETIRED) gentoo-dev 2013-04-05 10:42:20 UTC
In 30 days I will add "filter-flags -Wno-pointer-sign" to the ebuild and I will close this bug, if you don't have any objection.
Comment 2 Ryan Hill (RETIRED) gentoo-dev 2013-04-06 21:02:02 UTC
I don't know about "very common", but go ahead.
Comment 3 Vicente Olivert Riera (RETIRED) gentoo-dev 2013-04-07 00:24:35 UTC
(In reply to comment #2)
> I don't know about "very common", but go ahead.

Done.
Comment 4 SpanKY gentoo-dev 2013-04-10 18:23:51 UTC
(In reply to comment #2)

yeah, it's not common at all.  you also only updated libstdc++-v3-3.3.6.ebuild which isn't the latest.

i dropped your change and updated it to filter all -W flags.  none of them really make sense with this.