From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot build error [from v2013.01 onwards]
Date: Mon, 28 Jan 2013 07:59:29 +0100 [thread overview]
Message-ID: <20130128065929.38FD825922C@gemini.denx.de> (raw)
In-Reply-To: <CAD6G_RS1bV_8z_J0QEjbNooy=6+Zxi0faXjxNr1fN4U2ajbObg@mail.gmail.com>
Dear Jagan Teki,
In message <CAD6G_RS1bV_8z_J0QEjbNooy=6+Zxi0faXjxNr1fN4U2ajbObg@mail.gmail.com> you wrote:
>
> > Actually I'd be more interested in the result of the following commands:
> >
> > 1) $CROSS_COMPILE}gcc -v
>
> Mr.J> ${CROSS_COMPILE}gcc -v
> Using built-in specs.
> Target: arm-none-linux-gnueabi
> ....
> Thread model: posix
> gcc version 4.4.1 (Sourcery G++ Lite 2010q1-202)
Well, the actual error comes from the Makefile, so gcc should not be
involved here...
> Mr.J> git rev-parse HEAD
> 54b08efcf2f4ff532ce99c53f341a59c193331a5
Looks clean.
> Mr.J> git status
> # On branch master
> nothing to commit (working directory clean)
>
> Mr.J> ./MAKEALL versatilepb_config
> Makefile:597: *** missing `endif'. Stop.
> Makefile:597: *** missing `endif'. Stop.
> arm-none-linux-gnueabi-size: './u-boot': No such file
> Makefile:597: *** missing `endif'. Stop.
You should get this instead:
-> ./MAKEALL versatilepb_config
make: *** No rule to make target `versatilepb_config_config'. Stop.
make: *** [versatilepb_config_config] Error 1
make: *** [all] Error 1
arm-linux-gnueabi-size: './u-boot': No such file
System not configured - see README
make: *** [all] Error 1
--------------------- SUMMARY ----------------------------
Boards compiled: 1
Boards with errors: 1 ( versatilepb_config )
----------------------------------------------------------
Note that the correct name with MAKEALL is the board target name
_without_ the "_config" part. What does "make -v" report for you?
[GNU Make 3.82 on my end.]
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
[War] is instinctive. But the instinct can be fought. We're human
beings with the blood of a million savage years on our hands! But we
can stop it. We can admit that we're killers ... but we're not going
to kill today. That's all it takes! Knowing that we're not going to
kill today!
-- Kirk, "A Taste of Armageddon", stardate 3193.0
next prev parent reply other threads:[~2013-01-28 6:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 13:04 [U-Boot] u-boot build error [from v2013.01 onwards] Jagan Teki
2013-01-26 16:10 ` Albert ARIBAUD
2013-01-27 1:40 ` Jagan Teki
2013-01-27 3:54 ` Vikram Narayanan
2013-01-27 7:00 ` Jagan Teki
2013-01-27 15:14 ` Albert ARIBAUD
2013-01-28 6:00 ` Jagan Teki
2013-01-28 6:59 ` Wolfgang Denk [this message]
2013-01-28 8:01 ` Jagan Teki
2013-01-28 8:10 ` Jagan Teki
2013-01-28 11:34 ` Wolfgang Denk
2013-01-28 13:25 ` Jagan Teki
2013-01-28 11:32 ` 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=20130128065929.38FD825922C@gemini.denx.de \
--to=wd@denx.de \
--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