Please read this document carefully before installing the GNU Compiler Collection on your machine.

Note that this list of install notes is not 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.

- aarch64*-*-*
- amdgcn-*-amdhsa
- arc-*-elf32
- arc-linux-uclibc
- arm-*-eabi
- avr
- Blackfin
- cris
- DOS
- epiphany-*-elf
- ft32-*-elf
- *-*-freebsd*
- h8300-hms
- hppa-*-linux
- hppa64-hp-hpux11*
- *-*-linux-gnu
- i?86-*-linux*
- ia64-*-linux
- ia64-*-hpux*
- *-ibm-aix*
- iq2000-*-elf
- loongarch
- lm32-*-elf
- lm32-*-uclinux
- m32c-*-elf
- m32r-*-elf
- m68k-*-*
- m68k-*-uclinux
- microblaze-*-elf
- mips-*-*
- moxie-*-elf
- msp430-*-elf
- nds32le-*-elf
- nds32be-*-elf
- nvptx-*-none
- or1k-*-elf
- or1k-*-linux
- powerpc*-*-*
- powerpc-*-darwin*
- powerpc-*-elf
- powerpc*-*-linux-gnu*
- powerpc-*-netbsd*
- powerpc-*-eabisim
- powerpc-*-eabi
- powerpcle-*-elf
- powerpcle-*-eabisim
- powerpcle-*-eabi
- riscv32-*-elf
- riscv32-*-linux
- riscv64-*-elf
- riscv64-*-linux
- rl78-*-elf
- rx-*-elf
- s390-*-linux*
- s390x-*-linux*
- s390x-ibm-tpf*
- *-*-solaris2*
- sparc*-*-*
- sparc-*-linux*
- c6x-*-*
- visium-*-elf
- *-*-vxworks*
- x86_64-*-*, amd64-*-*
- xtensa*-*-elf
- xtensa*-*-linux*
- Microsoft Windows
- *-*-cygwin
- *-*-mingw32
- OS/2
- Older systems

- all ELF targets (SVR4, Solaris, etc.)

### aarch64*-*-* ¶

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 `--enable-fix-cortex-a53-835769` option. This will enable the fix by default and can be explicitly disabled during compilation by passing the `-mno-fix-cortex-a53-835769` option. Conversely, `--disable-fix-cortex-a53-835769` will disable the workaround by default. The workaround is disabled by default if neither of `--enable-fix-cortex-a53-835769` or `--disable-fix-cortex-a53-835769` is given at configure time.

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 `--enable-fix-cortex-a53-843419` 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 `-mno-fix-cortex-a53-843419` option. Conversely, `--disable-fix-cortex-a53-843419` will disable the workaround by default. The workaround is disabled by default if neither of `--enable-fix-cortex-a53-843419` or `--disable-fix-cortex-a53-843419` is given at configure time.

To enable Branch Target Identification Mechanism and Return Address Signing by default at configure time use the `--enable-standard-branch-protection` option. This is equivalent to having `-mbranch-protection=standard` during compilation. This can be explicitly disabled during compilation by passing the `-mbranch-protection=none` option which turns off all types of branch protections. Conversely, `--disable-standard-branch-protection` will disable both the protections by default. This mechanism is turned off by default if neither of the options are given at configure time.

### amdgcn-*-amdhsa ¶

AMD GCN GPU target.

Instead of GNU Binutils, you need to install LLVM and copy `bin/llvm-mc` to `amdgcn-amdhsa/bin/as`, `bin/lld` to `amdgcn-amdhsa/bin/ld`, `bin/llvm-objdump` to `amdgcn-amdhsa/bin/objdump`, `bin/llvm-nm` to `amdgcn-amdhsa/bin/nm`, and `bin/llvm-ar` to both `bin/amdgcn-amdhsa-ar` and `bin/amdgcn-amdhsa-ranlib`. 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; `nm`, `ar`, and `ranlib` are required when installing `gcc-nm`, `gcc-ar`, and `gcc-ranlib`.

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 `--with-multilib-list=` to tailor the built multilibs. Note that mixing ISAs in the same binary is not supported and gives a linker error.

