All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: openembedded-devel@openembedded.org
Subject: Re: OE breakages, was: Re: fakeroot fails to build
Date: Mon, 2 Mar 2009 11:55:35 -0700	[thread overview]
Message-ID: <20090302185535.GD26343@smtp.west.cox.net> (raw)
In-Reply-To: <goeffr$gm2$1@ger.gmane.org>

On Sun, Mar 01, 2009 at 06:09:14PM +0100, Koen Kooi wrote:
> On 28-02-09 19:29, Tom Rini wrote:
>
>> Tangentally, packaged staging _can_ help here, but it's not I believe,
>> relocatible (unless you assume-provided some -native packages and
>> possibly we've fixed what we're doing wrong with gcc configure args).
>> IOW, if you build in, /OE/tmp you can't re-use the packaged staging
>> packages in /home/me/OE/tmp
>
> You can, packaged staging has 2 dirs: one for relocatable packages and  
> one for non-relocatable packages. That's how I understand it.

Compiled for target packages and runs-on-host packages.  To me, that's a
non-relocatible solution.

-- 
Tom Rini



  reply	other threads:[~2009-03-02 18:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-26 17:20 OE breakages, was: Re: fakeroot fails to build Frans Meulenbroeks
2009-02-26 19:37 ` Michael 'Mickey' Lauer
2009-02-27 16:06 ` Leon Woestenberg
2009-02-27 16:26   ` Tom Rini
2009-02-27 17:56     ` Frans Meulenbroeks
2009-02-27 19:35       ` Tom Rini
2009-02-28 10:54     ` Frans Meulenbroeks
2009-02-28 15:53       ` Tom Rini
2009-02-28 18:07         ` Frans Meulenbroeks
2009-02-28 18:29           ` Tom Rini
2009-03-01 17:09             ` Koen Kooi
2009-03-02 18:55               ` Tom Rini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-02-25  6:53 Mike (mwester)
2009-02-25  7:57 ` Koen Kooi
2009-02-25  8:23   ` Michael 'Mickey' Lauer
2009-02-25 15:14     ` Mike (mwester)
2009-02-25 15:43       ` OE breakages, was: " Koen Kooi
2009-02-26 13:05         ` Bernhard Guillon
2009-02-27 19:30           ` Rodrigo Vivi

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=20090302185535.GD26343@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.