aboutsummaryrefslogtreecommitdiff
path: root/gcc/doc
diff options
context:
space:
mode:
authorGerald Pfeifer <gerald@pfeifer.com>2006-05-22 19:31:01 +0000
committerGerald Pfeifer <gerald@gcc.gnu.org>2006-05-22 19:31:01 +0000
commit3f2c089fe66cd5d015b73995962dec6f97d19357 (patch)
tree20358d22f108bdb22ed0a5df50892f82b4173fd6 /gcc/doc
parent1bd229b76d79228d76f15fb7c450e5462503d133 (diff)
downloadgcc-3f2c089fe66cd5d015b73995962dec6f97d19357.zip
gcc-3f2c089fe66cd5d015b73995962dec6f97d19357.tar.gz
gcc-3f2c089fe66cd5d015b73995962dec6f97d19357.tar.bz2
install.texi (Configuration): Remove reference to CrossGCC FAQ which was hijacked.
* doc/install.texi (Configuration): Remove reference to CrossGCC FAQ which was hijacked. (Building): Ditto. From-SVN: r113992
Diffstat (limited to 'gcc/doc')
-rw-r--r--gcc/doc/install.texi6
1 files changed, 0 insertions, 6 deletions
diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index 8e83c24..8697577 100644
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -1319,8 +1319,6 @@ will be run on these files to make them compatible with GCC@.
Tells GCC not use any target headers from a libc when building a cross
compiler. When crossing to GNU/Linux, you need the headers so GCC
can build the exception handling for libgcc.
-See @uref{http://www.objsw.com/CrossGCC/,,CrossGCC} for more information
-on this option.
@item --with-libs
@itemx --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}''
@@ -1656,10 +1654,6 @@ the one you are building on: for example, you could build a
@section Building a cross compiler
-We recommend reading the
-@uref{http://www.objsw.com/CrossGCC/,,crossgcc FAQ}
-for information about building cross compilers.
-
When building a cross compiler, it is not generally possible to do a
3-stage bootstrap of the compiler. This makes for an interesting problem
as parts of GCC can only be built with GCC@.