Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] sanity: display the parsed BBPATH when complaining about CWD elements
Date: Fri, 20 Jul 2012 17:24:27 -0700	[thread overview]
Message-ID: <5009F6BB.50006@linux.intel.com> (raw)
In-Reply-To: <1342714534-7032-1-git-send-email-ross.burton@intel.com>

On 07/19/2012 09:15 AM, Ross Burton wrote:
> Many people don't understand the nuances of PATH/BBPATH, so help them by clarifying
> the warning and displaying the parsed list element-by-element.
>
> Signed-off-by: Ross Burton <ross.burton@intel.com>
> ---
>   meta/classes/sanity.bbclass |    1 +
>   1 file changed, 1 insertion(+)
>
> diff --git a/meta/classes/sanity.bbclass b/meta/classes/sanity.bbclass
> index 6ef5450..575ce15 100644
> --- a/meta/classes/sanity.bbclass
> +++ b/meta/classes/sanity.bbclass
> @@ -400,6 +400,7 @@ def check_sanity(sanity_data):
>                   "Please check your layer.conf files and other BBPATH "        \
>                   "settings to remove the current working directory "           \
>                   "references.");
> +        bb.warn("Parsed BBPATH is" + str(bbpaths));
>
>       if sanity_data.getVar('TARGET_ARCH', True) == "arm":
>           # This path is no longer user-readable in modern (very recent) Linux
>

Merged into OE-Core

Thanks
	Sau!



      reply	other threads:[~2012-07-21  0:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-19 16:15 [PATCH] sanity: display the parsed BBPATH when complaining about CWD elements Ross Burton
2012-07-21  0:24 ` Saul Wold [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=5009F6BB.50006@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox