From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] native.bbclass: correct PATH to have native-intercept be prepended
Date: Tue, 26 Jun 2012 10:56:04 -0700 [thread overview]
Message-ID: <1340733364-29968-1-git-send-email-sgw@linux.intel.com> (raw)
This was needed since it was after the sysroots and thus in some cases
the native sysroot chown was being found and used instead of the script
provided by native-intercept/chown. This was noticed by the non-gplv3
build since it's coreutils depends on coreutils-native.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
---
meta/classes/native.bbclass | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/meta/classes/native.bbclass b/meta/classes/native.bbclass
index bca48d4..eb30b5a 100644
--- a/meta/classes/native.bbclass
+++ b/meta/classes/native.bbclass
@@ -99,7 +99,7 @@ PKG_CONFIG_SYSROOT_DIR = ""
LIBCOVERRIDE = ""
CLASSOVERRIDE = "class-native"
-PATH =. "${COREBASE}/scripts/native-intercept:"
+PATH_prepend = "${COREBASE}/scripts/native-intercept:"
python native_virtclass_handler () {
if not isinstance(e, bb.event.RecipePreFinalise):
--
1.7.7.6
reply other threads:[~2012-06-26 18:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1340733364-29968-1-git-send-email-sgw@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