gcc/INSTALL/specific.html - Issue 3050029: [gcc] GCC 4.5.0=>4.5.1

Unified Diff: gcc/INSTALL/specific.html

Issue 3050029: [gcc] GCC 4.5.0=>4.5.1 (Closed) Base URL: ssh://git@gitrw.chromium.org:9222/nacl-toolchain.git

Patch Set: Created 10 years, 5 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View side-by-side diff with in-line comments

Index: gcc/INSTALL/specific.html

diff --git a/gcc/INSTALL/specific.html b/gcc/INSTALL/specific.html

index 14d44c26d671c595659c4648534b4735cd89f875..7d6ab024b990a008baf4376c7b5e6b9a2f7d5cf5 100644

--- a/gcc/INSTALL/specific.html

+++ b/gcc/INSTALL/specific.html

@@ -3,7 +3,7 @@

<title>Host/Target specific installation notes for GCC</title>

-<meta name="generator" content="makeinfo 4.13">

+<meta name="generator" content="makeinfo 4.12">

<!--

@@ -56,8 +56,6 @@ information are.

<li><a href="#alpha-dec-osf">alpha*-dec-osf*</a>

-<a href="#arm-x-coff">arm-*-coff</a>

-<a href="#arm-x-aout">arm-*-aout</a>

<li><a href="#bfin">Blackfin</a>

@@ -68,17 +66,21 @@ information are.

<li><a href="#x-x-linux-gnu">*-*-linux-gnu</a>

<li><a href="#ix86-x-linux">i?86-*-linux*</a>

+<li><a href="#ix86-x-solaris289">i?86-*-solaris2.[89]</a>

<li><a href="#ix86-x-solaris210">i?86-*-solaris2.10</a>

<li><a href="#ia64-x-linux">ia64-*-linux</a>

+<li><a href="#lm32-x-elf">lm32-*-elf</a>

+<li><a href="#lm32-x-uclinux">lm32-*-uclinux</a>

<li><a href="#m68k-uclinux">m68k-uclinux</a>

+<li><a href="#mep-x-elf">mep-*-elf</a>

@@ -98,6 +100,7 @@ information are.

<li><a href="#x-x-solaris2">*-*-solaris2*</a>

<li><a href="#sparc-sun-solaris2">sparc-sun-solaris2*</a>

<li><a href="#sparc-sun-solaris27">sparc-sun-solaris2.7</a>

+<li><a href="#sparc-sun-solaris210">sparc-sun-solaris2.10</a>

<li><a href="#sparc-x-linux">sparc-*-linux*</a>

<li><a href="#sparc64-x-solaris2">sparc64-*-solaris2*</a>

<li><a href="#sparcv9-x-solaris2">sparcv9-*-solaris2*</a>

@@ -108,7 +111,7 @@ information are.

<li><a href="#windows">Microsoft Windows</a>

<li><a href="#x-x-cygwin">*-*-cygwin</a>

<li><a href="#x-x-interix">*-*-interix</a>

-<li><a href="#x-x-mingw">*-*-mingw</a>

+<li><a href="#x-x-mingw32">*-*-mingw32</a>

<li><a href="#older">Older systems</a>

</ul>

@@ -137,57 +140,38 @@ shared libraries.

<h3 class="heading"><a name="TOC1"></a><a name="alpha_002ddec_002dosf"></a>alpha*-dec-osf*</h3>

<p>Systems using processors that implement the DEC Alpha architecture and

-are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq

+are running the DEC/Compaq/HP Unix (DEC OSF/1, Digital UNIX, or Compaq/HP

Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.

<p>As of GCC 3.2, versions before <code>alpha*-dec-osf4</code> are no longer

supported. (These are the versions which identify themselves as DEC

-OSF/1.)

+OSF/1.) As of GCC 4.5, support for Tru64 UNIX V4.0 and V5.0 has been

+obsoleted, but can still be enabled by configuring with

+<samp><span class="option">--enable-obsolete</span></samp>. Support will be removed in GCC 4.6.

- <p>In Digital Unix V4.0, virtual memory exhausted bootstrap failures

-may be fixed by configuring with <samp><span class="option">--with-gc=simple</span></samp>,

-reconfiguring Kernel Virtual Memory and Swap parameters

+ <p>On Tru64 UNIX, virtual memory exhausted bootstrap failures

+may be fixed by reconfiguring Kernel Virtual Memory and Swap parameters

per the <samp><span class="command">/usr/sbin/sys_check</span></samp> Tuning Suggestions,

or applying the patch in

-<a href="http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html">http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html</a>.

+<a href="http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html">http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html</a>. Depending on

+the OS version used, you need a data segment size between 512 MB and

+1 GB, so simply use <samp><span class="command">ulimit -Sd unlimited</span></samp>.

- <p>In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not

-currently (2001-06-13) work with <samp><span class="command">mips-tfile</span></samp>. As a workaround,

-we need to use the old assembler, invoked via the barely documented

-<samp><span class="option">-oldas</span></samp> option. To bootstrap GCC, you either need to use the

-Compaq C Compiler:

-<pre class="smallexample"> % 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="smallexample"> % 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 <samp><span class="command">as</span></samp> nor GNU <samp><span class="command">ld</span></samp>

+ <p>As of GNU binutils 2.20.1, neither GNU <samp><span class="command">as</span></samp> nor GNU <samp><span class="command">ld</span></samp>

are supported on Tru64 UNIX, so you must not configure GCC with

<samp><span class="option">--with-gnu-as</span></samp> or <samp><span class="option">--with-gnu-ld</span></samp>.

<p>GCC writes a ‘<samp><span class="samp">.verstamp</span></samp>’ directive to the assembler output file

unless it is built as a cross-compiler. It gets the version to use from

the system header file <samp><span class="file">/usr/include/stamp.h</span></samp>. If you install a

-new version of DEC Unix, you should rebuild GCC to pick up the new version

+new version of Tru64 UNIX, you should rebuild GCC to pick up the new version

stamp.

- <p>‘<samp><span class="samp">make compare</span></samp>’ may fail on old versions of DEC Unix unless you add

-<samp><span class="option">-save-temps</span></samp> to <code>BOOT_CFLAGS</code>. On these systems, the name

-of the assembler input file is stored in the object file, and that makes

-comparison fail if it differs between the <code>stage1</code> and

-<code>stage2</code> compilations. The option <samp><span class="option">-save-temps</span></samp> forces a

-fixed name to be used for the assembler input file, instead of a

-randomly chosen name in <samp><span class="file">/tmp</span></samp>. Do not add <samp><span class="option">-save-temps</span></samp>

-unless the comparisons fail without that option. If you add

-<samp><span class="option">-save-temps</span></samp>, you will have to manually delete the ‘<samp><span class="samp">.i</span></samp>’ and

-‘<samp><span class="samp">.s</span></samp>’ files after each series of compilations.

<p>GCC now supports both the native (ECOFF) debugging format used by DBX

and GDB and an encapsulated STABS format for use only with GDB. See the

discussion of the <samp><span class="option">--with-stabs</span></samp> option of <samp><span class="file">configure</span></samp> above

-for more information on these formats and how to select them.

+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

for ECOFF format when the ‘<samp><span class="samp">.align</span></samp>’ directive is used. To work

@@ -201,6 +185,7 @@ different depending on whether or not <samp><span class="option">-g</span></samp

DBX. DEC is now aware of this problem with the assembler and hopes to

provide a fix shortly.

+

@@ -219,22 +204,7 @@ and <code>arm-*-rtems</code>.

-<h3 class="heading"><a name="TOC4"></a><a name="arm_002dx_002dcoff"></a>arm-*-coff</h3>

-<p>ARM-family processors. Note that there are two different varieties

-of PE format subtarget supported: <code>arm-wince-pe</code> and

-<code>arm-pe</code> as well as a standard COFF target <code>arm-*-coff</code>.

- <p><hr />

-<h3 class="heading"><a name="TOC5"></a><a name="arm_002dx_002daout"></a>arm-*-aout</h3>

