Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 346615 - flag-o-matic.eclass add -fgnu89-inline to ALLOWED_FLAGS
Summary: flag-o-matic.eclass add -fgnu89-inline to ALLOWED_FLAGS
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Toolchain Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 289757
  Show dependency tree
 
Reported: 2010-11-24 08:37 UTC by Kacper Kowalik (Xarthisius) (RETIRED)
Modified: 2010-11-26 10:30 UTC (History)
0 users

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


Attachments
add -fgnu89-inline to ALLOWED_FLAGS (flag-o-matic.eclass.patch,305 bytes, patch)
2010-11-24 08:37 UTC, Kacper Kowalik (Xarthisius) (RETIRED)
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Kacper Kowalik (Xarthisius) (RETIRED) gentoo-dev 2010-11-24 08:37:23 UTC
Multiple packages fail without it on Prefix (gcc in particular)
Comment 1 Kacper Kowalik (Xarthisius) (RETIRED) gentoo-dev 2010-11-24 08:37:54 UTC
Created attachment 255285 [details, diff]
add -fgnu89-inline to ALLOWED_FLAGS
Comment 2 SpanKY gentoo-dev 2010-11-24 08:53:43 UTC
err, what ?  -fgnu89-inline isnt a flag that should be managed by users and blindly thrown into make.conf' CFLAGS.  this is something that packages themselves should be managing.
Comment 3 Kacper Kowalik (Xarthisius) (RETIRED) gentoo-dev 2010-11-24 10:31:28 UTC
(In reply to comment #2)
> err, what ?  -fgnu89-inline isnt a flag that should be managed by users and
> blindly thrown into make.conf' CFLAGS.  this is something that packages
> themselves should be managing.
OK that was "lazy" approach. 
Alternative: Maybe allow that in toolchain.eclass:gcc_do_filter_flags. Something like use custom-cflags || strip-flags and big warning "don't come whining without patches" ?
Comment 4 SpanKY gentoo-dev 2010-11-24 21:33:10 UTC
yeah, i dont think that's worth the hassle.  especially considering the use case you're bringing to justify it.