Diego Biurrun <[email protected]> writes: > On Sun, May 15, 2011 at 10:42:20AM -0700, Dave Yeo wrote: >> On 05/15/11 06:20 am, Diego Biurrun wrote: >>> So we test for and appear to support nasm, but nasm fails to build >>> libavcodec/x86/fft_mmx.asm: >>> >>> $ make -k V=1 >>> nasm -f win32 -DPREFIX -I. -I"/home/diego/src/libav" -Pconfig.asm -I >>> libavcodec/x86/ -M -o libavcodec/x86/fft_mmx.o libavcodec/x86/fft_mmx.asm> >>> libavcodec/x86/fft_mmx.d >>> nasm -f win32 -DPREFIX -I. -I"/home/diego/src/libav" -Pconfig.asm -I >>> libavcodec/x86/ -o libavcodec/x86/fft_mmx.o libavcodec/x86/fft_mmx.asm >>> libavcodec/x86/fft_mmx.asm:339: error: invalid combination of opcode and >>> operands >>> [...] >>> >>> There are many more similar errors that I skipped pasting here. >>> This is a paste from Cygwin, but the same error appears on Linux. >>> >>> Can somebody fix this? Is nasm support worth keeping in the >>> first place? >> >> You need to update your nasm binary as it assembles fine here with the >> latest daily and appears to have been fixed in March. >> (http://permalink.gmane.org/gmane.comp.lang.nasm.cvs/2465) >> Yasm does not support a.out or OMF which OS/2 uses so I use nasm with >> the attached patch. > > I split the patch in two parts and pushed it, thanks.
And fucked up the executable bit. Clearly you did not test it. Please be more careful in future. -- Måns Rullgård [email protected] _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
