All of lore.kernel.org
 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 19:43:25 +0100	[thread overview]
Message-ID: <1270147405.4993.161.camel@rex> (raw)
In-Reply-To: <1270146830.6277.127.camel@trini-m4400>

On Thu, 2010-04-01 at 11:33 -0700, Tom Rini wrote:
> On Thu, 2010-04-01 at 19:09 +0100, Richard Purdie wrote:
> > On Thu, 2010-04-01 at 09:45 -0700, Tom Rini wrote:
> > > There's two uglies here.  Ugly one, above.  Quoting isn't nice to read
> > > and gdb/gcc/binutils are special.  It does however, work from the
> > > get-go.  And the only cases it doesn't get right, right off the bat are
> > > some perl (and possibly python) module cases where we aren't giving the
> > > right relative path there, but we can always figure it out and fix that
> > > up per recipe.  Ugly two, the chrpath way.  Depends on having a big
> > > enough RPATH in the initial binary to patch over.  Doesn't work if the
> > > RPATH isn't long enough as you say, which is why you can't do it on
> > > -cross.  
> > 
> > I've done the maths and it will always work within the sysroots/staging
> > directory as there is always enough length available. Since we want rid
> > of /cross/ for various reasons anyway I don't think this is a reason
> > against this approach.
> 
> What do you want to do on nativesdk ?  That's where this gets real
> important as well.

I'd argue for the same approach. We'd just have to ensure the base path
used for the SDK is long enough to accommodate this but again, thats not
difficult to arrange.

Cheers,

Richard





  reply	other threads:[~2010-04-01 18:46 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
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 [this message]
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=1270147405.4993.161.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.