After upgrading to -r3 of mplayer-1.0_pre5, I get the following error when trying to play most audio or video files (ogg's work fine) (where the error varies from decode_audio to init_audio_codec) MPlayer interrupted by signal 4 in module: decode_audio - MPlayer crashed by an 'Illegal Instruction'. It usually happens when you run it on a CPU different than the one it was compiled/optimized for. Verify this! - MPlayer crashed by bad usage of CPU/FPU/RAM. Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash. - MPlayer crashed. This shouldn't happen. It can be a bug in the MPlayer code _or_ in your drivers _or_ in your gcc version. If you think it's MPlayer's fault, please read DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and won't help unless you provide this information when reporting a possible bug. After downgrading back to -r2, these issues are now resolved, which means that there is a problem with the latest ebuild. Reproducible: Always Steps to Reproduce: 1. emerge mplayer-1.0_pre5-r3.ebuild 2. 3.
Please post your emerge --info and USE flags for MPlayer. Re-open the bug once this is posted.
Portage 2.0.50-r9 (default-x86-2004.0, gcc-3.3.4, glibc-2.3.4.20040808-r0, 2.6.8-gentoo-r1) ================================================================= System uname: 2.6.8-gentoo-r1 i686 Intel(R) Pentium(R) 4 CPU 2.53GHz Gentoo Base System version 1.5.3 distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=pentium4 -O3 -pipe -fomit-frame-pointer -funroll-loops" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3.3/share/config:/usr/kde/3.3/env:/usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mcpu=i686 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://mirror.datapipe.net/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="3dnow X aalib apache2 apm arts avi berkdb cdr crypt cups encode esd foomaticdb gdbm gif gnome gphoto2 gpm gtk gtk2 imlib java jpeg ldap libg++ libwww mad mikmod mmx motif mozilla mpeg ncurses nls oav oggvorbis opengl oss pam pdflib perl png python qt quicktime readline sdl slang spell sse ssl svga tcltk tcpd tiff truetype usb x86 xml2 xmms xv zlib"
There's some code in both ebuilds that makes a file called "configure-options" which exists in the temp directory of /var/tmp/portage/mplayer-[version]/temp. Run an emerge on both -r2 and -r3 and cancel the emerge right after the configure, get the output of the configure-options file and attach it to this bug.
Created attachment 37726 [details] configure-options-r2 /var/tmp/portage/mplayer-1.0_pre5-r2/temp/configure-options
Created attachment 37727 [details] configure-options-r3 /var/tmp/portage/mplayer-1.0_pre5-r3/temp/configure-options
the configure-options for -r3 seems a bit sketchy, considering it has --disable-3dnowex, and then --enable-3dnowex below it.
one has mmx and sse flags, one doesn't. Try the -r3 with mmx and sse enabled. As for the --disable --enable 3dnowex.. woh, gotta check that out >:/.
sse and mmx were both enabled in -r3 to begin with. adding sse2 and mmx2 to my USE flags seem to fix the problem.
The ebuild was fixed for the 3dnowex logic. As far as the mmx2/sse2 fix, the USE flags were put there because some people need mmx2 and sse2 to get it working with mmx and sse... However, some people have it break if mmx2 and/or sse2 is stuck in. Since this seems to have fixed the problem, I'm resolving this. If you feel that a better solution should be put in tact, feel free to re-open this bug. Thanks for posting!
*** Bug 61095 has been marked as a duplicate of this bug. ***
*** Bug 61902 has been marked as a duplicate of this bug. ***