By default, multilib support is built for `gfx908`, `gfx90a`, `gfx9-generic`, `gfx9-4-generic`, `gfx10-3-generic`, and `gfx11-generic`, 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 `--with-multilib-list=` that only lists GFX9 or GFX10-3 devices, while LLVM 15 is required for GFX 11 device and `gfx1036`. At least LLVM 16 is required for `gfx1150` and `gfx1151`, LLVM 18 for `gfx942`, LLVM 19 for the generic `gfx9-generic`, `gfx10-3-generic`, and `gfx11-generic` targets and for `gfx1152`, while LLVM 20 is required for `gfx950`, `gfx1153`, and `gfx9-4-generic`.

The supported ISA architectures are listed in the GCC manual. The generic ISA targets `gfx9-generic`, `gfx10-3-generic`, and `gfx11-generic` reduce the number of required multilibs but note that `gfx9-generic` does not include `gfx908` or `gfx90a`, 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.

Use Newlib (4.6.0 or newer).

To run the binaries, install the HSA Runtime from the ROCm Platform, and use `libexec/gcc/amdhsa-amdhsa/version/gcn-run` to launch them on the GPU.

### arc-*-elf32 ¶

Use ‘`configure --target=arc-elf32 --with-cpu=cpu --enable-languages="c,c++"`’ to configure GCC, with cpu being one of ‘`arc600`’, ‘`arc601`’, or ‘`arc700`’.

### arc-linux-uclibc ¶

Use ‘`configure --target=arc-linux-uclibc --with-cpu=arc700 --enable-languages="c,c++"`’ to configure GCC.

### arm-*-eabi ¶

ARM-family processors.

Building the Ada frontend commonly fails (an infinite loop executing `xsinfo`) 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.

### avr ¶

AVR 8-bit microcontrollers. These are used in embedded applications. There are no standard Unix configurations. See AVR Options in the main manual for the list of supported MCU types.

Use ‘`configure --target=avr --enable-languages="c,c++"`’ to configure GCC.

Further installation notes and other useful information about AVR tools can also be obtained from:

- AVR-LibC: Building and Installing the GNU Tool Chain
- AVRtest: Running the avr-gcc Testsuite

### Blackfin ¶

The Blackfin processor, an Analog Devices DSP. See “Blackfin Options” in the main manual

More information, and a version of binutils with support for this processor, are available at https://sourceforge.net/projects/adi-toolchain/.

### CRIS ¶

CRIS is a CPU architecture in Axis Communications systems-on-a-chip, for example the ETRAX series. These are used in embedded applications.

See “CRIS Options” in the main manual for a list of CRIS-specific options.

Use ‘`configure --target=cris-elf`’ to configure GCC for building a cross-compiler for CRIS.

### DOS ¶

Please have a look at the binaries page.

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.

### epiphany-*-elf ¶

Adapteva Epiphany. This configuration is intended for embedded systems.

### *-*-freebsd* ¶

FreeBSD using the ELF file format with DWARF 2 debugging.

We recommend bootstrapping against the latest GNU Binutils or the version found in the `devel/binutils` port. This also has been known to enable additional features and improve overall testsuite results.

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 `--disable-multilib` there in case you are building one of these front ends.

Go (or rather libgo) is generally broken on FreeBSD.

### ft32-*-elf ¶

The FT32 processor. This configuration is intended for embedded systems.

### h8300-hms ¶

Renesas H8/300 series of processors.

### hppa64-hp-hpux11* ¶

Only the 64-bit ‘`hppa`’ target is supported on HP-UX. Support for 32-bit ‘`hppa`’ was discontinued in GCC 13.

We require using gas on all hppa platforms.

It may be helpful to configure GCC with the `--with-gnu-as` and `--with-as=…` options to ensure that GCC can find GAS.

Only the HP linker is supported. Thus, it is best to explicitly configure the target with the `--with-ld=…` option.

The DCE thread library is not supported, so `--enable-threads=dce` does not work.

Currently, there are no precompiled binaries for 64-bit HP-UX.

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.

### *-*-linux-gnu ¶

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.

### i?86-*-linux* ¶

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 www.bitwizard.nl.

### ia64-*-linux ¶

IA-64 processor (also known as IPF, or Itanium Processor Family) running GNU/Linux.

If you are using the installed system libunwind library with `--with-system-libunwind`, then you must use libunwind 0.98 or later.

### ia64-*-hpux* ¶

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 `--with-gnu-as` may be necessary.

### *-ibm-aix* ¶

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.

“out of memory” bootstrap failures may indicate a problem with process resource limits (ulimit). Hard limits are configured in the `/etc/security/limits` system configuration file.

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.

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 LDR_CNTRL environment variable, e.g.,

    % LDR_CNTRL=MAXDATA=0x50000000
    % export LDR_CNTRL

