Libav 0.7 FTBFS on mipsel: Error: opcode not supported on this processor: mips2 (mips2) `ldl $2, 7($13)'

[David Kuehling]

>>>>> "Reinhard" == Reinhard Tartler <siretart at tauware.de> writes:

> Hi, I've noticed that Libav FTBFS on mipsel in experimental. The
> buildlog looks like this:

> /tmp/ccztZJXP.s: Assembler messages: /tmp/ccztZJXP.s:334: Error:
> opcode not supported on this processor: mips2 (mips2) `ldl $2,7($13)'
[..]
> https://buildd.debian.org/status/fetch.php?pkg=libav&arch=mipsel&ver=4%3A0.7-2&stamp=1310857239

> It seems that this build failure only happens on the buildd 'rem', but
> not on others such as 'monteverdi' or 'phrixos'. What is so special
> about 'rem' and is there anything I can or even should do about this
> in the package?

Grepping over a copy of the ffmpeg sources, I find ldl in
inline-assembler fragments in various files, such as intreadwrite.h.
These are #ifdefed checking for ARCH_MIPS64, which is set by the
configure script.

Unfortunately the configure script checks 'uname -m' for the
architecture, which might be mips64 when running debian on a 64-bit
kernel (this happens, e.g. when running with the loongson kernels
shipped by debian).

Forcing ./configure --arch=mips/mipsel might help. 

cheers,

David
-- 
GnuPG public key: http://dvdkhlng.users.sourceforge.net/dk.gpg
Fingerprint: B17A DC95 D293 657B 4205  D016 7DEF 5323 C174 7D40
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20110717/a4762a1e/attachment.pgp>