From: 25an <mans.zigher@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Can't Compile u-boot-1.1.5_atmel_1.2!!
Date: Tue, 27 Feb 2007 00:54:51 -0800 (PST) [thread overview]
Message-ID: <9177624.post@talk.nabble.com> (raw)
Hi!
I am trying to compile u-boot-1.1.5 for at91sam9261ek with arm926ejs cpu. I
am using the eldk
cross toolchain 4.1 which is using gcc 4.0.0.
When I try to compile u-boot I get following error
25an at 25an-desktop :/opt/x-compile/eldk/workingare
a/u-boot-1.1.5_atmel_1.2$ make ARCH=arm CROSS_COMPILE=arm-linux-
for dir in tools examples post post/cpu ; do make -C $dir _depend ; done
make[1]: Entering directory `/opt/x-compile/eldk/workingarea/u-
boot-1.1.5_atmel_1.2/tools'
make[1]: Nothing to be done for `_depend'.
make[1]: Leaving directory
`/opt/x-compile/eldk/workingarea/u-boot-1.1.5_atmel_1.2/tools'
make[1]: Entering directory `/opt/x-compile/eldk/workingarea/u-
boot-1.1.5_atmel_1.2/examples'
make[1]: Nothing to be done for `_depend'.
make[1]: Leaving directory
`/opt/x-compile/eldk/workingarea/u-boot-1.1.5_atmel_1.2/examples'
make[1]: Entering directory `/opt/x-compile/eldk/workingarea/u-
boot-1.1.5_atmel_1.2/post'
make[1]: Nothing to be done for `_depend'.
make[1]: Leaving directory
`/opt/x-compile/eldk/workingarea/u-boot-1.1.5_atmel_1.2/post'
make[1]: Entering directory `/opt/x-compile/eldk/workingarea/u-
boot-1.1.5_atmel_1.2/post/cpu'
make[1]: Nothing to be done for `_depend'.
make[1]: Leaving directory
`/opt/x-compile/eldk/workingarea/u-boot-1.1.5_atmel_1.2/post/cpu'
make -C tools all
make[1]: Entering directory `/opt/x-compile/eldk/workingarea/u-
boot-1.1.5_atmel_1.2/tools'
make[1]: Leaving directory
`/opt/x-compile/eldk/workingarea/u-boot-1.1.5_atmel_1.2/tools'
make -C examples all
make[1]: Entering directory
`/opt/x-compile/eldk/workingarea/u-boot-1.1.5_atmel_1.2/examples '
arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8
-msoft-float -fno-strict-aliasing -fno-common -ffixed-r8 -msoft-float
-D__KERNEL__ -DTEXT_BASE=0x23f00000 -I/opt/x-compile/eldk/workingarea/u-
boot-1.1.5_atmel_1.2/include -fno-builtin -ffreestanding -nostdinc -isystem
/opt/x-compile/eldk/usr/bin/../lib/gcc/arm-linux/4.0.0/include -pipe
-DCONFIG_ARM -D__ARM__ -march=armv4 -mabi=apcs-gnu -mapcs-32 -march=armv5te
-mtune=arm926ejs -Wall -Wstrict-prototypes -c -o hello_world.o hello_world.c
cc1: error: invalid option 'apcs-32'
hello_world.c:1: error: bad value (arm926ejs) for -mtune= switch
make[1]: *** [hello_world.o] Error 1
make[1]: Leaving directory `/opt/x-compile/eldk/workingarea/u-
boot-1.1.5_atmel_1.2/examples'
make: *** [examples] Error 2
Any ideas?
I would also appreciate any suggestion how to locate the error since right
now I have not even managed to locate were the flag is set.
Thanks
--
View this message in context: http://www.nabble.com/Can%27t-Compile-u-boot-1.1.5_atmel_1.2%21%21-tf3299257.html#a9177624
Sent from the Uboot - Users mailing list archive at Nabble.com.
next reply other threads:[~2007-02-27 8:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 8:54 25an [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-27 15:21 [U-Boot-Users] Can't Compile u-boot-1.1.5_atmel_1.2!! Daniel Hobi
2007-02-27 8:49 Måns Zigher
2007-02-27 9:44 ` Daniel Hobi
2007-02-27 14:23 ` 25an
2007-02-27 15:15 ` Daniel Hobi
2007-02-27 15:41 ` 25an
2007-02-27 16:09 ` 25an
2007-02-28 11:35 ` 25an
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=9177624.post@talk.nabble.com \
--to=mans.zigher@gmail.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 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.