From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] sanity.bbclass: warn the user if BBPATH contains wrong entries
Date: Wed, 13 Jun 2012 21:27:36 -0700 [thread overview]
Message-ID: <4FD96838.20508@linux.intel.com> (raw)
In-Reply-To: <1339514272-7427-2-git-send-email-laurentiu.palcu@intel.com>
On 06/12/2012 08:17 AM, Laurentiu Palcu wrote:
> If BBPATH references the working directory, the user is warned and asked
> to fix the problem.
>
> [Yocto #1465]
>
> Signed-off-by: Laurentiu Palcu<laurentiu.palcu@intel.com>
> ---
> meta/classes/sanity.bbclass | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/meta/classes/sanity.bbclass b/meta/classes/sanity.bbclass
> index f79fc3f..6ed1e6f 100644
> --- a/meta/classes/sanity.bbclass
> +++ b/meta/classes/sanity.bbclass
> @@ -387,6 +387,17 @@ def check_sanity(sanity_data):
> if "." in paths or "" in paths:
> messages = messages + "PATH contains '.' or '', which will break the build, please remove this."
>
> + 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.");
> +
This change seems to trigger in the default case of the standard
bblayers.conf file included in meta-yocto. Is there a fix for this? Do
we need to uprev the bblayers file?
Sau!
> if sanity_data.getVar('TARGET_ARCH', True) == "arm":
> # This path is no longer user-readable in modern (very recent) Linux
> try:
next prev parent reply other threads:[~2012-06-14 4:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 15:17 [PATCH 0/2] Bug fixes Laurentiu Palcu
2012-06-12 15:17 ` [PATCH 1/2] sanity.bbclass: warn the user if BBPATH contains wrong entries Laurentiu Palcu
2012-06-14 4:27 ` Saul Wold [this message]
2012-06-14 12:06 ` Laurentiu Palcu
2012-06-12 15:17 ` [PATCH 2/2] connman: make useradd parameters consistent with rootless X Laurentiu Palcu
2012-06-12 15:30 ` Burton, Ross
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=4FD96838.20508@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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.