Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC] Replacing chrpath with patchelf
Date: Sat, 18 Aug 2012 11:31:15 +0100	[thread overview]
Message-ID: <1345285875.27428.27.camel@ted> (raw)
In-Reply-To: <CAMKF1srvBZzMTbN-iOqEjitgSjFOK_Cpd0B94HjWm1z7s-0-iQ@mail.gmail.com>

On Sat, 2012-08-18 at 00:17 -0700, Khem Raj wrote:
> Hi,
> 
> I have a patchset that replaces use of chrpath with patchelf. Patchelf can
> resize the ELF headers to accomodate larger RPATHs
> 
> The branch is posted here
> 
> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/patchelf
> 
> Please test it out and let me know if you see any issues

chrpath is something we require users to install on the system they're
building on. The reason is that we need to relocate the native recipes
and you can't do that without chrpath. You can't build chrpath without
building a native recipe you need to stage to change its own RPATH. 

Now there are a variety of ways we can deal with this but we need to
think it through.

At the very least such a change would need to adjust all the
documentation about the prerequisites.

I'm not actually sure we need to deal with larger RPATHs in the real
world either. There are some bugs we're finding now the call is failing
but they're not turning out to be due to that.

Cheers,

Richard




  reply	other threads:[~2012-08-18 10:43 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 [this message]
2012-08-18 17:15   ` Khem Raj
2012-08-19  1:27     ` Phil Blundell
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=1345285875.27428.27.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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