OpenE2K/gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

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

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

From-SVN: r52335
This commit is contained in:
Loren J. Rittle 2002-04-15 21:28:46 +00:00 committed by Loren J. Rittle
parent 83248d496d
commit 0aa911c5b2
2 changed files with 10 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gcc/ChangeLog
View File

@ -1,3 +1,8 @@
2002-04-15 Loren J. Rittle <ljrittle@acm.org>
* doc/install.texi (Installing GCC: Configuration): Clarify
the only supported ways to configure gcc.
2002-04-15 Roland McGrath <roland@frob.com>
* config.gcc (alpha*-*-gnu*): New target configuration.

11
gcc/doc/install.texi
View File

@ -288,12 +288,11 @@ If you obtained the sources via CVS, @var{srcdir} must refer to the top
@file{gcc} directory, the one where the @file{MAINTAINERS} can be found,
and not its @file{gcc} subdirectory, otherwise the build will fail.
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.
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.
If you have previously built GCC in the same directory for a
different target machine, do @samp{make distclean} to delete all files