From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/doc: use silent-rules.mk in the Makefile
Date: Fri, 12 Apr 2024 21:31:06 +0300 [thread overview]
Message-ID: <868r1isaad.fsf@gnu.org> (raw)
In-Reply-To: <09d4a16a33cf31f558a8982075800b113ed4a14e.1712940998.git.aburgess@redhat.com> (message from Andrew Burgess on Fri, 12 Apr 2024 18:00:23 +0100)
> From: Andrew Burgess <aburgess@redhat.com>
> Cc: Andrew Burgess <aburgess@redhat.com>
> Date: Fri, 12 Apr 2024 18:00:23 +0100
>
> Make use of silent-rules.mk when building the GDB docs.
>
> Most of these are pretty straight forward, adding ECHO_GEN and then
> lots of SILENCE prefixes.
>
> I added a new SILENT_QUIET_FLAG to silent-rules.mk, this is like
> SILENT_FLAG, but is set to '-q' when in silent mode, this can be used
> with the 'dvips' and 'texi2dvi' commands, both of which use '-q' to
> mean: only report errors.
>
> As with the rest of the GDB makefiles, I've only converted the
> "generation" rules to use silent-rules.mk, the install / uninstall
> rules are left unchanged.
>
> There are still a few "generation" targets that produce output, there
> seems to be no flag to silence the 'tex' and 'pdftex' commands which
> some recipes use, I've not worried about these for now, e.g. the
> refcard.dvi and refcard.pdf targets still produce some output.
>
> Luckily, when doing a 'make all' in the gdb/ directory, we only build
> the info docs by default, and those rules are now nice and silent, so
> a complete GDB build is now looking nice and quiet by default.
> ---
> gdb/doc/Makefile.in | 158 ++++++++++++++++++++++++--------------------
> gdb/silent-rules.mk | 1 +
> 2 files changed, 86 insertions(+), 73 deletions(-)
Doesn't this silence too much? Can you should the output of each rule
after the changes?
Thanks.
next prev parent reply other threads:[~2024-04-12 18:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 17:00 Andrew Burgess
2024-04-12 18:31 ` Eli Zaretskii [this message]
2024-04-12 22:32 ` Andrew Burgess
2024-04-13 7:02 ` Eli Zaretskii
2024-04-15 13:55 ` Andrew Burgess
2024-04-15 14:18 ` Simon Marchi
2024-04-16 7:48 ` Andrew Burgess
2024-04-16 8:47 ` Andrew Burgess
2024-04-16 15:01 ` Simon Marchi
2024-04-17 21:00 ` Andrew Burgess
2024-05-08 17:46 ` Andrew Burgess
2024-05-26 18:20 ` Joel Brobecker
2024-05-26 22:02 ` Andrew Burgess
2024-05-26 22:58 ` Andrew Burgess
2024-05-28 15:25 ` Tom Tromey
2024-04-15 14:37 ` Eli Zaretskii
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=868r1isaad.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).