Bug#802550: x264: FTBFS on mipsel: Error: opcode not supported on this processor: mips2 (mips2) `addvi.b $w0, $w1, 1'

James Cowgill james410 at cowgill.org.uk
Tue Oct 20 23:20:32 UTC 2015


On Wed, 2015-10-21 at 00:56 +0200, Sebastian Ramacher wrote:
> Package: x264
> Version: 2:0.148.2601+gita0cd7d3-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> x264 failed to build on mipsel:
> > # Build static lib
> > LDFLAGS="-Wl,-z,relro" ./configure --prefix=/usr --libdir=/usr/lib/mipsel-linux-gnu --extra-cflags=-fno-aggressive-loop-optimizations --enable-static --disable-cli \
> >    || ( tail -v -n +0 config.log config.log ; exit 1 )
> > You specified a pre-MSA CPU in your CFLAGS.
> > If you really want to run on such a CPU, configure with --disable-asm.

So (with my mips porting hat on) you will need to pass --disable-asm
here for mips, mipsel and mips64el.

But why on earth is this the upstream default? MSA isn't exactly common
on MIPS processors at the moment (eg binutils support was only added
last year).

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20151021/852db579/attachment-0001.sig>

More information about the pkg-multimedia-maintainers mailing list