From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [[PATCHv2] 1/2] classes/testsdk: do_testsdkext avoid STAGING_DIR/BASE_WORKDIR in PATH
Date: Thu, 11 Feb 2016 16:08:05 -0600 [thread overview]
Message-ID: <1455228486-15517-1-git-send-email-anibal.limon@linux.intel.com> (raw)
The inclusion of STAGING_DIR/BASE_WORKDIR in PATH is contaminating
the environment, i.e. when try to sanity check perl (check_perl_modules)
it takes perl from STAGING_DIR causing eSDK install to fail.
Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
---
meta/classes/testsdk.bbclass | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/meta/classes/testsdk.bbclass b/meta/classes/testsdk.bbclass
index 487f40c..a56ad5e 100644
--- a/meta/classes/testsdk.bbclass
+++ b/meta/classes/testsdk.bbclass
@@ -97,9 +97,18 @@ def testsdkext_main(d):
# extensible sdk shows a warning if found bitbake in the path
# because can cause problems so clean it
new_path = ''
+ paths_to_avoid = ['bitbake/bin', 'poky/scripts',
+ d.getVar('STAGING_DIR', True),
+ d.getVar('BASE_WORKDIR', True)]
for p in os.environ['PATH'].split(':'):
- if 'bitbake/bin' in p or 'poky/scripts' in p:
+ avoid = False
+ for pa in paths_to_avoid:
+ if pa in p:
+ avoid = True
+ break
+ if avoid:
continue
+
new_path = new_path + p + ':'
new_path = new_path[:-1]
os.environ['PATH'] = new_path
--
2.1.4
next reply other threads:[~2016-02-11 22:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 22:08 Aníbal Limón [this message]
2016-02-11 22:08 ` [[PATCHv2] 2/2] nativesdk-buildtools-perl-dummy.bb: Fix variable expansion in python code Aníbal Limón
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=1455228486-15517-1-git-send-email-anibal.limon@linux.intel.com \
--to=anibal.limon@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