public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] Annoying make debug messages at v2013.10-rc3
Date: Thu, 19 Sep 2013 14:49:52 +0200	[thread overview]
Message-ID: <20130919144952.3190ea6a@lilith> (raw)
In-Reply-To: <20130918130018.E621.AA925319@jp.panasonic.com>

Hi Masahiro,

On Wed, 18 Sep 2013 13:00:18 +0900, Masahiro Yamada
<yamada.m@jp.panasonic.com> wrote:

> Hello Albert.
> 
> 
> Commit 27af930e modified top Makefile as follows:
> 
>     --- a/Makefile
>     +++ b/Makefile
>     @@ -838,7 +838,7 @@ unconfig:
>      
>      sinclude $(obj).boards.depend
>      $(obj).boards.depend:  boards.cfg
>     -       @awk '(NF && $$1 !~ /^#/) { print $$1 ": " $$1 "_config; $$(MAKE)" }' $< > $@
>     +       @awk '(NF && $$1 !~ /^#/) { print $$7 ": " $$7 "_config; $$(MAKE) -d" }' $< > $@
>      
>      #
>      # Functions to generate common board directory names
> 
> 
> I thought adding -d option is not what you intended.
> 
> So, I posted a patch  "[U-Boot] Makefile: Do not show make debug messages"
> to delete -d option again.
> Does my patch seem to be OK?
> 
> 
> I am really suffering from lots of debug messages like follows:
> 
> 
> $ make CROSS_COMPILE=arm-linux-gnueabi- omap4_panda
> Configuring for omap4_panda board...
> make -d
> GNU Make 3.81
> Copyright (C) 2006  Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.
> There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
> PARTICULAR PURPOSE.
> 
> This program built for x86_64-pc-linux-gnu
> Reading makefiles...
> Reading makefile `Makefile'...
> Reading makefile `include/autoconf.mk.dep' (search path) (don't care) (no ~ expansion)...
> Reading makefile `include/autoconf.mk' (search path) (don't care) (no ~ expansion)...
> Reading makefile `include/config.mk' (search path) (no ~ expansion)...
> Reading makefile `/home/yamada/workspace/u-boot/config.mk' (search path) (no ~ expansion)...
> Reading makefile `/home/yamada/workspace/u-boot/include/generated/cc_options.mk' (search path) (don't care) (no ~ expansion)...
> Reading makefile `/home/yamada/workspace/u-boot/include/autoconf.mk' (search path) (don't care) (no ~ expansion)...
> Reading makefile `/home/yamada/workspace/u-boot/include/config.mk' (search path) (don't care) (no ~ expansion)...
> Reading makefile `/home/yamada/workspace/u-boot/arch/arm/config.mk' (search path) (don't care) (no ~ expansion)...
> Reading makefile `/home/yamada/workspace/u-boot/arch/arm/cpu/armv7/config.mk' (search path) (don't care) (no ~ expansion)...
> Reading makefile `/home/yamada/workspace/u-boot/arch/arm/cpu/armv7/omap4/config.mk' (search path) (don't care) (no ~ expansion)...
> Reading makefile `/home/yamada/workspace/u-boot/board/ti/panda/config.mk' (search path) (don't care) (no ~ expansion)...
> Reading makefile `.boards.depend' (search path) (don't care) (no ~ expansion)...
> Updating makefiles....
>  Considering target file `.boards.depend'.
>    Considering target file `boards.cfg'.
>     Looking for an implicit rule for `boards.cfg'.
>     Trying pattern rule with stem `boards.cfg'.
>     Trying implicit prerequisite `boards.cfg.o'.
>     Trying pattern rule with stem `boards.cfg'.
>     .....

Can you repost according to the patch posting guidelines at
http://www.denx.de/wiki/U-Boot/Patches so that the patch shows up
properly on patchwork and attributed to you?

Basically, generate the patch with git format-patch -s, and send it
with git send-email.

> Best Regards
> Masahiro Yamada
> 


Amicalement,
-- 
Albert.

  parent reply	other threads:[~2013-09-19 12:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-18  4:00 [U-Boot] Annoying make debug messages at v2013.10-rc3 Masahiro Yamada
2013-09-19  6:39 ` Albert ARIBAUD
2013-09-19  8:04   ` Masahiro Yamada
2013-09-19 16:02   ` Tom Rini
2013-09-19 12:49 ` Albert ARIBAUD [this message]
2013-09-19 13:47   ` Albert ARIBAUD

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=20130919144952.3190ea6a@lilith \
    --to=albert.u.boot@aribaud.net \
    --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