From: <jackie.huang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] sstate.bbclass: fixup extra hardcoded paths
Date: Wed, 29 May 2013 05:20:59 -0400 [thread overview]
Message-ID: <cover.1369818931.git.jackie.huang@windriver.com> (raw)
From: Jackie Huang <jackie.huang@windriver.com>
We need this since we have a script in the sstate-cache that has a hard
coded path into the multilib toolchain directory and that isn't
automatically relocated like it should be, so add this extra logic.
--
The following changes since commit 8f5bc47729edb8cb051d81e9ff1680cb8d2eca25:
dropbear: a fix for hang in dropbearkey, built for x32 (2013-05-24 14:14:30 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib jhuang0/d_multilib_image_0529_1
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=jhuang0/d_multilib_image_0529_1
Jackie Huang (1):
sstate.bbclass: fixup extra hardcoded paths
meta/classes/sstate.bbclass | 11 +++++++++++
1 file changed, 11 insertions(+)
--
1.7.9.5
next reply other threads:[~2013-05-29 9:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 9:20 jackie.huang [this message]
2013-05-29 9:21 ` [PATCH 1/1] sstate.bbclass: fixup extra hardcoded paths jackie.huang
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.1369818931.git.jackie.huang@windriver.com \
--to=jackie.huang@windriver.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 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.