From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v3] bzip2-native: handling native path issue
Date: Sun, 29 Jul 2012 10:31:28 +0100 [thread overview]
Message-ID: <1343554288.16998.34.camel@ted> (raw)
In-Reply-To: <1343334859-21249-1-git-send-email-yao.zhao@windriver.com>
On Thu, 2012-07-26 at 16:34 -0400, Yao Zhao wrote:
> follow Richard's approach, modify bzip2-native recipe to install bzip2 package
> binaries to STAGING_BINDIR_NATIVE/bzip2-native to avoid problems when other
> package is doing upack to reference bzip2. libbz2.so* still installs to
> STAGING_LIBDIR_NATIVE.
>
> change python-native to depends on bzip2-replacement-native instead of
> bzip2-full-native and add EXTRANATIVEPATH for bzip2-native.
>
> Didn't add bzip2native.bbclass as python-native is the only user so far.
>
> Signed-off-by: Yao Zhao <yao.zhao@windriver.com>
> ---
> .../recipes-devtools/python/python-native_2.7.3.bb | 4 +++-
> meta/recipes-extended/bzip2/bzip2_1.0.6.bb | 4 +++-
> 2 files changed, 6 insertions(+), 2 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-07-29 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 20:34 [PATCH v3] bzip2-native: handling native path issue Yao Zhao
2012-07-29 9:31 ` Richard Purdie [this message]
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=1343554288.16998.34.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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