From: Andrew Burgess <aburgess@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PUSHED] gdb/doc: use POD2MAN5 when appropriate
Date: Thu, 06 Jun 2024 18:08:13 +0100 [thread overview]
Message-ID: <87frtqatj6.fsf@redhat.com> (raw)
In-Reply-To: <de4edfcb949c0d04ec8b49fdfe06267f92618589.1717693308.git.aburgess@redhat.com>
Andrew Burgess <aburgess@redhat.com> writes:
> In commit:
>
> commit 824083f34c222aa7419e2ea58e82d6f230d5f531
> Date: Fri Apr 12 17:47:20 2024 +0100
>
> gdb/doc: use silent-rules.mk in the Makefile
>
> I rewrote the rules for building the man pages. While doing this I
> accidentally switched from using MAN2POD5 to MAN2POD1 for generating
> the file gdbinit.5.
>
> Restore use of MAN2POD5 where appropriate.
Joel,
I've back-ported this fix to the gdb-15-branch too. Without this the
gdbinit man page will be in the wrong section, e.g.
man 5 gdbinit
will not return any results.
Thanks,
Andrew
> ---
> gdb/doc/Makefile.in | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gdb/doc/Makefile.in b/gdb/doc/Makefile.in
> index 6a112b98d0e..d9c13873a60 100644
> --- a/gdb/doc/Makefile.in
> +++ b/gdb/doc/Makefile.in
> @@ -679,7 +679,7 @@ $(MAN1S) : %.1 : $(GDB_DOC_FILES)
>
> $(MAN5S) : %.5 : $(GDB_DOC_FILES)
> $(ECHO_TEXI2POD) $(TEXI2POD) $(MANCONF) -D$* < $(srcdir)/gdb.texinfo > $*.pod
> - $(ECHO_TEXI2MAN) ($(POD2MAN1) $*.pod | sed -e '/^.if n .na/d' > $@.T$$$$ && \
> + $(ECHO_TEXI2MAN) ($(POD2MAN5) $*.pod | sed -e '/^.if n .na/d' > $@.T$$$$ && \
> mv -f $@.T$$$$ $@) || (rm -f $@.T$$$$ && exit 1)
> $(SILENCE) rm -f $*.pod
>
>
> base-commit: 61e608693b53a13c48d509a45b329f7ef9dfaa19
> --
> 2.25.4
next prev parent reply other threads:[~2024-06-06 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 17:03 Andrew Burgess
2024-06-06 17:08 ` Andrew Burgess [this message]
2024-06-06 17:40 ` Joel Brobecker
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=87frtqatj6.fsf@redhat.com \
--to=aburgess@redhat.com \
--cc=brobecker@adacore.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