From: Eric Gallager <egall@gwmail.gwu.edu>
To: Nick Clifton <nickc@redhat.com>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org,
binutils@sourceware.org, iains@gcc.gnu.org
Subject: Re: RFC: Top level configure: Require a minimum version 6.8 texinfo
Date: Tue, 29 Aug 2023 22:53:26 -0400 [thread overview]
Message-ID: <CAMfHzOvtWe8Hq9nNvVUWxxkOa97K5zD-+Sz6oOZ7-X7Lasq6hA@mail.gmail.com> (raw)
In-Reply-To: <87wmxd50xj.fsf@redhat.com>
On Tue, Aug 29, 2023 at 11:23 AM Nick Clifton via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> Hi Guys,
>
> 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 ?
>
Just as a point of reference, but the default makeinfo shipped with
macOS (/usr/bin/makeinfo) is stuck at version 4.8 due to the whole
GPL3 transition. The other makeinfos that I have installed are:
- /usr/local/bin/makeinfo (built manually) is at version 6.7
- /opt/local/bin/makeinfo (from MacPorts) is at version 7.0.3
- /opt/sw/bin/makeinfo (from Fink) is broken for me currently, so I
can't get its version at the moment
- /opt/sw/opt/texinfo-legacy/bin/makeinfo (also from Fink, but as a
separate package) is at version 4.13
- /opt/iains/x86_64-apple-darwin19/gcc-7-5-toolchain/bin/makeinfo
(from Iain Sandoe's package I used for bootstrapping Ada) is at
version 6.7
So, from this survey, the makeinfo from MacPorts is the only one I'd
be able to build with currently if this change went through. I think
that's a sign that 6.8 is too new.
Eric
> Cheers
> Nick
>
> [1] https://sourceware.org/bugzilla/show_bug.cgi?id=30703
> [2] https://sourceware.org/pipermail/binutils/2023-February/125943.html
>
> Suggested patch:
>
> diff --git a/configure.ac b/configure.ac
> index 01cfd017273..10bfef1c6c5 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -3678,10 +3678,10 @@ case " $build_configdirs " in
> *" texinfo "*) MAKEINFO='$$r/$(BUILD_SUBDIR)/texinfo/makeinfo/makeinfo' ;;
> *)
> changequote(,)
> - # For an installed makeinfo, we require it to be from texinfo 4.7 or
> + # For an installed makeinfo, we require it to be from texinfo 6.8 or
> # higher, else we use the "missing" dummy.
> if ${MAKEINFO} --version \
> - | egrep 'texinfo[^0-9]*(4\.([7-9]|[1-9][0-9])|[5-9]|[1-9][0-9])' >/dev/null 2>&1; then
> + | egrep 'texinfo[^0-9]*(6\.([8-9]|[1-9][0-9])|[7-9]|[1-9][0-9])' >/dev/null 2>&1; then
> :
> else
> MAKEINFO="$MISSING makeinfo"
>
next prev parent reply other threads:[~2023-08-30 2:53 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
2023-08-30 2:53 ` Eric Gallager [this message]
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=CAMfHzOvtWe8Hq9nNvVUWxxkOa97K5zD-+Sz6oOZ7-X7Lasq6hA@mail.gmail.com \
--to=egall@gwmail.gwu.edu \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=iains@gcc.gnu.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).