From: Verma <ubootusers@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Errors while executing 'make' for u-boot-1.1.6 for incaip board
Date: Wed, 12 Sep 2007 03:41:23 -0700 (PDT) [thread overview]
Message-ID: <12632914.post@talk.nabble.com> (raw)
Hi ,
Errors are generated ,when I am trying to create the u-boot.bin for
u-boot-1.1.6 version using the following commands.
-make incaip_config
-make / make all
The errors generated are as follows:make[1]: Entering directory
`/opt/u-boot-1.1.6/post/cpu'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/opt/u-boot-1.1.6/post/cpu'
make -C common/
make[1]: Entering directory `/opt/u-boot-1.1.6/common'
mips_4KC-gcc -g -Os -D__KERNEL__ -DTEXT_BASE=0xB0000000
-I/opt/u-boot-1.1.6/include -fno-builtin -ffreestanding -nostdinc -isystem
/usr/lib/gcc-lib/mips-linux/2.95.4/include -pipe -DCONFIG_MIPS -D__MIPS__
-mcpu=4kc -EB -mabicalls -Wall -Wstrict-prototypes -c -o cmd_bootm.o
cmd_bootm.c
cmd_bootm.c:477: warning: preprocessing directive not recognized within
macro arg
cmd_bootm.c:477: warning: preprocessing directive not recognized within
macro arg
cmd_bootm.c:469: undefined or invalid # directive
cmd_bootm.c:475: undefined or invalid # directive
make[1]: *** [cmd_bootm.o] Error 1
make[1]: Leaving directory `/opt/u-boot-1.1.6/common'
make: *** [common/libcommon.a] Error 2
How can I avoid these errors, should I make any particular modifications to
any of the Makefiles.Please let me know.
Verma.
--
View this message in context: http://www.nabble.com/Errors-while-executing-%27make%27-for-u-boot-1.1.6-for-incaip-board-tf4428422.html#a12632914
Sent from the Uboot - Users mailing list archive at Nabble.com.
next reply other threads:[~2007-09-12 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-12 10:41 Verma [this message]
2007-09-12 13:02 ` [U-Boot-Users] Errors while executing 'make' for u-boot-1.1.6 for incaip board 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=12632914.post@talk.nabble.com \
--to=ubootusers@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.