-<p>ARM-family processors. These targets support the AOUT file format:

-<code>arm-*-aout</code>, <code>arm-*-netbsd</code>.

- <p><hr />

-<h3 class="heading"><a name="TOC6"></a><a name="avr"></a>avr</h3>

+<h3 class="heading"><a name="TOC4"></a><a name="avr"></a>avr</h3>

<p>ATMEL AVR-family micro controllers. These are used in embedded

applications. There are no standard Unix configurations.

@@ -260,7 +230,7 @@ can also be obtained from:

-<h3 class="heading"><a name="TOC7"></a><a name="bfin"></a>Blackfin</h3>

+<h3 class="heading"><a name="TOC5"></a><a name="bfin"></a>Blackfin</h3>

<p>The Blackfin processor, an Analog Devices DSP.

See “Blackfin Options” in the main manual

@@ -270,7 +240,7 @@ is available at <a href="http://blackfin.uclinux.org">http://blackfin.uclinux.or

-<h3 class="heading"><a name="TOC8"></a><a name="cris"></a>CRIS</h3>

+<h3 class="heading"><a name="TOC6"></a><a name="cris"></a>CRIS</h3>

<p>CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip

series. These are used in embedded applications.

@@ -296,7 +266,7 @@ information about this platform is available at

-<h3 class="heading"><a name="TOC9"></a><a name="crx"></a>CRX</h3>

+<h3 class="heading"><a name="TOC7"></a><a name="crx"></a>CRX</h3>

<p>The CRX CompactRISC architecture is a low-power 32-bit architecture with

fast context switching and architectural extensibility features.

@@ -314,7 +284,7 @@ needs to be done in a separate step with the following configure settings:

-<h3 class="heading"><a name="TOC10"></a><a name="dos"></a>DOS</h3>

+<h3 class="heading"><a name="TOC8"></a><a name="dos"></a>DOS</h3>

<p>Please have a look at the <a href="binaries.html">binaries page</a>.

@@ -325,54 +295,43 @@ and includes all the necessary compilation tools and libraries.

-<h3 class="heading"><a name="TOC11"></a><a name="x_002dx_002dfreebsd"></a>*-*-freebsd*</h3>

-<p>The version of binutils installed in <samp><span class="file">/usr/bin</span></samp> probably works with

-this release of GCC. However, on FreeBSD 4, bootstrapping against the

-latest FSF binutils is known to improve overall testsuite results; and,

-on FreeBSD/alpha, using binutils 2.14 or later is required to build libjava.

+<h3 class="heading"><a name="TOC9"></a><a name="x_002dx_002dfreebsd"></a>*-*-freebsd*</h3>

- <p>Support for FreeBSD 1 was discontinued in GCC 3.2.

+<p>Support for FreeBSD 1 was discontinued in GCC 3.2. Support for

+FreeBSD 2 (and any mutant a.out variants of FreeBSD 3) was

+discontinued in GCC 4.0.

- <p>Support for FreeBSD 2 will be discontinued after GCC 3.4. The

-following was true for GCC 3.1 but the current status is unknown.

-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,

-it is unknown which version of binutils was used (it is assumed that it

-was the system copy in <samp><span class="file">/usr/bin</span></samp>) and C++ EH failures were noted.

+ <p>In GCC 4.5, we enabled the use of <code>dl_iterate_phdr</code> inside boehm-gc on

+FreeBSD 7 or later. In order to better match the configuration of the

+FreeBSD system compiler: We also enabled the check to see if libc

+provides SSP support (which it does on FreeBSD 7), the use of

+<code>dl_iterate_phdr</code> inside <samp><span class="file">libgcc_s.so.1</span></samp> (on FreeBSD 7 or later)

+and the use of <code>__cxa_atexit</code> by default (on FreeBSD 6 or later).

- <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 <samp><span class="option">-gstabs</span></samp> instead

-of <samp><span class="option">-g</span></samp>, if you really want the old debugging format. There are

+ <p>We support FreeBSD using the ELF file format with DWARF 2 debugging

+for all CPU architectures. You may use <samp><span class="option">-gstabs</span></samp> instead of

+<samp><span class="option">-g</span></samp>, if you really want the old debugging format. There are

no known issues with mixing object files and libraries with different

-debugging formats. Otherwise, this release of GCC should now match more

-of the configuration used in the stock FreeBSD configuration of GCC. In

-particular, <samp><span class="option">--enable-threads</span></samp> is now configured by default.

-However, as a general user, do not attempt to replace the system

-compiler with this release. Known to bootstrap and check with good

-results on FreeBSD 4.9-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,

-4.3, 4.4, 4.5, 4.8-STABLE.

- <p>In principle, <samp><span class="option">--enable-threads</span></samp> is now compatible with

-<samp><span class="option">--enable-libgcj</span></samp> on FreeBSD. However, it has only been built

-and tested on ‘<samp><span class="samp">i386-*-freebsd[45]</span></samp>’ and ‘<samp><span class="samp">alpha-*-freebsd[45]</span></samp>’.

-The static

-library may be incorrectly built (symbols are missing at link time).

-There is a rare timing-based startup hang (probably involves an

-assumption about the thread library). Multi-threaded boehm-gc (required for

-libjava) exposes severe threaded signal-handling bugs on FreeBSD before

-4.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 <samp><span class="file">libgcc_s.so</span></samp> is now built and installed by default.

+debugging formats. Otherwise, this release of GCC should now match

+more of the configuration used in the stock FreeBSD configuration of

+GCC. In particular, <samp><span class="option">--enable-threads</span></samp> is now configured by

+default. However, as a general user, do not attempt to replace the

+system compiler with this release. Known to bootstrap and check with

+good results on FreeBSD 7.2-STABLE. In the past, known to bootstrap

+and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4,

+4.5, 4.8, 4.9 and 5-CURRENT.

+ <p>The version of binutils installed in <samp><span class="file">/usr/bin</span></samp> probably works

+with this release of GCC. Bootstrapping against the latest GNU

+binutils and/or the version found in <samp><span class="file">/usr/ports/devel/binutils</span></samp> has

+been known to enable additional features and improve overall testsuite

+results. However, it is currently known that boehm-gc (which itself

+is required for java) may not configure properly on FreeBSD prior to

+the FreeBSD 7.0 release with GNU binutils after 2.16.1.

-<h3 class="heading"><a name="TOC12"></a><a name="h8300_002dhms"></a>h8300-hms</h3>

+<h3 class="heading"><a name="TOC10"></a><a name="h8300_002dhms"></a>h8300-hms</h3>

<p>Renesas H8/300 series of processors.

@@ -385,7 +344,7 @@ longer a multiple of 2 bytes.

-<h3 class="heading"><a name="TOC13"></a><a name="hppa_002dhp_002dhpux"></a>hppa*-hp-hpux*</h3>

+<h3 class="heading"><a name="TOC11"></a><a name="hppa_002dhp_002dhpux"></a>hppa*-hp-hpux*</h3>

<p>Support for HP-UX version 9 and older was discontinued in GCC 3.4.

@@ -437,7 +396,7 @@ a list of the predefines used with each standard.

-<h3 class="heading"><a name="TOC14"></a><a name="hppa_002dhp_002dhpux10"></a>hppa*-hp-hpux10</h3>

+<h3 class="heading"><a name="TOC12"></a><a name="hppa_002dhp_002dhpux10"></a>hppa*-hp-hpux10</h3>

<p>For hpux10.20, we <em>highly</em> recommend you pick up the latest sed patch

<code>PHCO_19798</code> from HP. HP has two sites which provide patches free of

@@ -455,7 +414,7 @@ with the one implemented under HP-UX 11 using secondary definitions.

-<h3 class="heading"><a name="TOC15"></a><a name="hppa_002dhp_002dhpux11"></a>hppa*-hp-hpux11</h3>

+<h3 class="heading"><a name="TOC13"></a><a name="hppa_002dhp_002dhpux11"></a>hppa*-hp-hpux11</h3>

<p>GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot

