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)' /tmp/ccztZJXP.s:335: Error: opcode not supported on this processor: mips2 (mips2) `ldr $2,0($13)' /tmp/ccztZJXP.s:447: Error: opcode not supported on this processor: mips2 (mips2) `ldl $4,7($17)' /tmp/ccztZJXP.s:448: Error: opcode not supported on this processor: mips2 (mips2) `ldr $4,0($17)' /tmp/ccztZJXP.s:2446: Error: opcode not supported on this processor: mips2 (mips2) `sdl $4,7($13)' /tmp/ccztZJXP.s:2447: Error: opcode not supported on this processor: mips2 (mips2) `sdr $4,0($13)' make[1]: *** [libavformat/asfcrypt.o] Error 1 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? If this mail should have been sent to the responsible buildd admin instead, please forward this mail on my behalf. Thanks. -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 _______________________________________________ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers