procyberian/gcc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Revert this change:

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

From-SVN: r58746
This commit is contained in:
Gerald Pfeifer 2002-11-02 11:28:09 +01:00 • committed by Gerald Pfeifer
parent ed6c7a042d
commit 102b60d127
2 changed files with 13 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
gcc/ChangeLog
View file

@ -1,3 +1,10 @@
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.
2002-11-01 Kazu Hirata <kazu@cs.umass.edu>
* config/h8300/h8300.md (anonymous and:QI pattern): Use 'n'

11
gcc/doc/install.texi
View file

@ -284,11 +284,12 @@ variable to an automounter-aware @command{pwd} command, e.g.,
@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