From: Tom Tromey <tom@tromey.com>
To: Nick Clifton via Gdb-patches <gdb-patches@sourceware.org>
Cc: gcc-patches@gcc.gnu.org, binutils@sourceware.org,
Nick Clifton <nickc@redhat.com>
Subject: Re: RFC: Top level configure: Require a minimum version 6.8 texinfo
Date: Tue, 29 Aug 2023 11:07:32 -0600 [thread overview]
Message-ID: <87cyz5sror.fsf@tromey.com> (raw)
In-Reply-To: <87wmxd50xj.fsf@redhat.com> (Nick Clifton via Gdb-patches's message of "Tue, 29 Aug 2023 16:21:44 +0100")
>>>>> "Nick" == Nick Clifton via Gdb-patches <gdb-patches@sourceware.org> writes:
Nick> The reason for the change is that the bfd documentation now needs at
Nick> least version 6.8 in order to build[1][2].
Sorry about this. It was fallout from my patch.
However, GDB has used this same one-argument @node syntax for a long
time without any complaint. Like, python.texi has used this since at
least 2014.
So, if makeinfo 6.8 is really needed by BFD, then I think it must be for
some other reason.
Tom
next prev parent reply other threads:[~2023-08-29 17:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 15:21 Nick Clifton
2023-08-29 15:45 ` Jakub Jelinek
2023-08-29 15:50 ` YunQiang Su
2023-08-29 16:09 ` Fangrui Song
2023-08-29 16:01 ` Eli Zaretskii
2023-08-29 16:09 ` Xi Ruoyao
2023-08-29 17:07 ` Tom Tromey [this message]
2023-08-30 2:53 ` Eric Gallager
2023-08-30 20:28 ` Tom Tromey
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=87cyz5sror.fsf@tromey.com \
--to=tom@tromey.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=nickc@redhat.com \
/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).