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

[Reinhard Tartler <siretart@tauware.de>]

On Sun, Jul 24, 2011 at 13:07:11 (CEST), Philipp Kern wrote:

> On Sun, Jul 24, 2011 at 12:59:11PM +0200, David Kuehling wrote:
>> Well, if it allows people like me to just do 'apt-get source' and
>> 'dpkg-buildpackage' without thinking about which kernel they run, it
>> does more good than harm, doesn't it :)
>> 
>> Maybe the really correct, and right way to fix that, though, is to patch
>> the configure script to check for the ABI used by $CC instead of 'uname
>> -m'.  That kind of fix could then also go upstream.
>
> Normally you pass the right build triplet coming from dpkg to configure through
> debian/rules, though.  So it shouldn't rely on uname.

Well, I've discussed this upstream before implementing the change I've
pointed to earlier in this thread. The upstream configure script does
check the ABI of CC on every arch but mips. On mips, I was told this
wasn't possible because mips was special there were so many ABIs there.

David (or anyone else interested), you are more than welcome to have a
look at libav's configure script and propose a patch:

http://anonscm.debian.org/gitweb/?p=pkg-multimedia/libav.git;a=blob;f=configure

or latest upstream:

http://git.libav.org/?p=libav.git;a=blob;f=configure

Note that upstream doesn't use autotools; i.e., the configure script is
hand-written.

-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4