Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 98931 - avidemux-2.0.24 fails to compile because of bogus filter-flags line
Summary: avidemux-2.0.24 fails to compile because of bogus filter-flags line
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Media-video project
URL:
Whiteboard:
Keywords:
: 101451 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-07-13 16:00 UTC by Joerg Schaible
Modified: 2005-08-05 09:52 UTC (History)
1 user (show)

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 Joerg Schaible 2005-07-13 16:00:56 UTC
I have the CXXFLAG -fno-default-inline set, that breaks the avidemux ebuild. 
This should not happen, since the flag is filtered in the ebuild, but it is 
present on the printed command lines calling the compiler. Using the 
filter-flags command for one flag only in the ebuild (as it is done in all 
other avidemux ebuilds), will really filter the flag. 

Reproducible: Always
Steps to Reproduce:
1. CXXFLAGS=-fno-default-inline emerge =avidemux-2.0.24 
 
Actual Results:  
Linker fails with undefined references. 

Expected Results:  
 

I suppose the real reason for the ignored filter-flags is the two line 
argument in the original ebuild.
Comment 1 Diego Elio Pettenò (RETIRED) gentoo-dev 2005-07-14 01:58:05 UTC
Please try with 2.0.40, it's the one going to be the next stable probably. 
 
Comment 2 Joerg Schaible 2005-07-14 10:31:03 UTC
Dependend faad2-2.0 is masked. ;-) 
Comment 3 Diego Elio Pettenò (RETIRED) gentoo-dev 2005-08-04 10:38:40 UTC
As soon as faad2 is going to stable this will go to stable, i refrain from 
changing a stable ebuild right now, as the filtered flags are unsafe. 
 
Comment 4 Diego Elio Pettenò (RETIRED) gentoo-dev 2005-08-05 09:52:55 UTC
*** Bug 101451 has been marked as a duplicate of this bug. ***