From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Qing He <qing.he@intel.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: [PATCH 0/6] recipe upgrades, Qing He, 12/31/2010
Date: Thu, 06 Jan 2011 10:21:26 +0000 [thread overview]
Message-ID: <1294309286.17519.24120.camel@rex> (raw)
In-Reply-To: <20110104083441.GA16835@qhe2-db>
On Tue, 2011-01-04 at 16:34 +0800, Qing He wrote:
> Thank you for the fix.
> The screen flushed too quick and I missed the error message.
> Btw, I observed an error, but the build process didn't halt, is that
> considered some kind of bug?
Bitbake will have exited with a return value of 1, not 0 if any ERROR
had been displayed. We should probably display some message to the user
as bitbake exits in this case so a normal shell user can see this
clearly (needs to be added to lib/bb/ui/knotty.py). The autobuilder
checks the exit code so will pick this up already.
Cheers,
Richard
next prev parent reply other threads:[~2011-01-06 10:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-31 3:16 [PATCH 0/6] recipe upgrades, Qing He, 12/31/2010 Qing He
2010-12-31 3:16 ` [PATCH 1/6] parted: upgrade to version 2.3 Qing He
2010-12-31 3:16 ` [PATCH 3/6] gnutls: upgrade to version 2.10.4 Qing He
2010-12-31 3:16 ` [PATCH 5/6] augeas: upgrade to version 0.7.4 Qing He
2010-12-31 3:16 ` [PATCH 6/6] lzo: upgrade to version 2.04 Qing He
2010-12-31 3:16 ` [PATCH 4/6] ncurses: upgrade to version 5.7 Qing He
2010-12-31 3:16 ` [PATCH 2/6] libtasn1: upgrade to version 2.9 Qing He
2010-12-31 9:50 ` [PATCH 0/6] recipe upgrades, Qing He, 12/31/2010 Saul Wold
2011-01-04 8:34 ` Qing He
2011-01-06 10:21 ` Richard Purdie [this message]
2011-01-04 1:25 ` Saul Wold
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=1294309286.17519.24120.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=poky@yoctoproject.org \
--cc=qing.he@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 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.