From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: McClintock Matthew-B29882 <B29882@freescale.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Yoder Stuart-B08248 <B08248@freescale.com>,
Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: qemu.inc do_install question / qemu-targets.inc
Date: Fri, 02 Mar 2012 14:05:09 +0000 [thread overview]
Message-ID: <1330697109.309.8.camel@ted> (raw)
In-Reply-To: <CAEsOVNfTjTNi_nBy=Fd98JURMMLAwvcpQs=zbxihMKeRgn_ehA@mail.gmail.com>
On Tue, 2012-02-28 at 21:40 +0000, McClintock Matthew-B29882 wrote:
> All,
>
> I'm wanting to remove this:
>
> diff --git a/meta/recipes-devtools/qemu/qemu.inc
> b/meta/recipes-devtools/qemu/qemu.inc
> index 58049b9..3be46f2 100644
> --- a/meta/recipes-devtools/qemu/qemu.inc
> +++ b/meta/recipes-devtools/qemu/qemu.inc
> @@ -49,13 +49,6 @@ do_configure() {
> test ! -e ${S}/target-i386/beginend_funcs.sh || chmod a+x
> ${S}/target-i386/beginend_funcs.s
> }
>
> -do_install () {
> - export STRIP="true"
> - autotools_do_install
> - install -d ${D}${datadir}/qemu
> - install -m 0755 ${WORKDIR}/powerpc_rom.bin ${D}${datadir}/qemu
> -}
> -
>
> Can anyone comment why it's there? Can we move it up a level to a
> specific recipe? We don't want to include this powerpc_rom.bin..
> should we just fork our qemu recipe instead?
From what I remember our qemuppc image didn't boot without that file
being present. Whether that is still the case I don't know.
I care that qemuppc continues to boot correctly, not about the location
the file is installed.
> Also, can we make this change? I don't think we want ppc-linux-user on
> our ppc-softmmu target.
>
> diff --git a/meta/recipes-devtools/qemu/qemu-targets.inc
> b/meta/recipes-devtools/qemu/qemu-targe
> index 550a7fe..8423aa1 100644
> --- a/meta/recipes-devtools/qemu/qemu-targets.inc
> +++ b/meta/recipes-devtools/qemu/qemu-targets.inc
> @@ -6,7 +6,7 @@ def get_qemu_target_list(d):
> import bb
> archs = bb.data.getVar('QEMU_TARGETS', d, True).split()
> targets = ""
> - for arch in ['mips64', 'mips64el', 'ppcemb']:
> + for arch in ['mips64', 'mips64el', 'ppcemb', 'ppc']:
> if arch in archs:
> targets += arch + "-softmmu,"
> archs.remove(arch)
I've no hard feelings on that one.
Cheers,
Richard
prev parent reply other threads:[~2012-03-02 14:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 21:40 qemu.inc do_install question / qemu-targets.inc McClintock Matthew-B29882
2012-03-02 14:05 ` Richard Purdie [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=1330697109.309.8.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=B08248@freescale.com \
--cc=B29882@freescale.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.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