All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Problem with building glibc
Date: Fri, 21 May 2010 11:58:41 +0200	[thread overview]
Message-ID: <201005211158.42460.marcin@juszkiewicz.com.pl> (raw)
In-Reply-To: <AANLkTilad9w4Dh67o_qqPaTHJRTvLBKrI7YbkUNl4A6G@mail.gmail.com>

Dnia piątek, 21 maja 2010 o 11:48:24 Grzegorz Toporek napisał(a):

> I would love to work with angstrom, however I'm using Colibri evaluation
> board with Intel® PXA270 Processor (this is a students project and I can't
> change it). Is it possible to run system built for angstrom on my board or
> I just miss something?!

Angstrom supports nearly every board which OpenEmbedded supports. Colibri is 
just another device. Build Angstrom for it, use it and you will soon find out 
how much work you do not have to do due to feeds with already built software.

Making own distribution and then properly maintain it is lot of work and I 
would never suggest that for someone who just started with OpenEmbedded.

Also one thing: do not use tune-iwmmxt for Colibri. This does not give any 
special improvements for system. Add "iwmmxt" to MACHINE_FEATURES like it is 
in few machines already - this will give you optimized versions of those 
packages where it is really worth to enable that.

And do not get flooded by Wisła :D

Regards, 
-- 
JID:      hrw@jabber.org
Website:  http://marcin.juszkiewicz.com.pl/
LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz





  reply	other threads:[~2010-05-21 10:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-20 21:51 Problem with building glibc Grzegorz Toporek
2010-05-20 22:44 ` Koen Kooi
2010-05-21  0:21 ` Khem Raj
2010-05-21  7:44 ` Michael Lippautz
2010-05-21  9:48   ` Grzegorz Toporek
2010-05-21  9:58     ` Marcin Juszkiewicz [this message]
2010-05-21 10:08       ` Grzegorz Toporek

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=201005211158.42460.marcin@juszkiewicz.com.pl \
    --to=marcin@juszkiewicz.com.pl \
    --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.