"nasm -r" is used by the configuration-script instead of "nasm -v" which should be used to get the version. Reproducible: Always Steps to Reproduce: 1. emerge libmp4v2 Actual Results: ... checking for glib.h... yes checking for nasm... true checking nasm version...... nasm: error: unrecognised option `-r' nasm: error: no input file specified type `nasm -h' for help util/testnasm.sh: line 8: test: =: unary operator expected util/testnasm.sh: line 8: test: =: unary operator expected util/testnasm.sh: line 8: test: =: unary operator expected util/testnasm.sh: line 8: test: =: unary operator expected util/testnasm.sh: line 8: test: =: unary operator expected util/testnasm.sh: line 8: test: =: unary operator expected ...
Same here. Looks like it's resolved in media-libs/libmp4v2-1.5.0.1-r1 Not sure why that isn't set to stable yet instead of ~x86. The difference: src_unpack() { unpack ${A} cd "${S}" + sed -e 's:nasm -r:nasm -v:g' -i configure || die "sed nasm" elibtoolize }
W00t! Arches, please stabilize =media-libs/libmp4v2-1.5.0.1-r1 as this is really annoying bug.
Would be better if i CC arches.
amd64/x86 stable
ppc stable
Stable for HPPA.
alpha/arm/ia64/sh/sparc stable
arm stable
ppc64 stable, closing