One can start with a pre-compiled version of GCC to build from sources. One may delete GCC’s “fixed” header files when starting with a version of GCC built for an earlier release of AIX.

To speed up the configuration phases of bootstrapping and installing GCC, one may use GNU Bash instead of AIX `/bin/sh`, e.g.,

    % CONFIG_SHELL=/opt/freeware/bin/bash
    % export CONFIG_SHELL

and then proceed as described in the build instructions, where we strongly recommend specifying an absolute path to invoke srcdir/configure.

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.

Errors involving `alloca` when building GCC generally are due to an incorrect definition of `CC` 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 must be invoked as `cc` (not `xlc`). Once `configure` has been informed of `xlc`, one needs to use ‘`make distclean`’ to remove the configure cache files and ensure that `CC` environment variable does not provide a definition that will confuse `configure`. If this error occurs during stage2 or later, then the problem most likely is the version of Make (see above).

The native `as` and `ld` 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 or AIX 7. The native AIX tools do interoperate with GCC.

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.

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.

Building `libstdc++.a` 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)

‘`libstdc++`’ in GCC 3.4 increments the major version number of the shared object and GCC installation places the `libstdc++.a` 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 ‘`libstdc++`’ shared object needs to be available to the AIX runtime loader. The GCC 3.1 ‘`libstdc++.so.4`’, if present, and GCC 3.3 ‘`libstdc++.so.5`’ shared objects can be installed for runtime dynamic loading using the following steps to set the ‘`F_LOADONLY`’ flag in the shared object for each multilib `libstdc++.a` installed:

Extract the shared objects from the currently installed `libstdc++.a` archive:

    % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5

Enable the ‘`F_LOADONLY`’ flag so that the shared object will be available for runtime dynamic loading, but not linking:

    % strip -e libstdc++.so.4 libstdc++.so.5

Archive the runtime-only shared object in the GCC 3.4 `libstdc++.a` archive:

    % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5

Eventually, the `--with-aix-soname=svr4` configure option may drop the need for this procedure for libraries that support it.

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.

AIX 4.3 utilizes a “large format” 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 “not a COFF file”. The version of the routines shipped with AIX 4.3.1 should work for a 32-bit environment. The `-g` option of the archive command may be used to create archives of 32-bit objects using the original “small format”. A correct version of the routines is shipped with AIX 4.3.2 and above.

Some versions of the AIX binder (linker) can fail with a relocation overflow severe error when the `-bbigtoc` 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.

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.

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.

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., ‘`.`’ vs ‘`,`’ 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 `LANG` environment variable to ‘`C`’ or ‘`En_US`’.

A default can be specified with the `-mcpu=cpu_type` switch and using the configure option `--with-cpu-cpu_type`.

### iq2000-*-elf ¶

Vitesse IQ2000 processors. These are used in embedded applications. There are no standard Unix configurations.

### lm32-*-elf ¶

Lattice Mico32 processor. This configuration is intended for embedded systems.

### lm32-*-uclinux ¶

Lattice Mico32 processor. This configuration is intended for embedded systems running uClinux.

### LoongArch ¶

LoongArch processor. The following LoongArch targets are available:

`loongarch64-linux-gnu*`

  LoongArch processor running GNU/Linux. This target triplet may be coupled with a small set of possible suffixes to identify their default ABI type:

  `f64`

    Uses `lp64d/base` ABI by default.

  `f32`

    Uses `lp64f/base` ABI by default.

  `sf`

    Uses `lp64s/base` ABI by default.

`loongarch64-linux-gnu`

  Same as `loongarch64-linux-gnuf64` for legacy support.

More information about LoongArch can be found at https://github.com/loongson/LoongArch-Documentation.

### m32c-*-elf ¶

Renesas M32C processor. This configuration is intended for embedded systems.

### m32r-*-elf ¶

Renesas M32R processor. This configuration is intended for embedded systems.

### m68k-*-* ¶

By default, ‘`m68k-*-elf*`’, ‘`m68k-*-rtems`’, ‘`m68k-*-uclinux`’ and ‘`m68k-*-linux`’ build libraries for both M680x0 and ColdFire processors. If you only need the M680x0 libraries, you can omit the ColdFire ones by passing `--with-arch=m68k` to `configure`. Alternatively, you can omit the M680x0 libraries by passing `--with-arch=cf` to `configure`. These targets default to 5206 or 5475 code as appropriate for the target system when configured with `--with-arch=cf` and 68020 code otherwise.

