From: "Ulf Samuelsson" <ulf@atmel.com>
To: <openembedded-devel@openembedded.org>
Subject: qemu-native failure on Angstrom
Date: Mon, 14 May 2007 15:14:03 +0200 [thread overview]
Message-ID: <07a101c7962b$e0db5860$0200a8c0@atmel.com> (raw)
Tried building OpenEmbedded for the first time, DISTRO=Ångström,
with an at91sam9263 target (made my own file) but it seems that
qemu.native is not compilable on my OpenSuSE 10.1 system using gcc-4.1.2.
The error message says that qemu has only been tested on gcc-4.x.x for arm
and that other architectures need gcc-3.x
Tried to update the bb files to allow gcc-4.1.2 but that resulted in
qemu-arm not beeing built, causing the build to terminate later.
Is there any way to have open embedded build a gcc-3.4.4 cross compiler
as part of the normal build.
Best Regards
Ulf Samuelsson
next reply other threads:[~2007-05-14 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 13:14 Ulf Samuelsson [this message]
2007-05-14 13:40 ` qemu-native failure on Angstrom Koen Kooi
2007-05-14 13:46 ` Alberto García Hierro
2007-05-14 14:13 ` Paul Sokolovsky
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='07a101c7962b$e0db5860$0200a8c0@atmel.com' \
--to=ulf@atmel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox