From: Curt Brune <curt@cucy.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] ARM Tool chain Recommendation
Date: Mon, 7 Jun 2004 11:00:37 -0700 [thread overview]
Message-ID: <20040607110037.C4471@cucy.com> (raw)
In-Reply-To: <20040607170057.AB314C109F@atlas.denx.de>
> > Related question -- For u-boot does it matter whether to use arm-linux
> > or arm-elf tool chain?
>
> Explain the differerence?
Well I have one tool chain call "arm-linux-" and one called "arm-elf-"
that I installed. I don't remember where I got the arm-linux tools
from, but the arm-elf tools came from
http://www.uclinux.org/pub/uClinux/m68k-elf-tools/
localhost$ arm-linux-gcc -v
Reading specs from /usr/lib/gcc-lib/arm-linux/2.95.4/specs
gcc version 2.95.4 20010319 (prerelease/franzo/20011204)
localhost$ arm-elf-gcc -v
Reading specs from /usr/local/lib/gcc-lib/arm-elf/2.95.3/specs
gcc version 2.95.3 20010315 (release)(ColdFire patches - 20010318 from
http://fiddes.net/coldfire/)(uClinux XIP and shared lib patches from
http://www.snapgear.com/)
The strange thing is these compiler define slightly different macros
by default. For instance running "gcc -E -dM tmp.c" on an empty tmp.c
files gives the following in the two cases:
arm-linux-gcc -E -dM tmp.c
#define __linux__ 1
#define __ARM_ARCH_3__ 1
#define __arm__ 1
#define linux 1
#define __GNUC_MINOR__ 95
#define __CHAR_UNSIGNED__ 1
#define __unix 1
#define __unix__ 1
#define __APCS_32__ 1
#define __GNUC__ 2
#define __linux 1
#define __ELF__ 1
#define unix 1
arm-elf-gcc -E -dM tmp.c
#define __arm_elf 1
#define arm_elf 1
#define __arm__ 1
#define __arm 1
#define __arm_elf__ 1
#define __ARM_ARCH_4T__ 1
#define __GNUC_MINOR__ 95
#define arm 1
#define __CHAR_UNSIGNED__ 1
#define __APCS_32__ 1
#define __GNUC__ 2
#define __ELF__ 1
Now the problem I run into with u-boot is that the arm-elf-gcc
compiler defines the symbol "arm", which the arm-linux-gcc does not.
This causes a problem when compiling
u-boot/include/asm-arm/processor.h, which has a structure member named
"arm".
I can #undef arm and things work OK. Or I can use arm-linux-gcc.
For my uclinux work, however, I need to use arm-elf-gcc.
I was just wondering what tool to use for u-boot. I figured the answer
was "ELDK, or course".
--
========================================================================
Curt Brune | Phone 1.650.380.2528 | Managing Principal
curt at cucy.com | WWW www.cucy.com | Cucy Systems
========================================================================
Cucy Systems -- Software. Integration. Training.
========================================================================
next prev parent reply other threads:[~2004-06-07 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 16:26 [U-Boot-Users] ARM Tool chain Recommendation Curt Brune
2004-06-07 17:00 ` Wolfgang Denk
2004-06-07 18:00 ` Curt Brune [this message]
[not found] <20040607105849.B4471@cucy.com>
2004-06-07 18:04 ` Wolfgang Denk
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=20040607110037.C4471@cucy.com \
--to=curt@cucy.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.