From: Nishanth Menon <nm@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Makefile: Do not show make debug messages
Date: Thu, 19 Sep 2013 08:00:01 -0500 [thread overview]
Message-ID: <523AF551.4010108@ti.com> (raw)
In-Reply-To: <1379473287-31492-1-git-send-email-yamada.m@jp.panasonic.com>
On 09/17/2013 10:01 PM, Masahiro Yamada wrote:
> In commit 27af930, the top Makefile was adjusted to the new
> boards.cfg format.
>
> But at the same time, -d option was added.
>
> If you configure and make separately, for example
> like follows:
>
> make omap4_panda_config
> make CROSS_COMPILE=<your_compiler_prefix>
>
> it works fine as it did before.
>
> But if you do them in one time like follows:
>
> make omap4_panda CROSS_COMPILE=<your_compiler_prefix>
>
> The log is sprinkled with annoying make debug messages.
>
> This commit deletes -d option again.
>
> Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
> ---
> Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Makefile b/Makefile
> index 28ddb7e..bc639b3 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -838,7 +838,7 @@ unconfig:
>
> sinclude $(obj).boards.depend
> $(obj).boards.depend: boards.cfg
> - @awk '(NF && $$1 !~ /^#/) { print $$7 ": " $$7 "_config; $$(MAKE) -d" }' $< > $@
> + @awk '(NF && $$1 !~ /^#/) { print $$7 ": " $$7 "_config; $$(MAKE)" }' $< > $@
>
> #
> # Functions to generate common board directory names
>
Thanks - this helped me.
Before log: http://pastebin.com/92HdiQdP
After log: http://pastebin.com/7UnYdajd
Tested-by: Nishanth Menon <nm@ti.com>
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2013-09-19 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 3:01 [U-Boot] [PATCH] Makefile: Do not show make debug messages Masahiro Yamada
2013-09-19 13:00 ` Nishanth Menon [this message]
2013-09-19 13:41 ` Nishanth Menon
2013-09-21 12:07 ` [U-Boot] " Tom Rini
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=523AF551.4010108@ti.com \
--to=nm@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox