From: Scott Garman <scott.a.garman@intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 4/8] sanity.bbclass: warn the user if BBPATH contains wrong entries
Date: Thu, 21 Jun 2012 13:57:23 -0700 [thread overview]
Message-ID: <4FE38AB3.40503@intel.com> (raw)
In-Reply-To: <CAMKF1sp4KvDtK68NQNtOhSmCF6WK738Yr9cXOA0ntkHJ9wpYUQ@mail.gmail.com>
On 06/21/2012 08:51 AM, Khem Raj wrote:
> On Mon, Jun 18, 2012 at 12:56 PM, Scott Garman<scott.a.garman@intel.com> wrote:
>> From: Laurentiu Palcu<laurentiu.palcu@intel.com>
>>
>> If BBPATH references the working directory, the user is warned and asked
>> to fix the problem.
>>
>> [Yocto #1465]
>>
>> (From OE-Core rev: 73f10ae955ba217078fa2c5288b736ae8a30b184)
>>
>> Signed-off-by: Laurentiu Palcu<laurentiu.palcu@intel.com>
>> Signed-off-by: Richard Purdie<richard.purdie@linuxfoundation.org>
>>
>> Reworked commit to fix merge conflicts with denzil branch.
>>
>> Signed-off-by: Scott Garman<scott.a.garman@intel.com>
>> ---
>> meta/classes/sanity.bbclass | 13 ++++++++++++-
>> 1 file changed, 12 insertions(+), 1 deletion(-)
>>
>> diff --git a/meta/classes/sanity.bbclass b/meta/classes/sanity.bbclass
>> index 9755694..298372b 100644
>> --- a/meta/classes/sanity.bbclass
>> +++ b/meta/classes/sanity.bbclass
>> @@ -310,7 +310,18 @@ def check_sanity(sanity_data):
>> if "." in data.getVar('PATH', sanity_data, True).split(":"):
>> messages = messages + "PATH contains '.' which will break the build, please remove this"
>>
>> - if data.getVar('TARGET_ARCH', sanity_data, True) == "arm":
>> + bbpaths = sanity_data.getVar('BBPATH', True).split(":")
>> + if "." in bbpaths or "" in bbpaths:
>> + # TODO: change the following message to fatal when all BBPATH issues
>> + # are fixed
>> + bb.warn("BBPATH references the current directory, either through " \
>> + "an empty entry, or a '.'.\n\t This is unsafe and means your "\
>> + "layer configuration is adding empty elements to BBPATH.\n\t "\
>> + "Please check your layer.conf files and other BBPATH " \
>> + "settings to remove the current working directory " \
>> + "references.");
>> +
>> + if sanity_data.getVar('TARGET_ARCH', True) == "arm":
>
> No I get this warning when I use OE-Core standalone. The reason is for OE-Core
>
> BBPATH .= ":${LAYERDIR}"
>
> and there are no more entries prepended since its the only layer so
> leading : is causing
> this warning to show up.
>
>> # This path is no longer user-readable in modern (very recent) Linux
>> try:
>> if os.path.exists("/proc/sys/vm/mmap_min_addr"):
>> --
>> 1.7.9.5
Richard didn't end up pulling this in, and explained his reasoning on
the oe-core ML. So no worries.
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2012-06-21 20:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 19:56 [PATCH 0/8] denzil pull request Scott Garman
2012-06-18 19:56 ` [PATCH 1/8] documentation: Updated Manual revision history table Scott Garman
2012-06-18 19:56 ` [PATCH 2/8] openjade-native: Ensure we reautoconf the package Scott Garman
2012-06-18 19:56 ` [PATCH 3/8] webkit-gtk: Apply work around for all PowerPC targets Scott Garman
2012-06-18 19:56 ` [PATCH 4/8] sanity.bbclass: warn the user if BBPATH contains wrong entries Scott Garman
2012-06-21 15:51 ` Khem Raj
2012-06-21 20:32 ` Andrei Gherzan
2012-06-21 21:00 ` Andrei Gherzan
2012-06-21 21:14 ` Martin Jansa
2012-06-21 21:24 ` Andrei Gherzan
2012-06-22 5:39 ` Martin Jansa
2012-06-22 5:58 ` Khem Raj
2012-06-22 14:57 ` Richard Purdie
2012-06-21 20:57 ` Scott Garman [this message]
2012-06-18 19:56 ` [PATCH 5/8] eglibc: package mtrace separately Scott Garman
2012-06-18 19:56 ` [PATCH 6/8] poky-tiny: eliminate mtrace rdepends Scott Garman
2012-06-18 19:56 ` [PATCH 7/8] quilt: added ac_cv_path_BASH to CACHED_CONFIGUREVARS Scott Garman
2012-06-18 19:56 ` [PATCH 8/8] eglibc: added ac_cv_path_ " Scott Garman
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=4FE38AB3.40503@intel.com \
--to=scott.a.garman@intel.com \
--cc=poky@yoctoproject.org \
--cc=raj.khem@gmail.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.