be used to compile GCC 3.0 and up.

@@ -564,7 +523,7 @@ supported, so <samp><span class="option">--enable-threads=dce</span></samp> does

-<h3 class="heading"><a name="TOC16"></a><a name="x_002dx_002dlinux_002dgnu"></a>*-*-linux-gnu</h3>

+<h3 class="heading"><a name="TOC14"></a><a name="x_002dx_002dlinux_002dgnu"></a>*-*-linux-gnu</h3>

<p>Versions of libstdc++-v3 starting with 3.2.1 require bug fixes present

in glibc 2.2.5 and later. More information is available in the

@@ -572,7 +531,7 @@ libstdc++-v3 documentation.

-<h3 class="heading"><a name="TOC17"></a><a name="ix86_002dx_002dlinux"></a>i?86-*-linux*</h3>

+<h3 class="heading"><a name="TOC15"></a><a name="ix86_002dx_002dlinux"></a>i?86-*-linux*</h3>

<p>As of GCC 3.3, binutils 2.13.1 or later is required for this platform.

See <a href="http://gcc.gnu.org/PR10877">bug 10877</a> for more information.

@@ -583,19 +542,57 @@ found on <a href="http://www.bitwizard.nl/sig11/">www.bitwizard.nl</a>.

-<h3 class="heading"><a name="TOC18"></a><a name="ix86_002dx_002dsolaris210"></a>i?86-*-solaris2.10</h3>

+<h3 class="heading"><a name="TOC16"></a><a name="ix86_002dx_002dsolaris289"></a>i?86-*-solaris2.[89]</h3>

-<p>Use this for Solaris 10 or later on x86 and x86-64 systems. This

-configuration is supported by GCC 4.0 and later versions only.

+<p>The Sun assembler in Solaris 8 and 9 has several bugs and limitations.

+While GCC works around them, several features are missing, so it is

+

+recommended to use the GNU assembler instead. There is no bundled

+version, but the current version, from GNU binutils 2.20.1, is known to

+work.

+ <p>Solaris~2/x86 doesn't support the execution of SSE/SSE2 instructions

+before Solaris~9 4/04, even if the CPU supports them. Programs will

+receive <code>SIGILL</code> if they try. The fix is available both in

+Solaris~9 Update~6 and kernel patch 112234-12 or newer. There is no

+corresponding patch for Solaris 8. To avoid this problem,

+<samp><span class="option">-march</span></samp> defaults to ‘<samp><span class="samp">pentiumpro</span></samp>’ on Solaris 8 and 9. If

+you have the patch installed, you can configure GCC with an appropriate

+<samp><span class="option">--with-arch</span></samp> option, but need GNU <samp><span class="command">as</span></samp> for SSE2 support.

+ <p><hr />

- <p>It is recommended that you configure GCC to use the GNU assembler in

-<samp><span class="file">/usr/sfw/bin/gas</span></samp> but the Sun linker, using the options

-<samp><span class="option">--with-gnu-as --with-as=/usr/sfw/bin/gas --without-gnu-ld

---with-ld=/usr/ccs/bin/ld</span></samp>.

+<h3 class="heading"><a name="TOC17"></a><a name="ix86_002dx_002dsolaris210"></a>i?86-*-solaris2.10</h3>

+<p>Use this for Solaris 10 or later on x86 and x86-64 systems. This

+configuration is supported by GCC 4.0 and later versions only. Unlike

+‘<samp><span class="samp">sparcv9-sun-solaris2*</span></samp>’, there is no corresponding 64-bit

+configuration like ‘<samp><span class="samp">amd64-*-solaris2*</span></samp>’ or ‘<samp><span class="samp">x86_64-*-solaris2*</span></samp>’.

+

+ <p>It is recommended that you configure GCC to use the GNU assembler, in

+<samp><span class="file">/usr/sfw/bin/gas</span></samp>. The versions included in Solaris 10, from GNU

+binutils 2.15, and Solaris 11, from GNU binutils 2.19, work fine,

+although the current version, from GNU binutils

+2.20.1, is known to work, too. Recent versions of the Sun assembler in

+<samp><span class="file">/usr/ccs/bin/as</span></samp> work almost as well, though.

+

+ <p>For linking, the Sun linker, is preferred. If you want to use the GNU

+linker instead, which is available in <samp><span class="file">/usr/sfw/bin/gld</span></samp>, note that

+due to a packaging bug the version in Solaris 10, from GNU binutils

+2.15, cannot be used, while the version in Solaris 11, from GNU binutils

+2.19, works, as does the latest version, from GNU binutils 2.20.1.

+ <p>To use GNU <samp><span class="command">as</span></samp>, configure with the options

+<samp><span class="option">--with-gnu-as --with-as=/usr/sfw/bin/gas</span></samp>. It may be necessary

+to configure with <samp><span class="option">--without-gnu-ld --with-ld=/usr/ccs/bin/ld</span></samp> to

+guarantee use of Sun <samp><span class="command">ld</span></samp>.

+

-<h3 class="heading"><a name="TOC19"></a><a name="ia64_002dx_002dlinux"></a>ia64-*-linux</h3>

+<h3 class="heading"><a name="TOC18"></a><a name="ia64_002dx_002dlinux"></a>ia64-*-linux</h3>

<p>IA-64 processor (also known as IPF, or Itanium Processor Family)

running GNU/Linux.

@@ -615,7 +612,7 @@ more major ABI changes are expected.

-<h3 class="heading"><a name="TOC20"></a><a name="ia64_002dx_002dhpux"></a>ia64-*-hpux*</h3>

+<h3 class="heading"><a name="TOC19"></a><a name="ia64_002dx_002dhpux"></a>ia64-*-hpux*</h3>

<p>Building GCC on this target requires the GNU Assembler. The bundled HP

assembler will not work. To prevent GCC from using the wrong assembler,

@@ -630,14 +627,27 @@ removed and the system libunwind library will always be used.

-<h3 class="heading"><a name="TOC21"></a><a name="x_002dibm_002daix"></a>*-ibm-aix*</h3>

+<h3 class="heading"><a name="TOC20"></a><a name="x_002dibm_002daix"></a>*-ibm-aix*</h3>

-<p>Support for AIX version 3 and older was discontinued in GCC 3.4.

+<p>Support for AIX version 3 and older was discontinued in GCC 3.4.

+Support for AIX version 4.2 and older was discontinued in GCC 4.5.

<p>“out of memory” bootstrap failures may indicate a problem with

process resource limits (ulimit). Hard limits are configured in the

<samp><span class="file">/etc/security/limits</span></samp> system configuration file.

+ <p>GCC can bootstrap with recent versions of IBM XLC, but bootstrapping

+with an earlier release of GCC is recommended. Bootstrapping with XLC

+requires a larger data segment, which can be enabled through the

+<var>LDR_CNTRL</var> environment variable, e.g.,

+<pre class="smallexample"> % LDR_CNTRL=MAXDATA=0x50000000

+ % export LDR_CNTRL

+</pre>

+ <p>One can start with a pre-compiled version of GCC to build from

+sources. One may delete GCC's “fixed” header files when starting

+with a version of GCC built for an earlier release of AIX.

<p>To speed up the configuration phases of bootstrapping and installing GCC,

one may use GNU Bash instead of AIX <samp><span class="command">/bin/sh</span></samp>, e.g.,

@@ -664,16 +674,14 @@ If this error occurs during stage2 or later, then the problem most likely

is the version of Make (see above).

<p>The native <samp><span class="command">as</span></samp> and <samp><span class="command">ld</span></samp> are recommended for bootstrapping

-on AIX 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.

+on AIX. The GNU Assembler, GNU Linker, and GNU Binutils version 2.20

+is required to bootstrap on AIX 5. The native AIX tools do

+interoperate with GCC.

<p>Building <samp><span class="file">libstdc++.a</span></samp> requires a fix for an AIX Assembler bug

APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a

fix for another AIX Assembler bug and a co-dependent AIX Archiver fix

