From: Laurentiu Palcu <laurentiu.palcu@intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-commits@lists.openembedded.org,
Martin Jansa <martin.jansa@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [oe-commits] Laurentiu Palcu : qemu: add wrapper for qemu-mips binary
Date: Mon, 08 Oct 2012 11:35:27 +0300 [thread overview]
Message-ID: <5072904F.8060007@intel.com> (raw)
In-Reply-To: <CAMKF1spAUgXTptMAdXe=utSRap2_xc6ULuLMA7=QdX0ewis6BQ@mail.gmail.com>
On 10/06/2012 09:13 PM, Khem Raj wrote:
> On Sat, Oct 6, 2012 at 9:21 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
>>
>>> +# IMPORTANT: This piece needs to be removed once the root cause is fixed!
>>> +do_install_append() {
>>> + create_wrapper ${D}/${bindir}/qemu-mips \
>>> + QEMU_RESERVED_VA=0x0
>>> +}
>>> +# END of qemu-mips workaround
>>
>> What about checking if mips is in QEMU_TARGETS before doing this?
>>
>
> or simply for check for existence of qemu-mips before creating the wrapper
>
>> Right now this breaks all distros without mips in QEMU_TARGETS.
Sorry, I totally missed this. :| What about adding a simple check in the
create_wrapper script itself? We create the wrapper only if the target
binary exists. It sounds better this way and the user does not
necessarily have to remember to check for the binary existence before
creating the wrapper.
I'll prepare a patch.
Thanks,
Laurentiu
>>
>> Cheers,
next prev parent reply other threads:[~2012-10-08 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121003114821.8D16410375@opal>
2012-10-06 16:21 ` [oe-commits] Laurentiu Palcu : qemu: add wrapper for qemu-mips binary Martin Jansa
2012-10-06 18:13 ` Khem Raj
2012-10-08 8:26 ` Richard Purdie
2012-10-08 8:35 ` Laurentiu Palcu [this message]
2012-10-08 9:14 ` Richard Purdie
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=5072904F.8060007@intel.com \
--to=laurentiu.palcu@intel.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-commits@lists.openembedded.org \
--cc=openembedded-core@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