Context Navigation

-              r1390
+              r1391
+<html lang="en"><head>
+   <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.0">
+<link href="http://texinfo.org/" rel=generator-home>
+</head><body>
+<p>P<p>lease read this document carefully <em>before</em> installing the
+<meta name="description" content="Host/Target specific installation notes for GCC">
+<meta name="generator" content="makeinfo 4.6">
+<!--
+Copyright &copy; 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
+, 2000, 2001, 2002, 2003 Free Software Foundation, Inc.
+<br><p>
+   <p>Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.2 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 "<a href="./gfdl.html">GNU Free Documentation License</a>".
+   <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.-->
+<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 }
+--></style>
+</head>
+<body>
+<h1 class="settitle">Host/Target specific installation notes for GCC</h1>
+Please read this document carefully <em>before</em> installing the
 GNU Compiler Collection on your machine.
+<ul>
+<li><a href="#1750a-*-*">1750a-*-*</a>
+<li><a href="#a29k">a29k</a>
+<li><a href="#a29k-*-bsd">a29k-*-bsd</a>
+     <ul>
 <li><a href="#alpha*-*-*">alpha*-*-*</a>
 <li><a href="#alpha*-dec-osf*">alpha*-dec-osf*</a>
 …
 <li><a href="#arm-*-elf">arm-*-elf</a>
 <li><a href="#arm*-*-linux-gnu">arm*-*-linux-gnu</a>
-<li><a href="#arm-*-riscix">arm-*-riscix</a>
 <li><a href="#avr">avr</a>
 <li><a href="#c4x">c4x</a>
 <li><a href="#dos">DOS</a>
 <li><a href="#dsp16xx">dsp16xx</a>
-<li><a href="#elxsi-elxsi-bsd">elxsi-elxsi-bsd</a>
 <li><a href="#*-*-freebsd*">*-*-freebsd*</a>
 <li><a href="#h8300-hms">h8300-hms</a>
 …
 <li><a href="#i370-*-*">i370-*-*</a>
 <li><a href="#*-*-linux-gnu">*-*-linux-gnu</a>
-<li><a href="#ix86-*-linux*oldld">i?86-*-linux*oldld</a>
 <li><a href="#ix86-*-linux*aout">i?86-*-linux*aout</a>
 <li><a href="#ix86-*-linux*">i?86-*-linux*</a>
 …
 <li><a href="#ix86-*-sco3.2v5*">i?86-*-sco3.2v5*</a>
 <li><a href="#ix86-*-udk">i?86-*-udk</a>
-<li><a href="#ix86-*-isc">i?86-*-isc</a>
 <li><a href="#ix86-*-esix">i?86-*-esix</a>
-<li><a href="#ix86-ibm-aix">i?86-ibm-aix</a>
-<li><a href="#ix86-sequent-bsd">i?86-sequent-bsd</a>
-<li><a href="#ix86-sequent-ptx1*">i?86-sequent-ptx1*</a> i?86-sequent-ptx2*, i?86-sequent-sysv3*
-<li><a href="#i860-intel-osf*">i860-intel-osf*</a>
 <li><a href="#ia64-*-linux">ia64-*-linux</a>
+<li><a href="#ia64-*-hpux*">ia64-*-hpux*</a>
 <li><a href="#*-lynx-lynxos">*-lynx-lynxos</a>
 <li><a href="#*-ibm-aix*">*-ibm-aix*</a>
+<li><a href="#ip2k-*-elf">ip2k-*-elf</a>
 <li><a href="#m32r-*-elf">m32r-*-elf</a>
 <li><a href="#m68000-hp-bsd">m68000-hp-bsd</a>
 <li><a href="#m6811-elf">m6811-elf</a>
 <li><a href="#m6812-elf">m6812-elf</a>
-<li><a href="#m68k-altos">m68k-altos</a>
-<li><a href="#m68k-apple-aux">m68k-apple-aux</a>
 <li><a href="#m68k-att-sysv">m68k-att-sysv</a>
-<li><a href="#m68k-bull-sysv">m68k-bull-sysv</a>
 <li><a href="#m68k-crds-unos">m68k-crds-unos</a>
 <li><a href="#m68k-hp-hpux">m68k-hp-hpux</a>
-<li><a href="#m68k-*-nextstep*">m68k-*-nextstep*</a>
 <li><a href="#m68k-ncr-*">m68k-ncr-*</a>
 <li><a href="#m68k-sun">m68k-sun</a>
 <li><a href="#m68k-sun-sunos4.1.1">m68k-sun-sunos4.1.1</a>
-<li><a href="#m88k-*-svr3">m88k-*-svr3</a>
-<li><a href="#m88k-*-dgux">m88k-*-dgux</a>
-<li><a href="#m88k-tektronix-sysv3">m88k-tektronix-sysv3</a>
 <li><a href="#mips-*-*">mips-*-*</a>
-<li><a href="#mips-dec-*">mips-dec-*</a>
-<li><a href="#mips-mips-bsd">mips-mips-bsd</a>
-<li><a href="#mips-mips-riscos*">mips-mips-riscos*</a>
-<li><a href="#mips-sgi-irix4">mips-sgi-irix4</a>
 <li><a href="#mips-sgi-irix5">mips-sgi-irix5</a>
 <li><a href="#mips-sgi-irix6">mips-sgi-irix6</a>
-<li><a href="#mips-sony-sysv">mips-sony-sysv</a>
-<li><a href="#ns32k-encore">ns32k-encore</a>
-<li><a href="#ns32k-*-genix">ns32k-*-genix</a>
-<li><a href="#ns32k-sequent">ns32k-sequent</a>
-<li><a href="#ns32k-utek">ns32k-utek</a>
 <li><a href="#powerpc*-*-*">powerpc*-*-*</a> powerpc-*-sysv4
 <li><a href="#powerpc-*-darwin*">powerpc-*-darwin*</a>
 …
 <li><a href="#powerpcle-*-eabisim">powerpcle-*-eabisim</a>
 <li><a href="#powerpcle-*-eabi">powerpcle-*-eabi</a>
+<li><a href="#powerpcle-*-winnt">powerpcle-*-winnt</a> powerpcle-*-pe
+<li><a href="#romp-*-aos">romp-*-aos</a> romp-*-mach
+<li><a href="#s390-*-linux*">#s390-*-linux*</a>
+<li><a href="#s390x-*-linux*">#s390x-*-linux*</a>
+<li><a href="#s390-*-linux*">s390-*-linux*</a>
+<li><a href="#s390x-*-linux*">s390x-*-linux*</a>
 <li><a href="#*-*-solaris2*">*-*-solaris2*</a>
 <li><a href="#sparc-sun-solaris2*">sparc-sun-solaris2*</a>
 …
 <li><a href="#sparc-unknown-linux-gnulibc1">sparc-unknown-linux-gnulibc1</a>
 <li><a href="#sparc-*-linux*">sparc-*-linux*</a>
 <li><a href="#sparc64-*-*">sparc64-*-*</a>
+<li><a href="#sparc64-*-solaris2*">sparc64-*-solaris2*</a>
 <li><a href="#sparcv9-*-solaris2*">sparcv9-*-solaris2*</a>
 <li><a href="#*-*-sysv*">*-*-sysv*</a>
 <li><a href="#vax-dec-ultrix">vax-dec-ultrix</a>
 <li><a href="#we32k-*-*">we32k-*-*</a>
+<li><a href="#x86_64-*-*">x86_64-*-*</a> amd64-*-*
 <li><a href="#xtensa-*-elf">xtensa-*-elf</a>
 <li><a href="#xtensa-*-linux*">xtensa-*-linux*</a>
 …
 </ul>
 <ul>
+     <ul>
 <li><a href="#elf_targets">all ELF targets</a> (SVR4, Solaris 2, etc.)
 </ul>
 <!- ------- host/target specific issues start here --------------- ->
+   <!- ------- host/target specific issues start here --------------- ->
 <hr />
+<h2><a name="TOC0"><a name="1750a-*-*"></a>1750a-*-*</h2>
+<p>MIL-STD-1750A processors.  This target is obsoleted in GCC 3.1.
+<p>The MIL-STD-1750A cross configuration produces output for
+<code>as1750</code>, an assembler/linker available under the GNU General Public
+License for the 1750A.  <code>as1750</code> can be obtained at
+<a href="ftp://ftp.fta-berlin.de/pub/crossgcc/1750gals/">ftp://ftp.fta-berlin.de/pub/crossgcc/1750gals/</a>.
+A similarly licensed simulator for
+the 1750A is available from same address.
+<p>You should ignore a fatal error during the building of <code>libgcc</code>
+(<code>libgcc</code> is not yet implemented for the 1750A.)
+<p>The <code>as1750</code> assembler requires the file <code>ms1750.inc</code>, which is
+found in the directory <code>gcc/config/1750a</code>.
+<p>GCC produced the same sections as the Fairchild F9450 C Compiler,
+namely:
+<dl>
+<dt><code>Normal</code>
+<dd>The program code section.
+<br><dt><code>Static</code>
+<dd>The read/write (RAM) data section.
+<br><dt><code>Konst</code>
+<dd>The read-only (ROM) constants section.
+<br><dt><code>Init</code>
+<dd>Initialization section (code to copy KREL to SREL).
+</dl>
+<p>The smallest addressable unit is 16 bits (<code>BITS_PER_UNIT</code> is 16).  This
+means that type <code>char</code> is represented with a 16-bit word per character.
+The 1750A's "Load/Store Upper/Lower Byte" instructions are not used by
+GCC.
+<hr />
+<h2><a name="TOC1"><a name="a29k"></a>a29k</h2>
+<p>AMD Am29k-family processors.  These are normally used in embedded
+applications.  This configuration corresponds to AMD's standard calling
+sequence and binary interface and is compatible with other 29k tools.
+<p>AMD has abandoned this processor.  All existing a29k targets are obsoleted
+in GCC 3.1.
+<p>You may need to make a variant of the file <code>a29k.h</code> for your
+particular configuration.
+<hr />
+<h2><a name="TOC2"><a name="a29k-*-bsd"></a>a29k-*-bsd</h2>
+<p>AMD Am29050 used in a system running a variant of BSD Unix.
+<hr />
+<h2><a name="TOC3"><a name="alpha*-*-*"></a>alpha*-*-*</h2>
+<h3 class="heading"><a name="TOC0"></a><a name="alpha*-*-*"></a>alpha*-*-*</h3>
 <p>This section contains general configuration information for all
 …
 section, please read all other sections that match your target.
 <p>We require binutils 2.11.2 or newer.
+   <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.
 <hr />
 <h2><a name="TOC4"><a name="alpha*-dec-osf*"></a>alpha*-dec-osf*</h2>
+   <hr />
+<h3 class="heading"><a name="TOC1"></a><a name="alpha*-dec-osf*"></a>alpha*-dec-osf*</h3>
 <p>Systems using processors that implement the DEC Alpha architecture and
 …
 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
+<p>Support for versions before <code>alpha*-dec-osf4</code> is obsoleted in GCC
+.1.  (These are the versions which identify themselves as DEC OSF/1.)
+<p>In Digital Unix V4.0, virtual memory exhausted bootstrap failures
+   <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.)
+   <p>In Digital Unix V4.0, virtual memory exhausted bootstrap failures
 may be fixed by configuring with <code>--with-gc=simple</code>,
 reconfiguring Kernel Virtual Memory and Swap parameters
 …
 <a href="http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html">http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html</a>.
 <p>In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
+   <p>In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
 currently (2001-06-13) work with <code>mips-tfile</code>.  As a workaround,
 we need to use the old assembler, invoked via the barely documented
 …
 Compaq C Compiler:
 <pre>   % CC=cc <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>]
 </pre>
 <p>or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
 <pre>   % CC=gcc -Wa,-oldas <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>]
 </pre>
 <p>As of GNU binutils 2.11.2, neither GNU <code>as</code> nor GNU <code>ld</code>
+<pre class="example">        % CC=cc <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>]
+     </pre>
+   <p>or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
+<pre class="example">        % CC=gcc -Wa,-oldas <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>]
+     </pre>
+   <p>As of GNU binutils 2.11.2, neither GNU <code>as</code> nor GNU <code>ld</code>
 are supported on Tru64 UNIX, so you must not configure GCC with
 <code>--with-gnu-as</code> or <code>--with-gnu-ld</code>.
 <p>The <code>--enable-threads</code> options isn't supported yet.  A patch is
+   <p>The <code>--enable-threads</code> options isn't supported yet.  A patch is
 in preparation for a future release.
 <p>GCC writes a <code>.verstamp</code> directive to the assembler output file
+   <p>GCC writes a <code>.verstamp</code> 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 <code>/usr/include/stamp.h</code>.  If you install a
 …
 stamp.
 <p>Note that since the Alpha is a 64-bit architecture, cross-compilers from
+   <p>Note that since the Alpha is a 64-bit architecture, cross-compilers from
 -bit machines will not generate code as efficient as that generated
 when the compiler is running on a 64-bit machine because many
 …
 a few cases and may not work properly.
 <p><code>make compare</code> may fail on old versions of DEC Unix unless you add
+   <p><code>make compare</code> may fail on old versions of DEC Unix unless you add
 <code>-save-temps</code> to <code>CFLAGS</code>.  On these systems, the name of the
 assembler input file is stored in the object file, and that makes
 …
 <code>.s</code> files after each series of compilations.
 <p>GCC now supports both the native (ECOFF) debugging format used by DBX
+   <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 <code>--with-stabs</code> option of <code>configure</code> above
 for more information on these formats and how to select them.
 <p>There is a bug in DEC's assembler that produces incorrect line numbers
+   <p>There is a bug in DEC's assembler that produces incorrect line numbers
 for ECOFF format when the <code>.align</code> directive is used.  To work
 around this problem, GCC will not emit such alignment directives
 …
 different depending on whether or not <code>-g</code> is also specified.
 <p>To avoid this behavior, specify <code>-gstabs+</code> and use GDB instead of
+   <p>To avoid this behavior, specify <code>-gstabs+</code> and use GDB instead of
 DBX.  DEC is now aware of this problem with the assembler and hopes to
 provide a fix shortly.
 <hr />
 <h2><a name="TOC5"><a name="alphaev5-cray-unicosmk*"></a>alphaev5-cray-unicosmk*</h2>
