The useflags are disabled on AMD64, so it'd probably be useful if the build could detect the arch and enable them. When I run mplayer I see: MMX supported but disabled MMX2 supported but disabled 3DNow supported but disabled 3DNowExt supported but disabled :(
I'd like to add that I did change the ebuild, compiled mplayer, and it works just fine. It now only says that: Cannot test OS support for SSE, disabling to be safe.
Georgi, could you please attach your change ebuild? Thanks, Roland
Created attachment 47595 [details, diff] mplayer-1.0_pre6.patch Here is the patch for the ebuild. Some of the lines I didn't indent in order to keep the changes as little as possible.
Well, if it's "disabling to be safe" I don't think the changed ebuild matters too much, perhaps someone should hack at mplayer? Should I report upstream?
also: For the ebuild to be valid you'll want to add amd64 to IUSE.
Re: comment #4 You only refer to the SSE support in your message. However, the changed ebuild seems to remove the warnings about mmx, mmx2, 3dnow and 3dnowext. That's a plus by itself I think. Re: comment #5 I didn't know that the keyword-specific use flags need to be added to IUSE. After all, there is "if use ppc64", "use sparc &&" inside the ebuild already, and these are not mentioned in IUSE. Plus, my patch adds an "use amd64" and an "use x86" check to the ebuild (point being, you didn't mention x86).
This stuff was added on Jan 11th: # mplayer now contains SIMD assembler code for amd64 # AMD64 Team decided to hardenable SIMD assembler for all users # Danny van Dyk <kugelfang@gentoo.org> 2005/01/11 if use amd64; then myconf="${myconf} --enable-3dnow --enable-3dnowex --enable-sse --enable- mmx --enable-mmx2" fi so this bug may as well be closed.
And so it is..