MPlayer pre7 got released, the path to the 1.0 final is still long and windy.
There is an ebuild p.masked for it. Hopefully I’ll test it a bit in the next days, it will be ~arch within the week, I hope.
MPlayer pre7 got released, the path to the 1.0 final is still long and windy.
There is an ebuild p.masked for it. Hopefully I’ll test it a bit in the next days, it will be ~arch within the week, I hope.
well, I’d like to see removed the custom CFLAGS/CPU_FLAGS section. It invalidates bug reports to upstream developers, and it is useless, because mplayer detects what it needs and its CFLAGS are more extreme than CFLAGS a normal user could set (by default it uses -O4)
maybe it is a good thing for cross-compiling, but not in a standard installation
As you can see in the ebuild you have a new useflag that triggers the custom cflags =)
good! just tested hard-masked pre7, it needs a little modification:
— mplayer-1.0_pre7.ebuild 2005-04-17 16:37:56.000000000 +0200
+++ mplayer-1.0_pre7.ebuild 2005-04-18 12:44:01.000000000 +0200
@@ -265,6 +265,8 @@
replace-flags -O3 -O2
filter-flags -fPIC -fPIE
fi
+ else
+ unset CFLAGS CXXFLAGS
fi
btw, it seems to me that patching configure for custom cflags is not needed anymore, cause with USE=”-cpudetection -custom-cflags” without my change my system CFLAGS are still used.
You are right