From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Building hg/help2man not relying on them?
Date: Fri, 15 Jul 2011 16:38:23 +0100 [thread overview]
Message-ID: <1310744304.30326.8.camel@phil-desktop> (raw)
In-Reply-To: <1310743401.20015.1251.camel@rex>
On Fri, 2011-07-15 at 16:23 +0100, Richard Purdie wrote:
> If we don't have chrpath present it means we need to disable sstate for
> all its dependencies and the whole thing got really messy and nasty very
> quickly :(.
Looking at the output of bitbake -e, the only dependencies for
gettext-native are:
DEPENDS="autoconf-native automake-native libtool-native
gnu-config-native"
and, if I remember right, all of those are basically scripts rather than
compiled binaries (and hence don't have any rpaths to ch.) So it seems
as though this would actually be a nonissue in practice.
> If attempting it again I'd probably want to remove the autotooling from
> it and turn it into a simple .c file since I'm not sure it derives much
> from the autotooling but causes immense pain. Its not exactly a large
> code base and I agree with the suckage comment.
Yeah, agreed.
p.
next prev parent reply other threads:[~2011-07-15 15:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 2:00 Building hg/help2man not relying on them? Tom Rini
2011-07-15 2:56 ` Mark Hatle
2011-07-15 14:39 ` Joshua Lock
2011-07-15 14:43 ` Mark Hatle
2011-07-15 15:08 ` Tom Rini
2011-07-15 15:18 ` Phil Blundell
2011-07-15 15:23 ` Richard Purdie
2011-07-15 15:38 ` Phil Blundell [this message]
2011-07-15 15:44 ` Phil Blundell
2011-07-15 18:09 ` Tom Rini
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=1310744304.30326.8.camel@phil-desktop \
--to=philb@gnu.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