The ‘`m68k-*-netbsd`’ and ‘`m68k-*-openbsd`’ targets also support the `--with-arch` option. They will generate ColdFire CFV4e code when configured with `--with-arch=cf` and 68020 code otherwise.

You can override the default processors listed above by configuring with `--with-cpu=target`. This target can either be a `-mcpu` argument or one of the following values: ‘`m68000`’, ‘`m68010`’, ‘`m68020`’, ‘`m68030`’, ‘`m68040`’, ‘`m68060`’, ‘`m68020-40`’ and ‘`m68020-60`’.

GCC requires at least binutils version 2.17 on these targets.

### m68k-*-uclinux ¶

GCC 4.3 changed the uClinux configuration so that it uses the ‘`m68k-linux-gnu`’ ABI rather than the ‘`m68k-elf`’ ABI. It also added improved support for C++ and flat shared libraries, both of which were ABI changes.

### microblaze-*-elf ¶

Xilinx MicroBlaze processor. This configuration is intended for embedded systems.

### mips-*-* ¶

If on a MIPS system you get an error message saying “does not have gp sections for all it’s [sic] sectons [sic]”, don’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.

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.

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 ‘`mips*-*-*`’ use the generic implementation instead. You can also configure for ‘`mipsel-elf`’ as a workaround. The ‘`mips*-*-linux*`’ target continues to use the MIPS II routines. More work on this is expected in future releases.

The built-in `__sync_*` functions are available on MIPS II and later systems and others that support the ‘`ll`’, ‘`sc`’ and ‘`sync`’ instructions. This can be overridden by passing `--with-llsc` or `--without-llsc` when configuring GCC. Since the Linux kernel emulates these instructions if they are missing, the default for ‘`mips*-*-linux*`’ targets is `--with-llsc`. The `--with-llsc` and `--without-llsc` configure options may be overridden at compile time by passing the `-mllsc` or `-mno-llsc` options to the compiler.

