From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/3] runqemu: Explicitly specify MACHINE when calling bitbake
Date: Wed, 12 Sep 2012 15:12:29 -0700 [thread overview]
Message-ID: <505108CD.8080408@intel.com> (raw)
In-Reply-To: <1347429555-32159-2-git-send-email-raj.khem@gmail.com>
On 09/11/2012 10:59 PM, Khem Raj wrote:
> When using runqemu with distros outside oe-core then
> MACHINE may not be there in local.conf so use the one
> thats available in environment of runqemu which is actually
> the correct one.
Looks simple enough.
Acked-by: Scott Garman <scott.a.garman@intel.com>
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> scripts/runqemu | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/runqemu b/scripts/runqemu
> index a3c3509..e843946 100755
> --- a/scripts/runqemu
> +++ b/scripts/runqemu
> @@ -281,7 +281,7 @@ setup_tmpdir() {
> exit 1; }
>
> # We have bitbake in PATH, get OE_TMPDIR from bitbake
> - OE_TMPDIR=`bitbake -e | grep ^TMPDIR=\" | cut -d '=' -f2 | cut -d '"' -f2`
> + OE_TMPDIR=`MACHINE=$MACHINE bitbake -e | grep ^TMPDIR=\" | cut -d '=' -f2 | cut -d '"' -f2`
> if [ -z "$OE_TMPDIR" ]; then
> echo "Error: this script needs to be run from your build directory,"
> echo "or you need to explicitly set OE_TMPDIR in your environment"
>
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2012-09-12 22:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 5:59 [PATCH V2 1/3] kernel.bbclass, module-base.bbclass: Use CC to form KERNEL_CC Khem Raj
2012-09-12 5:59 ` [PATCH 2/3] runqemu: Explicitly specify MACHINE when calling bitbake Khem Raj
2012-09-12 22:12 ` Scott Garman [this message]
2012-09-14 15:42 ` Saul Wold
2012-09-12 5:59 ` [PATCH 3/3] uclibc: Revert systemd regressing patch from upsteam uclibc Khem Raj
2012-09-12 6:37 ` Phil Blundell
2012-09-12 7:53 ` Khem Raj
2012-09-12 6:32 ` [PATCH V2 1/3] kernel.bbclass, module-base.bbclass: Use CC to form KERNEL_CC Phil Blundell
2012-09-12 7:49 ` Khem Raj
2012-09-13 18:02 ` Koen Kooi
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=505108CD.8080408@intel.com \
--to=scott.a.garman@intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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.