Obsolete installation instructions and inconvenient CVS HOWTO

[Gerald Pfeifer]

On Mon, 28 Oct 2002, DJ Delorie wrote:
> Yes.  Both Loren Rittle and I do ./configure builds of head every
> night, and have been for a while.
>
>> (or would you prefer me doing it)?
>
> Yes, please.

Done.

Gerald

2002-11-02  Gerald Pfeifer  <pfeifer@dbai.tuwien.ac.at>

	Revert this change:

	*doc/install.texi (Installing GCC: Configuration): Clarify
	the only supported ways to configure gcc.

Index: doc/install.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/install.texi,v
retrieving revision 1.145
diff -u -3 -p -r1.145 install.texi
--- doc/install.texi	24 Oct 2002 20:32:28 -0000	1.145
+++ doc/install.texi	2 Nov 2002 10:25:01 -0000
@@ -284,11 +284,12 @@ variable to an automounter-aware @comman
 @command{pawd} or @command{amq -w}, during the configuration and build
 phases.

-First, in general, GCC @strong{must} be built into a separate directory
-than the sources which does @strong{not} reside within the source tree.
-This is how almost all developers build GCC; building where @var{srcdir}
-== @var{objdir} is completely unsupported; building where @var{objdir}
-is a subdirectory of @var{srcdir} is completely unsupported.
+First, we @strong{highly} recommend that GCC be built into a
+separate directory than the sources which does @strong{not} reside
+within the source tree.  This is how we generally build GCC; building
+where @var{srcdir} == @var{objdir} should still work, but doesn't
+get extensive testing; building where @var{objdir} is a subdirectory
+of @var{srcdir} is unsupported.

 If you have previously built GCC in the same directory for a
 different target machine, do @samp{make distclean} to delete all files