From: akuster808 <akuster808@gmail.com>
To: "Hongzhi.Song" <hongzhi.song@windriver.com>,
raj.khem@gmail.com, openembedded-devel@lists.openembedded.org
Subject: Re: [OE-core][PATCH] x86: remove "qemu-usermode" from MACHINE_FEATURES_BACKFILL_CONSIDERED
Date: Fri, 13 Jul 2018 07:59:13 -0700 [thread overview]
Message-ID: <978a9da0-b906-816e-2ae7-40b505684fca@gmail.com> (raw)
In-Reply-To: <20180713140616.15664-3-hongzhi.song@windriver.com>
On 07/13/2018 07:06 AM, Hongzhi.Song wrote:
> error information:
> ---
> qemu: uncaught target signal 11 (Segmentation fault) - core dumped
> If the above error message is about missing .so libraries,
> then setting up GIR_EXTRA_LIBS_PATH in the recipe should help.
> (typically like this: GIR_EXTRA_LIBS_PATH="${B}/something/.libs" )
> ---
>
> qemux86 will face the error above.
Wrong ML
think it should be: openembedded-core@lists.openembedded.org
>
> Signed-off-by: Hongzhi.Song <hongzhi.song@windriver.com>
> ---
> meta/conf/machine/include/x86/arch-x86.inc | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/conf/machine/include/x86/arch-x86.inc b/meta/conf/machine/include/x86/arch-x86.inc
> index 70814b8d4d..091d60f507 100644
> --- a/meta/conf/machine/include/x86/arch-x86.inc
> +++ b/meta/conf/machine/include/x86/arch-x86.inc
> @@ -26,6 +26,7 @@ TUNE_LDARGS += "${@bb.utils.contains('TUNE_FEATURES', 'mx32', '-m elf32_x86_64',
> TUNE_ASARGS += "${@bb.utils.contains('TUNE_FEATURES', 'mx32', '-x32', '', d)}"
> # user mode qemu doesn't support x32
> MACHINE_FEATURES_BACKFILL_CONSIDERED_append = " ${@bb.utils.contains('TUNE_FEATURES', 'mx32', 'qemu-usermode', '', d)}"
> +MACHINE_FEATURES_BACKFILL_CONSIDERED_append = " ${@bb.utils.contains('TUNE_FEATURES', 'm32', 'qemu-usermode', '', d)}"
> MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'mx32', 'x86-x32:', '' ,d)}"
>
> # ELF64 ABI
next prev parent reply other threads:[~2018-07-13 14:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 14:06 [meta-oe][PATCH v2 0/1] Add a recipe on kernel selftest Hongzhi.Song
2018-07-13 14:06 ` [meta-oe][PATCH 1/1] kernel-selftest: " Hongzhi.Song
2018-07-13 16:23 ` Burton, Ross
2018-07-16 9:53 ` Hongzhi, Song
2018-07-27 8:40 ` Khem Raj
2018-07-27 9:00 ` Hongzhi, Song
2018-07-30 3:36 ` Hongzhi, Song
2018-07-30 4:02 ` Khem Raj
2018-07-30 12:14 ` Hongzhi, Song
2018-07-30 18:38 ` Khem Raj
2018-07-31 11:14 ` Hongzhi, Song
2018-07-13 14:06 ` [OE-core][PATCH] x86: remove "qemu-usermode" from MACHINE_FEATURES_BACKFILL_CONSIDERED Hongzhi.Song
2018-07-13 14:13 ` Alexander Kanavin
2018-07-14 8:44 ` Hongzhi, Song
2018-07-13 14:59 ` akuster808 [this message]
2018-07-13 14:10 ` [meta-oe][PATCH v2 0/1] Add a recipe on kernel selftest Hongzhi, Song
2018-07-13 15:02 ` akuster808
2018-07-16 10:04 ` Hongzhi, Song
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=978a9da0-b906-816e-2ae7-40b505684fca@gmail.com \
--to=akuster808@gmail.com \
--cc=hongzhi.song@windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox