Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Douglas Evans" <dje@google.com>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: fix gdbint.info autoconf version
Date: Wed, 28 Nov 2007 18:46:00 -0000	[thread overview]
Message-ID: <e394668d0711281046j7a6e2064rc1f62c1f2bc74cc4@mail.gmail.com> (raw)
In-Reply-To: <uzlx01ft9.fsf@gnu.org>

On Nov 26, 2007 8:18 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Mon, 26 Nov 2007 17:16:52 -0800
> > From: "Douglas Evans" <dje@google.com>
> >
> > How about this?
>
> Okay, but for these two minor issues:
>
> >  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.
>
> What is meant by ``the same version''? same as what?
>
> > Currently this is 2.59.
>
> Please remove this sentence.  "Currently" will become obsolete very
> quickly, and has no real value here.  If you want to be friendly, you
> could show the fragment of `configure' where one sees the version, and
> state that in this fragment the version is so-and-so.
>
> Thanks.

Thanks.  How's this?

2007-11-28  Doug Evans  <dje@google.com>

        * gdbint.texinfo (Create a release): Fix docs on what version
        of autoconf to use.

Index: gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.275
diff -u -p -u -p -r1.275 gdbint.texinfo
--- gdbint.texinfo      15 Nov 2007 06:14:26 -0000      1.275
+++ gdbint.texinfo      28 Nov 2007 18:43:48 -0000
@@ -6289,11 +6289,18 @@ 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.
+Check the @code{autoconf} version carefully.  You want to use the same version
+that was previously used.  See the top of @file{configure} to see what version
+generated it.  In this example the version is 2.59.
+
+@smallexample
+bash$ head -3 configure
+#! /bin/sh
+# Guess values for system-dependent variables and create Makefiles.
+# Generated by GNU Autoconf 2.59.
+@end smallexample
+
+Autoconf can be obtained from @uref{ftp://ftp.gnu.org/pub/autoconf/}.
 @end itemize

 @subsubheading Check out the relevant modules:


  reply	other threads:[~2007-11-28 18:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-27  1:17 Douglas Evans
2007-11-27  4:19 ` Eli Zaretskii
2007-11-28 18:46   ` Douglas Evans [this message]
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=e394668d0711281046j7a6e2064rc1f62c1f2bc74cc4@mail.gmail.com \
    --to=dje@google.com \
    --cc=eliz@gnu.org \
    --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