2017-09-18 1:16 GMT+02:00 Reindl Harald <[email protected]>: > frankly i build ffmpeg with static x264 for years now and with 3.3.4 as well > as master now it's just broken? > > [builduser@buildserver:/rpmbuild/SPECS]$ rpm -q --filesbypkg x264-latest > x264-latest /usr/local/x264/libx264.a > x264-latest /usr/local/x264/x264.h > x264-latest /usr/local/x264/x264_config.h > > + ../configure --prefix=/usr/local --bindir=/usr/local/bin > --mandir=/usr/local/man
> '--extra-cflags=-I/usr/local/x264 -m64 -O2 -g0 > -mfpmath=sse -mavx -msse2avx -march=sandybridge -mtune=sandybridge -fopenmp > -pipe -fno-strict-aliasing -fomit-frame-pointer -fexceptions > -fstack-protector-strong --param=ssp-buffer-size=6 -D_FORTIFY_SOURCE=2 > -Wstack-protector -Wformat -Werror=format-security -Ofast -ffast-math > -funsafe-math-optimizations -Wno-pointer-sign -minline-all-stringops > -fno-strict-aliasing -flto -ffat-lto-objects -fuse-ld=gold > -fuse-linker-plugin -Wa,--noexecstack' '--extra-ldflags=-I/usr/local/x264 > -L/usr/local/x264 -ldl -Wl,--as-needed -Wl,-z,now -Wl,-z,relro > -Wl,-z,noexecstack -m64 -O2 -g0 -mfpmath=sse -mavx -msse2avx > -march=sandybridge -mtune=sandybridge -fopenmp -pipe -fno-strict-aliasing > -fomit-frame-pointer -fexceptions -fstack-protector-strong > --param=ssp-buffer-size=6 -D_FORTIFY_SOURCE=2 -Wstack-protector -Wformat > -Werror=format-security -Ofast -ffast-math -funsafe-math-optimizations > -Wno-pointer-sign -minline-all-stringops -fno-strict-aliasing -flto > -ffat-lto-objects -pie -fPIE -fuse-ld=gold -fuse-linker-plugin > -Wa,--noexecstack' As said before: Either this makes sense (in any configuration!), then it should be added to the appropriate configure options, or it does not make sense (read: It makes the resulting binary slower but not more secure compared to the available configure options) then don't use it. In any case: These options make your configure line unsupported here. (Mostly because it makes the binary slower for no gain, but using contradicting compiler options also counts.) > --enable-lto --ar=gcc-ar --ranlib=true --enable-nonfree > --enable-gpl --enable-pic --enable-version3 --enable-libmp3lame > --enable-libtheora --enable-libx264 --enable-libx265 --enable-libvpx > --enable-openssl --enable-static --enable-runtime-cpudetect > --disable-amd3dnow --disable-amd3dnowext --disable-avdevice --disable-debug > --disable-devices --disable-ffplay --disable-ffprobe --disable-ffserver > --disable-htmlpages --disable-hwaccels --disable-iconv --disable-libdc1394 > --disable-libfreetype --disable-libgsm --disable-libopencore-amrnb > --disable-libopencore-amrwb --disable-libopencv --disable-libopenjpeg > --disable-libopus --disable-librtmp --disable-libspeex --disable-libvorbis > --disable-libxvid --disable-podpages --disable-postproc > --disable-protocol=gopher --disable-shared --disable-txtpages Making the configure line less readable by adding default disable-options also doesn't increase the chance of somebody finding the issue here. > ERROR: libx264 not found Cutting the most important part of the console output also won't help. Carl Eugen _______________________________________________ ffmpeg-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
