From: Stelios Koroneos <skoroneos@digital-opsis.com>
To: openembedded-devel@openembedded.org
Subject: Re: How should OE be used?
Date: Tue, 25 Sep 2007 15:19:57 +0300 [thread overview]
Message-ID: <1190722797.46f8fced3640a@www.emile.com> (raw)
In-Reply-To: <D61182AC8012EA4EBC531B3AF23BE1093F1639@tranzeo-mail2.12stewart.tranzeo.com>
>
> I tried using OE, but could not get it to complete a build for PowerPC
> 405 (neither uclibc or glibc - both failed but in different ways.
> Uclibc gets cross compiler badness errors - I think it is part of this
> powerpc vs ppc stuff in Linux). After days of frustration, I had to
> bail out and use buildroot for this particular project instead.
> Obviously OE has lots of ARM and x86 users, but the PPC support falls
> behind because it isn't as popular. I'll check back for a later
> project.
>
Well, not sure when you tried it, what distro etc but the ppc405 targets in OE
work :)
Infact i am giving a presentation today at the Power.org developer conference in
Austin on powerpc/OE
As we needed a stable tree for our devices/projects we have our distro called
OPLinux and OPlinux-uclibc with gcc 4.1.1 glibc 2.5 or uclibc 0.9.28
We push the changes back to OE on a regular bases and recently provided Koen
with a 405 board so he can do more test on Angstrom which uses newer versions
of gcc/uclibc.
If you (or any other) want a copy of what we use just let me know.
Stelios
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
next prev parent reply other threads:[~2007-09-25 12:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-22 21:24 How should OE be used? Philip Balister
2007-09-23 11:19 ` Leon Woestenberg
2007-09-23 12:33 ` Koen Kooi
2007-09-24 17:20 ` Tim Bird
2007-09-24 17:43 ` Koen Kooi
2007-09-24 18:01 ` Tim Bird
2007-09-24 15:55 ` Tim Bird
2007-09-24 16:35 ` Philip Balister
2007-09-24 17:14 ` Tim Bird
2007-09-24 18:04 ` Leon Woestenberg
2007-09-24 19:23 ` Koen Kooi
2007-09-24 14:48 ` Darcy Watkins
2007-09-25 12:19 ` Stelios Koroneos [this message]
2007-09-25 15:15 ` Koen Kooi
2007-09-25 20:54 ` Darcy Watkins
2007-09-24 16:14 ` Cliff Brake
2007-09-24 18:36 ` Craig Hughes
2007-09-24 19:27 ` Philip Balister
2007-09-24 21:37 ` Richard Purdie
2007-09-24 18:48 ` Lorn Potter
2007-09-24 19:01 ` Craig Hughes
2007-09-24 19:39 ` Lorn Potter
2007-09-24 20:33 ` Craig Hughes
2007-09-24 20:52 ` Richard Purdie
2007-09-24 21:11 ` Lorn Potter
2007-09-24 22:35 ` Richard Purdie
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=1190722797.46f8fced3640a@www.emile.com \
--to=skoroneos@digital-opsis.com \
--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.