[oe] [meta-multimedia] Problem with xbmc

[Khem Raj]

On Thu, Jun 6, 2013 at 6:24 AM, Martin Jansa <martin.jansa at gmail.com> wrote:
> On Thu, Jun 06, 2013 at 03:13:46PM +0200, Pasquale Bongiovanni wrote:
>> Hi all,
>> I'm new on yocto, I would like to create a core-image-sato including the
>> package xbmc.
>> But when I launch the command bitbake core-image-sato or bitbake xbmc, it
>> fails at task co_compile with the following file log:
>>
>> ...
>> In file included from DVDClock.cpp:25:0:
>> /home/pasquale/Scrivania/alibi/projects/prova/image-xbmc/tmp/work/armv7a-vfp-poky-linux-gnueabi/xbmc/11.0+gitrAUTOINC+82388d55dae79cbb2e486e307e23202e76a43efa-r15/git/xbmc/utils/MathUtils.h:
>> In member function 'int CDVDClock::UpdateFramerate(double, double*)':
>> /home/pasquale/Scrivania/alibi/projects/prova/image-xbmc/tmp/work/armv7a-vfp-poky-linux-gnueabi/xbmc/11.0+gitrAUTOINC+82388d55dae79cbb2e486e307e23202e76a43efa-r15/git/xbmc/utils/MathUtils.h:101:28:
>> error: impossible constraint in 'asm'
>> /home/pasquale/Scrivania/alibi/projects/prova/image-xbmc/tmp/work/armv7a-vfp-poky-linux-gnueabi/xbmc/11.0+gitrAUTOINC+82388d55dae79cbb2e486e307e23202e76a43efa-r15/git/xbmc/utils/MathUtils.h:101:28:
>> error: impossible constraint in 'asm'
>> /home/pasquale/Scrivania/alibi/projects/prova/image-xbmc/tmp/work/armv7a-vfp-poky-linux-gnueabi/xbmc/11.0+gitrAUTOINC+82388d55dae79cbb2e486e307e23202e76a43efa-r15/git/xbmc/utils/MathUtils.h:101:28:
>> error: impossible constraint in 'asm'
>> /home/pasquale/Scrivania/alibi/projects/prova/image-xbmc/tmp/work/armv7a-vfp-poky-linux-gnueabi/xbmc/11.0+gitrAUTOINC+82388d55dae79cbb2e486e307e23202e76a43efa-r15/git/xbmc/utils/MathUtils.h:101:28:
>> error: impossible constraint in 'asm'
>> make[1]: *** [DVDClock.o] Error 1
>> make: *** [xbmc/cores/dvdplayer/DVDPlayer.a] Error 2
>> ERROR: oe_runmake failed
>> ERROR: Function failed: do_compile
>> How can I solve this problem?
>
> It's known problem, fails for all my architectures, koen probably has it
> working, so maybe he will give you better advise..
>
> http://lists.openembedded.org/pipermail/openembedded-devel/2013-June/090945.html

as it seems if you have neon enabled for compiler to use then this
works out ok. So any arm platforms using neon
would work out to be ok. If your platform does not have neon then you
want to explore --with-platform option and probably
disable some features which includes the offending code

>
> --
> Martin 'JaMa' Jansa     jabber: Martin.Jansa at gmail.com
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>