MIPS systems check for division by zero (unless `-mno-check-zero-division` 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 (`SIGFPE`). To enable the use of break, use the `--with-divide=breaks` `configure` option when configuring GCC. The default is to use traps on systems that support them.

### moxie-*-elf ¶

The moxie processor.

### msp430-*-elf* ¶

TI MSP430 processor. This configuration is intended for embedded systems.

‘`msp430-*-elf`’ is the standard configuration with most GCC features enabled by default.

‘`msp430-*-elfbare`’ 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.

Features disabled by default include:

- transactional memory
- __cxa_atexit

### nds32le-*-elf ¶

Andes NDS32 target in little endian mode.

### nds32be-*-elf ¶

Andes NDS32 target in big endian mode.

### nvptx-*-none ¶

Nvidia PTX target.

Instead of GNU Binutils, you will need to install nvptx-tools. Tell GCC where to find it: `--with-build-time-tools=[install-nvptx-tools]/nvptx-none/bin`.

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’s `newlib` directory to the directory containing the GCC sources.

Use the `--disable-sjlj-exceptions` and `--enable-newlib-io-long-long` options when configuring.

The `--with-arch` option may be specified to override the default value for the `-march` option, and to also build corresponding target libraries. The default is `--with-arch=sm_52`.

For example, if `--with-arch=sm_70` is specified, code generation defaults to `-march=sm_70` and corresponding target libraries are built, in addition to those mandated by `--with-multilib-list`, if any, see `--with-multilib-list`.

### or1k-*-elf ¶

The OpenRISC 1000 32-bit processor with delay slots. This configuration is intended for embedded systems.

### or1k-*-linux ¶

The OpenRISC 1000 32-bit processor with delay slots.

### powerpc-*-* ¶

You can specify a default version for the `-mcpu=cpu_type` switch by using the configure option `--with-cpu-cpu_type`.

You will need GNU Binutils 2.20 or newer.

### powerpc-*-darwin* ¶

PowerPC running Darwin (Mac OS X kernel).

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 https://opensource.apple.com.

This version of GCC requires at least cctools-590.36. The cctools-590.36 package referenced from https://gcc.gnu.org/ml/gcc/2006-03/msg00507.html will not work on systems older than 10.3.9 (aka darwin7.9.0).

### powerpc-*-elf ¶

PowerPC system in big endian mode, running System V.4.

### powerpc*-*-linux-gnu* ¶

PowerPC system in big endian mode running Linux.

### powerpc-*-netbsd* ¶

PowerPC system in big endian mode running NetBSD.

### powerpc-*-eabisim ¶

Embedded PowerPC system in big endian mode for use in running under the PSIM simulator.

### powerpc-*-eabi ¶

Embedded PowerPC system in big endian mode.

### powerpcle-*-elf ¶

PowerPC system in little endian mode, running System V.4.

### powerpcle-*-eabisim ¶

Embedded PowerPC system in little endian mode for use in running under the PSIM simulator.

### powerpcle-*-eabi ¶

Embedded PowerPC system in little endian mode.

### rl78-*-elf ¶

The Renesas RL78 processor. This configuration is intended for embedded systems.

### riscv32-*-elf ¶

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.

### riscv32-*-linux ¶

The RISC-V RV32 instruction set running GNU/Linux. This (and all other RISC-V) targets require the binutils 2.40 release.

### riscv64-*-elf ¶

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.

### riscv64-*-linux ¶

The RISC-V RV64 instruction set running GNU/Linux. This (and all other RISC-V) targets require the binutils 2.40 release.

### rx-*-elf ¶

The Renesas RX processor.

### s390-*-linux* ¶

S/390 system running GNU/Linux for S/390.

### s390x-*-linux* ¶

zSeries system (64-bit) running GNU/Linux for zSeries.

### s390x-ibm-tpf* ¶

zSeries system (64-bit) running TPF. This platform is supported as cross-compilation target only.

### *-*-solaris2* ¶

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.

Solaris 11.4 bundles several versions of GCC installed in parallel. They can be found in `/usr/gcc/majorvers`, with the default in `/usr/bin`. 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.

In order to build the GNU Ada compiler, GNAT, a working GNAT is needed.

In order to build the GNU D compiler, GDC, a working GDC is needed which isn’t included with the bundled GCC. At least GDC 11.5.0 is required on both SPARC and x86. However, the ‘`libphobos`’ library wasn’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 `--enable-libphobos`.

You need to install the `system/header`, `system/linker`, and `developer/assembler` packages.

The build process works more smoothly with the GNU tools, so place `/usr/gnu/bin` before `/usr/bin` in your `PATH`.

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 `-m64` switch, and 64-bit configurations capable of 32-bit code generation with `-m32`.

In both cases, the build compiler must match the target configuration. Configure with ‘`CC='gcc -m32' CXX='g++ -m32' GDC='gdc -m32'`’ for a 32-bit target, or `-m64` for a 64-bit target. The target must always be specified explicitly with `--build=target` because `config.guess` misdetects the situation, which can cause build failures.

Use the following targets as appropriate:

32-bit-default Solaris/x86

  ‘`i386-pc-solaris2.11`’

64-bit-default Solaris/x86

  ‘`amd64-pc-solaris2.11`’ or ‘`x86_64-pc-solaris2.11`’

32-bit-default Solaris/SPARC

  ‘`sparc-sun-solaris2.11`’

64-bit-default Solaris/SPARC

  ‘`sparcv9-sun-solaris2.11`’ or ‘`sparc64-sun-solaris2.11`’

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.

- Solaris `as` and `ld`
- GNU `as` and Solaris `ld`
- GNU `as` and `ld`

However, the combination of Solaris `as` and GNU `ld` is broken and should be avoided.

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 `as` or GNU `ld`, GNU Binutils must be built separately as 32-bit executables.

Both the GNU assembler (in `/usr/bin/gas` and `/usr/gnu/bin/as`) and the Solaris assembler (in `/usr/bin/as`) work well. Solaris `as` has support for for hardware capabilities, while GNU `as` supports newer x86 ISAs. With GNU `as`, the binaries produced are smaller than the ones produced using Solaris `as`; this difference can be quite significant for binaries containing debugging information.

For linking, the Solaris linker (in `/usr/bin/ld`) is preferred. The GNU linker (in `/usr/bin/gld` and `/usr/gnu/bin/ld`) works, too. However, it generally lacks platform specific features. To use the LTO linker plugin (`-fuse-linker-plugin`) with GNU `ld` in a 32-bit-default configuration, GNU Binutils must be configured with `--enable-largefile`.

We strongly recommend to specify both the assembler and linker with the `configure` options `--with-as=pathname` and `--with-ld=pathname` to guarantee the right tool is found irrespective of the user’s `PATH`.

To enable symbol versioning in ‘`libstdc++`’ and other runtime libraries with the Solaris linker, you need to have GNU `c++filt`, which is part of GNU Binutils. Symbol versioning will be disabled if no appropriate version is found. Solaris `c++filt` from the Solaris Studio compilers does not work.

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’s requirements.

### sparc*-*-* ¶

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.

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 the prerequisites.

### sparc-*-linux* ¶

### c6x-*-* ¶

The C6X family of processors. This port requires binutils 2.22 or newer.

### visium-*-elf ¶

CDS VISIUMcore processor. This configuration is intended for embedded systems.

### *-*-vxworks* ¶

Support for VxWorks is in flux. At present GCC supports only 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 “configlette” (see below). We are not interested in supporting older, a.out or COFF-based, versions of VxWorks in GCC 3.

VxWorks comes with an older version of GCC installed in `$WIND_BASE/host`; we recommend you do not overwrite it. Choose an installation prefix entirely outside $WIND_BASE. Before running `configure`, create the directories `prefix` and `prefix/bin`. Link or copy the appropriate assembler, linker, etc. into `prefix/bin`, and set your PATH to include that directory while running both `configure` and `make`.

You must give `configure` the `--with-headers=$WIND_BASE/target/h` switch so that it can find the VxWorks system headers. Since VxWorks is a cross compilation target only, you must also specify `--target=target`. `configure` will attempt to create the directory `prefix/target/sys-include` and copy files into it; make sure the user running `configure` has sufficient privilege to do so.

GCC’s exception handling runtime requires a special “configlette” module, `contrib/gthr_supp_vxw_5x.c`. Follow the instructions in that file to add the module to your kernel build. (Future versions of VxWorks will incorporate this module.)

### x86_64-*-*, amd64-*-* ¶

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 `-m32` switch).

