The following binaries are generated by qemu-native, qemu-ppc64 is not there,
but qemu-ppc64 is used by g-ir-scanner-qemuwrapper script of
gobject-introspection.
tmp/sysroots/x86_64-linux/usr/bin/qemu-aarch64
tmp/sysroots/x86_64-linux/usr/bin/qemu-arm
tmp/sysroots/x86_64-linux/usr/bin/qemu-ga
tmp/sysroots/x86_64-linux/usr/bin/qemu-i386
tmp/sysroots/x86_64-linux/usr/bin/qemu-img
tmp/sysroots/x86_64-linux/usr/bin/qemu-io
tmp/sysroots/x86_64-linux/usr/bin/qemu-mips
tmp/sysroots/x86_64-linux/usr/bin/qemu-mips.real
tmp/sysroots/x86_64-linux/usr/bin/qemu-mips64
tmp/sysroots/x86_64-linux/usr/bin/qemu-mipsel
tmp/sysroots/x86_64-linux/usr/bin/qemu-nbd
tmp/sysroots/x86_64-linux/usr/bin/qemu-ppc
tmp/sysroots/x86_64-linux/usr/bin/qemu-system-aarch64
tmp/sysroots/x86_64-linux/usr/bin/qemu-system-arm
tmp/sysroots/x86_64-linux/usr/bin/qemu-system-i386
tmp/sysroots/x86_64-linux/usr/bin/qemu-system-mips
tmp/sysroots/x86_64-linux/usr/bin/qemu-system-mips64
tmp/sysroots/x86_64-linux/usr/bin/qemu-system-mipsel
tmp/sysroots/x86_64-linux/usr/bin/qemu-system-ppc
tmp/sysroots/x86_64-linux/usr/bin/qemu-system-x86_64
tmp/sysroots/x86_64-linux/usr/bin/qemu-x86_64
Best Regards,
Zhenhua
> -----Original Message-----
> From: Otavio Salvador [mailto:[email protected]]
> Sent: Thursday, March 17, 2016 7:44 PM
> To: Zhenhua Luo <[email protected]>
> Cc: Robert E. Cochran <[email protected]>; meta-
> [email protected]; Lauren Post <[email protected]>
> Subject: Re: [meta-freescale] Freescale meta-freescale announcement of new
> layer
>
> On Thu, Mar 17, 2016 at 7:44 AM, Zhenhua Luo <[email protected]> wrote:
> > After investigation, this is an issue in oe-core. The reason is that the
> generated qemu binary name of ppc64 targets is qemu-ppc instead of qemu-
> ppc64, the gobject-introspection uses qemu-ppc64, so the build issue
> appeared.
> >
> > There are two solutions for the issue, one is to update qemu-native recipe
> > to
> make sure qemu binary name is qemu-ppc64, the other one is to update
> gobject-introspection to use qemu-ppc when ppc64 target is built. May I know
> about your comments on which one is better?
>
> The fix needs to be generic and fixed in OE-Core, in this case.
> Provide some pointers where did you find the root cause and I can take a look
> about which routed I would take.
>
> --
> Otavio Salvador O.S. Systems
> http://www.ossystems.com.br http://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
--
_______________________________________________
meta-freescale mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-freescale
