public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: Todd Rinaldo <toddr@cpanel.net>
Cc: gcc@gnu.org, gcc-patches@gcc.gnu.org
Subject: [wwwdocs] PATCH for Re: FAQ conflict
Date: Tue, 25 May 2010 10:03:00 -0000	[thread overview]
Message-ID: <alpine.LSU.1.99.1005251053040.436@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <6D27904B-B1F6-43F0-A741-22B229D56513@cpanel.net>

On Thu, 13 May 2010, Todd Rinaldo wrote:
> Your FAQ at the below URLS conflicts as to which autoconf should be 
> used. one says 2.13 th other says 2.64. 2.65 is currently available.
> 
> http://gcc.gnu.org/faq.html#generated_files
> 
> http://gcc.gnu.org/install/prerequisites.html

Thanks for your report, Todd.  You are right, and the FAQ is out of
date whereas the installation documentation is correct.

I am updating FAQ per the patch below, and if you got to 
  http://gcc.gnu.org/faq.html#generated_files
you will see the new (and shorter) version already which
now directly refers to the installation documentation.

I hope this addresses the issue you have been seeing?

Gerald


Index: faq.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/faq.html,v
retrieving revision 1.209
diff -u -3 -p -r1.209 faq.html
--- faq.html	3 May 2010 13:47:48 -0000	1.209
+++ faq.html	25 May 2010 08:54:05 -0000
@@ -475,19 +475,9 @@ those generated files are out of date an
 </code> script in the contrib subdirectory of GCC, which handles this
 transparently without requiring installation of any additional tools.</p>
 
-
-<p>When building from diffs or SVN or if you modified some sources,
-you may also need to obtain development versions of some GNU tools, as
-the production versions do not necessarily handle all features needed
-to rebuild GCC.</p>
-
-<p>In general, the current versions of these tools from <a
-href="ftp://ftp.gnu.org/gnu/">ftp://ftp.gnu.org/gnu/</a> will work.
-At present, Autoconf 2.50 is not supported, and you will need to use
-Autoconf 2.13; work is in progress to fix this problem.  Also look at
-<a href="ftp://gcc.gnu.org/pub/gcc/infrastructure/">
-ftp://gcc.gnu.org/pub/gcc/infrastructure/</a> for any special versions
-of packages.</p>
+<p>If you modified some sources or when building from SVN you may also
+need <a href="http://gcc.gnu.org/install/prerequisites.html#TOC1">some
+additional tools</a>.</p>
 
 
 <hr />

      reply	other threads:[~2010-05-25  8:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-13 23:06 Todd Rinaldo
2010-05-25 10:03 ` Gerald Pfeifer [this message]

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=alpine.LSU.1.99.1005251053040.436@acrux.dbai.tuwien.ac.at \
    --to=gerald@pfeifer.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gnu.org \
    --cc=toddr@cpanel.net \
    /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).