From: Marco Cavallini <koansoftware@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Building for i486 based non-FPU device
Date: Mon, 26 Jan 2009 14:11:46 +0100 [thread overview]
Message-ID: <497DB692.1040100@gmail.com> (raw)
In-Reply-To: <glk6k7$ks8$1@ger.gmane.org>
Koen Kooi ha scritto:
> On 26-01-09 11:49, Phil Blundell wrote:
>> On Mon, 2009-01-26 at 10:11 +0100, Marco Cavallini wrote:
>>> DISTRO = "angstrom-2008.1"
>>
>> It might be worth trying with "minimal" to start with, just to eliminate
>> any angstrom-related uncertainties.
>
> Quite the reverse, minimal is perputually broken in OE, while angstrom
> has working x86 targets. Not i486sx targets, but it's straightforward to
> add such a target.
I also thought it was a straightforward task, but I was wrong.
What's missing in what I did until now?
--
Marco Cavallini
next prev parent reply other threads:[~2009-01-26 13:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 9:11 Building for i486 based non-FPU device Marco Cavallini
2009-01-26 10:49 ` Phil Blundell
2009-01-26 11:17 ` Marco Cavallini
2009-01-26 11:25 ` Koen Kooi
2009-01-26 13:11 ` Marco Cavallini [this message]
2009-01-26 13:41 ` Philip Balister
2009-01-26 20:08 ` Koen Kooi
2009-01-27 8:04 ` Marco Cavallini
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=497DB692.1040100@gmail.com \
--to=koansoftware@gmail.com \
--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