From: Eli Zaretskii <eliz@gnu.org>
To: Enze Li <enze.li@hotmail.com>
Cc: binutils@sourceware.org, gdb-patches@sourceware.org, enze.li@gmx.com
Subject: Re: [PATCH] bfd: add version check to makeinfo
Date: Tue, 04 Apr 2023 18:24:40 +0300 [thread overview]
Message-ID: <83cz4ju0uf.fsf@gnu.org> (raw)
In-Reply-To: <OS3P286MB2152D2B8F88B6EB24B91BD8BF0939@OS3P286MB2152.JPNP286.PROD.OUTLOOK.COM> (message from Enze Li via Gdb-patches on Tue, 4 Apr 2023 23:07:13 +0800)
> Cc: gdb-patches@sourceware.org,
> enze.li@gmx.com
> Date: Tue, 4 Apr 2023 23:07:13 +0800
> From: Enze Li via Gdb-patches <gdb-patches@sourceware.org>
>
> In this commit,
>
> commit 8bb23cdbb498ff645bb0937bc8c0cb89e9e5ebd8
> Date: Tue Feb 7 11:34:56 2023 -0700
>
> Simplify @node use in BFD documentation
>
> we use a modern style available from makeinfo 5.0 or later.
>
> This patch adds a check for makeinfo that no documentation will be
> generated if it is below the specified version.
>
> The motivation for this work comes from the fact that compiling GDB on
> the latest version of NetBSD(9.3) produces the following errors because
> it comes with makeinfo 4.8. This patch workaround this issus.
Some people still use makeinfo 4.x because it's at least an order of
magnitude faster than version 5 and later. For such simple problems,
wouldn't it be better to add the missing sectioning commands, and let
those users of makeinfo 4.x keep using it?
Just asking.
next prev parent reply other threads:[~2023-04-04 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 15:07 Enze Li
2023-04-04 15:24 ` Eli Zaretskii [this message]
2023-04-06 15:00 ` Enze Li
2023-04-06 15:38 ` 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=83cz4ju0uf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=binutils@sourceware.org \
--cc=enze.li@gmx.com \
--cc=enze.li@hotmail.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).