From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC] Replacing chrpath with patchelf
Date: Sun, 19 Aug 2012 02:27:19 +0100 [thread overview]
Message-ID: <1345339639.24626.62.camel@x121e.pbcl.net> (raw)
In-Reply-To: <CAMKF1srJ1w94g2rgu8FvZdmHLK-4t=GSj9OtSAncuquK6oNhjw@mail.gmail.com>
On Sat, 2012-08-18 at 10:15 -0700, Khem Raj wrote:
> so I figured. which now means you need to have patchelf on build host
> preinstalled instead of chrpath.
That'd be a bit of a pain, since (afaict) patchelf is not so widely
available in host distributions as chrpath.
> you never know. It just lifts this limitation. We ship
> chrpath-nativesdk as well and people can use it in different ways
I agree that removing the weird and arbitrary-seeming (from the user
perspective) restriction on rpath length would be a good thing. But
it's less clear that swapping a weird restriction that few people will
ever run into for a requirement to pre-install a relatively obscure host
binary on all systems is a good tradeoff.
How about writing a python function, or a trivial standalone program
(which can be compiled -native without requiring anything other than
${BUILD_CC}) to preprocess the binaries before chrpath sees them, or
indeed just to replace chrpath altogether? Or, as an alternative, how
about fixing chrpath to suck less and then just waiting for the improved
version to trickle down into deployed host distributions?
p.
next prev parent reply other threads:[~2012-08-19 1:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-18 7:17 [RFC] Replacing chrpath with patchelf Khem Raj
2012-08-18 10:31 ` Richard Purdie
2012-08-18 17:15 ` Khem Raj
2012-08-19 1:27 ` Phil Blundell [this message]
2012-08-22 0:21 ` Khem Raj
2012-08-22 7:47 ` Burton, Ross
2012-08-22 13:22 ` Richard Purdie
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=1345339639.24626.62.camel@x121e.pbcl.net \
--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