re PR fortran/15478 (gfortran manual problems)

PR fortran/15478
* doc/install.texi: Document GMP as prerequisite. Document
--with-gmp and --with-gmp-dir configure options.
* fortran/gfortran.texi: Remove section 'Compiling and testing',
remove TOC reference to it.

From-SVN: r82648

gcc/ChangeLog

+2004-06-01  Tobias Schlueter  <tobias.schlueter@physik.uni-muenchen.de>
+
+	PR fortran/15478
+	* doc/install.texi: Document GMP as prerequisite. Document
+	--with-gmp and --with-gmp-dir configure options.
+	* fortran/gfortran.texi: Remove section "Compiling and testing",
+	remove TOC reference to it. 
+
 2004-06-05  Graham Stott  <graham.stott@btinternet.com>
 
 	* combine.c(simplify_shift_const): Check shift amount is a

gcc/doc/install.texi

@@ -285,6 +285,12 @@ Necessary (only on some platforms) to untar the source code.  Many
 systems' @command{tar} programs will also work, only try GNU
 @command{tar} if you have problems.
 
+@item GNU Multiple Precision Library (GMP) version 4.0 (or later)
+
+Necessary to build the Fortran frontend. If you don't have it
+installed in your library search path, you will have to configure with
+the @option{--with-gmp} or @option{--with-gmp-dir} configure option.
+
 @end table
 
 
@@ -1196,6 +1202,22 @@ omitted from @file{libgcc.a} on the assumption that it will be provided by
 @samp{newlib}.
 @end table
 
+@subheading Fortran-specific Option
+
+The following options apply to the build of the Fortran front end.
+
+@table @code
+
+@item --with-gmp=@var{pathname}
+@itemx --with-gmp-dir=@var{pathname}
+If you don't have GMP (the GNU Multiple Precision library) installed
+in a standard location and you want to build the Fortran front-end,
+you can explicitly specify the directory where GMP is installed
+(@samp{--with-gmp=gmpinstalldir}) or where you built the GMP library without
+installing (@samp{--with-gmp-dir=gmpbuilddir}).
+
+@end table
+
 @subheading Java-Specific Options
 
 The following option applies to the build of the Java front end.

gcc/fortran/gfortran.texi

@@ -129,8 +129,6 @@ not accurately reflect the status of the most recent @command{gfortran}.
 * GFORTRAN and GCC::	    You can compile Fortran, C, or other programs.
 * GFORTRAN and G77::     Why we choose to start from scratch.
 * Invoking GFORTRAN::    Command options supported by @command{gfortran}.
-* Compiling and Testing::
-		    Need-to-knows about compiling and testing.
 * Project Status::  Status of GFORTRAN, Roadmap, proposed extensions.
 * Contributing::    Helping you can help.
 * Standards::	    Standards supported by GFORTRAN.
@@ -380,63 +378,6 @@ and then build a Fortran 95 compiler out of it.
 @include invoke.texi
 
 @c ---------------------------------------------------------------------
-@c Compiling and Testing
-@c ---------------------------------------------------------------------
-
-@node Compiling and Testing
-@chapter Compiling and Testing
-
-@command{gfortran} is not yet part of an official GCC release, so it is
-unlikley that OS distributor will provide it.
-
-@menu
-* Precompiled Binaries::
-* General notes about compiling GFORTRAN::
-* Testing::
-@end menu
-
-@node Precompiled Binaries
-@section Precompiled Binaries
-
-Precompiled binaries for i686-pc-linux-gnu in rpm format are available from
-@uref{http://people.redhat.com/dnovillo/pub/tree-ssa/snapshot/}
-
-@node General notes about compiling GFORTRAN
-@section General notes about compiling GFORTRAN
-@cindex GMP
-@cindex Multiple Precision Library
-
-Compiling gfortran requires the presence of GMP,
-the GNU Multiple Precision library version 4.0
-or better in order to do its arithmetic.
-Download @code{gmp} from your favorite GNU mirror,
-configure and compile it.  If your OS distributor provides prepackaged
-GMP libraries, you may also need the developent pacakges.
-
-If you do not have GMP installed in a standard system location, you may
-need to configure GCC with @option{--with-gmp} or @option{--with-gmp-dir}.
-
-Note: GMP is only required for the compiler itself.  Compiled fortran programs
-do not depend on the GMP library. 
-
-@node Testing
-@section Testing
-@cindex Test suite
-@cindex Testing
-
-The number of possible Fortran 95 programs is unlimited,
-and this means that gfortran has to correctly handle lots of possible inputs.
-Whenever you make any changes to the compiler,
-you should first test your change on a test program,
-then test your change against the gfortran test suite.
-In this way, we can be assured that once your fix has been made,
-the problem isn't re-introduced at some later time.
-
-The gfortran test suite is included in the gcc source distribution.
-
-We also encourage you to test gfortran on your own Fortran codes.
-
-@c ---------------------------------------------------------------------
 @c Project Status
 @c ---------------------------------------------------------------------