Summary: | avidemux-2.0.24: ebuild filtering of -fPIC | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | John Gill <jdgill0> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
John Gill
2005-04-18 09:55:45 UTC
We can't filter all and every problematic flag someone can choose. You should know what you do. So, if someone finds a USE flag that out right causes said package to fail compiling, then it should not be reported? I wasn't asking, nor would I expect, the ebuild maintainer to verify all USE flags for an ebuild, but instead thought that since I ran into this problem and it seemed very clear that avidemux does not like -fPIC, that reporting the problem might be of value. [quote]You should know what you do.[/quote] Then why have the "filter" functionality in ebuilds period? The avidemux ebuild already has: filter-flags "-fno-default-inline -funroll-loops -funroll-all-loops \ -maltivec -mabi=altivec" Anyways, I am not looking to argue about this. I was only trying to help, not demand more from the maintainers/developers. |