Summary: | media-video/avidemux-2.4_pre3 needs ssse3 use flag | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Honza <hkmaly> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Honza
2007-12-01 23:02:24 UTC
Try with a decent compiler... http://www.gentoo.org/doc/en/gcc-upgrading.xml This error has nothing to do with gcc. This error has even nothing to do with binutils (after upgrading binutils to sys-devel/binutils-2.18-r1, the error is of course gone and the compilation failed at later point, which I'm going investigate tomorow and fill other bug). This error is about the fact that AMD Athlon(tm) 64 physically DOESN'T HAVE SSSE3 and the HAND-OPTIMIZED INLINE ASSEMBLER FUNCTION which compilation produced that error CAN'T WORK on it. On the other hand, there is some autodetection around this part of code, so it IS possible it will work anyway (the problematic function will not be called and sse2 variant will be chosen instead). So, please do not close this bug unless you can confirm the application can encode to mpeg1 and mpeg2 on cpu without ssse3. In that case, you can solve this bug by adding "sys-devel/binutils new enough" to dependencies. Eh ... the "This error" should be "This bug" on beginning of all sentences of first paragraf in last comment ... binutils-2.18-r1.ebuild:KEYWORDS="alpha amd64 ~arm hppa ia64 mips ppc ppc64 ~s390 ~sh sparc x86" So, use at least stable binutils, or up. I don't see any problem here, and don't feel comfortable sticking system -depends into ebuild to avoid problems on outdated systems. As said, your toolchain is unsupported. Samuel: The relevant keyword line is binutils-2.16.1-r3.ebuild: KEYWORDS="-* alpha amd64 arm hppa ia64 m68k mips ppc ppc64 s390 sh sparc x86 ~x86-fbsd" (meaning 2.16.1-r3 is no longer considered stable), keywords of 2.18-r1 are irrelevant to your point. Still, unless portage warns about obsolete toolchain, it's not much friendly to common user ... and most ebuilds will compile fine even with binutils-2.16.1-r3. Which of you can confirm the application can encode to mpeg1 and mpeg2 on cpu without ssse3 ? Or should I wait to see what type of error it produces and then fill another bugreport ? |