-referenced as APAR IY53606 (AIX 5.2) or a APAR IY54774 (AIX 5.1)

+referenced as APAR IY53606 (AIX 5.2) or as APAR IY54774 (AIX 5.1)

<p>‘<samp><span class="samp">libstdc++</span></samp>’ in GCC 3.4 increments the major version number of the

shared object and GCC installation places the <samp><span class="file">libstdc++.a</span></samp>

@@ -744,52 +752,63 @@ GCC does not produce the same floating-point formats that the assembler

expects. If one encounters this problem, set the <samp><span class="env">LANG</span></samp>

environment variable to ‘<samp><span class="samp">C</span></samp>’ or ‘<samp><span class="samp">En_US</span></samp>’.

- <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 <samp><span class="option">-mcpu=</span><var>cpu_type</var></samp>

switch and using the configure option <samp><span class="option">--with-cpu-</span><var>cpu_type</var></samp>.

-<h3 class="heading"><a name="TOC22"></a><a name="iq2000_002dx_002delf"></a>iq2000-*-elf</h3>

+<h3 class="heading"><a name="TOC21"></a><a name="iq2000_002dx_002delf"></a>iq2000-*-elf</h3>

<p>Vitesse IQ2000 processors. These are used in embedded

applications. There are no standard Unix configurations.

-<h3 class="heading"><a name="TOC23"></a><a name="m32c_002dx_002delf"></a>m32c-*-elf</h3>

+<h3 class="heading"><a name="TOC22"></a><a name="lm32_002dx_002delf"></a>lm32-*-elf</h3>

+<p>Lattice Mico32 processor.

+This configuration is intended for embedded systems.

+ <p><hr />

+<h3 class="heading"><a name="TOC23"></a><a name="lm32_002dx_002duclinux"></a>lm32-*-uclinux</h3>

+<p>Lattice Mico32 processor.

+This configuration is intended for embedded systems running uClinux.

+ <p><hr />

+<h3 class="heading"><a name="TOC24"></a><a name="m32c_002dx_002delf"></a>m32c-*-elf</h3>

<p>Renesas M32C processor.

This configuration is intended for embedded systems.

-<h3 class="heading"><a name="TOC24"></a><a name="m32r_002dx_002delf"></a>m32r-*-elf</h3>

+<h3 class="heading"><a name="TOC25"></a><a name="m32r_002dx_002delf"></a>m32r-*-elf</h3>

<p>Renesas M32R processor.

This configuration is intended for embedded systems.

-<h3 class="heading"><a name="TOC25"></a><a name="m6811_002delf"></a>m6811-elf</h3>

+<h3 class="heading"><a name="TOC26"></a><a name="m6811_002delf"></a>m6811-elf</h3>

<p>Motorola 68HC11 family micro controllers. These are used in embedded

applications. There are no standard Unix configurations.

-<h3 class="heading"><a name="TOC26"></a><a name="m6812_002delf"></a>m6812-elf</h3>

+<h3 class="heading"><a name="TOC27"></a><a name="m6812_002delf"></a>m6812-elf</h3>

<p>Motorola 68HC12 family micro controllers. These are used in embedded

applications. There are no standard Unix configurations.

-<h3 class="heading"><a name="TOC27"></a><a name="m68k_002dx_002dx"></a>m68k-*-*</h3>

+<h3 class="heading"><a name="TOC28"></a><a name="m68k_002dx_002dx"></a>m68k-*-*</h3>

-<p>By default, ‘<samp><span class="samp">m68k-*-aout</span></samp>’, ‘<samp><span class="samp">m68k-*-coff*</span></samp>’,

+<p>By default,

‘<samp><span class="samp">m68k-*-elf*</span></samp>’, ‘<samp><span class="samp">m68k-*-rtems</span></samp>’, ‘<samp><span class="samp">m68k-*-uclinux</span></samp>’ and

‘<samp><span class="samp">m68k-*-linux</span></samp>’

build libraries for both M680x0 and ColdFire processors. If you only

@@ -813,7 +832,7 @@ be a <samp><span class="option">-mcpu</span></samp> argument or one of the follo

-<h3 class="heading"><a name="TOC28"></a><a name="m68k_002dx_002duclinux"></a>m68k-*-uclinux</h3>

+<h3 class="heading"><a name="TOC29"></a><a name="m68k_002dx_002duclinux"></a>m68k-*-uclinux</h3>

<p>GCC 4.3 changed the uClinux configuration so that it uses the

‘<samp><span class="samp">m68k-linux-gnu</span></samp>’ ABI rather than the ‘<samp><span class="samp">m68k-elf</span></samp>’ ABI.

@@ -824,7 +843,14 @@ original ABI by configuring for ‘<samp><span class="samp">m68k-uclinuxolda

-<h3 class="heading"><a name="TOC29"></a><a name="mips_002dx_002dx"></a>mips-*-*</h3>

+<h3 class="heading"><a name="TOC30"></a><a name="mep_002dx_002delf"></a>mep-*-elf</h3>

+<p>Toshiba Media embedded Processor.

+This configuration is intended for embedded systems.

+ <p><hr />

+<h3 class="heading"><a name="TOC31"></a><a name="mips_002dx_002dx"></a>mips-*-*</h3>

<p>If on a MIPS system you get an error message saying “does not have gp

sections for all it's [sic] sectons [sic]”, don't worry about it. This

@@ -881,51 +907,75 @@ made after Nov. 9, 2006) should be free from both of these problems.

-<h3 class="heading"><a name="TOC30"></a><a name="mips_002dsgi_002dirix5"></a>mips-sgi-irix5</h3>

+<h3 class="heading"><a name="TOC32"></a><a name="mips_002dsgi_002dirix5"></a>mips-sgi-irix5</h3>

-<p>In order to compile GCC on an SGI running IRIX 5, the ‘<samp><span class="samp">compiler_dev.hdr</span></samp>’

+<p>Support for IRIX 5 has been obsoleted in GCC 4.5, but can still be

+enabled by configuring with <samp><span class="option">--enable-obsolete</span></samp>. Support will be

+removed in GCC 4.6.

+ <p>In order to compile GCC on an SGI running IRIX 5, the ‘<samp><span class="samp">compiler_dev.hdr</span></samp>’

subsystem must be installed from the IDO CD-ROM supplied by SGI.

It is also available for download from

-<a href="ftp://ftp.sgi.com/sgi/IRIX5.3/iris-development-option-5.3.tardist">ftp://ftp.sgi.com/sgi/IRIX5.3/iris-development-option-5.3.tardist</a>.

+<a href="http://freeware.sgi.com/ido.html">http://freeware.sgi.com/ido.html</a>.

<p>If you use the MIPS C compiler to bootstrap, it may be necessary

to increase its table size for switch statements with the

<samp><span class="option">-Wf,-XNg1500</span></samp> option. If you use the <samp><span class="option">-O2</span></samp>

-optimization option, you also need to use <samp><span class="option">-Olimit 3000</span></samp>.

+optimization option, you also need to use <samp><span class="option">-Olimit 3000</span></samp>.

+

+ <p>GCC must be configured to use GNU <samp><span class="command">as</span></samp>. The latest version, from GNU

+binutils 2.20.1, is known to work.

<p>To enable debugging under IRIX 5, you must use GNU binutils 2.15 or

later, and use the <samp><span class="option">--with-gnu-ld</span></samp> <samp><span class="command">configure</span></samp> option

-when configuring GCC. You need to use GNU <samp><span class="command">ar</span></samp> and <samp><span class="command">nm</span></samp>,

-also distributed with GNU binutils.

+when configuring GCC.

+You need to use GNU <samp><span class="command">ar</span></samp> and <samp><span class="command">nm</span></samp>,

+also distributed with GNU binutils.

+

- <p>Some users have reported that <samp><span class="command">/bin/sh</span></samp> will hang during bootstrap.

-This problem can be avoided by running the commands:

+ <p>Configuring GCC with <samp><span class="command">/bin/sh</span></samp> is <em>extremely</em> slow and may

