From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Tidy up 'make' output
Date: Tue, 17 Jun 2008 16:53:44 -0400 [thread overview]
Message-ID: <1213736024.32234.16.camel@dv> (raw)
In-Reply-To: <20080617203710.GA31785@thorin>
On Tue, 2008-06-17 at 22:37 +0200, Robert Millan wrote:
> I don't like the idea of hiding information this way.
If something fails, "make V=1" can be used to find the command.
> If the goal is to
> catch warnings, I think -Werror can do a much better job (and catching
> errors shouldn't be a problem unless you're using make -j or -k).
Even with -j and -k, rerunning make would show the error at the end.
But -Werror would not help for linker warnings and whatever else some
utility may want to tell users. Also, projects that use -Werror often
find the build fail because a new, stricter compiler finds warnings in
headers of older libraries.
Also, using -Werror would put pressure on developers to fix warnings in
a provisional way rather than address the real issue.
The GRUB build is especially noisy. It's hard to say what's being
generated at the given time without looking very closely. Shorter
output could possibly help improve the build system, because it would be
clear where the build is spending most of the time.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-06-17 20:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 17:44 [PATCH] Tidy up 'make' output Colin D Bennett
2008-06-17 19:57 ` Pavel Roskin
2008-06-17 20:07 ` Colin D Bennett
2008-06-17 20:25 ` Pavel Roskin
2008-06-17 20:37 ` Robert Millan
2008-06-17 20:53 ` Pavel Roskin [this message]
2008-06-17 22:22 ` Stefan Reinauer
2008-06-18 17:43 ` Robert Millan
2008-06-17 22:31 ` Colin D Bennett
2008-06-18 17:46 ` Robert Millan
2008-06-18 18:02 ` Pavel Roskin
2008-06-18 22:21 ` Robert Millan
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=1213736024.32234.16.camel@dv \
--to=proski@gnu.org \
--cc=grub-devel@gnu.org \
/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.