public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: Problem building U-Boot for ARM target
Date: Tue, 11 Oct 2005 11:38:11 +0100	[thread overview]
Message-ID: <tnxhdboz6cs.fsf@arm.com> (raw)
In-Reply-To: <434B830B.4020405@softool.ch> (Paolo Broggini's message of "Tue, 11 Oct 2005 11:16:59 +0200")

Paolo Broggini <pbroggini@softool.ch> wrote:
> 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!

That's true but the cc-option checker should use -mapcs-32 if it is
available, otherwise it will fall back to -mabi=apcs-gnu. It looks
like your compiler doesn't support the first option either. In this
case, I'm not sure it worked before Peter's patch. What CPU is it?

You could try the following in your config.mk but you should
investigate why -mapcs-32 doesn't work:

PLATFORM_CPPFLAGS +=$(call cc-option,-mapcs-32,$(call cc-option,-mabi=apcs-gnu,))

-- 
Catalin

  reply	other threads:[~2005-10-11 10:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-11  9:16 [U-Boot-Users] Problem building U-Boot for ARM target Paolo Broggini
2005-10-11 10:38 ` Catalin Marinas [this message]
2005-10-11 12:14   ` [U-Boot-Users] " 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
     [not found] <89A528FE6DB0FA44877BB2F05B8467180331C12C@ZIPPY.Emea.Arm.com>
2005-10-12  8:46 ` Paolo Broggini
     [not found] <89A528FE6DB0FA44877BB2F05B8467180331C407@ZIPPY.Emea.Arm.com>
2005-10-12 12:26 ` 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=tnxhdboz6cs.fsf@arm.com \
    --to=catalin.marinas@arm.com \
    --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