+even hang. This problem can be avoided by running <samp><span class="command">configure</span></samp>

+like this:

-<pre class="smallexample"> % CONFIG_SHELL=/bin/ksh

+<pre class="smallexample"> % CONFIG_SHELL=/usr/local/bin/bash

% export CONFIG_SHELL

+ % $CONFIG_SHELL <var>srcdir</var>/configure [<var>options</var>]

</pre>

- <p>before starting the build.

+ <p class="noindent"><samp><span class="command">/bin/ksh</span></samp> doesn't work properly either.

-<h3 class="heading"><a name="TOC31"></a><a name="mips_002dsgi_002dirix6"></a>mips-sgi-irix6</h3>

+<h3 class="heading"><a name="TOC33"></a><a name="mips_002dsgi_002dirix6"></a>mips-sgi-irix6</h3>

+<p>Support for IRIX 6 releases before 6.5 has been obsoleted in GCC 4.5,

+but can still be enabled by configuring with <samp><span class="option">--enable-obsolete</span></samp>.

+Support will be removed in GCC 4.6, which will also disable support for

+the O32 ABI. It is <em>strongly</em> recommended to upgrade to at least

+IRIX 6.5.18. This release introduced full ISO C99 support, though for

+the N32 and N64 ABIs only.

-<p>If you are using SGI's MIPSpro <samp><span class="command">cc</span></samp> as your bootstrap compiler, you must

+ <p>To build and use GCC on IRIX 6, you need the IRIX Development Foundation

+(IDF) and IRIX Development Libraries (IDL). They are included with the

+IRIX 6.5 media and can be downloaded from

+<a href="http://freeware.sgi.com/idf_idl.html">http://freeware.sgi.com/idf_idl.html</a> for older IRIX 6 releases.

+ <p>If you are using SGI's MIPSpro <samp><span class="command">cc</span></samp> as your bootstrap compiler, you must

ensure that the N32 ABI is in use. To test this, compile a simple C

file with <samp><span class="command">cc</span></samp> and then run <samp><span class="command">file</span></samp> on the

resulting object file. The output should look like:

<pre class="smallexample"> test.o: ELF N32 MSB ...

</pre>

- <p>If you see:

+ <p class="noindent">If you see:

<pre class="smallexample"> test.o: ELF 32-bit MSB ...

</pre>

- <p>or

+ <p class="noindent">or

<pre class="smallexample"> test.o: ELF 64-bit MSB ...

</pre>

- <p>then your version of <samp><span class="command">cc</span></samp> uses the O32 or N64 ABI by default. You

+ <p class="noindent">then your version of <samp><span class="command">cc</span></samp> uses the O32 or N64 ABI by default. You

should set the environment variable <samp><span class="env">CC</span></samp> to ‘<samp><span class="samp">cc -n32</span></samp>’

before configuring GCC.

@@ -939,11 +989,11 @@ all on ‘<samp><span class="samp">mips3</span></samp>’-only systems.

<pre class="smallexample"> test.o: ELF N32 MSB mips-3 ...

</pre>

- <p>If you get:

+ <p class="noindent">If you get:

<pre class="smallexample"> test.o: ELF N32 MSB mips-4 ...

</pre>

- <p>instead, you should set the environment variable <samp><span class="env">CC</span></samp> to ‘<samp><span class="samp">cc

+ <p class="noindent">instead, you should set the environment variable <samp><span class="env">CC</span></samp> to ‘<samp><span class="samp">cc

-n32 -mips3</span></samp>’ or ‘<samp><span class="samp">gcc -mips3</span></samp>’ respectively before configuring GCC.

<p>MIPSpro C 7.4 may cause bootstrap failures, due to a bug when inlining

@@ -958,9 +1008,9 @@ try to use them. This will disable building the O32 libraries, too.

Look for <samp><span class="file">/usr/lib64/libc.so.1</span></samp> to see if you

have the 64-bit libraries installed.

- <p>To enable debugging for the O32 ABI, you must use GNU <samp><span class="command">as</span></samp> from

-GNU binutils 2.15 or later. You may also use GNU <samp><span class="command">ld</span></samp>, but

-this is not required and currently causes some problems with Ada.

+ <p>GCC must be configured with GNU <samp><span class="command">as</span></samp>. The latest version, from GNU

+binutils 2.20.1, is known to work. On the other hand, bootstrap fails

+with GNU <samp><span class="command">ld</span></samp> at least since GNU binutils 2.17.

<p>The <samp><span class="option">--enable-libgcj</span></samp>

option is disabled by default: IRIX 6 uses a very low default limit

@@ -969,19 +1019,24 @@ workaround for this problem, at least the N64 ‘<samp><span class="samp">li

to build despite this, running into an internal error of the native

<samp><span class="command">ld</span></samp>. A sure fix is to increase this limit (‘<samp><span class="samp">ncargs</span></samp>’) to

its maximum of 262144 bytes. If you have root access, you can use the

-<samp><span class="command">systune</span></samp> command to do this.

+<samp><span class="command">systune</span></samp> command to do this.

+

<p><code>wchar_t</code> support in ‘<samp><span class="samp">libstdc++</span></samp>’ is not available for old

IRIX 6.5.x releases, x < 19. The problem cannot be autodetected

and in order to build GCC for such targets you need to configure with

<samp><span class="option">--disable-wchar_t</span></samp>.

- <p>See <a href="http://freeware.sgi.com/">http://freeware.sgi.com/</a> for more

-information about using GCC on IRIX platforms.

+ <p><hr />

+<h3 class="heading"><a name="TOC34"></a><a name="moxie_002dx_002delf"></a>moxie-*-elf</h3>

+<p>The moxie processor. See <a href="http://moxielogic.org/">http://moxielogic.org/</a> for more

+information about this processor.

-<h3 class="heading"><a name="TOC32"></a><a name="powerpc_002dx_002dx"></a>powerpc-*-*</h3>

+<h3 class="heading"><a name="TOC35"></a><a name="powerpc_002dx_002dx"></a>powerpc-*-*</h3>

<p>You can specify a default version for the <samp><span class="option">-mcpu=</span><var>cpu_type</var></samp>

switch by using the configure option <samp><span class="option">--with-cpu-</span><var>cpu_type</var></samp>.

@@ -992,7 +1047,7 @@ or newer for a working GCC.

-<h3 class="heading"><a name="TOC33"></a><a name="powerpc_002dx_002ddarwin"></a>powerpc-*-darwin*</h3>

+<h3 class="heading"><a name="TOC36"></a><a name="powerpc_002dx_002ddarwin"></a>powerpc-*-darwin*</h3>

<p>PowerPC running Darwin (Mac OS X kernel).

@@ -1009,69 +1064,77 @@ on systems older than 10.3.9 (aka darwin7.9.0).

-<h3 class="heading"><a name="TOC34"></a><a name="powerpc_002dx_002delf"></a>powerpc-*-elf</h3>

+<h3 class="heading"><a name="TOC37"></a><a name="powerpc_002dx_002delf"></a>powerpc-*-elf</h3>

<p>PowerPC system in big endian mode, running System V.4.

-<h3 class="heading"><a name="TOC35"></a><a name="powerpc_002dx_002dlinux_002dgnu"></a>powerpc*-*-linux-gnu*</h3>

+<h3 class="heading"><a name="TOC38"></a><a name="powerpc_002dx_002dlinux_002dgnu"></a>powerpc*-*-linux-gnu*</h3>

<p>PowerPC system in big endian mode running Linux.

-<h3 class="heading"><a name="TOC36"></a><a name="powerpc_002dx_002dnetbsd"></a>powerpc-*-netbsd*</h3>

+<h3 class="heading"><a name="TOC39"></a><a name="powerpc_002dx_002dnetbsd"></a>powerpc-*-netbsd*</h3>

<p>PowerPC system in big endian mode running NetBSD.

-<h3 class="heading"><a name="TOC37"></a><a name="powerpc_002dx_002deabisim"></a>powerpc-*-eabisim</h3>

