From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] Fix for oe-buildenv-internal
Date: Mon, 21 Mar 2016 12:41:45 +0100 [thread overview]
Message-ID: <cover.1458560461.git.pkj@axis.com> (raw)
A late improvement to the oe-buildenv-internal patches i provided last
week introduced an error in the code that adds paths to $PATH. This
can cause $PATH to end up with a trailing : which will subsequently
cause the sannity checker to fail.
//Peter
The following changes since commit 068afc5d436c716591a54f7d6e1944d8b6f9a198:
tzdata: update to 2016b (2016-03-20 23:12:32 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib pkj/oe-init-build-env
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=pkj/oe-init-build-env
Peter Kjellerstedt (1):
oe-buildenv-internal: Correct the sed expression which updates $PATH
scripts/oe-buildenv-internal | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.1.0
next reply other threads:[~2016-03-21 11:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 11:41 Peter Kjellerstedt [this message]
2016-03-21 11:41 ` [PATCH 1/1] oe-buildenv-internal: Correct the sed expression which updates $PATH Peter Kjellerstedt
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.1458560461.git.pkj@axis.com \
--to=peter.kjellerstedt@axis.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