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