From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: McClintock Matthew-B29882 <B29882@freescale.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] chrpath: We should provide chrpath-replacement-native and install into a native specific directory
Date: Tue, 02 Oct 2012 21:19:11 +0100 [thread overview]
Message-ID: <1349209151.18301.13.camel@ted> (raw)
In-Reply-To: <70CC66F5C30A414DADDA6973E4CA391A6CA65A@039-SN1MPN1-001.039d.mgd.msft.net>
On Tue, 2012-10-02 at 17:30 +0000, McClintock Matthew-B29882 wrote:
> On Tue, Oct 2, 2012 at 11:29 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > On Tue, 2012-10-02 at 16:22 +0000, McClintock Matthew-B29882 wrote:
> >> Docs need to be updated, there was also a build warning if it was not
> >> installed - did that get removed too?
> >
> > You still need chrpath installed, this just avoids a different set of
> > problems in nativesdk and corrected ASSUME_PROVIDED.
>
> You still need it installed on your host?
Correct, it gets used for native sstate for example.
I've tried to remove this before and you get stuck in circular
dependencies which I decided weren’t worth the pain.
Cheers,
Richard
prev parent reply other threads:[~2012-10-02 20:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 13:13 [PATCH] chrpath: We should provide chrpath-replacement-native and install into a native specific directory Richard Purdie
2012-10-02 16:22 ` McClintock Matthew-B29882
2012-10-02 16:29 ` Richard Purdie
2012-10-02 17:30 ` McClintock Matthew-B29882
2012-10-02 20:19 ` 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=1349209151.18301.13.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=B29882@freescale.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