John Van Sickle <[email protected]> added the comment: Hi rbultje,
Thanks for responding. The solution you mention is, IMO, a rather poor one. How are users supposed to know that they need --enable-runtime-cpudetect? Because for me it took: 1) Having FFmpeg crash with any '-vf scale' 2) Build ffmpeg_g and backtrace 3) Build and test with --disable-amd3dnow --disable-amd3dnowext 4) File bug report 5) Dev responds Here's what should have happened. 1) FFmpeg's ./configure tests if my system can use 3dnow. [no] I'm not cross compiling here, the only thing I pass to ./configure is --enable-gpl and the $PATH to up-to-date gcc and as. Is it unreasonable to expect FFmpeg to build a binary that won't crash trying to using SIMD instructions my system doesn't support? ________________________________________________ FFmpeg issue tracker <[email protected]> <https://roundup.ffmpeg.org/issue2570> ________________________________________________