### xtensa*-*-elf ¶

This target is intended for embedded Xtensa systems using the ‘`newlib`’ 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.

The Xtensa configuration information must be specified prior to building GCC. The `include/xtensa-config.h` 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.

### xtensa*-*-linux* ¶

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 `-fpic` or `-fPIC` options are used. In other respects, this target is the same as the ‘`xtensa*-*-elf`’ target.

### Microsoft Windows ¶

#### Intel 32-bit versions ¶

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.

- Cygwin *-*-cygwin: Cygwin provides a user-space Linux API emulation layer in the Win32 subsystem.
- MinGW *-*-mingw32: MinGW is a native GCC port for the Win32 subsystem that provides a subset of POSIX.
- MKS i386-pc-mks: NuTCracker from MKS. See https://www.mkssoftware.com for more information.

#### Intel 64-bit versions ¶

GCC contains support for x86-64 using the mingw-w64 runtime library, available from https://www.mingw-w64.org/downloads/. This library should be used with the target triple x86_64-pc-mingw32.

#### Windows CE ¶

Windows CE is supported as a target only on Hitachi SuperH (sh-wince-pe), and MIPS (mips-wince-pe).

#### Other Windows Platforms ¶

GCC no longer supports Windows NT on the Alpha or PowerPC.

GCC no longer supports the Windows POSIX subsystem.

Old target names including *-*-winnt and *-*-windowsnt are no longer used.

UWIN support has been removed due to a lack of maintenance.

### *-*-cygwin ¶

Ports of GCC are included with the Cygwin environment.

GCC will build under Cygwin without modification; it does not build with Microsoft’s C++ compiler and there are no plans to make it do so.

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.

### *-*-mingw32 ¶

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 `extern inline` in `-std=c99` and `-std=gnu99` modes.

### Older systems ¶

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.

Starting with GCC 3.1, each release has a list of “obsoleted” systems. Support for these systems is still present in that release, but `configure` will fail unless the `--enable-obsolete` option is given. Unless a maintainer steps forward, support for these systems will be removed from the next release of GCC.

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 `old-releases` directory on the GCC mirror sites. Header bugs may generally be avoided using `fixincludes`, but bugs or deficiencies in libraries and the operating system may still cause problems.

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 following the usual requirements would be likely to be accepted, since they should not affect the support for more modern targets.

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.

### all ELF targets (SVR4, Solaris, etc.) ¶

C++ support is significantly better on ELF targets if you use the GNU linker; duplicate copies of inlines, vtables and template instantiations will be discarded automatically.

Return to the GCC Installation page