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] libctf: update regexp to allow makeinfo to build document
Date: Fri, 13 Jan 2023 17:05:47 +0200 [thread overview]
Message-ID: <835ydaa304.fsf@gnu.org> (raw)
In-Reply-To: <OS3P286MB2152AC3F96A88680022D57ADF0C29@OS3P286MB2152.JPNP286.PROD.OUTLOOK.COM> (message from Enze Li via Gdb-patches on Fri, 13 Jan 2023 22:42:32 +0800)
> Cc: gdb-patches@sourceware.org,
> enze.li@gmx.com
> Date: Fri, 13 Jan 2023 22:42:32 +0800
> From: Enze Li via Gdb-patches <gdb-patches@sourceware.org>
>
> While trying to build gdb on latest openSUSE Tumbleweed, I noticed the
> following warning,
>
> checking for makeinfo... makeinfo --split-size=5000000
> configure: WARNING:
> *** Makeinfo is too old. Info documentation will not be built.
>
> then I checked the version of makeinfo, it said,
> ======
> $ makeinfo --version
> texi2any (GNU texinfo) 7.0.1
>
> Copyright (C) 2022 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> ======
>
> After digging a little bit, it became quite obvious that a dot is
> missing in regexp that makes it impossible to match versions higher than
> 7.0.
Thanks.
> libctf/ChangeLog:
>
> * configure: Regenerated.
> * configure.ac: Update regexp to match versions higher than 7.0.
> ---
> libctf/configure | 2 +-
> libctf/configure.ac | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/libctf/configure b/libctf/configure
> index c22f7dffd2c..e9f7125edea 100755
> --- a/libctf/configure
> +++ b/libctf/configure
> @@ -14864,7 +14864,7 @@ esac
> # We require texinfo to be 6.3 or later, for a working synindex
> # and validatemenus: otherwise we fall back to /bin/true.
> if ${MAKEINFO} --version \
> - | egrep 'texinfo[^0-9]*(6\.[3-9]|[7-9][0-9])' >/dev/null 2>&1; then
> + | egrep 'texinfo[^0-9]*(6\.[3-9]|[7-9]\.[0-9])' >/dev/null 2>&1; then
> build_info=yes
> else
> build_info=
> diff --git a/libctf/configure.ac b/libctf/configure.ac
> index 1d0cf4d0fa5..4bc75736542 100644
> --- a/libctf/configure.ac
> +++ b/libctf/configure.ac
> @@ -184,7 +184,7 @@ changequote(,)
> # We require texinfo to be 6.3 or later, for a working synindex
> # and validatemenus: otherwise we fall back to /bin/true.
> if ${MAKEINFO} --version \
> - | egrep 'texinfo[^0-9]*(6\.[3-9]|[7-9][0-9])' >/dev/null 2>&1; then
> + | egrep 'texinfo[^0-9]*(6\.[3-9]|[7-9]\.[0-9])' >/dev/null 2>&1; then
> build_info=yes
> else
> build_info=
IMO, this solution has the same problem: it will stop working when
Texinfo 10.1 will be released. I think the solution should be to use
egrep 'texinfo[^0-9]*(6\.[3-9]|[7-9][0-9]?)'
That is, we don't care about the minor version for Texinfo > 6.9, we
only care about the major version.
next prev parent reply other threads:[~2023-01-13 15:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 14:42 Enze Li
2023-01-13 15:05 ` Eli Zaretskii [this message]
2023-01-13 15:36 ` Andreas Schwab
2023-01-13 15:44 ` Eli Zaretskii
2023-01-14 4:36 ` Enze Li
2023-01-14 7:36 ` Eli Zaretskii
2023-01-14 4:23 ` [PATCH v2] " Enze Li
2023-01-16 13:51 ` Nick Alcock
2023-01-16 15:19 ` Enze Li
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=835ydaa304.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).