From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: wenzong.fan@windriver.com
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 1/1] bitbake: Abort build if runtime dependency conflict
Date: Wed, 11 Jul 2012 11:44:11 +0100 [thread overview]
Message-ID: <1342003451.7934.8.camel@ted> (raw)
In-Reply-To: <05c49df922dac41a9d86377c1400ae2ef58fe4ae.1341977062.git.wenzong.fan@windriver.com>
On Wed, 2012-07-11 at 11:28 +0800, wenzong.fan@windriver.com wrote:
> From: Wenzong Fan <wenzong.fan@windriver.com>
>
> Currently if there are multiple preferred providers available for
> a runtime dependency, bitbake will print an Error message and let
> the build go on. Anyways the build should abort while any Errors
> occured.
>
> [YOCTO #2734]
>
> Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com>
> ---
> bitbake/lib/bb/providers.py | 2 ++
> bitbake/lib/bb/taskdata.py | 3 ++-
> 2 files changed, 4 insertions(+), 1 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-07-11 10:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 3:28 [PATCH 0/1] bitbake: Abort build if runtime dependency conflict wenzong.fan
2012-07-11 3:28 ` [PATCH 1/1] " wenzong.fan
2012-07-11 10:44 ` 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=1342003451.7934.8.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=wenzong.fan@windriver.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