public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] make make quiet
Date: Mon, 05 Jan 2009 22:13:24 +0100	[thread overview]
Message-ID: <20090105211324.87EC48387CDB@gemini.denx.de> (raw)
In-Reply-To: <20090105195311.GA24702@ld0162-tx32.am.freescale.net>

Dear Scott,

In message <20090105195311.GA24702@ld0162-tx32.am.freescale.net> you wrote:
>
> > But that's the preferred way of doing things, at least according to
> > Unix Philosophy.
> 
> Let's not get so bogged down in following some overgeneralized philosophy
> that we ignore the preferences of users.

Well, users are often in dire need to learn about the philosophical
background of a design.

> Besides, if you really wanted the build to be like a typical Unix tool,
> shouldn't -s be default, and verbose an option?  Patches of this sort get
> closer to that.

I have to admit that I almost always just run "./MAKEALL boardname",
which actually is as silent as "-s" (but it stores the *full* log in
case anything goes wrong).

> Most people don't use -s, and this will make more people see warnings.

Most people don;t use out of tree building either,  and  most  people
never run MAKEALL, not even before submitting patches.

That's the line of "a billion flies can't be wrong, you know.

> > U-Boot is the wrong place to fix this. Please fix this in make, for
> > the benefit of others, too.
> 
> Hmm, the best make could reasonably do on its own would be to print the
> name of each target, but that could get cluttered with intermediate and
> fake targets.  While such an option would be very nice, I don't think it
> should preclude makefile support for nicer output.

"make" knows exactly when it is running $(CC) or $(AS)  or  $(AR)  or
$(LD)  etc.,  so it can do automatically what now everybody is adding
to a zillion of innocent Makefiles.

Sorry, but the make process is complicated enough without this  fancy
stuff.  Every  now and then it shows funny behaviour. Just searcht he
archives for obscure build errors on ext3 but  not  on  NFS  or  vice
versa.  If  ther eis a real "make" expert here, there are many better
places to invest efforts for improvement. A semi-silent build is far,
far down on th list.

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
"In the long run, every program becomes rococo, and then rubble."
- Alan Perlis

  reply	other threads:[~2009-01-05 21:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-30 11:20 [U-Boot] [PATCH] make make quiet kenneth johansson
2008-12-30 22:14 ` Wolfgang Denk
2008-12-30 22:28   ` Scott Wood
2008-12-30 23:30     ` Wolfgang Denk
2008-12-31  9:23   ` kenneth johansson
2008-12-31  9:46     ` Mike Frysinger
2008-12-31 10:06       ` kenneth johansson
2008-12-31 11:15         ` Mike Frysinger
2008-12-31 12:04           ` kenneth johansson
2008-12-31 19:47     ` Wolfgang Denk
2009-01-05 19:53       ` Scott Wood
2009-01-05 21:13         ` Wolfgang Denk [this message]
2009-01-05 20:30       ` Remy Bohmer
2009-01-05 21:20         ` Wolfgang Denk
2009-01-06 20:16 ` Robert Schwebel
  -- strict thread matches above, loose matches on Subject: below --
2008-12-30  8:25 kenneth johansson
2008-12-30 10:48 ` Wolfgang Denk
2008-12-30 11:07   ` kenneth johansson
2008-12-30 21:46     ` Wolfgang Denk
2008-12-31  9:11 ` Mike Frysinger

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=20090105211324.87EC48387CDB@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