All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: OE and the developing host
Date: Wed, 28 Feb 2007 10:28:03 +0000	[thread overview]
Message-ID: <1172658483.16062.23.camel@localhost.localdomain> (raw)
In-Reply-To: <200702281109.25161.ranaldo@unina.it>

On Wed, 2007-02-28 at 11:09 +0100, Nicola Ranaldo wrote:
> I use OE on a gentoo box. This morning i updated the system, and the new 
> linux-headers package removed /usr/include/asm/page.h. So when building my 
> angstrom image it failed with perl asking to include that file. This problem 
> was discussed on the gentoo bug and after applying a simple workaround i was 
> able to emerge perl on the gentoo box and perl native on OE.
> After a while the oe build stopped on esound, this was caused by a malfunction 
> of /usr/lib/libosp.so.5 on gentoo, i reemerged it and solved the problem. Now 
> the armstrong-gpe-image is complete. But this introduced a doubt. OE build 
> some tools directly, and use other directly from the build host, so it could 
> be teoretically possible to produce different images on different host. Is 
> there a way or a plan to avoid it and make OE build host independant 
> (supposing i was correct)? If not, what's the most used/supported distro by 
> OE developers?

*-native packages can touch things on the system, any other packages
shouldn't and if they were found to be, it would be a bug and should be
fixed.

Its never going to be possible to make make OE build everything it needs
itself since you always need some prerequisites (e.g. a initial
toolchain).

Personally, I use OE/Poky on Ubuntu and Slackware. There are others
using Gentoo and other systems. Ideally it should work on most systems,
you might see problems with -native packages, you shouldn't see problems
with non -native ones.

Cheers,

Richard




  reply	other threads:[~2007-02-28 10:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-28 10:09 OE and the developing host Nicola Ranaldo
2007-02-28 10:28 ` Richard Purdie [this message]
2007-02-28 10:31   ` Koen Kooi
2007-02-28 15:58     ` Hans Henry von Tresckow
2007-02-28 16:27       ` Philip Balister
2007-02-28 20:27         ` Newbie Question Lee Studley
2007-02-28 20:30           ` gerwin van der kruis
2007-02-28 21:10             ` Richard Purdie
2007-02-28 23:44               ` Justin Patrin
2007-03-01  9:20                 ` Patrick Fischer
2007-03-01 14:49           ` Vladislav Grinchenko

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=1172658483.16062.23.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --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.