+<h3 class="heading"><a name="TOC40"></a><a name="powerpc_002dx_002deabisim"></a>powerpc-*-eabisim</h3>

<p>Embedded PowerPC system in big endian mode for use in running under the

PSIM simulator.

-<h3 class="heading"><a name="TOC38"></a><a name="powerpc_002dx_002deabi"></a>powerpc-*-eabi</h3>

+<h3 class="heading"><a name="TOC41"></a><a name="powerpc_002dx_002deabi"></a>powerpc-*-eabi</h3>

<p>Embedded PowerPC system in big endian mode.

-<h3 class="heading"><a name="TOC39"></a><a name="powerpcle_002dx_002delf"></a>powerpcle-*-elf</h3>

+<h3 class="heading"><a name="TOC42"></a><a name="powerpcle_002dx_002delf"></a>powerpcle-*-elf</h3>

<p>PowerPC system in little endian mode, running System V.4.

-<h3 class="heading"><a name="TOC40"></a><a name="powerpcle_002dx_002deabisim"></a>powerpcle-*-eabisim</h3>

+<h3 class="heading"><a name="TOC43"></a><a name="powerpcle_002dx_002deabisim"></a>powerpcle-*-eabisim</h3>

<p>Embedded PowerPC system in little endian mode for use in running under

the PSIM simulator.

-<h3 class="heading"><a name="TOC41"></a><a name="powerpcle_002dx_002deabi"></a>powerpcle-*-eabi</h3>

+<h3 class="heading"><a name="TOC44"></a><a name="powerpcle_002dx_002deabi"></a>powerpcle-*-eabi</h3>

<p>Embedded PowerPC system in little endian mode.

-<h3 class="heading"><a name="TOC42"></a><a name="s390_002dx_002dlinux"></a>s390-*-linux*</h3>

+<h3 class="heading"><a name="TOC45"></a><a name="rx_002dx_002delf"></a>rx-*-elf</h3>

+<p>The Renesas RX processor. See

+<a href="http://eu.renesas.com/fmwk.jsp?cnt=rx600_series_landing.jsp&fp=/products/mpumcu/rx_family/rx600_series">http://eu.renesas.com/fmwk.jsp?cnt=rx600_series_landing.jsp&fp=/products/mpumcu/rx_family/rx600_series</a>

+for more information about this processor.

+ <p><hr />

+<h3 class="heading"><a name="TOC46"></a><a name="s390_002dx_002dlinux"></a>s390-*-linux*</h3>

<p>S/390 system running GNU/Linux for S/390.

-<h3 class="heading"><a name="TOC43"></a><a name="s390x_002dx_002dlinux"></a>s390x-*-linux*</h3>

+<h3 class="heading"><a name="TOC47"></a><a name="s390x_002dx_002dlinux"></a>s390x-*-linux*</h3>

<p>zSeries system (64-bit) running GNU/Linux for zSeries.

-<h3 class="heading"><a name="TOC44"></a><a name="s390x_002dibm_002dtpf"></a>s390x-ibm-tpf*</h3>

+<h3 class="heading"><a name="TOC48"></a><a name="s390x_002dibm_002dtpf"></a>s390x-ibm-tpf*</h3>

<p>zSeries system (64-bit) running TPF. This platform is

supported as cross-compilation target only.

@@ -1081,22 +1144,28 @@ supported as cross-compilation target only.

-<h3 class="heading"><a name="TOC45"></a><a name="x_002dx_002dsolaris2"></a>*-*-solaris2*</h3>

+<h3 class="heading"><a name="TOC49"></a><a name="x_002dx_002dsolaris2"></a>*-*-solaris2*</h3>

-<p>Sun does not ship a C compiler with Solaris 2. To bootstrap and install

-GCC you first have to install a pre-built compiler, see the

+<p>Support for Solaris 7 has been obsoleted in GCC 4.5, but can still be

+enabled by configuring with <samp><span class="option">--enable-obsolete</span></samp>. Support will be

+removed in GCC 4.6.

+ <p>Sun does not ship a C compiler with Solaris 2, though you can download

+the Sun Studio compilers for free from

+<a href="http://developers.sun.com/sunstudio/downloads/">http://developers.sun.com/sunstudio/downloads/</a>. Alternatively,

+you can install a pre-built GCC to bootstrap and install GCC. See the

<a href="binaries.html">binaries page</a> for details.

<p>The Solaris 2 <samp><span class="command">/bin/sh</span></samp> will often fail to configure

-<samp><span class="file">libstdc++-v3</span></samp>, <samp><span class="file">boehm-gc</span></samp> or <samp><span class="file">libjava</span></samp>. We therefore

+‘<samp><span class="samp">libstdc++-v3</span></samp>’, ‘<samp><span class="samp">boehm-gc</span></samp>’ or ‘<samp><span class="samp">libjava</span></samp>’. We therefore

recommend using the following initial sequence of commands

<pre class="smallexample"> % CONFIG_SHELL=/bin/ksh

% export CONFIG_SHELL

</pre>

- <p>and proceed as described in <a href="configure.html">the configure instructions</a>.

+ <p class="noindent">and proceed as described in <a href="configure.html">the configure instructions</a>.

In addition we strongly recommend specifying an absolute path to invoke

-<var>srcdir</var>/configure.

+<samp><var>srcdir</var><span class="command">/configure</span></samp>.

<p>Solaris 2 comes with a number of optional OS packages. Some of these

are needed to use GCC fully, namely <code>SUNWarc</code>,

@@ -1119,37 +1188,30 @@ For example, the linker may hang indefinitely. The fix is to remove

have <samp><span class="file">/usr/xpg4/bin</span></samp> in your <samp><span class="env">PATH</span></samp>, we recommend that you place

<samp><span class="file">/usr/bin</span></samp> before <samp><span class="file">/usr/xpg4/bin</span></samp> for the duration of the build.

- <p>We recommend the use of GNU binutils 2.14 or later, or the vendor tools

-(Sun <samp><span class="command">as</span></samp>, Sun <samp><span class="command">ld</span></samp>). Note that your mileage may vary

+ <p>We recommend the use of the Sun assembler or the GNU assembler, in

+conjunction with the Sun linker. The GNU <samp><span class="command">as</span></samp>

+versions included in Solaris 10, from GNU binutils 2.15, and Solaris 11,

+from GNU binutils 2.19, are known to work. They can be found in

+<samp><span class="file">/usr/sfw/bin/gas</span></samp>. Current versions of GNU binutils (2.20.1)

+are known to work as well. Note that your mileage may vary

if you use a combination of the GNU tools and the Sun tools: while the

combination GNU <samp><span class="command">as</span></samp> + Sun <samp><span class="command">ld</span></samp> should reasonably work,

the reverse combination Sun <samp><span class="command">as</span></samp> + GNU <samp><span class="command">ld</span></samp> is known to

-cause memory corruption at runtime in some cases for C++ programs.

- <p>The stock GNU binutils 2.15 release is broken on this platform because of a

-single bug. It has been fixed on the 2.15 branch in the CVS repository.

-You can obtain a working version by checking out the binutils-2_15-branch

-from the CVS repository or applying the patch

-<a href="http://sourceware.org/ml/binutils-cvs/2004-09/msg00036.html">http://sourceware.org/ml/binutils-cvs/2004-09/msg00036.html</a> to the

-release.

- <p>We recommend the use of GNU binutils 2.16 or later in conjunction with GCC

-4.x, or the vendor tools (Sun <samp><span class="command">as</span></samp>, Sun <samp><span class="command">ld</span></samp>). However,

-for Solaris 10 and above, an additional patch is required in order for the

-GNU linker to be able to cope with a new flavor of shared libraries. You

-can obtain a working version by checking out the binutils-2_16-branch from

-the CVS repository or applying the patch

-<a href="http://sourceware.org/ml/binutils-cvs/2005-07/msg00122.html">http://sourceware.org/ml/binutils-cvs/2005-07/msg00122.html</a> to the

-release.

+cause memory corruption at runtime in some cases for C++ programs.

