From: Xi Ruoyao <xry111@xry111.site>
To: Eli Zaretskii <eliz@gnu.org>, Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org,
binutils@sourceware.org
Subject: Re: RFC: Top level configure: Require a minimum version 6.8 texinfo
Date: Wed, 30 Aug 2023 00:09:47 +0800 [thread overview]
Message-ID: <5021188cc7d7aa156314201462274f057dfb3d53.camel@xry111.site> (raw)
In-Reply-To: <83o7iphm71.fsf@gnu.org>
On Tue, 2023-08-29 at 19:01 +0300, Eli Zaretskii via Gcc-patches wrote:
> > Date: Tue, 29 Aug 2023 17:45:20 +0200
> > Cc: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org,
> > binutils@sourceware.org
> > From: Jakub Jelinek via Gdb-patches <gdb-patches@sourceware.org>
> >
> > On Tue, Aug 29, 2023 at 04:21:44PM +0100, Nick Clifton via Gcc-patches wrote:
> > > Currently the top level configure.ac file sets the minimum required
> > > version of texinfo to be 4.7. I would like to propose changing this
> > > to 6.8.
> > >
> > > The reason for the change is that the bfd documentation now needs at
> > > least version 6.8 in order to build[1][2]. Given that 4.7 is now
> > > almost 20 years old (it was released in April 2004), updating the
> > > requirement to a newer version does seem reasonable. On the other
> > > hand 6.8 is quite new (it was released in March 2021), so a lot of
> > > systems out there may not have it.
> > >
> > > Thoughts ?
> >
> > I think that is too new.
>
> It _is_ new. But I also don't understand why Nick thinks he needs
> Texinfo 6.8. AFAIR, makeinfo supported @node lines without explicit
> pointers since at least version 4.8. I have on my disk the manual
> produced for Emacs 22.1, where the Texinfo sources have no pointers,
> e.g.:
>
> @node Abbrev Concepts
>
> and the corresponding Info file says:
>
> This is ../info/emacs, produced by makeinfo version 4.8 from emacs.texi.
>
> So I'm not sure what exactly is the feature that requires Texinfo 6.8.
> What am I missing?
FWIW I tried building Binutils-2.41 with Texinfo 6.7 and it built
successfully.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2023-08-29 16:09 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 [this message]
2023-08-29 17:07 ` Tom Tromey
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=5021188cc7d7aa156314201462274f057dfb3d53.camel@xry111.site \
--to=xry111@xry111.site \
--cc=binutils@sourceware.org \
--cc=eliz@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jakub@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).