summaryrefslogtreecommitdiff
path: root/INSTALL
diff options
context:
space:
mode:
authorupstream source tree <ports@midipix.org>2015-03-15 20:14:05 -0400
committerupstream source tree <ports@midipix.org>2015-03-15 20:14:05 -0400
commit554fd8c5195424bdbcabf5de30fdc183aba391bd (patch)
tree976dc5ab7fddf506dadce60ae936f43f58787092 /INSTALL
downloadcbb-gcc-4.6.4-554fd8c5195424bdbcabf5de30fdc183aba391bd.tar.bz2
cbb-gcc-4.6.4-554fd8c5195424bdbcabf5de30fdc183aba391bd.tar.xz
obtained gcc-4.6.4.tar.bz2 from upstream website;upstream
verified gcc-4.6.4.tar.bz2.sig; imported gcc-4.6.4 source tree from verified upstream tarball. downloading a git-generated archive based on the 'upstream' tag should provide you with a source tree that is binary identical to the one extracted from the above tarball. if you have obtained the source via the command 'git clone', however, do note that line-endings of files in your working directory might differ from line-endings of the respective files in the upstream repository.
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL/README6
-rw-r--r--INSTALL/binaries.html126
-rw-r--r--INSTALL/build.html380
-rw-r--r--INSTALL/configure.html1249
-rw-r--r--INSTALL/download.html97
-rw-r--r--INSTALL/finalinstall.html174
-rw-r--r--INSTALL/gfdl.html517
-rw-r--r--INSTALL/index.html125
-rw-r--r--INSTALL/old.html213
-rw-r--r--INSTALL/prerequisites.html297
-rw-r--r--INSTALL/specific.html1561
-rw-r--r--INSTALL/test.html233
12 files changed, 4978 insertions, 0 deletions
diff --git a/INSTALL/README b/INSTALL/README
new file mode 100644
index 000000000..27bd1738b
--- /dev/null
+++ b/INSTALL/README
@@ -0,0 +1,6 @@
+This directory has been obsoleted for GCC snapshots and CVS access.
+
+For releases the installation documentation is generated from
+gcc/doc/install.texi and copied into this directory.
+
+To read this documentation, please point your HTML browser to "index.html".
diff --git a/INSTALL/binaries.html b/INSTALL/binaries.html
new file mode 100644
index 000000000..f360b1a8a
--- /dev/null
+++ b/INSTALL/binaries.html
@@ -0,0 +1,126 @@
+<html lang="en">
+<head>
+<title>Installing GCC: Binaries</title>
+<meta http-equiv="Content-Type" content="text/html">
+<meta name="description" content="Installing GCC: Binaries">
+<meta name="generator" content="makeinfo 4.13">
+<link title="Top" rel="top" href="#Top">
+<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
+<!--
+Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
+1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
+2010 Free Software Foundation, Inc.
+
+ Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, the Front-Cover texts being (a) (see below), and
+with the Back-Cover Texts being (b) (see below). A copy of the
+license is included in the section entitled "GNU Free Documentation License".
+
+(a) The FSF's Front-Cover Text is:
+
+ A GNU Manual
+
+(b) The FSF's Back-Cover Text is:
+
+ You have freedom to copy and modify this GNU Manual, like GNU
+ software. Copies published by the Free Software Foundation raise
+ funds for GNU development.-->
+<meta http-equiv="Content-Style-Type" content="text/css">
+<style type="text/css"><!--
+ pre.display { font-family:inherit }
+ pre.format { font-family:inherit }
+ pre.smalldisplay { font-family:inherit; font-size:smaller }
+ pre.smallformat { font-family:inherit; font-size:smaller }
+ pre.smallexample { font-size:smaller }
+ pre.smalllisp { font-size:smaller }
+ span.sc { font-variant:small-caps }
+ span.roman { font-family:serif; font-weight:normal; }
+ span.sansserif { font-family:sans-serif; font-weight:normal; }
+--></style>
+</head>
+<body>
+<h1 class="settitle">Installing GCC: Binaries</h1>
+<a name="index-Binaries-1"></a><a name="index-Installing-GCC_003a-Binaries-2"></a>
+We are often asked about pre-compiled versions of GCC. While we cannot
+provide these for all platforms, below you'll find links to binaries for
+various platforms where creating them by yourself is not easy due to various
+reasons.
+
+ <p>Please note that we did not create these binaries, nor do we
+support them. If you have any problems installing them, please
+contact their makers.
+
+ <ul>
+<li>AIX:
+ <ul>
+<li><a href="http://www.bullfreeware.com">Bull's Freeware and Shareware Archive for AIX</a>;
+
+ <li><a href="http://pware.hvcc.edu">Hudson Valley Community College Open Source Software for IBM System p</a>;
+
+ <li><a href="http://www.perzl.org/aix/">AIX 5L and 6 Open Source Packages</a>.
+</ul>
+
+ <li>DOS&mdash;<a href="http://www.delorie.com/djgpp/">DJGPP</a>.
+
+ <li>Renesas H8/300[HS]&mdash;<a href="http://h8300-hms.sourceforge.net/">GNU Development Tools for the Renesas H8/300[HS] Series</a>.
+
+ <li>HP-UX:
+ <ul>
+<li><a href="http://hpux.connect.org.uk/">HP-UX Porting Center</a>;
+
+ <li><a href="ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/">Binaries for HP-UX 11.00 at Aachen University of Technology</a>.
+</ul>
+
+ <li><a href="http://www.sco.com/skunkware/devtools/index.html#gcc">SCO OpenServer/Unixware</a>.
+
+ <li>Solaris 2 (SPARC, Intel):
+ <ul>
+<li><a href="http://www.sunfreeware.com/">Sunfreeware</a>
+
+ <li><a href="http://www.blastwave.org/">Blastwave</a>
+
+ <li><a href="http://www.opencsw.org/">OpenCSW</a>
+
+ <li><a href="http://jupiterrise.com/tgcware/">TGCware</a>
+</ul>
+
+ <li>SGI IRIX:
+ <ul>
+<li><a href="http://nekochan.net/">Nekoware</a>
+
+ <li><a href="http://jupiterrise.com/tgcware/">TGCware</a>
+</ul>
+
+ <li>Microsoft Windows:
+ <ul>
+<li>The <a href="http://sourceware.org/cygwin/">Cygwin</a> project;
+<li>The <a href="http://www.mingw.org/">MinGW</a> project.
+</ul>
+
+ <li><a href="ftp://ftp.thewrittenword.com/packages/by-name/">The Written Word</a> offers binaries for
+AIX 4.3.3, 5.1 and 5.2,
+IRIX 6.5,
+Tru64 UNIX 4.0D and 5.1,
+GNU/Linux (i386),
+HP-UX 10.20, 11.00, and 11.11, and
+Solaris/SPARC 2.5.1, 2.6, 7, 8, 9 and 10.
+
+ <li><a href="http://www.openpkg.org/">OpenPKG</a> offers binaries for quite a
+number of platforms.
+
+ <li>The <a href="http://gcc.gnu.org/wiki/GFortranBinaries">GFortran Wiki</a> has
+links to GNU Fortran binaries for several platforms.
+</ul>
+
+ <p><hr />
+<p><a href="./index.html">Return to the GCC Installation page</a>
+
+<!-- ***Specific**************************************************************** -->
+<!-- ***Old documentation****************************************************** -->
+<!-- ***GFDL******************************************************************** -->
+<!-- *************************************************************************** -->
+<!-- Part 6 The End of the Document -->
+</body></html>
+
diff --git a/INSTALL/build.html b/INSTALL/build.html
new file mode 100644
index 000000000..644900fd6
--- /dev/null
+++ b/INSTALL/build.html
@@ -0,0 +1,380 @@
+<html lang="en">
+<head>
+<title>Installing GCC: Building</title>
+<meta http-equiv="Content-Type" content="text/html">
+<meta name="description" content="Installing GCC: Building">
+<meta name="generator" content="makeinfo 4.13">
+<link title="Top" rel="top" href="#Top">
+<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
+<!--
+Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
+1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
+2010 Free Software Foundation, Inc.
+
+ Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, the Front-Cover texts being (a) (see below), and
+with the Back-Cover Texts being (b) (see below). A copy of the
+license is included in the section entitled "GNU Free Documentation License".
+
+(a) The FSF's Front-Cover Text is:
+
+ A GNU Manual
+
+(b) The FSF's Back-Cover Text is:
+
+ You have freedom to copy and modify this GNU Manual, like GNU
+ software. Copies published by the Free Software Foundation raise
+ funds for GNU development.-->
+<meta http-equiv="Content-Style-Type" content="text/css">
+<style type="text/css"><!--
+ pre.display { font-family:inherit }
+ pre.format { font-family:inherit }
+ pre.smalldisplay { font-family:inherit; font-size:smaller }
+ pre.smallformat { font-family:inherit; font-size:smaller }
+ pre.smallexample { font-size:smaller }
+ pre.smalllisp { font-size:smaller }
+ span.sc { font-variant:small-caps }
+ span.roman { font-family:serif; font-weight:normal; }
+ span.sansserif { font-family:sans-serif; font-weight:normal; }
+--></style>
+</head>
+<body>
+<h1 class="settitle">Installing GCC: Building</h1>
+<a name="index-Installing-GCC_003a-Building-1"></a>
+Now that GCC is configured, you are ready to build the compiler and
+runtime libraries.
+
+ <p>Some commands executed when making the compiler may fail (return a
+nonzero status) and be ignored by <samp><span class="command">make</span></samp>. These failures, which
+are often due to files that were not found, are expected, and can safely
+be ignored.
+
+ <p>It is normal to have compiler warnings when compiling certain files.
+Unless you are a GCC developer, you can generally ignore these warnings
+unless they cause compilation to fail. Developers should attempt to fix
+any warnings encountered, however they can temporarily continue past
+warnings-as-errors by specifying the configure flag
+<samp><span class="option">--disable-werror</span></samp>.
+
+ <p>On certain old systems, defining certain environment variables such as
+<samp><span class="env">CC</span></samp> can interfere with the functioning of <samp><span class="command">make</span></samp>.
+
+ <p>If you encounter seemingly strange errors when trying to build the
+compiler in a directory other than the source directory, it could be
+because you have previously configured the compiler in the source
+directory. Make sure you have done all the necessary preparations.
+
+ <p>If you build GCC on a BSD system using a directory stored in an old System
+V file system, problems may occur in running <samp><span class="command">fixincludes</span></samp> if the
+System V file system doesn't support symbolic links. These problems
+result in a failure to fix the declaration of <code>size_t</code> in
+<samp><span class="file">sys/types.h</span></samp>. If you find that <code>size_t</code> is a signed type and
+that type mismatches occur, this could be the cause.
+
+ <p>The solution is not to use such a directory for building GCC.
+
+ <p>Similarly, when building from SVN or snapshots, or if you modify
+<samp><span class="file">*.l</span></samp> files, you need the Flex lexical analyzer generator
+installed. If you do not modify <samp><span class="file">*.l</span></samp> files, releases contain
+the Flex-generated files and you do not need Flex installed to build
+them. There is still one Flex-based lexical analyzer (part of the
+build machinery, not of GCC itself) that is used even if you only
+build the C front end.
+
+ <p>When building from SVN or snapshots, or if you modify Texinfo
+documentation, you need version 4.7 or later of Texinfo installed if you
+want Info documentation to be regenerated. Releases contain Info
+documentation pre-built for the unmodified documentation in the release.
+
+<h3 class="section"><a name="TOC0"></a>Building a native compiler</h3>
+
+<p>For a native build, the default configuration is to perform
+a 3-stage bootstrap of the compiler when &lsquo;<samp><span class="samp">make</span></samp>&rsquo; is invoked.
+This will build the entire GCC system and ensure that it compiles
+itself correctly. It can be disabled with the <samp><span class="option">--disable-bootstrap</span></samp>
+parameter to &lsquo;<samp><span class="samp">configure</span></samp>&rsquo;, but bootstrapping is suggested because
+the compiler will be tested more completely and could also have
+better performance.
+
+ <p>The bootstrapping process will complete the following steps:
+
+ <ul>
+<li>Build tools necessary to build the compiler.
+
+ <li>Perform a 3-stage bootstrap of the compiler. This includes building
+three times the target tools for use by the compiler such as binutils
+(bfd, binutils, gas, gprof, ld, and opcodes) if they have been
+individually linked or moved into the top level GCC source tree before
+configuring.
+
+ <li>Perform a comparison test of the stage2 and stage3 compilers.
+
+ <li>Build runtime libraries using the stage3 compiler from the previous step.
+
+ </ul>
+
+ <p>If you are short on disk space you might consider &lsquo;<samp><span class="samp">make
+bootstrap-lean</span></samp>&rsquo; instead. The sequence of compilation is the
+same described above, but object files from the stage1 and
+stage2 of the 3-stage bootstrap of the compiler are deleted as
+soon as they are no longer needed.
+
+ <p>If you wish to use non-default GCC flags when compiling the stage2
+and stage3 compilers, set <code>BOOT_CFLAGS</code> on the command line when
+doing &lsquo;<samp><span class="samp">make</span></samp>&rsquo;. For example, if you want to save additional space
+during the bootstrap and in the final installation as well, you can
+build the compiler binaries without debugging information as in the
+following example. This will save roughly 40% of disk space both for
+the bootstrap and the final installation. (Libraries will still contain
+debugging information.)
+
+<pre class="smallexample"> make BOOT_CFLAGS='-O' bootstrap
+</pre>
+ <p>You can place non-default optimization flags into <code>BOOT_CFLAGS</code>; they
+are less well tested here than the default of &lsquo;<samp><span class="samp">-g -O2</span></samp>&rsquo;, but should
+still work. In a few cases, you may find that you need to specify special
+flags such as <samp><span class="option">-msoft-float</span></samp> here to complete the bootstrap; or,
+if the native compiler miscompiles the stage1 compiler, you may need
+to work around this, by choosing <code>BOOT_CFLAGS</code> to avoid the parts
+of the stage1 compiler that were miscompiled, or by using &lsquo;<samp><span class="samp">make
+bootstrap4</span></samp>&rsquo; to increase the number of stages of bootstrap.
+
+ <p><code>BOOT_CFLAGS</code> does not apply to bootstrapped target libraries.
+Since these are always compiled with the compiler currently being
+bootstrapped, you can use <code>CFLAGS_FOR_TARGET</code> to modify their
+compilation flags, as for non-bootstrapped target libraries.
+Again, if the native compiler miscompiles the stage1 compiler, you may
+need to work around this by avoiding non-working parts of the stage1
+compiler. Use <code>STAGE1_TFLAGS</code> to this end.
+
+ <p>If you used the flag <samp><span class="option">--enable-languages=...</span></samp> to restrict
+the compilers to be built, only those you've actually enabled will be
+built. This will of course only build those runtime libraries, for
+which the particular compiler has been built. Please note,
+that re-defining <samp><span class="env">LANGUAGES</span></samp> when calling &lsquo;<samp><span class="samp">make</span></samp>&rsquo;
+<strong>does not</strong> work anymore!
+
+ <p>If the comparison of stage2 and stage3 fails, this normally indicates
+that the stage2 compiler has compiled GCC incorrectly, and is therefore
+a potentially serious bug which you should investigate and report. (On
+a few systems, meaningful comparison of object files is impossible; they
+always appear &ldquo;different&rdquo;. If you encounter this problem, you will
+need to disable comparison in the <samp><span class="file">Makefile</span></samp>.)
+
+ <p>If you do not want to bootstrap your compiler, you can configure with
+<samp><span class="option">--disable-bootstrap</span></samp>. In particular cases, you may want to
+bootstrap your compiler even if the target system is not the same as
+the one you are building on: for example, you could build a
+<code>powerpc-unknown-linux-gnu</code> toolchain on a
+<code>powerpc64-unknown-linux-gnu</code> host. In this case, pass
+<samp><span class="option">--enable-bootstrap</span></samp> to the configure script.
+
+ <p><code>BUILD_CONFIG</code> can be used to bring in additional customization
+to the build. It can be set to a whitespace-separated list of names.
+For each such <code>NAME</code>, top-level <samp><span class="file">config/</span><code>NAME</code><span class="file">.mk</span></samp> will
+be included by the top-level <samp><span class="file">Makefile</span></samp>, bringing in any settings
+it contains. The default <code>BUILD_CONFIG</code> can be set using the
+configure option <samp><span class="option">--with-build-config=</span><code>NAME</code><span class="option">...</span></samp>. Some
+examples of supported build configurations are:
+
+ <dl>
+<dt>&lsquo;<samp><span class="samp">bootstrap-O1</span></samp>&rsquo;<dd>Removes any <samp><span class="option">-O</span></samp>-started option from <code>BOOT_CFLAGS</code>, and adds
+<samp><span class="option">-O1</span></samp> to it. &lsquo;<samp><span class="samp">BUILD_CONFIG=bootstrap-O1</span></samp>&rsquo; is equivalent to
+&lsquo;<samp><span class="samp">BOOT_CFLAGS='-g -O1'</span></samp>&rsquo;.
+
+ <br><dt>&lsquo;<samp><span class="samp">bootstrap-O3</span></samp>&rsquo;<dd>Analogous to <code>bootstrap-O1</code>.
+
+ <br><dt>&lsquo;<samp><span class="samp">bootstrap-lto</span></samp>&rsquo;<dd>Enables Link-Time Optimization for host tools during bootstrapping.
+&lsquo;<samp><span class="samp">BUILD_CONFIG=bootstrap-lto</span></samp>&rsquo; is equivalent to adding
+<samp><span class="option">-flto</span></samp> to &lsquo;<samp><span class="samp">BOOT_CFLAGS</span></samp>&rsquo;.
+
+ <br><dt>&lsquo;<samp><span class="samp">bootstrap-debug</span></samp>&rsquo;<dd>Verifies that the compiler generates the same executable code, whether
+or not it is asked to emit debug information. To this end, this
+option builds stage2 host programs without debug information, and uses
+<samp><span class="file">contrib/compare-debug</span></samp> to compare them with the stripped stage3
+object files. If <code>BOOT_CFLAGS</code> is overridden so as to not enable
+debug information, stage2 will have it, and stage3 won't. This option
+is enabled by default when GCC bootstrapping is enabled, if
+<code>strip</code> can turn object files compiled with and without debug
+info into identical object files. In addition to better test
+coverage, this option makes default bootstraps faster and leaner.
+
+ <br><dt>&lsquo;<samp><span class="samp">bootstrap-debug-big</span></samp>&rsquo;<dd>Rather than comparing stripped object files, as in
+<code>bootstrap-debug</code>, this option saves internal compiler dumps
+during stage2 and stage3 and compares them as well, which helps catch
+additional potential problems, but at a great cost in terms of disk
+space. It can be specified in addition to &lsquo;<samp><span class="samp">bootstrap-debug</span></samp>&rsquo;.
+
+ <br><dt>&lsquo;<samp><span class="samp">bootstrap-debug-lean</span></samp>&rsquo;<dd>This option saves disk space compared with <code>bootstrap-debug-big</code>,
+but at the expense of some recompilation. Instead of saving the dumps
+of stage2 and stage3 until the final compare, it uses
+<samp><span class="option">-fcompare-debug</span></samp> to generate, compare and remove the dumps
+during stage3, repeating the compilation that already took place in
+stage2, whose dumps were not saved.
+
+ <br><dt>&lsquo;<samp><span class="samp">bootstrap-debug-lib</span></samp>&rsquo;<dd>This option tests executable code invariance over debug information
+generation on target libraries, just like <code>bootstrap-debug-lean</code>
+tests it on host programs. It builds stage3 libraries with
+<samp><span class="option">-fcompare-debug</span></samp>, and it can be used along with any of the
+<code>bootstrap-debug</code> options above.
+
+ <p>There aren't <code>-lean</code> or <code>-big</code> counterparts to this option
+because most libraries are only build in stage3, so bootstrap compares
+would not get significant coverage. Moreover, the few libraries built
+in stage2 are used in stage3 host programs, so we wouldn't want to
+compile stage2 libraries with different options for comparison purposes.
+
+ <br><dt>&lsquo;<samp><span class="samp">bootstrap-debug-ckovw</span></samp>&rsquo;<dd>Arranges for error messages to be issued if the compiler built on any
+stage is run without the option <samp><span class="option">-fcompare-debug</span></samp>. This is
+useful to verify the full <samp><span class="option">-fcompare-debug</span></samp> testing coverage. It
+must be used along with <code>bootstrap-debug-lean</code> and
+<code>bootstrap-debug-lib</code>.
+
+ <br><dt>&lsquo;<samp><span class="samp">bootstrap-time</span></samp>&rsquo;<dd>Arranges for the run time of each program started by the GCC driver,
+built in any stage, to be logged to <samp><span class="file">time.log</span></samp>, in the top level of
+the build tree.
+
+ </dl>
+
+<h3 class="section"><a name="TOC1"></a>Building a cross compiler</h3>
+
+<p>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.
+
+ <p>To build a cross compiler, we recommend first building and installing a
+native compiler. You can then use the native GCC compiler to build the
+cross compiler. The installed native compiler needs to be GCC version
+2.95 or later.
+
+ <p>If the cross compiler is to be built with support for the Java
+programming language and the ability to compile .java source files is
+desired, the installed native compiler used to build the cross
+compiler needs to be the same GCC version as the cross compiler. In
+addition the cross compiler needs to be configured with
+<samp><span class="option">--with-ecj-jar=...</span></samp>.
+
+ <p>Assuming you have already installed a native copy of GCC and configured
+your cross compiler, issue the command <samp><span class="command">make</span></samp>, which performs the
+following steps:
+
+ <ul>
+<li>Build host tools necessary to build the compiler.
+
+ <li>Build target tools for use by the compiler such as binutils (bfd,
+binutils, gas, gprof, ld, and opcodes)
+if they have been individually linked or moved into the top level GCC source
+tree before configuring.
+
+ <li>Build the compiler (single stage only).
+
+ <li>Build runtime libraries using the compiler from the previous step.
+</ul>
+
+ <p>Note that if an error occurs in any step the make process will exit.
+
+ <p>If you are not building GNU binutils in the same source tree as GCC,
+you will need a cross-assembler and cross-linker installed before
+configuring GCC. Put them in the directory
+<samp><var>prefix</var><span class="file">/</span><var>target</var><span class="file">/bin</span></samp>. Here is a table of the tools
+you should put in this directory:
+
+ <dl>
+<dt><samp><span class="file">as</span></samp><dd>This should be the cross-assembler.
+
+ <br><dt><samp><span class="file">ld</span></samp><dd>This should be the cross-linker.
+
+ <br><dt><samp><span class="file">ar</span></samp><dd>This should be the cross-archiver: a program which can manipulate
+archive files (linker libraries) in the target machine's format.
+
+ <br><dt><samp><span class="file">ranlib</span></samp><dd>This should be a program to construct a symbol table in an archive file.
+</dl>
+
+ <p>The installation of GCC will find these programs in that directory,
+and copy or link them to the proper place to for the cross-compiler to
+find them when run later.
+
+ <p>The easiest way to provide these files is to build the Binutils package.
+Configure it with the same <samp><span class="option">--host</span></samp> and <samp><span class="option">--target</span></samp>
+options that you use for configuring GCC, then build and install
+them. They install their executables automatically into the proper
+directory. Alas, they do not support all the targets that GCC
+supports.
+
+ <p>If you are not building a C library in the same source tree as GCC,
+you should also provide the target libraries and headers before
+configuring GCC, specifying the directories with
+<samp><span class="option">--with-sysroot</span></samp> or <samp><span class="option">--with-headers</span></samp> and
+<samp><span class="option">--with-libs</span></samp>. Many targets also require &ldquo;start files&rdquo; such
+as <samp><span class="file">crt0.o</span></samp> and
+<samp><span class="file">crtn.o</span></samp> which are linked into each executable. There may be several
+alternatives for <samp><span class="file">crt0.o</span></samp>, for use with profiling or other
+compilation options. Check your target's definition of
+<code>STARTFILE_SPEC</code> to find out what start files it uses.
+
+<h3 class="section"><a name="TOC2"></a>Building in parallel</h3>
+
+<p>GNU Make 3.80 and above, which is necessary to build GCC, support
+building in parallel. To activate this, you can use &lsquo;<samp><span class="samp">make -j 2</span></samp>&rsquo;
+instead of &lsquo;<samp><span class="samp">make</span></samp>&rsquo;. You can also specify a bigger number, and
+in most cases using a value greater than the number of processors in
+your machine will result in fewer and shorter I/O latency hits, thus
+improving overall throughput; this is especially true for slow drives
+and network filesystems.
+
+<h3 class="section"><a name="TOC3"></a>Building the Ada compiler</h3>
+
+<p>In order to build GNAT, the Ada compiler, you need a working GNAT
+compiler (GCC version 4.0 or later).
+This includes GNAT tools such as <samp><span class="command">gnatmake</span></samp> and
+<samp><span class="command">gnatlink</span></samp>, since the Ada front end is written in Ada and
+uses some GNAT-specific extensions.
+
+ <p>In order to build a cross compiler, it is suggested to install
+the new compiler as native first, and then use it to build the cross
+compiler.
+
+ <p><samp><span class="command">configure</span></samp> does not test whether the GNAT installation works
+and has a sufficiently recent version; if too old a GNAT version is
+installed, the build will fail unless <samp><span class="option">--enable-languages</span></samp> is
+used to disable building the Ada front end.
+
+ <p><samp><span class="env">ADA_INCLUDE_PATH</span></samp> and <samp><span class="env">ADA_OBJECT_PATH</span></samp> environment variables
+must not be set when building the Ada compiler, the Ada tools, or the
+Ada runtime libraries. You can check that your build environment is clean
+by verifying that &lsquo;<samp><span class="samp">gnatls -v</span></samp>&rsquo; lists only one explicit path in each
+section.
+
+<h3 class="section"><a name="TOC4"></a>Building with profile feedback</h3>
+
+<p>It is possible to use profile feedback to optimize the compiler itself. This
+should result in a faster compiler binary. Experiments done on x86 using gcc
+3.3 showed approximately 7 percent speedup on compiling C programs. To
+bootstrap the compiler with profile feedback, use <code>make profiledbootstrap</code>.
+
+ <p>When &lsquo;<samp><span class="samp">make profiledbootstrap</span></samp>&rsquo; is run, it will first build a <code>stage1</code>
+compiler. This compiler is used to build a <code>stageprofile</code> compiler
+instrumented to collect execution counts of instruction and branch
+probabilities. Then runtime libraries are compiled with profile collected.
+Finally a <code>stagefeedback</code> compiler is built using the information collected.
+
+ <p>Unlike standard bootstrap, several additional restrictions apply. The
+compiler used to build <code>stage1</code> needs to support a 64-bit integral type.
+It is recommended to only use GCC for this. Also parallel make is currently
+not supported since collisions in profile collecting may occur.
+
+ <p><hr />
+<p><a href="./index.html">Return to the GCC Installation page</a>
+
+<!-- ***Testing***************************************************************** -->
+<!-- ***Final install*********************************************************** -->
+<!-- ***Binaries**************************************************************** -->
+<!-- ***Specific**************************************************************** -->
+<!-- ***Old documentation****************************************************** -->
+<!-- ***GFDL******************************************************************** -->
+<!-- *************************************************************************** -->
+<!-- Part 6 The End of the Document -->
+</body></html>
+
diff --git a/INSTALL/configure.html b/INSTALL/configure.html
new file mode 100644
index 000000000..6bb61c688
--- /dev/null
+++ b/INSTALL/configure.html
@@ -0,0 +1,1249 @@
+<html lang="en">
+<head>
+<title>Installing GCC: Configuration</title>
+<meta http-equiv="Content-Type" content="text/html">
+<meta name="description" content="Installing GCC: Configuration">
+<meta name="generator" content="makeinfo 4.13">
+<link title="Top" rel="top" href="#Top">
+<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
+<!--
+Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
+1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
+2010 Free Software Foundation, Inc.
+
+ Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, the Front-Cover texts being (a) (see below), and
+with the Back-Cover Texts being (b) (see below). A copy of the
+license is included in the section entitled "GNU Free Documentation License".
+
+(a) The FSF's Front-Cover Text is:
+
+ A GNU Manual
+
+(b) The FSF's Back-Cover Text is:
+
+ You have freedom to copy and modify this GNU Manual, like GNU
+ software. Copies published by the Free Software Foundation raise
+ funds for GNU development.-->
+<meta http-equiv="Content-Style-Type" content="text/css">
+<style type="text/css"><!--
+ pre.display { font-family:inherit }
+ pre.format { font-family:inherit }
+ pre.smalldisplay { font-family:inherit; font-size:smaller }
+ pre.smallformat { font-family:inherit; font-size:smaller }
+ pre.smallexample { font-size:smaller }
+ pre.smalllisp { font-size:smaller }
+ span.sc { font-variant:small-caps }
+ span.roman { font-family:serif; font-weight:normal; }
+ span.sansserif { font-family:sans-serif; font-weight:normal; }
+--></style>
+</head>
+<body>
+<h1 class="settitle">Installing GCC: Configuration</h1>
+<a name="index-Configuration-1"></a><a name="index-Installing-GCC_003a-Configuration-2"></a>
+Like most GNU software, GCC must be configured before it can be built.
+This document describes the recommended configuration procedure
+for both native and cross targets.
+
+ <p>We use <var>srcdir</var> to refer to the toplevel source directory for
+GCC; we use <var>objdir</var> to refer to the toplevel build/object directory.
+
+ <p>If you obtained the sources via SVN, <var>srcdir</var> must refer to the top
+<samp><span class="file">gcc</span></samp> directory, the one where the <samp><span class="file">MAINTAINERS</span></samp> file can be
+found, and not its <samp><span class="file">gcc</span></samp> subdirectory, otherwise the build will fail.
+
+ <p>If either <var>srcdir</var> or <var>objdir</var> is located on an automounted NFS
+file system, the shell's built-in <samp><span class="command">pwd</span></samp> command will return
+temporary pathnames. Using these can lead to various sorts of build
+problems. To avoid this issue, set the <samp><span class="env">PWDCMD</span></samp> environment
+variable to an automounter-aware <samp><span class="command">pwd</span></samp> command, e.g.,
+<samp><span class="command">pawd</span></samp> or &lsquo;<samp><span class="samp">amq -w</span></samp>&rsquo;, during the configuration and build
+phases.
+
+ <p>First, we <strong>highly</strong> recommend that GCC be built into a
+separate directory from the sources which does <strong>not</strong> reside
+within the source tree. This is how we generally build GCC; building
+where <var>srcdir</var> == <var>objdir</var> should still work, but doesn't
+get extensive testing; building where <var>objdir</var> is a subdirectory
+of <var>srcdir</var> is unsupported.
+
+ <p>If you have previously built GCC in the same directory for a
+different target machine, do &lsquo;<samp><span class="samp">make distclean</span></samp>&rsquo; to delete all files
+that might be invalid. One of the files this deletes is <samp><span class="file">Makefile</span></samp>;
+if &lsquo;<samp><span class="samp">make distclean</span></samp>&rsquo; complains that <samp><span class="file">Makefile</span></samp> does not exist
+or issues a message like &ldquo;don't know how to make distclean&rdquo; it probably
+means that the directory is already suitably clean. However, with the
+recommended method of building in a separate <var>objdir</var>, you should
+simply use a different <var>objdir</var> for each target.
+
+ <p>Second, when configuring a native system, either <samp><span class="command">cc</span></samp> or
+<samp><span class="command">gcc</span></samp> must be in your path or you must set <samp><span class="env">CC</span></samp> in
+your environment before running configure. Otherwise the configuration
+scripts may fail.
+
+ <p>To configure GCC:
+
+<pre class="smallexample"> % mkdir <var>objdir</var>
+ % cd <var>objdir</var>
+ % <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>]
+</pre>
+ <h3 class="heading"><a name="TOC0"></a>Distributor options</h3>
+
+<p>If you will be distributing binary versions of GCC, with modifications
+to the source code, you should use the options described in this
+section to make clear that your version contains modifications.
+
+ <dl>
+<dt><code>--with-pkgversion=</code><var>version</var><dd>Specify a string that identifies your package. You may wish
+to include a build number or build date. This version string will be
+included in the output of <samp><span class="command">gcc --version</span></samp>. This suffix does
+not replace the default version string, only the &lsquo;<samp><span class="samp">GCC</span></samp>&rsquo; part.
+
+ <p>The default value is &lsquo;<samp><span class="samp">GCC</span></samp>&rsquo;.
+
+ <br><dt><code>--with-bugurl=</code><var>url</var><dd>Specify the URL that users should visit if they wish to report a bug.
+You are of course welcome to forward bugs reported to you to the FSF,
+if you determine that they are not bugs in your modifications.
+
+ <p>The default value refers to the FSF's GCC bug tracker.
+
+ </dl>
+
+<h3 class="heading"><a name="TOC1"></a>Target specification</h3>
+
+ <ul>
+<li>GCC has code to correctly determine the correct value for <var>target</var>
+for nearly all native systems. Therefore, we highly recommend you do
+not provide a configure target when configuring a native compiler.
+
+ <li><var>target</var> must be specified as <samp><span class="option">--target=</span><var>target</var></samp>
+when configuring a cross compiler; examples of valid targets would be
+m68k-elf, sh-elf, etc.
+
+ <li>Specifying just <var>target</var> instead of <samp><span class="option">--target=</span><var>target</var></samp>
+implies that the host defaults to <var>target</var>.
+</ul>
+
+<h3 class="heading"><a name="TOC2"></a>Options specification</h3>
+
+<p>Use <var>options</var> to override several configure time options for
+GCC. A list of supported <var>options</var> follows; &lsquo;<samp><span class="samp">configure
+--help</span></samp>&rsquo; may list other options, but those not listed below may not
+work and should not normally be used.
+
+ <p>Note that each <samp><span class="option">--enable</span></samp> option has a corresponding
+<samp><span class="option">--disable</span></samp> option and that each <samp><span class="option">--with</span></samp> option has a
+corresponding <samp><span class="option">--without</span></samp> option.
+
+ <dl>
+<dt><code>--prefix=</code><var>dirname</var><dd>Specify the toplevel installation
+directory. This is the recommended way to install the tools into a directory
+other than the default. The toplevel installation directory defaults to
+<samp><span class="file">/usr/local</span></samp>.
+
+ <p>We <strong>highly</strong> recommend against <var>dirname</var> being the same or a
+subdirectory of <var>objdir</var> or vice versa. If specifying a directory
+beneath a user's home directory tree, some shells will not expand
+<var>dirname</var> correctly if it contains the &lsquo;<samp><span class="samp">~</span></samp>&rsquo; metacharacter; use
+<samp><span class="env">$HOME</span></samp> instead.
+
+ <p>The following standard <samp><span class="command">autoconf</span></samp> options are supported. Normally you
+should not need to use these options.
+ <dl>
+<dt><code>--exec-prefix=</code><var>dirname</var><dd>Specify the toplevel installation directory for architecture-dependent
+files. The default is <samp><var>prefix</var></samp>.
+
+ <br><dt><code>--bindir=</code><var>dirname</var><dd>Specify the installation directory for the executables called by users
+(such as <samp><span class="command">gcc</span></samp> and <samp><span class="command">g++</span></samp>). The default is
+<samp><var>exec-prefix</var><span class="file">/bin</span></samp>.
+
+ <br><dt><code>--libdir=</code><var>dirname</var><dd>Specify the installation directory for object code libraries and
+internal data files of GCC. The default is <samp><var>exec-prefix</var><span class="file">/lib</span></samp>.
+
+ <br><dt><code>--libexecdir=</code><var>dirname</var><dd>Specify the installation directory for internal executables of GCC.
+The default is <samp><var>exec-prefix</var><span class="file">/libexec</span></samp>.
+
+ <br><dt><code>--with-slibdir=</code><var>dirname</var><dd>Specify the installation directory for the shared libgcc library. The
+default is <samp><var>libdir</var></samp>.
+
+ <br><dt><code>--datarootdir=</code><var>dirname</var><dd>Specify the root of the directory tree for read-only architecture-independent
+data files referenced by GCC. The default is <samp><var>prefix</var><span class="file">/share</span></samp>.
+
+ <br><dt><code>--infodir=</code><var>dirname</var><dd>Specify the installation directory for documentation in info format.
+The default is <samp><var>datarootdir</var><span class="file">/info</span></samp>.
+
+ <br><dt><code>--datadir=</code><var>dirname</var><dd>Specify the installation directory for some architecture-independent
+data files referenced by GCC. The default is <samp><var>datarootdir</var></samp>.
+
+ <br><dt><code>--docdir=</code><var>dirname</var><dd>Specify the installation directory for documentation files (other
+than Info) for GCC. The default is <samp><var>datarootdir</var><span class="file">/doc</span></samp>.
+
+ <br><dt><code>--htmldir=</code><var>dirname</var><dd>Specify the installation directory for HTML documentation files.
+The default is <samp><var>docdir</var></samp>.
+
+ <br><dt><code>--pdfdir=</code><var>dirname</var><dd>Specify the installation directory for PDF documentation files.
+The default is <samp><var>docdir</var></samp>.
+
+ <br><dt><code>--mandir=</code><var>dirname</var><dd>Specify the installation directory for manual pages. The default is
+<samp><var>datarootdir</var><span class="file">/man</span></samp>. (Note that the manual pages are only extracts
+from the full GCC manuals, which are provided in Texinfo format. The manpages
+are derived by an automatic conversion process from parts of the full
+manual.)
+
+ <br><dt><code>--with-gxx-include-dir=</code><var>dirname</var><dd>Specify
+the installation directory for G++ header files. The default depends
+on other configuration options, and differs between cross and native
+configurations.
+
+ </dl>
+
+ <br><dt><code>--program-prefix=</code><var>prefix</var><dd>GCC supports some transformations of the names of its programs when
+installing them. This option prepends <var>prefix</var> to the names of
+programs to install in <var>bindir</var> (see above). For example, specifying
+<samp><span class="option">--program-prefix=foo-</span></samp> would result in &lsquo;<samp><span class="samp">gcc</span></samp>&rsquo;
+being installed as <samp><span class="file">/usr/local/bin/foo-gcc</span></samp>.
+
+ <br><dt><code>--program-suffix=</code><var>suffix</var><dd>Appends <var>suffix</var> to the names of programs to install in <var>bindir</var>
+(see above). For example, specifying <samp><span class="option">--program-suffix=-3.1</span></samp>
+would result in &lsquo;<samp><span class="samp">gcc</span></samp>&rsquo; being installed as
+<samp><span class="file">/usr/local/bin/gcc-3.1</span></samp>.
+
+ <br><dt><code>--program-transform-name=</code><var>pattern</var><dd>Applies the &lsquo;<samp><span class="samp">sed</span></samp>&rsquo; script <var>pattern</var> to be applied to the names
+of programs to install in <var>bindir</var> (see above). <var>pattern</var> has to
+consist of one or more basic &lsquo;<samp><span class="samp">sed</span></samp>&rsquo; editing commands, separated by
+semicolons. For example, if you want the &lsquo;<samp><span class="samp">gcc</span></samp>&rsquo; program name to be
+transformed to the installed program <samp><span class="file">/usr/local/bin/myowngcc</span></samp> and
+the &lsquo;<samp><span class="samp">g++</span></samp>&rsquo; program name to be transformed to
+<samp><span class="file">/usr/local/bin/gspecial++</span></samp> without changing other program names,
+you could use the pattern
+<samp><span class="option">--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'</span></samp>
+to achieve this effect.
+
+ <p>All three options can be combined and used together, resulting in more
+complex conversion patterns. As a basic rule, <var>prefix</var> (and
+<var>suffix</var>) are prepended (appended) before further transformations
+can happen with a special transformation script <var>pattern</var>.
+
+ <p>As currently implemented, this option only takes effect for native
+builds; cross compiler binaries' names are not transformed even when a
+transformation is explicitly asked for by one of these options.
+
+ <p>For native builds, some of the installed programs are also installed
+with the target alias in front of their name, as in
+&lsquo;<samp><span class="samp">i686-pc-linux-gnu-gcc</span></samp>&rsquo;. All of the above transformations happen
+before the target alias is prepended to the name&mdash;so, specifying
+<samp><span class="option">--program-prefix=foo-</span></samp> and <samp><span class="option">program-suffix=-3.1</span></samp>, the
+resulting binary would be installed as
+<samp><span class="file">/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1</span></samp>.
+
+ <p>As a last shortcoming, none of the installed Ada programs are
+transformed yet, which will be fixed in some time.
+
+ <br><dt><code>--with-local-prefix=</code><var>dirname</var><dd>Specify the
+installation directory for local include files. The default is
+<samp><span class="file">/usr/local</span></samp>. Specify this option if you want the compiler to
+search directory <samp><var>dirname</var><span class="file">/include</span></samp> for locally installed
+header files <em>instead</em> of <samp><span class="file">/usr/local/include</span></samp>.
+
+ <p>You should specify <samp><span class="option">--with-local-prefix</span></samp> <strong>only</strong> if your
+site has a different convention (not <samp><span class="file">/usr/local</span></samp>) for where to put
+site-specific files.
+
+ <p>The default value for <samp><span class="option">--with-local-prefix</span></samp> is <samp><span class="file">/usr/local</span></samp>
+regardless of the value of <samp><span class="option">--prefix</span></samp>. Specifying
+<samp><span class="option">--prefix</span></samp> has no effect on which directory GCC searches for
+local header files. This may seem counterintuitive, but actually it is
+logical.
+
+ <p>The purpose of <samp><span class="option">--prefix</span></samp> is to specify where to <em>install
+GCC</em>. The local header files in <samp><span class="file">/usr/local/include</span></samp>&mdash;if you put
+any in that directory&mdash;are not part of GCC. They are part of other
+programs&mdash;perhaps many others. (GCC installs its own header files in
+another directory which is based on the <samp><span class="option">--prefix</span></samp> value.)
+
+ <p>Both the local-prefix include directory and the GCC-prefix include
+directory are part of GCC's &ldquo;system include&rdquo; directories. Although these
+two directories are not fixed, they need to be searched in the proper
+order for the correct processing of the include_next directive. The
+local-prefix include directory is searched before the GCC-prefix
+include directory. Another characteristic of system include directories
+is that pedantic warnings are turned off for headers in these directories.
+
+ <p>Some autoconf macros add <samp><span class="option">-I </span><var>directory</var></samp> options to the
+compiler command line, to ensure that directories containing installed
+packages' headers are searched. When <var>directory</var> is one of GCC's
+system include directories, GCC will ignore the option so that system
+directories continue to be processed in the correct order. This
+may result in a search order different from what was specified but the
+directory will still be searched.
+
+ <p>GCC automatically searches for ordinary libraries using
+<samp><span class="env">GCC_EXEC_PREFIX</span></samp>. Thus, when the same installation prefix is
+used for both GCC and packages, GCC will automatically search for
+both headers and libraries. This provides a configuration that is
+easy to use. GCC behaves in a manner similar to that when it is
+installed as a system compiler in <samp><span class="file">/usr</span></samp>.
+
+ <p>Sites that need to install multiple versions of GCC may not want to
+use the above simple configuration. It is possible to use the
+<samp><span class="option">--program-prefix</span></samp>, <samp><span class="option">--program-suffix</span></samp> and
+<samp><span class="option">--program-transform-name</span></samp> options to install multiple versions
+into a single directory, but it may be simpler to use different prefixes
+and the <samp><span class="option">--with-local-prefix</span></samp> option to specify the location of the
+site-specific files for each version. It will then be necessary for
+users to specify explicitly the location of local site libraries
+(e.g., with <samp><span class="env">LIBRARY_PATH</span></samp>).
+
+ <p>The same value can be used for both <samp><span class="option">--with-local-prefix</span></samp> and
+<samp><span class="option">--prefix</span></samp> provided it is not <samp><span class="file">/usr</span></samp>. This can be used
+to avoid the default search of <samp><span class="file">/usr/local/include</span></samp>.
+
+ <p><strong>Do not</strong> specify <samp><span class="file">/usr</span></samp> as the <samp><span class="option">--with-local-prefix</span></samp>!
+The directory you use for <samp><span class="option">--with-local-prefix</span></samp> <strong>must not</strong>
+contain any of the system's standard header files. If it did contain
+them, certain programs would be miscompiled (including GNU Emacs, on
+certain targets), because this would override and nullify the header
+file corrections made by the <samp><span class="command">fixincludes</span></samp> script.
+
+ <p>Indications are that people who use this option use it based on mistaken
+ideas of what it is for. People use it as if it specified where to
+install part of GCC. Perhaps they make this assumption because
+installing GCC creates the directory.
+
+ <br><dt><code>--enable-shared[=</code><var>package</var><code>[,...]]</code><dd>Build shared versions of libraries, if shared libraries are supported on
+the target platform. Unlike GCC 2.95.x and earlier, shared libraries
+are enabled by default on all platforms that support shared libraries.
+
+ <p>If a list of packages is given as an argument, build shared libraries
+only for the listed packages. For other packages, only static libraries
+will be built. Package names currently recognized in the GCC tree are
+&lsquo;<samp><span class="samp">libgcc</span></samp>&rsquo; (also known as &lsquo;<samp><span class="samp">gcc</span></samp>&rsquo;), &lsquo;<samp><span class="samp">libstdc++</span></samp>&rsquo; (not
+&lsquo;<samp><span class="samp">libstdc++-v3</span></samp>&rsquo;), &lsquo;<samp><span class="samp">libffi</span></samp>&rsquo;, &lsquo;<samp><span class="samp">zlib</span></samp>&rsquo;, &lsquo;<samp><span class="samp">boehm-gc</span></samp>&rsquo;,
+&lsquo;<samp><span class="samp">ada</span></samp>&rsquo;, &lsquo;<samp><span class="samp">libada</span></samp>&rsquo;, &lsquo;<samp><span class="samp">libjava</span></samp>&rsquo;, &lsquo;<samp><span class="samp">libgo</span></samp>&rsquo;, and &lsquo;<samp><span class="samp">libobjc</span></samp>&rsquo;.
+Note &lsquo;<samp><span class="samp">libiberty</span></samp>&rsquo; does not support shared libraries at all.
+
+ <p>Use <samp><span class="option">--disable-shared</span></samp> to build only static libraries. Note that
+<samp><span class="option">--disable-shared</span></samp> does not accept a list of package names as
+argument, only <samp><span class="option">--enable-shared</span></samp> does.
+
+ <br><dt><code><a name="with_002dgnu_002das"></a>--with-gnu-as</code><dd>Specify that the compiler should assume that the
+assembler it finds is the GNU assembler. However, this does not modify
+the rules to find an assembler and will result in confusion if the
+assembler found is not actually the GNU assembler. (Confusion may also
+result if the compiler finds the GNU assembler but has not been
+configured with <samp><span class="option">--with-gnu-as</span></samp>.) If you have more than one
+assembler installed on your system, you may want to use this option in
+connection with <samp><span class="option">--with-as=</span><var>pathname</var></samp> or
+<samp><span class="option">--with-build-time-tools=</span><var>pathname</var></samp>.
+
+ <p>The following systems are the only ones where it makes a difference
+whether you use the GNU assembler. On any other system,
+<samp><span class="option">--with-gnu-as</span></samp> has no effect.
+
+ <ul>
+<li>&lsquo;<samp><span class="samp">hppa1.0-</span><var>any</var><span class="samp">-</span><var>any</var></samp>&rsquo;
+<li>&lsquo;<samp><span class="samp">hppa1.1-</span><var>any</var><span class="samp">-</span><var>any</var></samp>&rsquo;
+<li>&lsquo;<samp><span class="samp">sparc-sun-solaris2.</span><var>any</var></samp>&rsquo;
+<li>&lsquo;<samp><span class="samp">sparc64-</span><var>any</var><span class="samp">-solaris2.</span><var>any</var></samp>&rsquo;
+</ul>
+
+ <br><dt><code><a name="with_002das"></a>--with-as=</code><var>pathname</var><dd>Specify that the compiler should use the assembler pointed to by
+<var>pathname</var>, rather than the one found by the standard rules to find
+an assembler, which are:
+ <ul>
+<li>Unless GCC is being built with a cross compiler, check the
+<samp><var>libexec</var><span class="file">/gcc/</span><var>target</var><span class="file">/</span><var>version</var></samp> directory.
+<var>libexec</var> defaults to <samp><var>exec-prefix</var><span class="file">/libexec</span></samp>;
+<var>exec-prefix</var> defaults to <var>prefix</var>, which
+defaults to <samp><span class="file">/usr/local</span></samp> unless overridden by the
+<samp><span class="option">--prefix=</span><var>pathname</var></samp> switch described above. <var>target</var>
+is the target system triple, such as &lsquo;<samp><span class="samp">sparc-sun-solaris2.7</span></samp>&rsquo;, and
+<var>version</var> denotes the GCC version, such as 3.0.
+
+ <li>If the target system is the same that you are building on, check
+operating system specific directories (e.g. <samp><span class="file">/usr/ccs/bin</span></samp> on
+Sun Solaris 2).
+
+ <li>Check in the <samp><span class="env">PATH</span></samp> for a tool whose name is prefixed by the
+target system triple.
+
+ <li>Check in the <samp><span class="env">PATH</span></samp> for a tool whose name is not prefixed by the
+target system triple, if the host and target system triple are
+the same (in other words, we use a host tool if it can be used for
+the target as well).
+</ul>
+
+ <p>You may want to use <samp><span class="option">--with-as</span></samp> if no assembler
+is installed in the directories listed above, or if you have multiple
+assemblers installed and want to choose one that is not found by the
+above rules.
+
+ <br><dt><code><a name="with_002dgnu_002dld"></a>--with-gnu-ld</code><dd>Same as <a href="#with-gnu-as"><samp><span class="option">--with-gnu-as</span></samp></a>
+but for the linker.
+
+ <br><dt><code>--with-ld=</code><var>pathname</var><dd>Same as <a href="#with-as"><samp><span class="option">--with-as</span></samp></a>
+but for the linker.
+
+ <br><dt><code>--with-stabs</code><dd>Specify that stabs debugging
+information should be used instead of whatever format the host normally
+uses. Normally GCC uses the same debug format as the host system.
+
+ <p>On MIPS based systems and on Alphas, you must specify whether you want
+GCC to create the normal ECOFF debugging format, or to use BSD-style
+stabs passed through the ECOFF symbol table. The normal ECOFF debug
+format cannot fully handle languages other than C. BSD stabs format can
+handle other languages, but it only works with the GNU debugger GDB.
+
+ <p>Normally, GCC uses the ECOFF debugging format by default; if you
+prefer BSD stabs, specify <samp><span class="option">--with-stabs</span></samp> when you configure GCC.
+
+ <p>No matter which default you choose when you configure GCC, the user
+can use the <samp><span class="option">-gcoff</span></samp> and <samp><span class="option">-gstabs+</span></samp> options to specify explicitly
+the debug format for a particular compilation.
+
+ <p><samp><span class="option">--with-stabs</span></samp> is meaningful on the ISC system on the 386, also, if
+<samp><span class="option">--with-gas</span></samp> is used. It selects use of stabs debugging
+information embedded in COFF output. This kind of debugging information
+supports C++ well; ordinary COFF debugging information does not.
+
+ <p><samp><span class="option">--with-stabs</span></samp> is also meaningful on 386 systems running SVR4. It
+selects use of stabs debugging information embedded in ELF output. The
+C++ compiler currently (2.6.0) does not support the DWARF debugging
+information normally used on 386 SVR4 platforms; stabs provide a
+workable alternative. This requires gas and gdb, as the normal SVR4
+tools can not generate or interpret stabs.
+
+ <br><dt><code>--enable-multiarch</code><dd>Specify whether to enable or disable multiarch support. The default is
+to check for glibc start files in a multiarch location, and enable it
+if the files are found. The auto detection is enabled for native builds,
+and for cross builds configured with <samp><span class="option">--with-sysroot</span></samp>.
+More documentation about multiarch can be found at
+<a href="http://wiki.debian.org/Multiarch">http://wiki.debian.org/Multiarch</a>.
+
+ <br><dt><code>--disable-multilib</code><dd>Specify that multiple target
+libraries to support different target variants, calling
+conventions, etc. should not be built. The default is to build a
+predefined set of them.
+
+ <p>Some targets provide finer-grained control over which multilibs are built
+(e.g., <samp><span class="option">--disable-softfloat</span></samp>):
+ <dl>
+<dt><code>arc-*-elf*</code><dd>biendian.
+
+ <br><dt><code>arm-*-*</code><dd>fpu, 26bit, underscore, interwork, biendian, nofmult.
+
+ <br><dt><code>m68*-*-*</code><dd>softfloat, m68881, m68000, m68020.
+
+ <br><dt><code>mips*-*-*</code><dd>single-float, biendian, softfloat.
+
+ <br><dt><code>powerpc*-*-*, rs6000*-*-*</code><dd>aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
+sysv, aix.
+
+ </dl>
+
+ <br><dt><code>--with-multilib-list=</code><var>list</var><dt><code>--without-multilib-list</code><dd>Specify what multilibs to build.
+Currently only implemented for sh*-*-*.
+
+ <p><var>list</var> is a comma separated list of CPU names. These must be of the
+form <code>sh*</code> or <code>m*</code> (in which case they match the compiler option
+for that processor). The list should not contain any endian options -
+these are handled by <samp><span class="option">--with-endian</span></samp>.
+
+ <p>If <var>list</var> is empty, then there will be no multilibs for extra
+processors. The multilib for the secondary endian remains enabled.
+
+ <p>As a special case, if an entry in the list starts with a <code>!</code>
+(exclamation point), then it is added to the list of excluded multilibs.
+Entries of this sort should be compatible with &lsquo;<samp><span class="samp">MULTILIB_EXCLUDES</span></samp>&rsquo;
+(once the leading <code>!</code> has been stripped).
+
+ <p>If <samp><span class="option">--with-multilib-list</span></samp> is not given, then a default set of
+multilibs is selected based on the value of <samp><span class="option">--target</span></samp>. This is
+usually the complete set of libraries, but some targets imply a more
+specialized subset.
+
+ <p>Example 1: to configure a compiler for SH4A only, but supporting both
+endians, with little endian being the default:
+ <pre class="smallexample"> --with-cpu=sh4a --with-endian=little,big --with-multilib-list=
+</pre>
+ <p>Example 2: to configure a compiler for both SH4A and SH4AL-DSP, but with
+only little endian SH4AL:
+ <pre class="smallexample"> --with-cpu=sh4a --with-endian=little,big \
+ --with-multilib-list=sh4al,!mb/m4al
+</pre>
+ <br><dt><code>--with-endian=</code><var>endians</var><dd>Specify what endians to use.
+Currently only implemented for sh*-*-*.
+
+ <p><var>endians</var> may be one of the following:
+ <dl>
+<dt><code>big</code><dd>Use big endian exclusively.
+<br><dt><code>little</code><dd>Use little endian exclusively.
+<br><dt><code>big,little</code><dd>Use big endian by default. Provide a multilib for little endian.
+<br><dt><code>little,big</code><dd>Use little endian by default. Provide a multilib for big endian.
+</dl>
+
+ <br><dt><code>--enable-threads</code><dd>Specify that the target
+supports threads. This affects the Objective-C compiler and runtime
+library, and exception handling for other languages like C++ and Java.
+On some systems, this is the default.
+
+ <p>In general, the best (and, in many cases, the only known) threading
+model available will be configured for use. Beware that on some
+systems, GCC has not been taught what threading models are generally
+available for the system. In this case, <samp><span class="option">--enable-threads</span></samp> is an
+alias for <samp><span class="option">--enable-threads=single</span></samp>.
+
+ <br><dt><code>--disable-threads</code><dd>Specify that threading support should be disabled for the system.
+This is an alias for <samp><span class="option">--enable-threads=single</span></samp>.
+
+ <br><dt><code>--enable-threads=</code><var>lib</var><dd>Specify that
+<var>lib</var> is the thread support library. This affects the Objective-C
+compiler and runtime library, and exception handling for other languages
+like C++ and Java. The possibilities for <var>lib</var> are:
+
+ <dl>
+<dt><code>aix</code><dd>AIX thread support.
+<br><dt><code>dce</code><dd>DCE thread support.
+<br><dt><code>gnat</code><dd>Ada tasking support. For non-Ada programs, this setting is equivalent
+to &lsquo;<samp><span class="samp">single</span></samp>&rsquo;. When used in conjunction with the Ada run time, it
+causes GCC to use the same thread primitives as Ada uses. This option
+is necessary when using both Ada and the back end exception handling,
+which is the default for most Ada targets.
+<br><dt><code>mach</code><dd>Generic MACH thread support, known to work on NeXTSTEP. (Please note
+that the file needed to support this configuration, <samp><span class="file">gthr-mach.h</span></samp>, is
+missing and thus this setting will cause a known bootstrap failure.)
+<br><dt><code>no</code><dd>This is an alias for &lsquo;<samp><span class="samp">single</span></samp>&rsquo;.
+<br><dt><code>posix</code><dd>Generic POSIX/Unix98 thread support.
+<br><dt><code>posix95</code><dd>Generic POSIX/Unix95 thread support.
+<br><dt><code>rtems</code><dd>RTEMS thread support.
+<br><dt><code>single</code><dd>Disable thread support, should work for all platforms.
+<br><dt><code>solaris</code><dd>Sun Solaris 2/Unix International thread support. Only use this if you
+really need to use this legacy API instead of the default, &lsquo;<samp><span class="samp">posix</span></samp>&rsquo;.
+<br><dt><code>vxworks</code><dd>VxWorks thread support.
+<br><dt><code>win32</code><dd>Microsoft Win32 API thread support.
+<br><dt><code>nks</code><dd>Novell Kernel Services thread support.
+</dl>
+
+ <br><dt><code>--enable-tls</code><dd>Specify that the target supports TLS (Thread Local Storage). Usually
+configure can correctly determine if TLS is supported. In cases where
+it guesses incorrectly, TLS can be explicitly enabled or disabled with
+<samp><span class="option">--enable-tls</span></samp> or <samp><span class="option">--disable-tls</span></samp>. This can happen if
+the assembler supports TLS but the C library does not, or if the
+assumptions made by the configure test are incorrect.
+
+ <br><dt><code>--disable-tls</code><dd>Specify that the target does not support TLS.
+This is an alias for <samp><span class="option">--enable-tls=no</span></samp>.
+
+ <br><dt><code>--with-cpu=</code><var>cpu</var><dt><code>--with-cpu-32=</code><var>cpu</var><dt><code>--with-cpu-64=</code><var>cpu</var><dd>Specify which cpu variant the compiler should generate code for by default.
+<var>cpu</var> will be used as the default value of the <samp><span class="option">-mcpu=</span></samp> switch.
+This option is only supported on some targets, including ARM, i386, M68k,
+PowerPC, and SPARC. The <samp><span class="option">--with-cpu-32</span></samp> and
+<samp><span class="option">--with-cpu-64</span></samp> options specify separate default CPUs for
+32-bit and 64-bit modes; these options are only supported for i386,
+x86-64 and PowerPC.
+
+ <br><dt><code>--with-schedule=</code><var>cpu</var><dt><code>--with-arch=</code><var>cpu</var><dt><code>--with-arch-32=</code><var>cpu</var><dt><code>--with-arch-64=</code><var>cpu</var><dt><code>--with-tune=</code><var>cpu</var><dt><code>--with-tune-32=</code><var>cpu</var><dt><code>--with-tune-64=</code><var>cpu</var><dt><code>--with-abi=</code><var>abi</var><dt><code>--with-fpu=</code><var>type</var><dt><code>--with-float=</code><var>type</var><dd>These configure options provide default values for the <samp><span class="option">-mschedule=</span></samp>,
+<samp><span class="option">-march=</span></samp>, <samp><span class="option">-mtune=</span></samp>, <samp><span class="option">-mabi=</span></samp>, and <samp><span class="option">-mfpu=</span></samp>
+options and for <samp><span class="option">-mhard-float</span></samp> or <samp><span class="option">-msoft-float</span></samp>. As with
+<samp><span class="option">--with-cpu</span></samp>, which switches will be accepted and acceptable values
+of the arguments depend on the target.
+
+ <br><dt><code>--with-mode=</code><var>mode</var><dd>Specify if the compiler should default to <samp><span class="option">-marm</span></samp> or <samp><span class="option">-mthumb</span></samp>.
+This option is only supported on ARM targets.
+
+ <br><dt><code>--with-fpmath=</code><var>isa</var><dd>This options sets <samp><span class="option">-mfpmath=sse</span></samp> by default and specifies the default
+ISA for floating-point arithmetics. You can select either &lsquo;<samp><span class="samp">sse</span></samp>&rsquo; which
+enables <samp><span class="option">-msse2</span></samp> or &lsquo;<samp><span class="samp">avx</span></samp>&rsquo; which enables <samp><span class="option">-mavx</span></samp> by default.
+This option is only supported on i386 and x86-64 targets.
+
+ <br><dt><code>--with-divide=</code><var>type</var><dd>Specify how the compiler should generate code for checking for
+division by zero. This option is only supported on the MIPS target.
+The possibilities for <var>type</var> are:
+ <dl>
+<dt><code>traps</code><dd>Division by zero checks use conditional traps (this is the default on
+systems that support conditional traps).
+<br><dt><code>breaks</code><dd>Division by zero checks use the break instruction.
+</dl>
+
+ <!-- If you make -with-llsc the default for additional targets, -->
+ <!-- update the -with-llsc description in the MIPS section below. -->
+ <br><dt><code>--with-llsc</code><dd>On MIPS targets, make <samp><span class="option">-mllsc</span></samp> the default when no
+<samp><span class="option">-mno-llsc</span></samp> option is passed. This is the default for
+Linux-based targets, as the kernel will emulate them if the ISA does
+not provide them.
+
+ <br><dt><code>--without-llsc</code><dd>On MIPS targets, make <samp><span class="option">-mno-llsc</span></samp> the default when no
+<samp><span class="option">-mllsc</span></samp> option is passed.
+
+ <br><dt><code>--with-synci</code><dd>On MIPS targets, make <samp><span class="option">-msynci</span></samp> the default when no
+<samp><span class="option">-mno-synci</span></samp> option is passed.
+
+ <br><dt><code>--without-synci</code><dd>On MIPS targets, make <samp><span class="option">-mno-synci</span></samp> the default when no
+<samp><span class="option">-msynci</span></samp> option is passed. This is the default.
+
+ <br><dt><code>--with-mips-plt</code><dd>On MIPS targets, make use of copy relocations and PLTs.
+These features are extensions to the traditional
+SVR4-based MIPS ABIs and require support from GNU binutils
+and the runtime C library.
+
+ <br><dt><code>--enable-__cxa_atexit</code><dd>Define if you want to use __cxa_atexit, rather than atexit, to
+register C++ destructors for local statics and global objects.
+This is essential for fully standards-compliant handling of
+destructors, but requires __cxa_atexit in libc. This option is currently
+only available on systems with GNU libc. When enabled, this will cause
+<samp><span class="option">-fuse-cxa-atexit</span></samp> to be passed by default.
+
+ <br><dt><code>--enable-indirect-function</code><dd>Define if you want to enable the <code>ifunc</code> attribute. This option is
+currently only available on systems with GNU libc on certain targets.
+
+ <br><dt><code>--enable-target-optspace</code><dd>Specify that target
+libraries should be optimized for code space instead of code speed.
+This is the default for the m32r platform.
+
+ <br><dt><code>--with-cpp-install-dir=</code><var>dirname</var><dd>Specify that the user visible <samp><span class="command">cpp</span></samp> program should be installed
+in <samp><var>prefix</var><span class="file">/</span><var>dirname</var><span class="file">/cpp</span></samp>, in addition to <var>bindir</var>.
+
+ <br><dt><code>--enable-comdat</code><dd>Enable COMDAT group support. This is primarily used to override the
+automatically detected value.
+
+ <br><dt><code>--enable-initfini-array</code><dd>Force the use of sections <code>.init_array</code> and <code>.fini_array</code>
+(instead of <code>.init</code> and <code>.fini</code>) for constructors and
+destructors. Option <samp><span class="option">--disable-initfini-array</span></samp> has the
+opposite effect. If neither option is specified, the configure script
+will try to guess whether the <code>.init_array</code> and
+<code>.fini_array</code> sections are supported and, if they are, use them.
+
+ <br><dt><code>--enable-build-with-cxx</code><dd>Build GCC using a C++ compiler rather than a C compiler. This is an
+experimental option which may become the default in a later release.
+
+ <br><dt><code>--enable-maintainer-mode</code><dd>The build rules that regenerate the Autoconf and Automake output files as
+well as the GCC master message catalog <samp><span class="file">gcc.pot</span></samp> are normally
+disabled. This is because it can only be rebuilt if the complete source
+tree is present. If you have changed the sources and want to rebuild the
+catalog, configuring with <samp><span class="option">--enable-maintainer-mode</span></samp> will enable
+this. Note that you need a recent version of the <code>gettext</code> tools
+to do so.
+
+ <br><dt><code>--disable-bootstrap</code><dd>For a native build, the default configuration is to perform
+a 3-stage bootstrap of the compiler when &lsquo;<samp><span class="samp">make</span></samp>&rsquo; is invoked,
+testing that GCC can compile itself correctly. If you want to disable
+this process, you can configure with <samp><span class="option">--disable-bootstrap</span></samp>.
+
+ <br><dt><code>--enable-bootstrap</code><dd>In special cases, you may want to perform a 3-stage build
+even if the target and host triplets are different.
+This is possible when the host can run code compiled for
+the target (e.g. host is i686-linux, target is i486-linux).
+Starting from GCC 4.2, to do this you have to configure explicitly
+with <samp><span class="option">--enable-bootstrap</span></samp>.
+
+ <br><dt><code>--enable-generated-files-in-srcdir</code><dd>Neither the .c and .h files that are generated from Bison and flex nor the
+info manuals and man pages that are built from the .texi files are present
+in the SVN development tree. When building GCC from that development tree,
+or from one of our snapshots, those generated files are placed in your
+build directory, which allows for the source to be in a readonly
+directory.
+
+ <p>If you configure with <samp><span class="option">--enable-generated-files-in-srcdir</span></samp> then those
+generated files will go into the source directory. This is mainly intended
+for generating release or prerelease tarballs of the GCC sources, since it
+is not a requirement that the users of source releases to have flex, Bison,
+or makeinfo.
+
+ <br><dt><code>--enable-version-specific-runtime-libs</code><dd>Specify
+that runtime libraries should be installed in the compiler specific
+subdirectory (<samp><var>libdir</var><span class="file">/gcc</span></samp>) rather than the usual places. In
+addition, &lsquo;<samp><span class="samp">libstdc++</span></samp>&rsquo;'s include files will be installed into
+<samp><var>libdir</var></samp> unless you overruled it by using
+<samp><span class="option">--with-gxx-include-dir=</span><var>dirname</var></samp>. Using this option is
+particularly useful if you intend to use several versions of GCC in
+parallel. This is currently supported by &lsquo;<samp><span class="samp">libgfortran</span></samp>&rsquo;,
+&lsquo;<samp><span class="samp">libjava</span></samp>&rsquo;, &lsquo;<samp><span class="samp">libmudflap</span></samp>&rsquo;, &lsquo;<samp><span class="samp">libstdc++</span></samp>&rsquo;, and &lsquo;<samp><span class="samp">libobjc</span></samp>&rsquo;.
+
+ <br><dt><code>--enable-languages=</code><var>lang1</var><code>,</code><var>lang2</var><code>,...</code><dd>Specify that only a particular subset of compilers and
+their runtime libraries should be built. For a list of valid values for
+<var>langN</var> you can issue the following command in the
+<samp><span class="file">gcc</span></samp> directory of your GCC source tree:<br>
+ <pre class="smallexample"> grep language= */config-lang.in
+</pre>
+ <p>Currently, you can use any of the following:
+<code>all</code>, <code>ada</code>, <code>c</code>, <code>c++</code>, <code>fortran</code>,
+<code>go</code>, <code>java</code>, <code>objc</code>, <code>obj-c++</code>.
+Building the Ada compiler has special requirements, see below.
+If you do not pass this flag, or specify the option <code>all</code>, then all
+default languages available in the <samp><span class="file">gcc</span></samp> sub-tree will be configured.
+Ada, Go and Objective-C++ are not default languages; the rest are.
+
+ <br><dt><code>--enable-stage1-languages=</code><var>lang1</var><code>,</code><var>lang2</var><code>,...</code><dd>Specify that a particular subset of compilers and their runtime
+libraries should be built with the system C compiler during stage 1 of
+the bootstrap process, rather than only in later stages with the
+bootstrapped C compiler. The list of valid values is the same as for
+<samp><span class="option">--enable-languages</span></samp>, and the option <code>all</code> will select all
+of the languages enabled by <samp><span class="option">--enable-languages</span></samp>. This option is
+primarily useful for GCC development; for instance, when a development
+version of the compiler cannot bootstrap due to compiler bugs, or when
+one is debugging front ends other than the C front end. When this
+option is used, one can then build the target libraries for the
+specified languages with the stage-1 compiler by using <samp><span class="command">make
+stage1-bubble all-target</span></samp>, or run the testsuite on the stage-1 compiler
+for the specified languages using <samp><span class="command">make stage1-start check-gcc</span></samp>.
+
+ <br><dt><code>--disable-libada</code><dd>Specify that the run-time libraries and tools used by GNAT should not
+be built. This can be useful for debugging, or for compatibility with
+previous Ada build procedures, when it was required to explicitly
+do a &lsquo;<samp><span class="samp">make -C gcc gnatlib_and_tools</span></samp>&rsquo;.
+
+ <br><dt><code>--disable-libssp</code><dd>Specify that the run-time libraries for stack smashing protection
+should not be built.
+
+ <br><dt><code>--disable-libquadmath</code><dd>Specify that the GCC quad-precision math library should not be built.
+On some systems, the library is required to be linkable when building
+the Fortran front end, unless <samp><span class="option">--disable-libquadmath-support</span></samp>
+is used.
+
+ <br><dt><code>--disable-libquadmath-support</code><dd>Specify that the Fortran front end and <code>libgfortran</code> do not add
+support for <code>libquadmath</code> on systems supporting it.
+
+ <br><dt><code>--disable-libgomp</code><dd>Specify that the run-time libraries used by GOMP should not be built.
+
+ <br><dt><code>--with-dwarf2</code><dd>Specify that the compiler should
+use DWARF 2 debugging information as the default.
+
+ <br><dt><code>--enable-targets=all</code><dt><code>--enable-targets=</code><var>target_list</var><dd>Some GCC targets, e.g. powerpc64-linux, build bi-arch compilers.
+These are compilers that are able to generate either 64-bit or 32-bit
+code. Typically, the corresponding 32-bit target, e.g.
+powerpc-linux for powerpc64-linux, only generates 32-bit code. This
+option enables the 32-bit target to be a bi-arch compiler, which is
+useful when you want a bi-arch compiler that defaults to 32-bit, and
+you are building a bi-arch or multi-arch binutils in a combined tree.
+On mips-linux, this will build a tri-arch compiler (ABI o32/n32/64),
+defaulted to o32.
+Currently, this option only affects sparc-linux, powerpc-linux, x86-linux
+and mips-linux.
+
+ <br><dt><code>--enable-secureplt</code><dd>This option enables <samp><span class="option">-msecure-plt</span></samp> by default for powerpc-linux.
+See &ldquo;RS/6000 and PowerPC Options&rdquo; in the main manual
+
+ <br><dt><code>--enable-cld</code><dd>This option enables <samp><span class="option">-mcld</span></samp> by default for 32-bit x86 targets.
+See &ldquo;i386 and x86-64 Options&rdquo; in the main manual
+
+ <br><dt><code>--enable-win32-registry</code><dt><code>--enable-win32-registry=</code><var>key</var><dt><code>--disable-win32-registry</code><dd>The <samp><span class="option">--enable-win32-registry</span></samp> option enables Microsoft Windows-hosted GCC
+to look up installations paths in the registry using the following key:
+
+ <pre class="smallexample"> <code>HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\</code><var>key</var>
+</pre>
+ <p><var>key</var> defaults to GCC version number, and can be overridden by the
+<samp><span class="option">--enable-win32-registry=</span><var>key</var></samp> option. Vendors and distributors
+who use custom installers are encouraged to provide a different key,
+perhaps one comprised of vendor name and GCC version number, to
+avoid conflict with existing installations. This feature is enabled
+by default, and can be disabled by <samp><span class="option">--disable-win32-registry</span></samp>
+option. This option has no effect on the other hosts.
+
+ <br><dt><code>--nfp</code><dd>Specify that the machine does not have a floating point unit. This
+option only applies to &lsquo;<samp><span class="samp">m68k-sun-sunos</span><var>n</var></samp>&rsquo;. On any other
+system, <samp><span class="option">--nfp</span></samp> has no effect.
+
+ <br><dt><code>--enable-werror</code><dt><code>--disable-werror</code><dt><code>--enable-werror=yes</code><dt><code>--enable-werror=no</code><dd>When you specify this option, it controls whether certain files in the
+compiler are built with <samp><span class="option">-Werror</span></samp> in bootstrap stage2 and later.
+If you don't specify it, <samp><span class="option">-Werror</span></samp> is turned on for the main
+development trunk. However it defaults to off for release branches and
+final releases. The specific files which get <samp><span class="option">-Werror</span></samp> are
+controlled by the Makefiles.
+
+ <br><dt><code>--enable-checking</code><dt><code>--enable-checking=</code><var>list</var><dd>When you specify this option, the compiler is built to perform internal
+consistency checks of the requested complexity. This does not change the
+generated code, but adds error checking within the compiler. This will
+slow down the compiler and may only work properly if you are building
+the compiler with GCC. This is &lsquo;<samp><span class="samp">yes</span></samp>&rsquo; by default when building
+from SVN or snapshots, but &lsquo;<samp><span class="samp">release</span></samp>&rsquo; for releases. The default
+for building the stage1 compiler is &lsquo;<samp><span class="samp">yes</span></samp>&rsquo;. More control
+over the checks may be had by specifying <var>list</var>. The categories of
+checks available are &lsquo;<samp><span class="samp">yes</span></samp>&rsquo; (most common checks
+&lsquo;<samp><span class="samp">assert,misc,tree,gc,rtlflag,runtime</span></samp>&rsquo;), &lsquo;<samp><span class="samp">no</span></samp>&rsquo; (no checks at
+all), &lsquo;<samp><span class="samp">all</span></samp>&rsquo; (all but &lsquo;<samp><span class="samp">valgrind</span></samp>&rsquo;), &lsquo;<samp><span class="samp">release</span></samp>&rsquo; (cheapest
+checks &lsquo;<samp><span class="samp">assert,runtime</span></samp>&rsquo;) or &lsquo;<samp><span class="samp">none</span></samp>&rsquo; (same as &lsquo;<samp><span class="samp">no</span></samp>&rsquo;).
+Individual checks can be enabled with these flags &lsquo;<samp><span class="samp">assert</span></samp>&rsquo;,
+&lsquo;<samp><span class="samp">df</span></samp>&rsquo;, &lsquo;<samp><span class="samp">fold</span></samp>&rsquo;, &lsquo;<samp><span class="samp">gc</span></samp>&rsquo;, &lsquo;<samp><span class="samp">gcac</span></samp>&rsquo; &lsquo;<samp><span class="samp">misc</span></samp>&rsquo;, &lsquo;<samp><span class="samp">rtl</span></samp>&rsquo;,
+&lsquo;<samp><span class="samp">rtlflag</span></samp>&rsquo;, &lsquo;<samp><span class="samp">runtime</span></samp>&rsquo;, &lsquo;<samp><span class="samp">tree</span></samp>&rsquo;, and &lsquo;<samp><span class="samp">valgrind</span></samp>&rsquo;.
+
+ <p>The &lsquo;<samp><span class="samp">valgrind</span></samp>&rsquo; check requires the external <samp><span class="command">valgrind</span></samp>
+simulator, available from <a href="http://valgrind.org/">http://valgrind.org/</a>. The
+&lsquo;<samp><span class="samp">df</span></samp>&rsquo;, &lsquo;<samp><span class="samp">rtl</span></samp>&rsquo;, &lsquo;<samp><span class="samp">gcac</span></samp>&rsquo; and &lsquo;<samp><span class="samp">valgrind</span></samp>&rsquo; checks are very expensive.
+To disable all checking, &lsquo;<samp><span class="samp">--disable-checking</span></samp>&rsquo; or
+&lsquo;<samp><span class="samp">--enable-checking=none</span></samp>&rsquo; must be explicitly requested. Disabling
+assertions will make the compiler and runtime slightly faster but
+increase the risk of undetected internal errors causing wrong code to be
+generated.
+
+ <br><dt><code>--disable-stage1-checking</code><dt><code>--enable-stage1-checking</code><dt><code>--enable-stage1-checking=</code><var>list</var><dd>If no <samp><span class="option">--enable-checking</span></samp> option is specified the stage1
+compiler will be built with &lsquo;<samp><span class="samp">yes</span></samp>&rsquo; checking enabled, otherwise
+the stage1 checking flags are the same as specified by
+<samp><span class="option">--enable-checking</span></samp>. To build the stage1 compiler with
+different checking options use <samp><span class="option">--enable-stage1-checking</span></samp>.
+The list of checking options is the same as for <samp><span class="option">--enable-checking</span></samp>.
+If your system is too slow or too small to bootstrap a released compiler
+with checking for stage1 enabled, you can use &lsquo;<samp><span class="samp">--disable-stage1-checking</span></samp>&rsquo;
+to disable checking for the stage1 compiler.
+
+ <br><dt><code>--enable-coverage</code><dt><code>--enable-coverage=</code><var>level</var><dd>With this option, the compiler is built to collect self coverage
+information, every time it is run. This is for internal development
+purposes, and only works when the compiler is being built with gcc. The
+<var>level</var> argument controls whether the compiler is built optimized or
+not, values are &lsquo;<samp><span class="samp">opt</span></samp>&rsquo; and &lsquo;<samp><span class="samp">noopt</span></samp>&rsquo;. For coverage analysis you
+want to disable optimization, for performance analysis you want to
+enable optimization. When coverage is enabled, the default level is
+without optimization.
+
+ <br><dt><code>--enable-gather-detailed-mem-stats</code><dd>When this option is specified more detailed information on memory
+allocation is gathered. This information is printed when using
+<samp><span class="option">-fmem-report</span></samp>.
+
+ <br><dt><code>--with-gc</code><dt><code>--with-gc=</code><var>choice</var><dd>With this option you can specify the garbage collector implementation
+used during the compilation process. <var>choice</var> can be one of
+&lsquo;<samp><span class="samp">page</span></samp>&rsquo; and &lsquo;<samp><span class="samp">zone</span></samp>&rsquo;, where &lsquo;<samp><span class="samp">page</span></samp>&rsquo; is the default.
+
+ <br><dt><code>--enable-nls</code><dt><code>--disable-nls</code><dd>The <samp><span class="option">--enable-nls</span></samp> option enables Native Language Support (NLS),
+which lets GCC output diagnostics in languages other than American
+English. Native Language Support is enabled by default if not doing a
+canadian cross build. The <samp><span class="option">--disable-nls</span></samp> option disables NLS.
+
+ <br><dt><code>--with-included-gettext</code><dd>If NLS is enabled, the <samp><span class="option">--with-included-gettext</span></samp> option causes the build
+procedure to prefer its copy of GNU <samp><span class="command">gettext</span></samp>.
+
+ <br><dt><code>--with-catgets</code><dd>If NLS is enabled, and if the host lacks <code>gettext</code> but has the
+inferior <code>catgets</code> interface, the GCC build procedure normally
+ignores <code>catgets</code> and instead uses GCC's copy of the GNU
+<code>gettext</code> library. The <samp><span class="option">--with-catgets</span></samp> option causes the
+build procedure to use the host's <code>catgets</code> in this situation.
+
+ <br><dt><code>--with-libiconv-prefix=</code><var>dir</var><dd>Search for libiconv header files in <samp><var>dir</var><span class="file">/include</span></samp> and
+libiconv library files in <samp><var>dir</var><span class="file">/lib</span></samp>.
+
+ <br><dt><code>--enable-obsolete</code><dd>Enable configuration for an obsoleted system. If you attempt to
+configure GCC for a system (build, host, or target) which has been
+obsoleted, and you do not specify this flag, configure will halt with an
+error message.
+
+ <p>All support for systems which have been obsoleted in one release of GCC
+is removed entirely in the next major release, unless someone steps
+forward to maintain the port.
+
+ <br><dt><code>--enable-decimal-float</code><dt><code>--enable-decimal-float=yes</code><dt><code>--enable-decimal-float=no</code><dt><code>--enable-decimal-float=bid</code><dt><code>--enable-decimal-float=dpd</code><dt><code>--disable-decimal-float</code><dd>Enable (or disable) support for the C decimal floating point extension
+that is in the IEEE 754-2008 standard. This is enabled by default only
+on PowerPC, i386, and x86_64 GNU/Linux systems. Other systems may also
+support it, but require the user to specifically enable it. You can
+optionally control which decimal floating point format is used (either
+&lsquo;<samp><span class="samp">bid</span></samp>&rsquo; or &lsquo;<samp><span class="samp">dpd</span></samp>&rsquo;). The &lsquo;<samp><span class="samp">bid</span></samp>&rsquo; (binary integer decimal)
+format is default on i386 and x86_64 systems, and the &lsquo;<samp><span class="samp">dpd</span></samp>&rsquo;
+(densely packed decimal) format is default on PowerPC systems.
+
+ <br><dt><code>--enable-fixed-point</code><dt><code>--disable-fixed-point</code><dd>Enable (or disable) support for C fixed-point arithmetic.
+This option is enabled by default for some targets (such as MIPS) which
+have hardware-support for fixed-point operations. On other targets, you
+may enable this option manually.
+
+ <br><dt><code>--with-long-double-128</code><dd>Specify if <code>long double</code> type should be 128-bit by default on selected
+GNU/Linux architectures. If using <code>--without-long-double-128</code>,
+<code>long double</code> will be by default 64-bit, the same as <code>double</code> type.
+When neither of these configure options are used, the default will be
+128-bit <code>long double</code> when built against GNU C Library 2.4 and later,
+64-bit <code>long double</code> otherwise.
+
+ <br><dt><code>--with-gmp=</code><var>pathname</var><dt><code>--with-gmp-include=</code><var>pathname</var><dt><code>--with-gmp-lib=</code><var>pathname</var><dt><code>--with-mpfr=</code><var>pathname</var><dt><code>--with-mpfr-include=</code><var>pathname</var><dt><code>--with-mpfr-lib=</code><var>pathname</var><dt><code>--with-mpc=</code><var>pathname</var><dt><code>--with-mpc-include=</code><var>pathname</var><dt><code>--with-mpc-lib=</code><var>pathname</var><dd>If you do not have GMP (the GNU Multiple Precision library), the MPFR
+library and/or the MPC library installed in a standard location and
+you want to build GCC, you can explicitly specify the directory where
+they are installed (&lsquo;<samp><span class="samp">--with-gmp=</span><var>gmpinstalldir</var></samp>&rsquo;,
+&lsquo;<samp><span class="samp">--with-mpfr=</span><var>mpfrinstalldir</var></samp>&rsquo;,
+&lsquo;<samp><span class="samp">--with-mpc=</span><var>mpcinstalldir</var></samp>&rsquo;). The
+<samp><span class="option">--with-gmp=</span><var>gmpinstalldir</var></samp> option is shorthand for
+<samp><span class="option">--with-gmp-lib=</span><var>gmpinstalldir</var><span class="option">/lib</span></samp> and
+<samp><span class="option">--with-gmp-include=</span><var>gmpinstalldir</var><span class="option">/include</span></samp>. Likewise the
+<samp><span class="option">--with-mpfr=</span><var>mpfrinstalldir</var></samp> option is shorthand for
+<samp><span class="option">--with-mpfr-lib=</span><var>mpfrinstalldir</var><span class="option">/lib</span></samp> and
+<samp><span class="option">--with-mpfr-include=</span><var>mpfrinstalldir</var><span class="option">/include</span></samp>, also the
+<samp><span class="option">--with-mpc=</span><var>mpcinstalldir</var></samp> option is shorthand for
+<samp><span class="option">--with-mpc-lib=</span><var>mpcinstalldir</var><span class="option">/lib</span></samp> and
+<samp><span class="option">--with-mpc-include=</span><var>mpcinstalldir</var><span class="option">/include</span></samp>. If these
+shorthand assumptions are not correct, you can use the explicit
+include and lib options directly. You might also need to ensure the
+shared libraries can be found by the dynamic linker when building and
+using GCC, for example by setting the runtime shared library path
+variable (<samp><span class="env">LD_LIBRARY_PATH</span></samp> on GNU/Linux and Solaris systems).
+
+ <p>These flags are applicable to the host platform only. When building
+a cross compiler, they will not be used to configure target libraries.
+
+ <br><dt><code>--with-ppl=</code><var>pathname</var><dt><code>--with-ppl-include=</code><var>pathname</var><dt><code>--with-ppl-lib=</code><var>pathname</var><dt><code>--with-cloog=</code><var>pathname</var><dt><code>--with-cloog-include=</code><var>pathname</var><dt><code>--with-cloog-lib=</code><var>pathname</var><dd>If you do not have PPL (the Parma Polyhedra Library) and the CLooG
+libraries installed in a standard location and you want to build GCC,
+you can explicitly specify the directory where they are installed
+(&lsquo;<samp><span class="samp">--with-ppl=</span><var>pplinstalldir</var></samp>&rsquo;,
+&lsquo;<samp><span class="samp">--with-cloog=</span><var>clooginstalldir</var></samp>&rsquo;). The
+<samp><span class="option">--with-ppl=</span><var>pplinstalldir</var></samp> option is shorthand for
+<samp><span class="option">--with-ppl-lib=</span><var>pplinstalldir</var><span class="option">/lib</span></samp> and
+<samp><span class="option">--with-ppl-include=</span><var>pplinstalldir</var><span class="option">/include</span></samp>. Likewise the
+<samp><span class="option">--with-cloog=</span><var>clooginstalldir</var></samp> option is shorthand for
+<samp><span class="option">--with-cloog-lib=</span><var>clooginstalldir</var><span class="option">/lib</span></samp> and
+<samp><span class="option">--with-cloog-include=</span><var>clooginstalldir</var><span class="option">/include</span></samp>. If these
+shorthand assumptions are not correct, you can use the explicit
+include and lib options directly.
+
+ <p>These flags are applicable to the host platform only. When building
+a cross compiler, they will not be used to configure target libraries.
+
+ <br><dt><code>--with-host-libstdcxx=</code><var>linker-args</var><dd>If you are linking with a static copy of PPL, you can use this option
+to specify how the linker should find the standard C++ library used
+internally by PPL. Typical values of <var>linker-args</var> might be
+&lsquo;<samp><span class="samp">-lstdc++</span></samp>&rsquo; or &lsquo;<samp><span class="samp">-Wl,-Bstatic,-lstdc++,-Bdynamic -lm</span></samp>&rsquo;. If you are
+linking with a shared copy of PPL, you probably do not need this
+option; shared library dependencies will cause the linker to search
+for the standard C++ library automatically.
+
+ <br><dt><code>--with-stage1-ldflags=</code><var>flags</var><dd>This option may be used to set linker flags to be used when linking
+stage 1 of GCC. These are also used when linking GCC if configured with
+<samp><span class="option">--disable-bootstrap</span></samp>. By default no special flags are used.
+
+ <br><dt><code>--with-stage1-libs=</code><var>libs</var><dd>This option may be used to set libraries to be used when linking stage 1
+of GCC. These are also used when linking GCC if configured with
+<samp><span class="option">--disable-bootstrap</span></samp>. The default is the argument to
+<samp><span class="option">--with-host-libstdcxx</span></samp>, if specified.
+
+ <br><dt><code>--with-boot-ldflags=</code><var>flags</var><dd>This option may be used to set linker flags to be used when linking
+stage 2 and later when bootstrapping GCC. If neither &ndash;with-boot-libs
+nor &ndash;with-host-libstdcxx is set to a value, then the default is
+&lsquo;<samp><span class="samp">-static-libstdc++ -static-libgcc</span></samp>&rsquo;.
+
+ <br><dt><code>--with-boot-libs=</code><var>libs</var><dd>This option may be used to set libraries to be used when linking stage 2
+and later when bootstrapping GCC. The default is the argument to
+<samp><span class="option">--with-host-libstdcxx</span></samp>, if specified.
+
+ <br><dt><code>--with-debug-prefix-map=</code><var>map</var><dd>Convert source directory names using <samp><span class="option">-fdebug-prefix-map</span></samp> when
+building runtime libraries. &lsquo;<samp><var>map</var></samp>&rsquo; is a space-separated
+list of maps of the form &lsquo;<samp><var>old</var><span class="samp">=</span><var>new</var></samp>&rsquo;.
+
+ <br><dt><code>--enable-linker-build-id</code><dd>Tells GCC to pass <samp><span class="option">--build-id</span></samp> option to the linker for all final
+links (links performed without the <samp><span class="option">-r</span></samp> or <samp><span class="option">--relocatable</span></samp>
+option), if the linker supports it. If you specify
+<samp><span class="option">--enable-linker-build-id</span></samp>, but your linker does not
+support <samp><span class="option">--build-id</span></samp> option, a warning is issued and the
+<samp><span class="option">--enable-linker-build-id</span></samp> option is ignored. The default is off.
+
+ <br><dt><code>--enable-gnu-unique-object</code><dt><code>--disable-gnu-unique-object</code><dd>Tells GCC to use the gnu_unique_object relocation for C++ template
+static data members and inline function local statics. Enabled by
+default for a native toolchain with an assembler that accepts it and
+GLIBC 2.11 or above, otherwise disabled.
+
+ <br><dt><code>--enable-lto</code><dt><code>--disable-lto</code><dd>Enable support for link-time optimization (LTO). This is enabled by
+default, and may be disabled using <samp><span class="option">--disable-lto</span></samp>.
+
+ <br><dt><code>--with-plugin-ld=</code><var>pathname</var><dd>Enable an alternate linker to be used at link-time optimization (LTO)
+link time when <samp><span class="option">-fuse-linker-plugin</span></samp> is enabled.
+This linker should have plugin support such as gold starting with
+version 2.20 or GNU ld starting with version 2.21.
+See <samp><span class="option">-fuse-linker-plugin</span></samp> for details.
+</dl>
+
+<h4 class="subheading"><a name="TOC3"></a>Cross-Compiler-Specific Options</h4>
+
+<p>The following options only apply to building cross compilers.
+
+ <dl>
+<dt><code>--with-sysroot</code><dt><code>--with-sysroot=</code><var>dir</var><dd>Tells GCC to consider <var>dir</var> as the root of a tree that contains
+(a subset of) the root filesystem of the target operating system.
+Target system headers, libraries and run-time object files will be
+searched in there. More specifically, this acts as if
+<samp><span class="option">--sysroot=</span><var>dir</var></samp> was added to the default options of the built
+compiler. The specified directory is not copied into the
+install tree, unlike the options <samp><span class="option">--with-headers</span></samp> and
+<samp><span class="option">--with-libs</span></samp> that this option obsoletes. The default value,
+in case <samp><span class="option">--with-sysroot</span></samp> is not given an argument, is
+<samp><span class="option">${gcc_tooldir}/sys-root</span></samp>. If the specified directory is a
+subdirectory of <samp><span class="option">${exec_prefix}</span></samp>, then it will be found relative to
+the GCC binaries if the installation tree is moved.
+
+ <p>This option affects the system root for the compiler used to build
+target libraries (which runs on the build system) and the compiler newly
+installed with <code>make install</code>; it does not affect the compiler which is
+used to build GCC itself.
+
+ <br><dt><code>--with-build-sysroot</code><dt><code>--with-build-sysroot=</code><var>dir</var><dd>Tells GCC to consider <var>dir</var> as the system root (see
+<samp><span class="option">--with-sysroot</span></samp>) while building target libraries, instead of
+the directory specified with <samp><span class="option">--with-sysroot</span></samp>. This option is
+only useful when you are already using <samp><span class="option">--with-sysroot</span></samp>. You
+can use <samp><span class="option">--with-build-sysroot</span></samp> when you are configuring with
+<samp><span class="option">--prefix</span></samp> set to a directory that is different from the one in
+which you are installing GCC and your target libraries.
+
+ <p>This option affects the system root for the compiler used to build
+target libraries (which runs on the build system); it does not affect
+the compiler which is used to build GCC itself.
+
+ <br><dt><code>--with-headers</code><dt><code>--with-headers=</code><var>dir</var><dd>Deprecated in favor of <samp><span class="option">--with-sysroot</span></samp>.
+Specifies that target headers are available when building a cross compiler.
+The <var>dir</var> argument specifies a directory which has the target include
+files. These include files will be copied into the <samp><span class="file">gcc</span></samp> install
+directory. <em>This option with the </em><var>dir</var><em> argument is required</em> when
+building a cross compiler, if <samp><var>prefix</var><span class="file">/</span><var>target</var><span class="file">/sys-include</span></samp>
+doesn't pre-exist. If <samp><var>prefix</var><span class="file">/</span><var>target</var><span class="file">/sys-include</span></samp> does
+pre-exist, the <var>dir</var> argument may be omitted. <samp><span class="command">fixincludes</span></samp>
+will be run on these files to make them compatible with GCC.
+
+ <br><dt><code>--without-headers</code><dd>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.
+
+ <br><dt><code>--with-libs</code><dt><code>--with-libs="</code><var>dir1</var> <var>dir2</var><code> ... </code><var>dirN</var><code>"</code><dd>Deprecated in favor of <samp><span class="option">--with-sysroot</span></samp>.
+Specifies a list of directories which contain the target runtime
+libraries. These libraries will be copied into the <samp><span class="file">gcc</span></samp> install
+directory. If the directory list is omitted, this option has no
+effect.
+
+ <br><dt><code>--with-newlib</code><dd>Specifies that &lsquo;<samp><span class="samp">newlib</span></samp>&rsquo; is
+being used as the target C library. This causes <code>__eprintf</code> to be
+omitted from <samp><span class="file">libgcc.a</span></samp> on the assumption that it will be provided by
+&lsquo;<samp><span class="samp">newlib</span></samp>&rsquo;.
+
+ <br><dt><code>--with-build-time-tools=</code><var>dir</var><dd>Specifies where to find the set of target tools (assembler, linker, etc.)
+that will be used while building GCC itself. This option can be useful
+if the directory layouts are different between the system you are building
+GCC on, and the system where you will deploy it.
+
+ <p>For example, on an &lsquo;<samp><span class="samp">ia64-hp-hpux</span></samp>&rsquo; system, you may have the GNU
+assembler and linker in <samp><span class="file">/usr/bin</span></samp>, and the native tools in a
+different path, and build a toolchain that expects to find the
+native tools in <samp><span class="file">/usr/bin</span></samp>.
+
+ <p>When you use this option, you should ensure that <var>dir</var> includes
+<samp><span class="command">ar</span></samp>, <samp><span class="command">as</span></samp>, <samp><span class="command">ld</span></samp>, <samp><span class="command">nm</span></samp>,
+<samp><span class="command">ranlib</span></samp> and <samp><span class="command">strip</span></samp> if necessary, and possibly
+<samp><span class="command">objdump</span></samp>. Otherwise, GCC may use an inconsistent set of
+tools.
+</dl>
+
+<h4 class="subheading"><a name="TOC4"></a>Java-Specific Options</h4>
+
+<p>The following option applies to the build of the Java front end.
+
+ <dl>
+<dt><code>--disable-libgcj</code><dd>Specify that the run-time libraries
+used by GCJ should not be built. This is useful in case you intend
+to use GCJ with some other run-time, or you're going to install it
+separately, or it just happens not to build on your particular
+machine. In general, if the Java front end is enabled, the GCJ
+libraries will be enabled too, unless they're known to not work on
+the target platform. If GCJ is enabled but &lsquo;<samp><span class="samp">libgcj</span></samp>&rsquo; isn't built, you
+may need to port it; in this case, before modifying the top-level
+<samp><span class="file">configure.in</span></samp> so that &lsquo;<samp><span class="samp">libgcj</span></samp>&rsquo; is enabled by default on this platform,
+you may use <samp><span class="option">--enable-libgcj</span></samp> to override the default.
+
+ </dl>
+
+ <p>The following options apply to building &lsquo;<samp><span class="samp">libgcj</span></samp>&rsquo;.
+
+<h5 class="subsubheading"><a name="TOC5"></a>General Options</h5>
+
+ <dl>
+<dt><code>--enable-java-maintainer-mode</code><dd>By default the &lsquo;<samp><span class="samp">libjava</span></samp>&rsquo; build will not attempt to compile the
+<samp><span class="file">.java</span></samp> source files to <samp><span class="file">.class</span></samp>. Instead, it will use the
+<samp><span class="file">.class</span></samp> files from the source tree. If you use this option you
+must have executables named <samp><span class="command">ecj1</span></samp> and <samp><span class="command">gjavah</span></samp> in your path
+for use by the build. You must use this option if you intend to
+modify any <samp><span class="file">.java</span></samp> files in <samp><span class="file">libjava</span></samp>.
+
+ <br><dt><code>--with-java-home=</code><var>dirname</var><dd>This &lsquo;<samp><span class="samp">libjava</span></samp>&rsquo; option overrides the default value of the
+&lsquo;<samp><span class="samp">java.home</span></samp>&rsquo; system property. It is also used to set
+&lsquo;<samp><span class="samp">sun.boot.class.path</span></samp>&rsquo; to <samp><var>dirname</var><span class="file">/lib/rt.jar</span></samp>. By
+default &lsquo;<samp><span class="samp">java.home</span></samp>&rsquo; is set to <samp><var>prefix</var></samp> and
+&lsquo;<samp><span class="samp">sun.boot.class.path</span></samp>&rsquo; to
+<samp><var>datadir</var><span class="file">/java/libgcj-</span><var>version</var><span class="file">.jar</span></samp>.
+
+ <br><dt><code>--with-ecj-jar=</code><var>filename</var><dd>This option can be used to specify the location of an external jar
+file containing the Eclipse Java compiler. A specially modified
+version of this compiler is used by <samp><span class="command">gcj</span></samp> to parse
+<samp><span class="file">.java</span></samp> source files. If this option is given, the
+&lsquo;<samp><span class="samp">libjava</span></samp>&rsquo; build will create and install an <samp><span class="file">ecj1</span></samp> executable
+which uses this jar file at runtime.
+
+ <p>If this option is not given, but an <samp><span class="file">ecj.jar</span></samp> file is found in
+the topmost source tree at configure time, then the &lsquo;<samp><span class="samp">libgcj</span></samp>&rsquo;
+build will create and install <samp><span class="file">ecj1</span></samp>, and will also install the
+discovered <samp><span class="file">ecj.jar</span></samp> into a suitable place in the install tree.
+
+ <p>If <samp><span class="file">ecj1</span></samp> is not installed, then the user will have to supply one
+on his path in order for <samp><span class="command">gcj</span></samp> to properly parse <samp><span class="file">.java</span></samp>
+source files. A suitable jar is available from
+<a href="ftp://sourceware.org/pub/java/">ftp://sourceware.org/pub/java/</a>.
+
+ <br><dt><code>--disable-getenv-properties</code><dd>Don't set system properties from <samp><span class="env">GCJ_PROPERTIES</span></samp>.
+
+ <br><dt><code>--enable-hash-synchronization</code><dd>Use a global hash table for monitor locks. Ordinarily,
+&lsquo;<samp><span class="samp">libgcj</span></samp>&rsquo;'s &lsquo;<samp><span class="samp">configure</span></samp>&rsquo; script automatically makes
+the correct choice for this option for your platform. Only use
+this if you know you need the library to be configured differently.
+
+ <br><dt><code>--enable-interpreter</code><dd>Enable the Java interpreter. The interpreter is automatically
+enabled by default on all platforms that support it. This option
+is really only useful if you want to disable the interpreter
+(using <samp><span class="option">--disable-interpreter</span></samp>).
+
+ <br><dt><code>--disable-java-net</code><dd>Disable java.net. This disables the native part of java.net only,
+using non-functional stubs for native method implementations.
+
+ <br><dt><code>--disable-jvmpi</code><dd>Disable JVMPI support.
+
+ <br><dt><code>--disable-libgcj-bc</code><dd>Disable BC ABI compilation of certain parts of libgcj. By default,
+some portions of libgcj are compiled with <samp><span class="option">-findirect-dispatch</span></samp>
+and <samp><span class="option">-fno-indirect-classes</span></samp>, allowing them to be overridden at
+run-time.
+
+ <p>If <samp><span class="option">--disable-libgcj-bc</span></samp> is specified, libgcj is built without
+these options. This allows the compile-time linker to resolve
+dependencies when statically linking to libgcj. However it makes it
+impossible to override the affected portions of libgcj at run-time.
+
+ <br><dt><code>--enable-reduced-reflection</code><dd>Build most of libgcj with <samp><span class="option">-freduced-reflection</span></samp>. This reduces
+the size of libgcj at the expense of not being able to do accurate
+reflection on the classes it contains. This option is safe if you
+know that code using libgcj will never use reflection on the standard
+runtime classes in libgcj (including using serialization, RMI or CORBA).
+
+ <br><dt><code>--with-ecos</code><dd>Enable runtime eCos target support.
+
+ <br><dt><code>--without-libffi</code><dd>Don't use &lsquo;<samp><span class="samp">libffi</span></samp>&rsquo;. This will disable the interpreter and JNI
+support as well, as these require &lsquo;<samp><span class="samp">libffi</span></samp>&rsquo; to work.
+
+ <br><dt><code>--enable-libgcj-debug</code><dd>Enable runtime debugging code.
+
+ <br><dt><code>--enable-libgcj-multifile</code><dd>If specified, causes all <samp><span class="file">.java</span></samp> source files to be
+compiled into <samp><span class="file">.class</span></samp> files in one invocation of
+&lsquo;<samp><span class="samp">gcj</span></samp>&rsquo;. This can speed up build time, but is more
+resource-intensive. If this option is unspecified or
+disabled, &lsquo;<samp><span class="samp">gcj</span></samp>&rsquo; is invoked once for each <samp><span class="file">.java</span></samp>
+file to compile into a <samp><span class="file">.class</span></samp> file.
+
+ <br><dt><code>--with-libiconv-prefix=DIR</code><dd>Search for libiconv in <samp><span class="file">DIR/include</span></samp> and <samp><span class="file">DIR/lib</span></samp>.
+
+ <br><dt><code>--enable-sjlj-exceptions</code><dd>Force use of the <code>setjmp</code>/<code>longjmp</code>-based scheme for exceptions.
+&lsquo;<samp><span class="samp">configure</span></samp>&rsquo; ordinarily picks the correct value based on the platform.
+Only use this option if you are sure you need a different setting.
+
+ <br><dt><code>--with-system-zlib</code><dd>Use installed &lsquo;<samp><span class="samp">zlib</span></samp>&rsquo; rather than that included with GCC.
+
+ <br><dt><code>--with-win32-nlsapi=ansi, unicows or unicode</code><dd>Indicates how MinGW &lsquo;<samp><span class="samp">libgcj</span></samp>&rsquo; translates between UNICODE
+characters and the Win32 API.
+
+ <br><dt><code>--enable-java-home</code><dd>If enabled, this creates a JPackage compatible SDK environment during install.
+Note that if &ndash;enable-java-home is used, &ndash;with-arch-directory=ARCH must also
+be specified.
+
+ <br><dt><code>--with-arch-directory=ARCH</code><dd>Specifies the name to use for the <samp><span class="file">jre/lib/ARCH</span></samp> directory in the SDK
+environment created when &ndash;enable-java-home is passed. Typical names for this
+directory include i386, amd64, ia64, etc.
+
+ <br><dt><code>--with-os-directory=DIR</code><dd>Specifies the OS directory for the SDK include directory. This is set to auto
+detect, and is typically 'linux'.
+
+ <br><dt><code>--with-origin-name=NAME</code><dd>Specifies the JPackage origin name. This defaults to the 'gcj' in
+java-1.5.0-gcj.
+
+ <br><dt><code>--with-arch-suffix=SUFFIX</code><dd>Specifies the suffix for the sdk directory. Defaults to the empty string.
+Examples include '.x86_64' in 'java-1.5.0-gcj-1.5.0.0.x86_64'.
+
+ <br><dt><code>--with-jvm-root-dir=DIR</code><dd>Specifies where to install the SDK. Default is $(prefix)/lib/jvm.
+
+ <br><dt><code>--with-jvm-jar-dir=DIR</code><dd>Specifies where to install jars. Default is $(prefix)/lib/jvm-exports.
+
+ <br><dt><code>--with-python-dir=DIR</code><dd>Specifies where to install the Python modules used for aot-compile. DIR should
+not include the prefix used in installation. For example, if the Python modules
+are to be installed in /usr/lib/python2.5/site-packages, then
+&ndash;with-python-dir=/lib/python2.5/site-packages should be passed. If this is
+not specified, then the Python modules are installed in $(prefix)/share/python.
+
+ <br><dt><code>--enable-aot-compile-rpm</code><dd>Adds aot-compile-rpm to the list of installed scripts.
+
+ <br><dt><code>--enable-browser-plugin</code><dd>Build the gcjwebplugin web browser plugin.
+
+ <dl>
+<dt><code>ansi</code><dd>Use the single-byte <code>char</code> and the Win32 A functions natively,
+translating to and from UNICODE when using these functions. If
+unspecified, this is the default.
+
+ <br><dt><code>unicows</code><dd>Use the <code>WCHAR</code> and Win32 W functions natively. Adds
+<code>-lunicows</code> to <samp><span class="file">libgcj.spec</span></samp> to link with &lsquo;<samp><span class="samp">libunicows</span></samp>&rsquo;.
+<samp><span class="file">unicows.dll</span></samp> needs to be deployed on Microsoft Windows 9X machines
+running built executables. <samp><span class="file">libunicows.a</span></samp>, an open-source
+import library around Microsoft's <code>unicows.dll</code>, is obtained from
+<a href="http://libunicows.sourceforge.net/">http://libunicows.sourceforge.net/</a>, which also gives details
+on getting <samp><span class="file">unicows.dll</span></samp> from Microsoft.
+
+ <br><dt><code>unicode</code><dd>Use the <code>WCHAR</code> and Win32 W functions natively. Does <em>not</em>
+add <code>-lunicows</code> to <samp><span class="file">libgcj.spec</span></samp>. The built executables will
+only run on Microsoft Windows NT and above.
+</dl>
+ </dl>
+
+<h5 class="subsubheading"><a name="TOC6"></a>AWT-Specific Options</h5>
+
+ <dl>
+<dt><code>--with-x</code><dd>Use the X Window System.
+
+ <br><dt><code>--enable-java-awt=PEER(S)</code><dd>Specifies the AWT peer library or libraries to build alongside
+&lsquo;<samp><span class="samp">libgcj</span></samp>&rsquo;. If this option is unspecified or disabled, AWT
+will be non-functional. Current valid values are <samp><span class="option">gtk</span></samp> and
+<samp><span class="option">xlib</span></samp>. Multiple libraries should be separated by a
+comma (i.e. <samp><span class="option">--enable-java-awt=gtk,xlib</span></samp>).
+
+ <br><dt><code>--enable-gtk-cairo</code><dd>Build the cairo Graphics2D implementation on GTK.
+
+ <br><dt><code>--enable-java-gc=TYPE</code><dd>Choose garbage collector. Defaults to <samp><span class="option">boehm</span></samp> if unspecified.
+
+ <br><dt><code>--disable-gtktest</code><dd>Do not try to compile and run a test GTK+ program.
+
+ <br><dt><code>--disable-glibtest</code><dd>Do not try to compile and run a test GLIB program.
+
+ <br><dt><code>--with-libart-prefix=PFX</code><dd>Prefix where libart is installed (optional).
+
+ <br><dt><code>--with-libart-exec-prefix=PFX</code><dd>Exec prefix where libart is installed (optional).
+
+ <br><dt><code>--disable-libarttest</code><dd>Do not try to compile and run a test libart program.
+
+</dl>
+
+<h5 class="subsubheading"><a name="TOC7"></a>Overriding <samp><span class="command">configure</span></samp> test results</h5>
+
+<p>Sometimes, it might be necessary to override the result of some
+<samp><span class="command">configure</span></samp> test, for example in order to ease porting to a new
+system or work around a bug in a test. The toplevel <samp><span class="command">configure</span></samp>
+script provides three variables for this:
+
+ <dl>
+<dt><code>build_configargs</code><dd><a name="index-g_t_0040code_007bbuild_005fconfigargs_007d-3"></a>The contents of this variable is passed to all build <samp><span class="command">configure</span></samp>
+scripts.
+
+ <br><dt><code>host_configargs</code><dd><a name="index-g_t_0040code_007bhost_005fconfigargs_007d-4"></a>The contents of this variable is passed to all host <samp><span class="command">configure</span></samp>
+scripts.
+
+ <br><dt><code>target_configargs</code><dd><a name="index-g_t_0040code_007btarget_005fconfigargs_007d-5"></a>The contents of this variable is passed to all target <samp><span class="command">configure</span></samp>
+scripts.
+
+ </dl>
+
+ <p>In order to avoid shell and <samp><span class="command">make</span></samp> quoting issues for complex
+overrides, you can pass a setting for <samp><span class="env">CONFIG_SITE</span></samp> and set
+variables in the site file.
+
+ <p><hr />
+<p><a href="./index.html">Return to the GCC Installation page</a>
+
+<!-- ***Building**************************************************************** -->
+<!-- ***Testing***************************************************************** -->
+<!-- ***Final install*********************************************************** -->
+<!-- ***Binaries**************************************************************** -->
+<!-- ***Specific**************************************************************** -->
+<!-- ***Old documentation****************************************************** -->
+<!-- ***GFDL******************************************************************** -->
+<!-- *************************************************************************** -->
+<!-- Part 6 The End of the Document -->
+</body></html>
+
diff --git a/INSTALL/download.html b/INSTALL/download.html
new file mode 100644
index 000000000..68d0ba324
--- /dev/null
+++ b/INSTALL/download.html
@@ -0,0 +1,97 @@
+<html lang="en">
+<head>
+<title>Downloading GCC</title>
+<meta http-equiv="Content-Type" content="text/html">
+<meta name="description" content="Downloading GCC">
+<meta name="generator" content="makeinfo 4.13">
+<link title="Top" rel="top" href="#Top">
+<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
+<!--
+Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
+1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
+2010 Free Software Foundation, Inc.
+
+ Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, the Front-Cover texts being (a) (see below), and
+with the Back-Cover Texts being (b) (see below). A copy of the
+license is included in the section entitled "GNU Free Documentation License".
+
+(a) The FSF's Front-Cover Text is:
+
+ A GNU Manual
+
+(b) The FSF's Back-Cover Text is:
+
+ You have freedom to copy and modify this GNU Manual, like GNU
+ software. Copies published by the Free Software Foundation raise
+ funds for GNU development.-->
+<meta http-equiv="Content-Style-Type" content="text/css">
+<style type="text/css"><!--
+ pre.display { font-family:inherit }
+ pre.format { font-family:inherit }
+ pre.smalldisplay { font-family:inherit; font-size:smaller }
+ pre.smallformat { font-family:inherit; font-size:smaller }
+ pre.smallexample { font-size:smaller }
+ pre.smalllisp { font-size:smaller }
+ span.sc { font-variant:small-caps }
+ span.roman { font-family:serif; font-weight:normal; }
+ span.sansserif { font-family:sans-serif; font-weight:normal; }
+--></style>
+</head>
+<body>
+<h1 class="settitle">Downloading GCC</h1>
+<a name="index-Downloading-GCC-1"></a><a name="index-Downloading-the-Source-2"></a>
+GCC is distributed via <a href="http://gcc.gnu.org/svn.html">SVN</a> and FTP
+tarballs compressed with <samp><span class="command">gzip</span></samp> or
+<samp><span class="command">bzip2</span></samp>. It is possible to download a full distribution or specific
+components.
+
+ <p>Please refer to the <a href="http://gcc.gnu.org/releases.html">releases web page</a>
+for information on how to obtain GCC.
+
+ <p>The full distribution includes the C, C++, Objective-C, Fortran, Java,
+and Ada (in the case of GCC 3.1 and later) compilers. The full
+distribution also includes runtime libraries for C++, Objective-C,
+Fortran, and Java. In GCC 3.0 and later versions, the GNU compiler
+testsuites are also included in the full distribution.
+
+ <p>If you choose to download specific components, you must download the core
+GCC distribution plus any language specific distributions you wish to
+use. The core distribution includes the C language front end as well as the
+shared components. Each language has a tarball which includes the language
+front end as well as the language runtime (when appropriate).
+
+ <p>Unpack the core distribution as well as any language specific
+distributions in the same directory.
+
+ <p>If you also intend to build binutils (either to upgrade an existing
+installation or for use in place of the corresponding tools of your
+OS), unpack the binutils distribution either in the same directory or
+a separate one. In the latter case, add symbolic links to any
+components of the binutils you intend to build alongside the compiler
+(<samp><span class="file">bfd</span></samp>, <samp><span class="file">binutils</span></samp>, <samp><span class="file">gas</span></samp>, <samp><span class="file">gprof</span></samp>, <samp><span class="file">ld</span></samp>,
+<samp><span class="file">opcodes</span></samp>, <small class="dots">...</small>) to the directory containing the GCC sources.
+
+ <p>Likewise the GMP, MPFR and MPC libraries can be automatically built
+together with GCC. Unpack the GMP, MPFR and/or MPC source
+distributions in the directory containing the GCC sources and rename
+their directories to <samp><span class="file">gmp</span></samp>, <samp><span class="file">mpfr</span></samp> and <samp><span class="file">mpc</span></samp>,
+respectively (or use symbolic links with the same name).
+
+ <p><hr />
+<p><a href="./index.html">Return to the GCC Installation page</a>
+
+<!-- ***Configuration*********************************************************** -->
+<!-- ***Building**************************************************************** -->
+<!-- ***Testing***************************************************************** -->
+<!-- ***Final install*********************************************************** -->
+<!-- ***Binaries**************************************************************** -->
+<!-- ***Specific**************************************************************** -->
+<!-- ***Old documentation****************************************************** -->
+<!-- ***GFDL******************************************************************** -->
+<!-- *************************************************************************** -->
+<!-- Part 6 The End of the Document -->
+</body></html>
+
diff --git a/INSTALL/finalinstall.html b/INSTALL/finalinstall.html
new file mode 100644
index 000000000..73b882093
--- /dev/null
+++ b/INSTALL/finalinstall.html
@@ -0,0 +1,174 @@
+<html lang="en">
+<head>
+<title>Installing GCC: Final installation</title>
+<meta http-equiv="Content-Type" content="text/html">
+<meta name="description" content="Installing GCC: Final installation">
+<meta name="generator" content="makeinfo 4.13">
+<link title="Top" rel="top" href="#Top">
+<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
+<!--
+Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
+1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
+2010 Free Software Foundation, Inc.
+
+ Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, the Front-Cover texts being (a) (see below), and
+with the Back-Cover Texts being (b) (see below). A copy of the
+license is included in the section entitled "GNU Free Documentation License".
+
+(a) The FSF's Front-Cover Text is:
+
+ A GNU Manual
+
+(b) The FSF's Back-Cover Text is:
+
+ You have freedom to copy and modify this GNU Manual, like GNU
+ software. Copies published by the Free Software Foundation raise
+ funds for GNU development.-->
+<meta http-equiv="Content-Style-Type" content="text/css">
+<style type="text/css"><!--
+ pre.display { font-family:inherit }
+ pre.format { font-family:inherit }
+ pre.smalldisplay { font-family:inherit; font-size:smaller }
+ pre.smallformat { font-family:inherit; font-size:smaller }
+ pre.smallexample { font-size:smaller }
+ pre.smalllisp { font-size:smaller }
+ span.sc { font-variant:small-caps }
+ span.roman { font-family:serif; font-weight:normal; }
+ span.sansserif { font-family:sans-serif; font-weight:normal; }
+--></style>
+</head>
+<body>
+<h1 class="settitle">Installing GCC: Final installation</h1>
+Now that GCC has been built (and optionally tested), you can install it with
+<pre class="smallexample"> cd <var>objdir</var> &amp;&amp; make install
+</pre>
+ <p>We strongly recommend to install into a target directory where there is
+no previous version of GCC present. Also, the GNAT runtime should not
+be stripped, as this would break certain features of the debugger that
+depend on this debugging information (catching Ada exceptions for
+instance).
+
+ <p>That step completes the installation of GCC; user level binaries can
+be found in <samp><var>prefix</var><span class="file">/bin</span></samp> where <var>prefix</var> is the value
+you specified with the <samp><span class="option">--prefix</span></samp> to configure (or
+<samp><span class="file">/usr/local</span></samp> by default). (If you specified <samp><span class="option">--bindir</span></samp>,
+that directory will be used instead; otherwise, if you specified
+<samp><span class="option">--exec-prefix</span></samp>, <samp><var>exec-prefix</var><span class="file">/bin</span></samp> will be used.)
+Headers for the C++ and Java libraries are installed in
+<samp><var>prefix</var><span class="file">/include</span></samp>; libraries in <samp><var>libdir</var></samp>
+(normally <samp><var>prefix</var><span class="file">/lib</span></samp>); internal parts of the compiler in
+<samp><var>libdir</var><span class="file">/gcc</span></samp> and <samp><var>libexecdir</var><span class="file">/gcc</span></samp>; documentation
+in info format in <samp><var>infodir</var></samp> (normally
+<samp><var>prefix</var><span class="file">/info</span></samp>).
+
+ <p>When installing cross-compilers, GCC's executables
+are not only installed into <samp><var>bindir</var></samp>, that
+is, <samp><var>exec-prefix</var><span class="file">/bin</span></samp>, but additionally into
+<samp><var>exec-prefix</var><span class="file">/</span><var>target-alias</var><span class="file">/bin</span></samp>, if that directory
+exists. Typically, such <dfn>tooldirs</dfn> hold target-specific
+binutils, including assembler and linker.
+
+ <p>Installation into a temporary staging area or into a <samp><span class="command">chroot</span></samp>
+jail can be achieved with the command
+
+<pre class="smallexample"> make DESTDIR=<var>path-to-rootdir</var> install
+</pre>
+ <p class="noindent">where <var>path-to-rootdir</var> is the absolute path of
+a directory relative to which all installation paths will be
+interpreted. Note that the directory specified by <code>DESTDIR</code>
+need not exist yet; it will be created if necessary.
+
+ <p>There is a subtle point with tooldirs and <code>DESTDIR</code>:
+If you relocate a cross-compiler installation with
+e.g. &lsquo;<samp><span class="samp">DESTDIR=</span><var>rootdir</var></samp>&rsquo;, then the directory
+<samp><var>rootdir</var><span class="file">/</span><var>exec-prefix</var><span class="file">/</span><var>target-alias</var><span class="file">/bin</span></samp> will
+be filled with duplicated GCC executables only if it already exists,
+it will not be created otherwise. This is regarded as a feature,
+not as a bug, because it gives slightly more control to the packagers
+using the <code>DESTDIR</code> feature.
+
+ <p>You can install stripped programs and libraries with
+
+<pre class="smallexample"> make install-strip
+</pre>
+ <p>If you are bootstrapping a released version of GCC then please
+quickly review the build status page for your release, available from
+<a href="http://gcc.gnu.org/buildstat.html">http://gcc.gnu.org/buildstat.html</a>.
+If your system is not listed for the version of GCC that you built,
+send a note to
+<a href="mailto:gcc@gcc.gnu.org">gcc@gcc.gnu.org</a> indicating
+that you successfully built and installed GCC.
+Include the following information:
+
+ <ul>
+<li>Output from running <samp><var>srcdir</var><span class="file">/config.guess</span></samp>. Do not send
+that file itself, just the one-line output from running it.
+
+ <li>The output of &lsquo;<samp><span class="samp">gcc -v</span></samp>&rsquo; for your newly installed <samp><span class="command">gcc</span></samp>.
+This tells us which version of GCC you built and the options you passed to
+configure.
+
+ <li>Whether you enabled all languages or a subset of them. If you used a
+full distribution then this information is part of the configure
+options in the output of &lsquo;<samp><span class="samp">gcc -v</span></samp>&rsquo;, but if you downloaded the
+&ldquo;core&rdquo; compiler plus additional front ends then it isn't apparent
+which ones you built unless you tell us about it.
+
+ <li>If the build was for GNU/Linux, also include:
+ <ul>
+<li>The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
+this information should be available from <samp><span class="file">/etc/issue</span></samp>.
+
+ <li>The version of the Linux kernel, available from &lsquo;<samp><span class="samp">uname --version</span></samp>&rsquo;
+or &lsquo;<samp><span class="samp">uname -a</span></samp>&rsquo;.
+
+ <li>The version of glibc you used; for RPM-based systems like Red Hat,
+Mandrake, and SuSE type &lsquo;<samp><span class="samp">rpm -q glibc</span></samp>&rsquo; to get the glibc version,
+and on systems like Debian and Progeny use &lsquo;<samp><span class="samp">dpkg -l libc6</span></samp>&rsquo;.
+</ul>
+ For other systems, you can include similar information if you think it is
+relevant.
+
+ <li>Any other information that you think would be useful to people building
+GCC on the same configuration. The new entry in the build status list
+will include a link to the archived copy of your message.
+</ul>
+
+ <p>We'd also like to know if the
+<a href="specific.html">host/target specific installation notes</a>
+didn't include your host/target information or if that information is
+incomplete or out of date. Send a note to
+<a href="mailto:gcc@gcc.gnu.org">gcc@gcc.gnu.org</a> detailing how the information should be changed.
+
+ <p>If you find a bug, please report it following the
+<a href="../bugs/">bug reporting guidelines</a>.
+
+ <p>If you want to print the GCC manuals, do &lsquo;<samp><span class="samp">cd </span><var>objdir</var><span class="samp">; make
+dvi</span></samp>&rsquo;. You will need to have <samp><span class="command">texi2dvi</span></samp> (version at least 4.7)
+and TeX installed. This creates a number of <samp><span class="file">.dvi</span></samp> files in
+subdirectories of <samp><var>objdir</var></samp>; these may be converted for
+printing with programs such as <samp><span class="command">dvips</span></samp>. Alternately, by using
+&lsquo;<samp><span class="samp">make pdf</span></samp>&rsquo; in place of &lsquo;<samp><span class="samp">make dvi</span></samp>&rsquo;, you can create documentation
+in the form of <samp><span class="file">.pdf</span></samp> files; this requires <samp><span class="command">texi2pdf</span></samp>, which
+is included with Texinfo version 4.8 and later. You can also
+<a href="http://shop.fsf.org/">buy printed manuals from the Free Software Foundation</a>, though such manuals may not be for the most
+recent version of GCC.
+
+ <p>If you would like to generate online HTML documentation, do &lsquo;<samp><span class="samp">cd
+</span><var>objdir</var><span class="samp">; make html</span></samp>&rsquo; and HTML will be generated for the gcc manuals in
+<samp><var>objdir</var><span class="file">/gcc/HTML</span></samp>.
+
+ <p><hr />
+<p><a href="./index.html">Return to the GCC Installation page</a>
+
+<!-- ***Binaries**************************************************************** -->
+<!-- ***Specific**************************************************************** -->
+<!-- ***Old documentation****************************************************** -->
+<!-- ***GFDL******************************************************************** -->
+<!-- *************************************************************************** -->
+<!-- Part 6 The End of the Document -->
+</body></html>
+
diff --git a/INSTALL/gfdl.html b/INSTALL/gfdl.html
new file mode 100644
index 000000000..d4f387c88
--- /dev/null
+++ b/INSTALL/gfdl.html
@@ -0,0 +1,517 @@
+<html lang="en">
+<head>
+<title>Installing GCC: GNU Free Documentation License</title>
+<meta http-equiv="Content-Type" content="text/html">
+<meta name="description" content="Installing GCC: GNU Free Documentation License">
+<meta name="generator" content="makeinfo 4.13">
+<link title="Top" rel="top" href="#Top">
+<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
+<!--
+Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
+1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
+2010 Free Software Foundation, Inc.
+
+ Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, the Front-Cover texts being (a) (see below), and
+with the Back-Cover Texts being (b) (see below). A copy of the
+license is included in the section entitled "GNU Free Documentation License".
+
+(a) The FSF's Front-Cover Text is:
+
+ A GNU Manual
+
+(b) The FSF's Back-Cover Text is:
+
+ You have freedom to copy and modify this GNU Manual, like GNU
+ software. Copies published by the Free Software Foundation raise
+ funds for GNU development.-->
+<meta http-equiv="Content-Style-Type" content="text/css">
+<style type="text/css"><!--
+ pre.display { font-family:inherit }
+ pre.format { font-family:inherit }
+ pre.smalldisplay { font-family:inherit; font-size:smaller }
+ pre.smallformat { font-family:inherit; font-size:smaller }
+ pre.smallexample { font-size:smaller }
+ pre.smalllisp { font-size:smaller }
+ span.sc { font-variant:small-caps }
+ span.roman { font-family:serif; font-weight:normal; }
+ span.sansserif { font-family:sans-serif; font-weight:normal; }
+--></style>
+</head>
+<body>
+<h1 class="settitle">Installing GCC: GNU Free Documentation License</h1>
+<h1 align="center">Installing GCC: GNU Free Documentation License</h1><!-- man begin DESCRIPTION -->
+
+ <p><a name="index-FDL_002c-GNU-Free-Documentation-License-1"></a><div align="center">Version 1.3, 3 November 2008</div>
+
+<pre class="display"> Copyright &copy; 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
+ <a href="http://fsf.org/">http://fsf.org/</a>
+
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+</pre>
+ <ol type=1 start=0>
+<li>PREAMBLE
+
+ <p>The purpose of this License is to make a manual, textbook, or other
+functional and useful document <dfn>free</dfn> in the sense of freedom: to
+assure everyone the effective freedom to copy and redistribute it,
+with or without modifying it, either commercially or noncommercially.
+Secondarily, this License preserves for the author and publisher a way
+to get credit for their work, while not being considered responsible
+for modifications made by others.
+
+ <p>This License is a kind of &ldquo;copyleft&rdquo;, which means that derivative
+works of the document must themselves be free in the same sense. It
+complements the GNU General Public License, which is a copyleft
+license designed for free software.
+
+ <p>We have designed this License in order to use it for manuals for free
+software, because free software needs free documentation: a free
+program should come with manuals providing the same freedoms that the
+software does. But this License is not limited to software manuals;
+it can be used for any textual work, regardless of subject matter or
+whether it is published as a printed book. We recommend this License
+principally for works whose purpose is instruction or reference.
+
+ <li>APPLICABILITY AND DEFINITIONS
+
+ <p>This License applies to any manual or other work, in any medium, that
+contains a notice placed by the copyright holder saying it can be
+distributed under the terms of this License. Such a notice grants a
+world-wide, royalty-free license, unlimited in duration, to use that
+work under the conditions stated herein. The &ldquo;Document&rdquo;, below,
+refers to any such manual or work. Any member of the public is a
+licensee, and is addressed as &ldquo;you&rdquo;. You accept the license if you
+copy, modify or distribute the work in a way requiring permission
+under copyright law.
+
+ <p>A &ldquo;Modified Version&rdquo; of the Document means any work containing the
+Document or a portion of it, either copied verbatim, or with
+modifications and/or translated into another language.
+
+ <p>A &ldquo;Secondary Section&rdquo; is a named appendix or a front-matter section
+of the Document that deals exclusively with the relationship of the
+publishers or authors of the Document to the Document's overall
+subject (or to related matters) and contains nothing that could fall
+directly within that overall subject. (Thus, if the Document is in
+part a textbook of mathematics, a Secondary Section may not explain
+any mathematics.) The relationship could be a matter of historical
+connection with the subject or with related matters, or of legal,
+commercial, philosophical, ethical or political position regarding
+them.
+
+ <p>The &ldquo;Invariant Sections&rdquo; are certain Secondary Sections whose titles
+are designated, as being those of Invariant Sections, in the notice
+that says that the Document is released under this License. If a
+section does not fit the above definition of Secondary then it is not
+allowed to be designated as Invariant. The Document may contain zero
+Invariant Sections. If the Document does not identify any Invariant
+Sections then there are none.
+
+ <p>The &ldquo;Cover Texts&rdquo; are certain short passages of text that are listed,
+as Front-Cover Texts or Back-Cover Texts, in the notice that says that
+the Document is released under this License. A Front-Cover Text may
+be at most 5 words, and a Back-Cover Text may be at most 25 words.
+
+ <p>A &ldquo;Transparent&rdquo; copy of the Document means a machine-readable copy,
+represented in a format whose specification is available to the
+general public, that is suitable for revising the document
+straightforwardly with generic text editors or (for images composed of
+pixels) generic paint programs or (for drawings) some widely available
+drawing editor, and that is suitable for input to text formatters or
+for automatic translation to a variety of formats suitable for input
+to text formatters. A copy made in an otherwise Transparent file
+format whose markup, or absence of markup, has been arranged to thwart
+or discourage subsequent modification by readers is not Transparent.
+An image format is not Transparent if used for any substantial amount
+of text. A copy that is not &ldquo;Transparent&rdquo; is called &ldquo;Opaque&rdquo;.
+
+ <p>Examples of suitable formats for Transparent copies include plain
+<span class="sc">ascii</span> without markup, Texinfo input format, LaTeX input
+format, <acronym>SGML</acronym> or <acronym>XML</acronym> using a publicly available
+<acronym>DTD</acronym>, and standard-conforming simple <acronym>HTML</acronym>,
+PostScript or <acronym>PDF</acronym> designed for human modification. Examples
+of transparent image formats include <acronym>PNG</acronym>, <acronym>XCF</acronym> and
+<acronym>JPG</acronym>. Opaque formats include proprietary formats that can be
+read and edited only by proprietary word processors, <acronym>SGML</acronym> or
+<acronym>XML</acronym> for which the <acronym>DTD</acronym> and/or processing tools are
+not generally available, and the machine-generated <acronym>HTML</acronym>,
+PostScript or <acronym>PDF</acronym> produced by some word processors for
+output purposes only.
+
+ <p>The &ldquo;Title Page&rdquo; means, for a printed book, the title page itself,
+plus such following pages as are needed to hold, legibly, the material
+this License requires to appear in the title page. For works in
+formats which do not have any title page as such, &ldquo;Title Page&rdquo; means
+the text near the most prominent appearance of the work's title,
+preceding the beginning of the body of the text.
+
+ <p>The &ldquo;publisher&rdquo; means any person or entity that distributes copies
+of the Document to the public.
+
+ <p>A section &ldquo;Entitled XYZ&rdquo; means a named subunit of the Document whose
+title either is precisely XYZ or contains XYZ in parentheses following
+text that translates XYZ in another language. (Here XYZ stands for a
+specific section name mentioned below, such as &ldquo;Acknowledgements&rdquo;,
+&ldquo;Dedications&rdquo;, &ldquo;Endorsements&rdquo;, or &ldquo;History&rdquo;.) To &ldquo;Preserve the Title&rdquo;
+of such a section when you modify the Document means that it remains a
+section &ldquo;Entitled XYZ&rdquo; according to this definition.
+
+ <p>The Document may include Warranty Disclaimers next to the notice which
+states that this License applies to the Document. These Warranty
+Disclaimers are considered to be included by reference in this
+License, but only as regards disclaiming warranties: any other
+implication that these Warranty Disclaimers may have is void and has
+no effect on the meaning of this License.
+
+ <li>VERBATIM COPYING
+
+ <p>You may copy and distribute the Document in any medium, either
+commercially or noncommercially, provided that this License, the
+copyright notices, and the license notice saying this License applies
+to the Document are reproduced in all copies, and that you add no other
+conditions whatsoever to those of this License. You may not use
+technical measures to obstruct or control the reading or further
+copying of the copies you make or distribute. However, you may accept
+compensation in exchange for copies. If you distribute a large enough
+number of copies you must also follow the conditions in section 3.
+
+ <p>You may also lend copies, under the same conditions stated above, and
+you may publicly display copies.
+
+ <li>COPYING IN QUANTITY
+
+ <p>If you publish printed copies (or copies in media that commonly have
+printed covers) of the Document, numbering more than 100, and the
+Document's license notice requires Cover Texts, you must enclose the
+copies in covers that carry, clearly and legibly, all these Cover
+Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
+the back cover. Both covers must also clearly and legibly identify
+you as the publisher of these copies. The front cover must present
+the full title with all words of the title equally prominent and
+visible. You may add other material on the covers in addition.
+Copying with changes limited to the covers, as long as they preserve
+the title of the Document and satisfy these conditions, can be treated
+as verbatim copying in other respects.
+
+ <p>If the required texts for either cover are too voluminous to fit
+legibly, you should put the first ones listed (as many as fit
+reasonably) on the actual cover, and continue the rest onto adjacent
+pages.
+
+ <p>If you publish or distribute Opaque copies of the Document numbering
+more than 100, you must either include a machine-readable Transparent
+copy along with each Opaque copy, or state in or with each Opaque copy
+a computer-network location from which the general network-using
+public has access to download using public-standard network protocols
+a complete Transparent copy of the Document, free of added material.
+If you use the latter option, you must take reasonably prudent steps,
+when you begin distribution of Opaque copies in quantity, to ensure
+that this Transparent copy will remain thus accessible at the stated
+location until at least one year after the last time you distribute an
+Opaque copy (directly or through your agents or retailers) of that
+edition to the public.
+
+ <p>It is requested, but not required, that you contact the authors of the
+Document well before redistributing any large number of copies, to give
+them a chance to provide you with an updated version of the Document.
+
+ <li>MODIFICATIONS
+
+ <p>You may copy and distribute a Modified Version of the Document under
+the conditions of sections 2 and 3 above, provided that you release
+the Modified Version under precisely this License, with the Modified
+Version filling the role of the Document, thus licensing distribution
+and modification of the Modified Version to whoever possesses a copy
+of it. In addition, you must do these things in the Modified Version:
+
+ <ol type=A start=1>
+<li>Use in the Title Page (and on the covers, if any) a title distinct
+from that of the Document, and from those of previous versions
+(which should, if there were any, be listed in the History section
+of the Document). You may use the same title as a previous version
+if the original publisher of that version gives permission.
+
+ <li>List on the Title Page, as authors, one or more persons or entities
+responsible for authorship of the modifications in the Modified
+Version, together with at least five of the principal authors of the
+Document (all of its principal authors, if it has fewer than five),
+unless they release you from this requirement.
+
+ <li>State on the Title page the name of the publisher of the
+Modified Version, as the publisher.
+
+ <li>Preserve all the copyright notices of the Document.
+
+ <li>Add an appropriate copyright notice for your modifications
+adjacent to the other copyright notices.
+
+ <li>Include, immediately after the copyright notices, a license notice
+giving the public permission to use the Modified Version under the
+terms of this License, in the form shown in the Addendum below.
+
+ <li>Preserve in that license notice the full lists of Invariant Sections
+and required Cover Texts given in the Document's license notice.
+
+ <li>Include an unaltered copy of this License.
+
+ <li>Preserve the section Entitled &ldquo;History&rdquo;, Preserve its Title, and add
+to it an item stating at least the title, year, new authors, and
+publisher of the Modified Version as given on the Title Page. If
+there is no section Entitled &ldquo;History&rdquo; in the Document, create one
+stating the title, year, authors, and publisher of the Document as
+given on its Title Page, then add an item describing the Modified
+Version as stated in the previous sentence.
+
+ <li>Preserve the network location, if any, given in the Document for
+public access to a Transparent copy of the Document, and likewise
+the network locations given in the Document for previous versions
+it was based on. These may be placed in the &ldquo;History&rdquo; section.
+You may omit a network location for a work that was published at
+least four years before the Document itself, or if the original
+publisher of the version it refers to gives permission.
+
+ <li>For any section Entitled &ldquo;Acknowledgements&rdquo; or &ldquo;Dedications&rdquo;, Preserve
+the Title of the section, and preserve in the section all the
+substance and tone of each of the contributor acknowledgements and/or
+dedications given therein.
+
+ <li>Preserve all the Invariant Sections of the Document,
+unaltered in their text and in their titles. Section numbers
+or the equivalent are not considered part of the section titles.
+
+ <li>Delete any section Entitled &ldquo;Endorsements&rdquo;. Such a section
+may not be included in the Modified Version.
+
+ <li>Do not retitle any existing section to be Entitled &ldquo;Endorsements&rdquo; or
+to conflict in title with any Invariant Section.
+
+ <li>Preserve any Warranty Disclaimers.
+ </ol>
+
+ <p>If the Modified Version includes new front-matter sections or
+appendices that qualify as Secondary Sections and contain no material
+copied from the Document, you may at your option designate some or all
+of these sections as invariant. To do this, add their titles to the
+list of Invariant Sections in the Modified Version's license notice.
+These titles must be distinct from any other section titles.
+
+ <p>You may add a section Entitled &ldquo;Endorsements&rdquo;, provided it contains
+nothing but endorsements of your Modified Version by various
+parties&mdash;for example, statements of peer review or that the text has
+been approved by an organization as the authoritative definition of a
+standard.
+
+ <p>You may add a passage of up to five words as a Front-Cover Text, and a
+passage of up to 25 words as a Back-Cover Text, to the end of the list
+of Cover Texts in the Modified Version. Only one passage of
+Front-Cover Text and one of Back-Cover Text may be added by (or
+through arrangements made by) any one entity. If the Document already
+includes a cover text for the same cover, previously added by you or
+by arrangement made by the same entity you are acting on behalf of,
+you may not add another; but you may replace the old one, on explicit
+permission from the previous publisher that added the old one.
+
+ <p>The author(s) and publisher(s) of the Document do not by this License
+give permission to use their names for publicity for or to assert or
+imply endorsement of any Modified Version.
+
+ <li>COMBINING DOCUMENTS
+
+ <p>You may combine the Document with other documents released under this
+License, under the terms defined in section 4 above for modified
+versions, provided that you include in the combination all of the
+Invariant Sections of all of the original documents, unmodified, and
+list them all as Invariant Sections of your combined work in its
+license notice, and that you preserve all their Warranty Disclaimers.
+
+ <p>The combined work need only contain one copy of this License, and
+multiple identical Invariant Sections may be replaced with a single
+copy. If there are multiple Invariant Sections with the same name but
+different contents, make the title of each such section unique by
+adding at the end of it, in parentheses, the name of the original
+author or publisher of that section if known, or else a unique number.
+Make the same adjustment to the section titles in the list of
+Invariant Sections in the license notice of the combined work.
+
+ <p>In the combination, you must combine any sections Entitled &ldquo;History&rdquo;
+in the various original documents, forming one section Entitled
+&ldquo;History&rdquo;; likewise combine any sections Entitled &ldquo;Acknowledgements&rdquo;,
+and any sections Entitled &ldquo;Dedications&rdquo;. You must delete all
+sections Entitled &ldquo;Endorsements.&rdquo;
+
+ <li>COLLECTIONS OF DOCUMENTS
+
+ <p>You may make a collection consisting of the Document and other documents
+released under this License, and replace the individual copies of this
+License in the various documents with a single copy that is included in
+the collection, provided that you follow the rules of this License for
+verbatim copying of each of the documents in all other respects.
+
+ <p>You may extract a single document from such a collection, and distribute
+it individually under this License, provided you insert a copy of this
+License into the extracted document, and follow this License in all
+other respects regarding verbatim copying of that document.
+
+ <li>AGGREGATION WITH INDEPENDENT WORKS
+
+ <p>A compilation of the Document or its derivatives with other separate
+and independent documents or works, in or on a volume of a storage or
+distribution medium, is called an &ldquo;aggregate&rdquo; if the copyright
+resulting from the compilation is not used to limit the legal rights
+of the compilation's users beyond what the individual works permit.
+When the Document is included in an aggregate, this License does not
+apply to the other works in the aggregate which are not themselves
+derivative works of the Document.
+
+ <p>If the Cover Text requirement of section 3 is applicable to these
+copies of the Document, then if the Document is less than one half of
+the entire aggregate, the Document's Cover Texts may be placed on
+covers that bracket the Document within the aggregate, or the
+electronic equivalent of covers if the Document is in electronic form.
+Otherwise they must appear on printed covers that bracket the whole
+aggregate.
+
+ <li>TRANSLATION
+
+ <p>Translation is considered a kind of modification, so you may
+distribute translations of the Document under the terms of section 4.
+Replacing Invariant Sections with translations requires special
+permission from their copyright holders, but you may include
+translations of some or all Invariant Sections in addition to the
+original versions of these Invariant Sections. You may include a
+translation of this License, and all the license notices in the
+Document, and any Warranty Disclaimers, provided that you also include
+the original English version of this License and the original versions
+of those notices and disclaimers. In case of a disagreement between
+the translation and the original version of this License or a notice
+or disclaimer, the original version will prevail.
+
+ <p>If a section in the Document is Entitled &ldquo;Acknowledgements&rdquo;,
+&ldquo;Dedications&rdquo;, or &ldquo;History&rdquo;, the requirement (section 4) to Preserve
+its Title (section 1) will typically require changing the actual
+title.
+
+ <li>TERMINATION
+
+ <p>You may not copy, modify, sublicense, or distribute the Document
+except as expressly provided under this License. Any attempt
+otherwise to copy, modify, sublicense, or distribute it is void, and
+will automatically terminate your rights under this License.
+
+ <p>However, if you cease all violation of this License, then your license
+from a particular copyright holder is reinstated (a) provisionally,
+unless and until the copyright holder explicitly and finally
+terminates your license, and (b) permanently, if the copyright holder
+fails to notify you of the violation by some reasonable means prior to
+60 days after the cessation.
+
+ <p>Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+ <p>Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License. If your rights have been terminated and not permanently
+reinstated, receipt of a copy of some or all of the same material does
+not give you any rights to use it.
+
+ <li>FUTURE REVISIONS OF THIS LICENSE
+
+ <p>The Free Software Foundation may publish new, revised versions
+of the GNU Free Documentation License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns. See
+<a href="http://www.gnu.org/copyleft/">http://www.gnu.org/copyleft/</a>.
+
+ <p>Each version of the License is given a distinguishing version number.
+If the Document specifies that a particular numbered version of this
+License &ldquo;or any later version&rdquo; applies to it, you have the option of
+following the terms and conditions either of that specified version or
+of any later version that has been published (not as a draft) by the
+Free Software Foundation. If the Document does not specify a version
+number of this License, you may choose any version ever published (not
+as a draft) by the Free Software Foundation. If the Document
+specifies that a proxy can decide which future versions of this
+License can be used, that proxy's public statement of acceptance of a
+version permanently authorizes you to choose that version for the
+Document.
+
+ <li>RELICENSING
+
+ <p>&ldquo;Massive Multiauthor Collaboration Site&rdquo; (or &ldquo;MMC Site&rdquo;) means any
+World Wide Web server that publishes copyrightable works and also
+provides prominent facilities for anybody to edit those works. A
+public wiki that anybody can edit is an example of such a server. A
+&ldquo;Massive Multiauthor Collaboration&rdquo; (or &ldquo;MMC&rdquo;) contained in the
+site means any set of copyrightable works thus published on the MMC
+site.
+
+ <p>&ldquo;CC-BY-SA&rdquo; means the Creative Commons Attribution-Share Alike 3.0
+license published by Creative Commons Corporation, a not-for-profit
+corporation with a principal place of business in San Francisco,
+California, as well as future copyleft versions of that license
+published by that same organization.
+
+ <p>&ldquo;Incorporate&rdquo; means to publish or republish a Document, in whole or
+in part, as part of another Document.
+
+ <p>An MMC is &ldquo;eligible for relicensing&rdquo; if it is licensed under this
+License, and if all works that were first published under this License
+somewhere other than this MMC, and subsequently incorporated in whole
+or in part into the MMC, (1) had no cover texts or invariant sections,
+and (2) were thus incorporated prior to November 1, 2008.
+
+ <p>The operator of an MMC Site may republish an MMC contained in the site
+under CC-BY-SA on the same site at any time before August 1, 2009,
+provided the MMC is eligible for relicensing.
+
+ </ol>
+
+<h3 class="unnumberedsec"><a name="TOC0"></a>ADDENDUM: How to use this License for your documents</h3>
+
+<p>To use this License in a document you have written, include a copy of
+the License in the document and put the following copyright and
+license notices just after the title page:
+
+<pre class="smallexample"> Copyright (C) <var>year</var> <var>your name</var>.
+ Permission is granted to copy, distribute and/or modify this document
+ under the terms of the GNU Free Documentation License, Version 1.3
+ or any later version published by the Free Software Foundation;
+ with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
+ Texts. A copy of the license is included in the section entitled ``GNU
+ Free Documentation License''.
+</pre>
+ <p>If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
+replace the &ldquo;with...Texts.&rdquo; line with this:
+
+<pre class="smallexample"> with the Invariant Sections being <var>list their titles</var>, with
+ the Front-Cover Texts being <var>list</var>, and with the Back-Cover Texts
+ being <var>list</var>.
+</pre>
+ <p>If you have Invariant Sections without Cover Texts, or some other
+combination of the three, merge those two alternatives to suit the
+situation.
+
+ <p>If your document contains nontrivial examples of program code, we
+recommend releasing these examples in parallel under your choice of
+free software license, such as the GNU General Public License,
+to permit their use in free software.
+
+<!-- Local Variables: -->
+<!-- ispell-local-pdict: "ispell-dict" -->
+<!-- End: -->
+<!-- man end -->
+ <p><hr />
+<p><a href="./index.html">Return to the GCC Installation page</a>
+
+<!-- *************************************************************************** -->
+<!-- Part 6 The End of the Document -->
+</body></html>
+
diff --git a/INSTALL/index.html b/INSTALL/index.html
new file mode 100644
index 000000000..9b294f2c0
--- /dev/null
+++ b/INSTALL/index.html
@@ -0,0 +1,125 @@
+<html lang="en">
+<head>
+<title>Installing GCC</title>
+<meta http-equiv="Content-Type" content="text/html">
+<meta name="description" content="Installing GCC">
+<meta name="generator" content="makeinfo 4.13">
+<link title="Top" rel="top" href="#Top">
+<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
+<!--
+Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
+1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
+2010 Free Software Foundation, Inc.
+
+ Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, the Front-Cover texts being (a) (see below), and
+with the Back-Cover Texts being (b) (see below). A copy of the
+license is included in the section entitled "GNU Free Documentation License".
+
+(a) The FSF's Front-Cover Text is:
+
+ A GNU Manual
+
+(b) The FSF's Back-Cover Text is:
+
+ You have freedom to copy and modify this GNU Manual, like GNU
+ software. Copies published by the Free Software Foundation raise
+ funds for GNU development.-->
+<meta http-equiv="Content-Style-Type" content="text/css">
+<style type="text/css"><!--
+ pre.display { font-family:inherit }
+ pre.format { font-family:inherit }
+ pre.smalldisplay { font-family:inherit; font-size:smaller }
+ pre.smallformat { font-family:inherit; font-size:smaller }
+ pre.smallexample { font-size:smaller }
+ pre.smalllisp { font-size:smaller }
+ span.sc { font-variant:small-caps }
+ span.roman { font-family:serif; font-weight:normal; }
+ span.sansserif { font-family:sans-serif; font-weight:normal; }
+--></style>
+</head>
+<body>
+<h1 class="settitle">Installing GCC</h1>
+The latest version of this document is always available at
+<a href="http://gcc.gnu.org/install/">http://gcc.gnu.org/install/</a>.
+
+ <p>This document describes the generic installation procedure for GCC as well
+as detailing some target specific installation instructions.
+
+ <p>GCC includes several components that previously were separate distributions
+with their own installation instructions. This document supersedes all
+package specific installation instructions.
+
+ <p><em>Before</em> starting the build/install procedure please check the
+<a href="specific.html">host/target specific installation notes</a>.
+We recommend you browse the entire generic installation instructions before
+you proceed.
+
+ <p>Lists of successful builds for released versions of GCC are
+available at <a href="http://gcc.gnu.org/buildstat.html">http://gcc.gnu.org/buildstat.html</a>.
+These lists are updated as new information becomes available.
+
+ <p>The installation procedure itself is broken into five steps.
+
+ <ol type=1 start=1>
+<li><a href="prerequisites.html">Prerequisites</a>
+<li><a href="download.html">Downloading the source</a>
+<li><a href="configure.html">Configuration</a>
+<li><a href="build.html">Building</a>
+<li><a href="test.html">Testing</a> (optional)
+<li><a href="finalinstall.html">Final install</a>
+ </ol>
+
+ <p>Please note that GCC does not support &lsquo;<samp><span class="samp">make uninstall</span></samp>&rsquo; and probably
+won't do so in the near future as this would open a can of worms. Instead,
+we suggest that you install GCC into a directory of its own and simply
+remove that directory when you do not need that specific version of GCC
+any longer, and, if shared libraries are installed there as well, no
+more binaries exist that use them.
+
+ <p>There are also some <a href="old.html">old installation instructions</a>,
+which are mostly obsolete but still contain some information which has
+not yet been merged into the main part of this manual.
+
+ <p><hr />
+<p><a href="./index.html">Return to the GCC Installation page</a>
+
+ <p>Copyright &copy; 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
+1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
+2010 Free Software Foundation, Inc.
+ <pre class="sp">
+
+</pre>
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, the Front-Cover texts being (a) (see below), and
+with the Back-Cover Texts being (b) (see below). A copy of the
+license is included in the section entitled &ldquo;<a href="./gfdl.html">GNU Free Documentation License</a>&rdquo;.
+
+ <p>(a) The FSF's Front-Cover Text is:
+
+ <p>A GNU Manual
+
+ <p>(b) The FSF's Back-Cover Text is:
+
+ <p>You have freedom to copy and modify this GNU Manual, like GNU
+ software. Copies published by the Free Software Foundation raise
+ funds for GNU development.
+
+<!-- ***Prerequisites************************************************** -->
+<!-- ***Downloading the source************************************************** -->
+<!-- ***Configuration*********************************************************** -->
+<!-- ***Building**************************************************************** -->
+<!-- ***Testing***************************************************************** -->
+<!-- ***Final install*********************************************************** -->
+<!-- ***Binaries**************************************************************** -->
+<!-- ***Specific**************************************************************** -->
+<!-- ***Old documentation****************************************************** -->
+<!-- ***GFDL******************************************************************** -->
+<!-- *************************************************************************** -->
+<!-- Part 6 The End of the Document -->
+</body></html>
+
diff --git a/INSTALL/old.html b/INSTALL/old.html
new file mode 100644
index 000000000..b0e26b99a
--- /dev/null
+++ b/INSTALL/old.html
@@ -0,0 +1,213 @@
+<html lang="en">
+<head>
+<title>Installing GCC: Old documentation</title>
+<meta http-equiv="Content-Type" content="text/html">
+<meta name="description" content="Installing GCC: Old documentation">
+<meta name="generator" content="makeinfo 4.13">
+<link title="Top" rel="top" href="#Top">
+<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
+<!--
+Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
+1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
+2010 Free Software Foundation, Inc.
+
+ Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, the Front-Cover texts being (a) (see below), and
+with the Back-Cover Texts being (b) (see below). A copy of the
+license is included in the section entitled "GNU Free Documentation License".
+
+(a) The FSF's Front-Cover Text is:
+
+ A GNU Manual
+
+(b) The FSF's Back-Cover Text is:
+
+ You have freedom to copy and modify this GNU Manual, like GNU
+ software. Copies published by the Free Software Foundation raise
+ funds for GNU development.-->
+<meta http-equiv="Content-Style-Type" content="text/css">
+<style type="text/css"><!--
+ pre.display { font-family:inherit }
+ pre.format { font-family:inherit }
+ pre.smalldisplay { font-family:inherit; font-size:smaller }
+ pre.smallformat { font-family:inherit; font-size:smaller }
+ pre.smallexample { font-size:smaller }
+ pre.smalllisp { font-size:smaller }
+ span.sc { font-variant:small-caps }
+ span.roman { font-family:serif; font-weight:normal; }
+ span.sansserif { font-family:sans-serif; font-weight:normal; }
+--></style>
+</head>
+<body>
+<h1 class="settitle">Installing GCC: Old documentation</h1>
+<h1 align="center">Old installation documentation</h1>
+
+ <p>Note most of this information is out of date and superseded by the
+previous chapters of this manual. It is provided for historical
+reference only, because of a lack of volunteers to merge it into the
+main manual.
+
+ <p>Here is the procedure for installing GCC on a GNU or Unix system.
+
+ <ol type=1 start=1>
+<li>If you have chosen a configuration for GCC which requires other GNU
+tools (such as GAS or the GNU linker) instead of the standard system
+tools, install the required tools in the build directory under the names
+<samp><span class="file">as</span></samp>, <samp><span class="file">ld</span></samp> or whatever is appropriate.
+
+ <p>Alternatively, you can do subsequent compilation using a value of the
+<code>PATH</code> environment variable such that the necessary GNU tools come
+before the standard system tools.
+
+ <li>Specify the host, build and target machine configurations. You do this
+when you run the <samp><span class="file">configure</span></samp> script.
+
+ <p>The <dfn>build</dfn> machine is the system which you are using, the
+<dfn>host</dfn> machine is the system where you want to run the resulting
+compiler (normally the build machine), and the <dfn>target</dfn> machine is
+the system for which you want the compiler to generate code.
+
+ <p>If you are building a compiler to produce code for the machine it runs
+on (a native compiler), you normally do not need to specify any operands
+to <samp><span class="file">configure</span></samp>; it will try to guess the type of machine you are on
+and use that as the build, host and target machines. So you don't need
+to specify a configuration when building a native compiler unless
+<samp><span class="file">configure</span></samp> cannot figure out what your configuration is or guesses
+wrong.
+
+ <p>In those cases, specify the build machine's <dfn>configuration name</dfn>
+with the <samp><span class="option">--host</span></samp> option; the host and target will default to be
+the same as the host machine.
+
+ <p>Here is an example:
+
+ <pre class="smallexample"> ./configure --host=sparc-sun-sunos4.1
+</pre>
+ <p>A configuration name may be canonical or it may be more or less
+abbreviated.
+
+ <p>A canonical configuration name has three parts, separated by dashes.
+It looks like this: &lsquo;<samp><var>cpu</var><span class="samp">-</span><var>company</var><span class="samp">-</span><var>system</var></samp>&rsquo;.
+(The three parts may themselves contain dashes; <samp><span class="file">configure</span></samp>
+can figure out which dashes serve which purpose.) For example,
+&lsquo;<samp><span class="samp">m68k-sun-sunos4.1</span></samp>&rsquo; specifies a Sun 3.
+
+ <p>You can also replace parts of the configuration by nicknames or aliases.
+For example, &lsquo;<samp><span class="samp">sun3</span></samp>&rsquo; stands for &lsquo;<samp><span class="samp">m68k-sun</span></samp>&rsquo;, so
+&lsquo;<samp><span class="samp">sun3-sunos4.1</span></samp>&rsquo; is another way to specify a Sun 3.
+
+ <p>You can specify a version number after any of the system types, and some
+of the CPU types. In most cases, the version is irrelevant, and will be
+ignored. So you might as well specify the version if you know it.
+
+ <p>See <a href="#Configurations">Configurations</a>, for a list of supported configuration names and
+notes on many of the configurations. You should check the notes in that
+section before proceeding any further with the installation of GCC.
+
+ </ol>
+
+ <p><h2><a name="Configurations"></a>Configurations Supported by GCC</h2><a name="index-configurations-supported-by-GCC-1"></a>
+Here are the possible CPU types:
+
+ <blockquote>
+<!-- gmicro, fx80, spur and tahoe omitted since they don't work. -->
+1750a, a29k, alpha, arm, avr, c<var>n</var>, clipper, dsp16xx, elxsi, fr30, h8300,
+hppa1.0, hppa1.1, i370, i386, i486, i586, i686, i786, i860, i960, ip2k, m32r,
+m68000, m68k, m6811, m6812, m88k, mcore, mips, mipsel, mips64, mips64el,
+mn10200, mn10300, ns32k, pdp11, powerpc, powerpcle, romp, rs6000, sh, sparc,
+sparclite, sparc64, v850, vax, we32k.
+</blockquote>
+
+ <p>Here are the recognized company names. As you can see, customary
+abbreviations are used rather than the longer official names.
+
+<!-- What should be done about merlin, tek*, dolphin? -->
+ <blockquote>
+acorn, alliant, altos, apollo, apple, att, bull,
+cbm, convergent, convex, crds, dec, dg, dolphin,
+elxsi, encore, harris, hitachi, hp, ibm, intergraph, isi,
+mips, motorola, ncr, next, ns, omron, plexus,
+sequent, sgi, sony, sun, tti, unicom, wrs.
+</blockquote>
+
+ <p>The company name is meaningful only to disambiguate when the rest of
+the information supplied is insufficient. You can omit it, writing
+just &lsquo;<samp><var>cpu</var><span class="samp">-</span><var>system</var></samp>&rsquo;, if it is not needed. For example,
+&lsquo;<samp><span class="samp">vax-ultrix4.2</span></samp>&rsquo; is equivalent to &lsquo;<samp><span class="samp">vax-dec-ultrix4.2</span></samp>&rsquo;.
+
+ <p>Here is a list of system types:
+
+ <blockquote>
+386bsd, aix, acis, amigaos, aos, aout, aux, bosx, bsd, clix, coff, ctix, cxux,
+dgux, dynix, ebmon, ecoff, elf, esix, freebsd, hms, genix, gnu, linux,
+linux-gnu, hiux, hpux, iris, irix, isc, luna, lynxos, mach, minix, msdos, mvs,
+netbsd, newsos, nindy, ns, osf, osfrose, ptx, riscix, riscos, rtu, sco, sim,
+solaris, sunos, sym, sysv, udi, ultrix, unicos, uniplus, unos, vms, vsta,
+vxworks, winnt, xenix.
+</blockquote>
+
+<p class="noindent">You can omit the system type; then <samp><span class="file">configure</span></samp> guesses the
+operating system from the CPU and company.
+
+ <p>You can add a version number to the system type; this may or may not
+make a difference. For example, you can write &lsquo;<samp><span class="samp">bsd4.3</span></samp>&rsquo; or
+&lsquo;<samp><span class="samp">bsd4.4</span></samp>&rsquo; to distinguish versions of BSD. In practice, the version
+number is most needed for &lsquo;<samp><span class="samp">sysv3</span></samp>&rsquo; and &lsquo;<samp><span class="samp">sysv4</span></samp>&rsquo;, which are often
+treated differently.
+
+ <p>&lsquo;<samp><span class="samp">linux-gnu</span></samp>&rsquo; is the canonical name for the GNU/Linux target; however
+GCC will also accept &lsquo;<samp><span class="samp">linux</span></samp>&rsquo;. The version of the kernel in use is
+not relevant on these systems. A suffix such as &lsquo;<samp><span class="samp">libc1</span></samp>&rsquo; or &lsquo;<samp><span class="samp">aout</span></samp>&rsquo;
+distinguishes major versions of the C library; all of the suffixed versions
+are obsolete.
+
+ <p>If you specify an impossible combination such as &lsquo;<samp><span class="samp">i860-dg-vms</span></samp>&rsquo;,
+then you may get an error message from <samp><span class="file">configure</span></samp>, or it may
+ignore part of the information and do the best it can with the rest.
+<samp><span class="file">configure</span></samp> always prints the canonical name for the alternative
+that it used. GCC does not support all possible alternatives.
+
+ <p>Often a particular model of machine has a name. Many machine names are
+recognized as aliases for CPU/company combinations. Thus, the machine
+name &lsquo;<samp><span class="samp">sun3</span></samp>&rsquo;, mentioned above, is an alias for &lsquo;<samp><span class="samp">m68k-sun</span></samp>&rsquo;.
+Sometimes we accept a company name as a machine name, when the name is
+popularly used for a particular machine. Here is a table of the known
+machine names:
+
+ <blockquote>
+3300, 3b1, 3b<var>n</var>, 7300, altos3068, altos,
+apollo68, att-7300, balance,
+convex-c<var>n</var>, crds, decstation-3100,
+decstation, delta, encore,
+fx2800, gmicro, hp7<var>nn</var>, hp8<var>nn</var>,
+hp9k2<var>nn</var>, hp9k3<var>nn</var>, hp9k7<var>nn</var>,
+hp9k8<var>nn</var>, iris4d, iris, isi68,
+m3230, magnum, merlin, miniframe,
+mmax, news-3600, news800, news, next,
+pbd, pc532, pmax, powerpc, powerpcle, ps2, risc-news,
+rtpc, sun2, sun386i, sun386, sun3,
+sun4, symmetry, tower-32, tower.
+</blockquote>
+
+<p class="noindent">Remember that a machine name specifies both the cpu type and the company
+name.
+If you want to install your own homemade configuration files, you can
+use &lsquo;<samp><span class="samp">local</span></samp>&rsquo; as the company name to access them. If you use
+configuration &lsquo;<samp><var>cpu</var><span class="samp">-local</span></samp>&rsquo;, the configuration name
+without the cpu prefix
+is used to form the configuration file names.
+
+ <p>Thus, if you specify &lsquo;<samp><span class="samp">m68k-local</span></samp>&rsquo;, configuration uses
+files <samp><span class="file">m68k.md</span></samp>, <samp><span class="file">local.h</span></samp>, <samp><span class="file">m68k.c</span></samp>,
+<samp><span class="file">xm-local.h</span></samp>, <samp><span class="file">t-local</span></samp>, and <samp><span class="file">x-local</span></samp>, all in the
+directory <samp><span class="file">config/m68k</span></samp>.
+<hr />
+<p><a href="./index.html">Return to the GCC Installation page</a>
+
+<!-- ***GFDL******************************************************************** -->
+<!-- *************************************************************************** -->
+<!-- Part 6 The End of the Document -->
+</body></html>
+
diff --git a/INSTALL/prerequisites.html b/INSTALL/prerequisites.html
new file mode 100644
index 000000000..f5d374626
--- /dev/null
+++ b/INSTALL/prerequisites.html
@@ -0,0 +1,297 @@
+<html lang="en">
+<head>
+<title>Prerequisites for GCC</title>
+<meta http-equiv="Content-Type" content="text/html">
+<meta name="description" content="Prerequisites for GCC">
+<meta name="generator" content="makeinfo 4.13">
+<link title="Top" rel="top" href="#Top">
+<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
+<!--
+Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
+1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
+2010 Free Software Foundation, Inc.
+
+ Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, the Front-Cover texts being (a) (see below), and
+with the Back-Cover Texts being (b) (see below). A copy of the
+license is included in the section entitled "GNU Free Documentation License".
+
+(a) The FSF's Front-Cover Text is:
+
+ A GNU Manual
+
+(b) The FSF's Back-Cover Text is:
+
+ You have freedom to copy and modify this GNU Manual, like GNU
+ software. Copies published by the Free Software Foundation raise
+ funds for GNU development.-->
+<meta http-equiv="Content-Style-Type" content="text/css">
+<style type="text/css"><!--
+ pre.display { font-family:inherit }
+ pre.format { font-family:inherit }
+ pre.smalldisplay { font-family:inherit; font-size:smaller }
+ pre.smallformat { font-family:inherit; font-size:smaller }
+ pre.smallexample { font-size:smaller }
+ pre.smalllisp { font-size:smaller }
+ span.sc { font-variant:small-caps }
+ span.roman { font-family:serif; font-weight:normal; }
+ span.sansserif { font-family:sans-serif; font-weight:normal; }
+--></style>
+</head>
+<body>
+<h1 class="settitle">Prerequisites for GCC</h1>
+<a name="index-Prerequisites-1"></a>
+GCC requires that various tools and packages be available for use in the
+build procedure. Modifying GCC sources requires additional tools
+described below.
+
+<h3 class="heading"><a name="TOC0"></a>Tools/packages necessary for building GCC</h3>
+
+ <dl>
+<dt>ISO C90 compiler<dd>Necessary to bootstrap GCC, although versions of GCC prior
+to 3.4 also allow bootstrapping with a traditional (K&amp;R) C compiler.
+
+ <p>To build all languages in a cross-compiler or other configuration where
+3-stage bootstrap is not performed, you need to start with an existing
+GCC binary (version 2.95 or later) because source code for language
+frontends other than C might use GCC extensions.
+
+ <br><dt>GNAT<dd>
+In order to build the Ada compiler (GNAT) you must already have GNAT
+installed because portions of the Ada frontend are written in Ada (with
+GNAT extensions.) Refer to the Ada installation instructions for more
+specific information.
+
+ <br><dt>A &ldquo;working&rdquo; POSIX compatible shell, or GNU bash<dd>
+Necessary when running <samp><span class="command">configure</span></samp> because some
+<samp><span class="command">/bin/sh</span></samp> shells have bugs and may crash when configuring the
+target libraries. In other cases, <samp><span class="command">/bin/sh</span></samp> or <samp><span class="command">ksh</span></samp>
+have disastrous corner-case performance problems. This
+can cause target <samp><span class="command">configure</span></samp> runs to literally take days to
+complete in some cases.
+
+ <p>So on some platforms <samp><span class="command">/bin/ksh</span></samp> is sufficient, on others it
+isn't. See the host/target specific instructions for your platform, or
+use <samp><span class="command">bash</span></samp> to be sure. Then set <samp><span class="env">CONFIG_SHELL</span></samp> in your
+environment to your &ldquo;good&rdquo; shell prior to running
+<samp><span class="command">configure</span></samp>/<samp><span class="command">make</span></samp>.
+
+ <p><samp><span class="command">zsh</span></samp> is not a fully compliant POSIX shell and will not
+work when configuring GCC.
+
+ <br><dt>A POSIX or SVR4 awk<dd>
+Necessary for creating some of the generated source files for GCC.
+If in doubt, use a recent GNU awk version, as some of the older ones
+are broken. GNU awk version 3.1.5 is known to work.
+
+ <br><dt>GNU binutils<dd>
+Necessary in some circumstances, optional in others. See the
+host/target specific instructions for your platform for the exact
+requirements.
+
+ <br><dt>gzip version 1.2.4 (or later) or<dt>bzip2 version 1.0.2 (or later)<dd>
+Necessary to uncompress GCC <samp><span class="command">tar</span></samp> files when source code is
+obtained via FTP mirror sites.
+
+ <br><dt>GNU make version 3.80 (or later)<dd>
+You must have GNU make installed to build GCC.
+
+ <br><dt>GNU tar version 1.14 (or later)<dd>
+Necessary (only on some platforms) to untar the source code. Many
+systems' <samp><span class="command">tar</span></samp> programs will also work, only try GNU
+<samp><span class="command">tar</span></samp> if you have problems.
+
+ <br><dt>Perl version 5.6.1 (or later)<dd>
+Necessary when targetting Darwin, building &lsquo;<samp><span class="samp">libstdc++</span></samp>&rsquo;,
+and not using <samp><span class="option">--disable-symvers</span></samp>.
+Necessary when targetting Solaris 2 with Sun <samp><span class="command">ld</span></samp> and not using
+<samp><span class="option">--disable-symvers</span></samp>. A helper
+script needs &lsquo;<samp><span class="samp">Glob.pm</span></samp>&rsquo;, which is missing from <samp><span class="command">perl</span></samp> 5.005
+included in Solaris&nbsp;8. The bundled <samp><span class="command">perl</span></samp> in Solaris&nbsp;9 and up
+works.
+
+ <p>Necessary when regenerating <samp><span class="file">Makefile</span></samp> dependencies in libiberty.
+Necessary when regenerating <samp><span class="file">libiberty/functions.texi</span></samp>.
+Necessary when generating manpages from Texinfo manuals.
+Used by various scripts to generate some files included in SVN (mainly
+Unicode-related and rarely changing) from source tables.
+
+ <br><dt><samp><span class="command">jar</span></samp>, or InfoZIP (<samp><span class="command">zip</span></samp> and <samp><span class="command">unzip</span></samp>)<dd>
+Necessary to build libgcj, the GCJ runtime.
+
+</dl>
+
+ <p>Several support libraries are necessary to build GCC, some are required,
+others optional. While any sufficiently new version of required tools
+usually work, library requirements are generally stricter. Newer
+versions may work in some cases, but it's safer to use the exact
+versions documented. We appreciate bug reports about problems with
+newer versions, though.
+
+ <dl>
+<dt>GNU Multiple Precision Library (GMP) version 4.3.2 (or later)<dd>
+Necessary to build GCC. If you do not have it installed in your
+library search path, you will have to configure with the
+<samp><span class="option">--with-gmp</span></samp> configure option. See also <samp><span class="option">--with-gmp-lib</span></samp>
+and <samp><span class="option">--with-gmp-include</span></samp>. Alternatively, if a GMP source
+distribution is found in a subdirectory of your GCC sources named
+<samp><span class="file">gmp</span></samp>, it will be built together with GCC.
+
+ <br><dt>MPFR Library version 2.4.2 (or later)<dd>
+Necessary to build GCC. It can be downloaded from
+<a href="http://www.mpfr.org/">http://www.mpfr.org/</a>. The <samp><span class="option">--with-mpfr</span></samp> configure
+option should be used if your MPFR Library is not installed in your
+default library search path. See also <samp><span class="option">--with-mpfr-lib</span></samp> and
+<samp><span class="option">--with-mpfr-include</span></samp>. Alternatively, if a MPFR source
+distribution is found in a subdirectory of your GCC sources named
+<samp><span class="file">mpfr</span></samp>, it will be built together with GCC.
+
+ <br><dt>MPC Library version 0.8.1 (or later)<dd>
+Necessary to build GCC. It can be downloaded from
+<a href="http://www.multiprecision.org/">http://www.multiprecision.org/</a>. The <samp><span class="option">--with-mpc</span></samp>
+configure option should be used if your MPC Library is not installed
+in your default library search path. See also <samp><span class="option">--with-mpc-lib</span></samp>
+and <samp><span class="option">--with-mpc-include</span></samp>. Alternatively, if an MPC source
+distribution is found in a subdirectory of your GCC sources named
+<samp><span class="file">mpc</span></samp>, it will be built together with GCC.
+
+ <br><dt>Parma Polyhedra Library (PPL) version 0.11<dd>
+Necessary to build GCC with the Graphite loop optimizations.
+It can be downloaded from <a href="http://www.cs.unipr.it/ppl/Download/">http://www.cs.unipr.it/ppl/Download/</a>.
+
+ <p>The <samp><span class="option">--with-ppl</span></samp> configure option should be used if PPL is not
+installed in your default library search path.
+
+ <br><dt>CLooG-PPL version 0.15 or CLooG 0.16<dd>
+Necessary to build GCC with the Graphite loop optimizations. There
+are two versions available. CLooG-PPL 0.15 as well as CLooG 0.16.
+The former is the default right now. It can be downloaded from
+<a href="ftp://gcc.gnu.org/pub/gcc/infrastructure/">ftp://gcc.gnu.org/pub/gcc/infrastructure/</a> as
+<samp><span class="file">cloog-ppl-0.15.tar.gz</span></samp>.
+
+ <p>CLooG 0.16 support is still in testing stage, but will be the
+default in future GCC releases. It is also available at
+<a href="ftp://gcc.gnu.org/pub/gcc/infrastructure/">ftp://gcc.gnu.org/pub/gcc/infrastructure/</a> as
+<samp><span class="file">cloog-0.16.1.tar.gz</span></samp>. To use it add the additional configure
+option <samp><span class="option">--enable-cloog-backend=isl</span></samp>. Even if CLooG 0.16
+does not use PPL, PPL is still required for Graphite.
+
+ <p>In both cases <samp><span class="option">--with-cloog</span></samp> configure option should be used
+if CLooG is not installed in your default library search path.
+
+ </dl>
+
+<h3 class="heading"><a name="TOC1"></a>Tools/packages necessary for modifying GCC</h3>
+
+ <dl>
+<dt>autoconf version 2.64<dt>GNU m4 version 1.4.6 (or later)<dd>
+Necessary when modifying <samp><span class="file">configure.ac</span></samp>, <samp><span class="file">aclocal.m4</span></samp>, etc.
+to regenerate <samp><span class="file">configure</span></samp> and <samp><span class="file">config.in</span></samp> files.
+
+ <br><dt>automake version 1.11.1<dd>
+Necessary when modifying a <samp><span class="file">Makefile.am</span></samp> file to regenerate its
+associated <samp><span class="file">Makefile.in</span></samp>.
+
+ <p>Much of GCC does not use automake, so directly edit the <samp><span class="file">Makefile.in</span></samp>
+file. Specifically this applies to the <samp><span class="file">gcc</span></samp>, <samp><span class="file">intl</span></samp>,
+<samp><span class="file">libcpp</span></samp>, <samp><span class="file">libiberty</span></samp>, <samp><span class="file">libobjc</span></samp> directories as well
+as any of their subdirectories.
+
+ <p>For directories that use automake, GCC requires the latest release in
+the 1.11 series, which is currently 1.11.1. When regenerating a directory
+to a newer version, please update all the directories using an older 1.11
+to the latest released version.
+
+ <br><dt>gettext version 0.14.5 (or later)<dd>
+Needed to regenerate <samp><span class="file">gcc.pot</span></samp>.
+
+ <br><dt>gperf version 2.7.2 (or later)<dd>
+Necessary when modifying <samp><span class="command">gperf</span></samp> input files, e.g.
+<samp><span class="file">gcc/cp/cfns.gperf</span></samp> to regenerate its associated header file, e.g.
+<samp><span class="file">gcc/cp/cfns.h</span></samp>.
+
+ <br><dt>DejaGnu 1.4.4<dt>Expect<dt>Tcl<dd>
+Necessary to run the GCC testsuite; see the section on testing for details.
+
+ <br><dt>autogen version 5.5.4 (or later) and<dt>guile version 1.4.1 (or later)<dd>
+Necessary to regenerate <samp><span class="file">fixinc/fixincl.x</span></samp> from
+<samp><span class="file">fixinc/inclhack.def</span></samp> and <samp><span class="file">fixinc/*.tpl</span></samp>.
+
+ <p>Necessary to run &lsquo;<samp><span class="samp">make check</span></samp>&rsquo; for <samp><span class="file">fixinc</span></samp>.
+
+ <p>Necessary to regenerate the top level <samp><span class="file">Makefile.in</span></samp> file from
+<samp><span class="file">Makefile.tpl</span></samp> and <samp><span class="file">Makefile.def</span></samp>.
+
+ <br><dt>Flex version 2.5.4 (or later)<dd>
+Necessary when modifying <samp><span class="file">*.l</span></samp> files.
+
+ <p>Necessary to build GCC during development because the generated output
+files are not included in the SVN repository. They are included in
+releases.
+
+ <br><dt>Texinfo version 4.7 (or later)<dd>
+Necessary for running <samp><span class="command">makeinfo</span></samp> when modifying <samp><span class="file">*.texi</span></samp>
+files to test your changes.
+
+ <p>Necessary for running <samp><span class="command">make dvi</span></samp> or <samp><span class="command">make pdf</span></samp> to
+create printable documentation in DVI or PDF format. Texinfo version
+4.8 or later is required for <samp><span class="command">make pdf</span></samp>.
+
+ <p>Necessary to build GCC documentation during development because the
+generated output files are not included in the SVN repository. They are
+included in releases.
+
+ <br><dt>TeX (any working version)<dd>
+Necessary for running <samp><span class="command">texi2dvi</span></samp> and <samp><span class="command">texi2pdf</span></samp>, which
+are used when running <samp><span class="command">make dvi</span></samp> or <samp><span class="command">make pdf</span></samp> to create
+DVI or PDF files, respectively.
+
+ <br><dt>SVN (any version)<dt>SSH (any version)<dd>
+Necessary to access the SVN repository. Public releases and weekly
+snapshots of the development sources are also available via FTP.
+
+ <br><dt>GNU diffutils version 2.7 (or later)<dd>
+Useful when submitting patches for the GCC source code.
+
+ <br><dt>patch version 2.5.4 (or later)<dd>
+Necessary when applying patches, created with <samp><span class="command">diff</span></samp>, to one's
+own sources.
+
+ <br><dt>ecj1<dt>gjavah<dd>
+If you wish to modify <samp><span class="file">.java</span></samp> files in libjava, you will need to
+configure with <samp><span class="option">--enable-java-maintainer-mode</span></samp>, and you will need
+to have executables named <samp><span class="command">ecj1</span></samp> and <samp><span class="command">gjavah</span></samp> in your path.
+The <samp><span class="command">ecj1</span></samp> executable should run the Eclipse Java compiler via
+the GCC-specific entry point. You can download a suitable jar from
+<a href="ftp://sourceware.org/pub/java/">ftp://sourceware.org/pub/java/</a>, or by running the script
+<samp><span class="command">contrib/download_ecj</span></samp>.
+
+ <br><dt>antlr.jar version 2.7.1 (or later)<dt>antlr binary<dd>
+If you wish to build the <samp><span class="command">gjdoc</span></samp> binary in libjava, you will
+need to have an <samp><span class="file">antlr.jar</span></samp> library available. The library is
+searched in system locations but can be configured with
+<samp><span class="option">--with-antlr-jar=</span></samp> instead. When configuring with
+<samp><span class="option">--enable-java-maintainer-mode</span></samp>, you will need to have one of
+the executables named <samp><span class="command">cantlr</span></samp>, <samp><span class="command">runantlr</span></samp> or
+<samp><span class="command">antlr</span></samp> in your path.
+
+</dl>
+
+ <p><hr />
+<p><a href="./index.html">Return to the GCC Installation page</a>
+
+<!-- ***Downloading the source************************************************** -->
+<!-- ***Configuration*********************************************************** -->
+<!-- ***Building**************************************************************** -->
+<!-- ***Testing***************************************************************** -->
+<!-- ***Final install*********************************************************** -->
+<!-- ***Binaries**************************************************************** -->
+<!-- ***Specific**************************************************************** -->
+<!-- ***Old documentation****************************************************** -->
+<!-- ***GFDL******************************************************************** -->
+<!-- *************************************************************************** -->
+<!-- Part 6 The End of the Document -->
+</body></html>
+
diff --git a/INSTALL/specific.html b/INSTALL/specific.html
new file mode 100644
index 000000000..11c9bccdd
--- /dev/null
+++ b/INSTALL/specific.html
@@ -0,0 +1,1561 @@
+<html lang="en">
+<head>
+<title>Host/Target specific installation notes for GCC</title>
+<meta http-equiv="Content-Type" content="text/html">
+<meta name="description" content="Host/Target specific installation notes for GCC">
+<meta name="generator" content="makeinfo 4.13">
+<link title="Top" rel="top" href="#Top">
+<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
+<!--
+Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
+1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
+2010 Free Software Foundation, Inc.
+
+ Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, the Front-Cover texts being (a) (see below), and
+with the Back-Cover Texts being (b) (see below). A copy of the
+license is included in the section entitled "GNU Free Documentation License".
+
+(a) The FSF's Front-Cover Text is:
+
+ A GNU Manual
+
+(b) The FSF's Back-Cover Text is:
+
+ You have freedom to copy and modify this GNU Manual, like GNU
+ software. Copies published by the Free Software Foundation raise
+ funds for GNU development.-->
+<meta http-equiv="Content-Style-Type" content="text/css">
+<style type="text/css"><!--
+ pre.display { font-family:inherit }
+ pre.format { font-family:inherit }
+ pre.smalldisplay { font-family:inherit; font-size:smaller }
+ pre.smallformat { font-family:inherit; font-size:smaller }
+ pre.smallexample { font-size:smaller }
+ pre.smalllisp { font-size:smaller }
+ span.sc { font-variant:small-caps }
+ span.roman { font-family:serif; font-weight:normal; }
+ span.sansserif { font-family:sans-serif; font-weight:normal; }
+--></style>
+</head>
+<body>
+<h1 class="settitle">Host/Target specific installation notes for GCC</h1>
+<a name="index-Specific-1"></a><a name="index-Specific-installation-notes-2"></a><a name="index-Target-specific-installation-3"></a><a name="index-Host-specific-installation-4"></a><a name="index-Target-specific-installation-notes-5"></a>
+Please read this document carefully <em>before</em> installing the
+GNU Compiler Collection on your machine.
+
+ <p>Note that this list of install notes is <em>not</em> a list of supported
+hosts or targets. Not all supported hosts and targets are listed
+here, only the ones that require host-specific or target-specific
+information are.
+
+ <ul>
+<li><a href="#alpha-x-x">alpha*-*-*</a>
+<li><a href="#alpha-dec-osf51">alpha*-dec-osf5.1</a>
+<li><a href="#arc-x-elf">arc-*-elf</a>
+<li><a href="#arm-x-elf">arm-*-elf</a>
+<li><a href="#avr">avr</a>
+<li><a href="#bfin">Blackfin</a>
+<li><a href="#dos">DOS</a>
+<li><a href="#x-x-freebsd">*-*-freebsd*</a>
+<li><a href="#h8300-hms">h8300-hms</a>
+<li><a href="#hppa-hp-hpux">hppa*-hp-hpux*</a>
+<li><a href="#hppa-hp-hpux10">hppa*-hp-hpux10</a>
+<li><a href="#hppa-hp-hpux11">hppa*-hp-hpux11</a>
+<li><a href="#x-x-linux-gnu">*-*-linux-gnu</a>
+<li><a href="#ix86-x-linux">i?86-*-linux*</a>
+<li><a href="#ix86-x-solaris289">i?86-*-solaris2.[89]</a>
+<li><a href="#ix86-x-solaris210">i?86-*-solaris2.10</a>
+<li><a href="#ia64-x-linux">ia64-*-linux</a>
+<li><a href="#ia64-x-hpux">ia64-*-hpux*</a>
+<li><a href="#x-ibm-aix">*-ibm-aix*</a>
+<li><a href="#iq2000-x-elf">iq2000-*-elf</a>
+<li><a href="#lm32-x-elf">lm32-*-elf</a>
+<li><a href="#lm32-x-uclinux">lm32-*-uclinux</a>
+<li><a href="#m32c-x-elf">m32c-*-elf</a>
+<li><a href="#m32r-x-elf">m32r-*-elf</a>
+<li><a href="#m6811-elf">m6811-elf</a>
+<li><a href="#m6812-elf">m6812-elf</a>
+<li><a href="#m68k-x-x">m68k-*-*</a>
+<li><a href="#m68k-uclinux">m68k-uclinux</a>
+<li><a href="#mep-x-elf">mep-*-elf</a>
+<li><a href="#microblaze-x-elf">microblaze-*-elf</a>
+<li><a href="#mips-x-x">mips-*-*</a>
+<li><a href="#mips-sgi-irix5">mips-sgi-irix5</a>
+<li><a href="#mips-sgi-irix6">mips-sgi-irix6</a>
+<li><a href="#powerpc-x-x">powerpc*-*-*</a>
+<li><a href="#powerpc-x-darwin">powerpc-*-darwin*</a>
+<li><a href="#powerpc-x-elf">powerpc-*-elf</a>
+<li><a href="#powerpc-x-linux-gnu">powerpc*-*-linux-gnu*</a>
+<li><a href="#powerpc-x-netbsd">powerpc-*-netbsd*</a>
+<li><a href="#powerpc-x-eabisim">powerpc-*-eabisim</a>
+<li><a href="#powerpc-x-eabi">powerpc-*-eabi</a>
+<li><a href="#powerpcle-x-elf">powerpcle-*-elf</a>
+<li><a href="#powerpcle-x-eabisim">powerpcle-*-eabisim</a>
+<li><a href="#powerpcle-x-eabi">powerpcle-*-eabi</a>
+<li><a href="#s390-x-linux">s390-*-linux*</a>
+<li><a href="#s390x-x-linux">s390x-*-linux*</a>
+<li><a href="#s390x-ibm-tpf">s390x-ibm-tpf*</a>
+<li><a href="#x-x-solaris2">*-*-solaris2*</a>
+<li><a href="#sparc-x-x">sparc*-*-*</a>
+<li><a href="#sparc-sun-solaris2">sparc-sun-solaris2*</a>
+<li><a href="#sparc-sun-solaris210">sparc-sun-solaris2.10</a>
+<li><a href="#sparc-x-linux">sparc-*-linux*</a>
+<li><a href="#sparc64-x-solaris2">sparc64-*-solaris2*</a>
+<li><a href="#sparcv9-x-solaris2">sparcv9-*-solaris2*</a>
+<li><a href="#x-x-vxworks">*-*-vxworks*</a>
+<li><a href="#x86-64-x-x">x86_64-*-*</a> amd64-*-*
+<li><a href="#xtensa-x-elf">xtensa*-*-elf</a>
+<li><a href="#xtensa-x-linux">xtensa*-*-linux*</a>
+<li><a href="#windows">Microsoft Windows</a>
+<li><a href="#x-x-cygwin">*-*-cygwin</a>
+<li><a href="#x-x-interix">*-*-interix</a>
+<li><a href="#x-x-mingw32">*-*-mingw32</a>
+<li><a href="#os2">OS/2</a>
+<li><a href="#older">Older systems</a>
+</ul>
+
+ <ul>
+<li><a href="#elf">all ELF targets</a> (SVR4, Solaris 2, etc.)
+</ul>
+
+ <p><!-- -------- host/target specific issues start here ---------------- -->
+<hr />
+
+<h3 class="heading"><a name="TOC0"></a><a name="alpha_002dx_002dx"></a>alpha*-*-*</h3>
+
+<p>This section contains general configuration information for all
+alpha-based platforms using ELF (in particular, ignore this section for
+DEC OSF/1, Digital UNIX and Tru64 UNIX). In addition to reading this
+section, please read all other sections that match your target.
+
+ <p>We require binutils 2.11.2 or newer.
+Previous binutils releases had a number of problems with DWARF 2
+debugging information, not the least of which is incorrect linking of
+shared libraries.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC1"></a><a name="alpha_002ddec_002dosf51"></a>alpha*-dec-osf5.1</h3>
+
+<p>Systems using processors that implement the DEC Alpha architecture and
+are running the DEC/Compaq/HP Unix (DEC OSF/1, Digital UNIX, or Compaq/HP
+Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
+
+ <p>As of GCC 3.2, versions before <code>alpha*-dec-osf4</code> are no longer
+supported. (These are the versions which identify themselves as DEC
+OSF/1.) As of GCC 4.6, support for Tru64 UNIX V4.0 and V5.0 has been
+removed.
+
+ <p>On Tru64 UNIX, virtual memory exhausted bootstrap failures
+may be fixed by reconfiguring Kernel Virtual Memory and Swap parameters
+per the <samp><span class="command">/usr/sbin/sys_check</span></samp> Tuning Suggestions,
+or applying the patch in
+<a href="http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html">http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html</a>. Depending on
+the OS version used, you need a data segment size between 512 MB and
+1 GB, so simply use <samp><span class="command">ulimit -Sd unlimited</span></samp>.
+
+ <p>As of GNU binutils 2.21, neither GNU <samp><span class="command">as</span></samp> nor GNU <samp><span class="command">ld</span></samp>
+are supported on Tru64 UNIX, so you must not configure GCC with
+<samp><span class="option">--with-gnu-as</span></samp> or <samp><span class="option">--with-gnu-ld</span></samp>.
+
+ <p>GCC writes a &lsquo;<samp><span class="samp">.verstamp</span></samp>&rsquo; directive to the assembler output file
+unless it is built as a cross-compiler. It gets the version to use from
+the system header file <samp><span class="file">/usr/include/stamp.h</span></samp>. If you install a
+new version of Tru64 UNIX, you should rebuild GCC to pick up the new version
+stamp.
+
+ <p>GCC now supports both the native (ECOFF) debugging format used by DBX
+and GDB and an encapsulated STABS format for use only with GDB. See the
+discussion of the <samp><span class="option">--with-stabs</span></samp> option of <samp><span class="file">configure</span></samp> above
+for more information on these formats and how to select them.
+<!-- FIXME: does this work at all? If so, perhaps make default. -->
+
+ <p>There is a bug in DEC's assembler that produces incorrect line numbers
+for ECOFF format when the &lsquo;<samp><span class="samp">.align</span></samp>&rsquo; directive is used. To work
+around this problem, GCC will not emit such alignment directives
+while writing ECOFF format debugging information even if optimization is
+being performed. Unfortunately, this has the very undesirable
+side-effect that code addresses when <samp><span class="option">-O</span></samp> is specified are
+different depending on whether or not <samp><span class="option">-g</span></samp> is also specified.
+
+ <p>To avoid this behavior, specify <samp><span class="option">-gstabs+</span></samp> and use GDB instead of
+DBX. DEC is now aware of this problem with the assembler and hopes to
+provide a fix shortly.
+
+<!-- FIXME: still applicable? -->
+ <p><hr />
+
+<h3 class="heading"><a name="TOC2"></a><a name="arc_002dx_002delf"></a>arc-*-elf</h3>
+
+<p>Argonaut ARC processor.
+This configuration is intended for embedded systems.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC3"></a><a name="arm_002dx_002delf"></a>arm-*-elf</h3>
+
+<p>ARM-family processors. Subtargets that use the ELF object format
+require GNU binutils 2.13 or newer. Such subtargets include:
+<code>arm-*-freebsd</code>, <code>arm-*-netbsdelf</code>, <code>arm-*-*linux</code>
+and <code>arm-*-rtems</code>.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC4"></a><a name="avr"></a>avr</h3>
+
+<p>ATMEL AVR-family micro controllers. These are used in embedded
+applications. There are no standard Unix configurations.
+See &ldquo;AVR Options&rdquo; in the main manual
+for the list of supported MCU types.
+
+ <p>Use &lsquo;<samp><span class="samp">configure --target=avr --enable-languages="c"</span></samp>&rsquo; to configure GCC.
+
+ <p>Further installation notes and other useful information about AVR tools
+can also be obtained from:
+
+ <ul>
+<li><a href="http://www.nongnu.org/avr/">http://www.nongnu.org/avr/</a>
+<li><a href="http://www.amelek.gda.pl/avr/">http://www.amelek.gda.pl/avr/</a>
+</ul>
+
+ <p>We <em>strongly</em> recommend using binutils 2.13 or newer.
+
+ <p>The following error:
+<pre class="smallexample"> Error: register required
+</pre>
+ <p>indicates that you should upgrade to a newer version of the binutils.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC5"></a><a name="bfin"></a>Blackfin</h3>
+
+<p>The Blackfin processor, an Analog Devices DSP.
+See &ldquo;Blackfin Options&rdquo; in the main manual
+
+ <p>More information, and a version of binutils with support for this processor,
+is available at <a href="http://blackfin.uclinux.org">http://blackfin.uclinux.org</a>
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC6"></a><a name="cris"></a>CRIS</h3>
+
+<p>CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
+series. These are used in embedded applications.
+
+ <p>See &ldquo;CRIS Options&rdquo; in the main manual
+for a list of CRIS-specific options.
+
+ <p>There are a few different CRIS targets:
+ <dl>
+<dt><code>cris-axis-elf</code><dd>Mainly for monolithic embedded systems. Includes a multilib for the
+&lsquo;<samp><span class="samp">v10</span></samp>&rsquo; core used in &lsquo;<samp><span class="samp">ETRAX 100 LX</span></samp>&rsquo;.
+<br><dt><code>cris-axis-linux-gnu</code><dd>A GNU/Linux port for the CRIS architecture, currently targeting
+&lsquo;<samp><span class="samp">ETRAX 100 LX</span></samp>&rsquo; by default.
+</dl>
+
+ <p>For <code>cris-axis-elf</code> you need binutils 2.11
+or newer. For <code>cris-axis-linux-gnu</code> you need binutils 2.12 or newer.
+
+ <p>Pre-packaged tools can be obtained from
+<a href="ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/">ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/</a>. More
+information about this platform is available at
+<a href="http://developer.axis.com/">http://developer.axis.com/</a>.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC7"></a><a name="crx"></a>CRX</h3>
+
+<p>The CRX CompactRISC architecture is a low-power 32-bit architecture with
+fast context switching and architectural extensibility features.
+
+ <p>See &ldquo;CRX Options&rdquo; in the main manual for a list of CRX-specific options.
+
+ <p>Use &lsquo;<samp><span class="samp">configure --target=crx-elf --enable-languages=c,c++</span></samp>&rsquo; to configure
+GCC for building a CRX cross-compiler. The option &lsquo;<samp><span class="samp">--target=crx-elf</span></samp>&rsquo;
+is also used to build the &lsquo;<samp><span class="samp">newlib</span></samp>&rsquo; C library for CRX.
+
+ <p>It is also possible to build libstdc++-v3 for the CRX architecture. This
+needs to be done in a separate step with the following configure settings:
+
+<pre class="smallexample"> gcc/libstdc++-v3/configure --host=crx-elf --with-newlib \
+ --enable-sjlj-exceptions --enable-cxx-flags='-fexceptions -frtti'
+</pre>
+ <p><hr />
+
+<h3 class="heading"><a name="TOC8"></a><a name="dos"></a>DOS</h3>
+
+<p>Please have a look at the <a href="binaries.html">binaries page</a>.
+
+ <p>You cannot install GCC by itself on MSDOS; it will not compile under
+any MSDOS compiler except itself. You need to get the complete
+compilation package DJGPP, which includes binaries as well as sources,
+and includes all the necessary compilation tools and libraries.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC9"></a><a name="x_002dx_002dfreebsd"></a>*-*-freebsd*</h3>
+
+<p>Support for FreeBSD 1 was discontinued in GCC 3.2. Support for
+FreeBSD 2 (and any mutant a.out variants of FreeBSD 3) was
+discontinued in GCC 4.0.
+
+ <p>In order to better utilize FreeBSD base system functionality and match
+the configuration of the system compiler, GCC 4.5 and above as well as
+GCC 4.4 past 2010-06-20 leverage SSP support in libc (which is present
+on FreeBSD 7 or later) and the use of <code>__cxa_atexit</code> by default
+(on FreeBSD 6 or later). The use of <code>dl_iterate_phdr</code> inside
+<samp><span class="file">libgcc_s.so.1</span></samp> and boehm-gc (on FreeBSD 7 or later) is enabled
+by GCC 4.5 and above.
+
+ <p>We support FreeBSD using the ELF file format with DWARF 2 debugging
+for all CPU architectures. You may use <samp><span class="option">-gstabs</span></samp> instead of
+<samp><span class="option">-g</span></samp>, if you really want the old debugging format. There are
+no known issues with mixing object files and libraries with different
+debugging formats. Otherwise, this release of GCC should now match
+more of the configuration used in the stock FreeBSD configuration of
+GCC. In particular, <samp><span class="option">--enable-threads</span></samp> is now configured by
+default. However, as a general user, do not attempt to replace the
+system compiler with this release. Known to bootstrap and check with
+good results on FreeBSD 7.2-STABLE. In the past, known to bootstrap
+and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4,
+4.5, 4.8, 4.9 and 5-CURRENT.
+
+ <p>The version of binutils installed in <samp><span class="file">/usr/bin</span></samp> probably works
+with this release of GCC. Bootstrapping against the latest GNU
+binutils and/or the version found in <samp><span class="file">/usr/ports/devel/binutils</span></samp> has
+been known to enable additional features and improve overall testsuite
+results. However, it is currently known that boehm-gc (which itself
+is required for java) may not configure properly on FreeBSD prior to
+the FreeBSD 7.0 release with GNU binutils after 2.16.1.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC10"></a><a name="h8300_002dhms"></a>h8300-hms</h3>
+
+<p>Renesas H8/300 series of processors.
+
+ <p>Please have a look at the <a href="binaries.html">binaries page</a>.
+
+ <p>The calling convention and structure layout has changed in release 2.6.
+All code must be recompiled. The calling convention now passes the
+first three arguments in function calls in registers. Structures are no
+longer a multiple of 2 bytes.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC11"></a><a name="hppa_002dhp_002dhpux"></a>hppa*-hp-hpux*</h3>
+
+<p>Support for HP-UX version 9 and older was discontinued in GCC 3.4.
+
+ <p>We require using gas/binutils on all hppa platforms. Version 2.19 or
+later is recommended.
+
+ <p>It may be helpful to configure GCC with the
+<a href="./configure.html#with-gnu-as"><samp><span class="option">--with-gnu-as</span></samp></a> and
+<samp><span class="option">--with-as=...</span></samp> options to ensure that GCC can find GAS.
+
+ <p>The HP assembler should not be used with GCC. It is rarely tested and may
+not work. It shouldn't be used with any languages other than C due to its
+many limitations.
+
+ <p>Specifically, <samp><span class="option">-g</span></samp> does not work (HP-UX uses a peculiar debugging
+format which GCC does not know about). It also inserts timestamps
+into each object file it creates, causing the 3-stage comparison test to
+fail during a bootstrap. You should be able to continue by saying
+&lsquo;<samp><span class="samp">make all-host all-target</span></samp>&rsquo; after getting the failure from &lsquo;<samp><span class="samp">make</span></samp>&rsquo;.
+
+ <p>Various GCC features are not supported. For example, it does not support weak
+symbols or alias definitions. As a result, explicit template instantiations
+are required when using C++. This makes it difficult if not impossible to
+build many C++ applications.
+
+ <p>There are two default scheduling models for instructions. These are
+PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
+architecture specified for the target machine when configuring.
+PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
+the target is a &lsquo;<samp><span class="samp">hppa1*</span></samp>&rsquo; machine.
+
+ <p>The PROCESSOR_8000 model is not well suited to older processors. Thus,
+it is important to completely specify the machine architecture when
+configuring if you want a model other than PROCESSOR_8000. The macro
+TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
+default scheduling model is desired.
+
+ <p>As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10
+through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later.
+This namespace change might cause problems when bootstrapping with
+an earlier version of GCC or the HP compiler as essentially the same
+namespace is required for an entire build. This problem can be avoided
+in a number of ways. With HP cc, <samp><span class="env">UNIX_STD</span></samp> can be set to &lsquo;<samp><span class="samp">95</span></samp>&rsquo;
+or &lsquo;<samp><span class="samp">98</span></samp>&rsquo;. Another way is to add an appropriate set of predefines
+to <samp><span class="env">CC</span></samp>. The description for the <samp><span class="option">munix=</span></samp> option contains
+a list of the predefines used with each standard.
+
+ <p>More specific information to &lsquo;<samp><span class="samp">hppa*-hp-hpux*</span></samp>&rsquo; targets follows.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC12"></a><a name="hppa_002dhp_002dhpux10"></a>hppa*-hp-hpux10</h3>
+
+<p>For hpux10.20, we <em>highly</em> recommend you pick up the latest sed patch
+<code>PHCO_19798</code> from HP.
+
+ <p>The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces are
+used for one-only code and data. This resolves many of the previous
+problems in using C++ on this target. However, the ABI is not compatible
+with the one implemented under HP-UX 11 using secondary definitions.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC13"></a><a name="hppa_002dhp_002dhpux11"></a>hppa*-hp-hpux11</h3>
+
+<p>GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot
+be used to compile GCC 3.0 and up.
+
+ <p>The libffi and libjava libraries haven't been ported to 64-bit HP-UX and don't build.
+
+ <p>Refer to <a href="binaries.html">binaries</a> for information about obtaining
+precompiled GCC binaries for HP-UX. Precompiled binaries must be obtained
+to build the Ada language as it can't be bootstrapped using C. Ada is
+only available for the 32-bit PA-RISC runtime.
+
+ <p>Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The
+bundled compiler supports only traditional C; you will need either HP's
+unbundled compiler, or a binary distribution of GCC.
+
+ <p>It is possible to build GCC 3.3 starting with the bundled HP compiler,
+but the process requires several steps. GCC 3.3 can then be used to
+build later versions. The fastjar program contains ISO C code and
+can't be built with the HP bundled compiler. This problem can be
+avoided by not building the Java language. For example, use the
+<samp><span class="option">--enable-languages="c,c++,f77,objc"</span></samp> option in your configure
+command.
+
+ <p>There are several possible approaches to building the distribution.
+Binutils can be built first using the HP tools. Then, the GCC
+distribution can be built. The second approach is to build GCC
+first using the HP tools, then build binutils, then rebuild GCC.
+There have been problems with various binary distributions, so it
+is best not to start from a binary distribution.
+
+ <p>On 64-bit capable systems, there are two distinct targets. Different
+installation prefixes must be used if both are to be installed on
+the same system. The &lsquo;<samp><span class="samp">hppa[1-2]*-hp-hpux11*</span></samp>&rsquo; target generates code
+for the 32-bit PA-RISC runtime architecture and uses the HP linker.
+The &lsquo;<samp><span class="samp">hppa64-hp-hpux11*</span></samp>&rsquo; target generates 64-bit code for the
+PA-RISC 2.0 architecture.
+
+ <p>The script config.guess now selects the target type based on the compiler
+detected during configuration. You must define <samp><span class="env">PATH</span></samp> or <samp><span class="env">CC</span></samp> so
+that configure finds an appropriate compiler for the initial bootstrap.
+When <samp><span class="env">CC</span></samp> is used, the definition should contain the options that are
+needed whenever <samp><span class="env">CC</span></samp> is used.
+
+ <p>Specifically, options that determine the runtime architecture must be
+in <samp><span class="env">CC</span></samp> to correctly select the target for the build. It is also
+convenient to place many other compiler options in <samp><span class="env">CC</span></samp>. For example,
+<samp><span class="env">CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"</span></samp>
+can be used to bootstrap the GCC 3.3 branch with the HP compiler in
+64-bit K&amp;R/bundled mode. The <samp><span class="option">+DA2.0W</span></samp> option will result in
+the automatic selection of the &lsquo;<samp><span class="samp">hppa64-hp-hpux11*</span></samp>&rsquo; target. The
+macro definition table of cpp needs to be increased for a successful
+build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to
+be defined when building with the bundled compiler, or when using the
+<samp><span class="option">-Ac</span></samp> option. These defines aren't necessary with <samp><span class="option">-Ae</span></samp>.
+
+ <p>It is best to explicitly configure the &lsquo;<samp><span class="samp">hppa64-hp-hpux11*</span></samp>&rsquo; target
+with the <samp><span class="option">--with-ld=...</span></samp> option. This overrides the standard
+search for ld. The two linkers supported on this target require different
+commands. The default linker is determined during configuration. As a
+result, it's not possible to switch linkers in the middle of a GCC build.
+This has been reported to sometimes occur in unified builds of binutils
+and GCC.
+
+ <p>A recent linker patch must be installed for the correct operation of
+GCC 3.3 and later. <code>PHSS_26559</code> and <code>PHSS_24304</code> are the
+oldest linker patches that are known to work. They are for HP-UX
+11.00 and 11.11, respectively. <code>PHSS_24303</code>, the companion to
+<code>PHSS_24304</code>, might be usable but it hasn't been tested. These
+patches have been superseded. Consult the HP patch database to obtain
+the currently recommended linker patch for your system.
+
+ <p>The patches are necessary for the support of weak symbols on the
+32-bit port, and for the running of initializers and finalizers. Weak
+symbols are implemented using SOM secondary definition symbols. Prior
+to HP-UX 11, there are bugs in the linker support for secondary symbols.
+The patches correct a problem of linker core dumps creating shared
+libraries containing secondary symbols, as well as various other
+linking issues involving secondary symbols.
+
+ <p>GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
+run initializers and finalizers on the 64-bit port. The 32-bit port
+uses the linker <samp><span class="option">+init</span></samp> and <samp><span class="option">+fini</span></samp> options for the same
+purpose. The patches correct various problems with the +init/+fini
+options, including program core dumps. Binutils 2.14 corrects a
+problem on the 64-bit port resulting from HP's non-standard use of
+the .init and .fini sections for array initializers and finalizers.
+
+ <p>Although the HP and GNU linkers are both supported for the
+&lsquo;<samp><span class="samp">hppa64-hp-hpux11*</span></samp>&rsquo; target, it is strongly recommended that the
+HP linker be used for link editing on this target.
+
+ <p>At this time, the GNU linker does not support the creation of long
+branch stubs. As a result, it can't successfully link binaries
+containing branch offsets larger than 8 megabytes. In addition,
+there are problems linking shared libraries, linking executables
+with <samp><span class="option">-static</span></samp>, and with dwarf2 unwind and exception support.
+It also doesn't provide stubs for internal calls to global functions
+in shared libraries, so these calls can't be overloaded.
+
+ <p>The HP dynamic loader does not support GNU symbol versioning, so symbol
+versioning is not supported. It may be necessary to disable symbol
+versioning with <samp><span class="option">--disable-symvers</span></samp> when using GNU ld.
+
+ <p>POSIX threads are the default. The optional DCE thread library is not
+supported, so <samp><span class="option">--enable-threads=dce</span></samp> does not work.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC14"></a><a name="x_002dx_002dlinux_002dgnu"></a>*-*-linux-gnu</h3>
+
+<p>Versions of libstdc++-v3 starting with 3.2.1 require bug fixes present
+in glibc 2.2.5 and later. More information is available in the
+libstdc++-v3 documentation.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC15"></a><a name="ix86_002dx_002dlinux"></a>i?86-*-linux*</h3>
+
+<p>As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
+See <a href="http://gcc.gnu.org/PR10877">bug 10877</a> for more information.
+
+ <p>If you receive Signal 11 errors when building on GNU/Linux, then it is
+possible you have a hardware problem. Further information on this can be
+found on <a href="http://www.bitwizard.nl/sig11/">www.bitwizard.nl</a>.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC16"></a><a name="ix86_002dx_002dsolaris289"></a>i?86-*-solaris2.[89]</h3>
+
+<p>The Sun assembler in Solaris 8 and 9 has several bugs and limitations.
+While GCC works around them, several features are missing, so it is
+<!-- FIXME: which ones? -->
+recommended to use the GNU assembler instead. There is no bundled
+version, but the current version, from GNU binutils 2.21, is known to
+work.
+
+ <p>Solaris&nbsp;2/x86 doesn't support the execution of SSE/SSE2 instructions
+before Solaris&nbsp;9 4/04, even if the CPU supports them. Programs will
+receive <code>SIGILL</code> if they try. The fix is available both in
+Solaris&nbsp;9 Update&nbsp;6 and kernel patch 112234-12 or newer. There is no
+corresponding patch for Solaris 8. To avoid this problem,
+<samp><span class="option">-march</span></samp> defaults to &lsquo;<samp><span class="samp">pentiumpro</span></samp>&rsquo; on Solaris 8 and 9. If
+you have the patch installed, you can configure GCC with an appropriate
+<samp><span class="option">--with-arch</span></samp> option, but need GNU <samp><span class="command">as</span></samp> for SSE2 support.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC17"></a><a name="ix86_002dx_002dsolaris210"></a>i?86-*-solaris2.10</h3>
+
+<p>Use this for Solaris 10 or later on x86 and x86-64 systems. This
+configuration is supported by GCC 4.0 and later versions only. Unlike
+&lsquo;<samp><span class="samp">sparcv9-sun-solaris2*</span></samp>&rsquo;, there is no corresponding 64-bit
+configuration like &lsquo;<samp><span class="samp">amd64-*-solaris2*</span></samp>&rsquo; or &lsquo;<samp><span class="samp">x86_64-*-solaris2*</span></samp>&rsquo;.
+<!-- FIXME: will there ever be? -->
+
+ <p>It is recommended that you configure GCC to use the GNU assembler, in
+<samp><span class="file">/usr/sfw/bin/gas</span></samp>. The versions included in Solaris 10, from GNU
+binutils 2.15, and Solaris 11, from GNU binutils 2.19, work fine,
+although the current version, from GNU binutils
+2.21, is known to work, too. Recent versions of the Sun assembler in
+<samp><span class="file">/usr/ccs/bin/as</span></samp> work almost as well, though.
+<!-- FIXME: as patch requirements? -->
+
+ <p>For linking, the Sun linker, is preferred. If you want to use the GNU
+linker instead, which is available in <samp><span class="file">/usr/sfw/bin/gld</span></samp>, note that
+due to a packaging bug the version in Solaris 10, from GNU binutils
+2.15, cannot be used, while the version in Solaris 11, from GNU binutils
+2.19, works, as does the latest version, from GNU binutils 2.21.
+
+ <p>To use GNU <samp><span class="command">as</span></samp>, configure with the options
+<samp><span class="option">--with-gnu-as --with-as=/usr/sfw/bin/gas</span></samp>. It may be necessary
+to configure with <samp><span class="option">--without-gnu-ld --with-ld=/usr/ccs/bin/ld</span></samp> to
+guarantee use of Sun <samp><span class="command">ld</span></samp>.
+<!-- FIXME: why -without-gnu-ld -with-ld? -->
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC18"></a><a name="ia64_002dx_002dlinux"></a>ia64-*-linux</h3>
+
+<p>IA-64 processor (also known as IPF, or Itanium Processor Family)
+running GNU/Linux.
+
+ <p>If you are using the installed system libunwind library with
+<samp><span class="option">--with-system-libunwind</span></samp>, then you must use libunwind 0.98 or
+later.
+
+ <p>None of the following versions of GCC has an ABI that is compatible
+with any of the other versions in this list, with the exception that
+Red Hat 2.96 and Trillian 000171 are compatible with each other:
+3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
+This primarily affects C++ programs and programs that create shared libraries.
+GCC 3.1 or later is recommended for compiling linux, the kernel.
+As of version 3.1 GCC is believed to be fully ABI compliant, and hence no
+more major ABI changes are expected.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC19"></a><a name="ia64_002dx_002dhpux"></a>ia64-*-hpux*</h3>
+
+<p>Building GCC on this target requires the GNU Assembler. The bundled HP
+assembler will not work. To prevent GCC from using the wrong assembler,
+the option <samp><span class="option">--with-gnu-as</span></samp> may be necessary.
+
+ <p>The GCC libunwind library has not been ported to HPUX. This means that for
+GCC versions 3.2.3 and earlier, <samp><span class="option">--enable-libunwind-exceptions</span></samp>
+is required to build GCC. For GCC 3.3 and later, this is the default.
+For gcc 3.4.3 and later, <samp><span class="option">--enable-libunwind-exceptions</span></samp> is
+removed and the system libunwind library will always be used.
+
+ <p><hr />
+<!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
+
+<h3 class="heading"><a name="TOC20"></a><a name="x_002dibm_002daix"></a>*-ibm-aix*</h3>
+
+<p>Support for AIX version 3 and older was discontinued in GCC 3.4.
+Support for AIX version 4.2 and older was discontinued in GCC 4.5.
+
+ <p>&ldquo;out of memory&rdquo; bootstrap failures may indicate a problem with
+process resource limits (ulimit). Hard limits are configured in the
+<samp><span class="file">/etc/security/limits</span></samp> system configuration file.
+
+ <p>GCC can bootstrap with recent versions of IBM XLC, but bootstrapping
+with an earlier release of GCC is recommended. Bootstrapping with XLC
+requires a larger data segment, which can be enabled through the
+<var>LDR_CNTRL</var> environment variable, e.g.,
+
+<pre class="smallexample"> % LDR_CNTRL=MAXDATA=0x50000000
+ % export LDR_CNTRL
+</pre>
+ <p>One can start with a pre-compiled version of GCC to build from
+sources. One may delete GCC's &ldquo;fixed&rdquo; header files when starting
+with a version of GCC built for an earlier release of AIX.
+
+ <p>To speed up the configuration phases of bootstrapping and installing GCC,
+one may use GNU Bash instead of AIX <samp><span class="command">/bin/sh</span></samp>, e.g.,
+
+<pre class="smallexample"> % CONFIG_SHELL=/opt/freeware/bin/bash
+ % export CONFIG_SHELL
+</pre>
+ <p>and then proceed as described in <a href="build.html">the build instructions</a>, where we strongly recommend specifying an absolute path
+to invoke <var>srcdir</var>/configure.
+
+ <p>Because GCC on AIX is built as a 32-bit executable by default,
+(although it can generate 64-bit programs) the GMP and MPFR libraries
+required by gfortran must be 32-bit libraries. Building GMP and MPFR
+as static archive libraries works better than shared libraries.
+
+ <p>Errors involving <code>alloca</code> when building GCC generally are due
+to an incorrect definition of <code>CC</code> in the Makefile or mixing files
+compiled with the native C compiler and GCC. During the stage1 phase of
+the build, the native AIX compiler <strong>must</strong> be invoked as <samp><span class="command">cc</span></samp>
+(not <samp><span class="command">xlc</span></samp>). Once <samp><span class="command">configure</span></samp> has been informed of
+<samp><span class="command">xlc</span></samp>, one needs to use &lsquo;<samp><span class="samp">make distclean</span></samp>&rsquo; to remove the
+configure cache files and ensure that <samp><span class="env">CC</span></samp> environment variable
+does not provide a definition that will confuse <samp><span class="command">configure</span></samp>.
+If this error occurs during stage2 or later, then the problem most likely
+is the version of Make (see above).
+
+ <p>The native <samp><span class="command">as</span></samp> and <samp><span class="command">ld</span></samp> are recommended for bootstrapping
+on AIX. The GNU Assembler, GNU Linker, and GNU Binutils version 2.20
+is required to bootstrap on AIX 5. The native AIX tools do
+interoperate with GCC.
+
+ <p>Building <samp><span class="file">libstdc++.a</span></samp> requires a fix for an AIX Assembler bug
+APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a
+fix for another AIX Assembler bug and a co-dependent AIX Archiver fix
+referenced as APAR IY53606 (AIX 5.2) or as APAR IY54774 (AIX 5.1)
+
+ <p>&lsquo;<samp><span class="samp">libstdc++</span></samp>&rsquo; in GCC 3.4 increments the major version number of the
+shared object and GCC installation places the <samp><span class="file">libstdc++.a</span></samp>
+shared library in a common location which will overwrite the and GCC
+3.3 version of the shared library. Applications either need to be
+re-linked against the new shared library or the GCC 3.1 and GCC 3.3
+versions of the &lsquo;<samp><span class="samp">libstdc++</span></samp>&rsquo; shared object needs to be available
+to the AIX runtime loader. The GCC 3.1 &lsquo;<samp><span class="samp">libstdc++.so.4</span></samp>&rsquo;, if
+present, and GCC 3.3 &lsquo;<samp><span class="samp">libstdc++.so.5</span></samp>&rsquo; shared objects can be
+installed for runtime dynamic loading using the following steps to set
+the &lsquo;<samp><span class="samp">F_LOADONLY</span></samp>&rsquo; flag in the shared object for <em>each</em>
+multilib <samp><span class="file">libstdc++.a</span></samp> installed:
+
+ <p>Extract the shared objects from the currently installed
+<samp><span class="file">libstdc++.a</span></samp> archive:
+<pre class="smallexample"> % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
+</pre>
+ <p>Enable the &lsquo;<samp><span class="samp">F_LOADONLY</span></samp>&rsquo; flag so that the shared object will be
+available for runtime dynamic loading, but not linking:
+<pre class="smallexample"> % strip -e libstdc++.so.4 libstdc++.so.5
+</pre>
+ <p>Archive the runtime-only shared object in the GCC 3.4
+<samp><span class="file">libstdc++.a</span></samp> archive:
+<pre class="smallexample"> % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
+</pre>
+ <p>Linking executables and shared libraries may produce warnings of
+duplicate symbols. The assembly files generated by GCC for AIX always
+have included multiple symbol definitions for certain global variable
+and function declarations in the original program. The warnings should
+not prevent the linker from producing a correct library or runnable
+executable.
+
+ <p>AIX 4.3 utilizes a &ldquo;large format&rdquo; archive to support both 32-bit and
+64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
+to parse archive libraries did not handle the new format correctly.
+These routines are used by GCC and result in error messages during
+linking such as &ldquo;not a COFF file&rdquo;. The version of the routines shipped
+with AIX 4.3.1 should work for a 32-bit environment. The <samp><span class="option">-g</span></samp>
+option of the archive command may be used to create archives of 32-bit
+objects using the original &ldquo;small format&rdquo;. A correct version of the
+routines is shipped with AIX 4.3.2 and above.
+
+ <p>Some versions of the AIX binder (linker) can fail with a relocation
+overflow severe error when the <samp><span class="option">-bbigtoc</span></samp> option is used to link
+GCC-produced object files into an executable that overflows the TOC. A fix
+for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
+available from IBM Customer Support and from its
+<a href="http://techsupport.services.ibm.com/">techsupport.services.ibm.com</a>
+website as PTF U455193.
+
+ <p>The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
+with a segmentation fault when invoked by any version of GCC. A fix for
+APAR IX87327 is available from IBM Customer Support and from its
+<a href="http://techsupport.services.ibm.com/">techsupport.services.ibm.com</a>
+website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
+
+ <p>The initial assembler shipped with AIX 4.3.0 generates incorrect object
+files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
+TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
+<a href="http://techsupport.services.ibm.com/">techsupport.services.ibm.com</a>
+website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
+
+ <p>AIX provides National Language Support (NLS). Compilers and assemblers
+use NLS to support locale-specific representations of various data
+formats including floating-point numbers (e.g., &lsquo;<samp><span class="samp">.</span></samp>&rsquo; vs &lsquo;<samp><span class="samp">,</span></samp>&rsquo; for
+separating decimal fractions). There have been problems reported where
+GCC does not produce the same floating-point formats that the assembler
+expects. If one encounters this problem, set the <samp><span class="env">LANG</span></samp>
+environment variable to &lsquo;<samp><span class="samp">C</span></samp>&rsquo; or &lsquo;<samp><span class="samp">En_US</span></samp>&rsquo;.
+
+ <p>A default can be specified with the <samp><span class="option">-mcpu=</span><var>cpu_type</var></samp>
+switch and using the configure option <samp><span class="option">--with-cpu-</span><var>cpu_type</var></samp>.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC21"></a><a name="iq2000_002dx_002delf"></a>iq2000-*-elf</h3>
+
+<p>Vitesse IQ2000 processors. These are used in embedded
+applications. There are no standard Unix configurations.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC22"></a><a name="lm32_002dx_002delf"></a>lm32-*-elf</h3>
+
+<p>Lattice Mico32 processor.
+This configuration is intended for embedded systems.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC23"></a><a name="lm32_002dx_002duclinux"></a>lm32-*-uclinux</h3>
+
+<p>Lattice Mico32 processor.
+This configuration is intended for embedded systems running uClinux.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC24"></a><a name="m32c_002dx_002delf"></a>m32c-*-elf</h3>
+
+<p>Renesas M32C processor.
+This configuration is intended for embedded systems.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC25"></a><a name="m32r_002dx_002delf"></a>m32r-*-elf</h3>
+
+<p>Renesas M32R processor.
+This configuration is intended for embedded systems.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC26"></a><a name="m6811_002delf"></a>m6811-elf</h3>
+
+<p>Motorola 68HC11 family micro controllers. These are used in embedded
+applications. There are no standard Unix configurations.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC27"></a><a name="m6812_002delf"></a>m6812-elf</h3>
+
+<p>Motorola 68HC12 family micro controllers. These are used in embedded
+applications. There are no standard Unix configurations.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC28"></a><a name="m68k_002dx_002dx"></a>m68k-*-*</h3>
+
+<p>By default,
+&lsquo;<samp><span class="samp">m68k-*-elf*</span></samp>&rsquo;, &lsquo;<samp><span class="samp">m68k-*-rtems</span></samp>&rsquo;, &lsquo;<samp><span class="samp">m68k-*-uclinux</span></samp>&rsquo; and
+&lsquo;<samp><span class="samp">m68k-*-linux</span></samp>&rsquo;
+build libraries for both M680x0 and ColdFire processors. If you only
+need the M680x0 libraries, you can omit the ColdFire ones by passing
+<samp><span class="option">--with-arch=m68k</span></samp> to <samp><span class="command">configure</span></samp>. Alternatively, you
+can omit the M680x0 libraries by passing <samp><span class="option">--with-arch=cf</span></samp> to
+<samp><span class="command">configure</span></samp>. These targets default to 5206 or 5475 code as
+appropriate for the target system when
+configured with <samp><span class="option">--with-arch=cf</span></samp> and 68020 code otherwise.
+
+ <p>The &lsquo;<samp><span class="samp">m68k-*-netbsd</span></samp>&rsquo; and
+&lsquo;<samp><span class="samp">m68k-*-openbsd</span></samp>&rsquo; targets also support the <samp><span class="option">--with-arch</span></samp>
+option. They will generate ColdFire CFV4e code when configured with
+<samp><span class="option">--with-arch=cf</span></samp> and 68020 code otherwise.
+
+ <p>You can override the default processors listed above by configuring
+with <samp><span class="option">--with-cpu=</span><var>target</var></samp>. This <var>target</var> can either
+be a <samp><span class="option">-mcpu</span></samp> argument or one of the following values:
+&lsquo;<samp><span class="samp">m68000</span></samp>&rsquo;, &lsquo;<samp><span class="samp">m68010</span></samp>&rsquo;, &lsquo;<samp><span class="samp">m68020</span></samp>&rsquo;, &lsquo;<samp><span class="samp">m68030</span></samp>&rsquo;,
+&lsquo;<samp><span class="samp">m68040</span></samp>&rsquo;, &lsquo;<samp><span class="samp">m68060</span></samp>&rsquo;, &lsquo;<samp><span class="samp">m68020-40</span></samp>&rsquo; and &lsquo;<samp><span class="samp">m68020-60</span></samp>&rsquo;.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC29"></a><a name="m68k_002dx_002duclinux"></a>m68k-*-uclinux</h3>
+
+<p>GCC 4.3 changed the uClinux configuration so that it uses the
+&lsquo;<samp><span class="samp">m68k-linux-gnu</span></samp>&rsquo; ABI rather than the &lsquo;<samp><span class="samp">m68k-elf</span></samp>&rsquo; ABI.
+It also added improved support for C++ and flat shared libraries,
+both of which were ABI changes. However, you can still use the
+original ABI by configuring for &lsquo;<samp><span class="samp">m68k-uclinuxoldabi</span></samp>&rsquo; or
+&lsquo;<samp><span class="samp">m68k-</span><var>vendor</var><span class="samp">-uclinuxoldabi</span></samp>&rsquo;.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC30"></a><a name="mep_002dx_002delf"></a>mep-*-elf</h3>
+
+<p>Toshiba Media embedded Processor.
+This configuration is intended for embedded systems.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC31"></a><a name="microblaze_002dx_002delf"></a>microblaze-*-elf</h3>
+
+<p>Xilinx MicroBlaze processor.
+This configuration is intended for embedded systems.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC32"></a><a name="mips_002dx_002dx"></a>mips-*-*</h3>
+
+<p>If on a MIPS system you get an error message saying &ldquo;does not have gp
+sections for all it's [sic] sectons [sic]&rdquo;, don't worry about it. This
+happens whenever you use GAS with the MIPS linker, but there is not
+really anything wrong, and it is okay to use the output file. You can
+stop such warnings by installing the GNU linker.
+
+ <p>It would be nice to extend GAS to produce the gp tables, but they are
+optional, and there should not be a warning about their absence.
+
+ <p>The libstdc++ atomic locking routines for MIPS targets requires MIPS II
+and later. A patch went in just after the GCC 3.3 release to
+make &lsquo;<samp><span class="samp">mips*-*-*</span></samp>&rsquo; use the generic implementation instead. You can also
+configure for &lsquo;<samp><span class="samp">mipsel-elf</span></samp>&rsquo; as a workaround. The
+&lsquo;<samp><span class="samp">mips*-*-linux*</span></samp>&rsquo; target continues to use the MIPS II routines. More
+work on this is expected in future releases.
+
+<!-- If you make -with-llsc the default for another target, please also -->
+<!-- update the description of the -with-llsc option. -->
+ <p>The built-in <code>__sync_*</code> functions are available on MIPS II and
+later systems and others that support the &lsquo;<samp><span class="samp">ll</span></samp>&rsquo;, &lsquo;<samp><span class="samp">sc</span></samp>&rsquo; and
+&lsquo;<samp><span class="samp">sync</span></samp>&rsquo; instructions. This can be overridden by passing
+<samp><span class="option">--with-llsc</span></samp> or <samp><span class="option">--without-llsc</span></samp> when configuring GCC.
+Since the Linux kernel emulates these instructions if they are
+missing, the default for &lsquo;<samp><span class="samp">mips*-*-linux*</span></samp>&rsquo; targets is
+<samp><span class="option">--with-llsc</span></samp>. The <samp><span class="option">--with-llsc</span></samp> and
+<samp><span class="option">--without-llsc</span></samp> configure options may be overridden at compile
+time by passing the <samp><span class="option">-mllsc</span></samp> or <samp><span class="option">-mno-llsc</span></samp> options to
+the compiler.
+
+ <p>MIPS systems check for division by zero (unless
+<samp><span class="option">-mno-check-zero-division</span></samp> is passed to the compiler) by
+generating either a conditional trap or a break instruction. Using
+trap results in smaller code, but is only supported on MIPS II and
+later. Also, some versions of the Linux kernel have a bug that
+prevents trap from generating the proper signal (<code>SIGFPE</code>). To enable
+the use of break, use the <samp><span class="option">--with-divide=breaks</span></samp>
+<samp><span class="command">configure</span></samp> option when configuring GCC. The default is to
+use traps on systems that support them.
+
+ <p>Cross-compilers for the MIPS as target using the MIPS assembler
+currently do not work, because the auxiliary programs
+<samp><span class="file">mips-tdump.c</span></samp> and <samp><span class="file">mips-tfile.c</span></samp> can't be compiled on
+anything but a MIPS. It does work to cross compile for a MIPS
+if you use the GNU assembler and linker.
+
+ <p>The assembler from GNU binutils 2.17 and earlier has a bug in the way
+it sorts relocations for REL targets (o32, o64, EABI). This can cause
+bad code to be generated for simple C++ programs. Also the linker
+from GNU binutils versions prior to 2.17 has a bug which causes the
+runtime linker stubs in very large programs, like <samp><span class="file">libgcj.so</span></samp>, to
+be incorrectly generated. GNU Binutils 2.18 and later (and snapshots
+made after Nov. 9, 2006) should be free from both of these problems.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC33"></a><a name="mips_002dsgi_002dirix5"></a>mips-sgi-irix5</h3>
+
+<p>Support for IRIX 5 has been removed in GCC 4.6.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC34"></a><a name="mips_002dsgi_002dirix6"></a>mips-sgi-irix6</h3>
+
+<p>Support for IRIX 6 releases before 6.5 has been removed in GCC 4.6, as
+well as support for
+the O32 ABI. It is <em>strongly</em> recommended to upgrade to at least
+IRIX 6.5.18. This release introduced full ISO C99 support, though for
+the N32 and N64 ABIs only.
+
+ <p>To build and use GCC on IRIX 6.5, you need the IRIX Development Foundation
+(IDF) and IRIX Development Libraries (IDL). They are included with the
+IRIX 6.5 media.
+
+ <p>If you are using SGI's MIPSpro <samp><span class="command">cc</span></samp> as your bootstrap compiler, you must
+ensure that the N32 ABI is in use. To test this, compile a simple C
+file with <samp><span class="command">cc</span></samp> and then run <samp><span class="command">file</span></samp> on the
+resulting object file. The output should look like:
+
+<pre class="smallexample"> test.o: ELF N32 MSB ...
+</pre>
+ <p class="noindent">If you see:
+
+<pre class="smallexample"> test.o: ELF 32-bit MSB ...
+</pre>
+ <p class="noindent">or
+
+<pre class="smallexample"> test.o: ELF 64-bit MSB ...
+</pre>
+ <p class="noindent">then your version of <samp><span class="command">cc</span></samp> uses the O32 or N64 ABI by default. You
+should set the environment variable <samp><span class="env">CC</span></samp> to &lsquo;<samp><span class="samp">cc -n32</span></samp>&rsquo;
+before configuring GCC.
+
+ <p>If you want the resulting <samp><span class="command">gcc</span></samp> to run on old 32-bit systems
+with the MIPS R4400 CPU, you need to ensure that only code for the &lsquo;<samp><span class="samp">mips3</span></samp>&rsquo;
+instruction set architecture (ISA) is generated. While GCC 3.x does
+this correctly, both GCC 2.95 and SGI's MIPSpro <samp><span class="command">cc</span></samp> may change
+the ISA depending on the machine where GCC is built. Using one of them
+as the bootstrap compiler may result in &lsquo;<samp><span class="samp">mips4</span></samp>&rsquo; code, which won't run at
+all on &lsquo;<samp><span class="samp">mips3</span></samp>&rsquo;-only systems. For the test program above, you should see:
+
+<pre class="smallexample"> test.o: ELF N32 MSB mips-3 ...
+</pre>
+ <p class="noindent">If you get:
+
+<pre class="smallexample"> test.o: ELF N32 MSB mips-4 ...
+</pre>
+ <p class="noindent">instead, you should set the environment variable <samp><span class="env">CC</span></samp> to &lsquo;<samp><span class="samp">cc
+-n32 -mips3</span></samp>&rsquo; or &lsquo;<samp><span class="samp">gcc -mips3</span></samp>&rsquo; respectively before configuring GCC.
+
+ <p>MIPSpro C 7.4 may cause bootstrap failures, due to a bug when inlining
+<code>memcmp</code>. Either add <code>-U__INLINE_INTRINSICS</code> to the <samp><span class="env">CC</span></samp>
+environment variable as a workaround or upgrade to MIPSpro C 7.4.1m.
+
+ <p>GCC on IRIX 6.5 is usually built to support the N32 and N64 ABIs. If
+you build GCC on a system that doesn't have the N64 libraries installed
+or cannot run 64-bit binaries,
+you need to configure with <samp><span class="option">--disable-multilib</span></samp> so GCC doesn't
+try to use them.
+Look for <samp><span class="file">/usr/lib64/libc.so.1</span></samp> to see if you
+have the 64-bit libraries installed.
+
+ <p>GCC must be configured with GNU <samp><span class="command">as</span></samp>. The latest version, from GNU
+binutils 2.21, is known to work. On the other hand, bootstrap fails
+with GNU <samp><span class="command">ld</span></samp> at least since GNU binutils 2.17.
+
+ <p>The <samp><span class="option">--enable-libgcj</span></samp>
+option is disabled by default: IRIX 6 uses a very low default limit
+(20480) for the command line length. Although <samp><span class="command">libtool</span></samp> contains a
+workaround for this problem, at least the N64 &lsquo;<samp><span class="samp">libgcj</span></samp>&rsquo; is known not
+to build despite this, running into an internal error of the native
+<samp><span class="command">ld</span></samp>. A sure fix is to increase this limit (&lsquo;<samp><span class="samp">ncargs</span></samp>&rsquo;) to
+its maximum of 262144 bytes. If you have root access, you can use the
+<samp><span class="command">systune</span></samp> command to do this.
+<!-- FIXME: does this work with current libtool? -->
+
+ <p><code>wchar_t</code> support in &lsquo;<samp><span class="samp">libstdc++</span></samp>&rsquo; is not available for old
+IRIX 6.5.x releases, x &lt; 19. The problem cannot be autodetected
+and in order to build GCC for such targets you need to configure with
+<samp><span class="option">--disable-wchar_t</span></samp>.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC35"></a><a name="moxie_002dx_002delf"></a>moxie-*-elf</h3>
+
+<p>The moxie processor. See <a href="http://moxielogic.org/">http://moxielogic.org/</a> for more
+information about this processor.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC36"></a><a name="powerpc_002dx_002dx"></a>powerpc-*-*</h3>
+
+<p>You can specify a default version for the <samp><span class="option">-mcpu=</span><var>cpu_type</var></samp>
+switch by using the configure option <samp><span class="option">--with-cpu-</span><var>cpu_type</var></samp>.
+
+ <p>You will need
+<a href="ftp://ftp.kernel.org/pub/linux/devel/binutils">binutils 2.15</a>
+or newer for a working GCC.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC37"></a><a name="powerpc_002dx_002ddarwin"></a>powerpc-*-darwin*</h3>
+
+<p>PowerPC running Darwin (Mac OS X kernel).
+
+ <p>Pre-installed versions of Mac OS X may not include any developer tools,
+meaning that you will not be able to build GCC from source. Tool
+binaries are available at
+<a href="http://opensource.apple.com/">http://opensource.apple.com/</a>.
+
+ <p>This version of GCC requires at least cctools-590.36. The
+cctools-590.36 package referenced from
+<a href="http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html">http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html</a> will not work
+on systems older than 10.3.9 (aka darwin7.9.0).
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC38"></a><a name="powerpc_002dx_002delf"></a>powerpc-*-elf</h3>
+
+<p>PowerPC system in big endian mode, running System V.4.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC39"></a><a name="powerpc_002dx_002dlinux_002dgnu"></a>powerpc*-*-linux-gnu*</h3>
+
+<p>PowerPC system in big endian mode running Linux.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC40"></a><a name="powerpc_002dx_002dnetbsd"></a>powerpc-*-netbsd*</h3>
+
+<p>PowerPC system in big endian mode running NetBSD.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC41"></a><a name="powerpc_002dx_002deabisim"></a>powerpc-*-eabisim</h3>
+
+<p>Embedded PowerPC system in big endian mode for use in running under the
+PSIM simulator.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC42"></a><a name="powerpc_002dx_002deabi"></a>powerpc-*-eabi</h3>
+
+<p>Embedded PowerPC system in big endian mode.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC43"></a><a name="powerpcle_002dx_002delf"></a>powerpcle-*-elf</h3>
+
+<p>PowerPC system in little endian mode, running System V.4.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC44"></a><a name="powerpcle_002dx_002deabisim"></a>powerpcle-*-eabisim</h3>
+
+<p>Embedded PowerPC system in little endian mode for use in running under
+the PSIM simulator.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC45"></a><a name="powerpcle_002dx_002deabi"></a>powerpcle-*-eabi</h3>
+
+<p>Embedded PowerPC system in little endian mode.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC46"></a><a name="rx_002dx_002delf"></a>rx-*-elf</h3>
+
+<p>The Renesas RX processor. See
+<a href="http://eu.renesas.com/fmwk.jsp?cnt=rx600_series_landing.jsp&amp;fp=/products/mpumcu/rx_family/rx600_series">http://eu.renesas.com/fmwk.jsp?cnt=rx600_series_landing.jsp&amp;fp=/products/mpumcu/rx_family/rx600_series</a>
+for more information about this processor.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC47"></a><a name="s390_002dx_002dlinux"></a>s390-*-linux*</h3>
+
+<p>S/390 system running GNU/Linux for S/390.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC48"></a><a name="s390x_002dx_002dlinux"></a>s390x-*-linux*</h3>
+
+<p>zSeries system (64-bit) running GNU/Linux for zSeries.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC49"></a><a name="s390x_002dibm_002dtpf"></a>s390x-ibm-tpf*</h3>
+
+<p>zSeries system (64-bit) running TPF. This platform is
+supported as cross-compilation target only.
+
+ <p><hr /><!-- Please use Solaris 2 to refer to all release of Solaris, starting -->
+<!-- with 2.0 until 2.6, 7, 8, etc. Solaris 1 was a marketing name for -->
+<!-- SunOS 4 releases which we don't use to avoid confusion. Solaris -->
+<!-- alone is too unspecific and must be avoided. -->
+
+<h3 class="heading"><a name="TOC50"></a><a name="x_002dx_002dsolaris2"></a>*-*-solaris2*</h3>
+
+<p>Support for Solaris 7 has been removed in GCC 4.6.
+
+ <p>Sun does not ship a C compiler with Solaris 2, though you can download
+the Sun Studio compilers for free. Alternatively,
+you can install a pre-built GCC to bootstrap and install GCC. See the
+<a href="binaries.html">binaries page</a> for details.
+
+ <p>The Solaris 2 <samp><span class="command">/bin/sh</span></samp> will often fail to configure
+&lsquo;<samp><span class="samp">libstdc++-v3</span></samp>&rsquo;, &lsquo;<samp><span class="samp">boehm-gc</span></samp>&rsquo; or &lsquo;<samp><span class="samp">libjava</span></samp>&rsquo;. We therefore
+recommend using the following initial sequence of commands
+
+<pre class="smallexample"> % CONFIG_SHELL=/bin/ksh
+ % export CONFIG_SHELL
+</pre>
+ <p class="noindent">and proceed as described in <a href="configure.html">the configure instructions</a>.
+In addition we strongly recommend specifying an absolute path to invoke
+<samp><var>srcdir</var><span class="command">/configure</span></samp>.
+
+ <p>Solaris 2 comes with a number of optional OS packages. Some of these
+are needed to use GCC fully, namely <code>SUNWarc</code>,
+<code>SUNWbtool</code>, <code>SUNWesu</code>, <code>SUNWhea</code>, <code>SUNWlibm</code>,
+<code>SUNWsprot</code>, and <code>SUNWtoo</code>. If you did not install all
+optional packages when installing Solaris 2, you will need to verify that
+the packages that GCC needs are installed.
+
+ <p>To check whether an optional package is installed, use
+the <samp><span class="command">pkginfo</span></samp> command. To add an optional package, use the
+<samp><span class="command">pkgadd</span></samp> command. For further details, see the Solaris 2
+documentation.
+
+ <p>Trying to use the linker and other tools in
+<samp><span class="file">/usr/ucb</span></samp> to install GCC has been observed to cause trouble.
+For example, the linker may hang indefinitely. The fix is to remove
+<samp><span class="file">/usr/ucb</span></samp> from your <samp><span class="env">PATH</span></samp>.
+
+ <p>The build process works more smoothly with the legacy Sun tools so, if you
+have <samp><span class="file">/usr/xpg4/bin</span></samp> in your <samp><span class="env">PATH</span></samp>, we recommend that you place
+<samp><span class="file">/usr/bin</span></samp> before <samp><span class="file">/usr/xpg4/bin</span></samp> for the duration of the build.
+
+ <p>We recommend the use of the Sun assembler or the GNU assembler, in
+conjunction with the Sun linker. The GNU <samp><span class="command">as</span></samp>
+versions included in Solaris 10, from GNU binutils 2.15, and Solaris 11,
+from GNU binutils 2.19, are known to work. They can be found in
+<samp><span class="file">/usr/sfw/bin/gas</span></samp>. Current versions of GNU binutils (2.21)
+are known to work as well. Note that your mileage may vary
+if you use a combination of the GNU tools and the Sun tools: while the
+combination GNU <samp><span class="command">as</span></samp> + Sun <samp><span class="command">ld</span></samp> should reasonably work,
+the reverse combination Sun <samp><span class="command">as</span></samp> + GNU <samp><span class="command">ld</span></samp> is known to
+cause memory corruption at runtime in some cases for C++ programs.
+<!-- FIXME: still? -->
+GNU <samp><span class="command">ld</span></samp> usually works as well, although the version included in
+Solaris 10 cannot be used due to several bugs. Again, the current
+version (2.21) is known to work, but generally lacks platform specific
+features, so better stay with Sun <samp><span class="command">ld</span></samp>.
+
+ <p>To enable symbol versioning in &lsquo;<samp><span class="samp">libstdc++</span></samp>&rsquo; with Sun <samp><span class="command">ld</span></samp>,
+you need to have any version of GNU <samp><span class="command">c++filt</span></samp>, which is part of
+GNU binutils. &lsquo;<samp><span class="samp">libstdc++</span></samp>&rsquo; symbol versioning will be disabled if no
+appropriate version is found. Sun <samp><span class="command">c++filt</span></samp> from the Sun Studio
+compilers does <em>not</em> work.
+
+ <p>Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
+newer: <samp><span class="command">g++</span></samp> will complain that types are missing. These headers
+assume that omitting the type means <code>int</code>; this assumption worked for
+C90 but is wrong for C++, and is now wrong for C99 also.
+
+ <p><samp><span class="command">g++</span></samp> accepts such (invalid) constructs with the option
+<samp><span class="option">-fpermissive</span></samp>; it will assume that any missing type is <code>int</code>
+(as defined by C90).
+
+ <p>There are patches for Solaris 8 (108652-24 or newer for SPARC,
+108653-22 for Intel) that fix this bug.
+
+ <p>Sun bug 4927647 sometimes causes random spurious testsuite failures
+related to missing diagnostic output. This bug doesn't affect GCC
+itself, rather it is a kernel bug triggered by the <samp><span class="command">expect</span></samp>
+program which is used only by the GCC testsuite driver. When the bug
+causes the <samp><span class="command">expect</span></samp> program to miss anticipated output, extra
+testsuite failures appear.
+
+ <p>There are patches for Solaris 8 (117350-12 or newer for SPARC,
+117351-12 or newer for Intel) and Solaris 9 (117171-11 or newer for
+SPARC, 117172-11 or newer for Intel) that address this problem.
+
+ <p>Solaris&nbsp;8 provides an alternate implementation of the thread libraries,
+&lsquo;<samp><span class="samp">libpthread</span></samp>&rsquo; and &lsquo;<samp><span class="samp">libthread</span></samp>&rsquo;. They are required for TLS
+support and have been made the default in Solaris&nbsp;9, so they are always
+used on Solaris&nbsp;8.
+
+ <p>Thread-local storage (TLS) is supported in Solaris&nbsp;8 and 9, but requires
+some patches. The &lsquo;<samp><span class="samp">libthread</span></samp>&rsquo; patches provide the
+<code>__tls_get_addr</code> (SPARC, 64-bit x86) resp. <code>___tls_get_addr</code>
+(32-bit x86) functions. On Solaris&nbsp;8, you need 108993-26 or newer on
+SPARC, 108994-26 or newer on Intel. On Solaris&nbsp;9, the necessary support
+on SPARC is present since FCS, while 114432-05 or newer is required on
+Intel. Additionally, on Solaris&nbsp;8, patch 109147-14 or newer on SPARC or
+109148-22 or newer on Intel are required for the Sun <samp><span class="command">ld</span></samp> and
+runtime linker (<samp><span class="command">ld.so.1</span></samp>) support. Again, Solaris&nbsp;9/SPARC
+works since FCS, while 113986-02 is required on Intel. The linker
+patches must be installed even if GNU <samp><span class="command">ld</span></samp> is used. Sun
+<samp><span class="command">as</span></samp> in Solaris&nbsp;8 and 9 doesn't support the necessary
+relocations, so GNU <samp><span class="command">as</span></samp> must be used. The <samp><span class="command">configure</span></samp>
+script checks for those prerequisites and automatically enables TLS
+support if they are met. Although those minimal patch versions should
+work, it is recommended to use the latest patch versions which include
+additional bug fixes.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC51"></a><a name="sparc_002dx_002dx"></a>sparc*-*-*</h3>
+
+<p>This section contains general configuration information for all
+SPARC-based platforms. In addition to reading this section, please
+read all other sections that match your target.
+
+ <p>Newer versions of the GNU Multiple Precision Library (GMP), the MPFR
+library and the MPC library are known to be miscompiled by earlier
+versions of GCC on these platforms. We therefore recommend the use
+of the exact versions of these libraries listed as minimal versions
+in <a href="prerequisites.html">the prerequisites</a>.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC52"></a><a name="sparc_002dsun_002dsolaris2"></a>sparc-sun-solaris2*</h3>
+
+<p>When GCC is configured to use GNU binutils 2.14 or later, the binaries
+produced are smaller than the ones produced using Sun's native tools;
+this difference is quite significant for binaries containing debugging
+information.
+
+ <p>Starting with Solaris 7, the operating system is capable of executing
+64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
+this; the <samp><span class="option">-m64</span></samp> option enables 64-bit code generation.
+However, if all you want is code tuned for the UltraSPARC CPU, you
+should try the <samp><span class="option">-mtune=ultrasparc</span></samp> option instead, which produces
+code that, unlike full 64-bit code, can still run on non-UltraSPARC
+machines.
+
+ <p>When configuring on a Solaris 7 or later system that is running a kernel
+that supports only 32-bit binaries, one must configure with
+<samp><span class="option">--disable-multilib</span></samp>, since we will not be able to build the
+64-bit target libraries.
+
+ <p>GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of
+the GNU compiler (especially GCC 3.0.x versions), which lead to the
+miscompilation of the stage1 compiler and the subsequent failure of the
+bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary
+stage, i.e. to bootstrap that compiler with the base compiler and then
+use it to bootstrap the final compiler.
+
+ <p>GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE Studio 7)
+and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a bootstrap
+failure in form of a miscompilation of the stage1 compiler by the Sun
+compiler. This is Sun bug 4974440. This is fixed with patch 112760-07.
+
+ <p>GCC 3.4 changed the default debugging format from Stabs to DWARF-2 for
+32-bit code on Solaris 7 and later. If you use the Sun assembler, this
+change apparently runs afoul of Sun bug 4910101 (which is referenced as
+an x86-only problem by Sun, probably because they do not use DWARF-2).
+A symptom of the problem is that you cannot compile C++ programs like
+<samp><span class="command">groff</span></samp> 1.19.1 without getting messages similar to the following:
+
+<pre class="smallexample"> ld: warning: relocation error: R_SPARC_UA32: ...
+ external symbolic relocation against non-allocatable section
+ .debug_info cannot be processed at runtime: relocation ignored.
+</pre>
+ <p class="noindent">To work around this problem, compile with <samp><span class="option">-gstabs+</span></samp> instead of
+plain <samp><span class="option">-g</span></samp>.
+
+ <p>When configuring the GNU Multiple Precision Library (GMP), the MPFR
+library or the MPC library on a Solaris 7 or later system, the canonical
+target triplet must be specified as the <samp><span class="command">build</span></samp> parameter on the
+configure line. This target triplet can be obtained by invoking <samp><span class="command">./config.guess</span></samp> in the toplevel source directory of GCC (and
+not that of GMP or MPFR or MPC). For example on a Solaris 9 system:
+
+<pre class="smallexample"> % ./configure --build=sparc-sun-solaris2.9 --prefix=xxx
+</pre>
+ <p><hr />
+
+<h3 class="heading"><a name="TOC53"></a><a name="sparc_002dsun_002dsolaris210"></a>sparc-sun-solaris2.10</h3>
+
+<p>There is a bug in older versions of the Sun assembler which breaks
+thread-local storage (TLS). A typical error message is
+
+<pre class="smallexample"> ld: fatal: relocation error: R_SPARC_TLS_LE_HIX22: file /var/tmp//ccamPA1v.o:
+ symbol &lt;unknown&gt;: bad symbol type SECT: symbol type must be TLS
+</pre>
+ <p class="noindent">This bug is fixed in Sun patch 118683-03 or later.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC54"></a><a name="sparc_002dx_002dlinux"></a>sparc-*-linux*</h3>
+
+<p>GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
+or newer on this platform. All earlier binutils and glibc
+releases mishandled unaligned relocations on <code>sparc-*-*</code> targets.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC55"></a><a name="sparc64_002dx_002dsolaris2"></a>sparc64-*-solaris2*</h3>
+
+<p>When configuring the GNU Multiple Precision Library (GMP), the MPFR
+library or the MPC library, the canonical target triplet must be specified
+as the <samp><span class="command">build</span></samp> parameter on the configure line. For example
+on a Solaris 9 system:
+
+<pre class="smallexample"> % ./configure --build=sparc64-sun-solaris2.9 --prefix=xxx
+</pre>
+ <p>The following compiler flags must be specified in the configure
+step in order to bootstrap this target with the Sun compiler:
+
+<pre class="smallexample"> % CC="cc -xarch=v9 -xildoff" <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>]
+</pre>
+ <p class="noindent"><samp><span class="option">-xarch=v9</span></samp> specifies the SPARC-V9 architecture to the Sun toolchain
+and <samp><span class="option">-xildoff</span></samp> turns off the incremental linker.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC56"></a><a name="sparcv9_002dx_002dsolaris2"></a>sparcv9-*-solaris2*</h3>
+
+<p>This is a synonym for &lsquo;<samp><span class="samp">sparc64-*-solaris2*</span></samp>&rsquo;.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC57"></a><a name="x_002dx_002dvxworks"></a>*-*-vxworks*</h3>
+
+<p>Support for VxWorks is in flux. At present GCC supports <em>only</em> the
+very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC.
+We welcome patches for other architectures supported by VxWorks 5.5.
+Support for VxWorks AE would also be welcome; we believe this is merely
+a matter of writing an appropriate &ldquo;configlette&rdquo; (see below). We are
+not interested in supporting older, a.out or COFF-based, versions of
+VxWorks in GCC 3.
+
+ <p>VxWorks comes with an older version of GCC installed in
+<samp><var>$WIND_BASE</var><span class="file">/host</span></samp>; we recommend you do not overwrite it.
+Choose an installation <var>prefix</var> entirely outside <var>$WIND_BASE</var>.
+Before running <samp><span class="command">configure</span></samp>, create the directories <samp><var>prefix</var></samp>
+and <samp><var>prefix</var><span class="file">/bin</span></samp>. Link or copy the appropriate assembler,
+linker, etc. into <samp><var>prefix</var><span class="file">/bin</span></samp>, and set your <var>PATH</var> to
+include that directory while running both <samp><span class="command">configure</span></samp> and
+<samp><span class="command">make</span></samp>.
+
+ <p>You must give <samp><span class="command">configure</span></samp> the
+<samp><span class="option">--with-headers=</span><var>$WIND_BASE</var><span class="option">/target/h</span></samp> switch so that it can
+find the VxWorks system headers. Since VxWorks is a cross compilation
+target only, you must also specify <samp><span class="option">--target=</span><var>target</var></samp>.
+<samp><span class="command">configure</span></samp> will attempt to create the directory
+<samp><var>prefix</var><span class="file">/</span><var>target</var><span class="file">/sys-include</span></samp> and copy files into it;
+make sure the user running <samp><span class="command">configure</span></samp> has sufficient privilege
+to do so.
+
+ <p>GCC's exception handling runtime requires a special &ldquo;configlette&rdquo;
+module, <samp><span class="file">contrib/gthr_supp_vxw_5x.c</span></samp>. Follow the instructions in
+that file to add the module to your kernel build. (Future versions of
+VxWorks will incorporate this module.)
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC58"></a><a name="x86_002d64_002dx_002dx"></a>x86_64-*-*, amd64-*-*</h3>
+
+<p>GCC supports the x86-64 architecture implemented by the AMD64 processor
+(amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD.
+On GNU/Linux the default is a bi-arch compiler which is able to generate
+both 64-bit x86-64 and 32-bit x86 code (via the <samp><span class="option">-m32</span></samp> switch).
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC59"></a><a name="xtensa_002dx_002delf"></a>xtensa*-*-elf</h3>
+
+<p>This target is intended for embedded Xtensa systems using the
+&lsquo;<samp><span class="samp">newlib</span></samp>&rsquo; C library. It uses ELF but does not support shared
+objects. Designed-defined instructions specified via the
+Tensilica Instruction Extension (TIE) language are only supported
+through inline assembly.
+
+ <p>The Xtensa configuration information must be specified prior to
+building GCC. The <samp><span class="file">include/xtensa-config.h</span></samp> header
+file contains the configuration information. If you created your
+own Xtensa configuration with the Xtensa Processor Generator, the
+downloaded files include a customized copy of this header file,
+which you can use to replace the default header file.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC60"></a><a name="xtensa_002dx_002dlinux"></a>xtensa*-*-linux*</h3>
+
+<p>This target is for Xtensa systems running GNU/Linux. It supports ELF
+shared objects and the GNU C library (glibc). It also generates
+position-independent code (PIC) regardless of whether the
+<samp><span class="option">-fpic</span></samp> or <samp><span class="option">-fPIC</span></samp> options are used. In other
+respects, this target is the same as the
+<a href="#xtensa*-*-elf">&lsquo;<samp><span class="samp">xtensa*-*-elf</span></samp>&rsquo;</a> target.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC61"></a><a name="windows"></a>Microsoft Windows</h3>
+
+<h4 class="subheading"><a name="TOC62"></a>Intel 16-bit versions</h4>
+
+<p>The 16-bit versions of Microsoft Windows, such as Windows 3.1, are not
+supported.
+
+ <p>However, the 32-bit port has limited support for Microsoft
+Windows 3.11 in the Win32s environment, as a target only. See below.
+
+<h4 class="subheading"><a name="TOC63"></a>Intel 32-bit versions</h4>
+
+<p>The 32-bit versions of Windows, including Windows 95, Windows NT, Windows
+XP, and Windows Vista, are supported by several different target
+platforms. These targets differ in which Windows subsystem they target
+and which C libraries are used.
+
+ <ul>
+<li>Cygwin <a href="#x-x-cygwin">*-*-cygwin</a>: Cygwin provides a user-space
+Linux API emulation layer in the Win32 subsystem.
+<li>Interix <a href="#x-x-interix">*-*-interix</a>: The Interix subsystem
+provides native support for POSIX.
+<li>MinGW <a href="#x-x-mingw32">*-*-mingw32</a>: MinGW is a native GCC port for
+the Win32 subsystem that provides a subset of POSIX.
+<li>MKS i386-pc-mks: NuTCracker from MKS. See
+<a href="http://www.mkssoftware.com/">http://www.mkssoftware.com/</a> for more information.
+</ul>
+
+<h4 class="subheading"><a name="TOC64"></a>Intel 64-bit versions</h4>
+
+<p>GCC contains support for x86-64 using the mingw-w64
+runtime library, available from <a href="http://mingw-w64.sourceforge.net/">http://mingw-w64.sourceforge.net/</a>.
+This library should be used with the target triple x86_64-pc-mingw32.
+
+ <p>Presently Windows for Itanium is not supported.
+
+<h4 class="subheading"><a name="TOC65"></a>Windows CE</h4>
+
+<p>Windows CE is supported as a target only on ARM (arm-wince-pe), Hitachi
+SuperH (sh-wince-pe), and MIPS (mips-wince-pe).
+
+<h4 class="subheading"><a name="TOC66"></a>Other Windows Platforms</h4>
+
+<p>GCC no longer supports Windows NT on the Alpha or PowerPC.
+
+ <p>GCC no longer supports the Windows POSIX subsystem. However, it does
+support the Interix subsystem. See above.
+
+ <p>Old target names including *-*-winnt and *-*-windowsnt are no longer used.
+
+ <p>PW32 (i386-pc-pw32) support was never completed, and the project seems to
+be inactive. See <a href="http://pw32.sourceforge.net/">http://pw32.sourceforge.net/</a> for more information.
+
+ <p>UWIN support has been removed due to a lack of maintenance.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC67"></a><a name="x_002dx_002dcygwin"></a>*-*-cygwin</h3>
+
+<p>Ports of GCC are included with the
+<a href="http://www.cygwin.com/">Cygwin environment</a>.
+
+ <p>GCC will build under Cygwin without modification; it does not build
+with Microsoft's C++ compiler and there are no plans to make it do so.
+
+ <p>The Cygwin native compiler can be configured to target any 32-bit x86
+cpu architecture desired; the default is i686-pc-cygwin. It should be
+used with as up-to-date a version of binutils as possible; use either
+the latest official GNU binutils release in the Cygwin distribution,
+or version 2.20 or above if building your own.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC68"></a><a name="x_002dx_002dinterix"></a>*-*-interix</h3>
+
+<p>The Interix target is used by OpenNT, Interix, Services For UNIX (SFU),
+and Subsystem for UNIX-based Applications (SUA). Applications compiled
+with this target run in the Interix subsystem, which is separate from
+the Win32 subsystem. This target was last known to work in GCC 3.3.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC69"></a><a name="x_002dx_002dmingw32"></a>*-*-mingw32</h3>
+
+<p>GCC will build with and support only MinGW runtime 3.12 and later.
+Earlier versions of headers are incompatible with the new default semantics
+of <code>extern inline</code> in <code>-std=c99</code> and <code>-std=gnu99</code> modes.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC70"></a><a name="older"></a>Older systems</h3>
+
+<p>GCC contains support files for many older (1980s and early
+1990s) Unix variants. For the most part, support for these systems
+has not been deliberately removed, but it has not been maintained for
+several years and may suffer from bitrot.
+
+ <p>Starting with GCC 3.1, each release has a list of &ldquo;obsoleted&rdquo; systems.
+Support for these systems is still present in that release, but
+<samp><span class="command">configure</span></samp> will fail unless the <samp><span class="option">--enable-obsolete</span></samp>
+option is given. Unless a maintainer steps forward, support for these
+systems will be removed from the next release of GCC.
+
+ <p>Support for old systems as hosts for GCC can cause problems if the
+workarounds for compiler, library and operating system bugs affect the
+cleanliness or maintainability of the rest of GCC. In some cases, to
+bring GCC up on such a system, if still possible with current GCC, may
+require first installing an old version of GCC which did work on that
+system, and using it to compile a more recent GCC, to avoid bugs in the
+vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
+<samp><span class="file">old-releases</span></samp> directory on the <a href="../mirrors.html">GCC mirror sites</a>. Header bugs may generally be avoided using
+<samp><span class="command">fixincludes</span></samp>, but bugs or deficiencies in libraries and the
+operating system may still cause problems.
+
+ <p>Support for older systems as targets for cross-compilation is less
+problematic than support for them as hosts for GCC; if an enthusiast
+wishes to make such a target work again (including resurrecting any of
+the targets that never worked with GCC 2, starting from the last
+version before they were removed), patches
+<a href="../contribute.html">following the usual requirements</a> would be
+likely to be accepted, since they should not affect the support for more
+modern targets.
+
+ <p>For some systems, old versions of GNU binutils may also be useful,
+and are available from <samp><span class="file">pub/binutils/old-releases</span></samp> on
+<a href="http://sourceware.org/mirrors.html">sourceware.org mirror sites</a>.
+
+ <p>Some of the information on specific systems above relates to
+such older systems, but much of the information
+about GCC on such systems (which may no longer be applicable to
+current GCC) is to be found in the GCC texinfo manual.
+
+ <p><hr />
+
+<h3 class="heading"><a name="TOC71"></a><a name="elf"></a>all ELF targets (SVR4, Solaris 2, etc.)</h3>
+
+<p>C++ support is significantly better on ELF targets if you use the
+<a href="./configure.html#with-gnu-ld">GNU linker</a>; duplicate copies of
+inlines, vtables and template instantiations will be discarded
+automatically.
+
+ <p><hr />
+<p><a href="./index.html">Return to the GCC Installation page</a>
+
+<!-- ***Old documentation****************************************************** -->
+<!-- ***GFDL******************************************************************** -->
+<!-- *************************************************************************** -->
+<!-- Part 6 The End of the Document -->
+</body></html>
+
diff --git a/INSTALL/test.html b/INSTALL/test.html
new file mode 100644
index 000000000..ce8556bd6
--- /dev/null
+++ b/INSTALL/test.html
@@ -0,0 +1,233 @@
+<html lang="en">
+<head>
+<title>Installing GCC: Testing</title>
+<meta http-equiv="Content-Type" content="text/html">
+<meta name="description" content="Installing GCC: Testing">
+<meta name="generator" content="makeinfo 4.13">
+<link title="Top" rel="top" href="#Top">
+<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
+<!--
+Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
+1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
+2010 Free Software Foundation, Inc.
+
+ Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, the Front-Cover texts being (a) (see below), and
+with the Back-Cover Texts being (b) (see below). A copy of the
+license is included in the section entitled "GNU Free Documentation License".
+
+(a) The FSF's Front-Cover Text is:
+
+ A GNU Manual
+
+(b) The FSF's Back-Cover Text is:
+
+ You have freedom to copy and modify this GNU Manual, like GNU
+ software. Copies published by the Free Software Foundation raise
+ funds for GNU development.-->
+<meta http-equiv="Content-Style-Type" content="text/css">
+<style type="text/css"><!--
+ pre.display { font-family:inherit }
+ pre.format { font-family:inherit }
+ pre.smalldisplay { font-family:inherit; font-size:smaller }
+ pre.smallformat { font-family:inherit; font-size:smaller }
+ pre.smallexample { font-size:smaller }
+ pre.smalllisp { font-size:smaller }
+ span.sc { font-variant:small-caps }
+ span.roman { font-family:serif; font-weight:normal; }
+ span.sansserif { font-family:sans-serif; font-weight:normal; }
+--></style>
+</head>
+<body>
+<h1 class="settitle">Installing GCC: Testing</h1>
+<a name="index-Testing-1"></a><a name="index-Installing-GCC_003a-Testing-2"></a><a name="index-Testsuite-3"></a>
+Before you install GCC, we encourage you to run the testsuites and to
+compare your results with results from a similar configuration that have
+been submitted to the
+<a href="http://gcc.gnu.org/ml/gcc-testresults/">gcc-testresults mailing list</a>.
+Some of these archived results are linked from the build status lists
+at <a href="http://gcc.gnu.org/buildstat.html">http://gcc.gnu.org/buildstat.html</a>, although not everyone who
+reports a successful build runs the testsuites and submits the results.
+This step is optional and may require you to download additional software,
+but it can give you confidence in your new GCC installation or point out
+problems before you install and start using your new GCC.
+
+ <p>First, you must have <a href="download.html">downloaded the testsuites</a>.
+These are part of the full distribution, but if you downloaded the
+&ldquo;core&rdquo; compiler plus any front ends, you must download the testsuites
+separately.
+
+ <p>Second, you must have the testing tools installed. This includes
+<a href="http://www.gnu.org/software/dejagnu/">DejaGnu</a>, Tcl, and Expect;
+the DejaGnu site has links to these.
+
+ <p>If the directories where <samp><span class="command">runtest</span></samp> and <samp><span class="command">expect</span></samp> were
+installed are not in the <samp><span class="env">PATH</span></samp>, you may need to set the following
+environment variables appropriately, as in the following example (which
+assumes that DejaGnu has been installed under <samp><span class="file">/usr/local</span></samp>):
+
+<pre class="smallexample"> TCL_LIBRARY = /usr/local/share/tcl8.0
+ DEJAGNULIBS = /usr/local/share/dejagnu
+</pre>
+ <p>(On systems such as Cygwin, these paths are required to be actual
+paths, not mounts or links; presumably this is due to some lack of
+portability in the DejaGnu code.)
+
+ <p>Finally, you can run the testsuite (which may take a long time):
+<pre class="smallexample"> cd <var>objdir</var>; make -k check
+</pre>
+ <p>This will test various components of GCC, such as compiler
+front ends and runtime libraries. While running the testsuite, DejaGnu
+might emit some harmless messages resembling
+&lsquo;<samp><span class="samp">WARNING: Couldn't find the global config file.</span></samp>&rsquo; or
+&lsquo;<samp><span class="samp">WARNING: Couldn't find tool init file</span></samp>&rsquo; that can be ignored.
+
+ <p>If you are testing a cross-compiler, you may want to run the testsuite
+on a simulator as described at <a href="http://gcc.gnu.org/simtest-howto.html">http://gcc.gnu.org/simtest-howto.html</a>.
+
+<h3 class="section"><a name="TOC0"></a>How can you run the testsuite on selected tests?</h3>
+
+<p>In order to run sets of tests selectively, there are targets
+&lsquo;<samp><span class="samp">make check-gcc</span></samp>&rsquo; and &lsquo;<samp><span class="samp">make check-g++</span></samp>&rsquo;
+in the <samp><span class="file">gcc</span></samp> subdirectory of the object directory. You can also
+just run &lsquo;<samp><span class="samp">make check</span></samp>&rsquo; in a subdirectory of the object directory.
+
+ <p>A more selective way to just run all <samp><span class="command">gcc</span></samp> execute tests in the
+testsuite is to use
+
+<pre class="smallexample"> make check-gcc RUNTESTFLAGS="execute.exp <var>other-options</var>"
+</pre>
+ <p>Likewise, in order to run only the <samp><span class="command">g++</span></samp> &ldquo;old-deja&rdquo; tests in
+the testsuite with filenames matching &lsquo;<samp><span class="samp">9805*</span></samp>&rsquo;, you would use
+
+<pre class="smallexample"> make check-g++ RUNTESTFLAGS="old-deja.exp=9805* <var>other-options</var>"
+</pre>
+ <p>The <samp><span class="file">*.exp</span></samp> files are located in the testsuite directories of the GCC
+source, the most important ones being <samp><span class="file">compile.exp</span></samp>,
+<samp><span class="file">execute.exp</span></samp>, <samp><span class="file">dg.exp</span></samp> and <samp><span class="file">old-deja.exp</span></samp>.
+To get a list of the possible <samp><span class="file">*.exp</span></samp> files, pipe the
+output of &lsquo;<samp><span class="samp">make check</span></samp>&rsquo; into a file and look at the
+&lsquo;<samp><span class="samp">Running ... .exp</span></samp>&rsquo; lines.
+
+<h3 class="section"><a name="TOC1"></a>Passing options and running multiple testsuites</h3>
+
+<p>You can pass multiple options to the testsuite using the
+&lsquo;<samp><span class="samp">--target_board</span></samp>&rsquo; option of DejaGNU, either passed as part of
+&lsquo;<samp><span class="samp">RUNTESTFLAGS</span></samp>&rsquo;, or directly to <samp><span class="command">runtest</span></samp> if you prefer to
+work outside the makefiles. For example,
+
+<pre class="smallexample"> make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fmerge-constants"
+</pre>
+ <p>will run the standard <samp><span class="command">g++</span></samp> testsuites (&ldquo;unix&rdquo; is the target name
+for a standard native testsuite situation), passing
+&lsquo;<samp><span class="samp">-O3 -fmerge-constants</span></samp>&rsquo; to the compiler on every test, i.e.,
+slashes separate options.
+
+ <p>You can run the testsuites multiple times using combinations of options
+with a syntax similar to the brace expansion of popular shells:
+
+<pre class="smallexample"> ..."--target_board=arm-sim\{-mhard-float,-msoft-float\}\{-O1,-O2,-O3,\}"
+</pre>
+ <p>(Note the empty option caused by the trailing comma in the final group.)
+The following will run each testsuite eight times using the &lsquo;<samp><span class="samp">arm-sim</span></samp>&rsquo;
+target, as if you had specified all possible combinations yourself:
+
+<pre class="smallexample"> --target_board=arm-sim/-mhard-float/-O1
+ --target_board=arm-sim/-mhard-float/-O2
+ --target_board=arm-sim/-mhard-float/-O3
+ --target_board=arm-sim/-mhard-float
+ --target_board=arm-sim/-msoft-float/-O1
+ --target_board=arm-sim/-msoft-float/-O2
+ --target_board=arm-sim/-msoft-float/-O3
+ --target_board=arm-sim/-msoft-float
+</pre>
+ <p>They can be combined as many times as you wish, in arbitrary ways. This
+list:
+
+<pre class="smallexample"> ..."--target_board=unix/-Wextra\{-O3,-fno-strength\}\{-fomit-frame,\}"
+</pre>
+ <p>will generate four combinations, all involving &lsquo;<samp><span class="samp">-Wextra</span></samp>&rsquo;.
+
+ <p>The disadvantage to this method is that the testsuites are run in serial,
+which is a waste on multiprocessor systems. For users with GNU Make and
+a shell which performs brace expansion, you can run the testsuites in
+parallel by having the shell perform the combinations and <samp><span class="command">make</span></samp>
+do the parallel runs. Instead of using &lsquo;<samp><span class="samp">--target_board</span></samp>&rsquo;, use a
+special makefile target:
+
+<pre class="smallexample"> make -j<var>N</var> check-<var>testsuite</var>//<var>test-target</var>/<var>option1</var>/<var>option2</var>/...
+</pre>
+ <p>For example,
+
+<pre class="smallexample"> make -j3 check-gcc//sh-hms-sim/{-m1,-m2,-m3,-m3e,-m4}/{,-nofpu}
+</pre>
+ <p>will run three concurrent &ldquo;make-gcc&rdquo; testsuites, eventually testing all
+ten combinations as described above. Note that this is currently only
+supported in the <samp><span class="file">gcc</span></samp> subdirectory. (To see how this works, try
+typing <samp><span class="command">echo</span></samp> before the example given here.)
+
+<h3 class="section"><a name="TOC2"></a>Additional testing for Java Class Libraries</h3>
+
+<p>The Java runtime tests can be executed via &lsquo;<samp><span class="samp">make check</span></samp>&rsquo;
+in the <samp><var>target</var><span class="file">/libjava/testsuite</span></samp> directory in
+the build tree.
+
+ <p>The <a href="http://sourceware.org/mauve/">Mauve Project</a> provides
+a suite of tests for the Java Class Libraries. This suite can be run
+as part of libgcj testing by placing the Mauve tree within the libjava
+testsuite at <samp><span class="file">libjava/testsuite/libjava.mauve/mauve</span></samp>, or by
+specifying the location of that tree when invoking &lsquo;<samp><span class="samp">make</span></samp>&rsquo;, as in
+&lsquo;<samp><span class="samp">make MAUVEDIR=~/mauve check</span></samp>&rsquo;.
+
+<h3 class="section"><a name="TOC3"></a>How to interpret test results</h3>
+
+<p>The result of running the testsuite are various <samp><span class="file">*.sum</span></samp> and <samp><span class="file">*.log</span></samp>
+files in the testsuite subdirectories. The <samp><span class="file">*.log</span></samp> files contain a
+detailed log of the compiler invocations and the corresponding
+results, the <samp><span class="file">*.sum</span></samp> files summarize the results. These summaries
+contain status codes for all tests:
+
+ <ul>
+<li>PASS: the test passed as expected
+<li>XPASS: the test unexpectedly passed
+<li>FAIL: the test unexpectedly failed
+<li>XFAIL: the test failed as expected
+<li>UNSUPPORTED: the test is not supported on this platform
+<li>ERROR: the testsuite detected an error
+<li>WARNING: the testsuite detected a possible problem
+</ul>
+
+ <p>It is normal for some tests to report unexpected failures. At the
+current time the testing harness does not allow fine grained control
+over whether or not a test is expected to fail. This problem should
+be fixed in future releases.
+
+<h3 class="section"><a name="TOC4"></a>Submitting test results</h3>
+
+<p>If you want to report the results to the GCC project, use the
+<samp><span class="file">contrib/test_summary</span></samp> shell script. Start it in the <var>objdir</var> with
+
+<pre class="smallexample"> <var>srcdir</var>/contrib/test_summary -p your_commentary.txt \
+ -m gcc-testresults@gcc.gnu.org |sh
+</pre>
+ <p>This script uses the <samp><span class="command">Mail</span></samp> program to send the results, so
+make sure it is in your <samp><span class="env">PATH</span></samp>. The file <samp><span class="file">your_commentary.txt</span></samp> is
+prepended to the testsuite summary and should contain any special
+remarks you have on your results or your build environment. Please
+do not edit the testsuite result block or the subject line, as these
+messages may be automatically processed.
+
+ <p><hr />
+<p><a href="./index.html">Return to the GCC Installation page</a>
+
+<!-- ***Final install*********************************************************** -->
+<!-- ***Binaries**************************************************************** -->
+<!-- ***Specific**************************************************************** -->
+<!-- ***Old documentation****************************************************** -->
+<!-- ***GFDL******************************************************************** -->
+<!-- *************************************************************************** -->
+<!-- Part 6 The End of the Document -->
+</body></html>
+