mirror of
git://gcc.gnu.org/git/gcc.git
synced 2025-01-11 03:44:38 +08:00
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
This commit is contained in:
parent
1bd229b76d
commit
3f2c089fe6
@ -1,3 +1,9 @@
|
||||
2006-05-22 Gerald Pfeifer <gerald@pfeifer.com>
|
||||
|
||||
* doc/install.texi (Configuration): Remove reference to CrossGCC
|
||||
FAQ which was hijacked.
|
||||
(Building): Ditto.
|
||||
|
||||
2006-05-22 Kazu Hirata <kazu@codesourcery.com>
|
||||
|
||||
PR target/27266
|
||||
|
@ -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@.
|
||||
|
Loading…
Reference in New Issue
Block a user