From: Linux RegaTech <linux@regatech.dk>
To: u-boot@lists.denx.de
Subject: [U-Boot] Error compiling UBOOT 1.3.4 for AT91RM9200
Date: Sat, 29 Nov 2008 14:14:18 +0100 [thread overview]
Message-ID: <C410D14EF364463CB46F507FBF5B0760@RGLAPTOP> (raw)
Hello UBOOT mailinglist
I have encountered a problem when i try to compile any newer version of UBOOT than V1.2.0 for AT91RM9200,
below is given the output from console when i try to compile the UBOOT V1.3.4 for AT91RM9200,
could anybody please give me a hint what a solution to this problem might could be:
In file included from fdt_host.h:25,
from mkimage.h:36,
from mkimage.c:25:
../include/libfdt.h: In function `fdt_set_magic':
../include/libfdt.h:162: warning: implicit declaration of function `__cpu_to_be32'
In file included from mkimage.c:26:
/home/Rene/uboot134/include/image.h: At top level:
/home/Rene/uboot134/include/image.h:202: error: parse error before "ulong"
/home/Rene/uboot134/include/image.h:224: error: parse error before '}' token
/home/Rene/uboot134/include/image.h:334: error: parse error before "image_get_data"
/home/Rene/uboot134/include/image.h: In function `image_get_data':
/home/Rene/uboot134/include/image.h:336: error: `ulong' undeclared (first use in this function)
/home/Rene/uboot134/include/image.h:336: error: (Each undeclared identifier is reported only once
/home/Rene/uboot134/include/image.h:336: error: for each function it appears in.)
/home/Rene/uboot134/include/image.h:336: error: parse error before "hdr"
/home/Rene/uboot134/include/image.h: At top level:
/home/Rene/uboot134/include/image.h:343: error: parse error before "image_get_image_end"
/home/Rene/uboot134/include/image.h: In function `image_get_image_end':
/home/Rene/uboot134/include/image.h:345: error: `ulong' undeclared (first use in this function)
/home/Rene/uboot134/include/image.h:345: error: parse error before "hdr"
/home/Rene/uboot134/include/image.h: At top level:
/home/Rene/uboot134/include/image.h:402: error: parse error before "image_multi_count"
/home/Rene/uboot134/include/image.h:403: error: parse error before "ulong"
/home/Rene/uboot134/include/image.h:477: error: parse error before "ulong"
/home/Rene/uboot134/include/image.h:479: error: parse error before "ulong"
/home/Rene/uboot134/include/image.h:493: error: parse error before "fit_get_size"
/home/Rene/uboot134/include/image.h:505: error: parse error before "fit_get_end"
/home/Rene/uboot134/include/image.h: In function `fit_get_end':
/home/Rene/uboot134/include/image.h:507: error: `ulong' undeclared (first use in this function)
/home/Rene/uboot134/include/image.h:507: error: parse error before "fit"
/home/Rene/uboot134/include/image.h: At top level:
/home/Rene/uboot134/include/image.h:532: error: parse error before "ulong"
/home/Rene/uboot134/include/image.h:533: error: parse error before "ulong"
make[1]: *** [mkimage.o] Error 1
make: *** [tools] Error 2
Thanks in advance.
Best regards
Ren?
next reply other threads:[~2008-11-29 13:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-29 13:14 Linux RegaTech [this message]
2008-12-01 7:51 ` [U-Boot] Error compiling UBOOT 1.3.4 for AT91RM9200 Mohamed Thalib .H
2008-12-01 10:34 ` Jean-Christophe PLAGNIOL-VILLARD
2008-12-01 12:59 ` [U-Boot] Uboot AS Space in MPC85xx Start.S Vignesh Kumar B
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=C410D14EF364463CB46F507FBF5B0760@RGLAPTOP \
--to=linux@regatech.dk \
--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