From: Paolo Broggini <pbroggini@softool.ch>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Problem building U-Boot for ARM target
Date: Tue, 11 Oct 2005 11:16:59 +0200 [thread overview]
Message-ID: <434B830B.4020405@softool.ch> (raw)
Dear all,
I'm using the GCC 3.2 toolchain for building U-Boot (current head of git) for an ARM target.
I get the following error:
cc1: invalid option 'abi=apcs-gnu'
This option (correct me if I'm wrong) was introduced with a recent patch by Peter Pearse.
Digging a bit in gcc.gnu.org it appears that this option comes only with GCC 4.0!
Is this a known behaviour?
BTW: removing this option from 'cpu/armxxx/config.mk' U-Boot builds fine!
Best regards
-P.Broggini
next reply other threads:[~2005-10-11 9:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 9:16 Paolo Broggini [this message]
2005-10-11 10:38 ` [U-Boot-Users] Re: Problem building U-Boot for ARM target Catalin Marinas
2005-10-11 12:14 ` Paolo Broggini
2005-10-11 12:48 ` Catalin Marinas
2005-10-11 13:22 ` Paolo Broggini
2005-10-11 13:44 ` Catalin Marinas
2005-10-11 14:07 ` Paolo Broggini
2005-10-11 14:32 ` Catalin Marinas
2005-10-11 15:33 ` Paolo Broggini
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=434B830B.4020405@softool.ch \
--to=pbroggini@softool.ch \
--cc=u-boot@lists.denx.de \
/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