From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Building for i486 based non-FPU device
Date: Mon, 26 Jan 2009 21:08:16 +0100 [thread overview]
Message-ID: <gll57g$5s3$2@ger.gmane.org> (raw)
In-Reply-To: <497D7E2A.8050302@gmail.com>
On 26-01-09 10:11, Marco Cavallini wrote:
> Hello,
> This discussion was in thread "FOSDEM OE stand"
> I'm trying to build for a machine I'd like to let at OE stand.
> http://www.koala.it/it/nanopc.htm
> It's a i486 based non-FPU device (Vortex86sx), so I tried to build
>
> DISTRO = "angstrom-2008.1"
>
> I created my new machine copying it from
> conf/machine/i586-generic.conf
> and changing the following settings:
> TARGET_ARCH = "i486"
> PACKAGE_EXTRA_ARCHS = "x86"
> PREFERRED_VERSION_linux = "2.6.26"
> (I also changed 2.6.26 recipe)
>
> I found several problems:
> i586-generic uses TARGET_ARCH = "i586" : ok but for 586
> x86 uses TARGET_ARCH = "i586" : build broken
> qemux86 uses TARGET_ARCH = "i586" : not used
> i486-generic uses TARGET_ARCH = "i486" : build broken
>
> No one of the previous tested build give a useful result,
> what could I change to get a running system?
>
> Maybe do I have to specify TARGET_CC_ARCH = "-march=i486" ?
> Would be better to switch this discussion to IRC ?
> Any hint will be greatly appreciated.
'MACHINE=vortex86sx bitbake glibc' works for me with angstrom. It
doesn't use softfloat yes, as gccs configure script doesn't like
--with-float=soft, so we'll problably end up messing with TARGET_CC_ARCH.
regards,
Koen
next prev parent reply other threads:[~2009-01-26 20:17 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
2009-01-26 13:41 ` Philip Balister
2009-01-26 20:08 ` Koen Kooi [this message]
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='gll57g$5s3$2@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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.