Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] patchelf: Add patchelf recipe
Date: Wed, 27 Aug 2014 16:50:57 +0100	[thread overview]
Message-ID: <1409154657.29296.12.camel@ted> (raw)
In-Reply-To: <CAMKF1spTdX1Mom+X5LOt5-pRpCMUuNmxTpvfQ+VOjVaasNrS=w@mail.gmail.com>

On Wed, 2014-08-27 at 08:08 -0700, Khem Raj wrote:
> On Wed, Aug 27, 2014 at 7:50 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > This is useful since it allows us to edit the RPATH and interpreter fields
> > in ELF binaries. This is potentially particularly useful in improving the way
> > we can use the SDK and also potentially making native binaries more relocatable.
> >
> 
> Long ago I had a patch series to replace chrpath with patchelf see
> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/patchelf
> 
> can that be considered now ?

The issue is one of dependencies. We need chrpath/patchelf to relocate
things like {autoconf|automake|pkgconfig}-native. Native
patchelf/chrpath depend on those things to build so if we don't have it
in ASSUME_PROVIDED, we get circular dependencies.

chrpath is widely available in most distros. Unfortunately patchelf is
not. We therefore can't easily put patchelf-native into
ASSUME_PROVIDED :(

So the reason the above didn't merge hasn't really changed, much as I'd
also wish it had.

This does not stop us using patchelf for other things though (and I
believe we should).

Cheers,

Richard



  reply	other threads:[~2014-08-27 15:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27 14:50 [PATCH] patchelf: Add patchelf recipe Richard Purdie
2014-08-27 15:08 ` Khem Raj
2014-08-27 15:50   ` Richard Purdie [this message]
2014-08-27 21:12     ` Khem Raj

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=1409154657.29296.12.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