Files
RedBear-OS/local/recipes/dev/gcc16/source/INSTALL/specific.html
T
vasilito 48a924c561 recipes: regenerate Cargo.lock for the 0.3.2 fork versions
The libredox 0.1.19 / redox_syscall 0.9.1 bump left 45 recipe lockfiles
pinning libredox 0.1.18+rb0.3.1 and redox_syscall 0.9.0+rb0.3.1. The
cookbook builds with --locked, so every affected recipe died with

  error: cannot update the lock file .../Cargo.lock because --locked was
  passed to prevent this

which is what took out redox-driver-sys -- and with it every Red Bear
driver -- during the redbear-full build. Regenerating the fork lockfiles
was not enough; the recipes that consume the forks as path deps carry
their own. This is step 6 of local/docs/FORK-BUMP-PATCHING-POLICY.md
applied to the recipe layer.

Also drop the hardcoded GCC version in recipes/libs/libstdcxx-v3: the
literal include/c++/13.2.0 stopped resolving the moment the cross
toolchain moved to 16.1.0, leaving -I pointing at a directory that does
not exist. Now resolves the newest installed C++ header directory and
fails loudly if there is none. Same failure class as the hardcoded
13.2.0 in mk/prefix.mk.

Note: a few recipe-level Cargo.lock files (redox-driver-pci, cpufreqd,
redbear-acmd/-ecmd/-ftdi) sit beside a recipe.toml whose [source] is
path = "source", so they are not build inputs; redox-driver-pci's even
references a redox-driver-core/Cargo.toml that does not exist. They are
left alone rather than given meaning they do not have.

redox-driver-sys now cooks clean.
2026-08-03 14:15:38 +03:00

1164 lines
64 KiB
HTML

