From: Serhii Popovych <spopovyc@cisco.com>
To: openembedded-core@lists.openembedded.org
Cc: XE-Linux <xe-linux-external@cisco.com>
Subject: [PATCH v2 0/2] distutils: correct path to python for nativesdk
Date: Tue, 28 Mar 2017 19:31:58 +0000 [thread overview]
Message-ID: <cover.1490729401.git.spopovyc@cisco.com> (raw)
In-Reply-To: <20170328190227.6647.76065@do.openembedded.org>
Hi,
Here is another small set of similar changes.
While for target path to python interpreter is fixed
a while ago, for nativesdk it points to env(1) utility
with absolute path in SDK where it might not be present.
Also this absolute path might be too long.
Use ${USRBINPATH} instead of ${bindir} to correctly
configure path to env(1).
Please review.
Thanks.
Cc: XE-Linux <xe-linux-external@cisco.com>
Serhii Popovych (2):
distutils.bbclass: Fix path to python for scripts
distutils3.bbclass: Fix path to python for scripts
meta/classes/distutils.bbclass | 4 ++--
meta/classes/distutils3.bbclass | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
--
2.7.4
next prev parent reply other threads:[~2017-03-28 19:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 18:51 [PATCH 0/2] distutils: correct path to python for nativesdk Serhii Popovych
2017-03-28 18:51 ` [PATCH 1/2] distutils.bbclass: Fix path to python for scripts Serhii Popovych
2017-03-28 18:51 ` [PATCH 2/2] distutils3.bbclass: " Serhii Popovych
2017-03-28 19:02 ` ✗ patchtest: failure for distutils: correct path to python for nativesdk Patchwork
2017-03-28 19:31 ` Serhii Popovych [this message]
2017-03-28 19:31 ` [PATCH v2 1/2] distutils.bbclass: Fix path to python for scripts Serhii Popovych
2017-03-28 19:32 ` [PATCH v2 2/2] distutils3.bbclass: " Serhii Popovych
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=cover.1490729401.git.spopovyc@cisco.com \
--to=spopovyc@cisco.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=xe-linux-external@cisco.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.