This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Error report (gcc 3.1)
- From: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- To: Stan Shebs <shebs at apple dot com>
- Cc: Alexandre Oliva <aoliva at redhat dot com>, Maurizio Loreti <loreti at pd dot infn dot it>, <gcc at gcc dot gnu dot org>, Paolo Carlini <pcarlini at unitus dot it>
- Date: Thu, 16 May 2002 21:14:59 +0200 (CEST)
- Subject: Re: Error report (gcc 3.1)
On Thu, 16 May 2002, Stan Shebs wrote:
> Yes. We've been hosed by this too, and it's so confusing it should
> probably in some sort of FAQ or release note. The problem is that the
> old basic_file.h is always going to be in the search path ahead of the
> new one, and so any installation that doesn't completely delete the
> pre-3.1-final g++-v3 is going to get nailed by this.
I believe we'd be better of recommending against installing one version
of GCC over another one.
If you agree, would you mind applying the following patch or a variation
thereof? (You're in a "later" time zone than me, so I probably won't read
your response soon.)
Gerald
2002-05-16 Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
* doc/install.texi (Final install): Recommend to install into a
"clean" target directory.
Index: doc/install.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/install.texi,v
retrieving revision 1.116
diff -u -3 -p -r1.116 install.texi
--- doc/install.texi 14 May 2002 10:38:46 -0000 1.116
+++ doc/install.texi 16 May 2002 19:12:45 -0000
@@ -1256,6 +1256,9 @@ Now that GCC has been built (and optiona
cd @var{objdir}; make install
@end example
+We strongly recommend to install into a target directory where there is
+no previous version of GCC present.
+
That step completes the installation of GCC; user level binaries can
be found in @file{@var{prefix}/bin} where @var{prefix} is the value you
specified with the @option{--prefix} to configure (or @file{/usr/local}