Home | History | Annotate | Line # | Download | only in INSTALL
specific.html revision 1.6
      1 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
      2 <html>
      3 <!-- Copyright (C) 1988-2015 Free Software Foundation, Inc.
      4 
      5 Permission is granted to copy, distribute and/or modify this document
      6 under the terms of the GNU Free Documentation License, Version 1.3 or
      7 any later version published by the Free Software Foundation; with no
      8 Invariant Sections, the Front-Cover texts being (a) (see below), and
      9 with the Back-Cover Texts being (b) (see below).  A copy of the
     10 license is included in the section entitled "GNU
     11 Free Documentation License".
     12 
     13 (a) The FSF's Front-Cover Text is:
     14 
     15 A GNU Manual
     16 
     17 (b) The FSF's Back-Cover Text is:
     18 
     19 You have freedom to copy and modify this GNU Manual, like GNU
     20      software.  Copies published by the Free Software Foundation raise
     21      funds for GNU development. -->
     22 <!-- Created by GNU Texinfo 6.1, http://www.gnu.org/software/texinfo/ -->
     23 <head>
     24 <title>Installing GCC</title>
     25 
     26 <meta name="description" content="Installing GCC">
     27 <meta name="keywords" content="Installing GCC">
     28 <meta name="resource-type" content="document">
     29 <meta name="distribution" content="global">
     30 <meta name="Generator" content="makeinfo">
     31 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
     32 <style type="text/css">
     33 <!--
     34 a.summary-letter {text-decoration: none}
     35 blockquote.indentedblock {margin-right: 0em}
     36 blockquote.smallindentedblock {margin-right: 0em; font-size: smaller}
     37 blockquote.smallquotation {font-size: smaller}
     38 div.display {margin-left: 3.2em}
     39 div.example {margin-left: 3.2em}
     40 div.lisp {margin-left: 3.2em}
     41 div.smalldisplay {margin-left: 3.2em}
     42 div.smallexample {margin-left: 3.2em}
     43 div.smalllisp {margin-left: 3.2em}
     44 kbd {font-style: oblique}
     45 pre.display {font-family: inherit}
     46 pre.format {font-family: inherit}
     47 pre.menu-comment {font-family: serif}
     48 pre.menu-preformatted {font-family: serif}
     49 pre.smalldisplay {font-family: inherit; font-size: smaller}
     50 pre.smallexample {font-size: smaller}
     51 pre.smallformat {font-family: inherit; font-size: smaller}
     52 pre.smalllisp {font-size: smaller}
     53 span.nolinebreak {white-space: nowrap}
     54 span.roman {font-family: initial; font-weight: normal}
     55 span.sansserif {font-family: sans-serif; font-weight: normal}
     56 ul.no-bullet {list-style: none}
     57 -->
     58 </style>
     59 
     60 
     61 </head>
     62 
     63 <body lang="en">
     64 <h1 class="settitle" align="center">Installing GCC</h1>
     65 
     66 
     67 
     68 
     69 
     70 
     71 
     72 
     73 
     74 
     75 
     76 
     77 
     78 
     79 
     80 
     81 
     82 
     83 
     84 
     85 
     86 
     87 
     88 
     89 <a name="index-Specific"></a>
     90 <a name="index-Specific-installation-notes"></a>
     91 <a name="index-Target-specific-installation"></a>
     92 <a name="index-Host-specific-installation"></a>
     93 <a name="index-Target-specific-installation-notes"></a>
     94 
     95 <p>Please read this document carefully <em>before</em> installing the
     96 GNU Compiler Collection on your machine.
     97 </p>
     98 <p>Note that this list of install notes is <em>not</em> a list of supported
     99 hosts or targets.  Not all supported hosts and targets are listed
    100 here, only the ones that require host-specific or target-specific
    101 information have to. 
    102 </p>
    103 <ul>
    104 <li> <a href="#aarch64-x-x">aarch64*-*-*</a>
    105 </li><li> <a href="#alpha-x-x">alpha*-*-*</a>
    106 </li><li> <a href="#alpha-dec-osf51">alpha*-dec-osf5.1</a>
    107 </li><li> <a href="#amd64-x-solaris210">amd64-*-solaris2.10</a>
    108 </li><li> <a href="#arm-x-eabi">arm-*-eabi</a>
    109 </li><li> <a href="#avr">avr</a>
    110 </li><li> <a href="#bfin">Blackfin</a>
    111 </li><li> <a href="#dos">DOS</a>
    112 </li><li> <a href="#x-x-freebsd">*-*-freebsd*</a>
    113 </li><li> <a href="#h8300-hms">h8300-hms</a>
    114 </li><li> <a href="#hppa-hp-hpux">hppa*-hp-hpux*</a>
    115 </li><li> <a href="#hppa-hp-hpux10">hppa*-hp-hpux10</a>
    116 </li><li> <a href="#hppa-hp-hpux11">hppa*-hp-hpux11</a>
    117 </li><li> <a href="#x-x-linux-gnu">*-*-linux-gnu</a>
    118 </li><li> <a href="#ix86-x-linux">i?86-*-linux*</a>
    119 </li><li> <a href="#ix86-x-solaris210">i?86-*-solaris2.10</a>
    120 </li><li> <a href="#ia64-x-linux">ia64-*-linux</a>
    121 </li><li> <a href="#ia64-x-hpux">ia64-*-hpux*</a>
    122 </li><li> <a href="#x-ibm-aix">*-ibm-aix*</a>
    123 </li><li> <a href="#iq2000-x-elf">iq2000-*-elf</a>
    124 </li><li> <a href="#lm32-x-elf">lm32-*-elf</a>
    125 </li><li> <a href="#lm32-x-uclinux">lm32-*-uclinux</a>
    126 </li><li> <a href="#m32c-x-elf">m32c-*-elf</a>
    127 </li><li> <a href="#m32r-x-elf">m32r-*-elf</a>
    128 </li><li> <a href="#m68k-x-x">m68k-*-*</a>
    129 </li><li> <a href="#m68k-uclinux">m68k-uclinux</a>
    130 </li><li> <a href="#mep-x-elf">mep-*-elf</a>
    131 </li><li> <a href="#microblaze-x-elf">microblaze-*-elf</a>
    132 </li><li> <a href="#mips-x-x">mips-*-*</a>
    133 </li><li> <a href="#mips-sgi-irix5">mips-sgi-irix5</a>
    134 </li><li> <a href="#mips-sgi-irix6">mips-sgi-irix6</a>
    135 </li><li> <a href="#nds32le-x-elf">nds32le-*-elf</a>
    136 </li><li> <a href="#nds32be-x-elf">nds32be-*-elf</a>
    137 </li><li> <a href="#nvptx-x-none">nvptx-*-none</a>
    138 </li><li> <a href="#powerpc-x-x">powerpc*-*-*</a>
    139 </li><li> <a href="#powerpc-x-darwin">powerpc-*-darwin*</a>
    140 </li><li> <a href="#powerpc-x-elf">powerpc-*-elf</a>
    141 </li><li> <a href="#powerpc-x-linux-gnu">powerpc*-*-linux-gnu*</a>
    142 </li><li> <a href="#powerpc-x-netbsd">powerpc-*-netbsd*</a>
    143 </li><li> <a href="#powerpc-x-eabisim">powerpc-*-eabisim</a>
    144 </li><li> <a href="#powerpc-x-eabi">powerpc-*-eabi</a>
    145 </li><li> <a href="#powerpcle-x-elf">powerpcle-*-elf</a>
    146 </li><li> <a href="#powerpcle-x-eabisim">powerpcle-*-eabisim</a>
    147 </li><li> <a href="#powerpcle-x-eabi">powerpcle-*-eabi</a>
    148 </li><li> <a href="#s390-x-linux">s390-*-linux*</a>
    149 </li><li> <a href="#s390x-x-linux">s390x-*-linux*</a>
    150 </li><li> <a href="#s390x-ibm-tpf">s390x-ibm-tpf*</a>
    151 </li><li> <a href="#x-x-solaris2">*-*-solaris2*</a>
    152 </li><li> <a href="#sparc-x-x">sparc*-*-*</a>
    153 </li><li> <a href="#sparc-sun-solaris2">sparc-sun-solaris2*</a>
    154 </li><li> <a href="#sparc-sun-solaris210">sparc-sun-solaris2.10</a>
    155 </li><li> <a href="#sparc-x-linux">sparc-*-linux*</a>
    156 </li><li> <a href="#sparc64-x-solaris2">sparc64-*-solaris2*</a>
    157 </li><li> <a href="#sparcv9-x-solaris2">sparcv9-*-solaris2*</a>
    158 </li><li> <a href="#c6x-x-x">c6x-*-*</a>
    159 </li><li> <a href="#tilegx-x-linux">tilegx-*-linux*</a>
    160 </li><li> <a href="#tilegxbe-x-linux">tilegxbe-*-linux*</a>
    161 </li><li> <a href="#tilepro-x-linux">tilepro-*-linux*</a>
    162 </li><li> <a href="#visium-x-elf">visium-*-elf</a>
    163 </li><li> <a href="#x-x-vxworks">*-*-vxworks*</a>
    164 </li><li> <a href="#x86-64-x-x">x86_64-*-*, amd64-*-*</a>
    165 </li><li> <a href="#x86-64-x-solaris210">x86_64-*-solaris2.1[0-9]*</a>
    166 </li><li> <a href="#xtensa-x-elf">xtensa*-*-elf</a>
    167 </li><li> <a href="#xtensa-x-linux">xtensa*-*-linux*</a>
    168 </li><li> <a href="#windows">Microsoft Windows</a>
    169 </li><li> <a href="#x-x-cygwin">*-*-cygwin</a>
    170 </li><li> <a href="#x-x-interix">*-*-interix</a>
    171 </li><li> <a href="#x-x-mingw32">*-*-mingw32</a>
    172 </li><li> <a href="#os2">OS/2</a>
    173 </li><li> <a href="#older">Older systems</a>
    174 </li></ul>
    175 
    176 <ul>
    177 <li> <a href="#elf">all ELF targets</a> (SVR4, Solaris 2, etc.)
    178 </li></ul>
    179 
    180 
    181 <!-- -------- host/target specific issues start here ---------------- -->
    182 <hr />
    183 <a name="aarch64_002dx_002dx"></a><a name="aarch64_002a_002d_002a_002d_002a"></a>
    184 <h3 class="heading">aarch64*-*-*</h3>
    185 <p>Binutils pre 2.24 does not have support for selecting <samp>-mabi</samp> and
    186 does not support ILP32.  If it is used to build GCC 4.9 or later, GCC will
    187 not support option <samp>-mabi=ilp32</samp>.
    188 </p>
    189 <p>To enable a workaround for the Cortex-A53 erratum number 835769 by default
    190 (for all CPUs regardless of -mcpu option given) at configure time use the
    191 <samp>--enable-fix-cortex-a53-835769</samp> option.  This will enable the fix by
    192 default and can be explicitly disabled during compilation by passing the
    193 <samp>-mno-fix-cortex-a53-835769</samp> option.  Conversely,
    194 <samp>--disable-fix-cortex-a53-835769</samp> will disable the workaround by
    195 default.  The workaround is disabled by default if neither of
    196 <samp>--enable-fix-cortex-a53-835769</samp> or
    197 <samp>--disable-fix-cortex-a53-835769</samp> is given at configure time.
    198 </p>
    199 <p>To enable a workaround for the Cortex-A53 erratum number 843419 by default
    200 (for all CPUs regardless of -mcpu option given) at configure time use the
    201 <samp>--enable-fix-cortex-a53-843419</samp> option.  This workaround is applied at
    202 link time.  Enabling the workaround will cause GCC to pass the relevant option
    203 to the linker.  It can be explicitly disabled during compilation by passing the
    204 <samp>-mno-fix-cortex-a53-843419</samp> option.  Conversely,
    205 <samp>--disable-fix-cortex-a53-843419</samp> will disable the workaround by default.
    206 The workaround is disabled by default if neither of
    207 <samp>--enable-fix-cortex-a53-843419</samp> or
    208 <samp>--disable-fix-cortex-a53-843419</samp> is given at configure time.
    209 </p>
    210 <hr />
    211 <a name="alpha_002dx_002dx"></a><a name="alpha_002a_002d_002a_002d_002a"></a>
    212 <h3 class="heading">alpha*-*-*</h3>
    213 <p>This section contains general configuration information for all
    214 alpha-based platforms using ELF (in particular, ignore this section for
    215 DEC OSF/1, Digital UNIX and Tru64 UNIX).  In addition to reading this
    216 section, please read all other sections that match your target.
    217 </p>
    218 <p>We require binutils 2.11.2 or newer.
    219 Previous binutils releases had a number of problems with DWARF 2
    220 debugging information, not the least of which is incorrect linking of
    221 shared libraries.
    222 </p>
    223 <hr />
    224 <a name="alpha_002ddec_002dosf51"></a><a name="alpha_002a_002ddec_002dosf5_002e1"></a>
    225 <h3 class="heading">alpha*-dec-osf5.1</h3>
    226 <p>Systems using processors that implement the DEC Alpha architecture and
    227 are running the DEC/Compaq/HP Unix (DEC OSF/1, Digital UNIX, or Compaq/HP
    228 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
    229 </p>
    230 <p>Support for Tru64 UNIX V5.1 has been removed in GCC 4.8.  As of GCC 4.6,
    231 support for Tru64 UNIX V4.0 and V5.0 has been removed.  As of GCC 3.2,
    232 versions before <code>alpha*-dec-osf4</code> are no longer supported.  (These
    233 are the versions which identify themselves as DEC OSF/1.)
    234 </p>
    235 <hr />
    236 <a name="amd64_002dx_002dsolaris210"></a><a name="amd64_002d_002a_002dsolaris2_002e1_005b0_002d9_005d_002a"></a>
    237 <h3 class="heading">amd64-*-solaris2.1[0-9]*</h3>
    238 <p>This is a synonym for &lsquo;<samp>x86_64-*-solaris2.1[0-9]*</samp>&rsquo;.
    239 </p>
    240 <hr />
    241 <a name="arc_002dx_002delf32"></a><a name="arc_002d_002a_002delf32"></a>
    242 <h3 class="heading">arc-*-elf32</h3>
    243 
    244 <p>Use &lsquo;<samp>configure --target=arc-elf32 --with-cpu=<var>cpu</var> --enable-languages=&quot;c,c++&quot;</samp>&rsquo;
    245 to configure GCC, with <var>cpu</var> being one of &lsquo;<samp>arc600</samp>&rsquo;, &lsquo;<samp>arc601</samp>&rsquo;,
    246 or &lsquo;<samp>arc700</samp>&rsquo;.
    247 </p>
    248 <hr />
    249 <a name="arc_002dlinux_002duclibc"></a><a name="arc_002dlinux_002duclibc-1"></a>
    250 <h3 class="heading">arc-linux-uclibc</h3>
    251 
    252 <p>Use &lsquo;<samp>configure --target=arc-linux-uclibc --with-cpu=arc700 --enable-languages=&quot;c,c++&quot;</samp>&rsquo; to configure GCC.
    253 </p>
    254 <hr />
    255 <a name="arm_002dx_002deabi"></a><a name="arm_002d_002a_002deabi"></a>
    256 <h3 class="heading">arm-*-eabi</h3>
    257 <p>ARM-family processors.  Subtargets that use the ELF object format
    258 require GNU binutils 2.13 or newer.  Such subtargets include:
    259 <code>arm-*-netbsdelf</code>, <code>arm-*-*linux-*</code>
    260 and <code>arm-*-rtemseabi</code>.
    261 </p>
    262 <hr />
    263 <a name="avr"></a><a name="avr-1"></a>
    264 <h3 class="heading">avr</h3>
    265 <p>ATMEL AVR-family micro controllers.  These are used in embedded
    266 applications.  There are no standard Unix configurations.
    267 See &ldquo;AVR Options&rdquo; in the main manual
    268 for the list of supported MCU types.
    269 </p>
    270 <p>Use &lsquo;<samp>configure --target=avr --enable-languages=&quot;c&quot;</samp>&rsquo; to configure GCC.
    271 </p>
    272 <p>Further installation notes and other useful information about AVR tools
    273 can also be obtained from:
    274 </p>
    275 <ul>
    276 <li> <a href="http://www.nongnu.org/avr/">http://www.nongnu.org/avr/</a>
    277 </li><li> <a href="http://www.amelek.gda.pl/avr/">http://www.amelek.gda.pl/avr/</a>
    278 </li></ul>
    279 
    280 <p>We <em>strongly</em> recommend using binutils 2.13 or newer.
    281 </p>
    282 <p>The following error:
    283 </p><div class="smallexample">
    284 <pre class="smallexample">Error: register required
    285 </pre></div>
    286 
    287 <p>indicates that you should upgrade to a newer version of the binutils.
    288 </p>
    289 <hr />
    290 <a name="bfin"></a><a name="Blackfin"></a>
    291 <h3 class="heading">Blackfin</h3>
    292 <p>The Blackfin processor, an Analog Devices DSP.
    293 See &ldquo;Blackfin Options&rdquo; in the main manual
    294 </p>
    295 <p>More information, and a version of binutils with support for this processor,
    296 is available at <a href="http://blackfin.uclinux.org">http://blackfin.uclinux.org</a>
    297 </p>
    298 <hr />
    299 <a name="cr16"></a><a name="CR16"></a>
    300 <h3 class="heading">CR16</h3>
    301 <p>The CR16 CompactRISC architecture is a 16-bit architecture. This
    302 architecture is used in embedded applications.
    303 </p>
    304 
    305 <p>See &ldquo;CR16 Options&rdquo; in the main manual for a list of CR16-specific options.
    306 </p>
    307 <p>Use &lsquo;<samp>configure --target=cr16-elf --enable-languages=c,c++</samp>&rsquo; to configure
    308 GCC&nbsp;for building a CR16 elf cross-compiler.
    309 </p>
    310 <p>Use &lsquo;<samp>configure --target=cr16-uclinux --enable-languages=c,c++</samp>&rsquo; to
    311 configure GCC&nbsp;for building a CR16 uclinux cross-compiler.
    312 </p>
    313 <hr />
    314 <a name="cris"></a><a name="CRIS"></a>
    315 <h3 class="heading">CRIS</h3>
    316 <p>CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
    317 series.  These are used in embedded applications.
    318 </p>
    319 <p>See &ldquo;CRIS Options&rdquo; in the main manual
    320 for a list of CRIS-specific options.
    321 </p>
    322 <p>There are a few different CRIS targets:
    323 </p><dl compact="compact">
    324 <dt><code>cris-axis-elf</code></dt>
    325 <dd><p>Mainly for monolithic embedded systems.  Includes a multilib for the
    326 &lsquo;<samp>v10</samp>&rsquo; core used in &lsquo;<samp>ETRAX 100 LX</samp>&rsquo;.
    327 </p></dd>
    328 <dt><code>cris-axis-linux-gnu</code></dt>
    329 <dd><p>A GNU/Linux port for the CRIS architecture, currently targeting
    330 &lsquo;<samp>ETRAX 100 LX</samp>&rsquo; by default.
    331 </p></dd>
    332 </dl>
    333 
    334 <p>For <code>cris-axis-elf</code> you need binutils 2.11
    335 or newer.  For <code>cris-axis-linux-gnu</code> you need binutils 2.12 or newer.
    336 </p>
    337 <p>Pre-packaged tools can be obtained from
    338 <a href="ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/">ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/</a>.  More
    339 information about this platform is available at
    340 <a href="http://developer.axis.com/">http://developer.axis.com/</a>.
    341 </p>
    342 <hr />
    343 <a name="dos"></a><a name="DOS"></a>
    344 <h3 class="heading">DOS</h3>
    345 <p>Please have a look at the <a href="binaries.html">binaries page</a>.
    346 </p>
    347 <p>You cannot install GCC by itself on MSDOS; it will not compile under
    348 any MSDOS compiler except itself.  You need to get the complete
    349 compilation package DJGPP, which includes binaries as well as sources,
    350 and includes all the necessary compilation tools and libraries.
    351 </p>
    352 <hr />
    353 <a name="epiphany_002dx_002delf"></a><a name="epiphany_002d_002a_002delf"></a>
    354 <h3 class="heading">epiphany-*-elf</h3>
    355 <p>Adapteva Epiphany.
    356 This configuration is intended for embedded systems.
    357 </p>
    358 <hr />
    359 <a name="x_002dx_002dfreebsd"></a><a name="g_t_002a_002d_002a_002dfreebsd_002a"></a>
    360 <h3 class="heading">*-*-freebsd*</h3>
    361 <p>Support for FreeBSD 1 was discontinued in GCC 3.2.  Support for
    362 FreeBSD 2 (and any mutant a.out variants of FreeBSD 3) was
    363 discontinued in GCC 4.0.
    364 </p>
    365 <p>In order to better utilize FreeBSD base system functionality and match
    366 the configuration of the system compiler, GCC 4.5 and above as well as
    367 GCC 4.4 past 2010-06-20 leverage SSP support in libc (which is present
    368 on FreeBSD 7 or later) and the use of <code>__cxa_atexit</code> by default
    369 (on FreeBSD 6 or later).  The use of <code>dl_iterate_phdr</code> inside
    370 <samp>libgcc_s.so.1</samp> and boehm-gc (on FreeBSD 7 or later) is enabled
    371 by GCC 4.5 and above.
    372 </p>
    373 <p>We support FreeBSD using the ELF file format with DWARF 2 debugging
    374 for all CPU architectures.  You may use <samp>-gstabs</samp> instead of
    375 <samp>-g</samp>, if you really want the old debugging format.  There are
    376 no known issues with mixing object files and libraries with different
    377 debugging formats.  Otherwise, this release of GCC should now match
    378 more of the configuration used in the stock FreeBSD configuration of
    379 GCC.  In particular, <samp>--enable-threads</samp> is now configured by
    380 default.  However, as a general user, do not attempt to replace the
    381 system compiler with this release.  Known to bootstrap and check with
    382 good results on FreeBSD 7.2-STABLE.  In the past, known to bootstrap
    383 and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4,
    384 4.5, 4.8, 4.9 and 5-CURRENT.
    385 </p>
    386 <p>The version of binutils installed in <samp>/usr/bin</samp> probably works
    387 with this release of GCC.  Bootstrapping against the latest GNU
    388 binutils and/or the version found in <samp>/usr/ports/devel/binutils</samp> has
    389 been known to enable additional features and improve overall testsuite
    390 results.  However, it is currently known that boehm-gc (which itself
    391 is required for java) may not configure properly on FreeBSD prior to
    392 the FreeBSD 7.0 release with GNU binutils after 2.16.1.
    393 </p>
    394 <hr />
    395 <a name="h8300_002dhms"></a><a name="h8300_002dhms-1"></a>
    396 <h3 class="heading">h8300-hms</h3>
    397 <p>Renesas H8/300 series of processors.
    398 </p>
    399 <p>Please have a look at the <a href="binaries.html">binaries page</a>.
    400 </p>
    401 <p>The calling convention and structure layout has changed in release 2.6.
    402 All code must be recompiled.  The calling convention now passes the
    403 first three arguments in function calls in registers.  Structures are no
    404 longer a multiple of 2 bytes.
    405 </p>
    406 <hr />
    407 <a name="hppa_002dhp_002dhpux"></a><a name="hppa_002a_002dhp_002dhpux_002a"></a>
    408 <h3 class="heading">hppa*-hp-hpux*</h3>
    409 <p>Support for HP-UX version 9 and older was discontinued in GCC 3.4.
    410 </p>
    411 <p>We require using gas/binutils on all hppa platforms.  Version 2.19 or
    412 later is recommended.
    413 </p>
    414 <p>It may be helpful to configure GCC with the
    415 <a href="./configure.html#with-gnu-as"><samp>--with-gnu-as</samp></a> and
    416 <samp>--with-as=&hellip;</samp> options to ensure that GCC can find GAS.
    417 </p>
    418 <p>The HP assembler should not be used with GCC.  It is rarely tested and may
    419 not work.  It shouldn&rsquo;t be used with any languages other than C due to its
    420 many limitations.
    421 </p>
    422 <p>Specifically, <samp>-g</samp> does not work (HP-UX uses a peculiar debugging
    423 format which GCC does not know about).  It also inserts timestamps
    424 into each object file it creates, causing the 3-stage comparison test to
    425 fail during a bootstrap.  You should be able to continue by saying
    426 &lsquo;<samp>make all-host all-target</samp>&rsquo; after getting the failure from &lsquo;<samp>make</samp>&rsquo;.
    427 </p>
    428 <p>Various GCC features are not supported.  For example, it does not support weak
    429 symbols or alias definitions.  As a result, explicit template instantiations
    430 are required when using C++.  This makes it difficult if not impossible to
    431 build many C++ applications.
    432 </p>
    433 <p>There are two default scheduling models for instructions.  These are
    434 PROCESSOR_7100LC and PROCESSOR_8000.  They are selected from the pa-risc
    435 architecture specified for the target machine when configuring.
    436 PROCESSOR_8000 is the default.  PROCESSOR_7100LC is selected when
    437 the target is a &lsquo;<samp>hppa1*</samp>&rsquo; machine.
    438 </p>
    439 <p>The PROCESSOR_8000 model is not well suited to older processors.  Thus,
    440 it is important to completely specify the machine architecture when
    441 configuring if you want a model other than PROCESSOR_8000.  The macro
    442 TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
    443 default scheduling model is desired.
    444 </p>
    445 <p>As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10
    446 through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later.
    447 This namespace change might cause problems when bootstrapping with
    448 an earlier version of GCC or the HP compiler as essentially the same
    449 namespace is required for an entire build.  This problem can be avoided
    450 in a number of ways.  With HP cc, <code>UNIX_STD</code> can be set to &lsquo;<samp>95</samp>&rsquo;
    451 or &lsquo;<samp>98</samp>&rsquo;.  Another way is to add an appropriate set of predefines
    452 to <code>CC</code>.  The description for the <samp>munix=</samp> option contains
    453 a list of the predefines used with each standard.
    454 </p>
    455 <p>More specific information to &lsquo;<samp>hppa*-hp-hpux*</samp>&rsquo; targets follows.
    456 </p>
    457 <hr />
    458 <a name="hppa_002dhp_002dhpux10"></a><a name="hppa_002a_002dhp_002dhpux10"></a>
    459 <h3 class="heading">hppa*-hp-hpux10</h3>
    460 <p>For hpux10.20, we <em>highly</em> recommend you pick up the latest sed patch
    461 <code>PHCO_19798</code> from HP.
    462 </p>
    463 <p>The C++ ABI has changed incompatibly in GCC 4.0.  COMDAT subspaces are
    464 used for one-only code and data.  This resolves many of the previous
    465 problems in using C++ on this target.  However, the ABI is not compatible
    466 with the one implemented under HP-UX 11 using secondary definitions.
    467 </p>
    468 <hr />
    469 <a name="hppa_002dhp_002dhpux11"></a><a name="hppa_002a_002dhp_002dhpux11"></a>
    470 <h3 class="heading">hppa*-hp-hpux11</h3>
    471 <p>GCC 3.0 and up support HP-UX 11.  GCC 2.95.x is not supported and cannot
    472 be used to compile GCC 3.0 and up.
    473 </p>
    474 <p>The libffi and libjava libraries haven&rsquo;t been ported to 64-bit HP-UX&nbsp;and don&rsquo;t build.
    475 </p>
    476 <p>Refer to <a href="binaries.html">binaries</a> for information about obtaining
    477 precompiled GCC binaries for HP-UX.  Precompiled binaries must be obtained
    478 to build the Ada language as it can&rsquo;t be bootstrapped using C.  Ada is
    479 only available for the 32-bit PA-RISC runtime.
    480 </p>
    481 <p>Starting with GCC 3.4 an ISO C compiler is required to bootstrap.  The
    482 bundled compiler supports only traditional C; you will need either HP&rsquo;s
    483 unbundled compiler, or a binary distribution of GCC.
    484 </p>
    485 <p>It is possible to build GCC 3.3 starting with the bundled HP compiler,
    486 but the process requires several steps.  GCC 3.3 can then be used to
    487 build later versions.  The fastjar program contains ISO C code and
    488 can&rsquo;t be built with the HP bundled compiler.  This problem can be
    489 avoided by not building the Java language.  For example, use the
    490 <samp>--enable-languages=&quot;c,c++,f77,objc&quot;</samp> option in your configure
    491 command.
    492 </p>
    493 <p>There are several possible approaches to building the distribution.
    494 Binutils can be built first using the HP tools.  Then, the GCC
    495 distribution can be built.  The second approach is to build GCC
    496 first using the HP tools, then build binutils, then rebuild GCC.
    497 There have been problems with various binary distributions, so it
    498 is best not to start from a binary distribution.
    499 </p>
    500 <p>On 64-bit capable systems, there are two distinct targets.  Different
    501 installation prefixes must be used if both are to be installed on
    502 the same system.  The &lsquo;<samp>hppa[1-2]*-hp-hpux11*</samp>&rsquo; target generates code
    503 for the 32-bit PA-RISC runtime architecture and uses the HP linker.
    504 The &lsquo;<samp>hppa64-hp-hpux11*</samp>&rsquo; target generates 64-bit code for the
    505 PA-RISC 2.0 architecture.
    506 </p>
    507 <p>The script config.guess now selects the target type based on the compiler
    508 detected during configuration.  You must define <code>PATH</code> or <code>CC</code> so
    509 that configure finds an appropriate compiler for the initial bootstrap.
    510 When <code>CC</code> is used, the definition should contain the options that are
    511 needed whenever <code>CC</code> is used.
    512 </p>
    513 <p>Specifically, options that determine the runtime architecture must be
    514 in <code>CC</code> to correctly select the target for the build.  It is also
    515 convenient to place many other compiler options in <code>CC</code>.  For example,
    516 <code>CC=&quot;cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE&quot;</code>
    517 can be used to bootstrap the GCC 3.3 branch with the HP compiler in
    518 64-bit K&amp;R/bundled mode.  The <samp>+DA2.0W</samp> option will result in
    519 the automatic selection of the &lsquo;<samp>hppa64-hp-hpux11*</samp>&rsquo; target.  The
    520 macro definition table of cpp needs to be increased for a successful
    521 build with the HP compiler.  _CLASSIC_TYPES and _HPUX_SOURCE need to
    522 be defined when building with the bundled compiler, or when using the
    523 <samp>-Ac</samp> option.  These defines aren&rsquo;t necessary with <samp>-Ae</samp>.
    524 </p>
    525 <p>It is best to explicitly configure the &lsquo;<samp>hppa64-hp-hpux11*</samp>&rsquo; target
    526 with the <samp>--with-ld=&hellip;</samp> option.  This overrides the standard
    527 search for ld.  The two linkers supported on this target require different
    528 commands.  The default linker is determined during configuration.  As a
    529 result, it&rsquo;s not possible to switch linkers in the middle of a GCC build.
    530 This has been reported to sometimes occur in unified builds of binutils
    531 and GCC.
    532 </p>
    533 <p>A recent linker patch must be installed for the correct operation of
    534 GCC 3.3 and later.  <code>PHSS_26559</code> and <code>PHSS_24304</code> are the
    535 oldest linker patches that are known to work.  They are for HP-UX
    536 11.00 and 11.11, respectively.  <code>PHSS_24303</code>, the companion to
    537 <code>PHSS_24304</code>, might be usable but it hasn&rsquo;t been tested.  These
    538 patches have been superseded.  Consult the HP patch database to obtain
    539 the currently recommended linker patch for your system.
    540 </p>
    541 <p>The patches are necessary for the support of weak symbols on the
    542 32-bit port, and for the running of initializers and finalizers.  Weak
    543 symbols are implemented using SOM secondary definition symbols.  Prior
    544 to HP-UX 11, there are bugs in the linker support for secondary symbols.
    545 The patches correct a problem of linker core dumps creating shared
    546 libraries containing secondary symbols, as well as various other
    547 linking issues involving secondary symbols.
    548 </p>
    549 <p>GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
    550 run initializers and finalizers on the 64-bit port.  The 32-bit port
    551 uses the linker <samp>+init</samp> and <samp>+fini</samp> options for the same
    552 purpose.  The patches correct various problems with the +init/+fini
    553 options, including program core dumps.  Binutils 2.14 corrects a
    554 problem on the 64-bit port resulting from HP&rsquo;s non-standard use of
    555 the .init and .fini sections for array initializers and finalizers.
    556 </p>
    557 <p>Although the HP and GNU linkers are both supported for the
    558 &lsquo;<samp>hppa64-hp-hpux11*</samp>&rsquo; target, it is strongly recommended that the
    559 HP linker be used for link editing on this target.
    560 </p>
    561 <p>At this time, the GNU linker does not support the creation of long
    562 branch stubs.  As a result, it can&rsquo;t successfully link binaries
    563 containing branch offsets larger than 8 megabytes.  In addition,
    564 there are problems linking shared libraries, linking executables
    565 with <samp>-static</samp>, and with dwarf2 unwind and exception support.
    566 It also doesn&rsquo;t provide stubs for internal calls to global functions
    567 in shared libraries, so these calls can&rsquo;t be overloaded.
    568 </p>
    569 <p>The HP dynamic loader does not support GNU symbol versioning, so symbol
    570 versioning is not supported.  It may be necessary to disable symbol
    571 versioning with <samp>--disable-symvers</samp> when using GNU ld.
    572 </p>
    573 <p>POSIX threads are the default.  The optional DCE thread library is not
    574 supported, so <samp>--enable-threads=dce</samp> does not work.
    575 </p>
    576 <hr />
    577 <a name="x_002dx_002dlinux_002dgnu"></a><a name="g_t_002a_002d_002a_002dlinux_002dgnu"></a>
    578 <h3 class="heading">*-*-linux-gnu</h3>
    579 <p>Versions of libstdc++-v3 starting with 3.2.1 require bug fixes present
    580 in glibc 2.2.5 and later.  More information is available in the
    581 libstdc++-v3 documentation.
    582 </p>
    583 <hr />
    584 <a name="ix86_002dx_002dlinux"></a><a name="i_003f86_002d_002a_002dlinux_002a"></a>
    585 <h3 class="heading">i?86-*-linux*</h3>
    586 <p>As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
    587 See <a href="http://gcc.gnu.org/PR10877">bug 10877</a> for more information.
    588 </p>
    589 <p>If you receive Signal 11 errors when building on GNU/Linux, then it is
    590 possible you have a hardware problem.  Further information on this can be
    591 found on <a href="http://www.bitwizard.nl/sig11/">www.bitwizard.nl</a>.
    592 </p>
    593 <hr />
    594 <a name="ix86_002dx_002dsolaris210"></a><a name="i_003f86_002d_002a_002dsolaris2_002e10"></a>
    595 <h3 class="heading">i?86-*-solaris2.10</h3>
    596 <p>Use this for Solaris 10 or later on x86 and x86-64 systems.  Starting
    597 with GCC 4.7, there is also a 64-bit &lsquo;<samp>amd64-*-solaris2.1[0-9]*</samp>&rsquo; or
    598 &lsquo;<samp>x86_64-*-solaris2.1[0-9]*</samp>&rsquo; configuration that corresponds to
    599 &lsquo;<samp>sparcv9-sun-solaris2*</samp>&rsquo;.
    600 </p>
    601 <p>It is recommended that you configure GCC to use the GNU assembler, in
    602 <samp>/usr/sfw/bin/gas</samp>.  The versions included in Solaris 10, from GNU
    603 binutils 2.15, and Solaris 11, from GNU binutils 2.19, work fine,
    604 although the current version, from GNU binutils
    605 2.22, is known to work, too.  Recent versions of the Sun assembler in
    606 <samp>/usr/ccs/bin/as</samp> work almost as well, though.
    607 </p>
    608 <p>For linking, the Sun linker, is preferred.  If you want to use the GNU
    609 linker instead, which is available in <samp>/usr/sfw/bin/gld</samp>, note that
    610 due to a packaging bug the version in Solaris 10, from GNU binutils
    611 2.15, cannot be used, while the version in Solaris 11, from GNU binutils
    612 2.19, works, as does the latest version, from GNU binutils 2.22.
    613 </p>
    614 <p>To use GNU <code>as</code>, configure with the options
    615 <samp>--with-gnu-as --with-as=/usr/sfw/bin/gas</samp>.  It may be necessary
    616 to configure with <samp>--without-gnu-ld --with-ld=/usr/ccs/bin/ld</samp> to
    617 guarantee use of Sun <code>ld</code>.
    618 </p>
    619 <hr />
    620 <a name="ia64_002dx_002dlinux"></a><a name="ia64_002d_002a_002dlinux"></a>
    621 <h3 class="heading">ia64-*-linux</h3>
    622 <p>IA-64 processor (also known as IPF, or Itanium Processor Family)
    623 running GNU/Linux.
    624 </p>
    625 <p>If you are using the installed system libunwind library with
    626 <samp>--with-system-libunwind</samp>, then you must use libunwind 0.98 or
    627 later.
    628 </p>
    629 <p>None of the following versions of GCC has an ABI that is compatible
    630 with any of the other versions in this list, with the exception that
    631 Red Hat 2.96 and Trillian 000171 are compatible with each other:
    632 3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
    633 This primarily affects C++ programs and programs that create shared libraries.
    634 GCC 3.1 or later is recommended for compiling linux, the kernel.
    635 As of version 3.1 GCC is believed to be fully ABI compliant, and hence no
    636 more major ABI changes are expected.
    637 </p>
    638 <hr />
    639 <a name="ia64_002dx_002dhpux"></a><a name="ia64_002d_002a_002dhpux_002a"></a>
    640 <h3 class="heading">ia64-*-hpux*</h3>
    641 <p>Building GCC on this target requires the GNU Assembler.  The bundled HP
    642 assembler will not work.  To prevent GCC from using the wrong assembler,
    643 the option <samp>--with-gnu-as</samp> may be necessary.
    644 </p>
    645 <p>The GCC libunwind library has not been ported to HPUX.  This means that for
    646 GCC versions 3.2.3 and earlier, <samp>--enable-libunwind-exceptions</samp>
    647 is required to build GCC.  For GCC 3.3 and later, this is the default.
    648 For gcc 3.4.3 and later, <samp>--enable-libunwind-exceptions</samp> is
    649 removed and the system libunwind library will always be used.
    650 </p>
    651 <hr />
    652 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
    653 <a name="x_002dibm_002daix"></a><a name="g_t_002a_002dibm_002daix_002a"></a>
    654 <h3 class="heading">*-ibm-aix*</h3>
    655 <p>Support for AIX version 3 and older was discontinued in GCC 3.4.
    656 Support for AIX version 4.2 and older was discontinued in GCC 4.5.
    657 </p>
    658 <p>&ldquo;out of memory&rdquo; bootstrap failures may indicate a problem with
    659 process resource limits (ulimit).  Hard limits are configured in the
    660 <samp>/etc/security/limits</samp> system configuration file.
    661 </p>
    662 <p>GCC can bootstrap with recent versions of IBM XLC, but bootstrapping
    663 with an earlier release of GCC is recommended.  Bootstrapping with XLC
    664 requires a larger data segment, which can be enabled through the
    665 <var>LDR_CNTRL</var> environment variable, e.g.,
    666 </p>
    667 <div class="smallexample">
    668 <pre class="smallexample">% LDR_CNTRL=MAXDATA=0x50000000
    669 % export LDR_CNTRL
    670 </pre></div>
    671 
    672 <p>One can start with a pre-compiled version of GCC to build from
    673 sources.  One may delete GCC&rsquo;s &ldquo;fixed&rdquo; header files when starting
    674 with a version of GCC built for an earlier release of AIX.
    675 </p>
    676 <p>To speed up the configuration phases of bootstrapping and installing GCC,
    677 one may use GNU Bash instead of AIX <code>/bin/sh</code>, e.g.,
    678 </p>
    679 <div class="smallexample">
    680 <pre class="smallexample">% CONFIG_SHELL=/opt/freeware/bin/bash
    681 % export CONFIG_SHELL
    682 </pre></div>
    683 
    684 <p>and then proceed as described in <a href="build.html">the build
    685 instructions</a>, where we strongly recommend specifying an absolute path
    686 to invoke <var>srcdir</var>/configure.
    687 </p>
    688 <p>Because GCC on AIX is built as a 32-bit executable by default,
    689 (although it can generate 64-bit programs) the GMP and MPFR libraries
    690 required by gfortran must be 32-bit libraries.  Building GMP and MPFR
    691 as static archive libraries works better than shared libraries.
    692 </p>
    693 <p>Errors involving <code>alloca</code> when building GCC generally are due
    694 to an incorrect definition of <code>CC</code> in the Makefile or mixing files
    695 compiled with the native C compiler and GCC.  During the stage1 phase of
    696 the build, the native AIX compiler <strong>must</strong> be invoked as <code>cc</code>
    697 (not <code>xlc</code>).  Once <code>configure</code> has been informed of
    698 <code>xlc</code>, one needs to use &lsquo;<samp>make distclean</samp>&rsquo; to remove the
    699 configure cache files and ensure that <code>CC</code> environment variable
    700 does not provide a definition that will confuse <code>configure</code>.
    701 If this error occurs during stage2 or later, then the problem most likely
    702 is the version of Make (see above).
    703 </p>
    704 <p>The native <code>as</code> and <code>ld</code> are recommended for
    705 bootstrapping on AIX.  The GNU Assembler, GNU Linker, and GNU
    706 Binutils version 2.20 is the minimum level that supports bootstrap on
    707 AIX 5.  The GNU Assembler has not been updated to support AIX 6&nbsp;or
    708 AIX 7.  The native AIX tools do interoperate with GCC.
    709 </p>
    710 <p>AIX 5.3 TL10, AIX 6.1 TL05 and AIX 7.1 TL00 introduced an AIX
    711 assembler change that sometimes produces corrupt assembly files
    712 causing AIX linker errors.  The bug breaks GCC bootstrap on AIX and
    713 can cause compilation failures with existing GCC installations.  An
    714 AIX iFix for AIX 5.3 is available (APAR IZ98385 for AIX 5.3 TL10, APAR
    715 IZ98477 for AIX 5.3 TL11 and IZ98134 for AIX 5.3 TL12). AIX 5.3 TL11 SP8,
    716 AIX 5.3 TL12 SP5, AIX 6.1 TL04 SP11, AIX 6.1 TL05 SP7, AIX 6.1 TL06 SP6,
    717 AIX 6.1 TL07 and AIX 7.1 TL01 should include the fix.
    718 </p>
    719 <p>Building <samp>libstdc++.a</samp> requires a fix for an AIX Assembler bug
    720 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1).  It also requires a
    721 fix for another AIX Assembler bug and a co-dependent AIX Archiver fix
    722 referenced as APAR IY53606 (AIX 5.2) or as APAR IY54774 (AIX 5.1)
    723 </p>
    724 <a name="TransferAixShobj"></a><p>&lsquo;<samp>libstdc++</samp>&rsquo; in GCC 3.4 increments the major version number of the
    725 shared object and GCC installation places the <samp>libstdc++.a</samp>
    726 shared library in a common location which will overwrite the and GCC
    727 3.3 version of the shared library.  Applications either need to be
    728 re-linked against the new shared library or the GCC 3.1 and GCC 3.3
    729 versions of the &lsquo;<samp>libstdc++</samp>&rsquo; shared object needs to be available
    730 to the AIX runtime loader.  The GCC 3.1 &lsquo;<samp>libstdc++.so.4</samp>&rsquo;, if
    731 present, and GCC 3.3 &lsquo;<samp>libstdc++.so.5</samp>&rsquo; shared objects can be
    732 installed for runtime dynamic loading using the following steps to set
    733 the &lsquo;<samp>F_LOADONLY</samp>&rsquo; flag in the shared object for <em>each</em>
    734 multilib <samp>libstdc++.a</samp> installed:
    735 </p>
    736 <p>Extract the shared objects from the currently installed
    737 <samp>libstdc++.a</samp> archive:
    738 </p><div class="smallexample">
    739 <pre class="smallexample">% ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
    740 </pre></div>
    741 
    742 <p>Enable the &lsquo;<samp>F_LOADONLY</samp>&rsquo; flag so that the shared object will be
    743 available for runtime dynamic loading, but not linking:
    744 </p><div class="smallexample">
    745 <pre class="smallexample">% strip -e libstdc++.so.4 libstdc++.so.5
    746 </pre></div>
    747 
    748 <p>Archive the runtime-only shared object in the GCC 3.4
    749 <samp>libstdc++.a</samp> archive:
    750 </p><div class="smallexample">
    751 <pre class="smallexample">% ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
    752 </pre></div>
    753 
    754 <p>Eventually, the
    755 <a href="./configure.html#WithAixSoname"><samp>--with-aix-soname=svr4</samp></a>
    756 configure option may drop the need for this procedure for libraries that
    757 support it.
    758 </p>
    759 <p>Linking executables and shared libraries may produce warnings of
    760 duplicate symbols.  The assembly files generated by GCC for AIX always
    761 have included multiple symbol definitions for certain global variable
    762 and function declarations in the original program.  The warnings should
    763 not prevent the linker from producing a correct library or runnable
    764 executable.
    765 </p>
    766 <p>AIX 4.3 utilizes a &ldquo;large format&rdquo; archive to support both 32-bit and
    767 64-bit object modules.  The routines provided in AIX 4.3.0 and AIX 4.3.1
    768 to parse archive libraries did not handle the new format correctly.
    769 These routines are used by GCC and result in error messages during
    770 linking such as &ldquo;not a COFF file&rdquo;.  The version of the routines shipped
    771 with AIX 4.3.1 should work for a 32-bit environment.  The <samp>-g</samp>
    772 option of the archive command may be used to create archives of 32-bit
    773 objects using the original &ldquo;small format&rdquo;.  A correct version of the
    774 routines is shipped with AIX 4.3.2 and above.
    775 </p>
    776 <p>Some versions of the AIX binder (linker) can fail with a relocation
    777 overflow severe error when the <samp>-bbigtoc</samp> option is used to link
    778 GCC-produced object files into an executable that overflows the TOC.  A fix
    779 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
    780 available from IBM Customer Support and from its
    781 <a href="http://techsupport.services.ibm.com/">techsupport.services.ibm.com</a>
    782 website as PTF U455193.
    783 </p>
    784 <p>The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
    785 with a segmentation fault when invoked by any version of GCC.  A fix for
    786 APAR IX87327 is available from IBM Customer Support and from its
    787 <a href="http://techsupport.services.ibm.com/">techsupport.services.ibm.com</a>
    788 website as PTF U461879.  This fix is incorporated in AIX 4.3.3 and above.
    789 </p>
    790 <p>The initial assembler shipped with AIX 4.3.0 generates incorrect object
    791 files.  A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
    792 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
    793 <a href="http://techsupport.services.ibm.com/">techsupport.services.ibm.com</a>
    794 website as PTF U453956.  This fix is incorporated in AIX 4.3.1 and above.
    795 </p>
    796 <p>AIX provides National Language Support (NLS).  Compilers and assemblers
    797 use NLS to support locale-specific representations of various data
    798 formats including floating-point numbers (e.g., &lsquo;<samp>.</samp>&rsquo;  vs &lsquo;<samp>,</samp>&rsquo; for
    799 separating decimal fractions).  There have been problems reported where
    800 GCC does not produce the same floating-point formats that the assembler
    801 expects.  If one encounters this problem, set the <code>LANG</code>
    802 environment variable to &lsquo;<samp>C</samp>&rsquo; or &lsquo;<samp>En_US</samp>&rsquo;.
    803 </p>
    804 <p>A default can be specified with the <samp>-mcpu=<var>cpu_type</var></samp>
    805 switch and using the configure option <samp>--with-cpu-<var>cpu_type</var></samp>.
    806 </p>
    807 <hr />
    808 <a name="iq2000_002dx_002delf"></a><a name="iq2000_002d_002a_002delf"></a>
    809 <h3 class="heading">iq2000-*-elf</h3>
    810 <p>Vitesse IQ2000 processors.  These are used in embedded
    811 applications.  There are no standard Unix configurations.
    812 </p>
    813 <hr />
    814 <a name="lm32_002dx_002delf"></a><a name="lm32_002d_002a_002delf"></a>
    815 <h3 class="heading">lm32-*-elf</h3>
    816 <p>Lattice Mico32 processor.
    817 This configuration is intended for embedded systems.
    818 </p>
    819 <hr />
    820 <a name="lm32_002dx_002duclinux"></a><a name="lm32_002d_002a_002duclinux"></a>
    821 <h3 class="heading">lm32-*-uclinux</h3>
    822 <p>Lattice Mico32 processor.
    823 This configuration is intended for embedded systems running uClinux.
    824 </p>
    825 <hr />
    826 <a name="m32c_002dx_002delf"></a><a name="m32c_002d_002a_002delf"></a>
    827 <h3 class="heading">m32c-*-elf</h3>
    828 <p>Renesas M32C processor.
    829 This configuration is intended for embedded systems.
    830 </p>
    831 <hr />
    832 <a name="m32r_002dx_002delf"></a><a name="m32r_002d_002a_002delf"></a>
    833 <h3 class="heading">m32r-*-elf</h3>
    834 <p>Renesas M32R processor.
    835 This configuration is intended for embedded systems.
    836 </p>
    837 <hr />
    838 <a name="m68k_002dx_002dx"></a><a name="m68k_002d_002a_002d_002a"></a>
    839 <h3 class="heading">m68k-*-*</h3>
    840 <p>By default,
    841 &lsquo;<samp>m68k-*-elf*</samp>&rsquo;, &lsquo;<samp>m68k-*-rtems</samp>&rsquo;,  &lsquo;<samp>m68k-*-uclinux</samp>&rsquo; and
    842 &lsquo;<samp>m68k-*-linux</samp>&rsquo;
    843 build libraries for both M680x0 and ColdFire processors.  If you only
    844 need the M680x0 libraries, you can omit the ColdFire ones by passing
    845 <samp>--with-arch=m68k</samp> to <code>configure</code>.  Alternatively, you
    846 can omit the M680x0 libraries by passing <samp>--with-arch=cf</samp> to
    847 <code>configure</code>.  These targets default to 5206 or 5475 code as
    848 appropriate for the target system when
    849 configured with <samp>--with-arch=cf</samp> and 68020 code otherwise.
    850 </p>
    851 <p>The &lsquo;<samp>m68k-*-netbsd</samp>&rsquo; and
    852 &lsquo;<samp>m68k-*-openbsd</samp>&rsquo; targets also support the <samp>--with-arch</samp>
    853 option.  They will generate ColdFire CFV4e code when configured with
    854 <samp>--with-arch=cf</samp> and 68020 code otherwise.
    855 </p>
    856 <p>You can override the default processors listed above by configuring
    857 with <samp>--with-cpu=<var>target</var></samp>.  This <var>target</var> can either
    858 be a <samp>-mcpu</samp> argument or one of the following values:
    859 &lsquo;<samp>m68000</samp>&rsquo;, &lsquo;<samp>m68010</samp>&rsquo;, &lsquo;<samp>m68020</samp>&rsquo;, &lsquo;<samp>m68030</samp>&rsquo;,
    860 &lsquo;<samp>m68040</samp>&rsquo;, &lsquo;<samp>m68060</samp>&rsquo;, &lsquo;<samp>m68020-40</samp>&rsquo; and &lsquo;<samp>m68020-60</samp>&rsquo;.
    861 </p>
    862 <p>GCC requires at least binutils version 2.17 on these targets.
    863 </p>
    864 <hr />
    865 <a name="m68k_002dx_002duclinux"></a><a name="m68k_002d_002a_002duclinux"></a>
    866 <h3 class="heading">m68k-*-uclinux</h3>
    867 <p>GCC 4.3 changed the uClinux configuration so that it uses the
    868 &lsquo;<samp>m68k-linux-gnu</samp>&rsquo; ABI rather than the &lsquo;<samp>m68k-elf</samp>&rsquo; ABI.
    869 It also added improved support for C++ and flat shared libraries,
    870 both of which were ABI changes.
    871 </p>
    872 <hr />
    873 <a name="mep_002dx_002delf"></a><a name="mep_002d_002a_002delf"></a>
    874 <h3 class="heading">mep-*-elf</h3>
    875 <p>Toshiba Media embedded Processor.
    876 This configuration is intended for embedded systems.
    877 </p>
    878 <hr />
    879 <a name="microblaze_002dx_002delf"></a><a name="microblaze_002d_002a_002delf"></a>
    880 <h3 class="heading">microblaze-*-elf</h3>
    881 <p>Xilinx MicroBlaze processor.
    882 This configuration is intended for embedded systems.
    883 </p>
    884 <hr />
    885 <a name="mips_002dx_002dx"></a><a name="mips_002d_002a_002d_002a"></a>
    886 <h3 class="heading">mips-*-*</h3>
    887 <p>If on a MIPS system you get an error message saying &ldquo;does not have gp
    888 sections for all it&rsquo;s [sic] sectons [sic]&rdquo;, don&rsquo;t worry about it.  This
    889 happens whenever you use GAS with the MIPS linker, but there is not
    890 really anything wrong, and it is okay to use the output file.  You can
    891 stop such warnings by installing the GNU linker.
    892 </p>
    893 <p>It would be nice to extend GAS to produce the gp tables, but they are
    894 optional, and there should not be a warning about their absence.
    895 </p>
    896 <p>The libstdc++ atomic locking routines for MIPS targets requires MIPS II
    897 and later.  A patch went in just after the GCC 3.3 release to
    898 make &lsquo;<samp>mips*-*-*</samp>&rsquo; use the generic implementation instead.  You can also
    899 configure for &lsquo;<samp>mipsel-elf</samp>&rsquo; as a workaround.  The
    900 &lsquo;<samp>mips*-*-linux*</samp>&rsquo; target continues to use the MIPS II routines.  More
    901 work on this is expected in future releases.
    902 </p>
    903 
    904 <p>The built-in <code>__sync_*</code> functions are available on MIPS II and
    905 later systems and others that support the &lsquo;<samp>ll</samp>&rsquo;, &lsquo;<samp>sc</samp>&rsquo; and
    906 &lsquo;<samp>sync</samp>&rsquo; instructions.  This can be overridden by passing
    907 <samp>--with-llsc</samp> or <samp>--without-llsc</samp> when configuring GCC.
    908 Since the Linux kernel emulates these instructions if they are
    909 missing, the default for &lsquo;<samp>mips*-*-linux*</samp>&rsquo; targets is
    910 <samp>--with-llsc</samp>.  The <samp>--with-llsc</samp> and
    911 <samp>--without-llsc</samp> configure options may be overridden at compile
    912 time by passing the <samp>-mllsc</samp> or <samp>-mno-llsc</samp> options to
    913 the compiler.
    914 </p>
    915 <p>MIPS systems check for division by zero (unless
    916 <samp>-mno-check-zero-division</samp> is passed to the compiler) by
    917 generating either a conditional trap or a break instruction.  Using
    918 trap results in smaller code, but is only supported on MIPS II and
    919 later.  Also, some versions of the Linux kernel have a bug that
    920 prevents trap from generating the proper signal (<code>SIGFPE</code>).  To enable
    921 the use of break, use the <samp>--with-divide=breaks</samp>
    922 <code>configure</code> option when configuring GCC.  The default is to
    923 use traps on systems that support them.
    924 </p>
    925 <p>The assembler from GNU binutils 2.17 and earlier has a bug in the way
    926 it sorts relocations for REL targets (o32, o64, EABI).  This can cause
    927 bad code to be generated for simple C++ programs.  Also the linker
    928 from GNU binutils versions prior to 2.17 has a bug which causes the
    929 runtime linker stubs in very large programs, like <samp>libgcj.so</samp>, to
    930 be incorrectly generated.  GNU Binutils 2.18 and later (and snapshots
    931 made after Nov. 9, 2006) should be free from both of these problems.
    932 </p>
    933 <hr />
    934 <a name="mips_002dsgi_002dirix5"></a><a name="mips_002dsgi_002dirix5-1"></a>
    935 <h3 class="heading">mips-sgi-irix5</h3>
    936 <p>Support for IRIX 5 has been removed in GCC 4.6.
    937 </p>
    938 <hr />
    939 <a name="mips_002dsgi_002dirix6"></a><a name="mips_002dsgi_002dirix6-1"></a>
    940 <h3 class="heading">mips-sgi-irix6</h3>
    941 <p>Support for IRIX 6.5 has been removed in GCC 4.8.  Support for IRIX 6
    942 releases before 6.5 has been removed in GCC 4.6, as well as support for
    943 the O32 ABI.
    944 </p>
    945 <hr />
    946 <a name="moxie_002dx_002delf"></a><a name="moxie_002d_002a_002delf"></a>
    947 <h3 class="heading">moxie-*-elf</h3>
    948 <p>The moxie processor.
    949 </p>
    950 <hr />
    951 <a name="msp430_002dx_002delf"></a><a name="msp430_002d_002a_002delf"></a>
    952 <h3 class="heading">msp430-*-elf</h3>
    953 <p>TI MSP430 processor.
    954 This configuration is intended for embedded systems.
    955 </p>
    956 <hr />
    957 <a name="nds32le_002dx_002delf"></a><a name="nds32le_002d_002a_002delf"></a>
    958 <h3 class="heading">nds32le-*-elf</h3>
    959 <p>Andes NDS32 target in little endian mode.
    960 </p>
    961 <hr />
    962 <a name="nds32be_002dx_002delf"></a><a name="nds32be_002d_002a_002delf"></a>
    963 <h3 class="heading">nds32be-*-elf</h3>
    964 <p>Andes NDS32 target in big endian mode.
    965 </p>
    966 <hr />
    967 <a name="nvptx_002dx_002dnone"></a><a name="nvptx_002d_002a_002dnone"></a>
    968 <h3 class="heading">nvptx-*-none</h3>
    969 <p>Nvidia PTX target.
    970 </p>
    971 <p>Instead of GNU binutils, you will need to install
    972 <a href="https://github.com/MentorEmbedded/nvptx-tools/">nvptx-tools</a>.
    973 Tell GCC where to find it:
    974 <samp>--with-build-time-tools=[install-nvptx-tools]/nvptx-none/bin</samp>.
    975 </p>
    976 <p>A nvptx port of newlib is available at
    977 <a href="https://github.com/MentorEmbedded/nvptx-newlib/">nvptx-newlib</a>.
    978 It can be automatically built together with GCC.  For this, add a
    979 symbolic link to nvptx-newlib&rsquo;s <samp>newlib</samp> directory to the
    980 directory containing the GCC sources.
    981 </p>
    982 <p>Use the <samp>--disable-sjlj-exceptions</samp> and
    983 <samp>--enable-newlib-io-long-long</samp> options when configuring.
    984 </p>
    985 <hr />
    986 <a name="powerpc_002dx_002dx"></a><a name="powerpc_002d_002a_002d_002a"></a>
    987 <h3 class="heading">powerpc-*-*</h3>
    988 <p>You can specify a default version for the <samp>-mcpu=<var>cpu_type</var></samp>
    989 switch by using the configure option <samp>--with-cpu-<var>cpu_type</var></samp>.
    990 </p>
    991 <p>You will need
    992 <a href="ftp://ftp.kernel.org/pub/linux/devel/binutils">binutils 2.15</a>
    993 or newer for a working GCC.
    994 </p>
    995 <hr />
    996 <a name="powerpc_002dx_002ddarwin"></a><a name="powerpc_002d_002a_002ddarwin_002a"></a>
    997 <h3 class="heading">powerpc-*-darwin*</h3>
    998 <p>PowerPC running Darwin (Mac OS X kernel).
    999 </p>
   1000 <p>Pre-installed versions of Mac OS X may not include any developer tools,
   1001 meaning that you will not be able to build GCC from source.  Tool
   1002 binaries are available at
   1003 <a href="http://opensource.apple.com/">http://opensource.apple.com/</a>.
   1004 </p>
   1005 <p>This version of GCC requires at least cctools-590.36.  The
   1006 cctools-590.36 package referenced from
   1007 <a href="http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html">http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html</a> will not work
   1008 on systems older than 10.3.9 (aka darwin7.9.0).
   1009 </p>
   1010 <hr />
   1011 <a name="powerpc_002dx_002delf"></a><a name="powerpc_002d_002a_002delf"></a>
   1012 <h3 class="heading">powerpc-*-elf</h3>
   1013 <p>PowerPC system in big endian mode, running System V.4.
   1014 </p>
   1015 <hr />
   1016 <a name="powerpc_002dx_002dlinux_002dgnu"></a><a name="powerpc_002a_002d_002a_002dlinux_002dgnu_002a"></a>
   1017 <h3 class="heading">powerpc*-*-linux-gnu*</h3>
   1018 <p>PowerPC system in big endian mode running Linux.
   1019 </p>
   1020 <hr />
   1021 <a name="powerpc_002dx_002dnetbsd"></a><a name="powerpc_002d_002a_002dnetbsd_002a"></a>
   1022 <h3 class="heading">powerpc-*-netbsd*</h3>
   1023 <p>PowerPC system in big endian mode running NetBSD.
   1024 </p>
   1025 <hr />
   1026 <a name="powerpc_002dx_002deabisim"></a><a name="powerpc_002d_002a_002deabisim"></a>
   1027 <h3 class="heading">powerpc-*-eabisim</h3>
   1028 <p>Embedded PowerPC system in big endian mode for use in running under the
   1029 PSIM simulator.
   1030 </p>
   1031 <hr />
   1032 <a name="powerpc_002dx_002deabi"></a><a name="powerpc_002d_002a_002deabi"></a>
   1033 <h3 class="heading">powerpc-*-eabi</h3>
   1034 <p>Embedded PowerPC system in big endian mode.
   1035 </p>
   1036 <hr />
   1037 <a name="powerpcle_002dx_002delf"></a><a name="powerpcle_002d_002a_002delf"></a>
   1038 <h3 class="heading">powerpcle-*-elf</h3>
   1039 <p>PowerPC system in little endian mode, running System V.4.
   1040 </p>
   1041 <hr />
   1042 <a name="powerpcle_002dx_002deabisim"></a><a name="powerpcle_002d_002a_002deabisim"></a>
   1043 <h3 class="heading">powerpcle-*-eabisim</h3>
   1044 <p>Embedded PowerPC system in little endian mode for use in running under
   1045 the PSIM simulator.
   1046 </p>
   1047 <hr />
   1048 <a name="powerpcle_002dx_002deabi"></a><a name="powerpcle_002d_002a_002deabi"></a>
   1049 <h3 class="heading">powerpcle-*-eabi</h3>
   1050 <p>Embedded PowerPC system in little endian mode.
   1051 </p>
   1052 <hr />
   1053 <a name="rl78_002dx_002delf"></a><a name="rl78_002d_002a_002delf"></a>
   1054 <h3 class="heading">rl78-*-elf</h3>
   1055 <p>The Renesas RL78 processor.
   1056 This configuration is intended for embedded systems.
   1057 </p>
   1058 <hr />
   1059 <a name="rx_002dx_002delf"></a><a name="rx_002d_002a_002delf"></a>
   1060 <h3 class="heading">rx-*-elf</h3>
   1061 <p>The Renesas RX processor.  See
   1062 <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>
   1063 for more information about this processor.
   1064 </p>
   1065 <hr />
   1066 <a name="s390_002dx_002dlinux"></a><a name="s390_002d_002a_002dlinux_002a"></a>
   1067 <h3 class="heading">s390-*-linux*</h3>
   1068 <p>S/390 system running GNU/Linux for S/390.
   1069 </p>
   1070 <hr />
   1071 <a name="s390x_002dx_002dlinux"></a><a name="s390x_002d_002a_002dlinux_002a"></a>
   1072 <h3 class="heading">s390x-*-linux*</h3>
   1073 <p>zSeries system (64-bit) running GNU/Linux for zSeries.
   1074 </p>
   1075 <hr />
   1076 <a name="s390x_002dibm_002dtpf"></a><a name="s390x_002dibm_002dtpf_002a"></a>
   1077 <h3 class="heading">s390x-ibm-tpf*</h3>
   1078 <p>zSeries system (64-bit) running TPF.  This platform is
   1079 supported as cross-compilation target only.
   1080 </p>
   1081 <hr />
   1082 <a name="x_002dx_002dsolaris2"></a><a name="g_t_002a_002d_002a_002dsolaris2_002a"></a>
   1083 <h3 class="heading">*-*-solaris2*</h3>
   1084 <p>Support for Solaris 9 has been removed in GCC 5.  Support for Solaris
   1085 8 has been removed in GCC 4.8.  Support for Solaris 7 has been removed
   1086 in GCC 4.6.
   1087 </p>
   1088 <p>Sun does not ship a C compiler with Solaris 2 before Solaris 10, though
   1089 you can download the Sun Studio compilers for free.  In Solaris 10 and
   1090 11, GCC 3.4.3 is available as <code>/usr/sfw/bin/gcc</code>.  Solaris 11
   1091 also provides GCC 4.5.2 as <code>/usr/gcc/4.5/bin/gcc</code>.  Alternatively,
   1092 you can install a pre-built GCC to bootstrap and install GCC.  See the
   1093 <a href="binaries.html">binaries page</a> for details.
   1094 </p>
   1095 <p>The Solaris 2 <code>/bin/sh</code> will often fail to configure
   1096 &lsquo;<samp>libstdc++-v3</samp>&rsquo;, &lsquo;<samp>boehm-gc</samp>&rsquo; or &lsquo;<samp>libjava</samp>&rsquo;.  We therefore
   1097 recommend using the following initial sequence of commands
   1098 </p>
   1099 <div class="smallexample">
   1100 <pre class="smallexample">% CONFIG_SHELL=/bin/ksh
   1101 % export CONFIG_SHELL
   1102 </pre></div>
   1103 
   1104 <p>and proceed as described in <a href="configure.html">the configure instructions</a>.
   1105 In addition we strongly recommend specifying an absolute path to invoke
   1106 <code><var>srcdir</var>/configure</code>.
   1107 </p>
   1108 <p>Solaris 2 comes with a number of optional OS packages.  Some of these
   1109 are needed to use GCC fully, namely <code>SUNWarc</code>,
   1110 <code>SUNWbtool</code>, <code>SUNWesu</code>, <code>SUNWhea</code>, <code>SUNWlibm</code>,
   1111 <code>SUNWsprot</code>, and <code>SUNWtoo</code>.  If you did not install all
   1112 optional packages when installing Solaris 2, you will need to verify that
   1113 the packages that GCC needs are installed.
   1114 </p>
   1115 <p>To check whether an optional package is installed, use
   1116 the <code>pkginfo</code> command.  To add an optional package, use the
   1117 <code>pkgadd</code> command.  For further details, see the Solaris 2
   1118 documentation.
   1119 </p>
   1120 <p>Trying to use the linker and other tools in
   1121 <samp>/usr/ucb</samp> to install GCC has been observed to cause trouble.
   1122 For example, the linker may hang indefinitely.  The fix is to remove
   1123 <samp>/usr/ucb</samp> from your <code>PATH</code>.
   1124 </p>
   1125 <p>The build process works more smoothly with the legacy Sun tools so, if you
   1126 have <samp>/usr/xpg4/bin</samp> in your <code>PATH</code>, we recommend that you place
   1127 <samp>/usr/bin</samp> before <samp>/usr/xpg4/bin</samp> for the duration of the build.
   1128 </p>
   1129 <p>We recommend the use of the Sun assembler or the GNU assembler, in
   1130 conjunction with the Sun linker.  The GNU <code>as</code>
   1131 versions included in Solaris 10, from GNU binutils 2.15, and Solaris 11,
   1132 from GNU binutils 2.19, are known to work.  They can be found in
   1133 <samp>/usr/sfw/bin/gas</samp>.  Current versions of GNU binutils (2.22)
   1134 are known to work as well.  Note that your mileage may vary
   1135 if you use a combination of the GNU tools and the Sun tools: while the
   1136 combination GNU <code>as</code> + Sun <code>ld</code> should reasonably work,
   1137 the reverse combination Sun <code>as</code> + GNU <code>ld</code> may fail to
   1138 build or cause memory corruption at runtime in some cases for C++ programs.
   1139 GNU <code>ld</code> usually works as well, although the version included in
   1140 Solaris 10 cannot be used due to several bugs.  Again, the current
   1141 version (2.22) is known to work, but generally lacks platform specific
   1142 features, so better stay with Sun <code>ld</code>.  To use the LTO linker
   1143 plugin (<samp>-fuse-linker-plugin</samp>) with GNU <code>ld</code>, GNU
   1144 binutils <em>must</em> be configured with <samp>--enable-largefile</samp>.
   1145 </p>
   1146 <p>To enable symbol versioning in &lsquo;<samp>libstdc++</samp>&rsquo; with the Sun linker,
   1147 you need to have any version of GNU <code>c++filt</code>, which is part of
   1148 GNU binutils.  &lsquo;<samp>libstdc++</samp>&rsquo; symbol versioning will be disabled if no
   1149 appropriate version is found.  Sun <code>c++filt</code> from the Sun Studio
   1150 compilers does <em>not</em> work.
   1151 </p>
   1152 <p>GNU <code>make</code> version 3.81 or later is required to build libjava
   1153 with the Sun linker.
   1154 </p>
   1155 <p>Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
   1156 newer: <code>g++</code> will complain that types are missing.  These headers
   1157 assume that omitting the type means <code>int</code>; this assumption worked for
   1158 C90 but is wrong for C++, and is now wrong for C99 also.
   1159 </p>
   1160 <p>Sun bug 4927647 sometimes causes random spurious testsuite failures
   1161 related to missing diagnostic output.  This bug doesn&rsquo;t affect GCC
   1162 itself, rather it is a kernel bug triggered by the <code>expect</code>
   1163 program which is used only by the GCC testsuite driver.  When the bug
   1164 causes the <code>expect</code> program to miss anticipated output, extra
   1165 testsuite failures appear.
   1166 </p>
   1167 <hr />
   1168 <a name="sparc_002dx_002dx"></a><a name="sparc_002a_002d_002a_002d_002a"></a>
   1169 <h3 class="heading">sparc*-*-*</h3>
   1170 <p>This section contains general configuration information for all
   1171 SPARC-based platforms.  In addition to reading this section, please
   1172 read all other sections that match your target.
   1173 </p>
   1174 <p>Newer versions of the GNU Multiple Precision Library (GMP), the MPFR
   1175 library and the MPC library are known to be miscompiled by earlier
   1176 versions of GCC on these platforms.  We therefore recommend the use
   1177 of the exact versions of these libraries listed as minimal versions
   1178 in <a href="prerequisites.html">the prerequisites</a>.
   1179 </p>
   1180 <hr />
   1181 <a name="sparc_002dsun_002dsolaris2"></a><a name="sparc_002dsun_002dsolaris2_002a"></a>
   1182 <h3 class="heading">sparc-sun-solaris2*</h3>
   1183 <p>When GCC is configured to use GNU binutils 2.14 or later, the binaries
   1184 produced are smaller than the ones produced using Sun&rsquo;s native tools;
   1185 this difference is quite significant for binaries containing debugging
   1186 information.
   1187 </p>
   1188 <p>Starting with Solaris 7, the operating system is capable of executing
   1189 64-bit SPARC V9 binaries.  GCC 3.1 and later properly supports
   1190 this; the <samp>-m64</samp> option enables 64-bit code generation.
   1191 However, if all you want is code tuned for the UltraSPARC CPU, you
   1192 should try the <samp>-mtune=ultrasparc</samp> option instead, which produces
   1193 code that, unlike full 64-bit code, can still run on non-UltraSPARC
   1194 machines.
   1195 </p>
   1196 <p>When configuring on a Solaris 7 or later system that is running a kernel
   1197 that supports only 32-bit binaries, one must configure with
   1198 <samp>--disable-multilib</samp>, since we will not be able to build the
   1199 64-bit target libraries.
   1200 </p>
   1201 <p>GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of
   1202 the GNU compiler (especially GCC 3.0.x versions), which lead to the
   1203 miscompilation of the stage1 compiler and the subsequent failure of the
   1204 bootstrap process.  A workaround is to use GCC 3.2.3 as an intermediary
   1205 stage, i.e. to bootstrap that compiler with the base compiler and then
   1206 use it to bootstrap the final compiler.
   1207 </p>
   1208 <p>GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE Studio 7)
   1209 and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a bootstrap
   1210 failure in form of a miscompilation of the stage1 compiler by the Sun
   1211 compiler.  This is Sun bug 4974440.  This is fixed with patch 112760-07.
   1212 </p>
   1213 <p>GCC 3.4 changed the default debugging format from Stabs to DWARF-2 for
   1214 32-bit code on Solaris 7 and later.  If you use the Sun assembler, this
   1215 change apparently runs afoul of Sun bug 4910101 (which is referenced as
   1216 an x86-only problem by Sun, probably because they do not use DWARF-2).
   1217 A symptom of the problem is that you cannot compile C++ programs like
   1218 <code>groff</code> 1.19.1 without getting messages similar to the following:
   1219 </p>
   1220 <div class="smallexample">
   1221 <pre class="smallexample">ld: warning: relocation error: R_SPARC_UA32: &hellip;
   1222   external symbolic relocation against non-allocatable section
   1223   .debug_info cannot be processed at runtime: relocation ignored.
   1224 </pre></div>
   1225 
   1226 <p>To work around this problem, compile with <samp>-gstabs+</samp> instead of
   1227 plain <samp>-g</samp>.
   1228 </p>
   1229 <p>When configuring the GNU Multiple Precision Library (GMP), the MPFR
   1230 library or the MPC library on a Solaris 7 or later system, the canonical
   1231 target triplet must be specified as the <code>build</code> parameter on the
   1232 configure line.  This target triplet can be obtained by invoking <code>./config.guess</code> in the toplevel source directory of GCC (and
   1233 not that of GMP or MPFR or MPC).  For example on a Solaris 9 system:
   1234 </p>
   1235 <div class="smallexample">
   1236 <pre class="smallexample">% ./configure --build=sparc-sun-solaris2.9 --prefix=xxx
   1237 </pre></div>
   1238 
   1239 <hr />
   1240 <a name="sparc_002dsun_002dsolaris210"></a><a name="sparc_002dsun_002dsolaris2_002e10"></a>
   1241 <h3 class="heading">sparc-sun-solaris2.10</h3>
   1242 <p>There is a bug in older versions of the Sun assembler which breaks
   1243 thread-local storage (TLS).  A typical error message is
   1244 </p>
   1245 <div class="smallexample">
   1246 <pre class="smallexample">ld: fatal: relocation error: R_SPARC_TLS_LE_HIX22: file /var/tmp//ccamPA1v.o:
   1247   symbol &lt;unknown&gt;: bad symbol type SECT: symbol type must be TLS
   1248 </pre></div>
   1249 
   1250 <p>This bug is fixed in Sun patch 118683-03 or later.
   1251 </p>
   1252 <hr />
   1253 <a name="sparc_002dx_002dlinux"></a><a name="sparc_002d_002a_002dlinux_002a"></a>
   1254 <h3 class="heading">sparc-*-linux*</h3>
   1255 
   1256 <p>GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
   1257 or newer on this platform.  All earlier binutils and glibc
   1258 releases mishandled unaligned relocations on <code>sparc-*-*</code> targets.
   1259 </p>
   1260 
   1261 <hr />
   1262 <a name="sparc64_002dx_002dsolaris2"></a><a name="sparc64_002d_002a_002dsolaris2_002a"></a>
   1263 <h3 class="heading">sparc64-*-solaris2*</h3>
   1264 <p>When configuring the GNU Multiple Precision Library (GMP), the MPFR
   1265 library or the MPC library, the canonical target triplet must be specified
   1266 as the <code>build</code> parameter on the configure line.  For example
   1267 on a Solaris 9 system:
   1268 </p>
   1269 <div class="smallexample">
   1270 <pre class="smallexample">% ./configure --build=sparc64-sun-solaris2.9 --prefix=xxx
   1271 </pre></div>
   1272 
   1273 <p>The following compiler flags must be specified in the configure
   1274 step in order to bootstrap this target with the Sun compiler:
   1275 </p>
   1276 <div class="smallexample">
   1277 <pre class="smallexample">% CC=&quot;cc -xarch=v9 -xildoff&quot; <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>]
   1278 </pre></div>
   1279 
   1280 <p><samp>-xarch=v9</samp> specifies the SPARC-V9 architecture to the Sun toolchain
   1281 and <samp>-xildoff</samp> turns off the incremental linker.
   1282 </p>
   1283 <hr />
   1284 <a name="sparcv9_002dx_002dsolaris2"></a><a name="sparcv9_002d_002a_002dsolaris2_002a"></a>
   1285 <h3 class="heading">sparcv9-*-solaris2*</h3>
   1286 <p>This is a synonym for &lsquo;<samp>sparc64-*-solaris2*</samp>&rsquo;.
   1287 </p>
   1288 <hr />
   1289 <a name="c6x_002dx_002dx"></a><a name="c6x_002d_002a_002d_002a"></a>
   1290 <h3 class="heading">c6x-*-*</h3>
   1291 <p>The C6X family of processors. This port requires binutils-2.22 or newer.
   1292 </p>
   1293 <hr />
   1294 <a name="tilegx_002d_002a_002dlinux"></a><a name="tilegx_002d_002a_002dlinux_002a"></a>
   1295 <h3 class="heading">tilegx-*-linux*</h3>
   1296 <p>The TILE-Gx processor in little endian mode, running GNU/Linux.  This
   1297 port requires binutils-2.22 or newer.
   1298 </p>
   1299 <hr />
   1300 <a name="tilegxbe_002d_002a_002dlinux"></a><a name="tilegxbe_002d_002a_002dlinux_002a"></a>
   1301 <h3 class="heading">tilegxbe-*-linux*</h3>
   1302 <p>The TILE-Gx processor in big endian mode, running GNU/Linux.  This
   1303 port requires binutils-2.23 or newer.
   1304 </p>
   1305 <hr />
   1306 <a name="tilepro_002d_002a_002dlinux"></a><a name="tilepro_002d_002a_002dlinux_002a"></a>
   1307 <h3 class="heading">tilepro-*-linux*</h3>
   1308 <p>The TILEPro processor running GNU/Linux.  This port requires
   1309 binutils-2.22 or newer.
   1310 </p>
   1311 <hr />
   1312 <a name="visium_002dx_002delf"></a><a name="visium_002d_002a_002delf"></a>
   1313 <h3 class="heading">visium-*-elf</h3>
   1314 <p>CDS VISIUMcore processor.
   1315 This configuration is intended for embedded systems.
   1316 </p>
   1317 <hr />
   1318 <a name="x_002dx_002dvxworks"></a><a name="g_t_002a_002d_002a_002dvxworks_002a"></a>
   1319 <h3 class="heading">*-*-vxworks*</h3>
   1320 <p>Support for VxWorks is in flux.  At present GCC supports <em>only</em> the
   1321 very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC.
   1322 We welcome patches for other architectures supported by VxWorks 5.5.
   1323 Support for VxWorks AE would also be welcome; we believe this is merely
   1324 a matter of writing an appropriate &ldquo;configlette&rdquo; (see below).  We are
   1325 not interested in supporting older, a.out or COFF-based, versions of
   1326 VxWorks in GCC 3.
   1327 </p>
   1328 <p>VxWorks comes with an older version of GCC installed in
   1329 <samp><var>$WIND_BASE</var>/host</samp>; we recommend you do not overwrite it.
   1330 Choose an installation <var>prefix</var> entirely outside <var>$WIND_BASE</var>.
   1331 Before running <code>configure</code>, create the directories <samp><var>prefix</var></samp>
   1332 and <samp><var>prefix</var>/bin</samp>.  Link or copy the appropriate assembler,
   1333 linker, etc. into <samp><var>prefix</var>/bin</samp>, and set your <var>PATH</var> to
   1334 include that directory while running both <code>configure</code> and
   1335 <code>make</code>.
   1336 </p>
   1337 <p>You must give <code>configure</code> the
   1338 <samp>--with-headers=<var>$WIND_BASE</var>/target/h</samp> switch so that it can
   1339 find the VxWorks system headers.  Since VxWorks is a cross compilation
   1340 target only, you must also specify <samp>--target=<var>target</var></samp>.
   1341 <code>configure</code> will attempt to create the directory
   1342 <samp><var>prefix</var>/<var>target</var>/sys-include</samp> and copy files into it;
   1343 make sure the user running <code>configure</code> has sufficient privilege
   1344 to do so.
   1345 </p>
   1346 <p>GCC&rsquo;s exception handling runtime requires a special &ldquo;configlette&rdquo;
   1347 module, <samp>contrib/gthr_supp_vxw_5x.c</samp>.  Follow the instructions in
   1348 that file to add the module to your kernel build.  (Future versions of
   1349 VxWorks will incorporate this module.)
   1350 </p>
   1351 <hr />
   1352 <a name="x86_002d64_002dx_002dx"></a><a name="x86_005f64_002d_002a_002d_002a_002c-amd64_002d_002a_002d_002a"></a>
   1353 <h3 class="heading">x86_64-*-*, amd64-*-*</h3>
   1354 <p>GCC supports the x86-64 architecture implemented by the AMD64 processor
   1355 (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD.
   1356 On GNU/Linux the default is a bi-arch compiler which is able to generate
   1357 both 64-bit x86-64 and 32-bit x86 code (via the <samp>-m32</samp> switch).
   1358 </p>
   1359 <hr />
   1360 <a name="x86_002d64_002dx_002dsolaris210"></a><a name="x86_005f64_002d_002a_002dsolaris2_002e1_005b0_002d9_005d_002a"></a>
   1361 <h3 class="heading">x86_64-*-solaris2.1[0-9]*</h3>
   1362 <p>GCC also supports the x86-64 architecture implemented by the AMD64
   1363 processor (&lsquo;<samp>amd64-*-*</samp>&rsquo; is an alias for &lsquo;<samp>x86_64-*-*</samp>&rsquo;) on
   1364 Solaris 10 or later.  Unlike other systems, without special options a
   1365 bi-arch compiler is built which generates 32-bit code by default, but
   1366 can generate 64-bit x86-64 code with the <samp>-m64</samp> switch.  Since
   1367 GCC 4.7, there is also configuration that defaults to 64-bit code, but
   1368 can generate 32-bit code with <samp>-m32</samp>.  To configure and build
   1369 this way, you have to provide all support libraries like <samp>libgmp</samp>
   1370 as 64-bit code, configure with <samp>--target=x86_64-pc-solaris2.1x</samp>
   1371 and &lsquo;<samp>CC=gcc -m64</samp>&rsquo;.
   1372 </p>
   1373 <hr />
   1374 <a name="xtensa_002dx_002delf"></a><a name="xtensa_002a_002d_002a_002delf"></a>
   1375 <h3 class="heading">xtensa*-*-elf</h3>
   1376 <p>This target is intended for embedded Xtensa systems using the
   1377 &lsquo;<samp>newlib</samp>&rsquo; C library.  It uses ELF but does not support shared
   1378 objects.  Designed-defined instructions specified via the
   1379 Tensilica Instruction Extension (TIE) language are only supported
   1380 through inline assembly.
   1381 </p>
   1382 <p>The Xtensa configuration information must be specified prior to
   1383 building GCC.  The <samp>include/xtensa-config.h</samp> header
   1384 file contains the configuration information.  If you created your
   1385 own Xtensa configuration with the Xtensa Processor Generator, the
   1386 downloaded files include a customized copy of this header file,
   1387 which you can use to replace the default header file.
   1388 </p>
   1389 <hr />
   1390 <a name="xtensa_002dx_002dlinux"></a><a name="xtensa_002a_002d_002a_002dlinux_002a"></a>
   1391 <h3 class="heading">xtensa*-*-linux*</h3>
   1392 <p>This target is for Xtensa systems running GNU/Linux.  It supports ELF
   1393 shared objects and the GNU C library (glibc).  It also generates
   1394 position-independent code (PIC) regardless of whether the
   1395 <samp>-fpic</samp> or <samp>-fPIC</samp> options are used.  In other
   1396 respects, this target is the same as the
   1397 <a href="#xtensa*-*-elf">&lsquo;<samp>xtensa*-*-elf</samp>&rsquo;</a> target.
   1398 </p>
   1399 <hr />
   1400 <a name="windows"></a><a name="Microsoft-Windows"></a>
   1401 <h3 class="heading">Microsoft Windows</h3>
   1402 
   1403 <a name="Intel-16_002dbit-versions"></a>
   1404 <h4 class="subheading">Intel 16-bit versions</h4>
   1405 <p>The 16-bit versions of Microsoft Windows, such as Windows 3.1, are not
   1406 supported.
   1407 </p>
   1408 <p>However, the 32-bit port has limited support for Microsoft
   1409 Windows 3.11 in the Win32s environment, as a target only.  See below.
   1410 </p>
   1411 <a name="Intel-32_002dbit-versions"></a>
   1412 <h4 class="subheading">Intel 32-bit versions</h4>
   1413 <p>The 32-bit versions of Windows, including Windows 95, Windows NT, Windows
   1414 XP, and Windows Vista, are supported by several different target
   1415 platforms.  These targets differ in which Windows subsystem they target
   1416 and which C libraries are used.
   1417 </p>
   1418 <ul>
   1419 <li> Cygwin <a href="#x-x-cygwin">*-*-cygwin</a>: Cygwin provides a user-space
   1420 Linux API emulation layer in the Win32 subsystem.
   1421 </li><li> Interix <a href="#x-x-interix">*-*-interix</a>: The Interix subsystem
   1422 provides native support for POSIX.
   1423 </li><li> MinGW <a href="#x-x-mingw32">*-*-mingw32</a>: MinGW is a native GCC port for
   1424 the Win32 subsystem that provides a subset of POSIX.
   1425 </li><li> MKS i386-pc-mks: NuTCracker from MKS.  See
   1426 <a href="http://www.mkssoftware.com/">http://www.mkssoftware.com/</a> for more information.
   1427 </li></ul>
   1428 
   1429 <a name="Intel-64_002dbit-versions"></a>
   1430 <h4 class="subheading">Intel 64-bit versions</h4>
   1431 <p>GCC contains support for x86-64 using the mingw-w64
   1432 runtime library, available from <a href="http://mingw-w64.sourceforge.net/">http://mingw-w64.sourceforge.net/</a>.
   1433 This library should be used with the target triple x86_64-pc-mingw32.
   1434 </p>
   1435 <p>Presently Windows for Itanium is not supported.
   1436 </p>
   1437 <a name="Windows-CE"></a>
   1438 <h4 class="subheading">Windows CE</h4>
   1439 <p>Windows CE is supported as a target only on Hitachi
   1440 SuperH (sh-wince-pe), and MIPS (mips-wince-pe).
   1441 </p>
   1442 <a name="Other-Windows-Platforms"></a>
   1443 <h4 class="subheading">Other Windows Platforms</h4>
   1444 <p>GCC no longer supports Windows NT on the Alpha or PowerPC.
   1445 </p>
   1446 <p>GCC no longer supports the Windows POSIX subsystem.  However, it does
   1447 support the Interix subsystem.  See above.
   1448 </p>
   1449 <p>Old target names including *-*-winnt and *-*-windowsnt are no longer used.
   1450 </p>
   1451 <p>PW32 (i386-pc-pw32) support was never completed, and the project seems to
   1452 be inactive.  See <a href="http://pw32.sourceforge.net/">http://pw32.sourceforge.net/</a> for more information.
   1453 </p>
   1454 <p>UWIN support has been removed due to a lack of maintenance.
   1455 </p>
   1456 <hr />
   1457 <a name="x_002dx_002dcygwin"></a><a name="g_t_002a_002d_002a_002dcygwin"></a>
   1458 <h3 class="heading">*-*-cygwin</h3>
   1459 <p>Ports of GCC are included with the
   1460 <a href="http://www.cygwin.com/">Cygwin environment</a>.
   1461 </p>
   1462 <p>GCC will build under Cygwin without modification; it does not build
   1463 with Microsoft&rsquo;s C++ compiler and there are no plans to make it do so.
   1464 </p>
   1465 <p>The Cygwin native compiler can be configured to target any 32-bit x86
   1466 cpu architecture desired; the default is i686-pc-cygwin.  It should be
   1467 used with as up-to-date a version of binutils as possible; use either
   1468 the latest official GNU binutils release in the Cygwin distribution,
   1469 or version 2.20 or above if building your own.
   1470 </p>
   1471 <hr />
   1472 <a name="x_002dx_002dinterix"></a><a name="g_t_002a_002d_002a_002dinterix"></a>
   1473 <h3 class="heading">*-*-interix</h3>
   1474 <p>The Interix target is used by OpenNT, Interix, Services For UNIX (SFU),
   1475 and Subsystem for UNIX-based Applications (SUA).  Applications compiled
   1476 with this target run in the Interix subsystem, which is separate from
   1477 the Win32 subsystem.  This target was last known to work in GCC 3.3.
   1478 </p>
   1479 <hr />
   1480 <a name="x_002dx_002dmingw32"></a><a name="g_t_002a_002d_002a_002dmingw32"></a>
   1481 <h3 class="heading">*-*-mingw32</h3>
   1482 <p>GCC will build with and support only MinGW runtime 3.12 and later.
   1483 Earlier versions of headers are incompatible with the new default semantics
   1484 of <code>extern inline</code> in <code>-std=c99</code> and <code>-std=gnu99</code> modes.
   1485 </p>
   1486 <hr />
   1487 <a name="older"></a><a name="Older-systems"></a>
   1488 <h3 class="heading">Older systems</h3>
   1489 <p>GCC contains support files for many older (1980s and early
   1490 1990s) Unix variants.  For the most part, support for these systems
   1491 has not been deliberately removed, but it has not been maintained for
   1492 several years and may suffer from bitrot.
   1493 </p>
   1494 <p>Starting with GCC 3.1, each release has a list of &ldquo;obsoleted&rdquo; systems.
   1495 Support for these systems is still present in that release, but
   1496 <code>configure</code> will fail unless the <samp>--enable-obsolete</samp>
   1497 option is given.  Unless a maintainer steps forward, support for these
   1498 systems will be removed from the next release of GCC.
   1499 </p>
   1500 <p>Support for old systems as hosts for GCC can cause problems if the
   1501 workarounds for compiler, library and operating system bugs affect the
   1502 cleanliness or maintainability of the rest of GCC.  In some cases, to
   1503 bring GCC up on such a system, if still possible with current GCC, may
   1504 require first installing an old version of GCC which did work on that
   1505 system, and using it to compile a more recent GCC, to avoid bugs in the
   1506 vendor compiler.  Old releases of GCC 1 and GCC 2 are available in the
   1507 <samp>old-releases</samp> directory on the <a href="../mirrors.html">GCC mirror
   1508 sites</a>.  Header bugs may generally be avoided using
   1509 <code>fixincludes</code>, but bugs or deficiencies in libraries and the
   1510 operating system may still cause problems.
   1511 </p>
   1512 <p>Support for older systems as targets for cross-compilation is less
   1513 problematic than support for them as hosts for GCC; if an enthusiast
   1514 wishes to make such a target work again (including resurrecting any of
   1515 the targets that never worked with GCC 2, starting from the last
   1516 version before they were removed), patches
   1517 <a href="../contribute.html">following the usual requirements</a> would be
   1518 likely to be accepted, since they should not affect the support for more
   1519 modern targets.
   1520 </p>
   1521 <p>For some systems, old versions of GNU binutils may also be useful,
   1522 and are available from <samp>pub/binutils/old-releases</samp> on
   1523 <a href="http://sourceware.org/mirrors.html">sourceware.org mirror sites</a>.
   1524 </p>
   1525 <p>Some of the information on specific systems above relates to
   1526 such older systems, but much of the information
   1527 about GCC on such systems (which may no longer be applicable to
   1528 current GCC) is to be found in the GCC texinfo manual.
   1529 </p>
   1530 <hr />
   1531 <a name="elf"></a><a name="all-ELF-targets-_0028SVR4_002c-Solaris-2_002c-etc_002e_0029"></a>
   1532 <h3 class="heading">all ELF targets (SVR4, Solaris 2, etc.)</h3>
   1533 <p>C++ support is significantly better on ELF targets if you use the
   1534 <a href="./configure.html#with-gnu-ld">GNU linker</a>; duplicate copies of
   1535 inlines, vtables and template instantiations will be discarded
   1536 automatically.
   1537 </p>
   1538 
   1539 <hr />
   1540 <p>
   1541 <p><a href="./index.html">Return to the GCC Installation page</a>
   1542 </p>
   1543 
   1544 
   1545 
   1546 
   1547 
   1548 
   1549 </body>
   1550 </html>
   1551