+   <hr />
+<h3 class="heading"><a name="TOC2"></a><a name="alphaev5-cray-unicosmk*"></a>alphaev5-cray-unicosmk*</h3>
 <p>Cray T3E systems running Unicos/Mk.
 <p>This port is incomplete and has many known bugs.  We hope to improve the
+   <p>This port is incomplete and has many known bugs.  We hope to improve the
 support for this target soon.  Currently, only the C front end is supported,
 and it is not possible to build parallel applications.  Cray modules are not
 …
 <code>/opt/ctl/craylibs/craylibs</code>.
 <p>You absolutely <strong>must</strong> use GNU make on this platform.  Also, you
+   <p>You absolutely <strong>must</strong> use GNU make on this platform.  Also, you
 need to tell GCC where to find the assembler and the linker.  The
 simplest way to do so is by providing <code>--with-as</code> and
 <code>--with-ld</code> to <code>configure</code>, e.g.
 <pre>    configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld \
       --enable-languages=c
 </pre>
 <p>The comparison test during <code>make bootstrap</code> fails on Unicos/Mk
+<pre class="example">         configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld \
+           --enable-languages=c
+     </pre>
+   <p>The comparison test during <code>make bootstrap</code> fails on Unicos/Mk
 because the assembler inserts timestamps into object files.  You should
 be able to work around this by doing <code>make all</code> after getting this
 failure.
 <hr />
 <h2><a name="TOC6"><a name="arc-*-elf"></a>arc-*-elf</h2>
+   <hr />
+<h3 class="heading"><a name="TOC3"></a><a name="arc-*-elf"></a>arc-*-elf</h3>
 <p>Argonaut ARC processor.
 This configuration is intended for embedded systems.
+<hr />
+<h2><a name="TOC7"><a name="arm-*-aout"></a>arm-*-aout</h2>
+<p>Advanced RISC Machines ARM-family processors.  These are often used in
+   <hr />
+<h3 class="heading"><a name="TOC4"></a><a name="arm-*-aout"></a>arm-*-aout</h3>
+<p>This configuration is obsoleted in GCC 3.3.
+   <p>Advanced RISC Machines ARM-family processors.  These are often used in
 embedded applications.  There are no standard Unix configurations.
 This configuration corresponds to the basic instruction sequences and will
 produce <code>a.out</code> format object modules.
 <p>You may need to make a variant of the file <code>arm.h</code> for your particular
+   <p>You may need to make a variant of the file <code>arm.h</code> for your particular
 configuration.
 <hr />
 <h2><a name="TOC8"><a name="arm-*-elf"></a>arm-*-elf</h2>
+   <hr />
+<h3 class="heading"><a name="TOC5"></a><a name="arm-*-elf"></a>arm-*-elf</h3>
 <p>This configuration is intended for embedded systems.
 <hr />
 <h2><a name="TOC9"><a name="arm*-*-linux-gnu"></a>arm*-*-linux-gnu</h2>
+   <hr />
+<h3 class="heading"><a name="TOC6"></a><a name="arm*-*-linux-gnu"></a>arm*-*-linux-gnu</h3>
 <p>We require GNU binutils 2.10 or newer.
+<hr />
+<h2><a name="TOC10"><a name="arm-*-riscix"></a>arm-*-riscix</h2>
+<p>The ARM2 or ARM3 processor running RISC iX, Acorn's port of BSD Unix.
+This configuration is obsoleted in GCC 3.1.
+<p>If you are running a version of RISC iX prior to 1.2 then you must
+specify the version number during configuration.  Note that the
+assembler shipped with RISC iX does not support stabs debugging
+information; a new version of the assembler, with stabs support
+included, is now available from Acorn and via ftp
+<a href="ftp://ftp.acorn.com/pub/riscix/as+xterm.tar.Z">ftp://ftp.acorn.com/pub/riscix/as+xterm.tar.Z</a>.  To enable stabs
+debugging, pass <code>--with-gnu-as</code> to configure.
+<p>You will need to install GNU <code>sed</code> before you can run configure.
+<hr />
+<h2><a name="TOC11"><a name="avr"></a>avr</h2>
+   <hr />
+<h3 class="heading"><a name="TOC7"></a><a name="avr"></a>avr</h3>
 <p>ATMEL AVR-family micro controllers.  These are used in embedded
 …
 for the list of supported MCU types.
 <p>Use <code>configure --target=avr --enable-languages="c"</code> to configure GCC.
 <p>Further installation notes and other useful information about AVR tools
+   <p>Use <code>configure --target=avr --enable-languages="c"</code> to configure GCC.
+   <p>Further installation notes and other useful information about AVR tools
 can also be obtained from:
+<ul>
+<li><a href="http://home.overta.ru/users/denisc">http://home.overta.ru/users/denisc</a>
+<li><a href="http://www.amelek.gda.pl/avr">http://www.amelek.gda.pl/avr</a>
+     <ul>
+<li><a href="http://www.openavr.org">http://www.openavr.org</a>
+<li><a href="http://home.overta.ru/users/denisc/">http://home.overta.ru/users/denisc/</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.11 or newer.
 <p>The following error:
 <pre>  Error: register required
 </pre>
 <p>indicates that you should upgrade to a newer version of the binutils.
 <hr />
 <h2><a name="TOC12"><a name="c4x"></a>c4x</h2>
+   <p>We <em>strongly</em> recommend using binutils 2.13 or newer.
+   <p>The following error:
+<pre class="example">       Error: register required
+     </pre>
+   <p>indicates that you should upgrade to a newer version of the binutils.
+   <hr />
+<h3 class="heading"><a name="TOC8"></a><a name="c4x"></a>c4x</h3>
 <p>Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal
 …
 for the list of supported MCU types.
 <p>GCC can be configured as a cross compiler for both the C3x and C4x
+   <p>GCC can be configured as a cross compiler for both the C3x and C4x
 architectures on the same system.  Use <code>configure --target=c4x
 --enable-languages="c,c++"</code> to configure.
 <p>Further installation notes and other useful information about C4x tools
+   <p>Further installation notes and other useful information about C4x tools
 can also be obtained from:
 <ul>
+     <ul>
 <li><a href="http://www.elec.canterbury.ac.nz/c4x/">http://www.elec.canterbury.ac.nz/c4x/</a>
 </ul>
 <hr />
 <h2><a name="TOC13"><a name="cris"></a>CRIS</h2>
+   <hr />
+<h3 class="heading"><a name="TOC9"></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 "CRIS Options" in the main manual
+   <p>See "CRIS Options" in the main manual
 for a list of CRIS-specific options.
 <p>There are a few different CRIS targets:
 <dl>
+   <p>There are a few different CRIS targets:
+     <dl>
 <dt><code>cris-axis-aout</code>
 <dd>Old target.  Includes a multilib for the <code>elinux</code> a.out-based
+     <dd>Old target.  Includes a multilib for the <code>elinux</code> a.out-based
 target.  No multilibs for newer architecture variants.
 <br><dt><code>cris-axis-elf</code>
 <dd>Mainly for monolithic embedded systems.  Includes a multilib for the
+     <dd>Mainly for monolithic embedded systems.  Includes a multilib for the
 <code>v10</code> core used in <code>ETRAX 100 LX</code>.
 <br><dt><code>cris-axis-linux-gnu</code>
 <dd>A GNU/Linux port for the CRIS architecture, currently targeting
+     <dd>A GNU/Linux port for the CRIS architecture, currently targeting
 <code>ETRAX 100 LX</code> by default.
 </dl>
 <p>For <code>cris-axis-aout</code> and <code>cris-axis-elf</code> you need binutils 2.11
+   <p>For <code>cris-axis-aout</code> and <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
+   <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>.
 <hr />
 <h2><a name="TOC14"><a name="dos"></a>DOS</h2>
+   <hr />
+<h3 class="heading"><a name="TOC10"></a><a name="dos"></a>DOS</h3>
 <p>Please have a look at our <a href="binaries.html">binaries page</a>.
 <p>You cannot install GCC by itself on MSDOS; it will not compile under
+   <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.
 <hr />
 <h2><a name="TOC15"><a name="dsp16xx"></a>dsp16xx</h2>
+   <hr />
+<h3 class="heading"><a name="TOC11"></a><a name="dsp16xx"></a>dsp16xx</h3>
 <p>A port to the AT&amp;T DSP1610 family of processors.
 <hr />
 <h2><a name="TOC16"><a name="*-*-freebsd*"></a>*-*-freebsd*</h2>
+   <hr />
+<h3 class="heading"><a name="TOC12"></a><a name="*-*-freebsd*"></a>*-*-freebsd*</h3>
 <p>The version of binutils installed in <code>/usr/bin</code> is known to work unless
 …
 .12.1 or greater is known to improve overall testsuite results.
+<p>For FreeBSD 1, FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
+   <p>Support for FreeBSD 1 was discontinued in GCC 3.2.
+   <p>For FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
 configuration support and files as shipped with GCC 2.95 are still in
 place.  FreeBSD 2.2.7 has been known to bootstrap completely; however,
 …
 was the system copy in <code>/usr/bin</code>) and C++ EH failures were noted.
+<p>Support for FreeBSD 1 is obsoleted in GCC 3.1.
+<p>For FreeBSD using the ELF file format: DWARF 2 debugging is now the
+   <p>For FreeBSD using the ELF file format: DWARF 2 debugging is now the
 default for all CPU architectures.  It had been the default on
 FreeBSD/alpha since its inception.  You may use <code>-gstabs</code> instead
 …
 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 3.0, 3.4, 4.0, 4.2, 4.3, 4.4, 4.5-STABLE and 5-CURRENT.
+<p>In principle, <code>--enable-threads</code> is now compatible with
+results on FreeBSD 4.8-STABLE and 5-CURRENT.  In the past, known to
+bootstrap and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2,
+.3, 4.4, 4.5-STABLE.
+   <p>In principle, <code>--enable-threads</code> is now compatible with
 <code>--enable-libgcj</code> on FreeBSD.  However, it has only been built
 and tested on <code>i386-*-freebsd4.5</code> and <code>alpha-*-freebsd5.0</code>.
+and tested on <code>i386-*-freebsd[45]</code> and <code>alpha-*-freebsd[45]</code>.
 The static
 library may be incorrectly built (symbols are missing at link time).
 There is a rare timing-based startup hang (probably involves an
 assupmtion about the thread library).  Multi-threaded boehm-gc (required for
+assumption about the thread library).  Multi-threaded boehm-gc (required for
 libjava) exposes severe threaded signal-handling bugs on FreeBSD before
+.5-RELEASE.  The alpha port may not fully bootstrap without some manual
+intervention: <code>gcjh</code> will crash with a floating-point exception while
+generating <code>java/lang/Double.h</code> (just copy the version built on
+<code>i386-*-freebsd*</code> and rerun the top-level <code>gmake</code> with no
+arguments and it
+should properly complete the bootstrap).  Other CPU architectures
+.5-RELEASE.  Other CPU architectures
 supported by FreeBSD will require additional configuration tuning in, at
 the very least, both boehm-gc and libffi.
+<p>Shared <code>libgcc_s.so</code> is now built and installed by default.
+<hr />
+<h2><a name="TOC17"><a name="elxsi-elxsi-bsd"></a>elxsi-elxsi-bsd</h2>
+<p>The Elxsi's C compiler has known limitations that prevent it from
+compiling GCC.  Please contact <a href="mailto:mrs@wrs.com">mrs@wrs.com</a> for more details.
+<p>Support for this processor is obsoleted in GCC 3.1.
+<hr />
+<h2><a name="TOC18"><a name="h8300-hms"></a>h8300-hms</h2>
+<p>Hitachi H8/300 series of processors.
+<p>Please have a look at our <a href="binaries.html">binaries page</a>.
+<p>The calling convention and structure layout has changed in release 2.6.
+   <p>Shared <code>libgcc_s.so</code> is now built and installed by default.
+   <hr />
+<h3 class="heading"><a name="TOC13"></a><a name="h8300-hms"></a>h8300-hms</h3>
+<p>Renesas H8/300 series of processors.
+   <p>Please have a look at our <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.
+<hr />
+<h2><a name="TOC19"><a name="hppa*-hp-hpux*"></a>hppa*-hp-hpux*</h2>
+<p>We <em>highly</em> recommend using gas/binutils 2.8 or newer on all hppa
+   <hr />
+<h3 class="heading"><a name="TOC14"></a><a name="hppa*-hp-hpux*"></a>hppa*-hp-hpux*</h3>
+<p>Support for HP-UX versions 7, 8, and 9 is obsoleted in GCC 3.3.
+   <p>We <em>highly</em> recommend using gas/binutils 2.8 or newer on all hppa
 platforms; you may encounter a variety of problems when using the HP