<!DOCTYPE html>
<html>
<!-- Created by GNU Texinfo 7.2, https://www.gnu.org/software/texinfo/ -->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<!-- Copyright © 1988-2026 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with no
Invariant Sections, the Front-Cover texts being (a) (see below), and
with the Back-Cover Texts being (b) (see below). A copy of the
license is included in the section entitled "GNU
Free Documentation License".
(a) The FSF's Front-Cover Text is:
A GNU Manual
(b) The FSF's Back-Cover Text is:
You have freedom to copy and modify this GNU Manual, like GNU
software. Copies published by the Free Software Foundation raise
funds for GNU development. -->
<title>Host/Target specific installation notes for GCC</title>
<meta name="description" content="Host/Target specific installation notes for GCC">
<meta name="keywords" content="Host/Target specific installation notes for GCC">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="makeinfo">
<meta name="viewport" content="width=device-width,initial-scale=1">
<style type="text/css">
<!--
a.copiable-link {visibility: hidden; text-decoration: none; line-height: 0em}
div.example {margin-left: 3.2em}
span:hover a.copiable-link {visibility: visible}
ul.mark-bullet {list-style-type: disc}
-->
</style>
</head>
<body lang="en">
<a class="index-entry-id" id="index-Specific"></a>
<a class="index-entry-id" id="index-Specific-installation-notes"></a>
<a class="index-entry-id" id="index-Target-specific-installation"></a>
<a class="index-entry-id" id="index-Host-specific-installation"></a>
<a class="index-entry-id" id="index-Target-specific-installation-notes"></a>
<p>Please read this document carefully <em class="emph">before</em> installing the
GNU Compiler Collection on your machine.
</p>
<p>Note that this list of install notes is <em class="emph">not</em> a list of supported
hosts or targets. Not all supported hosts and targets are listed
here, only the ones that require host-specific or target-specific
information have to.
</p>
<ul class="itemize mark-bullet">
<li><a class="uref" href="#aarch64-x-x">aarch64*-*-*</a>
</li><li><a class="uref" href="#amdgcn-x-amdhsa">amdgcn-*-amdhsa</a>
</li><li><a class="uref" href="#arc-x-elf32">arc-*-elf32</a>
</li><li><a class="uref" href="#arc-linux-uclibc">arc-linux-uclibc</a>
</li><li><a class="uref" href="#arm-x-eabi">arm-*-eabi</a>
</li><li><a class="uref" href="#avr">avr</a>
</li><li><a class="uref" href="#bfin">Blackfin</a>
</li><li><a class="uref" href="#cris">cris</a>
</li><li><a class="uref" href="#dos">DOS</a>
</li><li><a class="uref" href="#epiphany-x-elf">epiphany-*-elf</a>
</li><li><a class="uref" href="#ft32-x-elf">ft32-*-elf</a>
</li><li><a class="uref" href="#x-x-freebsd">*-*-freebsd*</a>
</li><li><a class="uref" href="#h8300-hms">h8300-hms</a>
</li><li><a class="uref" href="#hppa-x-linux">hppa-*-linux</a>
</li><li><a class="uref" href="#hppa64-hp-hpux11">hppa64-hp-hpux11*</a>
</li><li><a class="uref" href="#x-x-linux-gnu">*-*-linux-gnu</a>
</li><li><a class="uref" href="#ix86-x-linux">i?86-*-linux*</a>
</li><li><a class="uref" href="#ia64-x-linux">ia64-*-linux</a>
</li><li><a class="uref" href="#ia64-x-hpux">ia64-*-hpux*</a>
</li><li><a class="uref" href="#x-ibm-aix">*-ibm-aix*</a>
</li><li><a class="uref" href="#iq2000-x-elf">iq2000-*-elf</a>
</li><li><a class="uref" href="#loongarch">loongarch</a>
</li><li><a class="uref" href="#lm32-x-elf">lm32-*-elf</a>
</li><li><a class="uref" href="#lm32-x-uclinux">lm32-*-uclinux</a>
</li><li><a class="uref" href="#m32c-x-elf">m32c-*-elf</a>
</li><li><a class="uref" href="#m32r-x-elf">m32r-*-elf</a>
</li><li><a class="uref" href="#m68k-x-x">m68k-*-*</a>
</li><li><a class="uref" href="#m68k-x-uclinux">m68k-*-uclinux</a>
</li><li><a class="uref" href="#microblaze-x-elf">microblaze-*-elf</a>
</li><li><a class="uref" href="#mips-x-x">mips-*-*</a>
</li><li><a class="uref" href="#moxie-x-elf">moxie-*-elf</a>
</li><li><a class="uref" href="#msp430-x-elf">msp430-*-elf</a>
</li><li><a class="uref" href="#nds32le-x-elf">nds32le-*-elf</a>
</li><li><a class="uref" href="#nds32be-x-elf">nds32be-*-elf</a>
</li><li><a class="uref" href="#nvptx-x-none">nvptx-*-none</a>
</li><li><a class="uref" href="#or1k-x-elf">or1k-*-elf</a>
</li><li><a class="uref" href="#or1k-x-linux">or1k-*-linux</a>
</li><li><a class="uref" href="#powerpc-x-x">powerpc*-*-*</a>
</li><li><a class="uref" href="#powerpc-x-darwin">powerpc-*-darwin*</a>
</li><li><a class="uref" href="#powerpc-x-elf">powerpc-*-elf</a>
</li><li><a class="uref" href="#powerpc-x-linux-gnu">powerpc*-*-linux-gnu*</a>
</li><li><a class="uref" href="#powerpc-x-netbsd">powerpc-*-netbsd*</a>
</li><li><a class="uref" href="#powerpc-x-eabisim">powerpc-*-eabisim</a>
</li><li><a class="uref" href="#powerpc-x-eabi">powerpc-*-eabi</a>
</li><li><a class="uref" href="#powerpcle-x-elf">powerpcle-*-elf</a>
</li><li><a class="uref" href="#powerpcle-x-eabisim">powerpcle-*-eabisim</a>
</li><li><a class="uref" href="#powerpcle-x-eabi">powerpcle-*-eabi</a>
</li><li><a class="uref" href="#riscv32-x-elf">riscv32-*-elf</a>
</li><li><a class="uref" href="#riscv32-x-linux">riscv32-*-linux</a>
</li><li><a class="uref" href="#riscv64-x-elf">riscv64-*-elf</a>
</li><li><a class="uref" href="#riscv64-x-linux">riscv64-*-linux</a>
</li><li><a class="uref" href="#rl78-x-elf">rl78-*-elf</a>
</li><li><a class="uref" href="#rx-x-elf">rx-*-elf</a>
</li><li><a class="uref" href="#s390-x-linux">s390-*-linux*</a>
</li><li><a class="uref" href="#s390x-x-linux">s390x-*-linux*</a>
</li><li><a class="uref" href="#s390x-ibm-tpf">s390x-ibm-tpf*</a>
</li><li><a class="uref" href="#x-x-solaris2">*-*-solaris2*</a>
</li><li><a class="uref" href="#sparc-x-x">sparc*-*-*</a>
</li><li><a class="uref" href="#sparc-x-linux">sparc-*-linux*</a>
</li><li><a class="uref" href="#c6x-x-x">c6x-*-*</a>
</li><li><a class="uref" href="#visium-x-elf">visium-*-elf</a>
</li><li><a class="uref" href="#x-x-vxworks">*-*-vxworks*</a>
</li><li><a class="uref" href="#x86-64-x-x">x86_64-*-*, amd64-*-*</a>
</li><li><a class="uref" href="#xtensa-x-elf">xtensa*-*-elf</a>
</li><li><a class="uref" href="#xtensa-x-linux">xtensa*-*-linux*</a>
</li><li><a class="uref" href="#windows">Microsoft Windows</a>
</li><li><a class="uref" href="#x-x-cygwin">*-*-cygwin</a>
</li><li><a class="uref" href="#x-x-mingw32">*-*-mingw32</a>
</li><li><a class="uref" href="#os2">OS/2</a>
</li><li><a class="uref" href="#older">Older systems</a>
</li></ul>
<ul class="itemize mark-bullet">
<li><a class="uref" href="#elf">all ELF targets</a> (SVR4, Solaris, etc.)
</li></ul>
<!-- -------- host/target specific issues start here ---------------- -->
<hr />
<a class="anchor" id="aarch64-x-x"></a><h3 class="heading" id="aarch64*-*-*"><span>aarch64*-*-*<a class="copiable-link" href="#aarch64*-*-*"> &para;</a></span></h3>
<p>To enable a workaround for the Cortex-A53 erratum number 835769 by default
(for all CPUs regardless of -mcpu option given) at configure time use the
<samp class="option">--enable-fix-cortex-a53-835769</samp> option. This will enable the fix by
default and can be explicitly disabled during compilation by passing the
<samp class="option">-mno-fix-cortex-a53-835769</samp> option. Conversely,
<samp class="option">--disable-fix-cortex-a53-835769</samp> will disable the workaround by
default. The workaround is disabled by default if neither of
<samp class="option">--enable-fix-cortex-a53-835769</samp> or
<samp class="option">--disable-fix-cortex-a53-835769</samp> is given at configure time.
</p>
<p>To enable a workaround for the Cortex-A53 erratum number 843419 by default
(for all CPUs regardless of -mcpu option given) at configure time use the
<samp class="option">--enable-fix-cortex-a53-843419</samp> option. This workaround is applied at
link time. Enabling the workaround will cause GCC to pass the relevant option
to the linker. It can be explicitly disabled during compilation by passing the
<samp class="option">-mno-fix-cortex-a53-843419</samp> option. Conversely,
<samp class="option">--disable-fix-cortex-a53-843419</samp> will disable the workaround by default.
The workaround is disabled by default if neither of
<samp class="option">--enable-fix-cortex-a53-843419</samp> or
<samp class="option">--disable-fix-cortex-a53-843419</samp> is given at configure time.
</p>
<p>To enable Branch Target Identification Mechanism and Return Address Signing by
default at configure time use the <samp class="option">--enable-standard-branch-protection</samp>
option. This is equivalent to having <samp class="option">-mbranch-protection=standard</samp>
during compilation. This can be explicitly disabled during compilation by
passing the <samp class="option">-mbranch-protection=none</samp> option which turns off all
types of branch protections. Conversely,
<samp class="option">--disable-standard-branch-protection</samp> will disable both the
protections by default. This mechanism is turned off by default if neither
of the options are given at configure time.
</p>
<hr />
<a class="anchor" id="amdgcn-x-amdhsa"></a><h3 class="heading" id="amdgcn-*-amdhsa"><span>amdgcn-*-amdhsa<a class="copiable-link" href="#amdgcn-*-amdhsa"> &para;</a></span></h3>
<p>AMD GCN GPU target.
</p>
<p>Instead of GNU Binutils, you need to install LLVM and copy
<samp class="file">bin/llvm-mc</samp> to <samp class="file">amdgcn-amdhsa/bin/as</samp>,
<samp class="file">bin/lld</samp> to <samp class="file">amdgcn-amdhsa/bin/ld</samp>,
<samp class="file">bin/llvm-objdump</samp> to <samp class="file">amdgcn-amdhsa/bin/objdump</samp>,
<samp class="file">bin/llvm-nm</samp> to <samp class="file">amdgcn-amdhsa/bin/nm</samp>, and
<samp class="file">bin/llvm-ar</samp> to both <samp class="file">bin/amdgcn-amdhsa-ar</samp> and
<samp class="file">bin/amdgcn-amdhsa-ranlib</samp>. The LLVM version is required for the
assembler (llvm-mc) and linker (lld); however, for the others, the respective
GNU Binutils counterpart can be used instead. While all mentioned programs are
required when building GCC, the installed GCC compiler only needs the assembler
and linker; <code class="code">nm</code>, <code class="code">ar</code>, and <code class="code">ranlib</code> are required when installing
<code class="code">gcc-nm</code>, <code class="code">gcc-ar</code>, and <code class="code">gcc-ranlib</code>.
</p>
<p>The required version of LLVM depends on the devices that you want to support.
As the list of ISAs is long, GCC by default only builds a subset of the
supported ISAs as multilib; use <code class="code">--with-multilib-list=</code> to tailor the built
multilibs. Note that mixing ISAs in the same binary is not supported and gives
a linker error.
</p>
<p>By default, multilib support is built for <code class="code">gfx908</code>, <code class="code">gfx90a</code>,
<code class="code">gfx9-generic</code>, <code class="code">gfx9-4-generic</code>, <code class="code">gfx10-3-generic</code>, and
<code class="code">gfx11-generic</code>, which covers all supported archs. The default multilib
configuration requires LLVM 20 or newer. LLVM 13.0.1 or LLVM 14 can be used by
specifying a <code class="code">--with-multilib-list=</code> that only lists GFX9 or GFX10-3
devices, while LLVM 15 is required for GFX 11 device and <code class="code">gfx1036</code>.
At least LLVM 16 is required for <code class="code">gfx1150</code> and <code class="code">gfx1151</code>,
LLVM 18 for <code class="code">gfx942</code>, LLVM 19 for the generic <code class="code">gfx9-generic</code>,
<code class="code">gfx10-3-generic</code>, and <code class="code">gfx11-generic</code> targets and for <code class="code">gfx1152</code>,
while LLVM 20 is required for <code class="code">gfx950</code>, <code class="code">gfx1153</code>, and
<code class="code">gfx9-4-generic</code>.
</p>
<p>The supported ISA architectures are listed in the GCC manual. The generic
ISA targets <code class="code">gfx9-generic</code>, <code class="code">gfx10-3-generic</code>, and
<code class="code">gfx11-generic</code> reduce the number of required multilibs but note
that <code class="code">gfx9-generic</code> does not include <code class="code">gfx908</code> or <code class="code">gfx90a</code>,
that linking specific ISA code with generic code is currently not supported,
and that only ROCm 6.4.0 or newer is able to execute generic code.
</p>
<p>Use Newlib (4.6.0 or newer).
</p>
<p>To run the binaries, install the HSA Runtime from the
<a class="uref" href="https://rocm.docs.amd.com/">ROCm Platform</a>, and use
<samp class="file">libexec/gcc/amdhsa-amdhsa/<var class="var">version</var>/gcn-run</samp> to launch them
on the GPU.
</p>
<hr />
<a class="anchor" id="arc-x-elf32"></a><h3 class="heading" id="arc-*-elf32"><span>arc-*-elf32<a class="copiable-link" href="#arc-*-elf32"> &para;</a></span></h3>
<p>Use &lsquo;<samp class="samp">configure --target=arc-elf32 --with-cpu=<var class="var">cpu</var> --enable-languages=&quot;c,c++&quot;</samp>&rsquo;
to configure GCC, with <var class="var">cpu</var> being one of &lsquo;<samp class="samp">arc600</samp>&rsquo;, &lsquo;<samp class="samp">arc601</samp>&rsquo;,
or &lsquo;<samp class="samp">arc700</samp>&rsquo;.
</p>
<hr />
<a class="anchor" id="arc-linux-uclibc"></a><h3 class="heading" id="arc-linux-uclibc-1"><span>arc-linux-uclibc<a class="copiable-link" href="#arc-linux-uclibc-1"> &para;</a></span></h3>
<p>Use &lsquo;<samp class="samp">configure --target=arc-linux-uclibc --with-cpu=arc700 --enable-languages=&quot;c,c++&quot;</samp>&rsquo; to configure GCC.
</p>
<hr />
<a class="anchor" id="arm-x-eabi"></a><h3 class="heading" id="arm-*-eabi"><span>arm-*-eabi<a class="copiable-link" href="#arm-*-eabi"> &para;</a></span></h3>
<p>ARM-family processors.
</p>
<p>Building the Ada frontend commonly fails (an infinite loop executing
<code class="code">xsinfo</code>) if the host compiler is GNAT 4.8. Host compilers built from the
GNAT 4.6, 4.9 or 5 release branches are known to succeed.
</p>
<hr />
<a class="anchor" id="avr"></a><h3 class="heading" id="avr-1"><span>avr<a class="copiable-link" href="#avr-1"> &para;</a></span></h3>
<p>AVR 8-bit microcontrollers. These are used in embedded
applications. There are no standard Unix configurations.
See <a class="uref" href="https://gcc.gnu.org/onlinedocs/gcc/AVR-Options.html">AVR Options</a>
in the main manual
for the list of supported MCU types.
</p>
<p>Use &lsquo;<samp class="samp">configure --target=avr --enable-languages=&quot;c,c++&quot;</samp>&rsquo; to configure GCC.
</p>
<p>Further installation notes and other useful information about AVR tools
can also be obtained from:
</p>
<ul class="itemize mark-bullet">
<li><a class="uref" href="https://avrdudes.github.io/avr-libc/avr-libc-user-manual/install_tools.html">AVR-LibC: Building and Installing the GNU Tool Chain</a>
</li><li><a class="uref" href="https://github.com/sprintersb/atest?tab=readme-ov-file#running-the-avr-gcc-testsuite-using-the-avrtest-simulator">AVRtest: Running the avr-gcc Testsuite</a>
</li></ul>
<hr />
<a class="anchor" id="bfin"></a><h3 class="heading" id="Blackfin"><span>Blackfin<a class="copiable-link" href="#Blackfin"> &para;</a></span></h3>
<p>The Blackfin processor, an Analog Devices DSP.
See &ldquo;Blackfin Options&rdquo; in the main manual
</p>
<p>More information, and a version of binutils with support for this processor,
are available at <a class="uref" href="https://sourceforge.net/projects/adi-toolchain/">https://sourceforge.net/projects/adi-toolchain/</a>.
</p>
<hr />
<a class="anchor" id="cris"></a><h3 class="heading" id="CRIS"><span>CRIS<a class="copiable-link" href="#CRIS"> &para;</a></span></h3>
<p>CRIS is a CPU architecture in Axis Communications systems-on-a-chip, for
example the ETRAX series. These are used in embedded applications.
</p>
<p>See &ldquo;CRIS Options&rdquo; in the main manual
for a list of CRIS-specific options.
</p>
<p>Use &lsquo;<samp class="samp">configure --target=cris-elf</samp>&rsquo; to configure GCC&nbsp;for building
a cross-compiler for CRIS.
<hr />
<a class="anchor" id="dos"></a></p><h3 class="heading" id="DOS"><span>DOS<a class="copiable-link" href="#DOS"> &para;</a></span></h3>
<p>Please have a look at the <a class="uref" href="binaries.html">binaries page</a>.
</p>
<p>You cannot install GCC by itself on MSDOS; it will not compile under
any MSDOS compiler except itself. You need to get the complete
compilation package DJGPP, which includes binaries as well as sources,
and includes all the necessary compilation tools and libraries.
</p>
<hr />
<a class="anchor" id="epiphany-x-elf"></a><h3 class="heading" id="epiphany-*-elf"><span>epiphany-*-elf<a class="copiable-link" href="#epiphany-*-elf"> &para;</a></span></h3>
<p>Adapteva Epiphany.
This configuration is intended for embedded systems.
</p>
<hr />
<a class="anchor" id="x-x-freebsd"></a><h3 class="heading" id="g_t*-*-freebsd*"><span>*-*-freebsd*<a class="copiable-link" href="#g_t*-*-freebsd*"> &para;</a></span></h3>
<p>FreeBSD using the ELF file format with DWARF 2 debugging.
</p>
<p>We recommend bootstrapping against the latest GNU Binutils or the
version found in the <samp class="file">devel/binutils</samp> port. This also has been
known to enable additional features and improve overall testsuite
results.
</p>
<p>Ada and D (or rather their respective libraries) are broken on
FreeBSD/i386. This also affects building 32-bit libraries on
FreeBSD/amd64, so configure with <samp class="option">--disable-multilib</samp>
there in case you are building one of these front ends.
</p>
<p>Go (or rather libgo) is generally broken on FreeBSD.
</p>
<hr />
<a class="anchor" id="ft32-x-elf"></a><h3 class="heading" id="ft32-*-elf"><span>ft32-*-elf<a class="copiable-link" href="#ft32-*-elf"> &para;</a></span></h3>
<p>The FT32 processor.
This configuration is intended for embedded systems.
</p>
<hr />
<a class="anchor" id="h8300-hms"></a><h3 class="heading" id="h8300-hms-1"><span>h8300-hms<a class="copiable-link" href="#h8300-hms-1"> &para;</a></span></h3>
<p>Renesas H8/300 series of processors.
</p>
<hr />
<a class="anchor" id="hppa64-hp-hpux11"></a><h3 class="heading" id="hppa64-hp-hpux11*"><span>hppa64-hp-hpux11*<a class="copiable-link" href="#hppa64-hp-hpux11*"> &para;</a></span></h3>
<p>Only the 64-bit &lsquo;<samp class="samp">hppa</samp>&rsquo; target is supported on HP-UX. Support
for 32-bit &lsquo;<samp class="samp">hppa</samp>&rsquo; was discontinued in GCC 13.
</p>
<p>We require using gas on all hppa platforms.
</p>
<p>It may be helpful to configure GCC with the
<a class="uref" href="./configure.html#with-gnu-as"><samp class="option">--with-gnu-as</samp></a> and
<samp class="option">--with-as=&hellip;</samp> options to ensure that GCC can find GAS.
</p>
<p>Only the HP linker is supported. Thus, it is best to explicitly
configure the target with the <samp class="option">--with-ld=&hellip;</samp> option.
</p>
<p>The DCE thread library is not supported, so <samp class="option">--enable-threads=dce</samp>
does not work.
</p>
<p>Currently, there are no precompiled binaries for 64-bit HP-UX.
</p>
<p>Binutils and other required tools can be built using the HP tools.
Then, the GCC distribution can be built. This is challenging due
to the many dependencies.
</p>
<hr />
<a class="anchor" id="x-x-linux-gnu"></a><h3 class="heading" id="g_t*-*-linux-gnu"><span>*-*-linux-gnu<a class="copiable-link" href="#g_t*-*-linux-gnu"> &para;</a></span></h3>
<p>Versions of libstdc++-v3 starting with 3.2.1 require bug fixes present
in glibc 2.2.5 and later. More information is available in the
libstdc++-v3 documentation.
</p>
<hr />
<a class="anchor" id="ix86-x-linux"></a><h3 class="heading" id="i_003f86-*-linux*"><span>i?86-*-linux*<a class="copiable-link" href="#i_003f86-*-linux*"> &para;</a></span></h3>
<p>If you receive Signal 11 errors when building on GNU/Linux, then it is
possible you have a hardware problem. Further information on this can be
found on <a class="uref" href="https://www.bitwizard.nl/sig11/">www.bitwizard.nl</a>.
</p>
<hr />
<a class="anchor" id="ia64-x-linux"></a><h3 class="heading" id="ia64-*-linux"><span>ia64-*-linux<a class="copiable-link" href="#ia64-*-linux"> &para;</a></span></h3>
<p>IA-64 processor (also known as IPF, or Itanium Processor Family)
running GNU/Linux.
</p>
<p>If you are using the installed system libunwind library with
<samp class="option">--with-system-libunwind</samp>, then you must use libunwind 0.98 or
later.
</p>
<hr />
<a class="anchor" id="ia64-x-hpux"></a><h3 class="heading" id="ia64-*-hpux*"><span>ia64-*-hpux*<a class="copiable-link" href="#ia64-*-hpux*"> &para;</a></span></h3>
<p>Building GCC on this target requires the GNU Assembler. The bundled HP
assembler will not work. To prevent GCC from using the wrong assembler,
the option <samp class="option">--with-gnu-as</samp> may be necessary.
</p>
<hr />
<!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
<a class="anchor" id="x-ibm-aix"></a><h3 class="heading" id="g_t*-ibm-aix*"><span>*-ibm-aix*<a class="copiable-link" href="#g_t*-ibm-aix*"> &para;</a></span></h3>
<p>Support for AIX version 3 and older was discontinued in GCC 3.4.
Support for AIX version 4.2 and older was discontinued in GCC 4.5.
</p>
<p>&ldquo;out of memory&rdquo; bootstrap failures may indicate a problem with
process resource limits (ulimit). Hard limits are configured in the
<samp class="file">/etc/security/limits</samp> system configuration file.
</p>
<p>GCC 4.9 and above require a C++ compiler for bootstrap. IBM VAC++ / xlC
cannot bootstrap GCC. xlc can bootstrap an older version of GCC and
G++ can bootstrap recent releases of GCC.
</p>
<p>GCC can bootstrap with recent versions of IBM XLC, but bootstrapping
with an earlier release of GCC is recommended. Bootstrapping with XLC
requires a larger data segment, which can be enabled through the
<var class="var">LDR_CNTRL</var> environment variable, e.g.,
</p>
<div class="example smallexample">
<pre class="example-preformatted">% LDR_CNTRL=MAXDATA=0x50000000
% export LDR_CNTRL
</pre></div>
<p>One can start with a pre-compiled version of GCC to build from
sources. One may delete GCC&rsquo;s &ldquo;fixed&rdquo; header files when starting
with a version of GCC built for an earlier release of AIX.
</p>
<p>To speed up the configuration phases of bootstrapping and installing GCC,
one may use GNU Bash instead of AIX <code class="command">/bin/sh</code>, e.g.,
</p>
<div class="example smallexample">
<pre class="example-preformatted">% CONFIG_SHELL=/opt/freeware/bin/bash
% export CONFIG_SHELL
</pre></div>
<p>and then proceed as described in <a class="uref" href="build.html">the build
instructions</a>, where we strongly recommend specifying an absolute path
to invoke <var class="var">srcdir</var>/configure.
</p>
<p>Because GCC on AIX is built as a 32-bit executable by default,
(although it can generate 64-bit programs) the GMP and MPFR libraries
required by gfortran must be 32-bit libraries. Building GMP and MPFR
as static archive libraries works better than shared libraries.
</p>
<p>Errors involving <code class="code">alloca</code> when building GCC generally are due
to an incorrect definition of <code class="code">CC</code> in the Makefile or mixing files
compiled with the native C compiler and GCC. During the stage1 phase of
the build, the native AIX compiler <strong class="strong">must</strong> be invoked as <code class="command">cc</code>
(not <code class="command">xlc</code>). Once <code class="command">configure</code> has been informed of
<code class="command">xlc</code>, one needs to use &lsquo;<samp class="samp">make distclean</samp>&rsquo; to remove the
configure cache files and ensure that <code class="env">CC</code> environment variable
does not provide a definition that will confuse <code class="command">configure</code>.
If this error occurs during stage2 or later, then the problem most likely
is the version of Make (see above).
</p>
<p>The native <code class="command">as</code> and <code class="command">ld</code> are recommended for
bootstrapping on AIX. The GNU Assembler, GNU Linker, and GNU
Binutils version 2.20 is the minimum level that supports bootstrap on
AIX 5. The GNU Assembler has not been updated to support AIX 6&nbsp;or
AIX 7. The native AIX tools do interoperate with GCC.
</p>
<p>AIX 7.1 added partial support for DWARF debugging, but full support
requires AIX 7.1 TL03 SP7 that supports additional DWARF sections and
fixes a bug in the assembler. AIX 7.1 TL03 SP5 distributed a version
of libm.a missing important symbols; a fix for IV77796 will be
included in SP6.
</p>
<p>AIX 5.3 TL10, AIX 6.1 TL05 and AIX 7.1 TL00 introduced an AIX
assembler change that sometimes produces corrupt assembly files
causing AIX linker errors. The bug breaks GCC bootstrap on AIX and
can cause compilation failures with existing GCC installations. An
AIX iFix for AIX 5.3 is available (APAR IZ98385 for AIX 5.3 TL10, APAR
IZ98477 for AIX 5.3 TL11 and IZ98134 for AIX 5.3 TL12). AIX 5.3 TL11 SP8,
AIX 5.3 TL12 SP5, AIX 6.1 TL04 SP11, AIX 6.1 TL05 SP7, AIX 6.1 TL06 SP6,
AIX 6.1 TL07 and AIX 7.1 TL01 should include the fix.
</p>
<p>Building <samp class="file">libstdc++.a</samp> requires a fix for an AIX Assembler bug
APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a
fix for another AIX Assembler bug and a co-dependent AIX Archiver fix
referenced as APAR IY53606 (AIX 5.2) or as APAR IY54774 (AIX 5.1)
</p>
<a class="anchor" id="TransferAixShobj"></a><p>&lsquo;<samp class="samp">libstdc++</samp>&rsquo; in GCC 3.4 increments the major version number of the
shared object and GCC installation places the <samp class="file">libstdc++.a</samp>
shared library in a common location which will overwrite the and GCC
3.3 version of the shared library. Applications either need to be
re-linked against the new shared library or the GCC 3.1 and GCC 3.3
versions of the &lsquo;<samp class="samp">libstdc++</samp>&rsquo; shared object needs to be available
to the AIX runtime loader. The GCC 3.1 &lsquo;<samp class="samp">libstdc++.so.4</samp>&rsquo;, if
present, and GCC 3.3 &lsquo;<samp class="samp">libstdc++.so.5</samp>&rsquo; shared objects can be
installed for runtime dynamic loading using the following steps to set
the &lsquo;<samp class="samp">F_LOADONLY</samp>&rsquo; flag in the shared object for <em class="emph">each</em>
multilib <samp class="file">libstdc++.a</samp> installed:
</p>
<p>Extract the shared objects from the currently installed
<samp class="file">libstdc++.a</samp> archive:
</p><div class="example smallexample">
<pre class="example-preformatted">% ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
</pre></div>
<p>Enable the &lsquo;<samp class="samp">F_LOADONLY</samp>&rsquo; flag so that the shared object will be
available for runtime dynamic loading, but not linking:
</p><div class="example smallexample">
<pre class="example-preformatted">% strip -e libstdc++.so.4 libstdc++.so.5
</pre></div>
<p>Archive the runtime-only shared object in the GCC 3.4
<samp class="file">libstdc++.a</samp> archive:
</p><div class="example smallexample">
<pre class="example-preformatted">% ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
</pre></div>
<p>Eventually, the
<a class="uref" href="./configure.html#WithAixSoname"><samp class="option">--with-aix-soname=svr4</samp></a>
configure option may drop the need for this procedure for libraries that
support it.
</p>
<p>Linking executables and shared libraries may produce warnings of
duplicate symbols. The assembly files generated by GCC for AIX always
have included multiple symbol definitions for certain global variable
and function declarations in the original program. The warnings should
not prevent the linker from producing a correct library or runnable
executable.
</p>
<p>AIX 4.3 utilizes a &ldquo;large format&rdquo; archive to support both 32-bit and
64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
to parse archive libraries did not handle the new format correctly.
These routines are used by GCC and result in error messages during
linking such as &ldquo;not a COFF file&rdquo;. The version of the routines shipped
with AIX 4.3.1 should work for a 32-bit environment. The <samp class="option">-g</samp>
option of the archive command may be used to create archives of 32-bit
objects using the original &ldquo;small format&rdquo;. A correct version of the
routines is shipped with AIX 4.3.2 and above.
</p>
<p>Some versions of the AIX binder (linker) can fail with a relocation
overflow severe error when the <samp class="option">-bbigtoc</samp> option is used to link
GCC-produced object files into an executable that overflows the TOC. A fix
for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
available as PTF U455193.
</p>
<p>The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
with a segmentation fault when invoked by any version of GCC. A fix for
APAR IX87327 is available as PTF U461879. This fix is incorporated in
AIX 4.3.3 and above.
</p>
<p>The initial assembler shipped with AIX 4.3.0 generates incorrect object
files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
TO ASSEMBLE/BIND) is available as PTF U453956. This fix is incorporated in
AIX 4.3.1 and above.
</p>
<p>AIX provides National Language Support (NLS). Compilers and assemblers
use NLS to support locale-specific representations of various data
formats including floating-point numbers (e.g., &lsquo;<samp class="samp">.</samp>&rsquo; vs &lsquo;<samp class="samp">,</samp>&rsquo; for
separating decimal fractions). There have been problems reported where
GCC does not produce the same floating-point formats that the assembler
expects. If one encounters this problem, set the <code class="env">LANG</code>
environment variable to &lsquo;<samp class="samp">C</samp>&rsquo; or &lsquo;<samp class="samp">En_US</samp>&rsquo;.
</p>
<p>A default can be specified with the <samp class="option">-mcpu=<var class="var">cpu_type</var></samp>
switch and using the configure option <samp class="option">--with-cpu-<var class="var">cpu_type</var></samp>.
</p>
<hr />
<a class="anchor" id="iq2000-x-elf"></a><h3 class="heading" id="iq2000-*-elf"><span>iq2000-*-elf<a class="copiable-link" href="#iq2000-*-elf"> &para;</a></span></h3>
<p>Vitesse IQ2000 processors. These are used in embedded
applications. There are no standard Unix configurations.
</p>
<hr />
<a class="anchor" id="lm32-x-elf"></a><h3 class="heading" id="lm32-*-elf"><span>lm32-*-elf<a class="copiable-link" href="#lm32-*-elf"> &para;</a></span></h3>
<p>Lattice Mico32 processor.
This configuration is intended for embedded systems.
</p>
<hr />
<a class="anchor" id="lm32-x-uclinux"></a><h3 class="heading" id="lm32-*-uclinux"><span>lm32-*-uclinux<a class="copiable-link" href="#lm32-*-uclinux"> &para;</a></span></h3>
<p>Lattice Mico32 processor.
This configuration is intended for embedded systems running uClinux.
</p>
<hr />
<a class="anchor" id="loongarch"></a><h3 class="heading" id="LoongArch"><span>LoongArch<a class="copiable-link" href="#LoongArch"> &para;</a></span></h3>
<p>LoongArch processor.
The following LoongArch targets are available:
</p><dl class="table">
<dt><code class="code">loongarch64-linux-gnu*</code></dt>
<dd><p>LoongArch processor running GNU/Linux. This target triplet may be coupled
with a small set of possible suffixes to identify their default ABI type:
</p><dl class="table">
<dt><code class="code">f64</code></dt>
<dd><p>Uses <code class="code">lp64d/base</code> ABI by default.
</p></dd>
<dt><code class="code">f32</code></dt>
<dd><p>Uses <code class="code">lp64f/base</code> ABI by default.
</p></dd>
<dt><code class="code">sf</code></dt>
<dd><p>Uses <code class="code">lp64s/base</code> ABI by default.
</p></dd>
</dl>
</dd>
<dt><code class="code">loongarch64-linux-gnu</code></dt>
<dd><p>Same as <code class="code">loongarch64-linux-gnuf64</code> for legacy support.
</p></dd>
</dl>
<p>More information about LoongArch can be found at
<a class="uref" href="https://github.com/loongson/LoongArch-Documentation">https://github.com/loongson/LoongArch-Documentation</a>.
</p>
<hr />
<a class="anchor" id="m32c-x-elf"></a><h3 class="heading" id="m32c-*-elf"><span>m32c-*-elf<a class="copiable-link" href="#m32c-*-elf"> &para;</a></span></h3>
<p>Renesas M32C processor.
This configuration is intended for embedded systems.
</p>
<hr />
<a class="anchor" id="m32r-x-elf"></a><h3 class="heading" id="m32r-*-elf"><span>m32r-*-elf<a class="copiable-link" href="#m32r-*-elf"> &para;</a></span></h3>
<p>Renesas M32R processor.
This configuration is intended for embedded systems.
</p>
<hr />
<a class="anchor" id="m68k-x-x"></a><h3 class="heading" id="m68k-*-*"><span>m68k-*-*<a class="copiable-link" href="#m68k-*-*"> &para;</a></span></h3>
<p>By default,
&lsquo;<samp class="samp">m68k-*-elf*</samp>&rsquo;, &lsquo;<samp class="samp">m68k-*-rtems</samp>&rsquo;, &lsquo;<samp class="samp">m68k-*-uclinux</samp>&rsquo; and
&lsquo;<samp class="samp">m68k-*-linux</samp>&rsquo;
build libraries for both M680x0 and ColdFire processors. If you only
need the M680x0 libraries, you can omit the ColdFire ones by passing
<samp class="option">--with-arch=m68k</samp> to <code class="command">configure</code>. Alternatively, you
can omit the M680x0 libraries by passing <samp class="option">--with-arch=cf</samp> to
<code class="command">configure</code>. These targets default to 5206 or 5475 code as
appropriate for the target system when
configured with <samp class="option">--with-arch=cf</samp> and 68020 code otherwise.
</p>
<p>The &lsquo;<samp class="samp">m68k-*-netbsd</samp>&rsquo; and
&lsquo;<samp class="samp">m68k-*-openbsd</samp>&rsquo; targets also support the <samp class="option">--with-arch</samp>
option. They will generate ColdFire CFV4e code when configured with
<samp class="option">--with-arch=cf</samp> and 68020 code otherwise.
</p>
<p>You can override the default processors listed above by configuring
with <samp class="option">--with-cpu=<var class="var">target</var></samp>. This <var class="var">target</var> can either
be a <samp class="option">-mcpu</samp> argument or one of the following values:
&lsquo;<samp class="samp">m68000</samp>&rsquo;, &lsquo;<samp class="samp">m68010</samp>&rsquo;, &lsquo;<samp class="samp">m68020</samp>&rsquo;, &lsquo;<samp class="samp">m68030</samp>&rsquo;,
&lsquo;<samp class="samp">m68040</samp>&rsquo;, &lsquo;<samp class="samp">m68060</samp>&rsquo;, &lsquo;<samp class="samp">m68020-40</samp>&rsquo; and &lsquo;<samp class="samp">m68020-60</samp>&rsquo;.
</p>
<p>GCC requires at least binutils version 2.17 on these targets.
</p>
<hr />
<a class="anchor" id="m68k-x-uclinux"></a><h3 class="heading" id="m68k-*-uclinux"><span>m68k-*-uclinux<a class="copiable-link" href="#m68k-*-uclinux"> &para;</a></span></h3>
<p>GCC 4.3 changed the uClinux configuration so that it uses the
&lsquo;<samp class="samp">m68k-linux-gnu</samp>&rsquo; ABI rather than the &lsquo;<samp class="samp">m68k-elf</samp>&rsquo; ABI.
It also added improved support for C++ and flat shared libraries,
both of which were ABI changes.
</p>
<hr />
<a class="anchor" id="microblaze-x-elf"></a><h3 class="heading" id="microblaze-*-elf"><span>microblaze-*-elf<a class="copiable-link" href="#microblaze-*-elf"> &para;</a></span></h3>
<p>Xilinx MicroBlaze processor.
This configuration is intended for embedded systems.
</p>
<hr />
<a class="anchor" id="mips-x-x"></a><h3 class="heading" id="mips-*-*"><span>mips-*-*<a class="copiable-link" href="#mips-*-*"> &para;</a></span></h3>
<p>If on a MIPS system you get an error message saying &ldquo;does not have gp
sections for all it&rsquo;s [sic] sectons [sic]&rdquo;, don&rsquo;t worry about it. This
happens whenever you use GAS with the MIPS linker, but there is not
really anything wrong, and it is okay to use the output file. You can
stop such warnings by installing the GNU linker.
</p>
<p>It would be nice to extend GAS to produce the gp tables, but they are
optional, and there should not be a warning about their absence.
</p>
<p>The libstdc++ atomic locking routines for MIPS targets requires MIPS II
and later. A patch went in just after the GCC 3.3 release to
make &lsquo;<samp class="samp">mips*-*-*</samp>&rsquo; use the generic implementation instead. You can also
configure for &lsquo;<samp class="samp">mipsel-elf</samp>&rsquo; as a workaround. The
&lsquo;<samp class="samp">mips*-*-linux*</samp>&rsquo; target continues to use the MIPS II routines. More
work on this is expected in future releases.
</p>
<p>The built-in <code class="code">__sync_*</code> functions are available on MIPS II and
later systems and others that support the &lsquo;<samp class="samp">ll</samp>&rsquo;, &lsquo;<samp class="samp">sc</samp>&rsquo; and
&lsquo;<samp class="samp">sync</samp>&rsquo; instructions. This can be overridden by passing
<samp class="option">--with-llsc</samp> or <samp class="option">--without-llsc</samp> when configuring GCC.
Since the Linux kernel emulates these instructions if they are
missing, the default for &lsquo;<samp class="samp">mips*-*-linux*</samp>&rsquo; targets is
<samp class="option">--with-llsc</samp>. The <samp class="option">--with-llsc</samp> and
<samp class="option">--without-llsc</samp> configure options may be overridden at compile
time by passing the <samp class="option">-mllsc</samp> or <samp class="option">-mno-llsc</samp> options to
the compiler.
</p>
<p>MIPS systems check for division by zero (unless
<samp class="option">-mno-check-zero-division</samp> is passed to the compiler) by
generating either a conditional trap or a break instruction. Using
trap results in smaller code, but is only supported on MIPS II and
later. Also, some versions of the Linux kernel have a bug that
prevents trap from generating the proper signal (<code class="code">SIGFPE</code>). To enable
the use of break, use the <samp class="option">--with-divide=breaks</samp>
<code class="command">configure</code> option when configuring GCC. The default is to
use traps on systems that support them.
</p>
<hr />
<a class="anchor" id="moxie-x-elf"></a><h3 class="heading" id="moxie-*-elf"><span>moxie-*-elf<a class="copiable-link" href="#moxie-*-elf"> &para;</a></span></h3>
<p>The moxie processor.
</p>
<hr />
<a class="anchor" id="msp430-x-elf"></a><h3 class="heading" id="msp430-*-elf*"><span>msp430-*-elf*<a class="copiable-link" href="#msp430-*-elf*"> &para;</a></span></h3>
<p>TI MSP430 processor.
This configuration is intended for embedded systems.
</p>
<p>&lsquo;<samp class="samp">msp430-*-elf</samp>&rsquo; is the standard configuration with most GCC
features enabled by default.
</p>
<p>&lsquo;<samp class="samp">msp430-*-elfbare</samp>&rsquo; is tuned for a bare-metal environment, and disables
features related to shared libraries and other functionality not used for
this device. This reduces code and data usage of the GCC libraries, resulting
in a minimal run-time environment by default.
</p>
<p>Features disabled by default include:
</p><ul class="itemize mark-bullet">
<li>transactional memory
</li><li>__cxa_atexit
</li></ul>
<hr />
<a class="anchor" id="nds32le-x-elf"></a><h3 class="heading" id="nds32le-*-elf"><span>nds32le-*-elf<a class="copiable-link" href="#nds32le-*-elf"> &para;</a></span></h3>
<p>Andes NDS32 target in little endian mode.
</p>
<hr />
<a class="anchor" id="nds32be-x-elf"></a><h3 class="heading" id="nds32be-*-elf"><span>nds32be-*-elf<a class="copiable-link" href="#nds32be-*-elf"> &para;</a></span></h3>
<p>Andes NDS32 target in big endian mode.
</p>
<hr />
<a class="anchor" id="nvptx-x-none"></a><h3 class="heading" id="nvptx-*-none"><span>nvptx-*-none<a class="copiable-link" href="#nvptx-*-none"> &para;</a></span></h3>
<p>Nvidia PTX target.
</p>
<p>Instead of GNU Binutils, you will need to install
<a class="uref" href="https://github.com/SourceryTools/nvptx-tools">nvptx-tools</a>.
Tell GCC where to find it:
<samp class="option">--with-build-time-tools=[install-nvptx-tools]/nvptx-none/bin</samp>.
</p>
<p>You will need newlib 4.3.0 or later. It can be
automatically built together with GCC. For this, add a symbolic link
to nvptx-newlib&rsquo;s <samp class="file">newlib</samp> directory to the directory containing
the GCC sources.
</p>
<p>Use the <samp class="option">--disable-sjlj-exceptions</samp> and
<samp class="option">--enable-newlib-io-long-long</samp> options when configuring.
</p>
<p>The <samp class="option">--with-arch</samp> option may be specified to override the
default value for the <samp class="option">-march</samp> option, and to also build
corresponding target libraries.
The default is <samp class="option">--with-arch=sm_52</samp>.
</p>
<p>For example, if <samp class="option">--with-arch=sm_70</samp> is specified,
code generation defaults to <samp class="option">-march=sm_70</samp> and
corresponding target libraries are built, in addition to those
mandated by <samp class="option">--with-multilib-list</samp>, if any,
see
<a class="uref" href="configure.html#with-multilib-list"><samp class="option">--with-multilib-list</samp></a>.
</p>
<hr />
<a class="anchor" id="or1k-x-elf"></a><h3 class="heading" id="or1k-*-elf"><span>or1k-*-elf<a class="copiable-link" href="#or1k-*-elf"> &para;</a></span></h3>
<p>The OpenRISC 1000 32-bit processor with delay slots.
This configuration is intended for embedded systems.
</p>
<hr />
<a class="anchor" id="or1k-x-linux"></a><h3 class="heading" id="or1k-*-linux"><span>or1k-*-linux<a class="copiable-link" href="#or1k-*-linux"> &para;</a></span></h3>
<p>The OpenRISC 1000 32-bit processor with delay slots.
</p>
<hr />
<a class="anchor" id="powerpc-x-x"></a><h3 class="heading" id="powerpc-*-*"><span>powerpc-*-*<a class="copiable-link" href="#powerpc-*-*"> &para;</a></span></h3>
<p>You can specify a default version for the <samp class="option">-mcpu=<var class="var">cpu_type</var></samp>
switch by using the configure option <samp class="option">--with-cpu-<var class="var">cpu_type</var></samp>.
</p>
<p>You will need GNU Binutils 2.20 or newer.
</p>
<hr />
<a class="anchor" id="powerpc-x-darwin"></a><h3 class="heading" id="powerpc-*-darwin*"><span>powerpc-*-darwin*<a class="copiable-link" href="#powerpc-*-darwin*"> &para;</a></span></h3>
<p>PowerPC running Darwin (Mac OS X kernel).
</p>
<p>Pre-installed versions of Mac OS X may not include any developer tools,
meaning that you will not be able to build GCC from source. Tool
binaries are available at
<a class="uref" href="https://opensource.apple.com">https://opensource.apple.com</a>.
</p>
<p>This version of GCC requires at least cctools-590.36. The
cctools-590.36 package referenced from
<a class="uref" 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
on systems older than 10.3.9 (aka darwin7.9.0).
</p>
<hr />
<a class="anchor" id="powerpc-x-elf"></a><h3 class="heading" id="powerpc-*-elf"><span>powerpc-*-elf<a class="copiable-link" href="#powerpc-*-elf"> &para;</a></span></h3>
<p>PowerPC system in big endian mode, running System V.4.
</p>
<hr />
<a class="anchor" id="powerpc-x-linux-gnu"></a><h3 class="heading" id="powerpc*-*-linux-gnu*"><span>powerpc*-*-linux-gnu*<a class="copiable-link" href="#powerpc*-*-linux-gnu*"> &para;</a></span></h3>
<p>PowerPC system in big endian mode running Linux.
</p>
<hr />
<a class="anchor" id="powerpc-x-netbsd"></a><h3 class="heading" id="powerpc-*-netbsd*"><span>powerpc-*-netbsd*<a class="copiable-link" href="#powerpc-*-netbsd*"> &para;</a></span></h3>
<p>PowerPC system in big endian mode running NetBSD.
</p>
<hr />
<a class="anchor" id="powerpc-x-eabisim"></a><h3 class="heading" id="powerpc-*-eabisim"><span>powerpc-*-eabisim<a class="copiable-link" href="#powerpc-*-eabisim"> &para;</a></span></h3>
<p>Embedded PowerPC system in big endian mode for use in running under the
PSIM simulator.
</p>
<hr />
<a class="anchor" id="powerpc-x-eabi"></a><h3 class="heading" id="powerpc-*-eabi"><span>powerpc-*-eabi<a class="copiable-link" href="#powerpc-*-eabi"> &para;</a></span></h3>
<p>Embedded PowerPC system in big endian mode.
</p>
<hr />
<a class="anchor" id="powerpcle-x-elf"></a><h3 class="heading" id="powerpcle-*-elf"><span>powerpcle-*-elf<a class="copiable-link" href="#powerpcle-*-elf"> &para;</a></span></h3>
<p>PowerPC system in little endian mode, running System V.4.
</p>
<hr />
<a class="anchor" id="powerpcle-x-eabisim"></a><h3 class="heading" id="powerpcle-*-eabisim"><span>powerpcle-*-eabisim<a class="copiable-link" href="#powerpcle-*-eabisim"> &para;</a></span></h3>
<p>Embedded PowerPC system in little endian mode for use in running under
the PSIM simulator.
</p>
<hr />
<a class="anchor" id="powerpcle-x-eabi"></a><h3 class="heading" id="powerpcle-*-eabi"><span>powerpcle-*-eabi<a class="copiable-link" href="#powerpcle-*-eabi"> &para;</a></span></h3>
<p>Embedded PowerPC system in little endian mode.
</p>
<hr />
<a class="anchor" id="rl78-x-elf"></a><h3 class="heading" id="rl78-*-elf"><span>rl78-*-elf<a class="copiable-link" href="#rl78-*-elf"> &para;</a></span></h3>
<p>The Renesas RL78 processor.
This configuration is intended for embedded systems.
</p>
<hr />
<a class="anchor" id="riscv32-x-elf"></a><h3 class="heading" id="riscv32-*-elf"><span>riscv32-*-elf<a class="copiable-link" href="#riscv32-*-elf"> &para;</a></span></h3>
<p>The RISC-V RV32 instruction set.
This configuration is intended for embedded systems.
This (and all other RISC-V) targets require the binutils 2.40 release.
</p>
<hr />
<a class="anchor" id="riscv32-x-linux"></a><h3 class="heading" id="riscv32-*-linux"><span>riscv32-*-linux<a class="copiable-link" href="#riscv32-*-linux"> &para;</a></span></h3>
<p>The RISC-V RV32 instruction set running GNU/Linux.
This (and all other RISC-V) targets require the binutils 2.40 release.
</p>
<hr />
<a class="anchor" id="riscv64-x-elf"></a><h3 class="heading" id="riscv64-*-elf"><span>riscv64-*-elf<a class="copiable-link" href="#riscv64-*-elf"> &para;</a></span></h3>
<p>The RISC-V RV64 instruction set.
This configuration is intended for embedded systems.
This (and all other RISC-V) targets require the binutils 2.40 release.
</p>
<hr />
<a class="anchor" id="riscv64-x-linux"></a><h3 class="heading" id="riscv64-*-linux"><span>riscv64-*-linux<a class="copiable-link" href="#riscv64-*-linux"> &para;</a></span></h3>
<p>The RISC-V RV64 instruction set running GNU/Linux.
This (and all other RISC-V) targets require the binutils 2.40 release.
</p>
<hr />
<a class="anchor" id="rx-x-elf"></a><h3 class="heading" id="rx-*-elf"><span>rx-*-elf<a class="copiable-link" href="#rx-*-elf"> &para;</a></span></h3>
<p>The Renesas RX processor.
</p>
<hr />
<a class="anchor" id="s390-x-linux"></a><h3 class="heading" id="s390-*-linux*"><span>s390-*-linux*<a class="copiable-link" href="#s390-*-linux*"> &para;</a></span></h3>
<p>S/390 system running GNU/Linux for S/390.
</p>
<hr />
<a class="anchor" id="s390x-x-linux"></a><h3 class="heading" id="s390x-*-linux*"><span>s390x-*-linux*<a class="copiable-link" href="#s390x-*-linux*"> &para;</a></span></h3>
<p>zSeries system (64-bit) running GNU/Linux for zSeries.
</p>
<hr />
<a class="anchor" id="s390x-ibm-tpf"></a><h3 class="heading" id="s390x-ibm-tpf*"><span>s390x-ibm-tpf*<a class="copiable-link" href="#s390x-ibm-tpf*"> &para;</a></span></h3>
<p>zSeries system (64-bit) running TPF. This platform is
supported as cross-compilation target only.
</p>
<hr />
<a class="anchor" id="x-x-solaris2"></a><h3 class="heading" id="g_t*-*-solaris2*"><span>*-*-solaris2*<a class="copiable-link" href="#g_t*-*-solaris2*"> &para;</a></span></h3>
<p>GCC only supports Solaris 11.4. Support for Solaris 11.3 and earlier
has been removed in GCC 15. Support for Solaris 10 has been removed
in GCC 10.
</p>
<p>Solaris 11.4 bundles several versions of GCC installed in parallel.
They can be found in <samp class="file">/usr/gcc/<var class="var">majorvers</var></samp>, with the default
in <samp class="file">/usr/bin</samp>. The exact set depends on the update installed. It
includes a subset of the available languages: since SRU 39 this
consists of C, C++, Objective-C, Ada, Fortran, and Go.
</p>
<p>In order to build the GNU Ada compiler, GNAT, a working GNAT is
needed.
</p>
<p>In order to build the GNU D compiler, GDC, a working GDC is needed
which isn&rsquo;t included with the bundled GCC. At least GDC 11.5.0 is
required on both SPARC and x86. However, the &lsquo;<samp class="samp">libphobos</samp>&rsquo; library
wasn&rsquo;t built by default in GCC 11 on SPARC, or on x86 when the Solaris
assembler is used, but can be enabled by configuring with
<samp class="option">--enable-libphobos</samp>.
</p>
<p>You need to install the <code class="code">system/header</code>, <code class="code">system/linker</code>, and
<code class="code">developer/assembler</code> packages.
</p>
<p>The build process works more smoothly with the GNU tools, so place
<samp class="file">/usr/gnu/bin</samp> before <samp class="file">/usr/bin</samp> in your <code class="env">PATH</code>.
</p>
<p>Unlike other systems, without special options a bi-arch compiler is
built. There are both 32-bit configurations which can also generate
64-bit code with the <samp class="option">-m64</samp> switch, and 64-bit configurations
capable of 32-bit code generation with <samp class="option">-m32</samp>.
</p>
<p>In both cases, the build compiler must match the target configuration.
Configure with &lsquo;<samp class="samp">CC='gcc -m32' CXX='g++ -m32' GDC='gdc -m32'</samp>&rsquo; for
a 32-bit target, or <samp class="option">-m64</samp> for a 64-bit target. The target
must always be specified explicitly with <samp class="option">--build=<var class="var">target</var></samp>
because <samp class="file">config.guess</samp> misdetects the situation, which can cause
build failures.
</p>
<p>Use the following targets as appropriate:
</p>
<dl class="table">
<dt>32-bit-default Solaris/x86</dt>
<dd><p>&lsquo;<samp class="samp">i386-pc-solaris2.11</samp>&rsquo;
</p></dd>
<dt>64-bit-default Solaris/x86</dt>
<dd><p>&lsquo;<samp class="samp">amd64-pc-solaris2.11</samp>&rsquo; or &lsquo;<samp class="samp">x86_64-pc-solaris2.11</samp>&rsquo;
</p></dd>
<dt>32-bit-default Solaris/SPARC</dt>
<dd><p>&lsquo;<samp class="samp">sparc-sun-solaris2.11</samp>&rsquo;
</p></dd>
<dt>64-bit-default Solaris/SPARC</dt>
<dd><p>&lsquo;<samp class="samp">sparcv9-sun-solaris2.11</samp>&rsquo; or &lsquo;<samp class="samp">sparc64-sun-solaris2.11</samp>&rsquo;
</p></dd>
</dl>
<p>GCC can use both the native Solaris assembler and linker and those
from GNU Binutils, with 3 supported combinations. One of those needs
to be selected when configuring GCC.
</p>
<ul class="itemize mark-bullet">
<li>Solaris <code class="command">as</code> and <code class="command">ld</code>
</li><li>GNU <code class="command">as</code> and Solaris <code class="command">ld</code>
</li><li>GNU <code class="command">as</code> and <code class="command">ld</code>
</li></ul>
<p>However, the combination of Solaris <code class="command">as</code> and GNU <code class="command">ld</code>
is broken and should be avoided.
</p>
<p>Solaris 11.4 includes GNU Binutils 2.30.1 or newer. This is the
minimum supported version. Either the bundled version or newer ones
are known to work well. When building a 32-bit-default version of GCC
with either or both GNU <code class="command">as</code> or GNU <code class="command">ld</code>, GNU Binutils
must be built separately as 32-bit executables.
</p>
<p>Both the GNU assembler (in <samp class="file">/usr/bin/gas</samp> and
<samp class="file">/usr/gnu/bin/as</samp>) and the Solaris assembler (in
<samp class="file">/usr/bin/as</samp>) work well. Solaris <code class="command">as</code> has support for
for hardware capabilities, while GNU <code class="command">as</code> supports newer x86
ISAs. With GNU <code class="command">as</code>, the binaries produced are smaller than
the ones produced using Solaris <code class="command">as</code>; this difference can be
quite significant for binaries containing debugging information.
</p>
<p>For linking, the Solaris linker (in <samp class="file">/usr/bin/ld</samp>) is preferred.
The GNU linker (in <samp class="file">/usr/bin/gld</samp> and <samp class="file">/usr/gnu/bin/ld</samp>)
works, too. However, it generally lacks platform specific features.
To use the LTO linker plugin (<samp class="option">-fuse-linker-plugin</samp>) with GNU
<code class="command">ld</code> in a 32-bit-default configuration, GNU Binutils
<em class="emph">must</em> be configured with <samp class="option">--enable-largefile</samp>.
</p>
<p>We <em class="emph">strongly</em> recommend to specify both the assembler and linker
with the <code class="command">configure</code> options <samp class="option">--with-as=<var class="var">pathname</var></samp>
and <samp class="option">--with-ld=<var class="var">pathname</var></samp> to guarantee the right tool is
found irrespective of the user&rsquo;s <code class="env">PATH</code>.
</p>
<p>To enable symbol versioning in &lsquo;<samp class="samp">libstdc++</samp>&rsquo; and other runtime
libraries with the Solaris linker, you need to have GNU
<code class="command">c++filt</code>, which is part of GNU Binutils. Symbol versioning
will be disabled if no appropriate version is found. Solaris
<code class="command">c++filt</code> from the Solaris Studio compilers does <em class="emph">not</em>
work.
</p>
<p>The versions of the GNU Multiple Precision Library (GMP), the MPFR
library and the MPC library bundled with Solaris 11.4 are
recent enough to match GCC&rsquo;s requirements.
</p>
<hr />
<a class="anchor" id="sparc-x-x"></a><h3 class="heading" id="sparc*-*-*"><span>sparc*-*-*<a class="copiable-link" href="#sparc*-*-*"> &para;</a></span></h3>
<p>This section contains general configuration information for all
SPARC-based platforms. In addition to reading this section, please
read all other sections that match your target.
</p>
<p>Newer versions of the GNU Multiple Precision Library (GMP), the MPFR
library and the MPC library are known to be miscompiled by earlier
versions of GCC on these platforms. We therefore recommend the use
of the exact versions of these libraries listed as minimal versions
in <a class="uref" href="prerequisites.html">the prerequisites</a>.
</p>
<hr />
<a class="anchor" id="sparc-x-linux"></a><h3 class="heading" id="sparc-*-linux*"><span>sparc-*-linux*<a class="copiable-link" href="#sparc-*-linux*"> &para;</a></span></h3>
<hr />
<a class="anchor" id="c6x-x-x"></a><h3 class="heading" id="c6x-*-*"><span>c6x-*-*<a class="copiable-link" href="#c6x-*-*"> &para;</a></span></h3>
<p>The C6X family of processors. This port requires binutils 2.22 or newer.
</p>
<hr />
<a class="anchor" id="visium-x-elf"></a><h3 class="heading" id="visium-*-elf"><span>visium-*-elf<a class="copiable-link" href="#visium-*-elf"> &para;</a></span></h3>
<p>CDS VISIUMcore processor.
This configuration is intended for embedded systems.
</p>
<hr />
<a class="anchor" id="x-x-vxworks"></a><h3 class="heading" id="g_t*-*-vxworks*"><span>*-*-vxworks*<a class="copiable-link" href="#g_t*-*-vxworks*"> &para;</a></span></h3>
<p>Support for VxWorks is in flux. At present GCC supports <em class="emph">only</em> the
very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC.
We welcome patches for other architectures supported by VxWorks 5.5.
Support for VxWorks AE would also be welcome; we believe this is merely
a matter of writing an appropriate &ldquo;configlette&rdquo; (see below). We are
not interested in supporting older, a.out or COFF-based, versions of
VxWorks in GCC 3.
</p>
<p>VxWorks comes with an older version of GCC installed in
<samp class="file"><var class="var">$WIND_BASE</var>/host</samp>; we recommend you do not overwrite it.
Choose an installation <var class="var">prefix</var> entirely outside <var class="var">$WIND_BASE</var>.
Before running <code class="command">configure</code>, create the directories <samp class="file"><var class="var">prefix</var></samp>
and <samp class="file"><var class="var">prefix</var>/bin</samp>. Link or copy the appropriate assembler,
linker, etc. into <samp class="file"><var class="var">prefix</var>/bin</samp>, and set your <var class="var">PATH</var> to
include that directory while running both <code class="command">configure</code> and
<code class="command">make</code>.
</p>
<p>You must give <code class="command">configure</code> the
<samp class="option">--with-headers=<var class="var">$WIND_BASE</var>/target/h</samp> switch so that it can
find the VxWorks system headers. Since VxWorks is a cross compilation
target only, you must also specify <samp class="option">--target=<var class="var">target</var></samp>.
<code class="command">configure</code> will attempt to create the directory
<samp class="file"><var class="var">prefix</var>/<var class="var">target</var>/sys-include</samp> and copy files into it;
make sure the user running <code class="command">configure</code> has sufficient privilege
to do so.
</p>
<p>GCC&rsquo;s exception handling runtime requires a special &ldquo;configlette&rdquo;
module, <samp class="file">contrib/gthr_supp_vxw_5x.c</samp>. Follow the instructions in
that file to add the module to your kernel build. (Future versions of
VxWorks will incorporate this module.)
</p>
<hr />
<a class="anchor" id="x86-64-x-x"></a><h3 class="heading" id="x86_005f64-*-*_002c-amd64-*-*"><span>x86_64-*-*, amd64-*-*<a class="copiable-link" href="#x86_005f64-*-*_002c-amd64-*-*"> &para;</a></span></h3>
<p>GCC supports the x86-64 architecture implemented by the AMD64 processor
(amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD.
On GNU/Linux the default is a bi-arch compiler which is able to generate
both 64-bit x86-64 and 32-bit x86 code (via the <samp class="option">-m32</samp> switch).
</p>
<hr />
<a class="anchor" id="xtensa-x-elf"></a><h3 class="heading" id="xtensa*-*-elf"><span>xtensa*-*-elf<a class="copiable-link" href="#xtensa*-*-elf"> &para;</a></span></h3>
<p>This target is intended for embedded Xtensa systems using the
&lsquo;<samp class="samp">newlib</samp>&rsquo; C library. It uses ELF but does not support shared
objects. Designed-defined instructions specified via the
Tensilica Instruction Extension (TIE) language are only supported
through inline assembly.
</p>
<p>The Xtensa configuration information must be specified prior to
building GCC. The <samp class="file">include/xtensa-config.h</samp> header
file contains the configuration information. If you created your
own Xtensa configuration with the Xtensa Processor Generator, the
downloaded files include a customized copy of this header file,
which you can use to replace the default header file.
</p>
<hr />
<a class="anchor" id="xtensa-x-linux"></a><h3 class="heading" id="xtensa*-*-linux*"><span>xtensa*-*-linux*<a class="copiable-link" href="#xtensa*-*-linux*"> &para;</a></span></h3>
<p>This target is for Xtensa systems running GNU/Linux. It supports ELF
shared objects and the GNU C library (glibc). It also generates
position-independent code (PIC) regardless of whether the
<samp class="option">-fpic</samp> or <samp class="option">-fPIC</samp> options are used. In other
respects, this target is the same as the
<a class="uref" href="#xtensa*-*-elf">&lsquo;<samp class="samp">xtensa*-*-elf</samp>&rsquo;</a> target.
</p>
<hr />
<a class="anchor" id="windows"></a><h3 class="heading" id="Microsoft-Windows"><span>Microsoft Windows<a class="copiable-link" href="#Microsoft-Windows"> &para;</a></span></h3>
<h4 class="subheading" id="Intel-32-bit-versions"><span>Intel 32-bit versions<a class="copiable-link" href="#Intel-32-bit-versions"> &para;</a></span></h4>
<p>The 32-bit versions of Windows, including Windows 95, Windows NT, Windows
XP, and Windows Vista, are supported by several different target
platforms. These targets differ in which Windows subsystem they target
and which C libraries are used.
</p>
<ul class="itemize mark-bullet">
<li>Cygwin <a class="uref" href="#x-x-cygwin">*-*-cygwin</a>: Cygwin provides a user-space
Linux API emulation layer in the Win32 subsystem.
</li><li>MinGW <a class="uref" href="#x-x-mingw32">*-*-mingw32</a>: MinGW is a native GCC port for
the Win32 subsystem that provides a subset of POSIX.
</li><li>MKS i386-pc-mks: NuTCracker from MKS. See
<a class="uref" href="https://www.mkssoftware.com">https://www.mkssoftware.com</a> for more information.
</li></ul>
<h4 class="subheading" id="Intel-64-bit-versions"><span>Intel 64-bit versions<a class="copiable-link" href="#Intel-64-bit-versions"> &para;</a></span></h4>
<p>GCC contains support for x86-64 using the mingw-w64
runtime library, available from <a class="uref" href="https://www.mingw-w64.org/downloads/">https://www.mingw-w64.org/downloads/</a>.
This library should be used with the target triple x86_64-pc-mingw32.
</p>
<h4 class="subheading" id="Windows-CE"><span>Windows CE<a class="copiable-link" href="#Windows-CE"> &para;</a></span></h4>
<p>Windows CE is supported as a target only on Hitachi
SuperH (sh-wince-pe), and MIPS (mips-wince-pe).
</p>
<h4 class="subheading" id="Other-Windows-Platforms"><span>Other Windows Platforms<a class="copiable-link" href="#Other-Windows-Platforms"> &para;</a></span></h4>
<p>GCC no longer supports Windows NT on the Alpha or PowerPC.
</p>
<p>GCC no longer supports the Windows POSIX subsystem.
</p>
<p>Old target names including *-*-winnt and *-*-windowsnt are no longer used.
</p>
<p>UWIN support has been removed due to a lack of maintenance.
</p>
<hr />
<a class="anchor" id="x-x-cygwin"></a><h3 class="heading" id="g_t*-*-cygwin"><span>*-*-cygwin<a class="copiable-link" href="#g_t*-*-cygwin"> &para;</a></span></h3>
<p>Ports of GCC are included with the
<a class="uref" href="https://cygwin.com">Cygwin environment</a>.
</p>
<p>GCC will build under Cygwin without modification; it does not build
with Microsoft&rsquo;s C++ compiler and there are no plans to make it do so.
</p>
<p>The Cygwin native compiler can be configured to target any 32-bit x86
cpu architecture desired; the default is i686-pc-cygwin. It should be
used with as up-to-date a version of binutils as possible; use either
the latest official GNU Binutils release in the Cygwin distribution,
or version 2.20 or above if building your own.
</p>
<hr />
<a class="anchor" id="x-x-mingw32"></a><h3 class="heading" id="g_t*-*-mingw32"><span>*-*-mingw32<a class="copiable-link" href="#g_t*-*-mingw32"> &para;</a></span></h3>
<p>GCC will build with and support only MinGW runtime 3.12 and later.
Earlier versions of headers are incompatible with the new default semantics
of <code class="code">extern inline</code> in <code class="code">-std=c99</code> and <code class="code">-std=gnu99</code> modes.
</p>
<hr />
<a class="anchor" id="older"></a><h3 class="heading" id="Older-systems"><span>Older systems<a class="copiable-link" href="#Older-systems"> &para;</a></span></h3>
<p>GCC contains support files for many older (1980s and early
1990s) Unix variants. For the most part, support for these systems
has not been deliberately removed, but it has not been maintained for
several years and may suffer from bitrot.
</p>
<p>Starting with GCC 3.1, each release has a list of &ldquo;obsoleted&rdquo; systems.
Support for these systems is still present in that release, but
<code class="command">configure</code> will fail unless the <samp class="option">--enable-obsolete</samp>
option is given. Unless a maintainer steps forward, support for these
systems will be removed from the next release of GCC.
</p>
<p>Support for old systems as hosts for GCC can cause problems if the
workarounds for compiler, library and operating system bugs affect the
cleanliness or maintainability of the rest of GCC. In some cases, to
bring GCC up on such a system, if still possible with current GCC, may
require first installing an old version of GCC which did work on that
system, and using it to compile a more recent GCC, to avoid bugs in the
vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
<samp class="file">old-releases</samp> directory on the <a class="uref" href="../mirrors.html">GCC mirror
sites</a>. Header bugs may generally be avoided using
<code class="command">fixincludes</code>, but bugs or deficiencies in libraries and the
operating system may still cause problems.
</p>
<p>Support for older systems as targets for cross-compilation is less
problematic than support for them as hosts for GCC; if an enthusiast
wishes to make such a target work again (including resurrecting any of
the targets that never worked with GCC 2, starting from the last
version before they were removed), patches
<a class="uref" href="../contribute.html">following the usual requirements</a> would be
likely to be accepted, since they should not affect the support for more
modern targets.
</p>
<p>Some of the information on specific systems above relates to
such older systems, but much of the information
about GCC on such systems (which may no longer be applicable to
current GCC) is to be found in the GCC texinfo manual.
</p>
<hr />
<a class="anchor" id="elf"></a><h3 class="heading" id="all-ELF-targets-_0028SVR4_002c-Solaris_002c-etc_002e_0029"><span>all ELF targets (SVR4, Solaris, etc.)<a class="copiable-link" href="#all-ELF-targets-_0028SVR4_002c-Solaris_002c-etc_002e_0029"> &para;</a></span></h3>
<p>C++ support is significantly better on ELF targets if you use the
<a class="uref" href="./configure.html#with-gnu-ld">GNU linker</a>; duplicate copies of
inlines, vtables and template instantiations will be discarded
automatically.
</p>
<hr />
<p>
<p><a class="uref" href="./index.html">Return to the GCC Installation page</a>
</p>
</body>
</html>