Hi, 2011/5/26 Måns Rullgård <[email protected]>: > "Ronald S. Bultje" <[email protected]> writes: >> 2011/5/26 Måns Rullgård <[email protected]>: >>> Diego Biurrun <[email protected]> writes: >>>> --- >>>> configure | 2 ++ >>>> 1 files changed, 2 insertions(+), 0 deletions(-) >>>> >>>> diff --git a/configure b/configure >>>> index 5e3d6fb..7e9d30b 100755 >>>> --- a/configure >>>> +++ b/configure >>>> @@ -2720,6 +2720,7 @@ EOF >>>> yasm_debug="-g dwarf2" >>>> elif check_cmd nasm -v; then >>>> yasmexe=nasm >>>> + nasm=yes >>>> yasm_debug="-g -F dwarf" >>>> enabled x86_64 && test "$objformat" = elf && objformat=elf64 >>>> fi >>>> @@ -3105,6 +3106,7 @@ echo "big-endian ${bigendian-no}" >>>> echo "runtime cpu detection ${runtime_cpudetect-no}" >>>> if enabled x86; then >>>> echo "yasm ${yasm-no}" >>>> + echo "nasm ${nasm-no}" >>>> echo "MMX enabled ${mmx-no}" >>>> echo "MMX2 enabled ${mmx2-no}" >>>> echo "3DNow! enabled ${amd3dnow-no}" >>>> -- >>> >>> This is also confusing. A normal configuration will say nasm=no, making >>> it look like something was disabled. What are you trying to do really? >>> Why don't you work on flashsv or whatever it is you're supposed to be doing? >> >> If you do want to work on it, as a user I'd expect this: >> >> A) when yasm was found: >> yasm: yes >> >> B) when nasm was found: >> nasm: yes >> >> C) when neither was found: >> yasm/nasm: no > > Why not simply replace the label with "yasm/nasm" in all cases?
OK with me, although it'd be nice if it told me which one it chose to use (even fancier, allowing --asm=nasm to override the default of yasm and force using nasm). Ronald _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
