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