public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Angelos Manousarides <amanous@inaccessnetworks.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Compile error with arm-linux-gcc
Date: Tue, 06 Jun 2006 20:24:51 +0300	[thread overview]
Message-ID: <4485BA63.2020408@inaccessnetworks.com> (raw)

When trying to compile with this gcc:

Reading specs from 
/opt/inaccess/xdvl/toolchain/gcc-3.4.3-glibc-2.3.5/arm-linux/lib/gcc/arm-linux/3.4.3/specs
Configured with: 
/home/u0/amanous/crosstool-0.38/build/arm-linux/gcc-3.4.3-glibc-2.3.5/gcc-3.4.3/configure 
--target=arm-linux --host=i686-host_pc-linux-gnu 
--prefix=/opt/inaccess/xdvl/toolchain/gcc-3.4.3-glibc-2.3.5/arm-linux 
--with-float=soft 
--with-headers=/opt/inaccess/xdvl/toolchain/gcc-3.4.3-glibc-2.3.5/arm-linux/arm-linux/include 
--with-local-prefix=/opt/inaccess/xdvl/toolchain/gcc-3.4.3-glibc-2.3.5/arm-linux/arm-linux 
--disable-nls --enable-threads=posix --enable-symvers=gnu 
--enable-__cxa_atexit --enable-languages=c,c++ --enable-shared 
--enable-c99 --enable-long-long
Thread model: posix
gcc version 3.4.3

I get the following error:


cc1: error: invalid option `abi=apcs-gnu'
cc1: error: invalid option `abi=apcs-gnu'
...


There was a problem with the arm compilers and a fix was introduced in 
u-boot 1.1.4, in cpu/pxa/config.mk (this is one of the reasons I 
upgraded from 1.1.3). But it seems that this solution introduced this 
problem.

I have compiled and executed u-boot successfully with the line 
containing the offending flag commented.

--
Angelos Manousarides

                 reply	other threads:[~2006-06-06 17:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4485BA63.2020408@inaccessnetworks.com \
    --to=amanous@inaccessnetworks.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