+

+GNU <samp><span class="command">ld</span></samp> usually works as well, although the version included in

+Solaris 10 cannot be used due to several bugs. Again, the current

+version (2.20.1) is known to work, but generally lacks platform specific

+features, so better stay with Sun <samp><span class="command">ld</span></samp>.

<p>Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or

newer: <samp><span class="command">g++</span></samp> will complain that types are missing. These headers

assume that omitting the type means <code>int</code>; this assumption worked for

-C89 but is wrong for C++, and is now wrong for C99 also.

+C90 but is wrong for C++, and is now wrong for C99 also.

<p><samp><span class="command">g++</span></samp> accepts such (invalid) constructs with the option

<samp><span class="option">-fpermissive</span></samp>; it will assume that any missing type is <code>int</code>

-(as defined by C89).

+(as defined by C90).

<p>There are patches for Solaris 7 (108376-21 or newer for SPARC,

108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC,

@@ -1168,9 +1230,9 @@ SPARC, 117172-11 or newer for Intel) that address this problem.

-<h3 class="heading"><a name="TOC46"></a><a name="sparc_002dsun_002dsolaris2"></a>sparc-sun-solaris2*</h3>

+<h3 class="heading"><a name="TOC50"></a><a name="sparc_002dsun_002dsolaris2"></a>sparc-sun-solaris2*</h3>

-<p>When GCC is configured to use binutils 2.14 or later the binaries

+<p>When GCC is configured to use GNU binutils 2.14 or later, the binaries

produced are smaller than the ones produced using Sun's native tools;

this difference is quite significant for binaries containing debugging

information.

@@ -1200,10 +1262,10 @@ and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a bootstrap

failure in form of a miscompilation of the stage1 compiler by the Sun

compiler. This is Sun bug 4974440. This is fixed with patch 112760-07.

- <p>GCC 3.4 changed the default debugging format from STABS to DWARF-2 for

+ <p>GCC 3.4 changed the default debugging format from Stabs to DWARF-2 for

32-bit code on Solaris 7 and later. If you use the Sun assembler, this

change apparently runs afoul of Sun bug 4910101 (which is referenced as

-a x86-only problem by Sun, probably because they do not use DWARF-2).

+an x86-only problem by Sun, probably because they do not use DWARF-2).

A symptom of the problem is that you cannot compile C++ programs like

<samp><span class="command">groff</span></samp> 1.19.1 without getting messages similar to the following:

@@ -1211,13 +1273,13 @@ A symptom of the problem is that you cannot compile C++ programs like

external symbolic relocation against non-allocatable section

.debug_info cannot be processed at runtime: relocation ignored.

</pre>

- <p>To work around this problem, compile with <samp><span class="option">-gstabs+</span></samp> instead of

+ <p class="noindent">To work around this problem, compile with <samp><span class="option">-gstabs+</span></samp> instead of

plain <samp><span class="option">-g</span></samp>.

<p>When configuring the GNU Multiple Precision Library (GMP) or the MPFR

library on a Solaris 7 or later system, the canonical target triplet

must be specified as the <samp><span class="command">build</span></samp> parameter on the configure

-line. This triplet can be obtained by invoking ./config.guess in

+line. This triplet can be obtained by invoking <samp><span class="command">./config.guess</span></samp> in

the toplevel source directory of GCC (and not that of GMP or MPFR).

For example on a Solaris 7 system:

@@ -1225,9 +1287,12 @@ For example on a Solaris 7 system:

</pre>

-<h3 class="heading"><a name="TOC47"></a><a name="sparc_002dsun_002dsolaris27"></a>sparc-sun-solaris2.7</h3>

+<h3 class="heading"><a name="TOC51"></a><a name="sparc_002dsun_002dsolaris27"></a>sparc-sun-solaris2.7</h3>

+<p><em>Note</em> that this configuration has been obsoleted in GCC 4.5, and will be

+removed in GCC 4.6.

-<p>Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in

+ <p>Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in

the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8

and later, including all EGCS releases. Sun formerly recommended

107058-01 for all Solaris 7 users, but around 1999-09-01 it started to

@@ -1261,12 +1326,12 @@ the Solaris 7 Recommended Patch Cluster.

<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:

+‘<samp><span class="samp">libgcc</span></samp>’. A typical error message is:

<pre class="smallexample"> ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o:

symbol <unknown>: offset 0xffffffff7ec133e7 is non-aligned.

</pre>

- <p>This bug has been fixed in the final 5.0 version of the assembler.

+ <p class="noindent">This bug has been fixed in the final 5.0 version of the assembler.

<p>A similar problem was reported for version Sun WorkShop 6 99/08/18 of the

Sun assembler, which causes a bootstrap failure with GCC 4.0.0:

@@ -1275,11 +1340,23 @@ Sun assembler, which causes a bootstrap failure with GCC 4.0.0:

file .libs/libstdc++.lax/libsupc++convenience.a/vterminate.o:

symbol <unknown>: offset 0xfccd33ad is non-aligned

</pre>

- <p>This bug has been fixed in more recent revisions of the assembler.

+ <p class="noindent">This bug has been fixed in more recent revisions of the assembler.

+ <p><hr />

+<h3 class="heading"><a name="TOC52"></a><a name="sparc_002dsun_002dsolaris210"></a>sparc-sun-solaris2.10</h3>

+<p>There is a bug in older versions of the Sun assembler which breaks

+thread-local storage (TLS). A typical error message is

+<pre class="smallexample"> ld: fatal: relocation error: R_SPARC_TLS_LE_HIX22: file /var/tmp//ccamPA1v.o:

+ symbol <unknown>: bad symbol type SECT: symbol type must be TLS

+</pre>

+ <p class="noindent">This bug is fixed in Sun patch 118683-03 or later.

-<h3 class="heading"><a name="TOC48"></a><a name="sparc_002dx_002dlinux"></a>sparc-*-linux*</h3>

+<h3 class="heading"><a name="TOC53"></a><a name="sparc_002dx_002dlinux"></a>sparc-*-linux*</h3>

<p>GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4

or newer on this platform. All earlier binutils and glibc

@@ -1287,7 +1364,7 @@ releases mishandled unaligned relocations on <code>sparc-*-*</code> targets.

-<h3 class="heading"><a name="TOC49"></a><a name="sparc64_002dx_002dsolaris2"></a>sparc64-*-solaris2*</h3>

+<h3 class="heading"><a name="TOC54"></a><a name="sparc64_002dx_002dsolaris2"></a>sparc64-*-solaris2*</h3>

<p>When configuring the GNU Multiple Precision Library (GMP) or the

MPFR library, the canonical target triplet must be specified as

@@ -1301,18 +1378,18 @@ step in order to bootstrap this target with the Sun compiler:

<pre class="smallexample"> % CC="cc -xarch=v9 -xildoff" <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>]

</pre>

- <p><samp><span class="option">-xarch=v9</span></samp> specifies the SPARC-V9 architecture to the Sun toolchain

+ <p class="noindent"><samp><span class="option">-xarch=v9</span></samp> specifies the SPARC-V9 architecture to the Sun toolchain

and <samp><span class="option">-xildoff</span></samp> turns off the incremental linker.

-<h3 class="heading"><a name="TOC50"></a><a name="sparcv9_002dx_002dsolaris2"></a>sparcv9-*-solaris2*</h3>

+<h3 class="heading"><a name="TOC55"></a><a name="sparcv9_002dx_002dsolaris2"></a>sparcv9-*-solaris2*</h3>

-<p>This is a synonym for sparc64-*-solaris2*.

+<p>This is a synonym for ‘<samp><span class="samp">sparc64-*-solaris2*</span></samp>’.

-<h3 class="heading"><a name="TOC51"></a><a name="x_002dx_002dvxworks"></a>*-*-vxworks*</h3>

+<h3 class="heading"><a name="TOC56"></a><a name="x_002dx_002dvxworks"></a>*-*-vxworks*</h3>

<p>Support for VxWorks is in flux. At present GCC supports <em>only</em> the

