From: Ben Elliston <bje@au1.ibm.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, newlib@sourceware.org,
cygwin-patches@sourceware.org
Subject: Re: raising minimum Texinfo requirement in src tree
Date: Sun, 02 Apr 2006 23:53:00 -0000 [thread overview]
Message-ID: <20060402235418.GA20771@ozlabs.au.ibm.com> (raw)
In-Reply-To: <u1wwjavmx.fsf@gnu.org>
> Which patch was that? Can you show it or give a URL? I don't
> remember seeing such a patch on gdb-patches, but my memory is not
> what it used to be.
2006-03-31 Ben Elliston <bje@au.ibm.com>
PR binutils/1860
* configure.in: Require makeinfo 4.4 or higher.
* configure: Regenerate.
Index: configure.in
===================================================================
RCS file: /cvs/src/src/configure.in,v
retrieving revision 1.301
retrieving revision 1.302
diff -u -p -r1.301 -r1.302
--- configure.in 14 Mar 2006 16:10:08 -0000 1.301
+++ configure.in 31 Mar 2006 02:32:20 -0000 1.302
@@ -2203,10 +2203,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.2 or
+ # For an installed makeinfo, we require it to be from texinfo 4.4 or
# higher, else we use the "missing" dummy.
if ${MAKEINFO} --version \
- | egrep 'texinfo[^0-9]*([1-3][0-9]|4\.[2-9]|[5-9])' >/dev/null 2>&1; then
+ | egrep 'texinfo[^0-9]*([1-3][0-9]|4\.[4-9]|[5-9])' >/dev/null 2>&1; then
:
else
MAKEINFO="$MISSING makeinfo"
next prev parent reply other threads:[~2006-04-02 23:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-31 10:28 Ben Elliston
2006-03-31 13:56 ` Eli Zaretskii
2006-04-02 23:53 ` Ben Elliston [this message]
2006-04-03 3:35 ` Eli Zaretskii
2006-04-03 3:42 ` Daniel Jacobowitz
2006-04-03 3:52 ` Ben Elliston
2006-04-03 18:45 ` Mark Kettenis
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=20060402235418.GA20771@ozlabs.au.ibm.com \
--to=bje@au1.ibm.com \
--cc=cygwin-patches@sourceware.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=newlib@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