Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Cc: "Lock, Joshua" <joshua.lock@intel.com>
Subject: Re: Request for branch merge
Date: Thu, 01 Apr 2010 17:07:07 +0100	[thread overview]
Message-ID: <1270138027.4993.139.camel@rex> (raw)
In-Reply-To: <1270136609.6277.98.camel@trini-m4400>

On Thu, 2010-04-01 at 08:43 -0700, Tom Rini wrote:
> On Thu, 2010-04-01 at 08:41 -0700, Tom Rini wrote:
> > On Thu, 2010-04-01 at 16:33 +0100, Richard Purdie wrote:
> > 
> > > * Added relocatable binary processing from Poky for -native binaries 
> > >   using chrpath. This isn't enabled for -cross packages due to the 
> > >   relative path length problems.
> > 
> > Is there a reason to not use $ORIGIN here instead?  The patch Chris
> > Larson posted ages ago does get this right (the hard part is
> > gcc/gdb/binutils due to the multi configure running).  And any path
> > length issues you hit with -cross you should be able to hit with
> > -native, no?
> 
> For reference it's just doing:
> export RELATIVERPATH = "${@base_path_relative(d.getVar('bindir', 1),
> d.getVar('STAGING_LIBDIR_NATIVE', 1))}"
> export BUILD_LDFLAGS = "-L${STAGING_LIBDIR_NATIVE} \
>                         -Wl,-rpath,\\\$\$ORIGIN/${RELATIVERPATH} -Wl,-O1
> \
>                         -Wl,-rpath,${STAGING_LIBDIR_NATIVE} -Wl,-O1 \
>                         "
> 
> In bitbake.conf (extra variable for dealing with the hard packages
> later).

I really much prefer the post processing approach as it "just works" and
doesn't need exceptions for hard packages, nor does it have horrible
quoting.

Cheers,

Richard





  reply	other threads:[~2010-04-01 16:10 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-01 15:33 Request for branch merge Richard Purdie
2010-04-01 15:41 ` Tom Rini
2010-04-01 15:43   ` Tom Rini
2010-04-01 16:07     ` Richard Purdie [this message]
2010-04-01 16:45       ` Tom Rini
2010-04-01 18:09         ` Richard Purdie
2010-04-01 18:33           ` Tom Rini
2010-04-01 18:43             ` Richard Purdie
2010-04-01 16:05   ` Richard Purdie
2010-04-01 16:46     ` Tom Rini
2010-04-01 15:46 ` Khem Raj
2010-04-01 16:09   ` Richard Purdie
2010-04-01 16:18     ` Andrea Adami
2010-04-01 16:29       ` Richard Purdie
2010-04-01 16:37 ` Gary Thomas
2010-04-01 17:17   ` Joshua Lock
2010-04-01 17:55 ` Koen Kooi
2010-04-01 18:17   ` Richard Purdie
2010-04-01 20:03   ` Chris Larson
2010-04-01 20:34     ` Tom Rini
2010-04-01 21:08       ` Koen Kooi
2010-04-01 21:25         ` Tom Rini
2010-04-01 21:27         ` Philip Balister
2010-04-01 22:26       ` Tom Rini
2010-04-02 13:40 ` Koen Kooi
2010-04-02 14:35   ` Koen Kooi
2010-04-02 21:41     ` Richard Purdie
2010-04-03  7:21       ` Koen Kooi
2010-04-02 21:29   ` Richard Purdie
2010-04-03  7:23     ` Koen Kooi
2010-04-08 15:40       ` Joshua Lock
2010-04-03 13:24     ` Koen Kooi
2010-04-12  8:37 ` Koen Kooi
2010-04-12 15:59   ` Tom Rini
2010-04-12 16:46     ` Joshua Lock
2010-05-01 23:29       ` Richard Purdie
2010-05-03 16:46         ` Tom Rini
2010-05-04 18:10           ` Richard Purdie
2010-05-04 18:55             ` Tom Rini
2010-05-05 23:22               ` Richard Purdie
2010-05-05 23:30                 ` Tom Rini
2010-04-12 16:45   ` Joshua Lock
2010-04-12 17:47     ` Koen Kooi
2010-04-12 20:55     ` Koen Kooi
2010-04-12 22:19     ` Koen Kooi
2010-04-13  3:46       ` Richard Purdie
2010-04-13  7:06         ` Koen Kooi
2010-05-01 23:28           ` Richard Purdie
2010-05-02 14:13             ` Koen Kooi

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=1270138027.4993.139.camel@rex \
    --to=rpurdie@rpsys.net \
    --cc=joshua.lock@intel.com \
    --cc=openembedded-devel@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