very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC.

@@ -1347,7 +1424,7 @@ VxWorks will incorporate this module.)

-<h3 class="heading"><a name="TOC52"></a><a name="x86_002d64_002dx_002dx"></a>x86_64-*-*, amd64-*-*</h3>

+<h3 class="heading"><a name="TOC57"></a><a name="x86_002d64_002dx_002dx"></a>x86_64-*-*, amd64-*-*</h3>

<p>GCC supports the x86-64 architecture implemented by the AMD64 processor

(amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD.

@@ -1356,7 +1433,7 @@ both 64-bit x86-64 and 32-bit x86 code (via the <samp><span class="option">-m32<

-<h3 class="heading"><a name="TOC53"></a><a name="xtensa_002dx_002delf"></a>xtensa*-*-elf</h3>

+<h3 class="heading"><a name="TOC58"></a><a name="xtensa_002dx_002delf"></a>xtensa*-*-elf</h3>

<p>This target is intended for embedded Xtensa systems using the

‘<samp><span class="samp">newlib</span></samp>’ C library. It uses ELF but does not support shared

@@ -1373,7 +1450,7 @@ which you can use to replace the default header file.

-<h3 class="heading"><a name="TOC54"></a><a name="xtensa_002dx_002dlinux"></a>xtensa*-*-linux*</h3>

+<h3 class="heading"><a name="TOC59"></a><a name="xtensa_002dx_002dlinux"></a>xtensa*-*-linux*</h3>

<p>This target is for Xtensa systems running GNU/Linux. It supports ELF

shared objects and the GNU C library (glibc). It also generates

@@ -1384,9 +1461,9 @@ respects, this target is the same as the

-<h3 class="heading"><a name="TOC55"></a><a name="windows"></a>Microsoft Windows</h3>

+<h3 class="heading"><a name="TOC60"></a><a name="windows"></a>Microsoft Windows</h3>

-<h4 class="subheading"><a name="TOC56"></a>Intel 16-bit versions</h4>

+<h4 class="subheading"><a name="TOC61"></a>Intel 16-bit versions</h4>

<p>The 16-bit versions of Microsoft Windows, such as Windows 3.1, are not

supported.

@@ -1394,7 +1471,7 @@ supported.

<p>However, the 32-bit port has limited support for Microsoft

Windows 3.11 in the Win32s environment, as a target only. See below.

-<h4 class="subheading"><a name="TOC57"></a>Intel 32-bit versions</h4>

+<h4 class="subheading"><a name="TOC62"></a>Intel 32-bit versions</h4>

<p>The 32-bit versions of Windows, including Windows 95, Windows NT, Windows

XP, and Windows Vista, are supported by several different target

@@ -1406,13 +1483,13 @@ and which C libraries are used.

Linux API emulation layer in the Win32 subsystem.

<li>Interix <a href="#x-x-interix">*-*-interix</a>: The Interix subsystem

provides native support for POSIX.

-<li>MinGW <a href="#x-x-mingw">*-*-mingw</a>: MinGW is a native GCC port for

+<li>MinGW <a href="#x-x-mingw32">*-*-mingw32</a>: MinGW is a native GCC port for

the Win32 subsystem that provides a subset of POSIX.

<li>MKS i386-pc-mks: NuTCracker from MKS. See

<a href="http://www.mkssoftware.com/">http://www.mkssoftware.com/</a> for more information.

</ul>

-<h4 class="subheading"><a name="TOC58"></a>Intel 64-bit versions</h4>

+<h4 class="subheading"><a name="TOC63"></a>Intel 64-bit versions</h4>

<p>GCC contains support for x86-64 using the mingw-w64

runtime library, available from <a href="http://mingw-w64.sourceforge.net/">http://mingw-w64.sourceforge.net/</a>.

@@ -1420,12 +1497,12 @@ This library should be used with the target triple x86_64-pc-mingw32.

<p>Presently Windows for Itanium is not supported.

-<h4 class="subheading"><a name="TOC59"></a>Windows CE</h4>

+<h4 class="subheading"><a name="TOC64"></a>Windows CE</h4>

<p>Windows CE is supported as a target only on ARM (arm-wince-pe), Hitachi

SuperH (sh-wince-pe), and MIPS (mips-wince-pe).

-<h4 class="subheading"><a name="TOC60"></a>Other Windows Platforms</h4>

+<h4 class="subheading"><a name="TOC65"></a>Other Windows Platforms</h4>

<p>GCC no longer supports Windows NT on the Alpha or PowerPC.

@@ -1441,7 +1518,7 @@ be inactive. See <a href="http://pw32.sourceforge.net/">http://pw32.sourceforge

-<h3 class="heading"><a name="TOC61"></a><a name="x_002dx_002dcygwin"></a>*-*-cygwin</h3>

+<h3 class="heading"><a name="TOC66"></a><a name="x_002dx_002dcygwin"></a>*-*-cygwin</h3>

<p>Ports of GCC are included with the

<a href="http://www.cygwin.com/">Cygwin environment</a>.

@@ -1449,11 +1526,15 @@ be inactive. See <a href="http://pw32.sourceforge.net/">http://pw32.sourceforge

<p>GCC will build under Cygwin without modification; it does not build

with Microsoft's C++ compiler and there are no plans to make it do so.

- <p>Cygwin can be compiled with i?86-pc-cygwin.

+ <p>The Cygwin native compiler can be configured to target any 32-bit x86

+cpu architecture desired; the default is i686-pc-cygwin. It should be

+used with as up-to-date a version of binutils as possible; use either

+the latest official GNU binutils release in the Cygwin distribution,

+or version 2.20 or above if building your own.

-<h3 class="heading"><a name="TOC62"></a><a name="x_002dx_002dinterix"></a>*-*-interix</h3>

+<h3 class="heading"><a name="TOC67"></a><a name="x_002dx_002dinterix"></a>*-*-interix</h3>

<p>The Interix target is used by OpenNT, Interix, Services For UNIX (SFU),

and Subsystem for UNIX-based Applications (SUA). Applications compiled

@@ -1464,7 +1545,7 @@ the Win32 subsystem. This target was last known to work in GCC 3.3.

-<h3 class="heading"><a name="TOC63"></a><a name="x_002dx_002dmingw32"></a>*-*-mingw32</h3>

+<h3 class="heading"><a name="TOC68"></a><a name="x_002dx_002dmingw32"></a>*-*-mingw32</h3>

<p>GCC will build with and support only MinGW runtime 3.12 and later.

Earlier versions of headers are incompatible with the new default semantics

@@ -1472,15 +1553,7 @@ of <code>extern inline</code> in <code>-std=c99</code> and <code>-std=gnu99</cod

-<h3 class="heading"><a name="TOC64"></a><a name="os2"></a>OS/2</h3>

-<p>GCC does not currently support OS/2. However, Andrew Zabolotny has been

-working on a generic OS/2 port with pgcc. The current code can be found

-at <a href="http://www.goof.com/pcg/os2/">http://www.goof.com/pcg/os2/</a>.

- <p><hr />

-<h3 class="heading"><a name="TOC65"></a><a name="older"></a>Older systems</h3>

+<h3 class="heading"><a name="TOC69"></a><a name="older"></a>Older systems</h3>

<p>GCC contains support files for many older (1980s and early

1990s) Unix variants. For the most part, support for these systems

@@ -1524,7 +1597,7 @@ current GCC) is to be found in the GCC texinfo manual.

-<h3 class="heading"><a name="TOC66"></a><a name="elf"></a>all ELF targets (SVR4, Solaris 2, etc.)</h3>

+<h3 class="heading"><a name="TOC70"></a><a name="elf"></a>all ELF targets (SVR4, Solaris 2, etc.)</h3>

<p>C++ support is significantly better on ELF targets if you use the

<a href="./configure.html#with-gnu-ld">GNU linker</a>; duplicate copies of

« no previous file with comments | « gcc/INSTALL/prerequisites.html ('k') | gcc/INSTALL/test.html » ('j') | no next file with comments »