When compiling xine-lib-1-rc2, in the directory src/libffmpeg/libavcodec/i386, I received the following error compiling dsputil_mmx.c: > In file included from dsputil_mmx.c:22: > ../dsputil.h:492: warning: static declaration for `lrintf' follows non-static > ../dsputil.h: In function `lrintf': > ../dsputil.h:499: internal error: Segmentation fault > Please submit a full bug report, > with preprocessed source if appropriate. > See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. My gcc version is 3.2.1. I will be attaching preprocessed source in a comment to this bug (there doesn't seem to be a file attach button on the main bug page).
Created attachment 5295 [details] Preprocessed source causing the error Here is the preprocessed source code causing the error. Oops, I forgot the command line: /bin/sh ../../../../libtool-nofpic --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../../../.. -I../../../.. -I../../../../include -I../../../../include -I../../../../src -I../../../../src/xine-engine -I../../../../src/xine-engine -I../../../../src/xine-utils -I../../../../src/input -I../../../../src/input -DSIMPLE_IDCT -DHAVE_AV_CONFIG_H -DRUNTIME_CPUDETECT -DUSE_FASTMEMCPY -DCONFIG_RISKY -DCONFIG_ENCODERS `echo -mcpu=pentiumpro -O3 -pipe -fomit-frame-pointer -falign-functions=4 -falign-loops=4 -falign-jumps=4 -mpreferred-stack-boundary=2 -fexpensive-optimizations -fschedule-insns2 -fno-strict-aliasing -ffast-math -funroll-loops -finline-functions -Wall -D_REENTRANT -D_FILE_OFFSET_BITS=64 -DXINE_COMPILE -Wpointer-arith -Wnested-externs -Wcast-align -Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes -I/opt/kde-3.1/include/artsc | sed -e 's/-funroll-loops//g'` -c -o dsputil_mmx.lo `test -f 'dsputil_mmx.i' || echo './'`dsputil_mmx.i and gcc -v output: Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/specs Configured with: ../gcc-3.2.1/configure --prefix=/usr --enable-shared --enable-threads=posix --with-slibdir=/lib --enable-__cxa_atexit --enable-clocale=gnu Thread model: posix gcc version 3.2.1
*** Bug 13345 has been marked as a duplicate of this bug. ***
I cannot reproduce it on 3.2.2, 3.2.3, 3.3.1, or 3.4 so it must be fixed.