From: Simon Marchi <simark@simark.ca>
To: Andrew Burgess <aburgess@redhat.com>, Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/doc: use silent-rules.mk in the Makefile
Date: Mon, 15 Apr 2024 10:18:21 -0400 [thread overview]
Message-ID: <81120371-21de-45ab-8ea7-bd8146a7f7a3@simark.ca> (raw)
In-Reply-To: <874jc2ivcb.fsf@redhat.com>
On 4/15/24 9:55 AM, Andrew Burgess wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>> So my preference would be for having the above emit something like the
>> below instead
>>
>> TEXI2POD gdb.pod
>> POD2MAN1 gdb.1
>
> That one's harder. The target information comes from make's $@
> variable, so it's easy enough to do:
>
> TEXI2POD gdb.1
> POD2MAN gdb.1
>
> which isn't exactly what you asked for.
Could you split the rule in two? One rule generating gdb.pod and one
rule generating gdb.1.
I personally think the original output from Andrew's patch is fine. In
the silent mode, all I need to know is that make is currently working on
getting gdb.1 generated. The intermediary gdb.pod file is an
implementation detail of the rule. If I want to see it, then I'll use
`make V=1`.
But if it makes everyone happy, I don't mind if we split the rule in
two. Smaller and simpler rules are easier to understand.
Simon
next prev parent reply other threads:[~2024-04-15 14:18 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
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 [this message]
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=81120371-21de-45ab-8ea7-bd8146a7f7a3@simark.ca \
--to=simark@simark.ca \
--cc=aburgess@redhat.com \
--cc=eliz@gnu.org \
--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).