From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org, dvhart@linux.intel.com,
poky@yoctoproject.org, saul.wold@intel.com
Subject: [PATCH 0/1] kern-tools: error if features are not found
Date: Thu, 12 May 2011 16:21:15 -0400 [thread overview]
Message-ID: <cover.1305229934.git.bruce.ashfield@windriver.com> (raw)
Richard/Saul,
I'll repeat the patch contents here, since they explain
the change
---->---->---->---->---->---->
Fixes bug: [YOCTO #955]
Updating the SRCREV to pickup the kern-tools change:
[
updateme: error if features are not found
Rather than silently dropping addon features, we emit a warning
and then exit with a failure code. The caller can then abort a
build and not simply miss features.
Passing --no-strict to the script disables this new functionality
if for some reason a feature description is missing on purpose.
]
---->---->---->---->---->---->
This takes care of one thing we hit during 1.0 development,
and provides a clear message about features that are not
part of the kernel being built.
In a test of a forced invalid feature, the output is:
| WARNING: addon feature "cfg/non-exisistent" was not found
| ERROR: required features were not found. aborting
.. and the build stops.
Thanks,
Bruce Ashfield <bruce.ashfield@windriver.com>
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: zedd/kernel
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
---
Bruce Ashfield (1):
kern-tools: error if features are not found
.../kern-tools/kern-tools-native_git.bb | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
next reply other threads:[~2011-05-12 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 20:21 Bruce Ashfield [this message]
2011-05-12 20:21 ` [PATCH 1/1] kern-tools: error if features are not found Bruce Ashfield
2011-05-12 20:22 ` Bruce Ashfield
2011-05-13 22:13 ` [PATCH 0/1] " 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=cover.1305229934.git.bruce.ashfield@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@yoctoproject.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=saul.wold@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