After updating to gcc-4.3.3-r1 yesterday, I wanted to re-emerge ffmpeg-0.5-r1. (originally I wanted to change some use-flags of it, but as I got an error, I also tried to re-emerge it with the same use-flags). Anyway, the compilation stops with a: libavcodec/eatqi.c:166: internal compiler error: Segmentation fault make: *** [libavcodec/eatqi.o] Error 1 and tells me to file a bugreport. If you need anything from me, just tell me (it's my first bugreport at all). Reproducible: Always Steps to Reproduce: 1. GCC-4.3.3-r1 (I think so, as I originally emerged ffmpeg a few days/weeks ago with GCC-4.3.3 without problems) 2. emerge ffmpeg-0.5-r1 Actual Results: i686-pc-linux-gnu-gcc -DHAVE_AV_CONFIG_H -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I. -I"/var/tmp/portage/media-video/ffmpeg-0.5-r1/work/ffmpeg-0.5" -O2 -march=core2 -msse4.1 -pipe -fomit-frame-pointer -D_ISOC99_SOURCE -D_POSIX_C_SOURCE=200112 -std=c99 -fomit-frame-pointer -march=core2 -Wdeclaration-after-statement -Wall -Wno-switch -Wdisabled-optimization -Wpointer-arith -Wredundant-decls -Wno-pointer-sign -Wcast-qual -Wwrite-strings -Wtype-limits -Wundef -O3 -fno-math-errno -fno-signed-zeros -c -o libavcodec/8svx.o libavcodec/8svx.c libavcodec/eatqi.c:166: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <http://bugs.gentoo.org/> for instructions. make: *** [libavcodec/eatqi.o] Error 1 make: *** Waiting for unfinished jobs.... * * ERROR: media-video/ffmpeg-0.5-r1 failed. ... Expected Results: successful compiling CFLAGS="-O2 -march=core2 -msse4.1 -pipe" CXXFLAGS="-O2 -march=core2 -msse4.1 -pipe" CHOST="i686-pc-linux-gnu" MAKEOPTS="-j3" USE="X gnome gtk -kde -qt3 -eds dvd dbus firefox xulrunner alsa jpeg svg png tiff mp3 gif opengl bluetooth laptop sse x$ FEATURES="parallel-fetch ccache" CCACHE_SIZE="512M" ACCEPT_KEYWORDS="~x86"
Created attachment 185174 [details] build-log of ffmpeg
After some more research, this seems to be kind of a duplicate of http://bugs.gentoo.org/show_bug.cgi?id=262567, at least it looks like that.
*** This bug has been marked as a duplicate of bug 262567 ***