+assembler.  The HP assembler does not work with the <code>hppa64-hp-hpux11*</code>
+port.
+<p>Specifically, <code>-g</code> does not work on HP-UX (since that system
+assembler.
+   <p>Specifically, <code>-g</code> does not work on HP-UX (since that system
 uses a peculiar debugging format which GCC does not know about), unless you
 use GAS and GDB and configure GCC with the
 <a href="./configure.html#with-gnu-as"><code>--with-gnu-as</code></a> and
 <code>--with-as=<small>...</small></code> options.
 <p>If you wish to use the pa-risc 2.0 architecture support with a 32-bit
+<code>--with-as=...</code> options.
+   <p>If you wish to use the pa-risc 2.0 architecture support with a 32-bit
 runtime, you must use either the HP assembler, gas/binutils 2.11 or newer,
 or a recent
 <a href="ftp://sources.redhat.com/pub/binutils/snapshots">snapshot of gas</a>.
+<p>More specific information to <code>hppa*-hp-hpux*</code> targets follows.
+<hr />
+<h2><a name="TOC20"><a name="hppa*-hp-hpux9"></a>hppa*-hp-hpux9</h2>
+<p>The HP assembler has major problems on this platform.  We've tried to work
+   <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 <code>hppa1*</code> 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>More specific information to <code>hppa*-hp-hpux*</code> targets follows.
+   <hr />
+<h3 class="heading"><a name="TOC15"></a><a name="hppa*-hp-hpux9"></a>hppa*-hp-hpux9</h3>
+<p>Support for this system is obsoleted in GCC 3.3.
+   <p>The HP assembler has major problems on this platform.  We've tried to work
 around the worst of the problems.  However, those workarounds may be causing
 linker crashes in some circumstances; the workarounds also probably prevent
 shared libraries from working.  Use the GNU assembler to avoid these problems.
 <p>The configuration scripts for GCC will also trigger a bug in the hpux9
+   <p>The configuration scripts for GCC will also trigger a bug in the hpux9
 shell.  To avoid this problem set <code>CONFIG_SHELL</code> to <code>/bin/ksh</code>
 and <code>SHELL</code> to <code>/bin/ksh</code> in your environment.
 <hr />
 <h2><a name="TOC21"><a name="hppa*-hp-hpux10"></a>hppa*-hp-hpux10</h2>
+   <hr />
+<h3 class="heading"><a name="TOC16"></a><a name="hppa*-hp-hpux10"></a>hppa*-hp-hpux10</h3>
 <p>For hpux10.20, we <em>highly</em> recommend you pick up the latest sed patch
 …
 charge:
 <ul>
 <li><a href="http://us-support.external.hp.com">US, Canada, Asia-Pacific, and
+     <ul>
+<li><a href="http://us.itrc.hp.com/service/home/home.do">US, Canada, Asia-Pacific, and
 Latin-America</a>
 <li><a href="http://europe-support.external.hp.com">Europe</a>
+<li><a href="http://europe.itrc.hp.com/service/home/home.do">http://europe.itrc.hp.com/service/home/home.do</a> Europe.
 </ul>
 <p>The HP assembler on these systems is much better than the hpux9 assembler,
+   <p>The HP assembler on these systems is much better than the hpux9 assembler,
 but still has some problems.  Most notably the assembler inserts timestamps
 into each object file it creates, causing the 3-stage comparison test to fail
 …
 bootstrap</code>.
 <hr />
 <h2><a name="TOC22"><a name="hppa*-hp-hpux11"></a>hppa*-hp-hpux11</h2>
+   <hr />
+<h3 class="heading"><a name="TOC17"></a><a name="hppa*-hp-hpux11"></a>hppa*-hp-hpux11</h3>
 <p>GCC 3.0 and up support HP-UX 11.  On 64-bit capable systems, there
 are two distinct ports.  The <code>hppa2.0w-hp-hpux11*</code> port generates
 code for the 32-bit pa-risc runtime architecture.  It uses the HP
+linker and is currently the default selected by config.guess.  The
+optional <code>hppa64-hp-hpux11*</code> port generates 64-bit code for the
+pa-risc 2.0 architecture.  It must be explicitly selected using the
+<code>--host=hppa64-hp-hpux11*</code> configure option.  Different prefixes
+must be used if both ports are to be installed on the same system.
+<p>You must use GNU binutils 2.11 or above with the 32-bit port.  Thread
+linker.  The <code>hppa64-hp-hpux11*</code> port generates 64-bit code for the
+pa-risc 2.0 architecture.  The script config.guess now selects the port
+type based on the type compiler detected during configuration.  You must
+set your <code>PATH</code> or define <code>CC</code> so that configure finds an appropriate
+compiler for the initial bootstrap.  Different prefixes must be used if
+both ports are to be installed on the same system.
+   <p>It is best to explicitly configure the <code>hppa64-hp-hpux11*</code> target
+with the <code>--with-ld=...</code> option.  We support both the HP
+and GNU linkers for this target.  The two linkers require different
+link commands.  Thus, it's not possible to switch linkers during a
+GCC build.  This has been been reported to occur in a unified build
+of binutils and GCC.
+   <p>GCC 2.95.x is not supported under HP-UX 11 and cannot be used to
+compile GCC 3.0 and up.  Refer to <a href="binaries.html">binaries</a> for
+information about obtaining precompiled GCC binaries for HP-UX.
+   <p>You must use GNU binutils 2.11 or above with the 32-bit port.  Thread
 support is not currently implemented, so <code>--enable-threads</code> does
 not work.  See:
 <ul>
+     <ul>
 <li><a href="http://gcc.gnu.org/ml/gcc-prs/2002-01/msg00551.html">http://gcc.gnu.org/ml/gcc-prs/2002-01/msg00551.html</a>
 <li><a href="http://gcc.gnu.org/ml/gcc-bugs/2002-01/msg00663.html">http://gcc.gnu.org/ml/gcc-bugs/2002-01/msg00663.html</a>.
+<li><a href="http://gcc.gnu.org/ml/gcc-bugs/2002-01/msg00663.html">http://gcc.gnu.org/ml/gcc-bugs/2002-01/msg00663.html</a>
 </ul>
+<p>GCC 2.95.x is not supported under HP-UX 11 and cannot be used to
+compile GCC 3.0 and up.  Refer to <a href="binaries.html">binaries</a> for
+information about obtaining precompiled GCC binaries for HP-UX.
+<p>GNU binutils 2.13 or later is recommended with the 64-bit port.
+The HP assembler is not supported.  It is <em>highly</em> recommended
+that the GNU linker be used as well.  Either binutils must be built
+prior to gcc, or a binary distribution of gcc or binutils must be
+obtained for the initial builds.  When starting with a HP compiler,
+it is preferable to use the ANSI compiler as the bundled compiler
+only supports traditional C.  Bootstrapping with the bundled compiler
+is tested infrequently and problems often arise because of the subtle
+differences in semantics between traditional and ISO C.  There also
+have been problems reported with various binary distributions.  This
+port still is undergoing significant development.
+<hr />
+<h2><a name="TOC23"><a name="i370-*-*"></a>i370-*-*</h2>
+   <p>GCC 3.3 and later support weak symbols on the 32-bit port using SOM
+secondary definition symbols.  This feature is not enabled for earlier
+versions of HP-UX since there have been bugs in the linker support for
+secondary symbols.  The HP linker patches <code>PHSS_26559</code> and
+<code>PHSS_24304</code> for HP-UX 11.00 and 11.11, respectively, correct the
+problem of linker core dumps creating C++ libraries.  Earlier patches
+may work but they have not been tested.
+   <p>GCC 3.3 nows uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capability
+to run initializers and finalizers on the 64-bit port.  The feature
+requires CVS binutils as of January 2, 2003, or a subsequent release
+to correct a problem arising from HP's non-standard use of the .init
+and .fini sections.  The 32-bit port uses the linker <code>+init</code>
+and <code>+fini</code> options.  As with the support for secondary symbols,
+there have been bugs in the order in which these options are executed
+by the HP linker.  So, again a recent linker patch is recommended.
+   <p>The HP assembler has many limitations and is not recommended for either
+the 32 or 64-bit ports.  For example, it does not support weak symbols
+or alias definitions.  As a result, explicit template instantiations
+are required when using C++.  This will make it difficult if not
+impossible to build many C++ applications.  You also can't generate
+debugging information when using the HP assembler with GCC.
+   <p>There are a number of issues to consider in selecting which linker to
+use with the 64-bit port.  The  GNU 64-bit linker can only create dynamic
+binaries.  The <code>-static</code> option causes linking with archive
+libraries but doesn't produce a truly static binary.  Dynamic binaries
+still require final binding by the dynamic loader to resolve a set of
+dynamic-loader-defined symbols.  The default behavior of the HP linker
+is the same as the GNU linker.  However, it can generate true 64-bit
+static binaries using the <code>+compat</code> option.
+   <p>The HP 64-bit linker doesn't support linkonce semantics.  As a
+result, C++ programs have many more sections than they should.
+   <p>The GNU 64-bit linker has some issues with shared library support
+and exceptions.  As a result, we only support libgcc in archive
+format.  For similar reasons, dwarf2 unwind and exception support
+are disabled.  The GNU linker also has problems creating binaries
+with <code>-static</code>.  It doesn't provide stubs for internal
+calls to global functions in shared libraries, so these calls
+can't be overloaded.
+   <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>When starting with a HP compiler, it is preferable to use the ANSI
+compiler as the bundled compiler only supports traditional C.
+Bootstrapping with the bundled compiler is tested infrequently and
+problems often arise because of the subtle differences in semantics
+between traditional and ISO C.
+   <p>This port still is undergoing significant development.
+   <hr />
+<h3 class="heading"><a name="TOC18"></a><a name="i370-*-*"></a>i370-*-*</h3>
 <p>This port is very preliminary and has many known bugs.  We hope to
 have a higher-quality port for this machine soon.
+<hr />
+<h2><a name="TOC24"><a name="*-*-linux-gnu"></a>*-*-linux-gnu</h2>
+<p>If you use glibc 2.2 (or 2.1.9x), GCC 2.95.2 won't install
+   <hr />
+<h3 class="heading"><a name="TOC19"></a><a name="*-*-linux-gnu"></a>*-*-linux-gnu</h3>
+<p>Versions of libstdc++-v3 starting with 3.2.1 require bugfixes present
+in glibc 2.2.5 and later.  More information is available in the
+libstdc++-v3 documentation.
+   <p>If you use glibc 2.2 (or 2.1.9x), GCC 2.95.2 won't install
 out-of-the-box.  You'll get compile errors while building <code>libstdc++</code>.
 The patch <a href="glibc-2.2.patch">glibc-2.2.patch</a>, that is to be
 applied in the GCC source tree, fixes the compatibility problems.
+<p>
+<p>Currently Glibc 2.2.3 (and older releases) and GCC 3.0 are out of sync
+   <p>Currently Glibc 2.2.3 (and older releases) and GCC 3.0 are out of sync
 since the latest exception handling changes for GCC.  Compiling glibc
 with GCC 3.0 will give a binary incompatible glibc and therefore cause
 lots of problems and might make your system completly unusable.  This
 will definitly need fixes in glibc but might also need fixes in GCC.  We
+lots of problems and might make your system completely unusable.  This
+will definitely need fixes in glibc but might also need fixes in GCC.  We
 strongly advise to wait for glibc 2.2.4 and to read the release notes of
 glibc 2.2.4 whether patches for GCC 3.0 are needed.  You can use glibc
 .2.3 with GCC 3.0, just do not try to recompile it.
+<hr />
+<h2><a name="TOC25"><a name="ix86-*-linux*oldld"></a>i?86-*-linux*oldld</h2>
+<p>Use this configuration to generate <code>a.out</code> binaries on Linux-based
+GNU systems if you do not have gas/binutils version 2.5.2 or later
+installed.
+<p>This configuration is obsoleted in GCC 3.1.
+<hr />
+<h2><a name="TOC26"><a name="ix86-*-linux*aout"></a>i?86-*-linux*aout</h2>
+   <hr />
+<h3 class="heading"><a name="TOC20"></a><a name="ix86-*-linux*aout"></a>i?86-*-linux*aout</h3>
 <p>Use this configuration to generate <code>a.out</code> binaries on Linux-based
 …
 gas/binutils version 2.5.2 or later.
+<hr />
+<h2><a name="TOC27"><a name="ix86-*-linux*"></a>i?86-*-linux*</h2>
+<p>You will need binutils 2.9.1.0.15 or newer for exception handling to work.
+<p>If you receive Signal 11 errors when building on GNU/Linux, then it is
+   <hr />
+<h3 class="heading"><a name="TOC21"></a><a name="ix86-*-linux*"></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>.
 <hr />
 <h2><a name="TOC28"><a name="ix86-*-sco"></a>i?86-*-sco</h2>
+   <hr />
+<h3 class="heading"><a name="TOC22"></a><a name="ix86-*-sco"></a>i?86-*-sco</h3>
 <p>Compilation with RCC is recommended.  Also, it may be a good idea to
 link with GNU malloc instead of the malloc that comes with the system.
+<hr />
+<h2><a name="TOC29"><a name="ix86-*-sco3.2v4"></a>i?86-*-sco3.2v4</h2>
+<p>Use this configuration for SCO release 3.2 version 4.
+<hr />
+<h2><a name="TOC30"><a name="ix86-*-sco3.2v5*"></a>i?86-*-sco3.2v5*</h2>
+   <hr />
+<h3 class="heading"><a name="TOC23"></a><a name="ix86-*-sco3.2v5*"></a>i?86-*-sco3.2v5*</h3>
 <p>Use this for the SCO OpenServer Release 5 family of operating systems.
 <p>Unlike earlier versions of GCC, the ability to generate COFF with this
+   <p>Unlike earlier versions of GCC, the ability to generate COFF with this
 target is no longer provided.
 <p>Earlier versions of GCC emitted DWARF 1 when generating ELF to allow
+   <p>Earlier versions of GCC emitted DWARF 1 when generating ELF to allow
 the system debugger to be used.  That support was too burdensome to
 maintain.  GCC now emits only DWARF 2 for this target.  This means you
 …
 version of GCC.
+<p>Use of the <code>-march=pentiumpro</code> flag can result in
+unrecognized opcodes when using the native assembler on OS versions before
+.0.6.  (Support for P6 opcodes was added to the native ELF assembler in
+that version.)  While it's rather rare to see these emitted by GCC yet,
+errors of the basic form:
+<pre>  /usr/tmp/ccaNlqBc.s:22:unknown instruction: fcomip
+  /usr/tmp/ccaNlqBc.s:50:unknown instruction: fucomip
+</pre>
+<p>are symptoms of this problem.  You may work around this by not
+building affected files with that flag, by using the GNU assembler, or
+by using the assembler provided with the current version of the OS.
+Users of GNU assembler should see the note below for hazards on doing
+so.
+<p>The native SCO assembler that is provided with the OS at no
+charge is normally required.  If, however, you must be able to use
+the GNU assembler (perhaps you're compiling code with asms that
+require GAS syntax) you may configure this package using the flags
+<a href="./configure.html#with-gnu-as"><code>--with-gnu-as</code></a>.  You must
+use a recent version of GNU binutils; versions past 2.9.1 seem to work
+well.
+<p>In general, the <code>--with-gnu-as</code> option isn't as well tested
+as the native assembler.
+<p>Look in <code>gcc/config/i386/sco5.h</code> (search for "messy") for
+additional OpenServer-specific flags.
+<p>Systems based on OpenServer before 5.0.4 (<code>uname -X</code>
+will tell you what you're running) require TLS597 from
+<a href="ftp://ftp.sco.com/TLS/">ftp://ftp.sco.com/TLS/</a>
+for C++ constructors and destructors to work right.
+<p>The system linker in (at least) 5.0.4 and 5.0.5 will sometimes
+do the wrong thing for a construct that GCC will emit for PIC
+code.  This can be seen as execution testsuite failures when using
+<code>-fPIC</code> on <code>921215-1.c</code>, <code>931002-1.c</code>, <code>nestfunc-1.c</code>, and <code>gcov-1.c</code>.
+For 5.0.5, an updated linker that will cure this problem is
+available.  You must install both
+<a href="ftp://ftp.sco.com/Supplements/rs505a/">ftp://ftp.sco.com/Supplements/rs505a/</a>
+and <a href="ftp://ftp.sco.com/SLS/">OSS499A</a>.
+<p>The dynamic linker in OpenServer 5.0.5 (earlier versions may show
+the same problem) aborts on certain G77-compiled programs.  It's particularly
+likely to be triggered by building Fortran code with the <code>-fPIC</code> flag.
+Although it's conceivable that the error could be triggered by other
+code, only G77-compiled code has been observed to cause this abort.
+If you are getting core dumps immediately upon execution of your
+G77 program--and especially if it's compiled with <code>-fPIC</code>--try applying
+<a href="sco_osr5_g77.patch"><code>sco_osr5_g77.patch</code></a> to your <code>libf2c</code> and
+rebuilding GCC.
+Affected faults, when analyzed in a debugger, will show a stack
+backtrace with a fault occurring in <code>rtld()</code> and the program
+running as <code>/usr/lib/ld.so.1</code>.  This problem has been reported to SCO
+engineering and will hopefully be addressed in later releases.
+<hr />
+<h2><a name="TOC31"><a name="ix86-*-udk"></a>i?86-*-udk</h2>
+   <p>GCC is now only supported on releases 5.0.4 and later, and requires that
+you install Support Level Supplement OSS646B or later, and the latest
+version of the Supplement Graphics, Web and X11 Libraries (GWXLIBS)
+package.  If you are using release 5.0.7 of OpenServer, you must have at
+least the first maintenance pack installed (this includes the relevant
+portions of OSS646 and GWXLIBS).  OSS646, also known as the "Execution
+Environment Update", provides updated link editors and assemblers, as well
+as updated standard C and math libraries.  The C startup modules are also
+updated to support the System V gABI draft, and GCC relies on that
+behavior.  GWXLIBS provides a collection of commonly used open source
+libraries, some of which GCC depends on (such as GNU gettext and zlib).
+SCO OpenServer Release 5.0.7 has all of this built in by default, but
+GWXLIBS is significantly updated in Maintenance Pack 1.  Please visit
+<a href="ftp://ftp.sco.com/pub/openserver5">ftp://ftp.sco.com/pub/openserver5</a>
+and
+<a href="ftp://ftp.sco.com/pub/openserver5/opensrc">ftp://ftp.sco.com/pub/openserver5/opensrc</a>
+for the latest versions of these (and other potentially useful) supplements.
+   <p>Although there is support for using the native assembler, it is recommended
+that you configure GCC to use the GNU assembler.  You do this by using the
+flags <a href="./configure.html#with-gnu-as"><code>--with-gnu-as</code></a>.  You
+should use a modern version of GNU binutils.  Version 2.14 was used for all
+testing.  In general, only the <code>--with-gnu-as</code> option is tested.  A
+modern bintuils (as well as a plethora of other development related GNU
+utilities) can be found in the GNU Development Tools package.  See the
+SCO web and ftp sites for details.  That package also contains the
+currently "officially supported" version of GCC, version 2.95.3.  It is
+useful for bootstrapping this version.
+   <hr />
+<h3 class="heading"><a name="TOC24"></a><a name="ix86-*-udk"></a>i?86-*-udk</h3>
 <p>This target emulates the SCO Universal Development Kit and requires that
 …
 with the same warnings and caveats as the SCO UDK.
 <p>This target is a little tricky to build because we have to distinguish
+   <p>This target is a little tricky to build because we have to distinguish
 it from the native tools (so it gets headers, startups, and libraries
 from the right place) while making the tools not think we're actually
 …
 command like this:
 <pre>    CC=/udk/usr/ccs/bin/cc <var>/your/path/to</var>/gcc/configure \
       --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-
 </pre>
 <p><em>You should substitute <code>i686</code> in the above command with the appropriate
+<pre class="example">         CC=/udk/usr/ccs/bin/cc <var>/your/path/to</var>/gcc/configure \
+           --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-
+     </pre>
+   <p><em>You should substitute </em><code>i686</code><em> in the above command with the appropriate
 processor for your host.</em>
 <p>After the usual <code>make bootstrap</code> and
+   <p>After the usual <code>make bootstrap</code> and
 <code>make install</code>, you can then access the UDK-targeted GCC
 tools by adding <code>udk-</code> before the commonly known name.  For
 …
 have installed.
+<hr />
+<h2><a name="TOC32"><a name="ix86-*-isc"></a>i?86-*-isc</h2>
+<p>This configuration is obsoleted in GCC 3.1.
+<p>It may be a good idea to link with GNU malloc instead of the malloc that
+comes with the system.
+<p>In ISC version 4.1, <code>sed</code> core dumps when building
+<code>deduced.h</code>.  Use the version of <code>sed</code> from version 4.0.
+<hr />
+<h2><a name="TOC33"><a name="ix86-ibm-aix"></a>i?86-ibm-aix</h2>
+<p>This configuration is obsoleted in GCC 3.1.
+<p>You need to use GAS version 2.1 or later, and LD from
+GNU binutils version 2.2 or later.
+<hr />
+<h2><a name="TOC34"><a name="ix86-sequent-bsd"></a>i?86-sequent-bsd</h2>
+<p>This configuration is obsoleted in GCC 3.1.
+<p>Go to the Berkeley universe before compiling.
+<hr />
+<h2><a name="TOC35"><a name="ix86-sequent-ptx1*"></a>i?86-sequent-ptx1*, i?86-sequent-ptx2*, i?86-sequent-sysv3*</h2>
+<p>This configuration is obsoleted in GCC 3.1.
+<p>You must install GNU <code>sed</code> before running <code>configure</code>.
+<p>The <code>fixproto</code> shell script may trigger a bug in the system shell.
+If you encounter this problem, upgrade your operating system or
+use <code>bash</code> (the GNU shell) to run <code>fixproto</code>.
+<hr />
+<h2><a name="TOC36"><a name="i860-intel-osf*"></a>i860-intel-osf*</h2>
+<p>All support for the i860 processor is obsoleted in GCC 3.1.
+<p>On the Intel Paragon (an i860 machine), if you are using operating
+system version 1.0, you will get warnings or errors about redefinition
+of <code>va_arg</code> when you build GCC.
+<p>If this happens, then you need to link most programs with the library
+<code>iclib.a</code>.  You must also modify <code>stdio.h</code> as follows: before
+the lines
+<pre>#if     defined(__i860__) &amp;&amp; !defined(_VA_LIST)
+#include &lt;va_list.h&gt;
+</pre>
+<p>insert the line
+<pre>#if __PGC__
+</pre>
+<p>and after the lines
+<pre>extern int  vprintf(const char *, va_list );
+extern int  vsprintf(char *, const char *, va_list );
+#endif
+</pre>
+<p>insert the line
+<pre>#endif /* __PGC__ */
+</pre>
+<p>These problems don't exist in operating system version 1.1.
+<hr />
+<h2><a name="TOC37"><a name="ia64-*-linux"></a>ia64-*-linux</h2>
+   <hr />
+<h3 class="heading"><a name="TOC25"></a><a name="ia64-*-linux"></a>ia64-*-linux</h3>
 <p>IA-64 processor (also known as IPF, or Itanium Processor Family)
 running GNU/Linux.
 <p>The toolchain is not completely finished, so requirements will continue
+   <p>The toolchain is not completely finished, so requirements will continue
 to change.
 GCC 3.0.1 and later require glibc 2.2.4.
 …
 GCC 3.0.1 requires binutils 2.11.1 or later.
 <p>None of the following versions of GCC has an ABI that is compatible
+   <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:
 …
 ABI changes are expected.
+<hr />
+<h2><a name="TOC38"><a name="*-lynx-lynxos"></a>*-lynx-lynxos</h2>
+<p>LynxOS 2.2 and earlier comes with GCC 1.x already installed as
+   <hr />
+<h3 class="heading"><a name="TOC26"></a><a name="ia64-*-hpux*"></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 <code>--with-gnu-as</code> 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, <code>--enable-libunwind-exceptions</code>
+is required to build GCC. For GCC 3.3 and later, this is the default.
+   <hr />
+<h3 class="heading"><a name="TOC27"></a><a name="*-lynx-lynxos"></a>*-lynx-lynxos</h3>
+<p>Support for SPARC LynxOS is obsoleted in GCC 3.3.
+   <p>LynxOS 2.2 and earlier comes with GCC 1.x already installed as
 <code>/bin/gcc</code>.  You should compile with this instead of <code>/bin/cc</code>.
 You can tell GCC to use the GNU assembler and linker, by specifying
 …
 installed tools, which produce <code>a.out</code> format executables.
 <hr />
+   <hr />
 <!- rs6000-ibm-aix*, powerpc-ibm-aix* ->
+<h2><a name="TOC39"><a name="*-ibm-aix*"></a>*-ibm-aix*</h2>
+<p>AIX Make frequently has problems with GCC makefiles.  GNU Make 3.76 or
+<h3 class="heading"><a name="TOC28"></a><a name="*-ibm-aix*"></a>*-ibm-aix*</h3>
+<p>Support for AIX versions 1, 2, and 3 is obsoleted in GCC 3.3.
+   <p>AIX Make frequently has problems with GCC makefiles.  GNU Make 3.76 or
 newer is recommended to build on this platform.
 <p>Errors involving <code>alloca</code> when building GCC generally are due
+   <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
 …
 is the version of Make (see above).
+<p>The GNU Assembler incorrectly reports that it supports WEAK symbols on
+AIX which causes GCC to try to utilize weak symbol functionality which
+is not really supported on the platform.  The native <code>as</code> and
+<code>ld</code> still are recommended.  The native AIX tools do
+interoperate with GCC.
+<p>Building <code>libstdc++.a</code> requires a fix for a AIX Assembler bug
+   <p>The native <code>as</code> and <code>ld</code> are recommended for bootstrapping
+on AIX 4 and required for bootstrapping on AIX 5L.  The GNU Assembler
+reports that it supports WEAK symbols on AIX 4, which causes GCC to try to
+utilize weak symbol functionality although it is not supported.  The GNU
+Assembler and Linker do not support AIX 5L sufficiently to bootstrap GCC.
+The native AIX tools do interoperate with GCC.
+   <p>Building <code>libstdc++.a</code> requires a fix for an AIX Assembler bug
 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1).
 <p><code>libstdc++</code> in GCC 3.2 increments the major version number of the
+   <p><code>libstdc++</code> in GCC 3.2 increments the major version number of the
 shared object and GCC installation places the <code>libstdc++.a</code>
 shared library in a common location which will overwrite the GCC 3.1
 …
 multilib <code>libstdc++.a</code> installed:
 <p>Extract the shared object from each the GCC 3.1 <code>libstdc++.a</code>
+   <p>Extract the shared object from each the GCC 3.1 <code>libstdc++.a</code>
 archive:
 <pre>   % ar -x libstdc++.a libstdc++.so.4
 </pre>
 <p>Enable the <code>F_LOADONLY</code> flag so that the shared object will be
+<pre class="example">        % ar -x libstdc++.a libstdc++.so.4
+     </pre>
+   <p>Enable the <code>F_LOADONLY</code> flag so that the shared object will be
 available for runtime dynamic loading, but not linking:
 <pre>   % strip -e libstdc++.so.4
 </pre>
 <p>Archive the runtime-only shared object in the GCC 3.2
+<pre class="example">        % strip -e libstdc++.so.4
+     </pre>
+   <p>Archive the runtime-only shared object in the GCC 3.2
 <code>libstdc++.a</code> archive:
 <pre>   % ar -q libstdc++.a libstdc++.so.4
 </pre>
 <p>Linking executables and shared libraries may produce warnings of
+<pre class="example">        % ar -q libstdc++.a libstdc++.so.4
+     </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
 …
 executable.
 <p>AIX 4.3 utilizes a "large format" archive to support both 32-bit and
+   <p>AIX 4.3 utilizes a "large format" archive to support both 32-bit and
 -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.
 …
 routines is shipped with AIX 4.3.2 and above.
 <p>Some versions of the AIX binder (linker) can fail with a relocation
+   <p>Some versions of the AIX binder (linker) can fail with a relocation
 overflow severe error when the <code>-bbigtoc</code> option is used to link
 GCC-produced object files into an executable that overflows the TOC.  A fix
 …
 website as PTF U455193.
 <p>The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
+   <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
 …
 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
+   <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
 …
 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
+   <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., <code>.</code>  vs <code>,</code> for
 …
 environment variable to <code>C</code> or <code>En_US</code>.
 <p>By default, GCC for AIX 4.1 and above produces code that can be used on
+   <p>By default, GCC for AIX 4.1 and above produces code that can be used on
 both Power or PowerPC processors.
+<p>A default can be specified with the <code>-mcpu=<var>cpu_type</var></code>
+switch and using the configure option <code>--with-cpu-<var>cpu_type</var></code>.
+<hr />
+<h2><a name="TOC40"><a name="m32r-*-elf"></a>m32r-*-elf</h2>
+<p>Mitsubishi M32R processor.
+   <p>A default can be specified with the <code>-mcpu=</code><var>cpu_type</var><code></code>
+switch and using the configure option <code>--with-cpu-</code><var>cpu_type</var><code></code>.
+   <hr />
+<h3 class="heading"><a name="TOC29"></a><a name="ip2k-*-elf"></a>ip2k-*-elf</h3>
+<p>Ubicom IP2022 micro controller.
+This configuration is intended for embedded systems.
+There are no standard Unix configurations.
+   <p>Use <code>configure --target=ip2k-elf --enable-languages=c</code> to configure GCC.
+   <hr />
+<h3 class="heading"><a name="TOC30"></a><a name="m32r-*-elf"></a>m32r-*-elf</h3>
+<p>Renesas M32R processor.
 This configuration is intended for embedded systems.
+<hr />
+<h2><a name="TOC41"><a name="m68000-hp-bsd"></a>m68000-hp-bsd</h2>
+<p>HP 9000 series 200 running BSD.  Note that the C compiler that comes
+   <hr />
+<h3 class="heading"><a name="TOC31"></a><a name="m68000-hp-bsd"></a>m68000-hp-bsd</h3>
+<p>Support for this system is obsoleted in GCC 3.3.
+   <p>HP 9000 series 200 running BSD.  Note that the C compiler that comes
 with this system cannot compile GCC; contact <a href="mailto:law@cygnus.com">law@cygnus.com</a>
 to get binaries of GCC for bootstrapping.
 <hr />
 <h2><a name="TOC42"><a name="m6811-elf"></a>m6811-elf</h2>
+   <hr />
+<h3 class="heading"><a name="TOC32"></a><a name="m6811-elf"></a>m6811-elf</h3>
 <p>Motorola 68HC11 family micro controllers.  These are used in embedded
 applications.  There are no standard Unix configurations.
 <hr />
 <h2><a name="TOC43"><a name="m6812-elf"></a>m6812-elf</h2>
+   <hr />
+<h3 class="heading"><a name="TOC33"></a><a name="m6812-elf"></a>m6812-elf</h3>
 <p>Motorola 68HC12 family micro controllers.  These are used in embedded
 applications.  There are no standard Unix configurations.
+<hr />
+<h2><a name="TOC44"><a name="m68k-altos"></a>m68k-altos</h2>
+<p>Altos 3068.  This configuration is obsoleted in GCC 3.1.
+<p>You must use the GNU assembler, linker and debugger.
+Also, you must fix a kernel bug.
+<hr />
+<h2><a name="TOC45"><a name="m68k-apple-aux"></a>m68k-apple-aux</h2>
+<p>Apple Macintosh running A/UX.
+This configuration is obsoleted in GCC 3.1.
+<p>You may configure GCC  to use either the system assembler and
+linker or the GNU assembler and linker.  You should use the GNU configuration
+if you can, especially if you also want to use G++.  You enable
+that configuration with the <code>--with-gnu-as</code> and <code>--with-gnu-ld</code>
+options to <code>configure</code>.
+<p>Note the C compiler that comes
+with this system cannot compile GCC.  You can find binaries of GCC
+for bootstrapping on <code>jagubox.gsfc.nasa.gov</code>.
+You will also a patched version of <code>/bin/ld</code> there that
+raises some of the arbitrary limits found in the original.
+<hr />
+<h2><a name="TOC46"><a name="m68k-att-sysv"></a>m68k-att-sysv</h2>
+<p>AT&amp;T 3b1, a.k.a. 7300 PC.  This version of GCC cannot
+   <hr />
+<h3 class="heading"><a name="TOC34"></a><a name="m68k-att-sysv"></a>m68k-att-sysv</h3>
+<p>Support for this system is obsoleted in GCC 3.3.
+   <p>AT&amp;T 3b1, a.k.a. 7300 PC.  This version of GCC cannot
 be compiled with the system C compiler, which is too buggy.
 You will need to get a previous version of GCC and use it to
 bootstrap.  Binaries are available from the OSU-CIS archive, at
+<a href="ftp://archive.cis.ohio-state.edu/pub/att7300/">ftp://archive.cis.ohio-state.edu/pub/att7300/</a>.
+<hr />
+<h2><a name="TOC47"><a name="m68k-bull-sysv"></a>m68k-bull-sysv</h2>
+<p>Bull DPX/2 series 200 and 300 with BOS-2.00.45 up to BOS-2.01.
+This configuration is obsoleted in GCC 3.1.
+<p>GCC works
+either with native assembler or GNU assembler.  You can use
+GNU assembler with native COFF generation by providing <code>--with-gnu-as</code> to
+the configure script or use GNU assembler with stabs-in-COFF encapsulation
+by providing <code>--with-gnu-as --stabs</code>.  For any problem with the native
+assembler or for availability of the DPX/2 port of GAS, contact
+<a href="mailto:F.Pierresteguy@frcl.bull.fr">F.Pierresteguy@frcl.bull.fr</a>.
+<hr />
+<h2><a name="TOC48"><a name="m68k-crds-unos"></a>m68k-crds-unos</h2>
+<p>Use <code>configure unos</code> for building on Unos.
+<p>The Unos assembler is named <code>casm</code> instead of <code>as</code>.  For some
+<a href="ftp://ftp.uu.net/systems/att7300/">ftp://ftp.uu.net/systems/att7300/</a>.
+   <hr />
+<h3 class="heading"><a name="TOC35"></a><a name="m68k-crds-unos"></a>m68k-crds-unos</h3>
+<p>Support for this system is obsoleted in GCC 3.3.
+   <p>Use <code>configure unos</code> for building on Unos.
+   <p>The Unos assembler is named <code>casm</code> instead of <code>as</code>.  For some
 strange reason linking <code>/bin/as</code> to <code>/bin/casm</code> changes the
 behavior, and does not work.  So, when installing GCC, you should
 …
 the passes of GCC are installed:
 <pre>#!/bin/sh
 casm $*
 </pre>
 <p>The default Unos library is named <code>libunos.a</code> instead of
+<pre class="example">     #!/bin/sh
+     casm $*
+     </pre>
+   <p>The default Unos library is named <code>libunos.a</code> instead of
 <code>libc.a</code>.  To allow GCC to function, either change all
 references to <code>-lc</code> in <code>gcc.c</code> to <code>-lunos</code> or link
 <code>/lib/libc.a</code> to <code>/lib/libunos.a</code>.
 <p>When compiling GCC with the standard compiler, to overcome bugs in
+   <p>When compiling GCC with the standard compiler, to overcome bugs in
 the support of <code>alloca</code>, do not use <code>-O</code> when making stage 2.
 Then use the stage 2 compiler with <code>-O</code> to make the stage 3
 …
 and compare that with stage 3 to verify proper compilation.
 <p>(Perhaps simply defining <code>ALLOCA</code> in <code>x-crds</code> as described in
+   <p>(Perhaps simply defining <code>ALLOCA</code> in <code>x-crds</code> as described in
 the comments there will make the above paragraph superfluous.  Please
 inform us of whether this works.)
 <p>Unos uses memory segmentation instead of demand paging, so you will need
+   <p>Unos uses memory segmentation instead of demand paging, so you will need
 a lot of memory.  5 Mb is barely enough if no other tasks are running.
 If linking <code>cc1</code> fails, try putting the object files into a library
 and linking from that library.
 <hr />
 <h2><a name="TOC49"><a name="m68k-hp-hpux"></a>m68k-hp-hpux</h2>
+   <hr />
+<h3 class="heading"><a name="TOC36"></a><a name="m68k-hp-hpux"></a>m68k-hp-hpux</h3>
 <p>HP 9000 series 300 or 400 running HP-UX.  HP-UX version 8.0 has a bug in
 …
 building <code>libgcc2.a</code>:
 <pre>_floatdisf
 cc1: warning: `-g' option not supported on this version of GCC
 cc1: warning: `-g1' option not supported on this version of GCC
 ./xgcc: Internal compiler error: program as got fatal signal 11
 </pre>
 <p>A patched version of the assembler is available as the file
+<pre class="smallexample">     _floatdisf
+     cc1: warning: `-g' option not supported on this version of GCC
+     cc1: warning: `-g1' option not supported on this version of GCC
+     ./xgcc: Internal compiler error: program as got fatal signal 11
+     </pre>
+   <p>A patched version of the assembler is available as the file
 <a href="ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler">ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler</a>.  If you
 have HP software support, the patch can also be obtained directly from
 HP, as described in the following note:
 <blockquote>
+   <blockquote>
 This is the patched assembler, to patch SR#1653-010439, where the
 assembler aborts on floating point constants.
 <p>The bug is not really in the assembler, but in the shared library
+        <p>The bug is not really in the assembler, but in the shared library
 version of the function "cvtnum(3c)".  The bug on "cvtnum(3c)" is
 SR#4701-078451.  Anyway, the attached assembler uses the archive
 …
 </blockquote>
 <p>This patch is also known as PHCO_4484.
 <p>In addition, if you wish to use gas, you must use
+   <p>This patch is also known as PHCO_4484.
+   <p>In addition, if you wish to use gas, you must use
 gas version 2.1 or later, and you must use the GNU linker version 2.1 or
 later.  Earlier versions of gas relied upon a program which converted the
 …
 you must use gas if you wish to use gdb.
 <p>On HP-UX version 8.05, but not on 8.07 or more recent versions, the
+   <p>On HP-UX version 8.05, but not on 8.07 or more recent versions, the
 <code>fixproto</code> shell script triggers a bug in the system shell.  If you
 encounter this problem, upgrade your operating system or use BASH (the
 …
 program to report an error of the form:
 <pre>./fixproto: sh internal 1K buffer overflow
 </pre>
 <p>To fix this, you can also change the first line of the fixproto script
+<pre class="example">     ./fixproto: sh internal 1K buffer overflow
+     </pre>
+   <p>To fix this, you can also change the first line of the fixproto script
 to look like:
+<pre>#!/bin/ksh
+</pre>
+<hr />
+<h2><a name="TOC50"><a name="m68k-*-nextstep*"></a>m68k-*-nextstep*</h2>
+<p>These configurations are obsoleted in GCC 3.1.
+<p>Current GCC versions probably do not work on version 2 of the NeXT
+operating system.
+<p>On NeXTStep 3.0, the Objective-C compiler does not work, due,
+apparently, to a kernel bug that it happens to trigger.  This problem
+does not happen on 3.1.
+<p>You absolutely <strong>must</strong> use GNU sed and GNU make on this platform.
+<p>On NeXTSTEP 3.x where x &lt; 3 the build of GCC will abort during
+stage1 with an error message like this:
+<pre>  _eh
+  /usr/tmp/ccbbsZ0U.s:987:Unknown pseudo-op: .section
+  /usr/tmp/ccbbsZ0U.s:987:Rest of line ignored. 1st junk character
+  valued 95 (_).
+</pre>
+<p>The reason for this is the fact that NeXT's assembler for these
+versions of the operating system does not support the <code>.section</code>
+pseudo op that's needed for full C++ exception functionality.
+<p>As NeXT's assembler is a derived work from GNU as, a free
+replacement that does can be obtained at
+<a href="ftp://ftp.next.peak.org:/next-ftp/next/apps/devtools/as.3.3.NIHS.s.tar.gz">ftp://ftp.next.peak.org:/next-ftp/next/apps/devtools/as.3.3.NIHS.s.tar.gz</a>.
+<p>If you try to build the integrated C++ &amp; C++ runtime libraries on this system
+you will run into trouble with include files.  The way to get around this is
+to use the following sequence.  Note you must have write permission to
+the directory <var>prefix</var> you specified in the configuration process of GCC
+for this sequence to work.
+<pre>  cd bld-gcc
+  make all-texinfo all-bison all-byacc all-binutils all-gas all-ld
+  cd gcc
+  make bootstrap
+  make install-headers-tar
+  cd ..
+  make bootstrap3
+</pre>
+<hr />
+<h2><a name="TOC51"><a name="m68k-ncr-*"></a>m68k-ncr-*</h2>
+<p>On the Tower models 4<var>n</var>0 and 6<var>n</var>0, by default a process is not
+<pre class="example">     #!/bin/ksh
+     </pre>
+   <hr />
+<h3 class="heading"><a name="TOC37"></a><a name="m68k-ncr-*"></a>m68k-ncr-*</h3>
+<p>Support for this system is obsoleted in GCC 3.3.
+   <p>On the Tower models 4<var>n</var>0 and 6<var>n</var>0, by default a process is not
 allowed to have more than one megabyte of memory.  GCC cannot compile
 itself (or many other programs) with <code>-O</code> in that much memory.
 <p>To solve this problem, reconfigure the kernel adding the following line
+   <p>To solve this problem, reconfigure the kernel adding the following line
 to the configuration file:
+<pre>MAXUMEM = 4096
+</pre>
+<hr />
+<h2><a name="TOC52"><a name="m68k-sun"></a>m68k-sun</h2>
+<p>Sun 3.  We do not provide a configuration file to use the Sun FPA by
+<pre class="smallexample">     MAXUMEM = 4096
+     </pre>
+   <hr />
+<h3 class="heading"><a name="TOC38"></a><a name="m68k-sun"></a>m68k-sun</h3>
+<p>Support for this system is obsoleted in GCC 3.3.
+   <p>Sun 3.  We do not provide a configuration file to use the Sun FPA by
 default, because programs that establish signal handlers for floating
 point traps inherently cannot work with the FPA.
+<hr />
+<h2><a name="TOC53"><a name="m68k-sun-sunos4.1.1"></a>m68k-sun-sunos4.1.1</h2>
+<p>It is reported that you may need the GNU assembler on this platform.
+<hr />
+<h2><a name="TOC54"><a name="m88k-*-svr3"></a>m88k-*-svr3</h2>
+<p>Motorola m88k running the AT&amp;T/Unisoft/Motorola V.3 reference port.
+These configurations are obsoleted in GCC 3.1.
+<p>These systems tend to use the Green Hills C, revision 1.8.5, as the
+standard C compiler.  There are apparently bugs in this compiler that
+result in object files differences between stage 2 and stage 3.  If this
+happens, make the stage 4 compiler and compare it to the stage 3
+compiler.  If the stage 3 and stage 4 object files are identical, this
+suggests you encountered a problem with the standard C compiler; the
+stage 3 and 4 compilers may be usable.
+<p>It is best, however, to use an older version of GCC for bootstrapping
+if you have one.
+<hr />
+<h2><a name="TOC55"><a name="m88k-*-dgux"></a>m88k-*-dgux</h2>
+<p>Motorola m88k running DG/UX.
+These configurations are obsoleted in GCC 3.1.
+<p>To build 88open BCS native or cross
+compilers on DG/UX, specify the configuration name as
+<code>m88k-*-dguxbcs</code> and build in the 88open BCS software development
+environment.  To build ELF native or cross compilers on DG/UX, specify
+<code>m88k-*-dgux</code> and build in the DG/UX ELF development environment.
+You set the software development environment by issuing
+<code>sde-target</code> command and specifying either <code>m88kbcs</code> or
+<code>m88kdguxelf</code> as the operand.
+<p>If you do not specify a configuration name, <code>configure</code> guesses the
+configuration based on the current software development environment.
+<hr />
+<h2><a name="TOC56"><a name="m88k-tektronix-sysv3"></a>m88k-tektronix-sysv3</h2>
+<p>Tektronix XD88 running UTekV 3.2e.
+These configurations are obsoleted in GCC 3.1.
+<p>Do not turn on
+optimization while building stage1 if you bootstrap with
+the buggy Green Hills compiler.  Also, the bundled LAI
+System V NFS is buggy so if you build in an NFS mounted
+directory, start from a fresh reboot, or avoid NFS all together.
+Otherwise you may have trouble getting clean comparisons
+between stages.
+<hr />
+<h2><a name="TOC57"><a name="mips-*-*"></a>mips-*-*</h2>
+<p>If you use the 1.31 version of the MIPS assembler (such as was shipped
+with Ultrix 3.1), you will need to use the <code>-fno-delayed-branch</code> switch
+when optimizing floating point code.  Otherwise, the assembler will
+complain when the GCC compiler fills a branch delay slot with a
+floating point instruction, such as <code>add.d</code>.
+   <hr />
+<h3 class="heading"><a name="TOC39"></a><a name="m68k-sun-sunos4.1.1"></a>m68k-sun-sunos4.1.1</h3>
+<p>Support for this system is obsoleted in GCC 3.3.
+   <p>It is reported that you may need the GNU assembler on this platform.
+   <hr />
+<h3 class="heading"><a name="TOC40"></a><a name="mips-*-*"></a>mips-*-*</h3>
 <p>If on a MIPS system you get an error message saying "does not have gp
 …
 stop such warnings by installing the GNU linker.
 <p>It would be nice to extend GAS to produce the gp tables, but they are
+   <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>Users have reported some problems with version 2.0 of the MIPS
+compiler tools that were shipped with Ultrix 4.1.  Version 2.10
+which came with Ultrix 4.2 seems to work fine.
+<p>Users have also reported some problems with version 2.20 of the
+MIPS compiler tools that were shipped with RISC/os 4.x.  The earlier
+version 2.11 seems to work fine.
+<p>Some versions of the MIPS linker will issue an assertion failure
+when linking code that uses <code>alloca</code> against shared
+libraries on RISC-OS 5.0, and DEC's OSF/1 systems.  This is a bug
+in the linker, that is supposed to be fixed in future revisions.
+To protect against this, GCC passes <code>-non_shared</code> to the
+linker unless you pass an explicit <code>-shared</code> or
+<code>-call_shared</code> switch.
+<h2><a name="TOC58"><a name="mips-mips-bsd"></a>mips-mips-bsd</h2>
+<p>MIPS machines running the MIPS operating system in BSD mode.
+These configurations are obsoleted in GCC 3.1.
+<p>It's possible that some old versions of the system lack the functions
+<code>memcpy</code>, <code>memmove</code>, <code>memcmp</code>, and <code>memset</code>.  If your
+system lacks these, you must remove or undo the definition of
+<code>TARGET_MEM_FUNCTIONS</code> in <code>mips-bsd.h</code>.
+<p>If you use the MIPS C compiler to bootstrap, it may be necessary
+to increase its table size for switch statements with the
+<code>-Wf,-XNg1500</code> option.  If you use the <code>-O2</code>
+optimization option, you also need to use <code>-Olimit 3000</code>.
+Both of these options are automatically generated in the
+<code>Makefile</code> that the shell script <code>configure</code> builds.
+If you override the <code>CC</code> make variable and use the MIPS
+compilers, you may need to add <code>-Wf,-XNg1500 -Olimit 3000</code>.
+<hr />
+<h2><a name="TOC59"><a name="mips-dec-*"></a>mips-dec-*</h2>
+<p>These configurations are obsoleted in GCC 3.1.
+<p>MIPS-based DECstations can support three different personalities:
+Ultrix, DEC OSF/1, and OSF/rose.  (Alpha-based DECstation products have
+a configuration name beginning with <code>alpha*-dec</code>.)  To configure GCC
+for these platforms use the following configurations:
+<dl>
+<dt><code>mips-dec-ultrix</code>
+<dd>Ultrix configuration.
+<br><dt><code>mips-dec-osf1</code>
+<dd>DEC's version of OSF/1.
+<br><dt><code>mips-dec-osfrose</code>
+<dd>Open Software Foundation reference port of OSF/1 which uses the
+OSF/rose object file format instead of ECOFF.  Normally, you
+would not select this configuration.
+</dl>
+<p>If you use the MIPS C compiler to bootstrap, it may be necessary
+to increase its table size for switch statements with the
+<code>-Wf,-XNg1500</code> option.  If you use the <code>-O2</code>
+optimization option, you also need to use <code>-Olimit 3000</code>.
+Both of these options are automatically generated in the
+<code>Makefile</code> that the shell script <code>configure</code> builds.
+If you override the <code>CC</code> make variable and use the MIPS
+compilers, you may need to add <code>-Wf,-XNg1500 -Olimit 3000</code>.
+<hr />
+<h2><a name="TOC60"><a name="mips-mips-riscos*"></a>mips-mips-riscos*</h2>
+<p>These configurations are obsoleted in GCC 3.1.
+<p>If you use the MIPS C compiler to bootstrap, it may be necessary
+to increase its table size for switch statements with the
+<code>-Wf,-XNg1500</code> option.  If you use the <code>-O2</code>
+optimization option, you also need to use <code>-Olimit 3000</code>.
+Both of these options are automatically generated in the
+<code>Makefile</code> that the shell script <code>configure</code> builds.
+If you override the <code>CC</code> make variable and use the MIPS
+compilers, you may need to add <code>-Wf,-XNg1500 -Olimit 3000</code>.
+<p>MIPS computers running RISC-OS can support four different
+personalities: default, BSD 4.3, System V.3, and System V.4
+(older versions of RISC-OS don't support V.4).  To configure GCC
+for these platforms use the following configurations:
+<dl>
+<dt><code>mips-mips-riscos<var>rev</var></code>
+<dd>Default configuration for RISC-OS, revision <var>rev</var>.
+<br><dt><code>mips-mips-riscos<var>rev</var>bsd</code>
+<dd>BSD 4.3 configuration for RISC-OS, revision <var>rev</var>.
+<br><dt><code>mips-mips-riscos<var>rev</var>sysv4</code>
+<dd>System V.4 configuration for RISC-OS, revision <var>rev</var>.
+<hr />
+<br><dt><code>mips-mips-riscos<var>rev</var>sysv</code>
+<dd>System V.3 configuration for RISC-OS, revision <var>rev</var>.
+</dl>
+<p>The revision <code>rev</code> mentioned above is the revision of
+RISC-OS to use.  You must reconfigure GCC when going from a
+RISC-OS revision 4 to RISC-OS revision 5.  This has the effect of
+avoiding a linker bug.
+<hr />
+<h2><a name="TOC61"><a name="mips-sgi-irix4"></a>mips-sgi-irix4</h2>
+<p>This configuration is obsoleted in GCC 3.1.
+<p>In order to compile GCC on an SGI running IRIX 4, the "c.hdr.lib"
+option must be installed from the CD-ROM supplied from Silicon Graphics.
+This is found on the 2nd CD in release 4.0.1.
+<p>On IRIX version 4.0.5F, and perhaps on some other versions as well,
+there is an assembler bug that reorders instructions incorrectly.  To
+work around it, specify the target configuration
+<code>mips-sgi-irix4loser</code>.  This configuration inhibits assembler
+optimization.
+<p>In a compiler configured with target <code>mips-sgi-irix4</code>, you can turn
+off assembler optimization by using the <code>-noasmopt</code> option.  This
+compiler option passes the option <code>-O0</code> to the assembler, to
+inhibit reordering.
+<p>The <code>-noasmopt</code> option can be useful for testing whether a problem
+is due to erroneous assembler reordering.  Even if a problem does not go
+away with <code>-noasmopt</code>, it may still be due to assembler
+reordering--perhaps GCC itself was miscompiled as a result.
+<p>You may get the following warning on IRIX 4 platforms, it can be safely
+ignored.
+<pre>  warning: foo.o does not have gp tables for all its sections.
+</pre>
+<hr />
+<h2><a name="TOC62"><a name="mips-sgi-irix5"></a>mips-sgi-irix5</h2>
+   <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 <code>mips*-*-*</code> use the generic implementation instead.  You can also
+configure for <code>mipsel-elf</code> as a workaround.  The
+<code>mips*-*-linux*</code> target continues to use the MIPS II routines.  More
+work on this is expected in future releases.
+   <hr />
+<h3 class="heading"><a name="TOC41"></a><a name="mips-sgi-irix5"></a>mips-sgi-irix5</h3>
 <p>This configuration has considerable problems, which will be fixed in a
 future release.
 <p>In order to compile GCC on an SGI running IRIX 5, the "compiler_dev.hdr"
+   <p>In order to compile GCC on an SGI running IRIX 5, the "compiler_dev.hdr"
 subsystem must be installed from the IDO CD-ROM supplied by Silicon
 Graphics.  It is also available for download from
 <a href="http://www.sgi.com/developers/devtools/apis/ido.html">http://www.sgi.com/developers/devtools/apis/ido.html</a>.
 <p><code>make compare</code> may fail on version 5 of IRIX unless you add
+   <p><code>make compare</code> may fail on version 5 of IRIX unless you add
 <code>-save-temps</code> to <code>CFLAGS</code>.  On these systems, the name of the
 assembler input file is stored in the object file, and that makes
 …
 <code>.s</code> files after each series of compilations.
 <p>If you use the MIPS C compiler to bootstrap, it may be necessary
+   <p>If you use the MIPS C compiler to bootstrap, it may be necessary
 to increase its table size for switch statements with the
 <code>-Wf,-XNg1500</code> option.  If you use the <code>-O2</code>
 optimization option, you also need to use <code>-Olimit 3000</code>.
 <p>To enable debugging under IRIX 5, you must use GNU <code>as</code> 2.11.2
+   <p>To enable debugging under IRIX 5, you must use GNU <code>as</code> 2.11.2
 or later,
 and use the <code>--with-gnu-as</code> configure option when configuring GCC.
 …
 which will be included in the next release of binutils.
 <p>When building GCC, the build process loops rebuilding <code>cc1</code> over
+   <p>When building GCC, the build process loops rebuilding <code>cc1</code> over
 and over again.  This happens on <code>mips-sgi-irix5.2</code>, and possibly
 other platforms.  It has been reported that this is a known bug in the
 …
 not have GNU <code>make</code> available.
 <hr />
 <h2><a name="TOC63"><a name="mips-sgi-irix6"></a>mips-sgi-irix6</h2>
+   <hr />
+<h3 class="heading"><a name="TOC42"></a><a name="mips-sgi-irix6"></a>mips-sgi-irix6</h3>
 <p>If you are using IRIX <code>cc</code> as your bootstrap compiler, you must
 …
 resulting object file.  The output should look like:
 <pre>test.o: ELF N32 MSB <small>...</small>
 </pre>
 <p>If you see:
 <pre>test.o: ELF 32-bit MSB <small>...</small>
 </pre>
 <p>or
 <pre>test.o: ELF 64-bit MSB <small>...</small>
 </pre>
 <p>then your version of <code>cc</code> uses the O32 or N64 ABI by default.  You
+<pre class="example">     test.o: ELF N32 MSB ...
+     </pre>
+   <p>If you see:
+<pre class="example">     test.o: ELF 32-bit MSB ...
+     </pre>
+   <p>or
+<pre class="example">     test.o: ELF 64-bit MSB ...
+     </pre>
+   <p>then your version of <code>cc</code> uses the O32 or N64 ABI by default.  You
 should set the environment variable <code>CC</code> to <code>cc -n32</code>
 before configuring GCC.
 <p>If you want the resulting <code>gcc</code> to run on old 32-bit systems
+   <p>If you want the resulting <code>gcc</code> to run on old 32-bit systems
 with the MIPS R4400 CPU, you need to ensure that only code for the mips3
 instruction set architecture (ISA) is generated.  While GCC 3.x does
 …
 all on mips3-only systems.  For the test program above, you should see:
 <pre>test.o: ELF N32 MSB mips-3 <small>...</small>
 </pre>
 <p>If you get:
 <pre>test.o: ELF N32 MSB mips-4 <small>...</small>
 </pre>
 <p>instead, you should set the environment variable <code>CC</code> to <code>cc
+<pre class="example">     test.o: ELF N32 MSB mips-3 ...
+     </pre>
+   <p>If you get:
+<pre class="example">     test.o: ELF N32 MSB mips-4 ...
+     </pre>
+   <p>instead, you should set the environment variable <code>CC</code> to <code>cc
 -n32 -mips3</code> or <code>gcc -mips3</code> respectively before configuring GCC.
 <p>GCC on IRIX 6 is usually built to support both the N32 and N64 ABIs.  If
+   <p>GCC on IRIX 6 is usually built to support both the N32 and N64 ABIs.  If
 you build GCC on a system that doesn't have the N64 libraries installed,
 you need to configure with <code>--disable-multilib</code> so GCC doesn't
 …
 have the 64-bit libraries installed.
 <p>You must <em>not</em> use GNU <code>as</code> (which isn't built anyway as of
+   <p>You must <em>not</em> use GNU <code>as</code> (which isn't built anyway as of
 binutils 2.11.2) on IRIX 6 platforms; doing so will only cause problems.
 <p>GCC does not currently support generating O32 ABI binaries in the
+   <p>GCC does not currently support generating O32 ABI binaries in the
 <code>mips-sgi-irix6</code> configurations.  It is possible to create a GCC
 with O32 ABI only support by configuring it for the <code>mips-sgi-irix5</code>
 …
 expected that O32 ABI support will be available again in a future release.
 <p>The <code>--enable-threads</code> option doesn't currently work, a patch is
+   <p>The <code>--enable-threads</code> option doesn't currently work, a patch is
 in preparation for a future release.  The <code>--enable-libgcj</code>
 option is disabled by default: IRIX 6 uses a very low default limit
 …
 <code>systune</code> command to do this.
 <p>GCC does not correctly pass/return structures which are
+   <p>GCC does not correctly pass/return structures which are
 smaller than 16 bytes and which are not 8 bytes.  The problem is very
 involved and difficult to fix.  It affects a number of other targets also,
 …
 register.
 <p>GCC is consistent with itself, but not consistent with the SGI C compiler
+   <p>GCC is consistent with itself, but not consistent with the SGI C compiler
 (and the SGI supplied runtime libraries), so the only failures that can
 happen are when there are library functions that take/return such
 …
 bug is fixed, GCC contains workarounds for the known affected functions.
 <p>See <a href="http://freeware.sgi.com/">http://freeware.sgi.com/</a> for more
+   <p>See <a href="http://freeware.sgi.com/">http://freeware.sgi.com/</a> for more
 information about using GCC on IRIX platforms.
+<hr />
+<h2><a name="TOC64"><a name="mips-sony-sysv"></a>mips-sony-sysv</h2>
+<p>Sony MIPS NEWS.  This configuration is obsoleted in GCC 3.1.
+<p>This works in NEWSOS 5.0.1, but not in 5.0.2 (which uses ELF instead of
+COFF).  In particular, the linker does not like the code generated by
+GCC when shared libraries are linked in.
+<hr />
+<h2><a name="TOC65"><a name="ns32k-encore"></a>ns32k-encore</h2>
+<p>This configuration is obsoleted in GCC 3.1.
+<p>Encore ns32000 system.  Encore systems are supported only under BSD.
+<hr />
+<h2><a name="TOC66"><a name="ns32k-*-genix"></a>ns32k-*-genix</h2>
+<p>National Semiconductor ns32000 system. This configuration is obsoleted
+in GCC 3.1.
+<p>Genix has bugs in <code>alloca</code> and <code>malloc</code>; you must get the
+compiled versions of these from GNU Emacs.
+<hr />
+<h2><a name="TOC67"><a name="ns32k-sequent"></a>ns32k-sequent</h2>
+<p>This configuration is obsoleted in GCC 3.1.
+<p>Go to the Berkeley universe before compiling.
+<hr />
+<h2><a name="TOC68"><a name="ns32k-utek"></a>ns32k-utek</h2>
+<p>UTEK ns32000 system ("merlin").  This configuration is obsoleted in
+GCC 3.1.
+<p>The C compiler that comes with this system cannot compile GCC; contact
+<code>tektronix!reed!mason</code> to get binaries of GCC for bootstrapping.
+<hr />
+<h2><a name="TOC69"><a name="powerpc*-*-*"></a>powerpc-*-*</h2>
+<p>You can specify a default version for the <code>-mcpu=<var>cpu_type</var></code>
+switch by using the configure option <code>--with-cpu-<var>cpu_type</var></code>.
+<hr />
+<h2><a name="TOC70"><a name="powerpc-*-darwin*"></a>powerpc-*-darwin*</h2>
+   <hr />
+<h3 class="heading"><a name="TOC43"></a><a name="powerpc*-*-*"></a>powerpc-*-*</h3>
+<p>You can specify a default version for the <code>-mcpu=</code><var>cpu_type</var><code></code>
+switch by using the configure option <code>--with-cpu-</code><var>cpu_type</var><code></code>.
+   <hr />
+<h3 class="heading"><a name="TOC44"></a><a name="powerpc-*-darwin*"></a>powerpc-*-darwin*</h3>
 <p>PowerPC running Darwin (Mac OS X kernel).
+<p>GCC 3.0 does not support Darwin, but 3.1 and later releases will work.
+<p>Pre-installed versions of Mac OS X may not include any developer tools,
+   <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://www.opensource.apple.com/projects/darwin">http://www.opensource.apple.com/projects/darwin</a> (free
+<a href="http://developer.apple.com/tools/compilers.html">http://developer.apple.com/tools/compilers.html</a> (free
 registration required).
+<p>Versions of the assembler prior to "cctools-364" cannot handle the
+-argument form of <code>rlwinm</code> and related mask-using instructions.  Darwin
+.3 (Mac OS X 10.0) uses cctools-353 for instance.  To get cctools-364,
+check out <code>cctools</code> with tag <code>Apple-364</code>, build it, and
+install the assembler as <code>usr/bin/as</code>.  See
+<a href="http://www.opensource.apple.com/tools/cvs/docs.html">http://www.opensource.apple.com/tools/cvs/docs.html</a> for details.
+<p>Also, the default stack limit of 512K is too small, and a bootstrap will
+typically fail when self-compiling <code>expr.c</code>.  Set the stack to 800K
+or more, for instance by doing <code>limit stack 800</code>.  It's also
+convenient to use the GNU preprocessor instead of Apple's during the
+first stage of bootstrapping; this is automatic when doing <code>make
+bootstrap</code>, but to do it from the toplevel objdir you will need to say
+<code>make CC='cc -no-cpp-precomp' bootstrap</code>.
+<p>Note that the version of GCC shipped by Apple typically includes a
+number of extensions not available in a standard GCC release.  These
+extensions are generally specific to Mac programming.
+<hr />
+<h2><a name="TOC71"><a name="powerpc-*-elf"></a>powerpc-*-elf, powerpc-*-sysv4</h2>
+   <p>The default stack limit of 512K is too small, which may cause compiles
+to fail with 'Bus error'.  Set the stack larger, for instance
+by doing <code>limit stack 800</code>.  It's a good idea to use the GNU
+preprocessor instead of Apple's <code>cpp-precomp</code> during the first stage of
+bootstrapping; this is automatic when doing <code>make bootstrap</code>, but
+to do it from the toplevel objdir you will need to say <code>make
+CC='cc -no-cpp-precomp' bootstrap</code>.
+   <p>The version of GCC shipped by Apple typically includes a number of
+extensions not available in a standard GCC release.  These extensions
+are generally specific to Mac programming.
+   <hr />
+<h3 class="heading"><a name="TOC45"></a><a name="powerpc-*-elf"></a>powerpc-*-elf, powerpc-*-sysv4</h3>
 <p>PowerPC system in big endian mode, running System V.4.
 <hr />
 <h2><a name="TOC72"><a name="powerpc-*-linux-gnu*"></a>powerpc-*-linux-gnu*</h2>
+   <hr />
+<h3 class="heading"><a name="TOC46"></a><a name="powerpc-*-linux-gnu*"></a>powerpc-*-linux-gnu*</h3>
 <p>You will need
 …
 or newer for a working GCC.
 <hr />
 <h2><a name="TOC73"><a name="powerpc-*-netbsd*"></a>powerpc-*-netbsd*</h2>
+   <hr />
+<h3 class="heading"><a name="TOC47"></a><a name="powerpc-*-netbsd*"></a>powerpc-*-netbsd*</h3>
 <p>PowerPC system in big endian mode running NetBSD.  To build the
 documentation you will need Texinfo version 4.1 (NetBSD 1.5.1 included
+documentation you will need Texinfo version 4.2 (NetBSD 1.5.1 included
 Texinfo version 3.12).
 <hr />
 <h2><a name="TOC74"><a name="powerpc-*-eabiaix"></a>powerpc-*-eabiaix</h2>
+   <hr />
+<h3 class="heading"><a name="TOC48"></a><a name="powerpc-*-eabiaix"></a>powerpc-*-eabiaix</h3>
 <p>Embedded PowerPC system in big endian mode with <code>-mcall-aix</code> selected as
 the default.
 <hr />
 <h2><a name="TOC75"><a name="powerpc-*-eabisim"></a>powerpc-*-eabisim</h2>
+   <hr />
+<h3 class="heading"><a name="TOC49"></a><a name="powerpc-*-eabisim"></a>powerpc-*-eabisim</h3>
 <p>Embedded PowerPC system in big endian mode for use in running under the
 PSIM simulator.
 <hr />
 <h2><a name="TOC76"><a name="powerpc-*-eabi"></a>powerpc-*-eabi</h2>
+   <hr />
+<h3 class="heading"><a name="TOC50"></a><a name="powerpc-*-eabi"></a>powerpc-*-eabi</h3>
 <p>Embedded PowerPC system in big endian mode.
 <hr />
 <h2><a name="TOC77"><a name="powerpcle-*-elf"></a>powerpcle-*-elf, powerpcle-*-sysv4</h2>
+   <hr />
+<h3 class="heading"><a name="TOC51"></a><a name="powerpcle-*-elf"></a>powerpcle-*-elf, powerpcle-*-sysv4</h3>
 <p>PowerPC system in little endian mode, running System V.4.
 <hr />
 <h2><a name="TOC78"><a name="powerpcle-*-eabisim"></a>powerpcle-*-eabisim</h2>
+   <hr />
+<h3 class="heading"><a name="TOC52"></a><a name="powerpcle-*-eabisim"></a>powerpcle-*-eabisim</h3>
 <p>Embedded PowerPC system in little endian mode for use in running under
 the PSIM simulator.
 <hr />
 <h2><a name="TOC79"><a name="powerpcle-*-eabi"></a>powerpcle-*-eabi</h2>
+   <hr />
+<h3 class="heading"><a name="TOC53"></a><a name="powerpcle-*-eabi"></a>powerpcle-*-eabi</h3>
 <p>Embedded PowerPC system in little endian mode.
+<hr />
+<h2><a name="TOC80"><a name="powerpcle-*-winnt"></a>powerpcle-*-winnt, powerpcle-*-pe</h2>
+<p>PowerPC system in little endian mode running Windows NT.
+<hr />
+<h2><a name="TOC81"><a name="romp-*-aos"></a>romp-*-aos, romp-*-mach</h2>
+<p>These configurations are obsoleted in GCC 3.1.
+<p>We recommend you compile GCC with an earlier version of itself; if you
+compile GCC with <code>hc</code>, the Metaware compiler, it will work, but
+you will get mismatches between the stage 2 and stage 3 compilers in
+various files.  These errors are minor differences in some
+floating-point constants and can be safely ignored; the stage 3 compiler
+is correct.
+<hr />
+<h2><a name="TOC82"><a name="s390-*-linux*"></a>s390-*-linux*</h2>
+   <hr />
+<h3 class="heading"><a name="TOC54"></a><a name="s390-*-linux*"></a>s390-*-linux*</h3>
 <p>S/390 system running Linux for S/390.
 <hr />
 <h2><a name="TOC83"><a name="s390x-*-linux*"></a>s390x-*-linux*</h2>
+   <hr />
+<h3 class="heading"><a name="TOC55"></a><a name="s390x-*-linux*"></a>s390x-*-linux*</h3>
 <p>zSeries system (64-bit) running Linux for zSeries.
 <hr />
 <h2><a name="TOC84"><a name="*-*-solaris2*"></a>*-*-solaris2*</h2>
+   <hr />
+<h3 class="heading"><a name="TOC56"></a><a name="*-*-solaris2*"></a>*-*-solaris2*</h3>
 <p>Sun does not ship a C compiler with Solaris 2.  To bootstrap and install
 …
 <a href="binaries.html">binaries page</a> for details.
+<p>The Solaris 2 <code>/bin/sh</code> will often fail to configure
+<code>libstdc++-v3</code>, <code>boehm-gc</code> or
+<code>libjava</code>.  If you encounter this problem, set <code>CONFIG_SHELL</code> to
+<code>/bin/ksh</code> in your environment before running <code>configure</code>.
+<p>Solaris 2 comes with a number of optional OS packages.  Some of these
+packages are needed to use GCC fully, namely <code>SUNWarc</code>,
+   <p>The Solaris 2 <code>/bin/sh</code> will often fail to configure
+<code>libstdc++-v3</code>, <code>boehm-gc</code> or <code>libjava</code>.  We therefore
+recommend to use the following sequence of commands to bootstrap and
+install GCC:
+<pre class="smallexample">        % CONFIG_SHELL=/bin/ksh
+        % export CONFIG_SHELL
+        % <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>]
+        % gmake bootstrap
+        % gmake install
+     </pre>
+   <p>As explained in the <a href="build.html">build</a> instructions, we recommend
+to use GNU make, which we call <code>gmake</code> here to distinguish it
+from Sun make.
+   <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
 …
 the packages that GCC needs are installed.
 <p>To check whether an optional package is installed, use
+   <p>To check whether an optional package is installed, use
 the <code>pkginfo</code> command.  To add an optional package, use the
 <code>pkgadd</code> command.  For further details, see the Solaris 2
 documentation.
 <p>Trying to use the linker and other tools in
+   <p>Trying to use the linker and other tools in
 <code>/usr/ucb</code> to install GCC has been observed to cause trouble.
 For example, the linker may hang indefinitely.  The fix is to remove
 <code>/usr/ucb</code> from your <code>PATH</code>.
+<p>All releases of GNU binutils prior to 2.11.2 have known bugs on this
+   <p>The build process works more smoothly with the legacy Sun tools so, if you
+have <code>/usr/xpg4/bin</code> in your <code>PATH</code>, we recommend that you place
+<code>/usr/bin</code> before <code>/usr/xpg4/bin</code> for the duration of the build.
+   <p>All releases of GNU binutils prior to 2.11.2 have known bugs on this
 platform.  We recommend the use of GNU binutils 2.11.2 or the vendor
 tools (Sun <code>as</code>, Sun <code>ld</code>).
 <p>Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
+   <p>Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
 newer: <code>g++</code> will complain that types are missing.  These headers assume
 that omitting the type means <code>int</code>; this assumption worked for C89 but
 is wrong for C++, and is now wrong for C99 also.
 <p><code>g++</code> accepts such (invalid) constructs with the option
+   <p><code>g++</code> accepts such (invalid) constructs with the option
 <code>-fpermissive</code>; it
 will assume that any missing type is <code>int</code> (as defined by C89).
 <p>There are patches for Solaris 2.6 (105633-56 or newer for SPARC,
+   <p>There are patches for Solaris 2.6 (105633-56 or newer for SPARC,
 -42 or newer for Intel), Solaris 7 (108376-21 or newer for SPARC,
 -20 for Intel), and Solaris 8 (108652-24 or newer for SPARC,
 -22 for Intel) that fix this bug.
 <hr />
 <h2><a name="TOC85"><a name="sparc-sun-solaris2*"></a>sparc-sun-solaris2*</h2>
+   <hr />
+<h3 class="heading"><a name="TOC57"></a><a name="sparc-sun-solaris2*"></a>sparc-sun-solaris2*</h3>
 <p>When GCC is configured to use binutils 2.11.2 or later the binaries
 …
 information.
 <p>Sun <code>as</code> 4.x is broken in that it cannot cope with long symbol names.
+   <p>Sun <code>as</code> 4.x is broken in that it cannot cope with long symbol names.
 A typical error message might look similar to the following:
 <pre>/usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041: error:
   can't compute value of an expression involving an external symbol.
 </pre>
 <p>This is Sun bug 4237974.  This is fixed with patch 108908-02 for Solaris
+<pre class="smallexample">     /usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041: error:
+       can't compute value of an expression involving an external symbol.
+     </pre>
+   <p>This is Sun bug 4237974.  This is fixed with patch 108908-02 for Solaris
 .6 and has been fixed in later (5.x) versions of the assembler,
 starting with Solaris 7.
 <p>Starting with Solaris 7, the operating system is capable of executing
+   <p>Starting with Solaris 7, the operating system is capable of executing
 -bit SPARC V9 binaries.  GCC 3.1 and later properly supports
 this; the <code>-m64</code> option enables 64-bit code generation.
 …
 machines.
 <p>When configuring on a Solaris 7 or later system that is running a kernel
+   <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
 <code>--disable-multilib</code>, since we will not be able to build the
 -bit target libraries.
 <hr />
 <h2><a name="TOC86"><a name="sparc-sun-solaris2.7"></a>sparc-sun-solaris2.7</h2>
+   <hr />
+<h3 class="heading"><a name="TOC58"></a><a name="sparc-sun-solaris2.7"></a>sparc-sun-solaris2.7</h3>
 <p>Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in
 …
 recommend it only for people who use Sun's compilers.
 <p>Here are some workarounds to this problem:
 <ul>
+   <p>Here are some workarounds to this problem:
+     <ul>
 <li>Do not install Sun patch 107058-01 until after Sun releases a
 complete patch for bug 4210064.  This is the simplest course to take,
 …
 back it out.
 <li>Copy the original, unpatched Solaris 7
+     <li>Copy the original, unpatched Solaris 7
 <code>/usr/ccs/bin/as</code> into
 <code>/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/3.1/as</code>,
 …
 version numbers.
 <li>Install Sun patch 106950-03 (1999-05-25) or later.  Nobody with
+     <li>Install Sun patch 106950-03 (1999-05-25) or later.  Nobody with
 both 107058-01 and 106950-03 installed has reported the bug with GCC
 and Sun's dynamic linker.  This last course of action is riskiest,
 …
 </ul>
+<p>
+   <p>GCC 3.3 triggers a bug in version 5.0 Alpha 03/27/98 of the Sun assembler,
+which causes a bootstrap failure when linking the 64-bit shared version of
+libgcc. A typical error message is:
+<pre class="smallexample">     ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o:
+       symbol &lt;unknown&gt;:  offset 0xffffffff7ec133e7 is non-aligned.
+     </pre>
+   <p>This bug has been fixed in the final 5.0 version of the assembler.
+   <p>
 <hr />
+<h2><a name="TOC87"><a name="sparc-sun-sunos4*"></a>sparc-sun-sunos4*</h2>
+<p>A bug in the SunOS 4 linker will cause it to crash when linking
+<h3 class="heading"><a name="TOC59"></a><a name="sparc-sun-sunos4*"></a>sparc-sun-sunos4*</h3>
+<p>Support for this system is obsoleted in GCC 3.3.
+   <p>A bug in the SunOS 4 linker will cause it to crash when linking
 <code>-fPIC</code> compiled objects (and will therefore not allow you to build
 shared libraries).
 <p>To fix this problem you can either use the most recent version of
+   <p>To fix this problem you can either use the most recent version of
 binutils or get the latest SunOS 4 linker patch (patch ID 100170-10)
 from Sun's patch site.
 <p>Sometimes on a Sun 4 you may observe a crash in the program
+   <p>Sometimes on a Sun 4 you may observe a crash in the program
 <code>genflags</code> or <code>genoutput</code> while building GCC.  This is said to
 be due to a bug in <code>sh</code>.  You can probably get around it by running
 …
 <code>make</code>.
+<hr />
+<h2><a name="TOC88"><a name="sparc-unknown-linux-gnulibc1"></a>sparc-unknown-linux-gnulibc1</h2>
+<p>It has been reported that you might need
+   <hr />
+<h3 class="heading"><a name="TOC60"></a><a name="sparc-unknown-linux-gnulibc1"></a>sparc-unknown-linux-gnulibc1</h3>
+<p>Support for this system is obsoleted in GCC 3.3.
+   <p>It has been reported that you might need
 <a href="ftp://ftp.yggdrasil.com/private/hjl">binutils 2.8.1.0.23</a>
 for this platform, too.
 <hr />
 <h2><a name="TOC89"><a name="sparc-*-linux*"></a>sparc-*-linux*</h2>
+   <hr />
+<h3 class="heading"><a name="TOC61"></a><a name="sparc-*-linux*"></a>sparc-*-linux*</h3>
 <p>GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
 …
 releases mishandled unaligned relocations on <code>sparc-*-*</code> targets.
+<hr />
+<h2><a name="TOC90"><a name="sparc64-*-*"></a>sparc64-*-*</h2>
+<p>GCC version 2.95 is not able to compile code correctly for
+<code>sparc64</code> targets.  Users of the Linux kernel, at least,
+can use the <code>sparc32</code> program to start up a new shell
+invocation with an environment that causes <code>configure</code> to
+recognize (via <code>uname -a</code>) the system as <code>sparc-*-*</code> instead.
+<hr />
+<h2><a name="TOC91"><a name="sparcv9-*-solaris2*"></a>sparcv9-*-solaris2*</h2>
+   <hr />
+<h3 class="heading"><a name="TOC62"></a><a name="sparc64-*-solaris2*"></a>sparc64-*-solaris2*</h3>
 <p>The following compiler flags must be specified in the configure
 step in order to bootstrap this target with the Sun compiler:
+<pre>   % CC="cc -xildoff -xarch=v9" <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>]
+</pre>
+<p><code>-xildoff</code> turns off the incremental linker, and <code>-xarch=v9</code>
+specifies the v9 architecture to the Sun linker and assembler.
+<hr />
+<h2><a name="TOC92"><a name="%23*-*-sysv*"></a>*-*-sysv*</h2>
+<pre class="example">        % CC="cc -xildoff -xarch=v9" <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>]
+     </pre>
+   <p><code>-xildoff</code> turns off the incremental linker, and <code>-xarch=v9</code>
+specifies the SPARC-V9 architecture to the Sun linker and assembler.
+   <hr />
+<h3 class="heading"><a name="TOC63"></a><a name="sparcv9-*-solaris2*"></a>sparcv9-*-solaris2*</h3>
+<p>This is a synonym for sparc64-*-solaris2*.
+   <hr />
+<h3 class="heading"><a name="TOC64"></a><a name="%23*-*-sysv*"></a>*-*-sysv*</h3>
 <p>On System V release 3, you may get this error message
 while linking:
 <pre>ld fatal: failed to write symbol name <var>something</var>
  in strings table for file <var>whatever</var>
 </pre>
 <p>This probably indicates that the disk is full or your ulimit won't allow
+<pre class="smallexample">     ld fatal: failed to write symbol name <var>something</var>
+      in strings table for file <var>whatever</var>
+     </pre>
+   <p>This probably indicates that the disk is full or your ulimit won't allow
 the file to be as large as it needs to be.
 <p>This problem can also result because the kernel parameter <code>MAXUMEM</code>
+   <p>This problem can also result because the kernel parameter <code>MAXUMEM</code>
 is too small.  If so, you must regenerate the kernel and make the value
 much larger.  The default value is reported to be 1024; a value of 32768
 is said to work.  Smaller values may also work.
 <p>On System V, if you get an error like this,
 <pre>/usr/local/lib/bison.simple: In function `yyparse':
 /usr/local/lib/bison.simple:625: virtual memory exhausted
 </pre>
+   <p>On System V, if you get an error like this,
+<pre class="example">     /usr/local/lib/bison.simple: In function `yyparse':
+     /usr/local/lib/bison.simple:625: virtual memory exhausted
+     </pre>
 <p>that too indicates a problem with disk space, ulimit, or <code>MAXUMEM</code>.
 <p>On a System V release 4 system, make sure <code>/usr/bin</code> precedes
+   <p>On a System V release 4 system, make sure <code>/usr/bin</code> precedes
 <code>/usr/ucb</code> in <code>PATH</code>.  The <code>cc</code> command in
 <code>/usr/ucb</code> uses libraries which have bugs.
 <hr />
 <h2><a name="TOC93"><a name="vax-dec-ultrix"></a>vax-dec-ultrix</h2>
+   <hr />
+<h3 class="heading"><a name="TOC65"></a><a name="vax-dec-ultrix"></a>vax-dec-ultrix</h3>
 <p>Don't try compiling with VAX C (<code>vcc</code>).  It produces incorrect code
 in some cases (for example, when <code>alloca</code> is used).
+<hr />
+<h2><a name="TOC94"><a name="we32k-*-*"></a>we32k-*-*</h2>
+<p>These computers are also known as the 3b2, 3b5, 3b20 and other similar
+names.  (However, the 3b1 is actually a 68000.)
+These configurations are obsoleted in GCC 3.1.
+<p>Don't use <code>-g</code> when compiling with the system's compiler.  The
+system's linker seems to be unable to handle such a large program with
+debugging information.
+<p>The system's compiler runs out of capacity when compiling <code>stmt.c</code>
+in GCC.  You can work around this by building <code>cpp</code> in GCC
+first, then use that instead of the system's preprocessor with the
+system's C compiler to compile <code>stmt.c</code>.  Here is how:
+<pre>mv /lib/cpp /lib/cpp.att
+cp cpp /lib/cpp.gnu
+echo '/lib/cpp.gnu -traditional ${1+"$@"}' &gt; /lib/cpp
+chmod +x /lib/cpp
+</pre>
+<p>The system's compiler produces bad code for some of the GCC
+optimization files.  So you must build the stage 2 compiler without
+optimization.  Then build a stage 3 compiler with optimization.
+That executable should work.  Here are the necessary commands:
+<pre>make LANGUAGES=c CC=stage1/xgcc CFLAGS="-Bstage1/ -g"
+make stage2
+make CC=stage2/xgcc CFLAGS="-Bstage2/ -g -O"
+</pre>
+<p>You may need to raise the ULIMIT setting to build a C++ compiler,
+as the file <code>cc1plus</code> is larger than one megabyte.
+<hr />
+<h2><a name="TOC95"><a name="xtensa-*-elf"></a>xtensa-*-elf</h2>
+   <hr />
+<h3 class="heading"><a name="TOC66"></a><a name="x86_64-*-*"></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 <code>-m32</code> switch).
+   <hr />
+<h3 class="heading"><a name="TOC67"></a><a name="xtensa-*-elf"></a>xtensa-*-elf</h3>
 <p>This target is intended for embedded Xtensa systems using the
 …
 through inline assembly.
 <p>The Xtensa configuration information must be specified prior to
+   <p>The Xtensa configuration information must be specified prior to
 building GCC.  The <code>gcc/config/xtensa/xtensa-config.h</code> header
 file contains the configuration information.  If you created your
 …
 which you can use to replace the default header file.
 <hr />
 <h2><a name="TOC96"><a name="xtensa-*-linux*"></a>xtensa-*-linux*</h2>
+   <hr />
+<h3 class="heading"><a name="TOC68"></a><a name="xtensa-*-linux*"></a>xtensa-*-linux*</h3>
 <p>This target is for Xtensa systems running GNU/Linux.  It supports ELF
 …
 <a href="#xtensa-*-elf"><code>xtensa-*-elf</code></a> target.
 <hr />
 <h2><a name="TOC97"><a name="windows"></a>Microsoft Windows (32-bit)</h2>
 <p>A port of GCC 2.95.x is included with the
+   <hr />
+<h3 class="heading"><a name="TOC69"></a><a name="windows"></a>Microsoft Windows (32-bit)</h3>
+<p>A port of GCC 2.95.2 and 3.x is included with the
 <a href="http://www.cygwin.com/">Cygwin environment</a>.
 <p>Current (as of early 2001) snapshots of GCC will build under Cygwin
+   <p>Current (as of early 2001) snapshots of GCC will build under Cygwin
 without modification.
+<hr />
+<h2><a name="TOC98"><a name="os2"></a>OS/2</h2>
+   <p>GCC does not currently build with Microsoft's C++ compiler and there
+are no plans to make it do so.
+   <hr />
+<h3 class="heading"><a name="TOC70"></a><a name="os2"></a>OS/2</h3>
 <p>GCC does not currently support OS/2.  However, Andrew Zabolotny has been
 …
 at <a href="http://www.goof.com/pcg/os2/">http://www.goof.com/pcg/os2/</a>.
 <p>An older copy of GCC 2.8.1 is included with the EMX tools available at
+   <p>An older copy of GCC 2.8.1 is included with the EMX tools available at
 <a href="ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/">ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/</a>.
 <hr />
 <h2><a name="TOC99"><a name="older"></a>Older systems</h2>
+   <hr />
+<h3 class="heading"><a name="TOC71"></a><a name="older"></a>Older systems</h3>
 <p>GCC contains support files for many older (1980s and early
 s) 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.  Support from some systems
+has been removed from GCC 3: fx80, ns32-ns-genix, pyramid, tahoe,
+gmicro, spur; most of these targets had not been updated since GCC
+version 1.
+<p>We are planning to remove support for more older systems, starting in
+GCC 3.1.  Each release will have a list of "obsoleted" systems.
+several years and may suffer from bitrot.
+   <p>Starting with GCC 3.1, each release has a list of "obsoleted" systems.
 Support for these systems is still present in that release, but
 <code>configure</code> will fail unless the <code>--enable-obsolete</code>
+option is given.  Unless a maintainer steps forward, support for
+these systems will be removed from the next release of GCC.
+<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
+CVS 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>Support for old systems as hosts for GCC can cause problems if the
+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 <code>old-releases</code> directory on the
+<a href="../mirrors.html">GCC mirror sites</a>.  Header bugs may generally
+be avoided using <code>fixincludes</code>, but bugs or deficiencies in
+libraries and the operating system may still cause problems.
+<p>For some systems, old versions of GNU binutils may also be useful,
+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
+<code>old-releases</code> directory on the <a href="../mirrors.html">GCC mirror sites</a>.  Header bugs may generally be avoided using
+<code>fixincludes</code>, 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 CVS
+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 <code>pub/binutils/old-releases</code> on
 <a href="http://sources.redhat.com/mirrors.html">sources.redhat.com mirror sites</a>.
 <p>Some of the information on specific systems above relates to
+   <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.
 <hr />
 <h2><a name="TOC100"><a name="elf_targets"></a>all ELF targets (SVR4, Solaris 2, etc.)</h2>
+   <hr />
+<h3 class="heading"><a name="TOC72"></a><a name="elf_targets"></a>all ELF targets (SVR4, Solaris 2, etc.)</h3>
 <p>C++ support is significantly better on ELF targets if you use the
 …
 automatically.
 <hr />
+   <hr />
 <p>
 <a href="./index.html">Return to the GCC Installation page</a>
 </body></html>
+   </body></html>

Note: See TracChangeset for help on using the changeset viewer.

Context Navigation

Changeset 1391 for branches/GNU/src/gcc/INSTALL/specific.html

Legend:

branches/GNU/src/gcc

branches/GNU/src/gcc/INSTALL/specific.html

Download in other formats: