From: "Robert E. Cochran" <yocto@mindchasers.com>
To: Ting Liu <ting.liu@nxp.com>, Zhenhua Luo <zhenhua.luo@nxp.com>,
Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: Freescale meta-freescale announcement of new layer
Date: Fri, 18 Mar 2016 23:00:55 -0400 [thread overview]
Message-ID: <56ECC0E7.1080607@mindchasers.com> (raw)
In-Reply-To: <DB3PR04MB04210FA5A305F8E9B6919CC998C0@DB3PR04MB042.eurprd04.prod.outlook.com>
On 03/18/2016 02:34 AM, Ting Liu wrote:
> ppc64 is not in the default list of QEMU_TARGETS in poky/meta/recipes-devtools/qemu/qemu.inc
> you can add this in conf/local.conf to enable it:
> QEMU_TARGETS_append_pn-qemu-native = " ppc64"
Thank you. That moves the gobject-introspection compile task a little
further, but now qemu-ppc64 segfaults for me during the execution of the
g-ir-scanner-qemuwrapper script.
I'm curious as to whether one of you were able to compile
gobject-introspection with ppc64.
I'll send more info later.
Bob
>
> -Ting
>
>> -----Original Message-----
>> From: meta-freescale-bounces@yoctoproject.org [mailto:meta-freescale-
>> bounces@yoctoproject.org] On Behalf Of Zhenhua Luo
>> Sent: Friday, March 18, 2016 10:54 AM
>> To: Otavio Salvador <otavio.salvador@ossystems.com.br>
>> Cc: meta-freescale@yoctoproject.org; Lauren Post
>> <Lauren.Post@freescale.com>
>> Subject: Re: [meta-freescale] Freescale meta-freescale announcement of
>> new layer
>>
>> 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:otavio.salvador@ossystems.com.br]
>>> Sent: Thursday, March 17, 2016 7:44 PM
>>> To: Zhenhua Luo <zhenhua.luo@nxp.com>
>>> Cc: Robert E. Cochran <yocto@mindchasers.com>; meta-
>>> freescale@yoctoproject.org; Lauren Post <Lauren.Post@freescale.com>
>>> Subject: Re: [meta-freescale] Freescale meta-freescale announcement of
>>> new layer
>>>
>>> On Thu, Mar 17, 2016 at 7:44 AM, Zhenhua Luo <zhenhua.luo@nxp.com>
>> 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
>> meta-freescale@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-freescale
prev parent reply other threads:[~2016-03-19 3:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 18:38 Freescale meta-freescale announcement of new layer Lauren Post
2015-06-30 1:58 ` Bob Cochran
2015-06-30 2:25 ` Luo Zhenhua
2015-06-30 4:36 ` Weng White
2015-07-08 22:15 ` Bob Cochran
2016-03-09 15:38 ` Robert E. Cochran
2016-03-10 9:54 ` Zhenhua Luo
2016-03-10 15:00 ` Robert E. Cochran
2016-03-10 16:27 ` Otavio Salvador
2016-03-11 3:57 ` Robert E. Cochran
2016-03-11 4:37 ` Zhenhua Luo
2016-03-11 10:29 ` Otavio Salvador
2016-04-07 7:49 ` Ahsan, Noor
2016-04-07 10:31 ` Otavio Salvador
2016-04-07 13:43 ` Ahsan, Noor
2016-03-16 18:10 ` Robert E. Cochran
2016-03-16 19:56 ` Otavio Salvador
2016-03-17 10:44 ` Zhenhua Luo
2016-03-17 11:43 ` Otavio Salvador
2016-03-18 2:53 ` Zhenhua Luo
2016-03-18 6:34 ` Ting Liu
2016-03-18 12:56 ` Otavio Salvador
2016-03-19 3:00 ` Robert E. Cochran [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56ECC0E7.1080607@mindchasers.com \
--to=yocto@mindchasers.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio.salvador@ossystems.com.br \
--cc=ting.liu@nxp.com \
--cc=zhenhua.luo@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.