From: Michael Snyder <msnyder@specifix.com>
To: gdb-patches@sourceware.org
Cc: rsandifo@nildram.co.uk, schwab@suse.de, bkoz@redhat.com
Subject: [RFA] top level configure and makeinfo/texinfo
Date: Wed, 10 Oct 2007 01:11:00 -0000 [thread overview]
Message-ID: <1191977857.4409.0.camel@localhost.localdomain> (raw)
Texinfo is up to version 4.11, I believe (at least).
When somebody gets around to running gdb's top level
configure with this, it's going to fail due to a
regular expression that won't recognize a minor
version number greater than 9.
Not sure who should approve this...
And yes, I realize that there are 3 or 4 other configure
scripts to which this also applies.
2007-10-09 Michael Snyder <msnyder@specifix.com>
* configure.ac (makeinfo version number): Allow for texinfo versions
between 4.10 and 4.99.
* configure: Regenerate.
Index: configure.ac
===================================================================
RCS file: /cvs/src/src/configure.ac,v
retrieving revision 1.30
diff -u -p -r1.30 configure.ac
--- configure.ac 1 Oct 2007 07:55:47 -0000 1.30
+++ configure.ac 9 Oct 2007 23:39:39 -0000
@@ -2504,7 +2504,7 @@ changequote(,)
# For an installed makeinfo, we require it to be from texinfo 4.6
or
# higher, else we use the "missing" dummy.
if ${MAKEINFO} --version \
- | egrep 'texinfo[^0-9]*(4\.([6-9]|[1-9][0-9])|[5-9]|[1-9][0-9])'
>/dev/null 2>&1; then
+ | egrep 'texinfo[^0-9]*(4\.([6-9]|4
\.[1-9][0-9]|[1-9][0-9])|[5-9]|[1-9][0-9])' >/dev/null 2>&1; then
:
else
MAKEINFO="$MISSING makeinfo"
Index: configure
===================================================================
RCS file: /cvs/src/src/configure,v
retrieving revision 1.282
diff -u -p -r1.282 configure
--- configure 1 Oct 2007 09:04:55 -0000 1.282
+++ configure 9 Oct 2007 23:39:43 -0000
@@ -6233,7 +6233,7 @@ case " $build_configdirs " in
# For an installed makeinfo, we require it to be from texinfo 4.6
or
# higher, else we use the "missing" dummy.
if ${MAKEINFO} --version \
- | egrep 'texinfo[^0-9]*(4\.([6-9]|[1-9][0-9])|[5-9]|[1-9][0-9])'
>/dev/null 2>&1; then
+ | egrep 'texinfo[^0-9]*(4\.([6-9]|4
\.[1-9][0-9]|[1-9][0-9])|[5-9]|[1-9][0-9])' >/dev/null 2>&1; then
:
else
MAKEINFO="$MISSING makeinfo"
next reply other threads:[~2007-10-10 0:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 1:11 Michael Snyder [this message]
2007-10-10 1:56 ` DJ Delorie
2007-10-10 5:13 ` Michael Snyder
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=1191977857.4409.0.camel@localhost.localdomain \
--to=msnyder@specifix.com \
--cc=bkoz@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=rsandifo@nildram.co.uk \
--cc=schwab@suse.de \
/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