From: Shawn Jin <shawnxjin@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] uboot compilation error when using the toolchain arm-elf-tools from uClinux.org
Date: Mon, 9 Aug 2004 17:01:27 -0700 [thread overview]
Message-ID: <c3d0340b0408091701f3c1e29@mail.gmail.com> (raw)
Hi,
I checked out u-boot code from CVS today and tried to compile it for
ARM IntegratorCP board. The cross toolchain I used is arm-elf-tools
downloaded from uClinux.org. Unfortunately I got the following
compilation error.
arm-elf-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8
-mshort-load-bytes -msoft-float
-D__KERNEL__ -DTEXT_BASE=0x01000000 -I/u/code/denx/u-boot/include
-fno-builtin -ffreestandin
g -nostdinc -isystem /usr/local/lib/gcc-lib/arm-elf/2.95.3/include
-pipe -DCONFIG_ARM -D__ARM__ -
mapcs-32 -march=armv4 -Wall -Wstrict-prototypes -c -o cfi_flash.o cfi_flash.c
In file included from cfi_flash.c:48:
/u/code/denx/u-boot/include/asm/processor.h:52: parse error before `1'
/u/code/denx/u-boot/include/asm/processor.h:52: warning: no semicolon
at end of struct or union
/u/code/denx/u-boot/include/asm/processor.h:54: parse error before `}'
/u/code/denx/u-boot/include/asm/processor.h:58: field `insn' has incomplete type
The code is extracted from the header file processor.h.
51> union debug_insn {
52> u32 arm;
53> u16 thumb;
54> };
55>
56> struct debug_entry {
57> u32 address;
58> union debug_insn insn;
59> };
However I really don't think there is any syntax error. It might be a
toolchain problem?
--
Best regards,
Shawn Jin
next reply other threads:[~2004-08-10 0:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 0:01 Shawn Jin [this message]
2004-08-10 0:14 ` [U-Boot-Users] Re: [uClinux-dev] uboot compilation error when using the toolchain arm-elf-tools from uClinux.org David McCullough
2004-08-10 1:41 ` [U-Boot-Users] " Shawn Jin
2004-08-10 3:22 ` David McCullough
2004-08-10 6:43 ` [U-Boot-Users] " 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=c3d0340b0408091701f3c1e29@mail.gmail.com \
--to=shawnxjin@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.