Download MinGW-w64 - for 32 and 64 bit Windows for free. A complete runtime environment for gcc. The mingw-w64 project is a complete runtime environment for gcc to support binaries native to Windows 64-bit and 32-bit operating systems. Windows version of the free open source GCC (GNU Compiler Collection) compiler for C and C (and other languages like Objective-C, Fortran, D). This is a standalone personal build, which means this download offers a complete compiler environment for Windows. Code Blocks is an excellent programming option for C. It consists of an open source, multiplatform integrated development environment that supports using multiple compilers, among which are: GCC (MingW / GNU GCC), MSVC, Digital Mars, Borland C 5.5 and Open Watcom. The default compiler that this Code Blocks package comes with is MinGW.
If you work on a Mac OS X 10.9 Mavericks or later, you will run into the problem of Eclipse refusing to interactively debug problems that otherwise build and run fine: An attempt to start a debugging session by selecting Run
Debug from the menu will result in Eclipse complaining that an
Debug from the menu will result in Eclipse complaining that an
Error with command: gdb --versionhas occurred.
The problem is caused by Apple switching away from GDB, the GNU debugger, to LLDB, the LLVM debugger, in their Xcode toolchain (along with the transition from GCC to Clang). Unfortunately, Eclipse is not capable of communicating with any debugger other than GDB (yet). Here is a step-by-step guide for installing and configuring GDB.
Installing GDB
As with GCC, the easiest way to install GDB is through Homebrew. In a Terminal window, run the command
brew install gdb
, and wait for it to complete. (As usual, it may ask for your password.) Now, we need to code-sign the GDB executable, so it will be allowed to control other processes, as necessary for a debugger. For that, we will first create a new certificate in Keychain.
Creating a Certificate
Open the Keychain Access application (can be found in Applications/Utilities directory or through Spotlight). Select Certificate Assistant
Create a Certificate in the application menu (Keychain Access). An assistant window will appear for guiding you through the process.
Create a Certificate in the application menu (Keychain Access). An assistant window will appear for guiding you through the process.
- First, you will be asked for the name and type of the certificate. You may choose the name arbitrarily, but to simplify its future use in command line, prefer names without spaces or other fancy characters, e.g.,
gdbcert
. - Make sure that Identity Type is set to Self Signed Root, change Certificate Type to Code Signing, check the Let me override defaults checkbox, and click Continue. Click Continue again in the popup prompt warning about the certificate being self-signed.
- On the next page, leave Security Number to be 1, and set Validity Period to a large enough number of days to cover the duration of the class or more, say, 365. (Certificates cannot last forever; the maximum validity period is 20 years.)
- Then click Continue once again, and keep doing so to skip the next six screens until you see the one entitled Specify a Location For The Certificate. For the only property, Keychain, choose System from the drop-down list. Lastly, click Create, type in your password, if prompted, and click Done.
- Back in the main window, choose the System keychain in the sidebar on the left, and select the newly created certificate from the list. Open the context menu and select Get Info. In the information window that will appear, expand the Trust section and set the Code Signing property to Always Trust. Close this window (you may be asked for your password), and quit Keychain Access.
Signing GDB
Our new certificate is now ready to be used. In order to make it immediately available for signing, we need to restart the Taskgate access-control service. You can use Activity Monitor to do this (also found in Applications/Utilities). Open it and filter the list of processes by typing
All Processes is checked.)
taskgated
in the search field in the toolbar. (If you cannot find it, make sure the menu item ViewAll Processes is checked.)
There should be exactly one process left in the list. Highlight it, then select View
Quit Process from the menu, and click Quit in the popup prompt. The Taskgate process will be terminated and, consequently, should disappear from the list. In a few seconds, it will be restarted by the system and should reappear in the list. Please wait for this to happen (it may take up to a minute or two, at worst).
Quit Process from the menu, and click Quit in the popup prompt. The Taskgate process will be terminated and, consequently, should disappear from the list. In a few seconds, it will be restarted by the system and should reappear in the list. Please wait for this to happen (it may take up to a minute or two, at worst).
Finally, in a Terminal window, run
codesign -s gdbcert /usr/local/bin/gdb
(if you named your certificate differently, replace gdbcert
with its name here). Once again, you will be prompted for you username and password. If the command does not produce any output, then GDB is successfully signed. Configuring Eclipse
The only thing left to do is to point Eclipse to the GDB executable. Open Eclipse
Preferences from the main menu (not to be confused with Project Preferences). In the tree of options listed in the sidebar, navigate to C/C++
Debug
GDB, and set the GDB debugger field to
Preferences from the main menu (not to be confused with Project Preferences). In the tree of options listed in the sidebar, navigate to C/C++
Debug
GDB, and set the GDB debugger field to
/usr/local/bin/gdb
. If there is no GDB section in the C/C++
Debug subtree, close the preferences window, and try to first start a debugging session for any project that you can already run without problems. You can do it by either clicking the Debug button on the toolbar, or selecting Run
Debug from the main menu. This attempt will, of course, fail with an error message about the
Debug
GDB settings to appear in the preferences.
Debug subtree, close the preferences window, and try to first start a debugging session for any project that you can already run without problems. You can do it by either clicking the Debug button on the toolbar, or selecting Run
Debug from the main menu. This attempt will, of course, fail with an error message about the
gdb
command, but it will force the said C/C++Debug
GDB settings to appear in the preferences.
This will change the GDB executable for new projects; for all existing ones (that you are going to use debugging for), you will need to manually update their debug configurations. To do that, select Run
Debug Configurations from the menu. In the window that appears, one after another, select every project under the C++ Application section in the sidebar. For each of them, open the Debugger tab, set the GDB debugger field to the same path
Debug Configurations from the menu. In the window that appears, one after another, select every project under the C++ Application section in the sidebar. For each of them, open the Debugger tab, set the GDB debugger field to the same path
/usr/local/bin/gdb
, and click the Apply button. After repeating this change for all listed projects, click Close. If the above steps do not solve the issue on your machine, or you encounter a problem while following them, please do not hesitate to come to one of the upcoming common labs for help.
Please read this document carefully before installing theGNU Compiler Collection on your machine.
Note that this list of install notes is not a list of supportedhosts or targets. Not all supported hosts and targets are listedhere, only the ones that require host-specific or target-specificinformation have to.
- all ELF targets (SVR4, Solaris 2, etc.)
aarch64*-*-*
Binutils pre 2.24 does not have support for selecting -mabi anddoes not support ILP32. If it is used to build GCC 4.9 or later, GCC willnot support option -mabi=ilp32.
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 bydefault 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 bydefault. 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 atlink time. Enabling the workaround will cause GCC to pass the relevant optionto 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 bydefault at configure time use the --enable-standard-branch-protectionoption. This is equivalent to having -mbranch-protection=standardduring compilation. This can be explicitly disabled during compilation bypassing the -mbranch-protection=none option which turns off alltypes of branch protections. Conversely,--disable-standard-branch-protection will disable both theprotections by default. This mechanism is turned off by default if neitherof the options are given at configure time.
alpha*-*-*
This section contains general configuration information for allAlpha-based platforms using ELF. In addition to reading thissection, please read all other sections that match your target.
amd64-*-solaris2*
This is a synonym for ‘x86_64-*-solaris2*’.
amdgcn-*-amdhsa
AMD GCN GPU target.
Instead of GNU Binutils, you will need to install LLVM 6, or later, and copybin/llvm-mc to amdgcn-amdhsa/bin/as,bin/lld to amdgcn-amdhsa/bin/ld,bin/llvm-nm to amdgcn-amdhsa/bin/nm, andbin/llvm-ar to both bin/amdgcn-amdhsa-ar andbin/amdgcn-amdhsa-ranlib.
Use Newlib (2019-01-16, or newer).
To run the binaries, install the HSA Runtime from theROCm Platform, and uselibexec/gcc/amdhsa-amdhsa/version/gcn-run to launch themon 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 theGNAT 4.6, 4.9 or 5 release branches are known to succeed.avr
ATMEL AVR-family micro controllers. These are used in embeddedapplications. There are no standard Unix configurations.See “AVR Options” in the main manualfor the list of supported MCU types.
Use ‘configure --target=avr --enable-languages='c'’ to configure GCC.
Further installation notes and other useful information about AVR toolscan also be obtained from:
The following error:
indicates that you should upgrade to a newer version of the binutils.
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/.
CR16
The CR16 CompactRISC architecture is a 16-bit architecture. Thisarchitecture is used in embedded applications.
See “CR16 Options” in the main manual for a list of CR16-specific options.
Use ‘configure --target=cr16-elf --enable-languages=c,c++’ to configureGCC for building a CR16 elf cross-compiler.
Use ‘configure --target=cr16-uclinux --enable-languages=c,c++’ toconfigure GCC for building a CR16 uclinux cross-compiler.
CRIS
CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chipseries. These are used in embedded applications.
See “CRIS Options” in the main manualfor a list of CRIS-specific options.
There are a few different CRIS targets:
cris-axis-elf
Mainly for monolithic embedded systems. Includes a multilib for the‘v10’ core used in ‘ETRAX 100 LX’.
cris-axis-linux-gnu
A GNU/Linux port for the CRIS architecture, currently targeting‘ETRAX 100 LX’ by default.
Pre-packaged tools can be obtained fromftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/. Moreinformation about this platform is available athttp://developer.axis.com/.
DOS
Please have a look at the binaries page.
You cannot install GCC by itself on MSDOS; it will not compile underany MSDOS compiler except itself. You need to get the completecompilation 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*
Support for FreeBSD 1 was discontinued in GCC 3.2. Support forFreeBSD 2 (and any mutant a.out variants of FreeBSD 3) wasdiscontinued in GCC 4.0.
In order to better utilize FreeBSD base system functionality and matchthe configuration of the system compiler, GCC 4.5 and above as well asGCC 4.4 past 2010-06-20 leverage SSP support in libc (which is presenton FreeBSD 7 or later) and the use of
__cxa_atexit
by default(on FreeBSD 6 or later). The use of dl_iterate_phdr
insidelibgcc_s.so.1 and boehm-gc (on FreeBSD 7 or later) is enabledby GCC 4.5 and above.We support FreeBSD using the ELF file format with DWARF 2 debuggingfor all CPU architectures. You may use -gstabs instead of-g, if you really want the old debugging format. There areno known issues with mixing object files and libraries with differentdebugging formats. Otherwise, this release of GCC should now matchmore of the configuration used in the stock FreeBSD configuration ofGCC. In particular, --enable-threads is now configured bydefault. However, as a general user, do not attempt to replace thesystem compiler with this release. Known to bootstrap and check withgood results on FreeBSD 7.2-STABLE. In the past, known to bootstrapand check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4,4.5, 4.8, 4.9 and 5-CURRENT.
The version of binutils installed in /usr/bin probably workswith this release of GCC. Bootstrapping against the latest GNUbinutils and/or the version found in /usr/ports/devel/binutils hasbeen known to enable additional features and improve overall testsuiteresults. However, it is currently known that boehm-gc may not configureproperly on FreeBSD prior to the FreeBSD 7.0 release with GNU binutilsafter 2.16.1.
ft32-*-elf
The FT32 processor.This configuration is intended for embedded systems.
h8300-hms
Renesas H8/300 series of processors.
Please have a look at the binaries page.
The calling convention and structure layout has changed in release 2.6.All code must be recompiled. The calling convention now passes thefirst three arguments in function calls in registers. Structures are nolonger a multiple of 2 bytes.
hppa*-hp-hpux*
Support for HP-UX version 9 and older was discontinued in GCC 3.4.
We require using gas/binutils on all hppa platforms. Version 2.19 orlater is recommended.
It may be helpful to configure GCC with the--with-gnu-as and--with-as=… options to ensure that GCC can find GAS.
The HP assembler should not be used with GCC. It is rarely tested and maynot work. It shouldn’t be used with any languages other than C due to itsmany limitations.
Specifically, -g does not work (HP-UX uses a peculiar debuggingformat which GCC does not know about). It also inserts timestampsinto each object file it creates, causing the 3-stage comparison test tofail during a bootstrap. You should be able to continue by saying‘make all-host all-target’ after getting the failure from ‘make’.
Various GCC features are not supported. For example, it does not support weaksymbols or alias definitions. As a result, explicit template instantiationsare required when using C++. This makes it difficult if not impossible tobuild many C++ applications.
There are two default scheduling models for instructions. These arePROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-riscarchitecture specified for the target machine when configuring.PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected whenthe target is a ‘hppa1*’ machine.
The PROCESSOR_8000 model is not well suited to older processors. Thus,it is important to completely specify the machine architecture whenconfiguring if you want a model other than PROCESSOR_8000. The macroTARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a differentdefault scheduling model is desired.
As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later.This namespace change might cause problems when bootstrapping withan earlier version of GCC or the HP compiler as essentially the samenamespace is required for an entire build. This problem can be avoidedin a number of ways. With HP cc,
UNIX_STD
can be set to ‘95’or ‘98’. Another way is to add an appropriate set of predefinesto CC
. The description for the munix= option containsa list of the predefines used with each standard.More specific information to ‘hppa*-hp-hpux*’ targets follows.
hppa*-hp-hpux10
For hpux10.20, we highly recommend you pick up the latest sed patch
PHCO_19798
from HP.The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces areused for one-only code and data. This resolves many of the previousproblems in using C++ on this target. However, the ABI is not compatiblewith the one implemented under HP-UX 11 using secondary definitions.
hppa*-hp-hpux11
GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannotbe used to compile GCC 3.0 and up.
The libffi library haven’t been ported to 64-bit HP-UX and doesn’t build.
Refer to binaries for information about obtainingprecompiled GCC binaries for HP-UX. Precompiled binaries must be obtainedto build the Ada language as it cannot be bootstrapped using C. Ada isonly available for the 32-bit PA-RISC runtime.
Starting with GCC 3.4 an ISO C compiler is required to bootstrap. Thebundled compiler supports only traditional C; you will need either HP’sunbundled compiler, or a binary distribution of GCC.
It is possible to build GCC 3.3 starting with the bundled HP compiler,but the process requires several steps. GCC 3.3 can then be used tobuild later versions.
There are several possible approaches to building the distribution.Binutils can be built first using the HP tools. Then, the GCCdistribution can be built. The second approach is to build GCCfirst using the HP tools, then build binutils, then rebuild GCC.There have been problems with various binary distributions, so itis best not to start from a binary distribution.
On 64-bit capable systems, there are two distinct targets. Differentinstallation prefixes must be used if both are to be installed onthe same system. The ‘hppa[1-2]*-hp-hpux11*’ target generates codefor the 32-bit PA-RISC runtime architecture and uses the HP linker.The ‘hppa64-hp-hpux11*’ target generates 64-bit code for thePA-RISC 2.0 architecture.
The script config.guess now selects the target type based on the compilerdetected during configuration. You must define
PATH
or CC
sothat configure finds an appropriate compiler for the initial bootstrap.When CC
is used, the definition should contain the options that areneeded whenever CC
is used.Specifically, options that determine the runtime architecture must bein
CC
to correctly select the target for the build. It is alsoconvenient to place many other compiler options in CC
. For example,CC='cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE'
can be used to bootstrap the GCC 3.3 branch with the HP compiler in64-bit K&R/bundled mode. The +DA2.0W option will result inthe automatic selection of the ‘hppa64-hp-hpux11*’ target. Themacro definition table of cpp needs to be increased for a successfulbuild with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need tobe defined when building with the bundled compiler, or when using the-Ac option. These defines aren’t necessary with -Ae.It is best to explicitly configure the ‘hppa64-hp-hpux11*’ targetwith the --with-ld=… option. This overrides the standardsearch for ld. The two linkers supported on this target require differentcommands. The default linker is determined during configuration. As aresult, it’s not possible to switch linkers in the middle of a GCC build.This has been reported to sometimes occur in unified builds of binutilsand GCC.
A recent linker patch must be installed for the correct operation ofGCC 3.3 and later.
PHSS_26559
and PHSS_24304
are theoldest linker patches that are known to work. They are for HP-UX11.00 and 11.11, respectively. PHSS_24303
, the companion toPHSS_24304
, might be usable but it hasn’t been tested. Thesepatches have been superseded. Consult the HP patch database to obtainthe currently recommended linker patch for your system.The patches are necessary for the support of weak symbols on the32-bit port, and for the running of initializers and finalizers. Weaksymbols are implemented using SOM secondary definition symbols. Priorto HP-UX 11, there are bugs in the linker support for secondary symbols.The patches correct a problem of linker core dumps creating sharedlibraries containing secondary symbols, as well as various otherlinking issues involving secondary symbols.
GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities torun initializers and finalizers on the 64-bit port. The 32-bit portuses the linker +init and +fini options for the samepurpose. The patches correct various problems with the +init/+finioptions, including program core dumps. Binutils 2.14 corrects aproblem on the 64-bit port resulting from HP’s non-standard use ofthe .init and .fini sections for array initializers and finalizers.
Although the HP and GNU linkers are both supported for the‘hppa64-hp-hpux11*’ target, it is strongly recommended that theHP linker be used for link editing on this target.
At this time, the GNU linker does not support the creation of longbranch stubs. As a result, it cannot successfully link binariescontaining branch offsets larger than 8 megabytes. In addition,there are problems linking shared libraries, linking executableswith -static, and with dwarf2 unwind and exception support.It also doesn’t provide stubs for internal calls to global functionsin shared libraries, so these calls cannot be overloaded.
The HP dynamic loader does not support GNU symbol versioning, so symbolversioning is not supported. It may be necessary to disable symbolversioning with --disable-symvers when using GNU ld.
POSIX threads are the default. The optional DCE thread library is notsupported, so --enable-threads=dce does not work.
*-*-linux-gnu
Versions of libstdc++-v3 starting with 3.2.1 require bug fixes presentin glibc 2.2.5 and later. More information is available in thelibstdc++-v3 documentation.
i?86-*-linux*
As of GCC 3.3, binutils 2.13.1 or later is required for this platform.See bug 10877 for more information.
If you receive Signal 11 errors when building on GNU/Linux, then it ispossible you have a hardware problem. Further information on this can befound on www.bitwizard.nl.
i?86-*-solaris2*
Use this for Solaris 11.3 or later on x86 and x86-64 systems. Startingwith GCC 4.7, there is also a 64-bit ‘amd64-*-solaris2*’ or‘x86_64-*-solaris2*’ configuration that corresponds to‘sparcv9-sun-solaris2*’.
It is recommended that you configure GCC to use the GNU assembler. Theversions included in Solaris 11.3, from GNU binutils 2.23.1 ornewer (available as /usr/bin/gas and/usr/gnu/bin/as), work fine. The current version, from GNUbinutils 2.34, is known to work. Recent versions of the Solaris assembler in/usr/bin/as work almost as well, though.
For linking, the Solaris linker is preferred. If you want to use the GNUlinker instead, the version in Solaris 11.3, from GNU binutils 2.23.1 ornewer (in /usr/gnu/bin/ld and /usr/bin/gld), works,as does the latest version, from GNU binutils 2.34.
To use GNU
as
, configure with the options--with-gnu-as --with-as=/usr/gnu/bin/as. It may be necessaryto configure with --without-gnu-ld --with-ld=/usr/ccs/bin/ld toguarantee use of Solaris ld
.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 orlater.
None of the following versions of GCC has an ABI that is compatiblewith any of the other versions in this list, with the exception thatRed Hat 2.96 and Trillian 000171 are compatible with each other:3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.This primarily affects C++ programs and programs that create shared libraries.GCC 3.1 or later is recommended for compiling linux, the kernel.As of version 3.1 GCC is believed to be fully ABI compliant, and hence nomore major ABI changes are expected.
ia64-*-hpux*
Building GCC on this target requires the GNU Assembler. The bundled HPassembler will not work. To prevent GCC from using the wrong assembler,the option --with-gnu-as may be necessary.
The GCC libunwind library has not been ported to HPUX. This means that forGCC versions 3.2.3 and earlier, --enable-libunwind-exceptionsis required to build GCC. For GCC 3.3 and later, this is the default.For gcc 3.4.3 and later, --enable-libunwind-exceptions isremoved and the system libunwind library will always be used.
*-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 withprocess 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++ / xlCcannot bootstrap GCC. xlc can bootstrap an older version of GCC andG++ can bootstrap recent releases of GCC.
GCC can bootstrap with recent versions of IBM XLC, but bootstrappingwith an earlier release of GCC is recommended. Bootstrapping with XLCrequires a larger data segment, which can be enabled through theLDR_CNTRL environment variable, e.g.,
One can start with a pre-compiled version of GCC to build fromsources. One may delete GCC’s “fixed” header files when startingwith 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.,and then proceed as described in the buildinstructions, where we strongly recommend specifying an absolute pathto 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 librariesrequired by gfortran must be 32-bit libraries. Building GMP and MPFRas static archive libraries works better than shared libraries.
Errors involving
alloca
when building GCC generally are dueto an incorrect definition of CC
in the Makefile or mixing filescompiled with the native C compiler and GCC. During the stage1 phase ofthe build, the native AIX compiler must be invoked as cc
(not xlc
). Once configure
has been informed ofxlc
, one needs to use ‘make distclean’ to remove theconfigure cache files and ensure that CC
environment variabledoes not provide a definition that will confuse configure
.If this error occurs during stage2 or later, then the problem most likelyis the version of Make (see above).The native
as
and ld
are recommended forbootstrapping on AIX. The GNU Assembler, GNU Linker, and GNUBinutils version 2.20 is the minimum level that supports bootstrap onAIX 5. The GNU Assembler has not been updated to support AIX 6 orAIX 7. The native AIX tools do interoperate with GCC.AIX 7.1 added partial support for DWARF debugging, but full supportrequires AIX 7.1 TL03 SP7 that supports additional DWARF sections andfixes a bug in the assembler. AIX 7.1 TL03 SP5 distributed a versionof libm.a missing important symbols; a fix for IV77796 will beincluded in SP6.
AIX 5.3 TL10, AIX 6.1 TL05 and AIX 7.1 TL00 introduced an AIXassembler change that sometimes produces corrupt assembly filescausing AIX linker errors. The bug breaks GCC bootstrap on AIX andcan cause compilation failures with existing GCC installations. AnAIX iFix for AIX 5.3 is available (APAR IZ98385 for AIX 5.3 TL10, APARIZ98477 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 bugAPAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires afix for another AIX Assembler bug and a co-dependent AIX Archiver fixreferenced as APAR IY53606 (AIX 5.2) or as APAR IY54774 (AIX 5.1)
‘libstdc++’ in GCC 3.4 increments the major version number of theshared object and GCC installation places the libstdc++.ashared library in a common location which will overwrite the and GCC3.3 version of the shared library. Applications either need to bere-linked against the new shared library or the GCC 3.1 and GCC 3.3versions of the ‘libstdc++’ shared object needs to be availableto the AIX runtime loader. The GCC 3.1 ‘libstdc++.so.4’, ifpresent, and GCC 3.3 ‘libstdc++.so.5’ shared objects can beinstalled for runtime dynamic loading using the following steps to setthe ‘F_LOADONLY’ flag in the shared object for eachmultilib libstdc++.a installed:
Extract the shared objects from the currently installedlibstdc++.a archive:
Enable the ‘F_LOADONLY’ flag so that the shared object will beavailable for runtime dynamic loading, but not linking:
Archive the runtime-only shared object in the GCC 3.4libstdc++.a archive:
Eventually, the--with-aix-soname=svr4configure option may drop the need for this procedure for libraries thatsupport it.
Linking executables and shared libraries may produce warnings ofduplicate symbols. The assembly files generated by GCC for AIX alwayshave included multiple symbol definitions for certain global variableand function declarations in the original program. The warnings shouldnot prevent the linker from producing a correct library or runnableexecutable.
AIX 4.3 utilizes a “large format” archive to support both 32-bit and64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1to parse archive libraries did not handle the new format correctly.These routines are used by GCC and result in error messages duringlinking such as “not a COFF file”. The version of the routines shippedwith AIX 4.3.1 should work for a 32-bit environment. The -goption of the archive command may be used to create archives of 32-bitobjects using the original “small format”. A correct version of theroutines is shipped with AIX 4.3.2 and above.
Some versions of the AIX binder (linker) can fail with a relocationoverflow severe error when the -bbigtoc option is used to linkGCC-produced object files into an executable that overflows the TOC. A fixfor APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) isavailable from IBM Customer Support and from itstechsupport.services.ibm.comwebsite as PTF U455193.
The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump corewith a segmentation fault when invoked by any version of GCC. A fix forAPAR IX87327 is available from IBM Customer Support and from itstechsupport.services.ibm.comwebsite 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 objectfiles. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILSTO ASSEMBLE/BIND) is available from IBM Customer Support and from itstechsupport.services.ibm.comwebsite as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
AIX provides National Language Support (NLS). Compilers and assemblersuse NLS to support locale-specific representations of various dataformats including floating-point numbers (e.g., ‘.’ vs ‘,’ forseparating decimal fractions). There have been problems reported whereGCC does not produce the same floating-point formats that the assemblerexpects. If one encounters this problem, set the
LANG
environment variable to ‘C’ or ‘En_US’.A default can be specified with the -mcpu=cpu_typeswitch and using the configure option --with-cpu-cpu_type.
iq2000-*-elf
Vitesse IQ2000 processors. These are used in embeddedapplications. 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.
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 onlyneed the M680x0 libraries, you can omit the ColdFire ones by passing--with-arch=m68k to
configure
. Alternatively, youcan omit the M680x0 libraries by passing --with-arch=cf toconfigure
. These targets default to 5206 or 5475 code asappropriate for the target system whenconfigured with --with-arch=cf and 68020 code otherwise.The ‘m68k-*-netbsd’ and‘m68k-*-openbsd’ targets also support the --with-archoption. 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 configuringwith --with-cpu=target. This target can eitherbe 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 gpsections for all it’s [sic] sectons [sic]”, don’t worry about it. Thishappens whenever you use GAS with the MIPS linker, but there is notreally anything wrong, and it is okay to use the output file. You canstop such warnings by installing the GNU linker.
It would be nice to extend GAS to produce the gp tables, but they areoptional, and there should not be a warning about their absence.
The libstdc++ atomic locking routines for MIPS targets requires MIPS IIand later. A patch went in just after the GCC 3.3 release tomake ‘mips*-*-*’ use the generic implementation instead. You can alsoconfigure for ‘mipsel-elf’ as a workaround. The‘mips*-*-linux*’ target continues to use the MIPS II routines. Morework on this is expected in future releases.
The built-in
__sync_*
functions are available on MIPS II andlater 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 aremissing, the default for ‘mips*-*-linux*’ targets is--with-llsc. The --with-llsc and--without-llsc configure options may be overridden at compiletime by passing the -mllsc or -mno-llsc options tothe compiler.MIPS systems check for division by zero (unless-mno-check-zero-division is passed to the compiler) bygenerating either a conditional trap or a break instruction. Usingtrap results in smaller code, but is only supported on MIPS II andlater. Also, some versions of the Linux kernel have a bug thatprevents trap from generating the proper signal (
SIGFPE
). To enablethe use of break, use the --with-divide=breaksconfigure
option when configuring GCC. The default is touse 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 GCCfeatures enabled by default.
‘msp430-*-elfbare’ is tuned for a bare-metal environment, and disablesfeatures related to shared libraries and other functionality not used forthis device. This reduces code and data usage of the GCC libraries, resultingin 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 installnvptx-tools.Tell GCC where to find it:--with-build-time-tools=[install-nvptx-tools]/nvptx-none/bin.
You will need newlib 3.0 git revisioncd31fbb2aea25f94d7ecedc9db16dfc87ab0c316 or later. It can beautomatically built together with GCC. For this, add a symbolic linkto nvptx-newlib’s newlib directory to the directory containingthe GCC sources.
Use the --disable-sjlj-exceptions and--enable-newlib-io-long-long options when configuring.
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_typeswitch 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. Toolbinaries are available athttps://opensource.apple.com.
This version of GCC requires at least cctools-590.36. Thecctools-590.36 package referenced fromhttp://gcc.gnu.org/ml/gcc/2006-03/msg00507.html will not workon 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 thePSIM 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 underthe 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.30 release.
riscv32-*-linux
The RISC-V RV32 instruction set running GNU/Linux.This (and all other RISC-V) targets require the binutils 2.30 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.30 release.
riscv64-*-linux
The RISC-V RV64 instruction set running GNU/Linux.This (and all other RISC-V) targets require the binutils 2.30 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 issupported as cross-compilation target only.
*-*-solaris2*
Support for Solaris 10 has been removed in GCC 10. Support for Solaris9 has been removed in GCC 5. Support for Solaris 8 has been removed inGCC 4.8. Support for Solaris 7 has been removed in GCC 4.6.
Solaris 11.3 provides GCC 4.5.2, 4.7.3, and 4.8.2 as
/usr/gcc/4.5/bin/gcc
or similar. Newer Solaris versionsprovide one or more of GCC 5, 7, and 9. Alternatively,you can install a pre-built GCC to bootstrap and install GCC. See thebinaries page for details.The Solaris 2
/bin/sh
will often fail to configure‘libstdc++-v3’. We therefore recommend using thefollowing initial sequence of commandsand proceed as described in the configure instructions.In addition we strongly recommend specifying an absolute path to invoke
srcdir/configure
.In Solaris 11, you need to check for
system/header
,system/linker
, and developer/assembler
packages.Trying to use the linker and other tools in/usr/ucb to install GCC has been observed to cause trouble.For example, the linker may hang indefinitely. The fix is to remove/usr/ucb from your
PATH
.The build process works more smoothly with the legacy Solaris tools so, if youhave /usr/xpg4/bin in your
PATH
, we recommend that you place/usr/bin before /usr/xpg4/bin for the duration of the build.We recommend the use of the Solaris assembler or the GNU assembler, inconjunction with the Solaris linker. The GNU
as
versions included in Solaris 11.3,from GNU binutils 2.23.1 or newer (in /usr/bin/gas and/usr/gnu/bin/as), are known to work.The current version, from GNU binutils 2.34,is known to work as well. Note that your mileage may varyif you use a combination of the GNU tools and the Solaris tools: while thecombination GNU as
+ Solaris ld
should reasonably work,the reverse combination Solaris as
+ GNU ld
may fail tobuild or cause memory corruption at runtime in some cases for C++ programs.GNU ld
usually works as well. Again, the currentversion (2.34) is known to work, but generally lacks platform specificfeatures, so better stay with Solaris ld
. To use the LTO linkerplugin (-fuse-linker-plugin) with GNU ld
, GNUbinutils must be configured with --enable-largefile.To enable symbol versioning in ‘libstdc++’ with the Solaris linker,you need to have any version of GNU
c++filt
, which is part ofGNU binutils. ‘libstdc++’ symbol versioning will be disabled if noappropriate version is found. Solaris c++filt
from the SolarisStudio compilers does not work.The versions of the GNU Multiple Precision Library (GMP), the MPFRlibrary and the MPC library bundled with Solaris 11.3 and later areusually recent enough to match GCC’s requirements. There are twocaveats:
- While the version of the GMP library in Solaris 11.3 works with GCC, youneed to configure with --with-gmp-include=/usr/include/gmp.
- The version of the MPFR libary included in Solaris 11.3 is too old; youneed to provide a more recent one.
sparc*-*-*
This section contains general configuration information for allSPARC-based platforms. In addition to reading this section, pleaseread all other sections that match your target.
Newer versions of the GNU Multiple Precision Library (GMP), the MPFRlibrary and the MPC library are known to be miscompiled by earlierversions of GCC on these platforms. We therefore recommend the useof the exact versions of these libraries listed as minimal versionsin the prerequisites.
sparc-sun-solaris2*
When GCC is configured to use GNU binutils 2.14 or later, the binariesproduced are smaller than the ones produced using Solaris native tools;this difference is quite significant for binaries containing debugginginformation.
Starting with Solaris 7, the operating system is capable of executing64-bit SPARC V9 binaries. GCC 3.1 and later properly supportsthis; the -m64 option enables 64-bit code generation.However, if all you want is code tuned for the UltraSPARC CPU, youshould try the -mtune=ultrasparc option instead, which producescode that, unlike full 64-bit code, can still run on non-UltraSPARCmachines.
When configuring the GNU Multiple Precision Library (GMP), the MPFRlibrary or the MPC library on a Solaris 7 or later system, the canonicaltarget triplet must be specified as the
build
parameter on theconfigure line. This target triplet can be obtained by invoking ./config.guess
in the toplevel source directory of GCC (andnot that of GMP or MPFR or MPC). For example on a Solaris 11 system:sparc-*-linux*
sparc64-*-solaris2*
When configuring a 64-bit-default GCC on Solaris/SPARC, you must use abuild compiler that generates 64-bit code, either by default or byspecifying ‘CC='gcc -m64' CXX='gcc-m64'’ to
configure
.Additionally, you must pass --build=sparc64-sun-solaris2.11or --build=sparcv9-sun-solaris2.11 because config.guessmisdetects this situation, which can cause build failures.When configuring the GNU Multiple Precision Library (GMP), the MPFRlibrary or the MPC library, the canonical target triplet must be specifiedas the
build
parameter on the configure line. For exampleon a Solaris 11 system:sparcv9-*-solaris2*
This is a synonym for ‘sparc64-*-solaris2*’.
c6x-*-*
The C6X family of processors. This port requires binutils-2.22 or newer.
tilegx-*-linux*
The TILE-Gx processor in little endian mode, running GNU/Linux. Thisport requires binutils-2.22 or newer.
tilegxbe-*-linux*
The TILE-Gx processor in big endian mode, running GNU/Linux. Thisport requires binutils-2.23 or newer.
tilepro-*-linux*
The TILEPro processor running GNU/Linux. This port requiresbinutils-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 thevery 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 merelya matter of writing an appropriate “configlette” (see below). We arenot interested in supporting older, a.out or COFF-based, versions ofVxWorks 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 prefixand prefix/bin. Link or copy the appropriate assembler,linker, etc. into prefix/bin, and set your PATH toinclude that directory while running both configure
andmake
.You must give
configure
the--with-headers=$WIND_BASE/target/h switch so that it canfind the VxWorks system headers. Since VxWorks is a cross compilationtarget only, you must also specify --target=target.configure
will attempt to create the directoryprefix/target/sys-include and copy files into it;make sure the user running configure
has sufficient privilegeto do so.GCC’s exception handling runtime requires a special “configlette”module, contrib/gthr_supp_vxw_5x.c. Follow the instructions inthat file to add the module to your kernel build. (Future versions ofVxWorks 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 generateboth 64-bit x86-64 and 32-bit x86 code (via the -m32 switch).
x86_64-*-solaris2*
GCC also supports the x86-64 architecture implemented by the AMD64processor (‘amd64-*-*’ is an alias for ‘x86_64-*-*’) onSolaris 10 or later. Unlike other systems, without special options abi-arch compiler is built which generates 32-bit code by default, butcan generate 64-bit x86-64 code with the -m64 switch. SinceGCC 4.7, there is also a configuration that defaults to 64-bit code, butcan generate 32-bit code with -m32. To configure and buildthis way, you have to provide all support libraries like libgmpas 64-bit code, configure with --target=x86_64-pc-solaris2.11and ‘CC=gcc -m64’.
xtensa*-*-elf
This target is intended for embedded Xtensa systems using the‘newlib’ C library. It uses ELF but does not support sharedobjects. Designed-defined instructions specified via theTensilica Instruction Extension (TIE) language are only supportedthrough inline assembly.
The Xtensa configuration information must be specified prior tobuilding GCC. The include/xtensa-config.h headerfile contains the configuration information. If you created yourown Xtensa configuration with the Xtensa Processor Generator, thedownloaded 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 ELFshared objects and the GNU C library (glibc). It also generatesposition-independent code (PIC) regardless of whether the-fpic or -fPIC options are used. In otherrespects, this target is the same as the‘xtensa*-*-elf’ target.
Microsoft Windows
![Gcc Gcc](https://a.fsdn.com/con/app/proj/gdcmac/screenshots/50496.jpg/max/max/1)
Intel 16-bit versions
The 16-bit versions of Microsoft Windows, such as Windows 3.1, are notsupported.
However, the 32-bit port has limited support for MicrosoftWindows 3.11 in the Win32s environment, as a target only. See below.
Intel 32-bit versions
The 32-bit versions of Windows, including Windows 95, Windows NT, WindowsXP, and Windows Vista, are supported by several different targetplatforms. These targets differ in which Windows subsystem they targetand which C libraries are used.
- Cygwin *-*-cygwin: Cygwin provides a user-spaceLinux API emulation layer in the Win32 subsystem.
- MinGW *-*-mingw32: MinGW is a native GCC port forthe Win32 subsystem that provides a subset of POSIX.
- MKS i386-pc-mks: NuTCracker from MKS. Seehttps://www.mkssoftware.com for more information.
Intel 64-bit versions
GCC contains support for x86-64 using the mingw-w64runtime library, available from http://mingw-w64.org/doku.php.This library should be used with the target triple x86_64-pc-mingw32.
Presently Windows for Itanium is not supported.
Windows CE
Windows CE is supported as a target only on HitachiSuperH (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. However, it doessupport the Interix subsystem. See above.
Old target names including *-*-winnt and *-*-windowsnt are no longer used.
PW32 (i386-pc-pw32) support was never completed, and the project seems tobe inactive. See http://pw32.sourceforge.net/ for more information.
UWIN support has been removed due to a lack of maintenance.
*-*-cygwin
Ports of GCC are included with theCygwin environment.
GCC will build under Cygwin without modification; it does not buildwith 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 x86cpu architecture desired; the default is i686-pc-cygwin. It should beused with as up-to-date a version of binutils as possible; use eitherthe 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 semanticsof
extern inline
in -std=c99
and -std=gnu99
modes.Older systems
GCC contains support files for many older (1980s and early1990s) Unix variants. For the most part, support for these systemshas not been deliberately removed, but it has not been maintained forseveral 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-obsoleteoption is given. Unless a maintainer steps forward, support for thesesystems will be removed from the next release of GCC.Support for old systems as hosts for GCC can cause problems if theworkarounds for compiler, library and operating system bugs affect thecleanliness or maintainability of the rest of GCC. In some cases, tobring GCC up on such a system, if still possible with current GCC, mayrequire first installing an old version of GCC which did work on thatsystem, and using it to compile a more recent GCC, to avoid bugs in thevendor compiler. Old releases of GCC 1 and GCC 2 are available in theold-releases directory on the GCC mirrorsites. Header bugs may generally be avoided using
fixincludes
, but bugs or deficiencies in libraries and theoperating system may still cause problems.Support for older systems as targets for cross-compilation is lessproblematic than support for them as hosts for GCC; if an enthusiastwishes to make such a target work again (including resurrecting any ofthe targets that never worked with GCC 2, starting from the lastversion before they were removed), patchesfollowing the usual requirements would belikely to be accepted, since they should not affect the support for moremodern targets.
For some systems, old versions of GNU binutils may also be useful,and are available from pub/binutils/old-releases onsourceware.org mirror sites.
Some of the information on specific systems above relates tosuch older systems, but much of the informationabout GCC on such systems (which may no longer be applicable tocurrent GCC) is to be found in the GCC texinfo manual.
all ELF targets (SVR4, Solaris 2, etc.)
C++ support is significantly better on ELF targets if you use theGNU linker; duplicate copies ofinlines, vtables and template instantiations will be discardedautomatically.
For questions related to the use of GCC,please consult these web pages and theGCC manuals. If that fails,the [email protected] list might help.Comments on these web pages and the development of GCC are welcome on ourdeveloper list at [email protected] of our listshave public archives.Copyright (C)Free Software Foundation, Inc.Verbatim copying and distribution of this entire article ispermitted in any medium, provided this notice is preserved.
Downloader For Mac
These pages aremaintained by the GCC team.Last modified 2020-05-07.