From: "Douglas Evans" <dje@google.com>
To: gdb-patches@sourceware.org
Subject: RFA: fix gdbint.info autoconf version
Date: Tue, 27 Nov 2007 01:17:00 -0000 [thread overview]
Message-ID: <e394668d0711261716g28a2c2aeue829054403d761e4@mail.gmail.com> (raw)
gdbint.texinfo says to use the old autoconf on sourceware, but gdb/configure
is now regenerated with autoconf 2.59.
gdbint.texinfo:
Check the @code{autoconf} version carefully. You want to be using the
version taken from the @file{binutils} snapshot directory, which can be
found at @uref{ftp://sources.redhat.com/pub/binutils/}. It is very
unlikely that a system installed version of @code{autoconf} (e.g.,
@file{/usr/bin/autoconf}) is correct.
ChangeLog-2005:
2005-01-07 Andrew Cagney <cagney@gnu.org>
* configure.ac: Rename configure.in, require autoconf 2.59.
* configure: Re-generate.
How about this?
Index: doc/gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.275
diff -u -p -r1.275 gdbint.texinfo
--- doc/gdbint.texinfo 15 Nov 2007 06:14:26 -0000 1.275
+++ doc/gdbint.texinfo 27 Nov 2007 01:15:19 -0000
@@ -6290,10 +6290,9 @@ Notes:
@itemize @bullet
@item
Check the @code{autoconf} version carefully. You want to be using the
-version taken from the @file{binutils} snapshot directory, which can be
-found at @uref{ftp://sources.redhat.com/pub/binutils/}. It is very
-unlikely that a system installed version of @code{autoconf} (e.g.,
-@file{/usr/bin/autoconf}) is correct.
+same version. See the top of @file{configure} to see what version
+generated it. Currently this is 2.59. Autoconf can be obtained from
+@uref{ftp://ftp.gnu.org/pub/autoconf/}.
@end itemize
@subsubheading Check out the relevant modules:
next reply other threads:[~2007-11-27 1:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 1:17 Douglas Evans [this message]
2007-11-27 4:19 ` Eli Zaretskii
2007-11-28 18:46 ` Douglas Evans
2007-11-28 21:40 ` Eli Zaretskii
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=e394668d0711261716g28a2c2aeue829054403d761e4@mail.gmail.com \
--to=dje@google.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