[issue2306] YASM libavcodec/x86/dsputil_yasm.o
Martin Storsjö mar...@martin.st added the comment: I ran into the same issue recently. It turned out to be that the machine lacked yasm but used nasm instead. (After upgrading the latest yasm, I forgot to rerun configure, since I thought I actually had it installed already, and it took me a while to figure out.) Thus, installing yasm or disabling it (--disable-yasm?) so nasm won't be used instead probably are the best suggestions for now. FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2306
[issue2306] YASM libavcodec/x86/dsputil_yasm.o
Martin Storsjö mar...@martin.st added the comment: Here's the output of nasm -f macho -e -o /tmp/x.s libavcodec/x86/dsputil_yasm.asm -Ilibavcodec/x86/ FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2306 nasmoutput.s Description: Binary data
[issue2306] YASM libavcodec/x86/dsputil_yasm.o
New submission from jlx solutions jlxsoluti...@gmail.com: Fails to compile latest svn -- files: ffmpegfail messages: 12294 priority: normal status: new substatus: new title: YASMlibavcodec/x86/dsputil_yasm.o type: bug FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2306 ffmpegfail Description: Binary data
[issue2306] YASM libavcodec/x86/dsputil_yasm.o
Carl Eugen Hoyos ceho...@rainbow.studorg.tuwien.ac.at added the comment: Please provide the output of yasm --version -- status: new - open substatus: new - needs_more_info FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2306
[issue2306] YASM libavcodec/x86/dsputil_yasm.o
Ronald S. Bultje rsbul...@gmail.com added the comment: Also please run: yasm -f macho -e -o /tmp/x.s dsputil_yasm.asm and then attach /tmp/x.s here. Is this latest SVN of FFmpeg or latest SVN of YASM (or both). If FFmpeg SVN is problem, can you tell us which revision introduced the compiler bug? FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2306