Hi lool,

I remember that you have tuned the debian/rules file to accomodate to
the 'default' toolchain flags. Could you please have a look at this


On Wed, Aug 25, 2010 at 18:34:48 (CEST), Riku Voipio wrote:

> reopen 594093
> thanks
>> /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.
> Neither is it a toolchain bug nor do we have any NEON capable buildds.
> And, btw ubfx is not even a NEON instruction. It is a ARMv7 instruction.
> The error is caused by debians toolchain default flags. you need to pass
> -march=armv7-a for the debian-neon pass to get armv7 instructions accepted.
> Riku

Reinhard Tartler, KeyID 945348A4

pkg-multimedia-maintainers mailing list

Reply via email to