Bug#594093: closed by Reinhard Tartler <siretart at tauware.de> (Re: Bug#594093: mplayer: wrong byteorder on 16-bit displays with -vo x11 (-vo sdl works)?)

[Reinhard Tartler]

On Wed, Aug 25, 2010 at 17:37:33 (CEST), Timo Lindfors wrote:

F> owner at bugs.debian.org (Debian Bug Tracking System) writes:
>> TBH, I have no idea about if there are any buildds for
>> armel/experimental at all. I'd suggest asking on #debian-buildd or on
>> their mailing list.
>
> It seems mplayer is not built since ffmpeg fails to build:
>
> CC libavcodec/aacdec.o
> /tmp/ccv13sip.s: Assembler messages:
> /tmp/ccv13sip.s:5891: Error: selected processor does not support `ubfx ip,r3,#0,#4'
> /tmp/ccv13sip.s:5892: Error: selected processor does not support `ubfx r0,r3,#4,#4'
> /tmp/ccv13sip.s:6101: Error: selected processor does not support `ubfx r0,r3,#0,#4'
> /tmp/ccv13sip.s:6102: Error: selected processor does not support `ubfx ip,r3,#4,#4'
> /tmp/ccv13sip.s:6318: Error: selected processor does not support `ubfx ip,r3,#0,#2'
> /tmp/ccv13sip.s:6319: Error: selected processor does not support `ubfx r0,r3,#2,#2'
> /tmp/ccv13sip.s:6321: Error: selected processor does not support `ubfx r1,r3,#4,#2'
> /tmp/ccv13sip.s:6323: Error: selected processor does not support `ubfx r7,r3,#6,#2'
> /tmp/ccv13sip.s:6328: Error: selected processor does not support `rbit r9,r9'
> /tmp/ccv13sip.s:6562: Error: selected processor does not support `ubfx r7,r2,#0,#2'
> /tmp/ccv13sip.s:6563: Error: selected processor does not support `ubfx r8,r2,#2,#2'
> /tmp/ccv13sip.s:6565: Error: selected processor does not support `ubfx fp,r2,#4,#2'
> /tmp/ccv13sip.s:6567: Error: selected processor does not support `ubfx ip,r2,#6,#2'
> make[1]: *** [libavcodec/aacdec.o] Error 1
> make[1]: Leaving directory `/build/buildd-ffmpeg_0.6-2-armel-ldBGDA/ffmpeg-0.6/debian-neon'
> make: *** [build-stamp-neon] Error 2

which seems to me to be a toolchain bug. The build should care if the
processor is able to execute the NEON extensions; but compiling them
should be possible in any case. It's not like this binary is needed
during build or something.

I'm not going to investigate this further as the easiest fix would be
probably to reschedule the build on a NEON capable buildd.

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