Summary: | avidemux will not build, ADM_interlaced.cpp -> {standard input}:133: Error: symbol `admlloopp' is already defined | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Stefan Andersen <spamfilter> |
Component: | Current packages | Assignee: | Martin Holzer (RETIRED) <mholzer> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | zypher |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Stefan Andersen
2003-07-17 02:36:39 UTC
Hi! I'll try to reproduce that when I return from work. In the meantime please try to reduce your CFLAGS a bit (just guessing). Thanks for the report, Marc. avidemux-2.0.10-r1 is now in portage with lots of ebuild changes. Please test. Yepp, works fine here. The thing is, I build it (as my whole system) with: CFLAGS="-march=athlon-xp -Os -pipe -mfpmath=sse -mmmx -msse -m3dnow" Maybe we could here a word from some of the excessive-cflags-users? I still have the same problem (its my CFLAGS That are reported in the bugreport) Stefan: When I use your CFLAGS I get the same error. It work with: CFLAGS="-O3 -march=athlon-xp -pipe -fomit-frame-pointer -falign-functions=4" Just try to use these flags and post the results here. It now works, using your CFLAGS CFLAGS="-O3 -march=athlon-xp -pipe -fomit-frame-pointer -falign-functions=4" fixed I got this problem again when the package was upgraded (I only temorary changed my CFLAGS) So I did a little investigation of what flag got me the problem My orginal flags lookad like CFLAGS="-O3 -march=pentium3 -pipe -fomit-frame-pointer -funroll-loops -fforce-addr -frerun-cse-after-loop -frerun-loop-opt -falign-functions=4 " And -funroll-loops seems to cause me the problem, Since CFLAGS="-O3 -march=pentium3 -pipe -fomit-frame-pointer -fforce-addr -frerun-cse-after-loop -frerun-loop-opt -falign-functions=4 " workd. I will remove this flag from my CFLAGS for all builds, but I don't know if this is something that can/should be blocked in the ebuild for this product to avoid this problem from other setup's. see bug #26936 |