Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Request for branch merge
Date: Tue, 04 May 2010 19:10:01 +0100	[thread overview]
Message-ID: <1272996601.1355.5.camel@rex> (raw)
In-Reply-To: <1272905195.2931.0.camel@trini-m4400>

On Mon, 2010-05-03 at 09:46 -0700, Tom Rini wrote:
> On Sun, 2010-05-02 at 00:29 +0100, Richard Purdie wrote:
> > On Mon, 2010-04-12 at 17:46 +0100, Joshua Lock wrote:
> > > On Mon, 2010-04-12 at 08:59 -0700, Tom Rini wrote:
> > > > On Mon, 2010-04-12 at 10:37 +0200, Koen Kooi wrote:
> > >  > Joshuas last 3 commits to poky seem to fix Toms issue with binconfig and
> > > > > my issue with chrpath, which only leaves the cross staging lamangler
> > > > > stuff to get fixed.
> > > > 
> > > > Actually (and I'm OK with binconfig stuff being broken in the first
> > > > merge) the problem with binconfig junk isn't the file contents, but the
> > > > file location.  staging-target-pkg will contain
> > > > staging/<host>/usr/bin/<target>/foo-config.  Which means using pstaging
> > > > for a target pkg built on 32bit Linux fails when used on 64bit Linux.
> > > > Not that I wouldn't mind seeing the binconfig stuff die, just saying
> > > > it's a problem today :)
> > > 
> > > Ah, hmm... yes. That is a problem.
> > > 
> > > FWIW I don't think you'll get any arguments from the Poky team where the
> > > binconfig stuff to suffer an untimely demise!
> > 
> > FWIW, Poky has had some interesting commits recently that address Tom's
> > issue above from Josh.
> 
> Interesting.  When you killed CROSS_*, did you rework stuff so that gcc
> & co's sysroot stuff works automatically or no?  Can't tell off-hand.

What do you mean by "works automatically"?

Cheers,

Richard




  reply	other threads:[~2010-05-04 18:13 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
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 [this message]
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=1272996601.1355.5.camel@rex \
    --to=rpurdie@rpsys.net \
    --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