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