From: Phil Blundell <pb@pbcl.net>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC PATCH v3] chrpath.bbclass: strip common parent directories from rpath
Date: Tue, 30 Jul 2013 16:34:58 +0100 [thread overview]
Message-ID: <1375198498.8017.9.camel@phil-desktop.brightsign> (raw)
In-Reply-To: <825C7047-80C1-4FCF-B7F3-6F0895C41C36@gmail.com>
On Tue, 2013-07-30 at 08:27 -0700, Khem Raj wrote:
> On Jul 30, 2013, at 8:24 AM, Phil Blundell <pb@pbcl.net> wrote:
>
> > On Tue, 2013-07-02 at 11:50 +0200, Andreas Oberritter wrote:
> >> Allows to use shorter TMPDIRs in corner cases, e.g. with native
> >> perl modules, having a deep directory structure.
> >>
> >> The problem is that the original absolute rpath may be shorter
> >> than the newly generated relative rpath.
> >
> > Can we not just fix chrpath to cope with the case where the new path is
> > longer than the old one? It seems a bit sad to require
> > ever-more-convoluted workarounds for what is essentially a tool problem.
> >
>
> another option is to dump chrpath in favour of something which does it elegantly - patchelf
Right, or that. I've never used patchelf myself but if it works better
than chrpath (which isn't an especially high bar to set) then that
sounds like a decent enough option.
p.
next prev parent reply other threads:[~2013-07-30 15:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 23:55 [PATCH][RFC] chrpath.bbclass: strip common parent directories from rpath Andreas Oberritter
2013-03-06 0:32 ` [PATCH v2][RFC] " Andreas Oberritter
2013-03-06 7:19 ` [PATCH v2][RFC] chrpath.bbclass: strip common parent directories from rpath# Henning Heinold
2013-07-02 9:50 ` [RFC PATCH v3] chrpath.bbclass: strip common parent directories from rpath Andreas Oberritter
2013-07-30 15:24 ` Phil Blundell
2013-07-30 15:27 ` Khem Raj
2013-07-30 15:34 ` Phil Blundell [this message]
2013-07-30 18:47 ` Andreas Oberritter
2013-07-31 23:25 ` Trevor Woerner
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=1375198498.8017.9.camel@phil-desktop.brightsign \
--to=pb@pbcl.net \
--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