From: Simon Marchi <simon.marchi@ericsson.com>
To: Simon Marchi <simon.marchi@polymtl.ca>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2] Add silent Makefile rules
Date: Fri, 16 Mar 2018 20:32:00 -0000 [thread overview]
Message-ID: <ac723aca-e27c-4489-4256-4038a291ab69@ericsson.com> (raw)
In-Reply-To: <20180303182721.19009-1-simon.marchi@polymtl.ca>
On 2018-03-03 01:27 PM, Simon Marchi wrote:
> New in v2:
>
> - Enable Automake silent mode for our gnulib builds.
> - Replace CC with CXX, LD with CXXLD.
>
> Many projects (e.g. the Linux kernel) and build systems use "silent"
> rules, which means that they'll only print a summary of what's being
> done instead of printing all the detailed command lines. While chatting
> on the #gdb IRC channel, I realized a few people (including me) thought
> it would be nice to have it in GDB too.
>
> The idea is that too much text is not useful, the important information
> gets lost. If there's only the essential information, it's more likely
> to be useful. Most of the time, when I look at the build output, it's
> to see how it's progressing. By just printing a brief summary of each
> operation, I can easily spot what's currently being compiled and
> therefore how the build progresses (with time you know the order in
> which files are compiled almost by heart).
>
> As with other projects (Linux, automake-based things, probably others),
> it's possible to print the complete command lines by passing V=1 to make
> (or any other non-zero value).
>
> I had one hesitation about this: when people report build failures, we
> are more likely to miss the full compile command line. We'll probably
> sometimes need to ask people to include the build log with "make V=1".
> I don't think it's a big downside, if other projects the size of the
> Linux kernel can live with it, I'm sure we can too.
I pushed this patch.
Simon
prev parent reply other threads:[~2018-03-16 20:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 20:21 [PATCH] " Simon Marchi
2018-03-02 20:25 ` Simon Marchi
2018-03-03 8:09 ` Eli Zaretskii
2018-03-03 18:06 ` Simon Marchi
2018-03-03 7:54 ` Eli Zaretskii
2018-03-03 14:39 ` Simon Marchi
2018-03-03 18:27 ` [PATCH v2] " Simon Marchi
2018-03-16 20:32 ` Simon Marchi [this message]
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=ac723aca-e27c-4489-4256-4038a291ab69@ericsson.com \
--to=simon.marchi@ericsson.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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