Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Scott Garman <scott.a.garman@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/1] runqemu bugfix [v2]
Date: Fri, 21 Sep 2012 15:17:25 -0700	[thread overview]
Message-ID: <505CE775.4030104@linux.intel.com> (raw)
In-Reply-To: <cover.1348033737.git.scott.a.garman@intel.com>

On 09/18/2012 10:50 PM, Scott Garman wrote:
> Hello,
>
> This is a fix for Yocto bug #3112, where there are certain edge cases
> where the bitbake command is avalable to fails to run. Previously we
> mistakenly treated that as the same case as if bitbake didn't exist in
> the user's $PATH, and this fix causes us to show the user the output
> of bitbake so they can view the error message.
>
> v2 includes rework based on feedback from Mark Hatle (thanks!).
>
> Scott
>
> The following changes since commit 7887b99646d8e1e736ad6e4a306e47df9955221e:
>
>    local.conf.sample: change valgrind support architecture comment (2012-09-14 17:05:59 +0100)
>
> are available in the git repository at:
>
>    git://git.yoctoproject.org/poky-contrib sgarman/runqemu-bitbake-fix-oe
>    http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=sgarman/runqemu-bitbake-fix-oe
>
> Scott Garman (1):
>    runqemu: show bitbake errors to user
>
>   scripts/runqemu |   12 ++++++++++--
>   1 file changed, 10 insertions(+), 2 deletions(-)
>

Merged into OE-Core

Thanks	
	Sau!




      parent reply	other threads:[~2012-09-21 22:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-19  5:50 [PATCH 0/1] runqemu bugfix [v2] Scott Garman
2012-09-19  5:50 ` [PATCH 1/1] runqemu: show bitbake errors to user Scott Garman
2012-09-21 22:17 ` Saul Wold [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=505CE775.4030104@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=scott.a.garman@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