1 \input texinfo.tex @c -*-texinfo-*-
4 @setfilename gccinstall.info
5 @settitle Installing GCC
10 @include gcc-common.texi
12 @c Specify title for specific html page
14 @settitle Installing GCC
17 @settitle Host/Target specific installation notes for GCC
19 @ifset prerequisiteshtml
20 @settitle Prerequisites for GCC
23 @settitle Downloading GCC
26 @settitle Installing GCC: Configuration
29 @settitle Installing GCC: Building
32 @settitle Installing GCC: Testing
34 @ifset finalinstallhtml
35 @settitle Installing GCC: Final installation
38 @settitle Installing GCC: Binaries
41 @settitle Installing GCC: Old documentation
44 @settitle Installing GCC: GNU Free Documentation License
47 @c Copyright (C) 1988-2015 Free Software Foundation, Inc.
48 @c *** Converted to texinfo by Dean Wakerley, dean@wakerley.com
50 @c IMPORTANT: whenever you modify this file, run `install.texi2html' to
51 @c test the generation of HTML documents for the gcc.gnu.org web pages.
53 @c Do not use @footnote{} in this file as it breaks install.texi2html!
55 @c Include everything if we're not making html
59 @set prerequisiteshtml
70 @c Part 2 Summary Description and Copyright
72 Copyright @copyright{} 1988-2015 Free Software Foundation, Inc.
74 Permission is granted to copy, distribute and/or modify this document
75 under the terms of the GNU Free Documentation License, Version 1.3 or
76 any later version published by the Free Software Foundation; with no
77 Invariant Sections, the Front-Cover texts being (a) (see below), and
78 with the Back-Cover Texts being (b) (see below). A copy of the
79 license is included in the section entitled ``@uref{./gfdl.html,,GNU
80 Free Documentation License}''.
82 (a) The FSF's Front-Cover Text is:
86 (b) The FSF's Back-Cover Text is:
88 You have freedom to copy and modify this GNU Manual, like GNU
89 software. Copies published by the Free Software Foundation raise
90 funds for GNU development.
95 @dircategory Software development
97 * gccinstall: (gccinstall). Installing the GNU Compiler Collection.
100 @c Part 3 Titlepage and Copyright
102 @title Installing GCC
105 @c The following two commands start the copyright page.
107 @vskip 0pt plus 1filll
111 @c Part 4 Top node, Master Menu, and/or Table of Contents
114 @comment node-name, next, Previous, up
117 * Installing GCC:: This document describes the generic installation
118 procedure for GCC as well as detailing some target
119 specific installation instructions.
121 * Specific:: Host/target specific installation notes for GCC.
122 * Binaries:: Where to get pre-compiled binaries.
124 * Old:: Old installation documentation.
126 * GNU Free Documentation License:: How you can copy and share this manual.
127 * Concept Index:: This index has two entries.
135 @c Part 5 The Body of the Document
136 @c ***Installing GCC**********************************************************
138 @comment node-name, next, previous, up
139 @node Installing GCC, Binaries, , Top
143 @chapter Installing GCC
146 The latest version of this document is always available at
147 @uref{http://gcc.gnu.org/install/,,http://gcc.gnu.org/install/}.
148 It refers to the current development sources, instructions for
149 specific released versions are included with the sources.
151 This document describes the generic installation procedure for GCC as well
152 as detailing some target specific installation instructions.
154 GCC includes several components that previously were separate distributions
155 with their own installation instructions. This document supersedes all
156 package-specific installation instructions.
158 @emph{Before} starting the build/install procedure please check the
160 @ref{Specific, host/target specific installation notes}.
163 @uref{specific.html,,host/target specific installation notes}.
165 We recommend you browse the entire generic installation instructions before
168 Lists of successful builds for released versions of GCC are
169 available at @uref{http://gcc.gnu.org/buildstat.html}.
170 These lists are updated as new information becomes available.
172 The installation procedure itself is broken into five steps.
177 * Downloading the source::
180 * Testing:: (optional)
187 @uref{prerequisites.html,,Prerequisites}
189 @uref{download.html,,Downloading the source}
191 @uref{configure.html,,Configuration}
193 @uref{build.html,,Building}
195 @uref{test.html,,Testing} (optional)
197 @uref{finalinstall.html,,Final install}
201 Please note that GCC does not support @samp{make uninstall} and probably
202 won't do so in the near future as this would open a can of worms. Instead,
203 we suggest that you install GCC into a directory of its own and simply
204 remove that directory when you do not need that specific version of GCC
205 any longer, and, if shared libraries are installed there as well, no
206 more binaries exist that use them.
209 There are also some @uref{old.html,,old installation instructions},
210 which are mostly obsolete but still contain some information which has
211 not yet been merged into the main part of this manual.
219 @uref{./index.html,,Return to the GCC Installation page}
225 @c ***Prerequisites**************************************************
227 @comment node-name, next, previous, up
228 @node Prerequisites, Downloading the source, , Installing GCC
230 @ifset prerequisiteshtml
232 @chapter Prerequisites
234 @cindex Prerequisites
236 GCC requires that various tools and packages be available for use in the
237 build procedure. Modifying GCC sources requires additional tools
240 @heading Tools/packages necessary for building GCC
242 @item ISO C++98 compiler
243 Necessary to bootstrap GCC, although versions of GCC prior
244 to 4.8 also allow bootstrapping with a ISO C89 compiler and versions
245 of GCC prior to 3.4 also allow bootstrapping with a traditional
248 To build all languages in a cross-compiler or other configuration where
249 3-stage bootstrap is not performed, you need to start with an existing
250 GCC binary (version 3.4 or later) because source code for language
251 frontends other than C might use GCC extensions.
253 Note that to bootstrap GCC with versions of GCC earlier than 3.4, you
254 may need to use @option{--disable-stage1-checking}, though
255 bootstrapping the compiler with such earlier compilers is strongly
258 @item C standard library and headers
260 In order to build GCC, the C standard library and headers must be present
261 for all target variants for which target libraries will be built (and not
262 only the variant of the host C++ compiler).
264 This affects the popular @samp{x86_64-unknown-linux-gnu} platform (among
265 other multilib targets), for which 64-bit (@samp{x86_64}) and 32-bit
266 (@samp{i386}) libc headers are usually packaged separately. If you do a
267 build of a native compiler on @samp{x86_64-unknown-linux-gnu}, make sure you
268 either have the 32-bit libc developer package properly installed (the exact
269 name of the package depends on your distro) or you must build GCC as a
270 64-bit only compiler by configuring with the option
271 @option{--disable-multilib}. Otherwise, you may encounter an error such as
272 @samp{fatal error: gnu/stubs-32.h: No such file}
276 In order to build the Ada compiler (GNAT) you must already have GNAT
277 installed because portions of the Ada frontend are written in Ada (with
278 GNAT extensions.) Refer to the Ada installation instructions for more
279 specific information.
281 @item A ``working'' POSIX compatible shell, or GNU bash
283 Necessary when running @command{configure} because some
284 @command{/bin/sh} shells have bugs and may crash when configuring the
285 target libraries. In other cases, @command{/bin/sh} or @command{ksh}
286 have disastrous corner-case performance problems. This
287 can cause target @command{configure} runs to literally take days to
288 complete in some cases.
290 So on some platforms @command{/bin/ksh} is sufficient, on others it
291 isn't. See the host/target specific instructions for your platform, or
292 use @command{bash} to be sure. Then set @env{CONFIG_SHELL} in your
293 environment to your ``good'' shell prior to running
294 @command{configure}/@command{make}.
296 @command{zsh} is not a fully compliant POSIX shell and will not
297 work when configuring GCC@.
299 @item A POSIX or SVR4 awk
301 Necessary for creating some of the generated source files for GCC@.
302 If in doubt, use a recent GNU awk version, as some of the older ones
303 are broken. GNU awk version 3.1.5 is known to work.
307 Necessary in some circumstances, optional in others. See the
308 host/target specific instructions for your platform for the exact
311 @item gzip version 1.2.4 (or later) or
312 @itemx bzip2 version 1.0.2 (or later)
314 Necessary to uncompress GCC @command{tar} files when source code is
315 obtained via FTP mirror sites.
317 @item GNU make version 3.80 (or later)
319 You must have GNU make installed to build GCC@.
321 @item GNU tar version 1.14 (or later)
323 Necessary (only on some platforms) to untar the source code. Many
324 systems' @command{tar} programs will also work, only try GNU
325 @command{tar} if you have problems.
327 @item Perl version 5.6.1 (or later)
329 Necessary when targeting Darwin, building @samp{libstdc++},
330 and not using @option{--disable-symvers}.
331 Necessary when targeting Solaris 2 with Sun @command{ld} and not using
332 @option{--disable-symvers}. The bundled @command{perl} in Solaris@tie{}8
335 Necessary when regenerating @file{Makefile} dependencies in libiberty.
336 Necessary when regenerating @file{libiberty/functions.texi}.
337 Necessary when generating manpages from Texinfo manuals.
338 Used by various scripts to generate some files included in SVN (mainly
339 Unicode-related and rarely changing) from source tables.
341 @item @command{jar}, or InfoZIP (@command{zip} and @command{unzip})
343 Necessary to build libgcj, the GCJ runtime.
347 Several support libraries are necessary to build GCC, some are required,
348 others optional. While any sufficiently new version of required tools
349 usually work, library requirements are generally stricter. Newer
350 versions may work in some cases, but it's safer to use the exact
351 versions documented. We appreciate bug reports about problems with
352 newer versions, though. If your OS vendor provides packages for the
353 support libraries then using those packages may be the simplest way to
354 install the libraries.
357 @item GNU Multiple Precision Library (GMP) version 4.3.2 (or later)
359 Necessary to build GCC@. If a GMP source distribution is found in a
360 subdirectory of your GCC sources named @file{gmp}, it will be built
361 together with GCC. Alternatively, if GMP is already installed but it
362 is not in your library search path, you will have to configure with the
363 @option{--with-gmp} configure option. See also @option{--with-gmp-lib}
364 and @option{--with-gmp-include}.
366 @item MPFR Library version 2.4.2 (or later)
368 Necessary to build GCC@. It can be downloaded from
369 @uref{http://www.mpfr.org/}. If an MPFR source distribution is found
370 in a subdirectory of your GCC sources named @file{mpfr}, it will be
371 built together with GCC. Alternatively, if MPFR is already installed
372 but it is not in your default library search path, the
373 @option{--with-mpfr} configure option should be used. See also
374 @option{--with-mpfr-lib} and @option{--with-mpfr-include}.
376 @item MPC Library version 0.8.1 (or later)
378 Necessary to build GCC@. It can be downloaded from
379 @uref{http://www.multiprecision.org/}. If an MPC source distribution
380 is found in a subdirectory of your GCC sources named @file{mpc}, it
381 will be built together with GCC. Alternatively, if MPC is already
382 installed but it is not in your default library search path, the
383 @option{--with-mpc} configure option should be used. See also
384 @option{--with-mpc-lib} and @option{--with-mpc-include}.
386 @item ISL Library version 0.14 (or 0.12.2)
388 Necessary to build GCC with the Graphite loop optimizations.
389 It can be downloaded from @uref{ftp://gcc.gnu.org/pub/gcc/infrastructure/}
390 as @file{isl-0.12.2.tar.bz2}. If an ISL source distribution is found
391 in a subdirectory of your GCC sources named @file{isl}, it will be
392 built together with GCC. Alternatively, the @option{--with-isl} configure
393 option should be used if ISL is not installed in your default library
398 @heading Tools/packages necessary for modifying GCC
400 @item autoconf version 2.64
401 @itemx GNU m4 version 1.4.6 (or later)
403 Necessary when modifying @file{configure.ac}, @file{aclocal.m4}, etc.@:
404 to regenerate @file{configure} and @file{config.in} files.
406 @item automake version 1.11.6
408 Necessary when modifying a @file{Makefile.am} file to regenerate its
409 associated @file{Makefile.in}.
411 Much of GCC does not use automake, so directly edit the @file{Makefile.in}
412 file. Specifically this applies to the @file{gcc}, @file{intl},
413 @file{libcpp}, @file{libiberty}, @file{libobjc} directories as well
414 as any of their subdirectories.
416 For directories that use automake, GCC requires the latest release in
417 the 1.11 series, which is currently 1.11.6. When regenerating a directory
418 to a newer version, please update all the directories using an older 1.11
419 to the latest released version.
421 @item gettext version 0.14.5 (or later)
423 Needed to regenerate @file{gcc.pot}.
425 @item gperf version 2.7.2 (or later)
427 Necessary when modifying @command{gperf} input files, e.g.@:
428 @file{gcc/cp/cfns.gperf} to regenerate its associated header file, e.g.@:
429 @file{gcc/cp/cfns.h}.
435 Necessary to run the GCC testsuite; see the section on testing for
436 details. Tcl 8.6 has a known regression in RE pattern handling that
437 make parts of the testsuite fail. See
438 @uref{http://core.tcl.tk/tcl/tktview/267b7e2334ee2e9de34c4b00d6e72e2f1997085f}
439 for more information. This bug has been fixed in 8.6.1.
441 @item autogen version 5.5.4 (or later) and
442 @itemx guile version 1.4.1 (or later)
444 Necessary to regenerate @file{fixinc/fixincl.x} from
445 @file{fixinc/inclhack.def} and @file{fixinc/*.tpl}.
447 Necessary to run @samp{make check} for @file{fixinc}.
449 Necessary to regenerate the top level @file{Makefile.in} file from
450 @file{Makefile.tpl} and @file{Makefile.def}.
452 @item Flex version 2.5.4 (or later)
454 Necessary when modifying @file{*.l} files.
456 Necessary to build GCC during development because the generated output
457 files are not included in the SVN repository. They are included in
460 @item Texinfo version 4.7 (or later)
462 Necessary for running @command{makeinfo} when modifying @file{*.texi}
463 files to test your changes.
465 Necessary for running @command{make dvi} or @command{make pdf} to
466 create printable documentation in DVI or PDF format. Texinfo version
467 4.8 or later is required for @command{make pdf}.
469 Necessary to build GCC documentation during development because the
470 generated output files are not included in the SVN repository. They are
471 included in releases.
473 @item @TeX{} (any working version)
475 Necessary for running @command{texi2dvi} and @command{texi2pdf}, which
476 are used when running @command{make dvi} or @command{make pdf} to create
477 DVI or PDF files, respectively.
479 @item Sphinx version 1.0 (or later)
481 Necessary to regenerate @file{jit/docs/_build/texinfo} from the @file{.rst}
482 files in the directories below @file{jit/docs}.
484 @item SVN (any version)
485 @itemx SSH (any version)
487 Necessary to access the SVN repository. Public releases and weekly
488 snapshots of the development sources are also available via FTP@.
490 @item GNU diffutils version 2.7 (or later)
492 Useful when submitting patches for the GCC source code.
494 @item patch version 2.5.4 (or later)
496 Necessary when applying patches, created with @command{diff}, to one's
502 If you wish to modify @file{.java} files in libjava, you will need to
503 configure with @option{--enable-java-maintainer-mode}, and you will need
504 to have executables named @command{ecj1} and @command{gjavah} in your path.
505 The @command{ecj1} executable should run the Eclipse Java compiler via
506 the GCC-specific entry point. You can download a suitable jar from
507 @uref{ftp://sourceware.org/pub/java/}, or by running the script
508 @command{contrib/download_ecj}.
510 @item antlr.jar version 2.7.1 (or later)
513 If you wish to build the @command{gjdoc} binary in libjava, you will
514 need to have an @file{antlr.jar} library available. The library is
515 searched for in system locations but can be specified with
516 @option{--with-antlr-jar=} instead. When configuring with
517 @option{--enable-java-maintainer-mode}, you will need to have one of
518 the executables named @command{cantlr}, @command{runantlr} or
519 @command{antlr} in your path.
528 @uref{./index.html,,Return to the GCC Installation page}
532 @c ***Downloading the source**************************************************
534 @comment node-name, next, previous, up
535 @node Downloading the source, Configuration, Prerequisites, Installing GCC
539 @chapter Downloading GCC
541 @cindex Downloading GCC
542 @cindex Downloading the Source
544 GCC is distributed via @uref{http://gcc.gnu.org/svn.html,,SVN} and FTP
545 tarballs compressed with @command{gzip} or
548 Please refer to the @uref{http://gcc.gnu.org/releases.html,,releases web page}
549 for information on how to obtain GCC@.
551 The source distribution includes the C, C++, Objective-C, Fortran, Java,
552 and Ada (in the case of GCC 3.1 and later) compilers, as well as
553 runtime libraries for C++, Objective-C, Fortran, and Java.
554 For previous versions these were downloadable as separate components such
555 as the core GCC distribution, which included the C language front end and
556 shared components, and language-specific distributions including the
557 language front end and the language runtime (where appropriate).
559 If you also intend to build binutils (either to upgrade an existing
560 installation or for use in place of the corresponding tools of your
561 OS), unpack the binutils distribution either in the same directory or
562 a separate one. In the latter case, add symbolic links to any
563 components of the binutils you intend to build alongside the compiler
564 (@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld},
565 @file{opcodes}, @dots{}) to the directory containing the GCC sources.
567 Likewise the GMP, MPFR and MPC libraries can be automatically built
568 together with GCC. Unpack the GMP, MPFR and/or MPC source
569 distributions in the directory containing the GCC sources and rename
570 their directories to @file{gmp}, @file{mpfr} and @file{mpc},
571 respectively (or use symbolic links with the same name).
578 @uref{./index.html,,Return to the GCC Installation page}
582 @c ***Configuration***********************************************************
584 @comment node-name, next, previous, up
585 @node Configuration, Building, Downloading the source, Installing GCC
589 @chapter Installing GCC: Configuration
591 @cindex Configuration
592 @cindex Installing GCC: Configuration
594 Like most GNU software, GCC must be configured before it can be built.
595 This document describes the recommended configuration procedure
596 for both native and cross targets.
598 We use @var{srcdir} to refer to the toplevel source directory for
599 GCC; we use @var{objdir} to refer to the toplevel build/object directory.
601 If you obtained the sources via SVN, @var{srcdir} must refer to the top
602 @file{gcc} directory, the one where the @file{MAINTAINERS} file can be
603 found, and not its @file{gcc} subdirectory, otherwise the build will fail.
605 If either @var{srcdir} or @var{objdir} is located on an automounted NFS
606 file system, the shell's built-in @command{pwd} command will return
607 temporary pathnames. Using these can lead to various sorts of build
608 problems. To avoid this issue, set the @env{PWDCMD} environment
609 variable to an automounter-aware @command{pwd} command, e.g.,
610 @command{pawd} or @samp{amq -w}, during the configuration and build
613 First, we @strong{highly} recommend that GCC be built into a
614 separate directory from the sources which does @strong{not} reside
615 within the source tree. This is how we generally build GCC; building
616 where @var{srcdir} == @var{objdir} should still work, but doesn't
617 get extensive testing; building where @var{objdir} is a subdirectory
618 of @var{srcdir} is unsupported.
620 If you have previously built GCC in the same directory for a
621 different target machine, do @samp{make distclean} to delete all files
622 that might be invalid. One of the files this deletes is @file{Makefile};
623 if @samp{make distclean} complains that @file{Makefile} does not exist
624 or issues a message like ``don't know how to make distclean'' it probably
625 means that the directory is already suitably clean. However, with the
626 recommended method of building in a separate @var{objdir}, you should
627 simply use a different @var{objdir} for each target.
629 Second, when configuring a native system, either @command{cc} or
630 @command{gcc} must be in your path or you must set @env{CC} in
631 your environment before running configure. Otherwise the configuration
635 Note that the bootstrap compiler and the resulting GCC must be link
636 compatible, else the bootstrap will fail with linker errors about
637 incompatible object file formats. Several multilibed targets are
638 affected by this requirement, see
640 @ref{Specific, host/target specific installation notes}.
643 @uref{specific.html,,host/target specific installation notes}.
652 % @var{srcdir}/configure [@var{options}] [@var{target}]
655 @heading Distributor options
657 If you will be distributing binary versions of GCC, with modifications
658 to the source code, you should use the options described in this
659 section to make clear that your version contains modifications.
662 @item --with-pkgversion=@var{version}
663 Specify a string that identifies your package. You may wish
664 to include a build number or build date. This version string will be
665 included in the output of @command{gcc --version}. This suffix does
666 not replace the default version string, only the @samp{GCC} part.
668 The default value is @samp{GCC}.
670 @item --with-bugurl=@var{url}
671 Specify the URL that users should visit if they wish to report a bug.
672 You are of course welcome to forward bugs reported to you to the FSF,
673 if you determine that they are not bugs in your modifications.
675 The default value refers to the FSF's GCC bug tracker.
679 @heading Target specification
682 GCC has code to correctly determine the correct value for @var{target}
683 for nearly all native systems. Therefore, we highly recommend you do
684 not provide a configure target when configuring a native compiler.
687 @var{target} must be specified as @option{--target=@var{target}}
688 when configuring a cross compiler; examples of valid targets would be
689 m68k-elf, sh-elf, etc.
692 Specifying just @var{target} instead of @option{--target=@var{target}}
693 implies that the host defaults to @var{target}.
697 @heading Options specification
699 Use @var{options} to override several configure time options for
700 GCC@. A list of supported @var{options} follows; @samp{configure
701 --help} may list other options, but those not listed below may not
702 work and should not normally be used.
704 Note that each @option{--enable} option has a corresponding
705 @option{--disable} option and that each @option{--with} option has a
706 corresponding @option{--without} option.
709 @item --prefix=@var{dirname}
710 Specify the toplevel installation
711 directory. This is the recommended way to install the tools into a directory
712 other than the default. The toplevel installation directory defaults to
715 We @strong{highly} recommend against @var{dirname} being the same or a
716 subdirectory of @var{objdir} or vice versa. If specifying a directory
717 beneath a user's home directory tree, some shells will not expand
718 @var{dirname} correctly if it contains the @samp{~} metacharacter; use
721 The following standard @command{autoconf} options are supported. Normally you
722 should not need to use these options.
724 @item --exec-prefix=@var{dirname}
725 Specify the toplevel installation directory for architecture-dependent
726 files. The default is @file{@var{prefix}}.
728 @item --bindir=@var{dirname}
729 Specify the installation directory for the executables called by users
730 (such as @command{gcc} and @command{g++}). The default is
731 @file{@var{exec-prefix}/bin}.
733 @item --libdir=@var{dirname}
734 Specify the installation directory for object code libraries and
735 internal data files of GCC@. The default is @file{@var{exec-prefix}/lib}.
737 @item --libexecdir=@var{dirname}
738 Specify the installation directory for internal executables of GCC@.
739 The default is @file{@var{exec-prefix}/libexec}.
741 @item --with-slibdir=@var{dirname}
742 Specify the installation directory for the shared libgcc library. The
743 default is @file{@var{libdir}}.
745 @item --datarootdir=@var{dirname}
746 Specify the root of the directory tree for read-only architecture-independent
747 data files referenced by GCC@. The default is @file{@var{prefix}/share}.
749 @item --infodir=@var{dirname}
750 Specify the installation directory for documentation in info format.
751 The default is @file{@var{datarootdir}/info}.
753 @item --datadir=@var{dirname}
754 Specify the installation directory for some architecture-independent
755 data files referenced by GCC@. The default is @file{@var{datarootdir}}.
757 @item --docdir=@var{dirname}
758 Specify the installation directory for documentation files (other
759 than Info) for GCC@. The default is @file{@var{datarootdir}/doc}.
761 @item --htmldir=@var{dirname}
762 Specify the installation directory for HTML documentation files.
763 The default is @file{@var{docdir}}.
765 @item --pdfdir=@var{dirname}
766 Specify the installation directory for PDF documentation files.
767 The default is @file{@var{docdir}}.
769 @item --mandir=@var{dirname}
770 Specify the installation directory for manual pages. The default is
771 @file{@var{datarootdir}/man}. (Note that the manual pages are only extracts
772 from the full GCC manuals, which are provided in Texinfo format. The manpages
773 are derived by an automatic conversion process from parts of the full
776 @item --with-gxx-include-dir=@var{dirname}
778 the installation directory for G++ header files. The default depends
779 on other configuration options, and differs between cross and native
782 @item --with-specs=@var{specs}
783 Specify additional command line driver SPECS.
784 This can be useful if you need to turn on a non-standard feature by
785 default without modifying the compiler's source code, for instance
786 @option{--with-specs=%@{!fcommon:%@{!fno-common:-fno-common@}@}}.
788 @xref{Spec Files,, Specifying subprocesses and the switches to pass to them,
789 gcc, Using the GNU Compiler Collection (GCC)},
792 See ``Spec Files'' in the main manual
797 @item --program-prefix=@var{prefix}
798 GCC supports some transformations of the names of its programs when
799 installing them. This option prepends @var{prefix} to the names of
800 programs to install in @var{bindir} (see above). For example, specifying
801 @option{--program-prefix=foo-} would result in @samp{gcc}
802 being installed as @file{/usr/local/bin/foo-gcc}.
804 @item --program-suffix=@var{suffix}
805 Appends @var{suffix} to the names of programs to install in @var{bindir}
806 (see above). For example, specifying @option{--program-suffix=-3.1}
807 would result in @samp{gcc} being installed as
808 @file{/usr/local/bin/gcc-3.1}.
810 @item --program-transform-name=@var{pattern}
811 Applies the @samp{sed} script @var{pattern} to be applied to the names
812 of programs to install in @var{bindir} (see above). @var{pattern} has to
813 consist of one or more basic @samp{sed} editing commands, separated by
814 semicolons. For example, if you want the @samp{gcc} program name to be
815 transformed to the installed program @file{/usr/local/bin/myowngcc} and
816 the @samp{g++} program name to be transformed to
817 @file{/usr/local/bin/gspecial++} without changing other program names,
818 you could use the pattern
819 @option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'}
820 to achieve this effect.
822 All three options can be combined and used together, resulting in more
823 complex conversion patterns. As a basic rule, @var{prefix} (and
824 @var{suffix}) are prepended (appended) before further transformations
825 can happen with a special transformation script @var{pattern}.
827 As currently implemented, this option only takes effect for native
828 builds; cross compiler binaries' names are not transformed even when a
829 transformation is explicitly asked for by one of these options.
831 For native builds, some of the installed programs are also installed
832 with the target alias in front of their name, as in
833 @samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen
834 before the target alias is prepended to the name---so, specifying
835 @option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the
836 resulting binary would be installed as
837 @file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}.
839 As a last shortcoming, none of the installed Ada programs are
840 transformed yet, which will be fixed in some time.
842 @item --with-local-prefix=@var{dirname}
844 installation directory for local include files. The default is
845 @file{/usr/local}. Specify this option if you want the compiler to
846 search directory @file{@var{dirname}/include} for locally installed
847 header files @emph{instead} of @file{/usr/local/include}.
849 You should specify @option{--with-local-prefix} @strong{only} if your
850 site has a different convention (not @file{/usr/local}) for where to put
853 The default value for @option{--with-local-prefix} is @file{/usr/local}
854 regardless of the value of @option{--prefix}. Specifying
855 @option{--prefix} has no effect on which directory GCC searches for
856 local header files. This may seem counterintuitive, but actually it is
859 The purpose of @option{--prefix} is to specify where to @emph{install
860 GCC}. The local header files in @file{/usr/local/include}---if you put
861 any in that directory---are not part of GCC@. They are part of other
862 programs---perhaps many others. (GCC installs its own header files in
863 another directory which is based on the @option{--prefix} value.)
865 Both the local-prefix include directory and the GCC-prefix include
866 directory are part of GCC's ``system include'' directories. Although these
867 two directories are not fixed, they need to be searched in the proper
868 order for the correct processing of the include_next directive. The
869 local-prefix include directory is searched before the GCC-prefix
870 include directory. Another characteristic of system include directories
871 is that pedantic warnings are turned off for headers in these directories.
873 Some autoconf macros add @option{-I @var{directory}} options to the
874 compiler command line, to ensure that directories containing installed
875 packages' headers are searched. When @var{directory} is one of GCC's
876 system include directories, GCC will ignore the option so that system
877 directories continue to be processed in the correct order. This
878 may result in a search order different from what was specified but the
879 directory will still be searched.
881 GCC automatically searches for ordinary libraries using
882 @env{GCC_EXEC_PREFIX}. Thus, when the same installation prefix is
883 used for both GCC and packages, GCC will automatically search for
884 both headers and libraries. This provides a configuration that is
885 easy to use. GCC behaves in a manner similar to that when it is
886 installed as a system compiler in @file{/usr}.
888 Sites that need to install multiple versions of GCC may not want to
889 use the above simple configuration. It is possible to use the
890 @option{--program-prefix}, @option{--program-suffix} and
891 @option{--program-transform-name} options to install multiple versions
892 into a single directory, but it may be simpler to use different prefixes
893 and the @option{--with-local-prefix} option to specify the location of the
894 site-specific files for each version. It will then be necessary for
895 users to specify explicitly the location of local site libraries
896 (e.g., with @env{LIBRARY_PATH}).
898 The same value can be used for both @option{--with-local-prefix} and
899 @option{--prefix} provided it is not @file{/usr}. This can be used
900 to avoid the default search of @file{/usr/local/include}.
902 @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
903 The directory you use for @option{--with-local-prefix} @strong{must not}
904 contain any of the system's standard header files. If it did contain
905 them, certain programs would be miscompiled (including GNU Emacs, on
906 certain targets), because this would override and nullify the header
907 file corrections made by the @command{fixincludes} script.
909 Indications are that people who use this option use it based on mistaken
910 ideas of what it is for. People use it as if it specified where to
911 install part of GCC@. Perhaps they make this assumption because
912 installing GCC creates the directory.
914 @item --with-native-system-header-dir=@var{dirname}
915 Specifies that @var{dirname} is the directory that contains native system
916 header files, rather than @file{/usr/include}. This option is most useful
917 if you are creating a compiler that should be isolated from the system
918 as much as possible. It is most commonly used with the
919 @option{--with-sysroot} option and will cause GCC to search
920 @var{dirname} inside the system root specified by that option.
922 @item --enable-shared[=@var{package}[,@dots{}]]
923 Build shared versions of libraries, if shared libraries are supported on
924 the target platform. Unlike GCC 2.95.x and earlier, shared libraries
925 are enabled by default on all platforms that support shared libraries.
927 If a list of packages is given as an argument, build shared libraries
928 only for the listed packages. For other packages, only static libraries
929 will be built. Package names currently recognized in the GCC tree are
930 @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not
931 @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc},
932 @samp{ada}, @samp{libada}, @samp{libjava}, @samp{libgo}, and @samp{libobjc}.
933 Note @samp{libiberty} does not support shared libraries at all.
935 Use @option{--disable-shared} to build only static libraries. Note that
936 @option{--disable-shared} does not accept a list of package names as
937 argument, only @option{--enable-shared} does.
939 Contrast with @option{--enable-host-shared}, which affects @emph{host}
942 @item --enable-host-shared
943 Specify that the @emph{host} code should be built into position-independent
944 machine code (with -fPIC), allowing it to be used within shared libraries,
945 but yielding a slightly slower compiler.
947 This option is required when building the libgccjit.so library.
949 Contrast with @option{--enable-shared}, which affects @emph{target}
952 @item @anchor{with-gnu-as}--with-gnu-as
953 Specify that the compiler should assume that the
954 assembler it finds is the GNU assembler. However, this does not modify
955 the rules to find an assembler and will result in confusion if the
956 assembler found is not actually the GNU assembler. (Confusion may also
957 result if the compiler finds the GNU assembler but has not been
958 configured with @option{--with-gnu-as}.) If you have more than one
959 assembler installed on your system, you may want to use this option in
960 connection with @option{--with-as=@var{pathname}} or
961 @option{--with-build-time-tools=@var{pathname}}.
963 The following systems are the only ones where it makes a difference
964 whether you use the GNU assembler. On any other system,
965 @option{--with-gnu-as} has no effect.
968 @item @samp{hppa1.0-@var{any}-@var{any}}
969 @item @samp{hppa1.1-@var{any}-@var{any}}
970 @item @samp{sparc-sun-solaris2.@var{any}}
971 @item @samp{sparc64-@var{any}-solaris2.@var{any}}
974 @item @anchor{with-as}--with-as=@var{pathname}
975 Specify that the compiler should use the assembler pointed to by
976 @var{pathname}, rather than the one found by the standard rules to find
977 an assembler, which are:
980 Unless GCC is being built with a cross compiler, check the
981 @file{@var{libexec}/gcc/@var{target}/@var{version}} directory.
982 @var{libexec} defaults to @file{@var{exec-prefix}/libexec};
983 @var{exec-prefix} defaults to @var{prefix}, which
984 defaults to @file{/usr/local} unless overridden by the
985 @option{--prefix=@var{pathname}} switch described above. @var{target}
986 is the target system triple, such as @samp{sparc-sun-solaris2.7}, and
987 @var{version} denotes the GCC version, such as 3.0.
990 If the target system is the same that you are building on, check
991 operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
995 Check in the @env{PATH} for a tool whose name is prefixed by the
996 target system triple.
999 Check in the @env{PATH} for a tool whose name is not prefixed by the
1000 target system triple, if the host and target system triple are
1001 the same (in other words, we use a host tool if it can be used for
1002 the target as well).
1005 You may want to use @option{--with-as} if no assembler
1006 is installed in the directories listed above, or if you have multiple
1007 assemblers installed and want to choose one that is not found by the
1010 @item @anchor{with-gnu-ld}--with-gnu-ld
1011 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
1014 @item --with-ld=@var{pathname}
1015 Same as @uref{#with-as,,@option{--with-as}}
1019 Specify that stabs debugging
1020 information should be used instead of whatever format the host normally
1021 uses. Normally GCC uses the same debug format as the host system.
1023 On MIPS based systems and on Alphas, you must specify whether you want
1024 GCC to create the normal ECOFF debugging format, or to use BSD-style
1025 stabs passed through the ECOFF symbol table. The normal ECOFF debug
1026 format cannot fully handle languages other than C@. BSD stabs format can
1027 handle other languages, but it only works with the GNU debugger GDB@.
1029 Normally, GCC uses the ECOFF debugging format by default; if you
1030 prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@.
1032 No matter which default you choose when you configure GCC, the user
1033 can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
1034 the debug format for a particular compilation.
1036 @option{--with-stabs} is meaningful on the ISC system on the 386, also, if
1037 @option{--with-gas} is used. It selects use of stabs debugging
1038 information embedded in COFF output. This kind of debugging information
1039 supports C++ well; ordinary COFF debugging information does not.
1041 @option{--with-stabs} is also meaningful on 386 systems running SVR4. It
1042 selects use of stabs debugging information embedded in ELF output. The
1043 C++ compiler currently (2.6.0) does not support the DWARF debugging
1044 information normally used on 386 SVR4 platforms; stabs provide a
1045 workable alternative. This requires gas and gdb, as the normal SVR4
1046 tools can not generate or interpret stabs.
1048 @item --with-tls=@var{dialect}
1049 Specify the default TLS dialect, for systems were there is a choice.
1050 For ARM targets, possible values for @var{dialect} are @code{gnu} or
1051 @code{gnu2}, which select between the original GNU dialect and the GNU TLS
1052 descriptor-based dialect.
1054 @item --enable-multiarch
1055 Specify whether to enable or disable multiarch support. The default is
1056 to check for glibc start files in a multiarch location, and enable it
1057 if the files are found. The auto detection is enabled for native builds,
1058 and for cross builds configured with @option{--with-sysroot}, and without
1059 @option{--with-native-system-header-dir}.
1060 More documentation about multiarch can be found at
1061 @uref{http://wiki.debian.org/Multiarch}.
1063 @item --enable-vtable-verify
1064 Specify whether to enable or disable the vtable verification feature.
1065 Enabling this feature causes libstdc++ to be built with its virtual calls
1066 in verifiable mode. This means that, when linked with libvtv, every
1067 virtual call in libstdc++ will verify the vtable pointer through which the
1068 call will be made before actually making the call. If not linked with libvtv,
1069 the verifier will call stub functions (in libstdc++ itself) and do nothing.
1070 If vtable verification is disabled, then libstdc++ is not built with its
1071 virtual calls in verifiable mode at all. However the libvtv library will
1072 still be built (see @option{--disable-libvtv} to turn off building libvtv).
1073 @option{--disable-vtable-verify} is the default.
1075 @item --disable-multilib
1076 Specify that multiple target
1077 libraries to support different target variants, calling
1078 conventions, etc.@: should not be built. The default is to build a
1079 predefined set of them.
1081 Some targets provide finer-grained control over which multilibs are built
1082 (e.g., @option{--disable-softfloat}):
1085 fpu, 26bit, underscore, interwork, biendian, nofmult.
1088 softfloat, m68881, m68000, m68020.
1091 single-float, biendian, softfloat.
1093 @item powerpc*-*-*, rs6000*-*-*
1094 aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
1099 @item --with-multilib-list=@var{list}
1100 @itemx --without-multilib-list
1101 Specify what multilibs to build.
1102 Currently only implemented for sh*-*-* and x86-64-*-linux*.
1106 @var{list} is a comma separated list of CPU names. These must be of the
1107 form @code{sh*} or @code{m*} (in which case they match the compiler option
1108 for that processor). The list should not contain any endian options -
1109 these are handled by @option{--with-endian}.
1111 If @var{list} is empty, then there will be no multilibs for extra
1112 processors. The multilib for the secondary endian remains enabled.
1114 As a special case, if an entry in the list starts with a @code{!}
1115 (exclamation point), then it is added to the list of excluded multilibs.
1116 Entries of this sort should be compatible with @samp{MULTILIB_EXCLUDES}
1117 (once the leading @code{!} has been stripped).
1119 If @option{--with-multilib-list} is not given, then a default set of
1120 multilibs is selected based on the value of @option{--target}. This is
1121 usually the complete set of libraries, but some targets imply a more
1124 Example 1: to configure a compiler for SH4A only, but supporting both
1125 endians, with little endian being the default:
1127 --with-cpu=sh4a --with-endian=little,big --with-multilib-list=
1130 Example 2: to configure a compiler for both SH4A and SH4AL-DSP, but with
1131 only little endian SH4AL:
1133 --with-cpu=sh4a --with-endian=little,big \
1134 --with-multilib-list=sh4al,!mb/m4al
1137 @item x86-64-*-linux*
1138 @var{list} is a comma separated list of @code{m32}, @code{m64} and
1139 @code{mx32} to enable 32-bit, 64-bit and x32 run-time libraries,
1140 respectively. If @var{list} is empty, then there will be no multilibs
1141 and only the default run-time library will be enabled.
1143 If @option{--with-multilib-list} is not given, then only 32-bit and
1144 64-bit run-time libraries will be enabled.
1147 @item --with-endian=@var{endians}
1148 Specify what endians to use.
1149 Currently only implemented for sh*-*-*.
1151 @var{endians} may be one of the following:
1154 Use big endian exclusively.
1156 Use little endian exclusively.
1158 Use big endian by default. Provide a multilib for little endian.
1160 Use little endian by default. Provide a multilib for big endian.
1163 @item --enable-threads
1164 Specify that the target
1165 supports threads. This affects the Objective-C compiler and runtime
1166 library, and exception handling for other languages like C++ and Java.
1167 On some systems, this is the default.
1169 In general, the best (and, in many cases, the only known) threading
1170 model available will be configured for use. Beware that on some
1171 systems, GCC has not been taught what threading models are generally
1172 available for the system. In this case, @option{--enable-threads} is an
1173 alias for @option{--enable-threads=single}.
1175 @item --disable-threads
1176 Specify that threading support should be disabled for the system.
1177 This is an alias for @option{--enable-threads=single}.
1179 @item --enable-threads=@var{lib}
1181 @var{lib} is the thread support library. This affects the Objective-C
1182 compiler and runtime library, and exception handling for other languages
1183 like C++ and Java. The possibilities for @var{lib} are:
1191 LynxOS thread support.
1193 MIPS SDE thread support.
1195 This is an alias for @samp{single}.
1197 Generic POSIX/Unix98 thread support.
1199 RTEMS thread support.
1201 Disable thread support, should work for all platforms.
1205 VxWorks thread support.
1207 Microsoft Win32 API thread support.
1211 Specify that the target supports TLS (Thread Local Storage). Usually
1212 configure can correctly determine if TLS is supported. In cases where
1213 it guesses incorrectly, TLS can be explicitly enabled or disabled with
1214 @option{--enable-tls} or @option{--disable-tls}. This can happen if
1215 the assembler supports TLS but the C library does not, or if the
1216 assumptions made by the configure test are incorrect.
1219 Specify that the target does not support TLS.
1220 This is an alias for @option{--enable-tls=no}.
1222 @item --with-cpu=@var{cpu}
1223 @itemx --with-cpu-32=@var{cpu}
1224 @itemx --with-cpu-64=@var{cpu}
1225 Specify which cpu variant the compiler should generate code for by default.
1226 @var{cpu} will be used as the default value of the @option{-mcpu=} switch.
1227 This option is only supported on some targets, including ARC, ARM, i386, M68k,
1228 PowerPC, and SPARC@. It is mandatory for ARC@. The @option{--with-cpu-32} and
1229 @option{--with-cpu-64} options specify separate default CPUs for
1230 32-bit and 64-bit modes; these options are only supported for i386,
1233 @item --with-schedule=@var{cpu}
1234 @itemx --with-arch=@var{cpu}
1235 @itemx --with-arch-32=@var{cpu}
1236 @itemx --with-arch-64=@var{cpu}
1237 @itemx --with-tune=@var{cpu}
1238 @itemx --with-tune-32=@var{cpu}
1239 @itemx --with-tune-64=@var{cpu}
1240 @itemx --with-abi=@var{abi}
1241 @itemx --with-fpu=@var{type}
1242 @itemx --with-float=@var{type}
1243 These configure options provide default values for the @option{-mschedule=},
1244 @option{-march=}, @option{-mtune=}, @option{-mabi=}, and @option{-mfpu=}
1245 options and for @option{-mhard-float} or @option{-msoft-float}. As with
1246 @option{--with-cpu}, which switches will be accepted and acceptable values
1247 of the arguments depend on the target.
1249 @item --with-mode=@var{mode}
1250 Specify if the compiler should default to @option{-marm} or @option{-mthumb}.
1251 This option is only supported on ARM targets.
1253 @item --with-stack-offset=@var{num}
1254 This option sets the default for the -mstack-offset=@var{num} option,
1255 and will thus generally also control the setting of this option for
1256 libraries. This option is only supported on Epiphany targets.
1258 @item --with-fpmath=@var{isa}
1259 This options sets @option{-mfpmath=sse} by default and specifies the default
1260 ISA for floating-point arithmetics. You can select either @samp{sse} which
1261 enables @option{-msse2} or @samp{avx} which enables @option{-mavx} by default.
1262 This option is only supported on i386 and x86-64 targets.
1264 @item --with-fp-32=@var{mode}
1265 On MIPS targets, set the default value for the @option{-mfp} option when using
1266 the o32 ABI. The possibilities for @var{mode} are:
1269 Use the o32 FP32 ABI extension, as with the @option{-mfp32} command-line
1272 Use the o32 FPXX ABI extension, as with the @option{-mfpxx} command-line
1275 Use the o32 FP64 ABI extension, as with the @option{-mfp64} command-line
1278 In the absence of this configuration option the default is to use the o32
1281 @item --with-odd-spreg-32
1282 On MIPS targets, set the @option{-modd-spreg} option by default when using
1285 @item --without-odd-spreg-32
1286 On MIPS targets, set the @option{-mno-odd-spreg} option by default when using
1287 the o32 ABI. This is normally used in conjunction with
1288 @option{--with-fp-32=64} in order to target the o32 FP64A ABI extension.
1290 @item --with-nan=@var{encoding}
1291 On MIPS targets, set the default encoding convention to use for the
1292 special not-a-number (NaN) IEEE 754 floating-point data. The
1293 possibilities for @var{encoding} are:
1296 Use the legacy encoding, as with the @option{-mnan=legacy} command-line
1299 Use the 754-2008 encoding, as with the @option{-mnan=2008} command-line
1302 To use this configuration option you must have an assembler version
1303 installed that supports the @option{-mnan=} command-line option too.
1304 In the absence of this configuration option the default convention is
1305 the legacy encoding, as when neither of the @option{-mnan=2008} and
1306 @option{-mnan=legacy} command-line options has been used.
1308 @item --with-divide=@var{type}
1309 Specify how the compiler should generate code for checking for
1310 division by zero. This option is only supported on the MIPS target.
1311 The possibilities for @var{type} are:
1314 Division by zero checks use conditional traps (this is the default on
1315 systems that support conditional traps).
1317 Division by zero checks use the break instruction.
1320 @c If you make --with-llsc the default for additional targets,
1321 @c update the --with-llsc description in the MIPS section below.
1324 On MIPS targets, make @option{-mllsc} the default when no
1325 @option{-mno-llsc} option is passed. This is the default for
1326 Linux-based targets, as the kernel will emulate them if the ISA does
1329 @item --without-llsc
1330 On MIPS targets, make @option{-mno-llsc} the default when no
1331 @option{-mllsc} option is passed.
1334 On MIPS targets, make @option{-msynci} the default when no
1335 @option{-mno-synci} option is passed.
1337 @item --without-synci
1338 On MIPS targets, make @option{-mno-synci} the default when no
1339 @option{-msynci} option is passed. This is the default.
1341 @item --with-mips-plt
1342 On MIPS targets, make use of copy relocations and PLTs.
1343 These features are extensions to the traditional
1344 SVR4-based MIPS ABIs and require support from GNU binutils
1345 and the runtime C library.
1347 @item --enable-__cxa_atexit
1348 Define if you want to use __cxa_atexit, rather than atexit, to
1349 register C++ destructors for local statics and global objects.
1350 This is essential for fully standards-compliant handling of
1351 destructors, but requires __cxa_atexit in libc. This option is currently
1352 only available on systems with GNU libc. When enabled, this will cause
1353 @option{-fuse-cxa-atexit} to be passed by default.
1355 @item --enable-gnu-indirect-function
1356 Define if you want to enable the @code{ifunc} attribute. This option is
1357 currently only available on systems with GNU libc on certain targets.
1359 @item --enable-target-optspace
1361 libraries should be optimized for code space instead of code speed.
1362 This is the default for the m32r platform.
1364 @item --with-cpp-install-dir=@var{dirname}
1365 Specify that the user visible @command{cpp} program should be installed
1366 in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
1368 @item --enable-comdat
1369 Enable COMDAT group support. This is primarily used to override the
1370 automatically detected value.
1372 @item --enable-initfini-array
1373 Force the use of sections @code{.init_array} and @code{.fini_array}
1374 (instead of @code{.init} and @code{.fini}) for constructors and
1375 destructors. Option @option{--disable-initfini-array} has the
1376 opposite effect. If neither option is specified, the configure script
1377 will try to guess whether the @code{.init_array} and
1378 @code{.fini_array} sections are supported and, if they are, use them.
1380 @item --enable-link-mutex
1381 When building GCC, use a mutex to avoid linking the compilers for
1382 multiple languages at the same time, to avoid thrashing on build
1383 systems with limited free memory. The default is not to use such a mutex.
1385 @item --enable-maintainer-mode
1386 The build rules that regenerate the Autoconf and Automake output files as
1387 well as the GCC master message catalog @file{gcc.pot} are normally
1388 disabled. This is because it can only be rebuilt if the complete source
1389 tree is present. If you have changed the sources and want to rebuild the
1390 catalog, configuring with @option{--enable-maintainer-mode} will enable
1391 this. Note that you need a recent version of the @code{gettext} tools
1394 @item --disable-bootstrap
1395 For a native build, the default configuration is to perform
1396 a 3-stage bootstrap of the compiler when @samp{make} is invoked,
1397 testing that GCC can compile itself correctly. If you want to disable
1398 this process, you can configure with @option{--disable-bootstrap}.
1400 @item --enable-bootstrap
1401 In special cases, you may want to perform a 3-stage build
1402 even if the target and host triplets are different.
1403 This is possible when the host can run code compiled for
1404 the target (e.g.@: host is i686-linux, target is i486-linux).
1405 Starting from GCC 4.2, to do this you have to configure explicitly
1406 with @option{--enable-bootstrap}.
1408 @item --enable-generated-files-in-srcdir
1409 Neither the .c and .h files that are generated from Bison and flex nor the
1410 info manuals and man pages that are built from the .texi files are present
1411 in the SVN development tree. When building GCC from that development tree,
1412 or from one of our snapshots, those generated files are placed in your
1413 build directory, which allows for the source to be in a readonly
1416 If you configure with @option{--enable-generated-files-in-srcdir} then those
1417 generated files will go into the source directory. This is mainly intended
1418 for generating release or prerelease tarballs of the GCC sources, since it
1419 is not a requirement that the users of source releases to have flex, Bison,
1422 @item --enable-version-specific-runtime-libs
1424 that runtime libraries should be installed in the compiler specific
1425 subdirectory (@file{@var{libdir}/gcc}) rather than the usual places. In
1426 addition, @samp{libstdc++}'s include files will be installed into
1427 @file{@var{libdir}} unless you overruled it by using
1428 @option{--with-gxx-include-dir=@var{dirname}}. Using this option is
1429 particularly useful if you intend to use several versions of GCC in
1430 parallel. This is currently supported by @samp{libgfortran},
1431 @samp{libjava}, @samp{libstdc++}, and @samp{libobjc}.
1433 @item @anchor{WithAixSoname}--with-aix-soname=@samp{aix}, @samp{svr4} or @samp{both}
1434 Traditional AIX shared library versioning (versioned @code{Shared Object}
1435 files as members of unversioned @code{Archive Library} files named
1436 @samp{lib.a}) causes numerous headaches for package managers. However,
1437 @code{Import Files} as members of @code{Archive Library} files allow for
1438 @strong{filename-based versioning} of shared libraries as seen on Linux/SVR4,
1439 where this is called the "SONAME". But as they prevent static linking,
1440 @code{Import Files} may be used with @code{Runtime Linking} only, where the
1441 linker does search for @samp{libNAME.so} before @samp{libNAME.a} library
1442 filenames with the @samp{-lNAME} linker flag.
1444 @anchor{AixLdCommand}For detailed information please refer to the AIX
1445 @uref{http://www-01.ibm.com/support/knowledgecenter/search/%22the%20ld%20command%2C%20also%20called%20the%20linkage%20editor%20or%20binder%22,,ld
1448 As long as shared library creation is enabled, upon:
1450 @item --with-aix-soname=aix
1451 @item --with-aix-soname=both
1452 A (traditional AIX) @code{Shared Archive Library} file is created:
1454 @item using the @samp{libNAME.a} filename scheme
1455 @item with the @code{Shared Object} file as archive member named
1456 @samp{libNAME.so.V} (except for @samp{libgcc_s}, where the @code{Shared
1457 Object} file is named @samp{shr.o} for backwards compatibility), which
1459 @item is used for runtime loading from inside the @samp{libNAME.a} file
1460 @item is used for dynamic loading via
1461 @code{dlopen("libNAME.a(libNAME.so.V)", RTLD_MEMBER)}
1462 @item is used for shared linking
1463 @item is used for static linking, so no separate @code{Static Archive
1464 Library} file is needed
1467 @item --with-aix-soname=both
1468 @item --with-aix-soname=svr4
1469 A (second) @code{Shared Archive Library} file is created:
1471 @item using the @samp{libNAME.so.V} filename scheme
1472 @item with the @code{Shared Object} file as archive member named
1475 @item is created with the @code{-G linker flag}
1476 @item has the @code{F_LOADONLY} flag set
1477 @item is used for runtime loading from inside the @samp{libNAME.so.V} file
1478 @item is used for dynamic loading via @code{dlopen("libNAME.so.V(shr.o)",
1481 @item with the @code{Import File} as archive member named @samp{shr.imp},
1484 @item refers to @samp{libNAME.so.V(shr.o)} as the "SONAME", to be recorded
1485 in the @code{Loader Section} of subsequent binaries
1486 @item indicates whether @samp{libNAME.so.V(shr.o)} is 32 or 64 bit
1487 @item lists all the public symbols exported by @samp{lib.so.V(shr.o)},
1488 eventually decorated with the @code{@samp{weak} Keyword}
1489 @item is necessary for shared linking against @samp{lib.so.V(shr.o)}
1492 A symbolic link using the @samp{libNAME.so} filename scheme is created:
1494 @item pointing to the @samp{libNAME.so.V} @code{Shared Archive Library} file
1495 @item to permit the @code{ld Command} to find @samp{lib.so.V(shr.imp)} via
1496 the @samp{-lNAME} argument (requires @code{Runtime Linking} to be enabled)
1497 @item to permit dynamic loading of @samp{lib.so.V(shr.o)} without the need
1498 to specify the version number via @code{dlopen("libNAME.so(shr.o)",
1503 As long as static library creation is enabled, upon:
1505 @item --with-aix-soname=svr4
1506 A @code{Static Archive Library} is created:
1508 @item using the @samp{libNAME.a} filename scheme
1509 @item with all the @code{Static Object} files as archive members, which
1511 @item are used for static linking
1516 While the aix-soname=@samp{svr4} option does not create @code{Shared Object}
1517 files as members of unversioned @code{Archive Library} files any more, package
1518 managers still are responsible to
1519 @uref{./specific.html#TransferAixShobj,,transfer} @code{Shared Object} files
1520 found as member of a previously installed unversioned @code{Archive Library}
1521 file into the newly installed @code{Archive Library} file with the same
1524 @emph{WARNING:} Creating @code{Shared Object} files with @code{Runtime Linking}
1525 enabled may bloat the TOC, eventually leading to @code{TOC overflow} errors,
1526 requiring the use of either the @option{-Wl,-bbigtoc} linker flag (seen to
1527 break with the @code{GDB} debugger) or some of the TOC-related compiler flags,
1529 @xref{RS/6000 and PowerPC Options,, RS/6000 and PowerPC Options, gcc,
1530 Using the GNU Compiler Collection (GCC)}.
1533 see ``RS/6000 and PowerPC Options'' in the main manual.
1536 @option{--with-aix-soname} is currently supported by @samp{libgcc_s} only, so
1537 this option is still experimental and not for normal use yet.
1539 Default is the traditional behaviour @option{--with-aix-soname=@samp{aix}}.
1541 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
1542 Specify that only a particular subset of compilers and
1543 their runtime libraries should be built. For a list of valid values for
1544 @var{langN} you can issue the following command in the
1545 @file{gcc} directory of your GCC source tree:@*
1547 grep ^language= */config-lang.in
1549 Currently, you can use any of the following:
1550 @code{all}, @code{ada}, @code{c}, @code{c++}, @code{fortran},
1551 @code{go}, @code{java}, @code{jit}, @code{lto}, @code{objc}, @code{obj-c++}.
1552 Building the Ada compiler has special requirements, see below.
1553 If you do not pass this flag, or specify the option @code{all}, then all
1554 default languages available in the @file{gcc} sub-tree will be configured.
1555 Ada, Go, Jit, and Objective-C++ are not default languages. LTO is not a
1556 default language, but is built by default because @option{--enable-lto} is
1557 enabled by default. The other languages are default languages.
1559 @item --enable-stage1-languages=@var{lang1},@var{lang2},@dots{}
1560 Specify that a particular subset of compilers and their runtime
1561 libraries should be built with the system C compiler during stage 1 of
1562 the bootstrap process, rather than only in later stages with the
1563 bootstrapped C compiler. The list of valid values is the same as for
1564 @option{--enable-languages}, and the option @code{all} will select all
1565 of the languages enabled by @option{--enable-languages}. This option is
1566 primarily useful for GCC development; for instance, when a development
1567 version of the compiler cannot bootstrap due to compiler bugs, or when
1568 one is debugging front ends other than the C front end. When this
1569 option is used, one can then build the target libraries for the
1570 specified languages with the stage-1 compiler by using @command{make
1571 stage1-bubble all-target}, or run the testsuite on the stage-1 compiler
1572 for the specified languages using @command{make stage1-start check-gcc}.
1574 @item --disable-libada
1575 Specify that the run-time libraries and tools used by GNAT should not
1576 be built. This can be useful for debugging, or for compatibility with
1577 previous Ada build procedures, when it was required to explicitly
1578 do a @samp{make -C gcc gnatlib_and_tools}.
1580 @item --disable-libsanitizer
1581 Specify that the run-time libraries for the various sanitizers should
1584 @item --disable-libssp
1585 Specify that the run-time libraries for stack smashing protection
1586 should not be built.
1588 @item --disable-libquadmath
1589 Specify that the GCC quad-precision math library should not be built.
1590 On some systems, the library is required to be linkable when building
1591 the Fortran front end, unless @option{--disable-libquadmath-support}
1594 @item --disable-libquadmath-support
1595 Specify that the Fortran front end and @code{libgfortran} do not add
1596 support for @code{libquadmath} on systems supporting it.
1598 @item --disable-libgomp
1599 Specify that the GNU Offloading and Multi Processing Runtime Library
1600 should not be built.
1602 @item --disable-libvtv
1603 Specify that the run-time libraries used by vtable verification
1604 should not be built.
1607 Specify that the compiler should
1608 use DWARF 2 debugging information as the default.
1610 @item --with-advance-toolchain=@var{at}
1611 On 64-bit PowerPC Linux systems, configure the compiler to use the
1612 header files, library files, and the dynamic linker from the Advance
1613 Toolchain release @var{at} instead of the default versions that are
1614 provided by the Linux distribution. In general, this option is
1615 intended for the developers of GCC, and it is not intended for general
1618 @item --enable-targets=all
1619 @itemx --enable-targets=@var{target_list}
1620 Some GCC targets, e.g.@: powerpc64-linux, build bi-arch compilers.
1621 These are compilers that are able to generate either 64-bit or 32-bit
1622 code. Typically, the corresponding 32-bit target, e.g.@:
1623 powerpc-linux for powerpc64-linux, only generates 32-bit code. This
1624 option enables the 32-bit target to be a bi-arch compiler, which is
1625 useful when you want a bi-arch compiler that defaults to 32-bit, and
1626 you are building a bi-arch or multi-arch binutils in a combined tree.
1627 On mips-linux, this will build a tri-arch compiler (ABI o32/n32/64),
1629 Currently, this option only affects sparc-linux, powerpc-linux, x86-linux,
1630 mips-linux and s390-linux.
1632 @item --enable-default-pie
1633 Turn on @option{-fPIE} and @option{-pie} by default.
1635 @item --enable-secureplt
1636 This option enables @option{-msecure-plt} by default for powerpc-linux.
1638 @xref{RS/6000 and PowerPC Options,, RS/6000 and PowerPC Options, gcc,
1639 Using the GNU Compiler Collection (GCC)},
1642 See ``RS/6000 and PowerPC Options'' in the main manual
1646 This option enables @option{-mcld} by default for 32-bit x86 targets.
1648 @xref{i386 and x86-64 Options,, i386 and x86-64 Options, gcc,
1649 Using the GNU Compiler Collection (GCC)},
1652 See ``i386 and x86-64 Options'' in the main manual
1655 @item --enable-win32-registry
1656 @itemx --enable-win32-registry=@var{key}
1657 @itemx --disable-win32-registry
1658 The @option{--enable-win32-registry} option enables Microsoft Windows-hosted GCC
1659 to look up installations paths in the registry using the following key:
1662 @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
1665 @var{key} defaults to GCC version number, and can be overridden by the
1666 @option{--enable-win32-registry=@var{key}} option. Vendors and distributors
1667 who use custom installers are encouraged to provide a different key,
1668 perhaps one comprised of vendor name and GCC version number, to
1669 avoid conflict with existing installations. This feature is enabled
1670 by default, and can be disabled by @option{--disable-win32-registry}
1671 option. This option has no effect on the other hosts.
1674 Specify that the machine does not have a floating point unit. This
1675 option only applies to @samp{m68k-sun-sunos@var{n}}. On any other
1676 system, @option{--nfp} has no effect.
1678 @item --enable-werror
1679 @itemx --disable-werror
1680 @itemx --enable-werror=yes
1681 @itemx --enable-werror=no
1682 When you specify this option, it controls whether certain files in the
1683 compiler are built with @option{-Werror} in bootstrap stage2 and later.
1684 If you don't specify it, @option{-Werror} is turned on for the main
1685 development trunk. However it defaults to off for release branches and
1686 final releases. The specific files which get @option{-Werror} are
1687 controlled by the Makefiles.
1689 @item --enable-checking
1690 @itemx --enable-checking=@var{list}
1691 When you specify this option, the compiler is built to perform internal
1692 consistency checks of the requested complexity. This does not change the
1693 generated code, but adds error checking within the compiler. This will
1694 slow down the compiler and may only work properly if you are building
1695 the compiler with GCC@. This is @samp{yes} by default when building
1696 from SVN or snapshots, but @samp{release} for releases. The default
1697 for building the stage1 compiler is @samp{yes}. More control
1698 over the checks may be had by specifying @var{list}. The categories of
1699 checks available are @samp{yes} (most common checks
1700 @samp{assert,misc,tree,gc,rtlflag,runtime}), @samp{no} (no checks at
1701 all), @samp{all} (all but @samp{valgrind}), @samp{release} (cheapest
1702 checks @samp{assert,runtime}) or @samp{none} (same as @samp{no}).
1703 Individual checks can be enabled with these flags @samp{assert},
1704 @samp{df}, @samp{fold}, @samp{gc}, @samp{gcac} @samp{misc}, @samp{rtl},
1705 @samp{rtlflag}, @samp{runtime}, @samp{tree}, and @samp{valgrind}.
1707 The @samp{valgrind} check requires the external @command{valgrind}
1708 simulator, available from @uref{http://valgrind.org/}. The
1709 @samp{df}, @samp{rtl}, @samp{gcac} and @samp{valgrind} checks are very expensive.
1710 To disable all checking, @samp{--disable-checking} or
1711 @samp{--enable-checking=none} must be explicitly requested. Disabling
1712 assertions will make the compiler and runtime slightly faster but
1713 increase the risk of undetected internal errors causing wrong code to be
1716 @item --disable-stage1-checking
1717 @itemx --enable-stage1-checking
1718 @itemx --enable-stage1-checking=@var{list}
1719 If no @option{--enable-checking} option is specified the stage1
1720 compiler will be built with @samp{yes} checking enabled, otherwise
1721 the stage1 checking flags are the same as specified by
1722 @option{--enable-checking}. To build the stage1 compiler with
1723 different checking options use @option{--enable-stage1-checking}.
1724 The list of checking options is the same as for @option{--enable-checking}.
1725 If your system is too slow or too small to bootstrap a released compiler
1726 with checking for stage1 enabled, you can use @samp{--disable-stage1-checking}
1727 to disable checking for the stage1 compiler.
1729 @item --enable-coverage
1730 @itemx --enable-coverage=@var{level}
1731 With this option, the compiler is built to collect self coverage
1732 information, every time it is run. This is for internal development
1733 purposes, and only works when the compiler is being built with gcc. The
1734 @var{level} argument controls whether the compiler is built optimized or
1735 not, values are @samp{opt} and @samp{noopt}. For coverage analysis you
1736 want to disable optimization, for performance analysis you want to
1737 enable optimization. When coverage is enabled, the default level is
1738 without optimization.
1740 @item --enable-gather-detailed-mem-stats
1741 When this option is specified more detailed information on memory
1742 allocation is gathered. This information is printed when using
1743 @option{-fmem-report}.
1746 @itemx --disable-nls
1747 The @option{--enable-nls} option enables Native Language Support (NLS),
1748 which lets GCC output diagnostics in languages other than American
1749 English. Native Language Support is enabled by default if not doing a
1750 canadian cross build. The @option{--disable-nls} option disables NLS@.
1752 @item --with-included-gettext
1753 If NLS is enabled, the @option{--with-included-gettext} option causes the build
1754 procedure to prefer its copy of GNU @command{gettext}.
1756 @item --with-catgets
1757 If NLS is enabled, and if the host lacks @code{gettext} but has the
1758 inferior @code{catgets} interface, the GCC build procedure normally
1759 ignores @code{catgets} and instead uses GCC's copy of the GNU
1760 @code{gettext} library. The @option{--with-catgets} option causes the
1761 build procedure to use the host's @code{catgets} in this situation.
1763 @item --with-libiconv-prefix=@var{dir}
1764 Search for libiconv header files in @file{@var{dir}/include} and
1765 libiconv library files in @file{@var{dir}/lib}.
1767 @item --enable-obsolete
1768 Enable configuration for an obsoleted system. If you attempt to
1769 configure GCC for a system (build, host, or target) which has been
1770 obsoleted, and you do not specify this flag, configure will halt with an
1773 All support for systems which have been obsoleted in one release of GCC
1774 is removed entirely in the next major release, unless someone steps
1775 forward to maintain the port.
1777 @item --enable-decimal-float
1778 @itemx --enable-decimal-float=yes
1779 @itemx --enable-decimal-float=no
1780 @itemx --enable-decimal-float=bid
1781 @itemx --enable-decimal-float=dpd
1782 @itemx --disable-decimal-float
1783 Enable (or disable) support for the C decimal floating point extension
1784 that is in the IEEE 754-2008 standard. This is enabled by default only
1785 on PowerPC, i386, and x86_64 GNU/Linux systems. Other systems may also
1786 support it, but require the user to specifically enable it. You can
1787 optionally control which decimal floating point format is used (either
1788 @samp{bid} or @samp{dpd}). The @samp{bid} (binary integer decimal)
1789 format is default on i386 and x86_64 systems, and the @samp{dpd}
1790 (densely packed decimal) format is default on PowerPC systems.
1792 @item --enable-fixed-point
1793 @itemx --disable-fixed-point
1794 Enable (or disable) support for C fixed-point arithmetic.
1795 This option is enabled by default for some targets (such as MIPS) which
1796 have hardware-support for fixed-point operations. On other targets, you
1797 may enable this option manually.
1799 @item --with-long-double-128
1800 Specify if @code{long double} type should be 128-bit by default on selected
1801 GNU/Linux architectures. If using @code{--without-long-double-128},
1802 @code{long double} will be by default 64-bit, the same as @code{double} type.
1803 When neither of these configure options are used, the default will be
1804 128-bit @code{long double} when built against GNU C Library 2.4 and later,
1805 64-bit @code{long double} otherwise.
1807 @item --with-gmp=@var{pathname}
1808 @itemx --with-gmp-include=@var{pathname}
1809 @itemx --with-gmp-lib=@var{pathname}
1810 @itemx --with-mpfr=@var{pathname}
1811 @itemx --with-mpfr-include=@var{pathname}
1812 @itemx --with-mpfr-lib=@var{pathname}
1813 @itemx --with-mpc=@var{pathname}
1814 @itemx --with-mpc-include=@var{pathname}
1815 @itemx --with-mpc-lib=@var{pathname}
1816 If you want to build GCC but do not have the GMP library, the MPFR
1817 library and/or the MPC library installed in a standard location and
1818 do not have their sources present in the GCC source tree then you
1819 can explicitly specify the directory where they are installed
1820 (@samp{--with-gmp=@var{gmpinstalldir}},
1821 @samp{--with-mpfr=@/@var{mpfrinstalldir}},
1822 @samp{--with-mpc=@/@var{mpcinstalldir}}). The
1823 @option{--with-gmp=@/@var{gmpinstalldir}} option is shorthand for
1824 @option{--with-gmp-lib=@/@var{gmpinstalldir}/lib} and
1825 @option{--with-gmp-include=@/@var{gmpinstalldir}/include}. Likewise the
1826 @option{--with-mpfr=@/@var{mpfrinstalldir}} option is shorthand for
1827 @option{--with-mpfr-lib=@/@var{mpfrinstalldir}/lib} and
1828 @option{--with-mpfr-include=@/@var{mpfrinstalldir}/include}, also the
1829 @option{--with-mpc=@/@var{mpcinstalldir}} option is shorthand for
1830 @option{--with-mpc-lib=@/@var{mpcinstalldir}/lib} and
1831 @option{--with-mpc-include=@/@var{mpcinstalldir}/include}. If these
1832 shorthand assumptions are not correct, you can use the explicit
1833 include and lib options directly. You might also need to ensure the
1834 shared libraries can be found by the dynamic linker when building and
1835 using GCC, for example by setting the runtime shared library path
1836 variable (@env{LD_LIBRARY_PATH} on GNU/Linux and Solaris systems).
1838 These flags are applicable to the host platform only. When building
1839 a cross compiler, they will not be used to configure target libraries.
1841 @item --with-isl=@var{pathname}
1842 @itemx --with-isl-include=@var{pathname}
1843 @itemx --with-isl-lib=@var{pathname}
1844 If you do not have the ISL library installed in a standard location and you
1845 want to build GCC, you can explicitly specify the directory where it is
1846 installed (@samp{--with-isl=@/@var{islinstalldir}}). The
1847 @option{--with-isl=@/@var{islinstalldir}} option is shorthand for
1848 @option{--with-isl-lib=@/@var{islinstalldir}/lib} and
1849 @option{--with-isl-include=@/@var{islinstalldir}/include}. If this
1850 shorthand assumption is not correct, you can use the explicit
1851 include and lib options directly.
1853 These flags are applicable to the host platform only. When building
1854 a cross compiler, they will not be used to configure target libraries.
1856 @item --with-host-libstdcxx=@var{linker-args}
1857 If you are linking with a static copy of PPL, you can use this option
1858 to specify how the linker should find the standard C++ library used
1859 internally by PPL. Typical values of @var{linker-args} might be
1860 @samp{-lstdc++} or @samp{-Wl,-Bstatic,-lstdc++,-Bdynamic -lm}. If you are
1861 linking with a shared copy of PPL, you probably do not need this
1862 option; shared library dependencies will cause the linker to search
1863 for the standard C++ library automatically.
1865 @item --with-stage1-ldflags=@var{flags}
1866 This option may be used to set linker flags to be used when linking
1867 stage 1 of GCC. These are also used when linking GCC if configured with
1868 @option{--disable-bootstrap}. By default no special flags are used.
1870 @item --with-stage1-libs=@var{libs}
1871 This option may be used to set libraries to be used when linking stage 1
1872 of GCC. These are also used when linking GCC if configured with
1873 @option{--disable-bootstrap}. The default is the argument to
1874 @option{--with-host-libstdcxx}, if specified.
1876 @item --with-boot-ldflags=@var{flags}
1877 This option may be used to set linker flags to be used when linking
1878 stage 2 and later when bootstrapping GCC. If neither --with-boot-libs
1879 nor --with-host-libstdcxx is set to a value, then the default is
1880 @samp{-static-libstdc++ -static-libgcc}.
1882 @item --with-boot-libs=@var{libs}
1883 This option may be used to set libraries to be used when linking stage 2
1884 and later when bootstrapping GCC. The default is the argument to
1885 @option{--with-host-libstdcxx}, if specified.
1887 @item --with-debug-prefix-map=@var{map}
1888 Convert source directory names using @option{-fdebug-prefix-map} when
1889 building runtime libraries. @samp{@var{map}} is a space-separated
1890 list of maps of the form @samp{@var{old}=@var{new}}.
1892 @item --enable-linker-build-id
1893 Tells GCC to pass @option{--build-id} option to the linker for all final
1894 links (links performed without the @option{-r} or @option{--relocatable}
1895 option), if the linker supports it. If you specify
1896 @option{--enable-linker-build-id}, but your linker does not
1897 support @option{--build-id} option, a warning is issued and the
1898 @option{--enable-linker-build-id} option is ignored. The default is off.
1900 @item --with-linker-hash-style=@var{choice}
1901 Tells GCC to pass @option{--hash-style=@var{choice}} option to the
1902 linker for all final links. @var{choice} can be one of
1903 @samp{sysv}, @samp{gnu}, and @samp{both} where @samp{sysv} is the default.
1905 @item --enable-gnu-unique-object
1906 @itemx --disable-gnu-unique-object
1907 Tells GCC to use the gnu_unique_object relocation for C++ template
1908 static data members and inline function local statics. Enabled by
1909 default for a toolchain with an assembler that accepts it and
1910 GLIBC 2.11 or above, otherwise disabled.
1912 @item --with-diagnostics-color=@var{choice}
1913 Tells GCC to use @var{choice} as the default for @option{-fdiagnostics-color=}
1914 option (if not used explicitly on the command line). @var{choice}
1915 can be one of @samp{never}, @samp{auto}, @samp{always}, and @samp{auto-if-env}
1916 where @samp{auto} is the default. @samp{auto-if-env} means that
1917 @option{-fdiagnostics-color=auto} will be the default if @code{GCC_COLORS}
1918 is present and non-empty in the environment, and
1919 @option{-fdiagnostics-color=never} otherwise.
1922 @itemx --disable-lto
1923 Enable support for link-time optimization (LTO). This is enabled by
1924 default, and may be disabled using @option{--disable-lto}.
1926 @item --enable-linker-plugin-configure-flags=FLAGS
1927 @itemx --enable-linker-plugin-flags=FLAGS
1928 By default, linker plugins (such as the LTO plugin) are built for the
1929 host system architecture. For the case that the linker has a
1930 different (but run-time compatible) architecture, these flags can be
1931 specified to build plugins that are compatible to the linker. For
1932 example, if you are building GCC for a 64-bit x86_64
1933 (@samp{x86_64-unknown-linux-gnu}) host system, but have a 32-bit x86
1934 GNU/Linux (@samp{i686-pc-linux-gnu}) linker executable (which is
1935 executable on the former system), you can configure GCC as follows for
1936 getting compatible linker plugins:
1939 % @var{srcdir}/configure \
1940 --host=x86_64-unknown-linux-gnu \
1941 --enable-linker-plugin-configure-flags=--host=i686-pc-linux-gnu \
1942 --enable-linker-plugin-flags='CC=gcc\ -m32\ -Wl,-rpath,[...]/i686-pc-linux-gnu/lib'
1945 @item --with-plugin-ld=@var{pathname}
1946 Enable an alternate linker to be used at link-time optimization (LTO)
1947 link time when @option{-fuse-linker-plugin} is enabled.
1948 This linker should have plugin support such as gold starting with
1949 version 2.20 or GNU ld starting with version 2.21.
1950 See @option{-fuse-linker-plugin} for details.
1952 @item --enable-canonical-system-headers
1953 @itemx --disable-canonical-system-headers
1954 Enable system header path canonicalization for @file{libcpp}. This can
1955 produce shorter header file paths in diagnostics and dependency output
1956 files, but these changed header paths may conflict with some compilation
1957 environments. Enabled by default, and may be disabled using
1958 @option{--disable-canonical-system-headers}.
1960 @item --with-glibc-version=@var{major}.@var{minor}
1961 Tell GCC that when the GNU C Library (glibc) is used on the target it
1962 will be version @var{major}.@var{minor} or later. Normally this can
1963 be detected from the C library's header files, but this option may be
1964 needed when bootstrapping a cross toolchain without the header files
1965 available for building the initial bootstrap compiler.
1967 If GCC is configured with some multilibs that use glibc and some that
1968 do not, this option applies only to the multilibs that use glibc.
1969 However, such configurations may not work well as not all the relevant
1970 configuration in GCC is on a per-multilib basis.
1972 @item --enable-as-accelerator-for=@var{target}
1973 Build as offload target compiler. Specify offload host triple by @var{target}.
1975 @item --enable-offload-targets=@var{target1}[=@var{path1}],@dots{},@var{targetN}[=@var{pathN}]
1976 Enable offloading to targets @var{target1}, @dots{}, @var{targetN}.
1977 Offload compilers are expected to be already installed. Default search
1978 path for them is @file{@var{exec-prefix}}, but it can be changed by
1979 specifying paths @var{path1}, @dots{}, @var{pathN}.
1982 % @var{srcdir}/configure \
1983 --enable-offload-target=i686-unknown-linux-gnu=/path/to/i686/compiler,x86_64-pc-linux-gnu
1987 @subheading Cross-Compiler-Specific Options
1988 The following options only apply to building cross compilers.
1991 @item --with-sysroot
1992 @itemx --with-sysroot=@var{dir}
1993 Tells GCC to consider @var{dir} as the root of a tree that contains
1994 (a subset of) the root filesystem of the target operating system.
1995 Target system headers, libraries and run-time object files will be
1996 searched for in there. More specifically, this acts as if
1997 @option{--sysroot=@var{dir}} was added to the default options of the built
1998 compiler. The specified directory is not copied into the
1999 install tree, unlike the options @option{--with-headers} and
2000 @option{--with-libs} that this option obsoletes. The default value,
2001 in case @option{--with-sysroot} is not given an argument, is
2002 @option{$@{gcc_tooldir@}/sys-root}. If the specified directory is a
2003 subdirectory of @option{$@{exec_prefix@}}, then it will be found relative to
2004 the GCC binaries if the installation tree is moved.
2006 This option affects the system root for the compiler used to build
2007 target libraries (which runs on the build system) and the compiler newly
2008 installed with @code{make install}; it does not affect the compiler which is
2009 used to build GCC itself.
2011 If you specify the @option{--with-native-system-header-dir=@var{dirname}}
2012 option then the compiler will search that directory within @var{dirname} for
2013 native system headers rather than the default @file{/usr/include}.
2015 @item --with-build-sysroot
2016 @itemx --with-build-sysroot=@var{dir}
2017 Tells GCC to consider @var{dir} as the system root (see
2018 @option{--with-sysroot}) while building target libraries, instead of
2019 the directory specified with @option{--with-sysroot}. This option is
2020 only useful when you are already using @option{--with-sysroot}. You
2021 can use @option{--with-build-sysroot} when you are configuring with
2022 @option{--prefix} set to a directory that is different from the one in
2023 which you are installing GCC and your target libraries.
2025 This option affects the system root for the compiler used to build
2026 target libraries (which runs on the build system); it does not affect
2027 the compiler which is used to build GCC itself.
2029 If you specify the @option{--with-native-system-header-dir=@var{dirname}}
2030 option then the compiler will search that directory within @var{dirname} for
2031 native system headers rather than the default @file{/usr/include}.
2033 @item --with-headers
2034 @itemx --with-headers=@var{dir}
2035 Deprecated in favor of @option{--with-sysroot}.
2036 Specifies that target headers are available when building a cross compiler.
2037 The @var{dir} argument specifies a directory which has the target include
2038 files. These include files will be copied into the @file{gcc} install
2039 directory. @emph{This option with the @var{dir} argument is required} when
2040 building a cross compiler, if @file{@var{prefix}/@var{target}/sys-include}
2041 doesn't pre-exist. If @file{@var{prefix}/@var{target}/sys-include} does
2042 pre-exist, the @var{dir} argument may be omitted. @command{fixincludes}
2043 will be run on these files to make them compatible with GCC@.
2045 @item --without-headers
2046 Tells GCC not use any target headers from a libc when building a cross
2047 compiler. When crossing to GNU/Linux, you need the headers so GCC
2048 can build the exception handling for libgcc.
2051 @itemx --with-libs="@var{dir1} @var{dir2} @dots{} @var{dirN}"
2052 Deprecated in favor of @option{--with-sysroot}.
2053 Specifies a list of directories which contain the target runtime
2054 libraries. These libraries will be copied into the @file{gcc} install
2055 directory. If the directory list is omitted, this option has no
2059 Specifies that @samp{newlib} is
2060 being used as the target C library. This causes @code{__eprintf} to be
2061 omitted from @file{libgcc.a} on the assumption that it will be provided by
2064 @item --with-avrlibc
2065 Specifies that @samp{AVR-Libc} is
2066 being used as the target C library. This causes float support
2067 functions like @code{__addsf3} to be omitted from @file{libgcc.a} on
2068 the assumption that it will be provided by @file{libm.a}. For more
2069 technical details, cf. @uref{http://gcc.gnu.org/PR54461,,PR54461}.
2070 This option is only supported for the AVR target. It is not supported for
2071 RTEMS configurations, which currently use newlib. The option is
2072 supported since version 4.7.2 and is the default in 4.8.0 and newer.
2074 @item --with-nds32-lib=@var{library}
2075 Specifies that @var{library} setting is used for building @file{libgcc.a}.
2076 Currently, the valid @var{library} is @samp{newlib} or @samp{mculib}.
2077 This option is only supported for the NDS32 target.
2079 @item --with-build-time-tools=@var{dir}
2080 Specifies where to find the set of target tools (assembler, linker, etc.)
2081 that will be used while building GCC itself. This option can be useful
2082 if the directory layouts are different between the system you are building
2083 GCC on, and the system where you will deploy it.
2085 For example, on an @samp{ia64-hp-hpux} system, you may have the GNU
2086 assembler and linker in @file{/usr/bin}, and the native tools in a
2087 different path, and build a toolchain that expects to find the
2088 native tools in @file{/usr/bin}.
2090 When you use this option, you should ensure that @var{dir} includes
2091 @command{ar}, @command{as}, @command{ld}, @command{nm},
2092 @command{ranlib} and @command{strip} if necessary, and possibly
2093 @command{objdump}. Otherwise, GCC may use an inconsistent set of
2097 @subheading Java-Specific Options
2099 The following option applies to the build of the Java front end.
2102 @item --disable-libgcj
2103 Specify that the run-time libraries
2104 used by GCJ should not be built. This is useful in case you intend
2105 to use GCJ with some other run-time, or you're going to install it
2106 separately, or it just happens not to build on your particular
2107 machine. In general, if the Java front end is enabled, the GCJ
2108 libraries will be enabled too, unless they're known to not work on
2109 the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
2110 may need to port it; in this case, before modifying the top-level
2111 @file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
2112 you may use @option{--enable-libgcj} to override the default.
2116 The following options apply to building @samp{libgcj}.
2118 @subsubheading General Options
2121 @item --enable-java-maintainer-mode
2122 By default the @samp{libjava} build will not attempt to compile the
2123 @file{.java} source files to @file{.class}. Instead, it will use the
2124 @file{.class} files from the source tree. If you use this option you
2125 must have executables named @command{ecj1} and @command{gjavah} in your path
2126 for use by the build. You must use this option if you intend to
2127 modify any @file{.java} files in @file{libjava}.
2129 @item --with-java-home=@var{dirname}
2130 This @samp{libjava} option overrides the default value of the
2131 @samp{java.home} system property. It is also used to set
2132 @samp{sun.boot.class.path} to @file{@var{dirname}/lib/rt.jar}. By
2133 default @samp{java.home} is set to @file{@var{prefix}} and
2134 @samp{sun.boot.class.path} to
2135 @file{@var{datadir}/java/libgcj-@var{version}.jar}.
2137 @item --with-ecj-jar=@var{filename}
2138 This option can be used to specify the location of an external jar
2139 file containing the Eclipse Java compiler. A specially modified
2140 version of this compiler is used by @command{gcj} to parse
2141 @file{.java} source files. If this option is given, the
2142 @samp{libjava} build will create and install an @file{ecj1} executable
2143 which uses this jar file at runtime.
2145 If this option is not given, but an @file{ecj.jar} file is found in
2146 the topmost source tree at configure time, then the @samp{libgcj}
2147 build will create and install @file{ecj1}, and will also install the
2148 discovered @file{ecj.jar} into a suitable place in the install tree.
2150 If @file{ecj1} is not installed, then the user will have to supply one
2151 on his path in order for @command{gcj} to properly parse @file{.java}
2152 source files. A suitable jar is available from
2153 @uref{ftp://sourceware.org/pub/java/}.
2155 @item --disable-getenv-properties
2156 Don't set system properties from @env{GCJ_PROPERTIES}.
2158 @item --enable-hash-synchronization
2159 Use a global hash table for monitor locks. Ordinarily,
2160 @samp{libgcj}'s @samp{configure} script automatically makes
2161 the correct choice for this option for your platform. Only use
2162 this if you know you need the library to be configured differently.
2164 @item --enable-interpreter
2165 Enable the Java interpreter. The interpreter is automatically
2166 enabled by default on all platforms that support it. This option
2167 is really only useful if you want to disable the interpreter
2168 (using @option{--disable-interpreter}).
2170 @item --disable-java-net
2171 Disable java.net. This disables the native part of java.net only,
2172 using non-functional stubs for native method implementations.
2174 @item --disable-jvmpi
2175 Disable JVMPI support.
2177 @item --disable-libgcj-bc
2178 Disable BC ABI compilation of certain parts of libgcj. By default,
2179 some portions of libgcj are compiled with @option{-findirect-dispatch}
2180 and @option{-fno-indirect-classes}, allowing them to be overridden at
2183 If @option{--disable-libgcj-bc} is specified, libgcj is built without
2184 these options. This allows the compile-time linker to resolve
2185 dependencies when statically linking to libgcj. However it makes it
2186 impossible to override the affected portions of libgcj at run-time.
2188 @item --enable-reduced-reflection
2189 Build most of libgcj with @option{-freduced-reflection}. This reduces
2190 the size of libgcj at the expense of not being able to do accurate
2191 reflection on the classes it contains. This option is safe if you
2192 know that code using libgcj will never use reflection on the standard
2193 runtime classes in libgcj (including using serialization, RMI or CORBA).
2196 Enable runtime eCos target support.
2198 @item --without-libffi
2199 Don't use @samp{libffi}. This will disable the interpreter and JNI
2200 support as well, as these require @samp{libffi} to work.
2202 @item --enable-libgcj-debug
2203 Enable runtime debugging code.
2205 @item --enable-libgcj-multifile
2206 If specified, causes all @file{.java} source files to be
2207 compiled into @file{.class} files in one invocation of
2208 @samp{gcj}. This can speed up build time, but is more
2209 resource-intensive. If this option is unspecified or
2210 disabled, @samp{gcj} is invoked once for each @file{.java}
2211 file to compile into a @file{.class} file.
2213 @item --with-libiconv-prefix=DIR
2214 Search for libiconv in @file{DIR/include} and @file{DIR/lib}.
2216 @item --enable-sjlj-exceptions
2217 Force use of the @code{setjmp}/@code{longjmp}-based scheme for exceptions.
2218 @samp{configure} ordinarily picks the correct value based on the platform.
2219 Only use this option if you are sure you need a different setting.
2221 @item --with-system-zlib
2222 Use installed @samp{zlib} rather than that included with GCC@.
2224 @item --with-win32-nlsapi=ansi, unicows or unicode
2225 Indicates how MinGW @samp{libgcj} translates between UNICODE
2226 characters and the Win32 API@.
2228 @item --enable-java-home
2229 If enabled, this creates a JPackage compatible SDK environment during install.
2230 Note that if --enable-java-home is used, --with-arch-directory=ARCH must also
2233 @item --with-arch-directory=ARCH
2234 Specifies the name to use for the @file{jre/lib/ARCH} directory in the SDK
2235 environment created when --enable-java-home is passed. Typical names for this
2236 directory include i386, amd64, ia64, etc.
2238 @item --with-os-directory=DIR
2239 Specifies the OS directory for the SDK include directory. This is set to auto
2240 detect, and is typically 'linux'.
2242 @item --with-origin-name=NAME
2243 Specifies the JPackage origin name. This defaults to the 'gcj' in
2246 @item --with-arch-suffix=SUFFIX
2247 Specifies the suffix for the sdk directory. Defaults to the empty string.
2248 Examples include '.x86_64' in 'java-1.5.0-gcj-1.5.0.0.x86_64'.
2250 @item --with-jvm-root-dir=DIR
2251 Specifies where to install the SDK. Default is $(prefix)/lib/jvm.
2253 @item --with-jvm-jar-dir=DIR
2254 Specifies where to install jars. Default is $(prefix)/lib/jvm-exports.
2256 @item --with-python-dir=DIR
2257 Specifies where to install the Python modules used for aot-compile. DIR should
2258 not include the prefix used in installation. For example, if the Python modules
2259 are to be installed in /usr/lib/python2.5/site-packages, then
2260 --with-python-dir=/lib/python2.5/site-packages should be passed. If this is
2261 not specified, then the Python modules are installed in $(prefix)/share/python.
2263 @item --enable-aot-compile-rpm
2264 Adds aot-compile-rpm to the list of installed scripts.
2266 @item --enable-browser-plugin
2267 Build the gcjwebplugin web browser plugin.
2269 @item --enable-static-libjava
2270 Build static libraries in libjava. The default is to only build shared
2275 Use the single-byte @code{char} and the Win32 A functions natively,
2276 translating to and from UNICODE when using these functions. If
2277 unspecified, this is the default.
2280 Use the @code{WCHAR} and Win32 W functions natively. Adds
2281 @code{-lunicows} to @file{libgcj.spec} to link with @samp{libunicows}.
2282 @file{unicows.dll} needs to be deployed on Microsoft Windows 9X machines
2283 running built executables. @file{libunicows.a}, an open-source
2284 import library around Microsoft's @code{unicows.dll}, is obtained from
2285 @uref{http://libunicows.sourceforge.net/}, which also gives details
2286 on getting @file{unicows.dll} from Microsoft.
2289 Use the @code{WCHAR} and Win32 W functions natively. Does @emph{not}
2290 add @code{-lunicows} to @file{libgcj.spec}. The built executables will
2291 only run on Microsoft Windows NT and above.
2295 @subsubheading AWT-Specific Options
2299 Use the X Window System.
2301 @item --enable-java-awt=PEER(S)
2302 Specifies the AWT peer library or libraries to build alongside
2303 @samp{libgcj}. If this option is unspecified or disabled, AWT
2304 will be non-functional. Current valid values are @option{gtk} and
2305 @option{xlib}. Multiple libraries should be separated by a
2306 comma (i.e.@: @option{--enable-java-awt=gtk,xlib}).
2308 @item --enable-gtk-cairo
2309 Build the cairo Graphics2D implementation on GTK@.
2311 @item --enable-java-gc=TYPE
2312 Choose garbage collector. Defaults to @option{boehm} if unspecified.
2314 @item --disable-gtktest
2315 Do not try to compile and run a test GTK+ program.
2317 @item --disable-glibtest
2318 Do not try to compile and run a test GLIB program.
2320 @item --with-libart-prefix=PFX
2321 Prefix where libart is installed (optional).
2323 @item --with-libart-exec-prefix=PFX
2324 Exec prefix where libart is installed (optional).
2326 @item --disable-libarttest
2327 Do not try to compile and run a test libart program.
2331 @subsubheading Overriding @command{configure} test results
2333 Sometimes, it might be necessary to override the result of some
2334 @command{configure} test, for example in order to ease porting to a new
2335 system or work around a bug in a test. The toplevel @command{configure}
2336 script provides three variables for this:
2340 @item build_configargs
2341 @cindex @code{build_configargs}
2342 The contents of this variable is passed to all build @command{configure}
2345 @item host_configargs
2346 @cindex @code{host_configargs}
2347 The contents of this variable is passed to all host @command{configure}
2350 @item target_configargs
2351 @cindex @code{target_configargs}
2352 The contents of this variable is passed to all target @command{configure}
2357 In order to avoid shell and @command{make} quoting issues for complex
2358 overrides, you can pass a setting for @env{CONFIG_SITE} and set
2359 variables in the site file.
2366 @uref{./index.html,,Return to the GCC Installation page}
2370 @c ***Building****************************************************************
2372 @comment node-name, next, previous, up
2373 @node Building, Testing, Configuration, Installing GCC
2379 @cindex Installing GCC: Building
2381 Now that GCC is configured, you are ready to build the compiler and
2384 Some commands executed when making the compiler may fail (return a
2385 nonzero status) and be ignored by @command{make}. These failures, which
2386 are often due to files that were not found, are expected, and can safely
2389 It is normal to have compiler warnings when compiling certain files.
2390 Unless you are a GCC developer, you can generally ignore these warnings
2391 unless they cause compilation to fail. Developers should attempt to fix
2392 any warnings encountered, however they can temporarily continue past
2393 warnings-as-errors by specifying the configure flag
2394 @option{--disable-werror}.
2396 On certain old systems, defining certain environment variables such as
2397 @env{CC} can interfere with the functioning of @command{make}.
2399 If you encounter seemingly strange errors when trying to build the
2400 compiler in a directory other than the source directory, it could be
2401 because you have previously configured the compiler in the source
2402 directory. Make sure you have done all the necessary preparations.
2404 If you build GCC on a BSD system using a directory stored in an old System
2405 V file system, problems may occur in running @command{fixincludes} if the
2406 System V file system doesn't support symbolic links. These problems
2407 result in a failure to fix the declaration of @code{size_t} in
2408 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
2409 that type mismatches occur, this could be the cause.
2411 The solution is not to use such a directory for building GCC@.
2413 Similarly, when building from SVN or snapshots, or if you modify
2414 @file{*.l} files, you need the Flex lexical analyzer generator
2415 installed. If you do not modify @file{*.l} files, releases contain
2416 the Flex-generated files and you do not need Flex installed to build
2417 them. There is still one Flex-based lexical analyzer (part of the
2418 build machinery, not of GCC itself) that is used even if you only
2419 build the C front end.
2421 When building from SVN or snapshots, or if you modify Texinfo
2422 documentation, you need version 4.7 or later of Texinfo installed if you
2423 want Info documentation to be regenerated. Releases contain Info
2424 documentation pre-built for the unmodified documentation in the release.
2426 @section Building a native compiler
2428 For a native build, the default configuration is to perform
2429 a 3-stage bootstrap of the compiler when @samp{make} is invoked.
2430 This will build the entire GCC system and ensure that it compiles
2431 itself correctly. It can be disabled with the @option{--disable-bootstrap}
2432 parameter to @samp{configure}, but bootstrapping is suggested because
2433 the compiler will be tested more completely and could also have
2436 The bootstrapping process will complete the following steps:
2440 Build tools necessary to build the compiler.
2443 Perform a 3-stage bootstrap of the compiler. This includes building
2444 three times the target tools for use by the compiler such as binutils
2445 (bfd, binutils, gas, gprof, ld, and opcodes) if they have been
2446 individually linked or moved into the top level GCC source tree before
2450 Perform a comparison test of the stage2 and stage3 compilers.
2453 Build runtime libraries using the stage3 compiler from the previous step.
2457 If you are short on disk space you might consider @samp{make
2458 bootstrap-lean} instead. The sequence of compilation is the
2459 same described above, but object files from the stage1 and
2460 stage2 of the 3-stage bootstrap of the compiler are deleted as
2461 soon as they are no longer needed.
2463 If you wish to use non-default GCC flags when compiling the stage2
2464 and stage3 compilers, set @code{BOOT_CFLAGS} on the command line when
2465 doing @samp{make}. For example, if you want to save additional space
2466 during the bootstrap and in the final installation as well, you can
2467 build the compiler binaries without debugging information as in the
2468 following example. This will save roughly 40% of disk space both for
2469 the bootstrap and the final installation. (Libraries will still contain
2470 debugging information.)
2473 make BOOT_CFLAGS='-O' bootstrap
2476 You can place non-default optimization flags into @code{BOOT_CFLAGS}; they
2477 are less well tested here than the default of @samp{-g -O2}, but should
2478 still work. In a few cases, you may find that you need to specify special
2479 flags such as @option{-msoft-float} here to complete the bootstrap; or,
2480 if the native compiler miscompiles the stage1 compiler, you may need
2481 to work around this, by choosing @code{BOOT_CFLAGS} to avoid the parts
2482 of the stage1 compiler that were miscompiled, or by using @samp{make
2483 bootstrap4} to increase the number of stages of bootstrap.
2485 @code{BOOT_CFLAGS} does not apply to bootstrapped target libraries.
2486 Since these are always compiled with the compiler currently being
2487 bootstrapped, you can use @code{CFLAGS_FOR_TARGET} to modify their
2488 compilation flags, as for non-bootstrapped target libraries.
2489 Again, if the native compiler miscompiles the stage1 compiler, you may
2490 need to work around this by avoiding non-working parts of the stage1
2491 compiler. Use @code{STAGE1_TFLAGS} to this end.
2493 If you used the flag @option{--enable-languages=@dots{}} to restrict
2494 the compilers to be built, only those you've actually enabled will be
2495 built. This will of course only build those runtime libraries, for
2496 which the particular compiler has been built. Please note,
2497 that re-defining @env{LANGUAGES} when calling @samp{make}
2498 @strong{does not} work anymore!
2500 If the comparison of stage2 and stage3 fails, this normally indicates
2501 that the stage2 compiler has compiled GCC incorrectly, and is therefore
2502 a potentially serious bug which you should investigate and report. (On
2503 a few systems, meaningful comparison of object files is impossible; they
2504 always appear ``different''. If you encounter this problem, you will
2505 need to disable comparison in the @file{Makefile}.)
2507 If you do not want to bootstrap your compiler, you can configure with
2508 @option{--disable-bootstrap}. In particular cases, you may want to
2509 bootstrap your compiler even if the target system is not the same as
2510 the one you are building on: for example, you could build a
2511 @code{powerpc-unknown-linux-gnu} toolchain on a
2512 @code{powerpc64-unknown-linux-gnu} host. In this case, pass
2513 @option{--enable-bootstrap} to the configure script.
2515 @code{BUILD_CONFIG} can be used to bring in additional customization
2516 to the build. It can be set to a whitespace-separated list of names.
2517 For each such @code{NAME}, top-level @file{config/@code{NAME}.mk} will
2518 be included by the top-level @file{Makefile}, bringing in any settings
2519 it contains. The default @code{BUILD_CONFIG} can be set using the
2520 configure option @option{--with-build-config=@code{NAME}...}. Some
2521 examples of supported build configurations are:
2524 @item @samp{bootstrap-O1}
2525 Removes any @option{-O}-started option from @code{BOOT_CFLAGS}, and adds
2526 @option{-O1} to it. @samp{BUILD_CONFIG=bootstrap-O1} is equivalent to
2527 @samp{BOOT_CFLAGS='-g -O1'}.
2529 @item @samp{bootstrap-O3}
2530 Analogous to @code{bootstrap-O1}.
2532 @item @samp{bootstrap-lto}
2533 Enables Link-Time Optimization for host tools during bootstrapping.
2534 @samp{BUILD_CONFIG=bootstrap-lto} is equivalent to adding
2535 @option{-flto} to @samp{BOOT_CFLAGS}. This option assumes that the host
2536 supports the linker plugin (e.g. GNU ld version 2.21 or later or GNU gold
2537 version 2.21 or later).
2539 @item @samp{bootstrap-lto-noplugin}
2540 This option is similar to @code{bootstrap-lto}, but is intended for
2541 hosts that do not support the linker plugin. Without the linker plugin
2542 static libraries are not compiled with link-time optimizations. Since
2543 the GCC middle end and back end are in @file{libbackend.a} this means
2544 that only the front end is actually LTO optimized.
2546 @item @samp{bootstrap-debug}
2547 Verifies that the compiler generates the same executable code, whether
2548 or not it is asked to emit debug information. To this end, this
2549 option builds stage2 host programs without debug information, and uses
2550 @file{contrib/compare-debug} to compare them with the stripped stage3
2551 object files. If @code{BOOT_CFLAGS} is overridden so as to not enable
2552 debug information, stage2 will have it, and stage3 won't. This option
2553 is enabled by default when GCC bootstrapping is enabled, if
2554 @code{strip} can turn object files compiled with and without debug
2555 info into identical object files. In addition to better test
2556 coverage, this option makes default bootstraps faster and leaner.
2558 @item @samp{bootstrap-debug-big}
2559 Rather than comparing stripped object files, as in
2560 @code{bootstrap-debug}, this option saves internal compiler dumps
2561 during stage2 and stage3 and compares them as well, which helps catch
2562 additional potential problems, but at a great cost in terms of disk
2563 space. It can be specified in addition to @samp{bootstrap-debug}.
2565 @item @samp{bootstrap-debug-lean}
2566 This option saves disk space compared with @code{bootstrap-debug-big},
2567 but at the expense of some recompilation. Instead of saving the dumps
2568 of stage2 and stage3 until the final compare, it uses
2569 @option{-fcompare-debug} to generate, compare and remove the dumps
2570 during stage3, repeating the compilation that already took place in
2571 stage2, whose dumps were not saved.
2573 @item @samp{bootstrap-debug-lib}
2574 This option tests executable code invariance over debug information
2575 generation on target libraries, just like @code{bootstrap-debug-lean}
2576 tests it on host programs. It builds stage3 libraries with
2577 @option{-fcompare-debug}, and it can be used along with any of the
2578 @code{bootstrap-debug} options above.
2580 There aren't @code{-lean} or @code{-big} counterparts to this option
2581 because most libraries are only build in stage3, so bootstrap compares
2582 would not get significant coverage. Moreover, the few libraries built
2583 in stage2 are used in stage3 host programs, so we wouldn't want to
2584 compile stage2 libraries with different options for comparison purposes.
2586 @item @samp{bootstrap-debug-ckovw}
2587 Arranges for error messages to be issued if the compiler built on any
2588 stage is run without the option @option{-fcompare-debug}. This is
2589 useful to verify the full @option{-fcompare-debug} testing coverage. It
2590 must be used along with @code{bootstrap-debug-lean} and
2591 @code{bootstrap-debug-lib}.
2593 @item @samp{bootstrap-time}
2594 Arranges for the run time of each program started by the GCC driver,
2595 built in any stage, to be logged to @file{time.log}, in the top level of
2600 @section Building a cross compiler
2602 When building a cross compiler, it is not generally possible to do a
2603 3-stage bootstrap of the compiler. This makes for an interesting problem
2604 as parts of GCC can only be built with GCC@.
2606 To build a cross compiler, we recommend first building and installing a
2607 native compiler. You can then use the native GCC compiler to build the
2608 cross compiler. The installed native compiler needs to be GCC version
2611 If the cross compiler is to be built with support for the Java
2612 programming language and the ability to compile .java source files is
2613 desired, the installed native compiler used to build the cross
2614 compiler needs to be the same GCC version as the cross compiler. In
2615 addition the cross compiler needs to be configured with
2616 @option{--with-ecj-jar=@dots{}}.
2618 Assuming you have already installed a native copy of GCC and configured
2619 your cross compiler, issue the command @command{make}, which performs the
2624 Build host tools necessary to build the compiler.
2627 Build target tools for use by the compiler such as binutils (bfd,
2628 binutils, gas, gprof, ld, and opcodes)
2629 if they have been individually linked or moved into the top level GCC source
2630 tree before configuring.
2633 Build the compiler (single stage only).
2636 Build runtime libraries using the compiler from the previous step.
2639 Note that if an error occurs in any step the make process will exit.
2641 If you are not building GNU binutils in the same source tree as GCC,
2642 you will need a cross-assembler and cross-linker installed before
2643 configuring GCC@. Put them in the directory
2644 @file{@var{prefix}/@var{target}/bin}. Here is a table of the tools
2645 you should put in this directory:
2649 This should be the cross-assembler.
2652 This should be the cross-linker.
2655 This should be the cross-archiver: a program which can manipulate
2656 archive files (linker libraries) in the target machine's format.
2659 This should be a program to construct a symbol table in an archive file.
2662 The installation of GCC will find these programs in that directory,
2663 and copy or link them to the proper place to for the cross-compiler to
2664 find them when run later.
2666 The easiest way to provide these files is to build the Binutils package.
2667 Configure it with the same @option{--host} and @option{--target}
2668 options that you use for configuring GCC, then build and install
2669 them. They install their executables automatically into the proper
2670 directory. Alas, they do not support all the targets that GCC
2673 If you are not building a C library in the same source tree as GCC,
2674 you should also provide the target libraries and headers before
2675 configuring GCC, specifying the directories with
2676 @option{--with-sysroot} or @option{--with-headers} and
2677 @option{--with-libs}. Many targets also require ``start files'' such
2678 as @file{crt0.o} and
2679 @file{crtn.o} which are linked into each executable. There may be several
2680 alternatives for @file{crt0.o}, for use with profiling or other
2681 compilation options. Check your target's definition of
2682 @code{STARTFILE_SPEC} to find out what start files it uses.
2684 @section Building in parallel
2686 GNU Make 3.80 and above, which is necessary to build GCC, support
2687 building in parallel. To activate this, you can use @samp{make -j 2}
2688 instead of @samp{make}. You can also specify a bigger number, and
2689 in most cases using a value greater than the number of processors in
2690 your machine will result in fewer and shorter I/O latency hits, thus
2691 improving overall throughput; this is especially true for slow drives
2692 and network filesystems.
2694 @section Building the Ada compiler
2696 In order to build GNAT, the Ada compiler, you need a working GNAT
2697 compiler (GCC version 4.0 or later).
2698 This includes GNAT tools such as @command{gnatmake} and
2699 @command{gnatlink}, since the Ada front end is written in Ada and
2700 uses some GNAT-specific extensions.
2702 In order to build a cross compiler, it is suggested to install
2703 the new compiler as native first, and then use it to build the cross
2706 @command{configure} does not test whether the GNAT installation works
2707 and has a sufficiently recent version; if too old a GNAT version is
2708 installed, the build will fail unless @option{--enable-languages} is
2709 used to disable building the Ada front end.
2711 @env{ADA_INCLUDE_PATH} and @env{ADA_OBJECT_PATH} environment variables
2712 must not be set when building the Ada compiler, the Ada tools, or the
2713 Ada runtime libraries. You can check that your build environment is clean
2714 by verifying that @samp{gnatls -v} lists only one explicit path in each
2717 @section Building with profile feedback
2719 It is possible to use profile feedback to optimize the compiler itself. This
2720 should result in a faster compiler binary. Experiments done on x86 using gcc
2721 3.3 showed approximately 7 percent speedup on compiling C programs. To
2722 bootstrap the compiler with profile feedback, use @code{make profiledbootstrap}.
2724 When @samp{make profiledbootstrap} is run, it will first build a @code{stage1}
2725 compiler. This compiler is used to build a @code{stageprofile} compiler
2726 instrumented to collect execution counts of instruction and branch
2727 probabilities. Then runtime libraries are compiled with profile collected.
2728 Finally a @code{stagefeedback} compiler is built using the information collected.
2730 Unlike standard bootstrap, several additional restrictions apply. The
2731 compiler used to build @code{stage1} needs to support a 64-bit integral type.
2732 It is recommended to only use GCC for this.
2739 @uref{./index.html,,Return to the GCC Installation page}
2743 @c ***Testing*****************************************************************
2745 @comment node-name, next, previous, up
2746 @node Testing, Final install, Building, Installing GCC
2750 @chapter Installing GCC: Testing
2753 @cindex Installing GCC: Testing
2756 Before you install GCC, we encourage you to run the testsuites and to
2757 compare your results with results from a similar configuration that have
2758 been submitted to the
2759 @uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
2760 Some of these archived results are linked from the build status lists
2761 at @uref{http://gcc.gnu.org/buildstat.html}, although not everyone who
2762 reports a successful build runs the testsuites and submits the results.
2763 This step is optional and may require you to download additional software,
2764 but it can give you confidence in your new GCC installation or point out
2765 problems before you install and start using your new GCC@.
2767 First, you must have @uref{download.html,,downloaded the testsuites}.
2768 These are part of the full distribution, but if you downloaded the
2769 ``core'' compiler plus any front ends, you must download the testsuites
2772 Second, you must have the testing tools installed. This includes
2773 @uref{http://www.gnu.org/software/dejagnu/,,DejaGnu}, Tcl, and Expect;
2774 the DejaGnu site has links to these.
2776 If the directories where @command{runtest} and @command{expect} were
2777 installed are not in the @env{PATH}, you may need to set the following
2778 environment variables appropriately, as in the following example (which
2779 assumes that DejaGnu has been installed under @file{/usr/local}):
2782 TCL_LIBRARY = /usr/local/share/tcl8.0
2783 DEJAGNULIBS = /usr/local/share/dejagnu
2786 (On systems such as Cygwin, these paths are required to be actual
2787 paths, not mounts or links; presumably this is due to some lack of
2788 portability in the DejaGnu code.)
2791 Finally, you can run the testsuite (which may take a long time):
2793 cd @var{objdir}; make -k check
2796 This will test various components of GCC, such as compiler
2797 front ends and runtime libraries. While running the testsuite, DejaGnu
2798 might emit some harmless messages resembling
2799 @samp{WARNING: Couldn't find the global config file.} or
2800 @samp{WARNING: Couldn't find tool init file} that can be ignored.
2802 If you are testing a cross-compiler, you may want to run the testsuite
2803 on a simulator as described at @uref{http://gcc.gnu.org/simtest-howto.html}.
2805 @section How can you run the testsuite on selected tests?
2807 In order to run sets of tests selectively, there are targets
2808 @samp{make check-gcc} and language specific @samp{make check-c},
2809 @samp{make check-c++}, @samp{make check-fortran}, @samp{make check-java},
2810 @samp{make check-ada}, @samp{make check-objc}, @samp{make check-obj-c++},
2811 @samp{make check-lto}
2812 in the @file{gcc} subdirectory of the object directory. You can also
2813 just run @samp{make check} in a subdirectory of the object directory.
2816 A more selective way to just run all @command{gcc} execute tests in the
2820 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
2823 Likewise, in order to run only the @command{g++} ``old-deja'' tests in
2824 the testsuite with filenames matching @samp{9805*}, you would use
2827 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
2830 The @file{*.exp} files are located in the testsuite directories of the GCC
2831 source, the most important ones being @file{compile.exp},
2832 @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
2833 To get a list of the possible @file{*.exp} files, pipe the
2834 output of @samp{make check} into a file and look at the
2835 @samp{Running @dots{} .exp} lines.
2837 @section Passing options and running multiple testsuites
2839 You can pass multiple options to the testsuite using the
2840 @samp{--target_board} option of DejaGNU, either passed as part of
2841 @samp{RUNTESTFLAGS}, or directly to @command{runtest} if you prefer to
2842 work outside the makefiles. For example,
2845 make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fmerge-constants"
2848 will run the standard @command{g++} testsuites (``unix'' is the target name
2849 for a standard native testsuite situation), passing
2850 @samp{-O3 -fmerge-constants} to the compiler on every test, i.e.,
2851 slashes separate options.
2853 You can run the testsuites multiple times using combinations of options
2854 with a syntax similar to the brace expansion of popular shells:
2857 @dots{}"--target_board=arm-sim\@{-mhard-float,-msoft-float\@}\@{-O1,-O2,-O3,\@}"
2860 (Note the empty option caused by the trailing comma in the final group.)
2861 The following will run each testsuite eight times using the @samp{arm-sim}
2862 target, as if you had specified all possible combinations yourself:
2865 --target_board='arm-sim/-mhard-float/-O1 \
2866 arm-sim/-mhard-float/-O2 \
2867 arm-sim/-mhard-float/-O3 \
2868 arm-sim/-mhard-float \
2869 arm-sim/-msoft-float/-O1 \
2870 arm-sim/-msoft-float/-O2 \
2871 arm-sim/-msoft-float/-O3 \
2872 arm-sim/-msoft-float'
2875 They can be combined as many times as you wish, in arbitrary ways. This
2879 @dots{}"--target_board=unix/-Wextra\@{-O3,-fno-strength\@}\@{-fomit-frame,\@}"
2882 will generate four combinations, all involving @samp{-Wextra}.
2884 The disadvantage to this method is that the testsuites are run in serial,
2885 which is a waste on multiprocessor systems. For users with GNU Make and
2886 a shell which performs brace expansion, you can run the testsuites in
2887 parallel by having the shell perform the combinations and @command{make}
2888 do the parallel runs. Instead of using @samp{--target_board}, use a
2889 special makefile target:
2892 make -j@var{N} check-@var{testsuite}//@var{test-target}/@var{option1}/@var{option2}/@dots{}
2898 make -j3 check-gcc//sh-hms-sim/@{-m1,-m2,-m3,-m3e,-m4@}/@{,-nofpu@}
2901 will run three concurrent ``make-gcc'' testsuites, eventually testing all
2902 ten combinations as described above. Note that this is currently only
2903 supported in the @file{gcc} subdirectory. (To see how this works, try
2904 typing @command{echo} before the example given here.)
2907 @section Additional testing for Java Class Libraries
2909 The Java runtime tests can be executed via @samp{make check}
2910 in the @file{@var{target}/libjava/testsuite} directory in
2913 The @uref{http://sourceware.org/mauve/,,Mauve Project} provides
2914 a suite of tests for the Java Class Libraries. This suite can be run
2915 as part of libgcj testing by placing the Mauve tree within the libjava
2916 testsuite at @file{libjava/testsuite/libjava.mauve/mauve}, or by
2917 specifying the location of that tree when invoking @samp{make}, as in
2918 @samp{make MAUVEDIR=~/mauve check}.
2920 @section How to interpret test results
2922 The result of running the testsuite are various @file{*.sum} and @file{*.log}
2923 files in the testsuite subdirectories. The @file{*.log} files contain a
2924 detailed log of the compiler invocations and the corresponding
2925 results, the @file{*.sum} files summarize the results. These summaries
2926 contain status codes for all tests:
2930 PASS: the test passed as expected
2932 XPASS: the test unexpectedly passed
2934 FAIL: the test unexpectedly failed
2936 XFAIL: the test failed as expected
2938 UNSUPPORTED: the test is not supported on this platform
2940 ERROR: the testsuite detected an error
2942 WARNING: the testsuite detected a possible problem
2945 It is normal for some tests to report unexpected failures. At the
2946 current time the testing harness does not allow fine grained control
2947 over whether or not a test is expected to fail. This problem should
2948 be fixed in future releases.
2951 @section Submitting test results
2953 If you want to report the results to the GCC project, use the
2954 @file{contrib/test_summary} shell script. Start it in the @var{objdir} with
2957 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
2958 -m gcc-testresults@@gcc.gnu.org |sh
2961 This script uses the @command{Mail} program to send the results, so
2962 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
2963 prepended to the testsuite summary and should contain any special
2964 remarks you have on your results or your build environment. Please
2965 do not edit the testsuite result block or the subject line, as these
2966 messages may be automatically processed.
2973 @uref{./index.html,,Return to the GCC Installation page}
2977 @c ***Final install***********************************************************
2979 @comment node-name, next, previous, up
2980 @node Final install, , Testing, Installing GCC
2982 @ifset finalinstallhtml
2984 @chapter Installing GCC: Final installation
2987 Now that GCC has been built (and optionally tested), you can install it with
2989 cd @var{objdir} && make install
2992 We strongly recommend to install into a target directory where there is
2993 no previous version of GCC present. Also, the GNAT runtime should not
2994 be stripped, as this would break certain features of the debugger that
2995 depend on this debugging information (catching Ada exceptions for
2998 That step completes the installation of GCC; user level binaries can
2999 be found in @file{@var{prefix}/bin} where @var{prefix} is the value
3000 you specified with the @option{--prefix} to configure (or
3001 @file{/usr/local} by default). (If you specified @option{--bindir},
3002 that directory will be used instead; otherwise, if you specified
3003 @option{--exec-prefix}, @file{@var{exec-prefix}/bin} will be used.)
3004 Headers for the C++ and Java libraries are installed in
3005 @file{@var{prefix}/include}; libraries in @file{@var{libdir}}
3006 (normally @file{@var{prefix}/lib}); internal parts of the compiler in
3007 @file{@var{libdir}/gcc} and @file{@var{libexecdir}/gcc}; documentation
3008 in info format in @file{@var{infodir}} (normally
3009 @file{@var{prefix}/info}).
3011 When installing cross-compilers, GCC's executables
3012 are not only installed into @file{@var{bindir}}, that
3013 is, @file{@var{exec-prefix}/bin}, but additionally into
3014 @file{@var{exec-prefix}/@var{target-alias}/bin}, if that directory
3015 exists. Typically, such @dfn{tooldirs} hold target-specific
3016 binutils, including assembler and linker.
3018 Installation into a temporary staging area or into a @command{chroot}
3019 jail can be achieved with the command
3022 make DESTDIR=@var{path-to-rootdir} install
3026 where @var{path-to-rootdir} is the absolute path of
3027 a directory relative to which all installation paths will be
3028 interpreted. Note that the directory specified by @code{DESTDIR}
3029 need not exist yet; it will be created if necessary.
3031 There is a subtle point with tooldirs and @code{DESTDIR}:
3032 If you relocate a cross-compiler installation with
3033 e.g.@: @samp{DESTDIR=@var{rootdir}}, then the directory
3034 @file{@var{rootdir}/@var{exec-prefix}/@var{target-alias}/bin} will
3035 be filled with duplicated GCC executables only if it already exists,
3036 it will not be created otherwise. This is regarded as a feature,
3037 not as a bug, because it gives slightly more control to the packagers
3038 using the @code{DESTDIR} feature.
3040 You can install stripped programs and libraries with
3046 If you are bootstrapping a released version of GCC then please
3047 quickly review the build status page for your release, available from
3048 @uref{http://gcc.gnu.org/buildstat.html}.
3049 If your system is not listed for the version of GCC that you built,
3051 @email{gcc@@gcc.gnu.org} indicating
3052 that you successfully built and installed GCC@.
3053 Include the following information:
3057 Output from running @file{@var{srcdir}/config.guess}. Do not send
3058 that file itself, just the one-line output from running it.
3061 The output of @samp{gcc -v} for your newly installed @command{gcc}.
3062 This tells us which version of GCC you built and the options you passed to
3066 Whether you enabled all languages or a subset of them. If you used a
3067 full distribution then this information is part of the configure
3068 options in the output of @samp{gcc -v}, but if you downloaded the
3069 ``core'' compiler plus additional front ends then it isn't apparent
3070 which ones you built unless you tell us about it.
3073 If the build was for GNU/Linux, also include:
3076 The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
3077 this information should be available from @file{/etc/issue}.
3080 The version of the Linux kernel, available from @samp{uname --version}
3084 The version of glibc you used; for RPM-based systems like Red Hat,
3085 Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
3086 and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
3088 For other systems, you can include similar information if you think it is
3092 Any other information that you think would be useful to people building
3093 GCC on the same configuration. The new entry in the build status list
3094 will include a link to the archived copy of your message.
3097 We'd also like to know if the
3099 @ref{Specific, host/target specific installation notes}
3102 @uref{specific.html,,host/target specific installation notes}
3104 didn't include your host/target information or if that information is
3105 incomplete or out of date. Send a note to
3106 @email{gcc@@gcc.gnu.org} detailing how the information should be changed.
3108 If you find a bug, please report it following the
3109 @uref{../bugs/,,bug reporting guidelines}.
3111 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
3112 dvi}. You will need to have @command{texi2dvi} (version at least 4.7)
3113 and @TeX{} installed. This creates a number of @file{.dvi} files in
3114 subdirectories of @file{@var{objdir}}; these may be converted for
3115 printing with programs such as @command{dvips}. Alternately, by using
3116 @samp{make pdf} in place of @samp{make dvi}, you can create documentation
3117 in the form of @file{.pdf} files; this requires @command{texi2pdf}, which
3118 is included with Texinfo version 4.8 and later. You can also
3119 @uref{http://shop.fsf.org/,,buy printed manuals from the
3120 Free Software Foundation}, though such manuals may not be for the most
3121 recent version of GCC@.
3123 If you would like to generate online HTML documentation, do @samp{cd
3124 @var{objdir}; make html} and HTML will be generated for the gcc manuals in
3125 @file{@var{objdir}/gcc/HTML}.
3132 @uref{./index.html,,Return to the GCC Installation page}
3136 @c ***Binaries****************************************************************
3138 @comment node-name, next, previous, up
3139 @node Binaries, Specific, Installing GCC, Top
3143 @chapter Installing GCC: Binaries
3146 @cindex Installing GCC: Binaries
3148 We are often asked about pre-compiled versions of GCC@. While we cannot
3149 provide these for all platforms, below you'll find links to binaries for
3150 various platforms where creating them by yourself is not easy due to various
3153 Please note that we did not create these binaries, nor do we
3154 support them. If you have any problems installing them, please
3155 contact their makers.
3162 @uref{http://www.bullfreeware.com,,Bull's Freeware and Shareware Archive for AIX};
3165 @uref{http://pware.hvcc.edu,,Hudson Valley Community College Open Source Software for IBM System p};
3168 @uref{http://www.perzl.org/aix/,,AIX 5L and 6 Open Source Packages}.
3172 DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}.
3175 Renesas H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
3176 Development Tools for the Renesas H8/300[HS] Series}.
3182 @uref{http://hpux.connect.org.uk/,,HP-UX Porting Center};
3185 @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}.
3189 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
3190 OpenServer/Unixware}.
3193 Solaris 2 (SPARC, Intel):
3196 @uref{http://www.opencsw.org/,,OpenCSW}
3199 @uref{http://jupiterrise.com/tgcware/,,TGCware}
3206 The @uref{http://sourceware.org/cygwin/,,Cygwin} project;
3208 The @uref{http://www.mingw.org/,,MinGW} project.
3212 @uref{ftp://ftp.thewrittenword.com/packages/by-name/,,The
3213 Written Word} offers binaries for
3214 AIX 4.3.3, 5.1 and 5.2,
3216 HP-UX 10.20, 11.00, and 11.11, and
3217 Solaris/SPARC 2.5.1, 2.6, 7, 8, 9 and 10.
3220 @uref{http://www.openpkg.org/,,OpenPKG} offers binaries for quite a
3221 number of platforms.
3224 The @uref{http://gcc.gnu.org/wiki/GFortranBinaries,,GFortran Wiki} has
3225 links to GNU Fortran binaries for several platforms.
3233 @uref{./index.html,,Return to the GCC Installation page}
3237 @c ***Specific****************************************************************
3239 @comment node-name, next, previous, up
3240 @node Specific, Old, Binaries, Top
3244 @chapter Host/target specific installation notes for GCC
3247 @cindex Specific installation notes
3248 @cindex Target specific installation
3249 @cindex Host specific installation
3250 @cindex Target specific installation notes
3252 Please read this document carefully @emph{before} installing the
3253 GNU Compiler Collection on your machine.
3255 Note that this list of install notes is @emph{not} a list of supported
3256 hosts or targets. Not all supported hosts and targets are listed
3257 here, only the ones that require host-specific or target-specific
3258 information have to.
3263 @uref{#aarch64-x-x,,aarch64*-*-*}
3265 @uref{#alpha-x-x,,alpha*-*-*}
3267 @uref{#alpha-dec-osf51,,alpha*-dec-osf5.1}
3269 @uref{#amd64-x-solaris210,,amd64-*-solaris2.10}
3271 @uref{#arm-x-eabi,,arm-*-eabi}
3275 @uref{#bfin,,Blackfin}
3279 @uref{#x-x-freebsd,,*-*-freebsd*}
3281 @uref{#h8300-hms,,h8300-hms}
3283 @uref{#hppa-hp-hpux,,hppa*-hp-hpux*}
3285 @uref{#hppa-hp-hpux10,,hppa*-hp-hpux10}
3287 @uref{#hppa-hp-hpux11,,hppa*-hp-hpux11}
3289 @uref{#x-x-linux-gnu,,*-*-linux-gnu}
3291 @uref{#ix86-x-linux,,i?86-*-linux*}
3293 @uref{#ix86-x-solaris210,,i?86-*-solaris2.10}
3295 @uref{#ia64-x-linux,,ia64-*-linux}
3297 @uref{#ia64-x-hpux,,ia64-*-hpux*}
3299 @uref{#x-ibm-aix,,*-ibm-aix*}
3301 @uref{#iq2000-x-elf,,iq2000-*-elf}
3303 @uref{#lm32-x-elf,,lm32-*-elf}
3305 @uref{#lm32-x-uclinux,,lm32-*-uclinux}
3307 @uref{#m32c-x-elf,,m32c-*-elf}
3309 @uref{#m32r-x-elf,,m32r-*-elf}
3311 @uref{#m68k-x-x,,m68k-*-*}
3313 @uref{#m68k-uclinux,,m68k-uclinux}
3315 @uref{#mep-x-elf,,mep-*-elf}
3317 @uref{#microblaze-x-elf,,microblaze-*-elf}
3319 @uref{#mips-x-x,,mips-*-*}
3321 @uref{#mips-sgi-irix5,,mips-sgi-irix5}
3323 @uref{#mips-sgi-irix6,,mips-sgi-irix6}
3325 @uref{#nds32le-x-elf,,nds32le-*-elf}
3327 @uref{#nds32be-x-elf,,nds32be-*-elf}
3329 @uref{#nvptx-x-none,,nvptx-*-none}
3331 @uref{#powerpc-x-x,,powerpc*-*-*}
3333 @uref{#powerpc-x-darwin,,powerpc-*-darwin*}
3335 @uref{#powerpc-x-elf,,powerpc-*-elf}
3337 @uref{#powerpc-x-linux-gnu,,powerpc*-*-linux-gnu*}
3339 @uref{#powerpc-x-netbsd,,powerpc-*-netbsd*}
3341 @uref{#powerpc-x-eabisim,,powerpc-*-eabisim}
3343 @uref{#powerpc-x-eabi,,powerpc-*-eabi}
3345 @uref{#powerpcle-x-elf,,powerpcle-*-elf}
3347 @uref{#powerpcle-x-eabisim,,powerpcle-*-eabisim}
3349 @uref{#powerpcle-x-eabi,,powerpcle-*-eabi}
3351 @uref{#s390-x-linux,,s390-*-linux*}
3353 @uref{#s390x-x-linux,,s390x-*-linux*}
3355 @uref{#s390x-ibm-tpf,,s390x-ibm-tpf*}
3357 @uref{#x-x-solaris2,,*-*-solaris2*}
3359 @uref{#sparc-x-x,,sparc*-*-*}
3361 @uref{#sparc-sun-solaris2,,sparc-sun-solaris2*}
3363 @uref{#sparc-sun-solaris210,,sparc-sun-solaris2.10}
3365 @uref{#sparc-x-linux,,sparc-*-linux*}
3367 @uref{#sparc64-x-solaris2,,sparc64-*-solaris2*}
3369 @uref{#sparcv9-x-solaris2,,sparcv9-*-solaris2*}
3371 @uref{#c6x-x-x,,c6x-*-*}
3373 @uref{#tilegx-x-linux,,tilegx-*-linux*}
3375 @uref{#tilegxbe-x-linux,,tilegxbe-*-linux*}
3377 @uref{#tilepro-x-linux,,tilepro-*-linux*}
3379 @uref{#visium-x-elf, visium-*-elf}
3381 @uref{#x-x-vxworks,,*-*-vxworks*}
3383 @uref{#x86-64-x-x,,x86_64-*-*, amd64-*-*}
3385 @uref{#x86-64-x-solaris210,,x86_64-*-solaris2.1[0-9]*}
3387 @uref{#xtensa-x-elf,,xtensa*-*-elf}
3389 @uref{#xtensa-x-linux,,xtensa*-*-linux*}
3391 @uref{#windows,,Microsoft Windows}
3393 @uref{#x-x-cygwin,,*-*-cygwin}
3395 @uref{#x-x-interix,,*-*-interix}
3397 @uref{#x-x-mingw32,,*-*-mingw32}
3401 @uref{#older,,Older systems}
3406 @uref{#elf,,all ELF targets} (SVR4, Solaris 2, etc.)
3412 <!-- -------- host/target specific issues start here ---------------- -->
3415 @anchor{aarch64-x-x}
3416 @heading aarch64*-*-*
3417 Binutils pre 2.24 does not have support for selecting @option{-mabi} and
3418 does not support ILP32. If it is used to build GCC 4.9 or later, GCC will
3419 not support option @option{-mabi=ilp32}.
3421 To enable a workaround for the Cortex-A53 erratum number 835769 by default
3422 (for all CPUs regardless of -mcpu option given) at configure time use the
3423 @option{--enable-fix-cortex-a53-835769} option. This will enable the fix by
3424 default and can be explicitly disabled during compilation by passing the
3425 @option{-mno-fix-cortex-a53-835769} option. Conversely,
3426 @option{--disable-fix-cortex-a53-835769} will disable the workaround by
3427 default. The workaround is disabled by default if neither of
3428 @option{--enable-fix-cortex-a53-835769} or
3429 @option{--disable-fix-cortex-a53-835769} is given at configure time.
3431 To enable a workaround for the Cortex-A53 erratum number 843419 by default
3432 (for all CPUs regardless of -mcpu option given) at configure time use the
3433 @option{--enable-fix-cortex-a53-843419} option. This workaround is applied at
3434 link time. Enabling the workaround will cause GCC to pass the relevant option
3435 to the linker. It can be explicitly disabled during compilation by passing the
3436 @option{-mno-fix-cortex-a53-843419} option. Conversely,
3437 @option{--disable-fix-cortex-a53-843419} will disable the workaround by default.
3438 The workaround is disabled by default if neither of
3439 @option{--enable-fix-cortex-a53-843419} or
3440 @option{--disable-fix-cortex-a53-843419} is given at configure time.
3447 This section contains general configuration information for all
3448 alpha-based platforms using ELF (in particular, ignore this section for
3449 DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
3450 section, please read all other sections that match your target.
3452 We require binutils 2.11.2 or newer.
3453 Previous binutils releases had a number of problems with DWARF 2
3454 debugging information, not the least of which is incorrect linking of
3460 @anchor{alpha-dec-osf51}
3461 @heading alpha*-dec-osf5.1
3462 Systems using processors that implement the DEC Alpha architecture and
3463 are running the DEC/Compaq/HP Unix (DEC OSF/1, Digital UNIX, or Compaq/HP
3464 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
3466 Support for Tru64 UNIX V5.1 has been removed in GCC 4.8. As of GCC 4.6,
3467 support for Tru64 UNIX V4.0 and V5.0 has been removed. As of GCC 3.2,
3468 versions before @code{alpha*-dec-osf4} are no longer supported. (These
3469 are the versions which identify themselves as DEC OSF/1.)
3474 @anchor{amd64-x-solaris210}
3475 @heading amd64-*-solaris2.1[0-9]*
3476 This is a synonym for @samp{x86_64-*-solaris2.1[0-9]*}.
3481 @anchor{arc-x-elf32}
3482 @heading arc-*-elf32
3484 Use @samp{configure --target=arc-elf32 --with-cpu=@var{cpu} --enable-languages="c,c++"}
3485 to configure GCC, with @var{cpu} being one of @samp{arc600}, @samp{arc601},
3491 @anchor{arc-linux-uclibc}
3492 @heading arc-linux-uclibc
3494 Use @samp{configure --target=arc-linux-uclibc --with-cpu=arc700 --enable-languages="c,c++"} to configure GCC@.
3501 ARM-family processors. Subtargets that use the ELF object format
3502 require GNU binutils 2.13 or newer. Such subtargets include:
3503 @code{arm-*-netbsdelf}, @code{arm-*-*linux-*}
3504 and @code{arm-*-rtemseabi}.
3511 ATMEL AVR-family micro controllers. These are used in embedded
3512 applications. There are no standard Unix configurations.
3514 @xref{AVR Options,, AVR Options, gcc, Using the GNU Compiler
3518 See ``AVR Options'' in the main manual
3520 for the list of supported MCU types.
3522 Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
3524 Further installation notes and other useful information about AVR tools
3525 can also be obtained from:
3529 @uref{http://www.nongnu.org/avr/,,http://www.nongnu.org/avr/}
3531 @uref{http://www.amelek.gda.pl/avr/,,http://www.amelek.gda.pl/avr/}
3534 We @emph{strongly} recommend using binutils 2.13 or newer.
3536 The following error:
3538 Error: register required
3541 indicates that you should upgrade to a newer version of the binutils.
3548 The Blackfin processor, an Analog Devices DSP.
3550 @xref{Blackfin Options,, Blackfin Options, gcc, Using the GNU Compiler
3554 See ``Blackfin Options'' in the main manual
3557 More information, and a version of binutils with support for this processor,
3558 is available at @uref{http://blackfin.uclinux.org}
3565 The CR16 CompactRISC architecture is a 16-bit architecture. This
3566 architecture is used in embedded applications.
3569 @xref{CR16 Options,, CR16 Options, gcc, Using and Porting the GNU Compiler
3574 See ``CR16 Options'' in the main manual for a list of CR16-specific options.
3577 Use @samp{configure --target=cr16-elf --enable-languages=c,c++} to configure
3578 GCC@ for building a CR16 elf cross-compiler.
3580 Use @samp{configure --target=cr16-uclinux --enable-languages=c,c++} to
3581 configure GCC@ for building a CR16 uclinux cross-compiler.
3588 CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
3589 series. These are used in embedded applications.
3592 @xref{CRIS Options,, CRIS Options, gcc, Using the GNU Compiler
3596 See ``CRIS Options'' in the main manual
3598 for a list of CRIS-specific options.
3600 There are a few different CRIS targets:
3603 Mainly for monolithic embedded systems. Includes a multilib for the
3604 @samp{v10} core used in @samp{ETRAX 100 LX}.
3605 @item cris-axis-linux-gnu
3606 A GNU/Linux port for the CRIS architecture, currently targeting
3607 @samp{ETRAX 100 LX} by default.
3610 For @code{cris-axis-elf} you need binutils 2.11
3611 or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer.
3613 Pre-packaged tools can be obtained from
3614 @uref{ftp://ftp.axis.com/@/pub/@/axis/@/tools/@/cris/@/compiler-kit/}. More
3615 information about this platform is available at
3616 @uref{http://developer.axis.com/}.
3623 Please have a look at the @uref{binaries.html,,binaries page}.
3625 You cannot install GCC by itself on MSDOS; it will not compile under
3626 any MSDOS compiler except itself. You need to get the complete
3627 compilation package DJGPP, which includes binaries as well as sources,
3628 and includes all the necessary compilation tools and libraries.
3633 @anchor{epiphany-x-elf}
3634 @heading epiphany-*-elf
3636 This configuration is intended for embedded systems.
3641 @anchor{x-x-freebsd}
3642 @heading *-*-freebsd*
3643 Support for FreeBSD 1 was discontinued in GCC 3.2. Support for
3644 FreeBSD 2 (and any mutant a.out variants of FreeBSD 3) was
3645 discontinued in GCC 4.0.
3647 In order to better utilize FreeBSD base system functionality and match
3648 the configuration of the system compiler, GCC 4.5 and above as well as
3649 GCC 4.4 past 2010-06-20 leverage SSP support in libc (which is present
3650 on FreeBSD 7 or later) and the use of @code{__cxa_atexit} by default
3651 (on FreeBSD 6 or later). The use of @code{dl_iterate_phdr} inside
3652 @file{libgcc_s.so.1} and boehm-gc (on FreeBSD 7 or later) is enabled
3653 by GCC 4.5 and above.
3655 We support FreeBSD using the ELF file format with DWARF 2 debugging
3656 for all CPU architectures. You may use @option{-gstabs} instead of
3657 @option{-g}, if you really want the old debugging format. There are
3658 no known issues with mixing object files and libraries with different
3659 debugging formats. Otherwise, this release of GCC should now match
3660 more of the configuration used in the stock FreeBSD configuration of
3661 GCC@. In particular, @option{--enable-threads} is now configured by
3662 default. However, as a general user, do not attempt to replace the
3663 system compiler with this release. Known to bootstrap and check with
3664 good results on FreeBSD 7.2-STABLE@. In the past, known to bootstrap
3665 and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4,
3666 4.5, 4.8, 4.9 and 5-CURRENT@.
3668 The version of binutils installed in @file{/usr/bin} probably works
3669 with this release of GCC@. Bootstrapping against the latest GNU
3670 binutils and/or the version found in @file{/usr/ports/devel/binutils} has
3671 been known to enable additional features and improve overall testsuite
3672 results. However, it is currently known that boehm-gc (which itself
3673 is required for java) may not configure properly on FreeBSD prior to
3674 the FreeBSD 7.0 release with GNU binutils after 2.16.1.
3682 This configuration is intended for embedded systems.
3689 Renesas H8/300 series of processors.
3691 Please have a look at the @uref{binaries.html,,binaries page}.
3693 The calling convention and structure layout has changed in release 2.6.
3694 All code must be recompiled. The calling convention now passes the
3695 first three arguments in function calls in registers. Structures are no
3696 longer a multiple of 2 bytes.
3701 @anchor{hppa-hp-hpux}
3702 @heading hppa*-hp-hpux*
3703 Support for HP-UX version 9 and older was discontinued in GCC 3.4.
3705 We require using gas/binutils on all hppa platforms. Version 2.19 or
3706 later is recommended.
3708 It may be helpful to configure GCC with the
3709 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
3710 @option{--with-as=@dots{}} options to ensure that GCC can find GAS@.
3712 The HP assembler should not be used with GCC. It is rarely tested and may
3713 not work. It shouldn't be used with any languages other than C due to its
3716 Specifically, @option{-g} does not work (HP-UX uses a peculiar debugging
3717 format which GCC does not know about). It also inserts timestamps
3718 into each object file it creates, causing the 3-stage comparison test to
3719 fail during a bootstrap. You should be able to continue by saying
3720 @samp{make all-host all-target} after getting the failure from @samp{make}.
3722 Various GCC features are not supported. For example, it does not support weak
3723 symbols or alias definitions. As a result, explicit template instantiations
3724 are required when using C++. This makes it difficult if not impossible to
3725 build many C++ applications.
3727 There are two default scheduling models for instructions. These are
3728 PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
3729 architecture specified for the target machine when configuring.
3730 PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
3731 the target is a @samp{hppa1*} machine.
3733 The PROCESSOR_8000 model is not well suited to older processors. Thus,
3734 it is important to completely specify the machine architecture when
3735 configuring if you want a model other than PROCESSOR_8000. The macro
3736 TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
3737 default scheduling model is desired.
3739 As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10
3740 through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later.
3741 This namespace change might cause problems when bootstrapping with
3742 an earlier version of GCC or the HP compiler as essentially the same
3743 namespace is required for an entire build. This problem can be avoided
3744 in a number of ways. With HP cc, @env{UNIX_STD} can be set to @samp{95}
3745 or @samp{98}. Another way is to add an appropriate set of predefines
3746 to @env{CC}. The description for the @option{munix=} option contains
3747 a list of the predefines used with each standard.
3749 More specific information to @samp{hppa*-hp-hpux*} targets follows.
3754 @anchor{hppa-hp-hpux10}
3755 @heading hppa*-hp-hpux10
3756 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
3757 @code{PHCO_19798} from HP@.
3759 The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces are
3760 used for one-only code and data. This resolves many of the previous
3761 problems in using C++ on this target. However, the ABI is not compatible
3762 with the one implemented under HP-UX 11 using secondary definitions.
3767 @anchor{hppa-hp-hpux11}
3768 @heading hppa*-hp-hpux11
3769 GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot
3770 be used to compile GCC 3.0 and up.
3772 The libffi and libjava libraries haven't been ported to 64-bit HP-UX@
3775 Refer to @uref{binaries.html,,binaries} for information about obtaining
3776 precompiled GCC binaries for HP-UX@. Precompiled binaries must be obtained
3777 to build the Ada language as it can't be bootstrapped using C@. Ada is
3778 only available for the 32-bit PA-RISC runtime.
3780 Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The
3781 bundled compiler supports only traditional C; you will need either HP's
3782 unbundled compiler, or a binary distribution of GCC@.
3784 It is possible to build GCC 3.3 starting with the bundled HP compiler,
3785 but the process requires several steps. GCC 3.3 can then be used to
3786 build later versions. The fastjar program contains ISO C code and
3787 can't be built with the HP bundled compiler. This problem can be
3788 avoided by not building the Java language. For example, use the
3789 @option{--enable-languages="c,c++,f77,objc"} option in your configure
3792 There are several possible approaches to building the distribution.
3793 Binutils can be built first using the HP tools. Then, the GCC
3794 distribution can be built. The second approach is to build GCC
3795 first using the HP tools, then build binutils, then rebuild GCC@.
3796 There have been problems with various binary distributions, so it
3797 is best not to start from a binary distribution.
3799 On 64-bit capable systems, there are two distinct targets. Different
3800 installation prefixes must be used if both are to be installed on
3801 the same system. The @samp{hppa[1-2]*-hp-hpux11*} target generates code
3802 for the 32-bit PA-RISC runtime architecture and uses the HP linker.
3803 The @samp{hppa64-hp-hpux11*} target generates 64-bit code for the
3804 PA-RISC 2.0 architecture.
3806 The script config.guess now selects the target type based on the compiler
3807 detected during configuration. You must define @env{PATH} or @env{CC} so
3808 that configure finds an appropriate compiler for the initial bootstrap.
3809 When @env{CC} is used, the definition should contain the options that are
3810 needed whenever @env{CC} is used.
3812 Specifically, options that determine the runtime architecture must be
3813 in @env{CC} to correctly select the target for the build. It is also
3814 convenient to place many other compiler options in @env{CC}. For example,
3815 @env{CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"}
3816 can be used to bootstrap the GCC 3.3 branch with the HP compiler in
3817 64-bit K&R/bundled mode. The @option{+DA2.0W} option will result in
3818 the automatic selection of the @samp{hppa64-hp-hpux11*} target. The
3819 macro definition table of cpp needs to be increased for a successful
3820 build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to
3821 be defined when building with the bundled compiler, or when using the
3822 @option{-Ac} option. These defines aren't necessary with @option{-Ae}.
3824 It is best to explicitly configure the @samp{hppa64-hp-hpux11*} target
3825 with the @option{--with-ld=@dots{}} option. This overrides the standard
3826 search for ld. The two linkers supported on this target require different
3827 commands. The default linker is determined during configuration. As a
3828 result, it's not possible to switch linkers in the middle of a GCC build.
3829 This has been reported to sometimes occur in unified builds of binutils
3832 A recent linker patch must be installed for the correct operation of
3833 GCC 3.3 and later. @code{PHSS_26559} and @code{PHSS_24304} are the
3834 oldest linker patches that are known to work. They are for HP-UX
3835 11.00 and 11.11, respectively. @code{PHSS_24303}, the companion to
3836 @code{PHSS_24304}, might be usable but it hasn't been tested. These
3837 patches have been superseded. Consult the HP patch database to obtain
3838 the currently recommended linker patch for your system.
3840 The patches are necessary for the support of weak symbols on the
3841 32-bit port, and for the running of initializers and finalizers. Weak
3842 symbols are implemented using SOM secondary definition symbols. Prior
3843 to HP-UX 11, there are bugs in the linker support for secondary symbols.
3844 The patches correct a problem of linker core dumps creating shared
3845 libraries containing secondary symbols, as well as various other
3846 linking issues involving secondary symbols.
3848 GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
3849 run initializers and finalizers on the 64-bit port. The 32-bit port
3850 uses the linker @option{+init} and @option{+fini} options for the same
3851 purpose. The patches correct various problems with the +init/+fini
3852 options, including program core dumps. Binutils 2.14 corrects a
3853 problem on the 64-bit port resulting from HP's non-standard use of
3854 the .init and .fini sections for array initializers and finalizers.
3856 Although the HP and GNU linkers are both supported for the
3857 @samp{hppa64-hp-hpux11*} target, it is strongly recommended that the
3858 HP linker be used for link editing on this target.
3860 At this time, the GNU linker does not support the creation of long
3861 branch stubs. As a result, it can't successfully link binaries
3862 containing branch offsets larger than 8 megabytes. In addition,
3863 there are problems linking shared libraries, linking executables
3864 with @option{-static}, and with dwarf2 unwind and exception support.
3865 It also doesn't provide stubs for internal calls to global functions
3866 in shared libraries, so these calls can't be overloaded.
3868 The HP dynamic loader does not support GNU symbol versioning, so symbol
3869 versioning is not supported. It may be necessary to disable symbol
3870 versioning with @option{--disable-symvers} when using GNU ld.
3872 POSIX threads are the default. The optional DCE thread library is not
3873 supported, so @option{--enable-threads=dce} does not work.
3878 @anchor{x-x-linux-gnu}
3879 @heading *-*-linux-gnu
3880 Versions of libstdc++-v3 starting with 3.2.1 require bug fixes present
3881 in glibc 2.2.5 and later. More information is available in the
3882 libstdc++-v3 documentation.
3887 @anchor{ix86-x-linux}
3888 @heading i?86-*-linux*
3889 As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
3890 See @uref{http://gcc.gnu.org/PR10877,,bug 10877} for more information.
3892 If you receive Signal 11 errors when building on GNU/Linux, then it is
3893 possible you have a hardware problem. Further information on this can be
3894 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
3899 @anchor{ix86-x-solaris210}
3900 @heading i?86-*-solaris2.10
3901 Use this for Solaris 10 or later on x86 and x86-64 systems. Starting
3902 with GCC 4.7, there is also a 64-bit @samp{amd64-*-solaris2.1[0-9]*} or
3903 @samp{x86_64-*-solaris2.1[0-9]*} configuration that corresponds to
3904 @samp{sparcv9-sun-solaris2*}.
3906 It is recommended that you configure GCC to use the GNU assembler, in
3907 @file{/usr/sfw/bin/gas}. The versions included in Solaris 10, from GNU
3908 binutils 2.15, and Solaris 11, from GNU binutils 2.19, work fine,
3909 although the current version, from GNU binutils
3910 2.22, is known to work, too. Recent versions of the Sun assembler in
3911 @file{/usr/ccs/bin/as} work almost as well, though.
3912 @c FIXME: as patch requirements?
3914 For linking, the Sun linker, is preferred. If you want to use the GNU
3915 linker instead, which is available in @file{/usr/sfw/bin/gld}, note that
3916 due to a packaging bug the version in Solaris 10, from GNU binutils
3917 2.15, cannot be used, while the version in Solaris 11, from GNU binutils
3918 2.19, works, as does the latest version, from GNU binutils 2.22.
3920 To use GNU @command{as}, configure with the options
3921 @option{--with-gnu-as --with-as=@//usr/@/sfw/@/bin/@/gas}. It may be necessary
3922 to configure with @option{--without-gnu-ld --with-ld=@//usr/@/ccs/@/bin/@/ld} to
3923 guarantee use of Sun @command{ld}.
3924 @c FIXME: why --without-gnu-ld --with-ld?
3929 @anchor{ia64-x-linux}
3930 @heading ia64-*-linux
3931 IA-64 processor (also known as IPF, or Itanium Processor Family)
3934 If you are using the installed system libunwind library with
3935 @option{--with-system-libunwind}, then you must use libunwind 0.98 or
3938 None of the following versions of GCC has an ABI that is compatible
3939 with any of the other versions in this list, with the exception that
3940 Red Hat 2.96 and Trillian 000171 are compatible with each other:
3941 3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
3942 This primarily affects C++ programs and programs that create shared libraries.
3943 GCC 3.1 or later is recommended for compiling linux, the kernel.
3944 As of version 3.1 GCC is believed to be fully ABI compliant, and hence no
3945 more major ABI changes are expected.
3950 @anchor{ia64-x-hpux}
3951 @heading ia64-*-hpux*
3952 Building GCC on this target requires the GNU Assembler. The bundled HP
3953 assembler will not work. To prevent GCC from using the wrong assembler,
3954 the option @option{--with-gnu-as} may be necessary.
3956 The GCC libunwind library has not been ported to HPUX@. This means that for
3957 GCC versions 3.2.3 and earlier, @option{--enable-libunwind-exceptions}
3958 is required to build GCC@. For GCC 3.3 and later, this is the default.
3959 For gcc 3.4.3 and later, @option{--enable-libunwind-exceptions} is
3960 removed and the system libunwind library will always be used.
3964 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
3968 Support for AIX version 3 and older was discontinued in GCC 3.4.
3969 Support for AIX version 4.2 and older was discontinued in GCC 4.5.
3971 ``out of memory'' bootstrap failures may indicate a problem with
3972 process resource limits (ulimit). Hard limits are configured in the
3973 @file{/etc/security/limits} system configuration file.
3975 GCC can bootstrap with recent versions of IBM XLC, but bootstrapping
3976 with an earlier release of GCC is recommended. Bootstrapping with XLC
3977 requires a larger data segment, which can be enabled through the
3978 @var{LDR_CNTRL} environment variable, e.g.,
3981 % LDR_CNTRL=MAXDATA=0x50000000
3985 One can start with a pre-compiled version of GCC to build from
3986 sources. One may delete GCC's ``fixed'' header files when starting
3987 with a version of GCC built for an earlier release of AIX.
3989 To speed up the configuration phases of bootstrapping and installing GCC,
3990 one may use GNU Bash instead of AIX @command{/bin/sh}, e.g.,
3993 % CONFIG_SHELL=/opt/freeware/bin/bash
3994 % export CONFIG_SHELL
3997 and then proceed as described in @uref{build.html,,the build
3998 instructions}, where we strongly recommend specifying an absolute path
3999 to invoke @var{srcdir}/configure.
4001 Because GCC on AIX is built as a 32-bit executable by default,
4002 (although it can generate 64-bit programs) the GMP and MPFR libraries
4003 required by gfortran must be 32-bit libraries. Building GMP and MPFR
4004 as static archive libraries works better than shared libraries.
4006 Errors involving @code{alloca} when building GCC generally are due
4007 to an incorrect definition of @code{CC} in the Makefile or mixing files
4008 compiled with the native C compiler and GCC@. During the stage1 phase of
4009 the build, the native AIX compiler @strong{must} be invoked as @command{cc}
4010 (not @command{xlc}). Once @command{configure} has been informed of
4011 @command{xlc}, one needs to use @samp{make distclean} to remove the
4012 configure cache files and ensure that @env{CC} environment variable
4013 does not provide a definition that will confuse @command{configure}.
4014 If this error occurs during stage2 or later, then the problem most likely
4015 is the version of Make (see above).
4017 The native @command{as} and @command{ld} are recommended for
4018 bootstrapping on AIX@. The GNU Assembler, GNU Linker, and GNU
4019 Binutils version 2.20 is the minimum level that supports bootstrap on
4020 AIX 5@. The GNU Assembler has not been updated to support AIX 6@ or
4021 AIX 7. The native AIX tools do interoperate with GCC@.
4023 AIX 5.3 TL10, AIX 6.1 TL05 and AIX 7.1 TL00 introduced an AIX
4024 assembler change that sometimes produces corrupt assembly files
4025 causing AIX linker errors. The bug breaks GCC bootstrap on AIX and
4026 can cause compilation failures with existing GCC installations. An
4027 AIX iFix for AIX 5.3 is available (APAR IZ98385 for AIX 5.3 TL10, APAR
4028 IZ98477 for AIX 5.3 TL11 and IZ98134 for AIX 5.3 TL12). AIX 5.3 TL11 SP8,
4029 AIX 5.3 TL12 SP5, AIX 6.1 TL04 SP11, AIX 6.1 TL05 SP7, AIX 6.1 TL06 SP6,
4030 AIX 6.1 TL07 and AIX 7.1 TL01 should include the fix.
4032 Building @file{libstdc++.a} requires a fix for an AIX Assembler bug
4033 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a
4034 fix for another AIX Assembler bug and a co-dependent AIX Archiver fix
4035 referenced as APAR IY53606 (AIX 5.2) or as APAR IY54774 (AIX 5.1)
4037 @anchor{TransferAixShobj}
4038 @samp{libstdc++} in GCC 3.4 increments the major version number of the
4039 shared object and GCC installation places the @file{libstdc++.a}
4040 shared library in a common location which will overwrite the and GCC
4041 3.3 version of the shared library. Applications either need to be
4042 re-linked against the new shared library or the GCC 3.1 and GCC 3.3
4043 versions of the @samp{libstdc++} shared object needs to be available
4044 to the AIX runtime loader. The GCC 3.1 @samp{libstdc++.so.4}, if
4045 present, and GCC 3.3 @samp{libstdc++.so.5} shared objects can be
4046 installed for runtime dynamic loading using the following steps to set
4047 the @samp{F_LOADONLY} flag in the shared object for @emph{each}
4048 multilib @file{libstdc++.a} installed:
4050 Extract the shared objects from the currently installed
4051 @file{libstdc++.a} archive:
4053 % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
4056 Enable the @samp{F_LOADONLY} flag so that the shared object will be
4057 available for runtime dynamic loading, but not linking:
4059 % strip -e libstdc++.so.4 libstdc++.so.5
4062 Archive the runtime-only shared object in the GCC 3.4
4063 @file{libstdc++.a} archive:
4065 % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
4069 @uref{./configure.html#WithAixSoname,,@option{--with-aix-soname=svr4}}
4070 configure option may drop the need for this procedure for libraries that
4073 Linking executables and shared libraries may produce warnings of
4074 duplicate symbols. The assembly files generated by GCC for AIX always
4075 have included multiple symbol definitions for certain global variable
4076 and function declarations in the original program. The warnings should
4077 not prevent the linker from producing a correct library or runnable
4080 AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
4081 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
4082 to parse archive libraries did not handle the new format correctly.
4083 These routines are used by GCC and result in error messages during
4084 linking such as ``not a COFF file''. The version of the routines shipped
4085 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
4086 option of the archive command may be used to create archives of 32-bit
4087 objects using the original ``small format''. A correct version of the
4088 routines is shipped with AIX 4.3.2 and above.
4090 Some versions of the AIX binder (linker) can fail with a relocation
4091 overflow severe error when the @option{-bbigtoc} option is used to link
4092 GCC-produced object files into an executable that overflows the TOC@. A fix
4093 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
4094 available from IBM Customer Support and from its
4095 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
4096 website as PTF U455193.
4098 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
4099 with a segmentation fault when invoked by any version of GCC@. A fix for
4100 APAR IX87327 is available from IBM Customer Support and from its
4101 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
4102 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
4104 The initial assembler shipped with AIX 4.3.0 generates incorrect object
4105 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
4106 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
4107 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
4108 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
4110 AIX provides National Language Support (NLS)@. Compilers and assemblers
4111 use NLS to support locale-specific representations of various data
4112 formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
4113 separating decimal fractions). There have been problems reported where
4114 GCC does not produce the same floating-point formats that the assembler
4115 expects. If one encounters this problem, set the @env{LANG}
4116 environment variable to @samp{C} or @samp{En_US}.
4118 A default can be specified with the @option{-mcpu=@var{cpu_type}}
4119 switch and using the configure option @option{--with-cpu-@var{cpu_type}}.
4124 @anchor{iq2000-x-elf}
4125 @heading iq2000-*-elf
4126 Vitesse IQ2000 processors. These are used in embedded
4127 applications. There are no standard Unix configurations.
4134 Lattice Mico32 processor.
4135 This configuration is intended for embedded systems.
4140 @anchor{lm32-x-uclinux}
4141 @heading lm32-*-uclinux
4142 Lattice Mico32 processor.
4143 This configuration is intended for embedded systems running uClinux.
4150 Renesas M32C processor.
4151 This configuration is intended for embedded systems.
4158 Renesas M32R processor.
4159 This configuration is intended for embedded systems.
4167 @samp{m68k-*-elf*}, @samp{m68k-*-rtems}, @samp{m68k-*-uclinux} and
4169 build libraries for both M680x0 and ColdFire processors. If you only
4170 need the M680x0 libraries, you can omit the ColdFire ones by passing
4171 @option{--with-arch=m68k} to @command{configure}. Alternatively, you
4172 can omit the M680x0 libraries by passing @option{--with-arch=cf} to
4173 @command{configure}. These targets default to 5206 or 5475 code as
4174 appropriate for the target system when
4175 configured with @option{--with-arch=cf} and 68020 code otherwise.
4177 The @samp{m68k-*-netbsd} and
4178 @samp{m68k-*-openbsd} targets also support the @option{--with-arch}
4179 option. They will generate ColdFire CFV4e code when configured with
4180 @option{--with-arch=cf} and 68020 code otherwise.
4182 You can override the default processors listed above by configuring
4183 with @option{--with-cpu=@var{target}}. This @var{target} can either
4184 be a @option{-mcpu} argument or one of the following values:
4185 @samp{m68000}, @samp{m68010}, @samp{m68020}, @samp{m68030},
4186 @samp{m68040}, @samp{m68060}, @samp{m68020-40} and @samp{m68020-60}.
4188 GCC requires at least binutils version 2.17 on these targets.
4193 @anchor{m68k-x-uclinux}
4194 @heading m68k-*-uclinux
4195 GCC 4.3 changed the uClinux configuration so that it uses the
4196 @samp{m68k-linux-gnu} ABI rather than the @samp{m68k-elf} ABI.
4197 It also added improved support for C++ and flat shared libraries,
4198 both of which were ABI changes.
4205 Toshiba Media embedded Processor.
4206 This configuration is intended for embedded systems.
4211 @anchor{microblaze-x-elf}
4212 @heading microblaze-*-elf
4213 Xilinx MicroBlaze processor.
4214 This configuration is intended for embedded systems.
4221 If on a MIPS system you get an error message saying ``does not have gp
4222 sections for all it's [sic] sectons [sic]'', don't worry about it. This
4223 happens whenever you use GAS with the MIPS linker, but there is not
4224 really anything wrong, and it is okay to use the output file. You can
4225 stop such warnings by installing the GNU linker.
4227 It would be nice to extend GAS to produce the gp tables, but they are
4228 optional, and there should not be a warning about their absence.
4230 The libstdc++ atomic locking routines for MIPS targets requires MIPS II
4231 and later. A patch went in just after the GCC 3.3 release to
4232 make @samp{mips*-*-*} use the generic implementation instead. You can also
4233 configure for @samp{mipsel-elf} as a workaround. The
4234 @samp{mips*-*-linux*} target continues to use the MIPS II routines. More
4235 work on this is expected in future releases.
4237 @c If you make --with-llsc the default for another target, please also
4238 @c update the description of the --with-llsc option.
4240 The built-in @code{__sync_*} functions are available on MIPS II and
4241 later systems and others that support the @samp{ll}, @samp{sc} and
4242 @samp{sync} instructions. This can be overridden by passing
4243 @option{--with-llsc} or @option{--without-llsc} when configuring GCC.
4244 Since the Linux kernel emulates these instructions if they are
4245 missing, the default for @samp{mips*-*-linux*} targets is
4246 @option{--with-llsc}. The @option{--with-llsc} and
4247 @option{--without-llsc} configure options may be overridden at compile
4248 time by passing the @option{-mllsc} or @option{-mno-llsc} options to
4251 MIPS systems check for division by zero (unless
4252 @option{-mno-check-zero-division} is passed to the compiler) by
4253 generating either a conditional trap or a break instruction. Using
4254 trap results in smaller code, but is only supported on MIPS II and
4255 later. Also, some versions of the Linux kernel have a bug that
4256 prevents trap from generating the proper signal (@code{SIGFPE}). To enable
4257 the use of break, use the @option{--with-divide=breaks}
4258 @command{configure} option when configuring GCC@. The default is to
4259 use traps on systems that support them.
4261 The assembler from GNU binutils 2.17 and earlier has a bug in the way
4262 it sorts relocations for REL targets (o32, o64, EABI). This can cause
4263 bad code to be generated for simple C++ programs. Also the linker
4264 from GNU binutils versions prior to 2.17 has a bug which causes the
4265 runtime linker stubs in very large programs, like @file{libgcj.so}, to
4266 be incorrectly generated. GNU Binutils 2.18 and later (and snapshots
4267 made after Nov. 9, 2006) should be free from both of these problems.
4272 @anchor{mips-sgi-irix5}
4273 @heading mips-sgi-irix5
4274 Support for IRIX 5 has been removed in GCC 4.6.
4279 @anchor{mips-sgi-irix6}
4280 @heading mips-sgi-irix6
4281 Support for IRIX 6.5 has been removed in GCC 4.8. Support for IRIX 6
4282 releases before 6.5 has been removed in GCC 4.6, as well as support for
4288 @anchor{moxie-x-elf}
4289 @heading moxie-*-elf
4290 The moxie processor.
4295 @anchor{msp430-x-elf}
4296 @heading msp430-*-elf
4297 TI MSP430 processor.
4298 This configuration is intended for embedded systems.
4303 @anchor{nds32le-x-elf}
4304 @heading nds32le-*-elf
4305 Andes NDS32 target in little endian mode.
4310 @anchor{nds32be-x-elf}
4311 @heading nds32be-*-elf
4312 Andes NDS32 target in big endian mode.
4317 @anchor{nvptx-x-none}
4318 @heading nvptx-*-none
4321 Instead of GNU binutils, you will need to install
4322 @uref{https://github.com/MentorEmbedded/nvptx-tools/,,nvptx-tools}.
4323 Tell GCC where to find it:
4324 @option{--with-build-time-tools=[install-nvptx-tools]/nvptx-none/bin}.
4326 A nvptx port of newlib is available at
4327 @uref{https://github.com/MentorEmbedded/nvptx-newlib/,,nvptx-newlib}.
4328 It can be automatically built together with GCC@. For this, add a
4329 symbolic link to nvptx-newlib's @file{newlib} directory to the
4330 directory containing the GCC sources.
4332 Use the @option{--disable-sjlj-exceptions} and
4333 @option{--enable-newlib-io-long-long} options when configuring.
4338 @anchor{powerpc-x-x}
4339 @heading powerpc-*-*
4340 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
4341 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
4344 @uref{ftp://ftp.kernel.org/pub/linux/devel/binutils,,binutils 2.15}
4345 or newer for a working GCC@.
4350 @anchor{powerpc-x-darwin}
4351 @heading powerpc-*-darwin*
4352 PowerPC running Darwin (Mac OS X kernel).
4354 Pre-installed versions of Mac OS X may not include any developer tools,
4355 meaning that you will not be able to build GCC from source. Tool
4356 binaries are available at
4357 @uref{http://opensource.apple.com/}.
4359 This version of GCC requires at least cctools-590.36. The
4360 cctools-590.36 package referenced from
4361 @uref{http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html} will not work
4362 on systems older than 10.3.9 (aka darwin7.9.0).
4367 @anchor{powerpc-x-elf}
4368 @heading powerpc-*-elf
4369 PowerPC system in big endian mode, running System V.4.
4374 @anchor{powerpc-x-linux-gnu}
4375 @heading powerpc*-*-linux-gnu*
4376 PowerPC system in big endian mode running Linux.
4381 @anchor{powerpc-x-netbsd}
4382 @heading powerpc-*-netbsd*
4383 PowerPC system in big endian mode running NetBSD@.
4388 @anchor{powerpc-x-eabisim}
4389 @heading powerpc-*-eabisim
4390 Embedded PowerPC system in big endian mode for use in running under the
4396 @anchor{powerpc-x-eabi}
4397 @heading powerpc-*-eabi
4398 Embedded PowerPC system in big endian mode.
4403 @anchor{powerpcle-x-elf}
4404 @heading powerpcle-*-elf
4405 PowerPC system in little endian mode, running System V.4.
4410 @anchor{powerpcle-x-eabisim}
4411 @heading powerpcle-*-eabisim
4412 Embedded PowerPC system in little endian mode for use in running under
4418 @anchor{powerpcle-x-eabi}
4419 @heading powerpcle-*-eabi
4420 Embedded PowerPC system in little endian mode.
4427 The Renesas RL78 processor.
4428 This configuration is intended for embedded systems.
4435 The Renesas RX processor. See
4436 @uref{http://eu.renesas.com/fmwk.jsp?cnt=rx600_series_landing.jsp&fp=/products/mpumcu/rx_family/rx600_series}
4437 for more information about this processor.
4442 @anchor{s390-x-linux}
4443 @heading s390-*-linux*
4444 S/390 system running GNU/Linux for S/390@.
4449 @anchor{s390x-x-linux}
4450 @heading s390x-*-linux*
4451 zSeries system (64-bit) running GNU/Linux for zSeries@.
4456 @anchor{s390x-ibm-tpf}
4457 @heading s390x-ibm-tpf*
4458 zSeries system (64-bit) running TPF@. This platform is
4459 supported as cross-compilation target only.
4464 @c Please use Solaris 2 to refer to all release of Solaris, starting
4465 @c with 2.0 until 2.6, 7, 8, etc. Solaris 1 was a marketing name for
4466 @c SunOS 4 releases which we don't use to avoid confusion. Solaris
4467 @c alone is too unspecific and must be avoided.
4468 @anchor{x-x-solaris2}
4469 @heading *-*-solaris2*
4470 Support for Solaris 9 has been removed in GCC 4.10. Support for Solaris
4471 8 has been removed in GCC 4.8. Support for Solaris 7 has been removed
4474 Sun does not ship a C compiler with Solaris 2 before Solaris 10, though
4475 you can download the Sun Studio compilers for free. In Solaris 10 and
4476 11, GCC 3.4.3 is available as @command{/usr/sfw/bin/gcc}. Solaris 11
4477 also provides GCC 4.5.2 as @command{/usr/gcc/4.5/bin/gcc}. Alternatively,
4478 you can install a pre-built GCC to bootstrap and install GCC. See the
4479 @uref{binaries.html,,binaries page} for details.
4481 The Solaris 2 @command{/bin/sh} will often fail to configure
4482 @samp{libstdc++-v3}, @samp{boehm-gc} or @samp{libjava}. We therefore
4483 recommend using the following initial sequence of commands
4486 % CONFIG_SHELL=/bin/ksh
4487 % export CONFIG_SHELL
4491 and proceed as described in @uref{configure.html,,the configure instructions}.
4492 In addition we strongly recommend specifying an absolute path to invoke
4493 @command{@var{srcdir}/configure}.
4495 Solaris 2 comes with a number of optional OS packages. Some of these
4496 are needed to use GCC fully, namely @code{SUNWarc},
4497 @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
4498 @code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all
4499 optional packages when installing Solaris 2, you will need to verify that
4500 the packages that GCC needs are installed.
4502 To check whether an optional package is installed, use
4503 the @command{pkginfo} command. To add an optional package, use the
4504 @command{pkgadd} command. For further details, see the Solaris 2
4507 Trying to use the linker and other tools in
4508 @file{/usr/ucb} to install GCC has been observed to cause trouble.
4509 For example, the linker may hang indefinitely. The fix is to remove
4510 @file{/usr/ucb} from your @env{PATH}.
4512 The build process works more smoothly with the legacy Sun tools so, if you
4513 have @file{/usr/xpg4/bin} in your @env{PATH}, we recommend that you place
4514 @file{/usr/bin} before @file{/usr/xpg4/bin} for the duration of the build.
4516 We recommend the use of the Sun assembler or the GNU assembler, in
4517 conjunction with the Sun linker. The GNU @command{as}
4518 versions included in Solaris 10, from GNU binutils 2.15, and Solaris 11,
4519 from GNU binutils 2.19, are known to work. They can be found in
4520 @file{/usr/sfw/bin/gas}. Current versions of GNU binutils (2.22)
4521 are known to work as well. Note that your mileage may vary
4522 if you use a combination of the GNU tools and the Sun tools: while the
4523 combination GNU @command{as} + Sun @command{ld} should reasonably work,
4524 the reverse combination Sun @command{as} + GNU @command{ld} may fail to
4525 build or cause memory corruption at runtime in some cases for C++ programs.
4527 GNU @command{ld} usually works as well, although the version included in
4528 Solaris 10 cannot be used due to several bugs. Again, the current
4529 version (2.22) is known to work, but generally lacks platform specific
4530 features, so better stay with Sun @command{ld}. To use the LTO linker
4531 plugin (@option{-fuse-linker-plugin}) with GNU @command{ld}, GNU
4532 binutils @emph{must} be configured with @option{--enable-largefile}.
4534 To enable symbol versioning in @samp{libstdc++} with Sun @command{ld},
4535 you need to have any version of GNU @command{c++filt}, which is part of
4536 GNU binutils. @samp{libstdc++} symbol versioning will be disabled if no
4537 appropriate version is found. Sun @command{c++filt} from the Sun Studio
4538 compilers does @emph{not} work.
4540 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
4541 newer: @command{g++} will complain that types are missing. These headers
4542 assume that omitting the type means @code{int}; this assumption worked for
4543 C90 but is wrong for C++, and is now wrong for C99 also.
4545 Sun bug 4927647 sometimes causes random spurious testsuite failures
4546 related to missing diagnostic output. This bug doesn't affect GCC
4547 itself, rather it is a kernel bug triggered by the @command{expect}
4548 program which is used only by the GCC testsuite driver. When the bug
4549 causes the @command{expect} program to miss anticipated output, extra
4550 testsuite failures appear.
4557 This section contains general configuration information for all
4558 SPARC-based platforms. In addition to reading this section, please
4559 read all other sections that match your target.
4561 Newer versions of the GNU Multiple Precision Library (GMP), the MPFR
4562 library and the MPC library are known to be miscompiled by earlier
4563 versions of GCC on these platforms. We therefore recommend the use
4564 of the exact versions of these libraries listed as minimal versions
4565 in @uref{prerequisites.html,,the prerequisites}.
4570 @anchor{sparc-sun-solaris2}
4571 @heading sparc-sun-solaris2*
4572 When GCC is configured to use GNU binutils 2.14 or later, the binaries
4573 produced are smaller than the ones produced using Sun's native tools;
4574 this difference is quite significant for binaries containing debugging
4577 Starting with Solaris 7, the operating system is capable of executing
4578 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
4579 this; the @option{-m64} option enables 64-bit code generation.
4580 However, if all you want is code tuned for the UltraSPARC CPU, you
4581 should try the @option{-mtune=ultrasparc} option instead, which produces
4582 code that, unlike full 64-bit code, can still run on non-UltraSPARC
4585 When configuring on a Solaris 7 or later system that is running a kernel
4586 that supports only 32-bit binaries, one must configure with
4587 @option{--disable-multilib}, since we will not be able to build the
4588 64-bit target libraries.
4590 GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of
4591 the GNU compiler (especially GCC 3.0.x versions), which lead to the
4592 miscompilation of the stage1 compiler and the subsequent failure of the
4593 bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary
4594 stage, i.e.@: to bootstrap that compiler with the base compiler and then
4595 use it to bootstrap the final compiler.
4597 GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE Studio 7)
4598 and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a bootstrap
4599 failure in form of a miscompilation of the stage1 compiler by the Sun
4600 compiler. This is Sun bug 4974440. This is fixed with patch 112760-07.
4602 GCC 3.4 changed the default debugging format from Stabs to DWARF-2 for
4603 32-bit code on Solaris 7 and later. If you use the Sun assembler, this
4604 change apparently runs afoul of Sun bug 4910101 (which is referenced as
4605 an x86-only problem by Sun, probably because they do not use DWARF-2).
4606 A symptom of the problem is that you cannot compile C++ programs like
4607 @command{groff} 1.19.1 without getting messages similar to the following:
4610 ld: warning: relocation error: R_SPARC_UA32: @dots{}
4611 external symbolic relocation against non-allocatable section
4612 .debug_info cannot be processed at runtime: relocation ignored.
4616 To work around this problem, compile with @option{-gstabs+} instead of
4619 When configuring the GNU Multiple Precision Library (GMP), the MPFR
4620 library or the MPC library on a Solaris 7 or later system, the canonical
4621 target triplet must be specified as the @command{build} parameter on the
4622 configure line. This target triplet can be obtained by invoking @command{./config.guess} in the toplevel source directory of GCC (and
4623 not that of GMP or MPFR or MPC). For example on a Solaris 9 system:
4626 % ./configure --build=sparc-sun-solaris2.9 --prefix=xxx
4632 @anchor{sparc-sun-solaris210}
4633 @heading sparc-sun-solaris2.10
4634 There is a bug in older versions of the Sun assembler which breaks
4635 thread-local storage (TLS). A typical error message is
4638 ld: fatal: relocation error: R_SPARC_TLS_LE_HIX22: file /var/tmp//ccamPA1v.o:
4639 symbol <unknown>: bad symbol type SECT: symbol type must be TLS
4643 This bug is fixed in Sun patch 118683-03 or later.
4648 @anchor{sparc-x-linux}
4649 @heading sparc-*-linux*
4651 GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
4652 or newer on this platform. All earlier binutils and glibc
4653 releases mishandled unaligned relocations on @code{sparc-*-*} targets.
4659 @anchor{sparc64-x-solaris2}
4660 @heading sparc64-*-solaris2*
4661 When configuring the GNU Multiple Precision Library (GMP), the MPFR
4662 library or the MPC library, the canonical target triplet must be specified
4663 as the @command{build} parameter on the configure line. For example
4664 on a Solaris 9 system:
4667 % ./configure --build=sparc64-sun-solaris2.9 --prefix=xxx
4670 The following compiler flags must be specified in the configure
4671 step in order to bootstrap this target with the Sun compiler:
4674 % CC="cc -xarch=v9 -xildoff" @var{srcdir}/configure [@var{options}] [@var{target}]
4678 @option{-xarch=v9} specifies the SPARC-V9 architecture to the Sun toolchain
4679 and @option{-xildoff} turns off the incremental linker.
4684 @anchor{sparcv9-x-solaris2}
4685 @heading sparcv9-*-solaris2*
4686 This is a synonym for @samp{sparc64-*-solaris2*}.
4693 The C6X family of processors. This port requires binutils-2.22 or newer.
4698 @anchor{tilegx-*-linux}
4699 @heading tilegx-*-linux*
4700 The TILE-Gx processor in little endian mode, running GNU/Linux. This
4701 port requires binutils-2.22 or newer.
4706 @anchor{tilegxbe-*-linux}
4707 @heading tilegxbe-*-linux*
4708 The TILE-Gx processor in big endian mode, running GNU/Linux. This
4709 port requires binutils-2.23 or newer.
4714 @anchor{tilepro-*-linux}
4715 @heading tilepro-*-linux*
4716 The TILEPro processor running GNU/Linux. This port requires
4717 binutils-2.22 or newer.
4722 @anchor{visium-x-elf}
4723 @heading visium-*-elf
4724 CDS VISIUMcore processor.
4725 This configuration is intended for embedded systems.
4730 @anchor{x-x-vxworks}
4731 @heading *-*-vxworks*
4732 Support for VxWorks is in flux. At present GCC supports @emph{only} the
4733 very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC@.
4734 We welcome patches for other architectures supported by VxWorks 5.5.
4735 Support for VxWorks AE would also be welcome; we believe this is merely
4736 a matter of writing an appropriate ``configlette'' (see below). We are
4737 not interested in supporting older, a.out or COFF-based, versions of
4740 VxWorks comes with an older version of GCC installed in
4741 @file{@var{$WIND_BASE}/host}; we recommend you do not overwrite it.
4742 Choose an installation @var{prefix} entirely outside @var{$WIND_BASE}.
4743 Before running @command{configure}, create the directories @file{@var{prefix}}
4744 and @file{@var{prefix}/bin}. Link or copy the appropriate assembler,
4745 linker, etc.@: into @file{@var{prefix}/bin}, and set your @var{PATH} to
4746 include that directory while running both @command{configure} and
4749 You must give @command{configure} the
4750 @option{--with-headers=@var{$WIND_BASE}/target/h} switch so that it can
4751 find the VxWorks system headers. Since VxWorks is a cross compilation
4752 target only, you must also specify @option{--target=@var{target}}.
4753 @command{configure} will attempt to create the directory
4754 @file{@var{prefix}/@var{target}/sys-include} and copy files into it;
4755 make sure the user running @command{configure} has sufficient privilege
4758 GCC's exception handling runtime requires a special ``configlette''
4759 module, @file{contrib/gthr_supp_vxw_5x.c}. Follow the instructions in
4760 that file to add the module to your kernel build. (Future versions of
4761 VxWorks will incorporate this module.)
4767 @heading x86_64-*-*, amd64-*-*
4768 GCC supports the x86-64 architecture implemented by the AMD64 processor
4769 (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD@.
4770 On GNU/Linux the default is a bi-arch compiler which is able to generate
4771 both 64-bit x86-64 and 32-bit x86 code (via the @option{-m32} switch).
4776 @anchor{x86-64-x-solaris210}
4777 @heading x86_64-*-solaris2.1[0-9]*
4778 GCC also supports the x86-64 architecture implemented by the AMD64
4779 processor (@samp{amd64-*-*} is an alias for @samp{x86_64-*-*}) on
4780 Solaris 10 or later. Unlike other systems, without special options a
4781 bi-arch compiler is built which generates 32-bit code by default, but
4782 can generate 64-bit x86-64 code with the @option{-m64} switch. Since
4783 GCC 4.7, there is also configuration that defaults to 64-bit code, but
4784 can generate 32-bit code with @option{-m32}. To configure and build
4785 this way, you have to provide all support libraries like @file{libgmp}
4786 as 64-bit code, configure with @option{--target=x86_64-pc-solaris2.1x}
4787 and @samp{CC=gcc -m64}.
4792 @anchor{xtensa-x-elf}
4793 @heading xtensa*-*-elf
4794 This target is intended for embedded Xtensa systems using the
4795 @samp{newlib} C library. It uses ELF but does not support shared
4796 objects. Designed-defined instructions specified via the
4797 Tensilica Instruction Extension (TIE) language are only supported
4798 through inline assembly.
4800 The Xtensa configuration information must be specified prior to
4801 building GCC@. The @file{include/xtensa-config.h} header
4802 file contains the configuration information. If you created your
4803 own Xtensa configuration with the Xtensa Processor Generator, the
4804 downloaded files include a customized copy of this header file,
4805 which you can use to replace the default header file.
4810 @anchor{xtensa-x-linux}
4811 @heading xtensa*-*-linux*
4812 This target is for Xtensa systems running GNU/Linux. It supports ELF
4813 shared objects and the GNU C library (glibc). It also generates
4814 position-independent code (PIC) regardless of whether the
4815 @option{-fpic} or @option{-fPIC} options are used. In other
4816 respects, this target is the same as the
4817 @uref{#xtensa*-*-elf,,@samp{xtensa*-*-elf}} target.
4823 @heading Microsoft Windows
4825 @subheading Intel 16-bit versions
4826 The 16-bit versions of Microsoft Windows, such as Windows 3.1, are not
4829 However, the 32-bit port has limited support for Microsoft
4830 Windows 3.11 in the Win32s environment, as a target only. See below.
4832 @subheading Intel 32-bit versions
4833 The 32-bit versions of Windows, including Windows 95, Windows NT, Windows
4834 XP, and Windows Vista, are supported by several different target
4835 platforms. These targets differ in which Windows subsystem they target
4836 and which C libraries are used.
4839 @item Cygwin @uref{#x-x-cygwin,,*-*-cygwin}: Cygwin provides a user-space
4840 Linux API emulation layer in the Win32 subsystem.
4841 @item Interix @uref{#x-x-interix,,*-*-interix}: The Interix subsystem
4842 provides native support for POSIX.
4843 @item MinGW @uref{#x-x-mingw32,,*-*-mingw32}: MinGW is a native GCC port for
4844 the Win32 subsystem that provides a subset of POSIX.
4845 @item MKS i386-pc-mks: NuTCracker from MKS. See
4846 @uref{http://www.mkssoftware.com/} for more information.
4849 @subheading Intel 64-bit versions
4850 GCC contains support for x86-64 using the mingw-w64
4851 runtime library, available from @uref{http://mingw-w64.sourceforge.net/}.
4852 This library should be used with the target triple x86_64-pc-mingw32.
4854 Presently Windows for Itanium is not supported.
4856 @subheading Windows CE
4857 Windows CE is supported as a target only on Hitachi
4858 SuperH (sh-wince-pe), and MIPS (mips-wince-pe).
4860 @subheading Other Windows Platforms
4861 GCC no longer supports Windows NT on the Alpha or PowerPC.
4863 GCC no longer supports the Windows POSIX subsystem. However, it does
4864 support the Interix subsystem. See above.
4866 Old target names including *-*-winnt and *-*-windowsnt are no longer used.
4868 PW32 (i386-pc-pw32) support was never completed, and the project seems to
4869 be inactive. See @uref{http://pw32.sourceforge.net/} for more information.
4871 UWIN support has been removed due to a lack of maintenance.
4878 Ports of GCC are included with the
4879 @uref{http://www.cygwin.com/,,Cygwin environment}.
4881 GCC will build under Cygwin without modification; it does not build
4882 with Microsoft's C++ compiler and there are no plans to make it do so.
4884 The Cygwin native compiler can be configured to target any 32-bit x86
4885 cpu architecture desired; the default is i686-pc-cygwin. It should be
4886 used with as up-to-date a version of binutils as possible; use either
4887 the latest official GNU binutils release in the Cygwin distribution,
4888 or version 2.20 or above if building your own.
4893 @anchor{x-x-interix}
4894 @heading *-*-interix
4895 The Interix target is used by OpenNT, Interix, Services For UNIX (SFU),
4896 and Subsystem for UNIX-based Applications (SUA). Applications compiled
4897 with this target run in the Interix subsystem, which is separate from
4898 the Win32 subsystem. This target was last known to work in GCC 3.3.
4903 @anchor{x-x-mingw32}
4904 @heading *-*-mingw32
4905 GCC will build with and support only MinGW runtime 3.12 and later.
4906 Earlier versions of headers are incompatible with the new default semantics
4907 of @code{extern inline} in @code{-std=c99} and @code{-std=gnu99} modes.
4913 @heading Older systems
4914 GCC contains support files for many older (1980s and early
4915 1990s) Unix variants. For the most part, support for these systems
4916 has not been deliberately removed, but it has not been maintained for
4917 several years and may suffer from bitrot.
4919 Starting with GCC 3.1, each release has a list of ``obsoleted'' systems.
4920 Support for these systems is still present in that release, but
4921 @command{configure} will fail unless the @option{--enable-obsolete}
4922 option is given. Unless a maintainer steps forward, support for these
4923 systems will be removed from the next release of GCC@.
4925 Support for old systems as hosts for GCC can cause problems if the
4926 workarounds for compiler, library and operating system bugs affect the
4927 cleanliness or maintainability of the rest of GCC@. In some cases, to
4928 bring GCC up on such a system, if still possible with current GCC, may
4929 require first installing an old version of GCC which did work on that
4930 system, and using it to compile a more recent GCC, to avoid bugs in the
4931 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
4932 @file{old-releases} directory on the @uref{../mirrors.html,,GCC mirror
4933 sites}. Header bugs may generally be avoided using
4934 @command{fixincludes}, but bugs or deficiencies in libraries and the
4935 operating system may still cause problems.
4937 Support for older systems as targets for cross-compilation is less
4938 problematic than support for them as hosts for GCC; if an enthusiast
4939 wishes to make such a target work again (including resurrecting any of
4940 the targets that never worked with GCC 2, starting from the last
4941 version before they were removed), patches
4942 @uref{../contribute.html,,following the usual requirements} would be
4943 likely to be accepted, since they should not affect the support for more
4946 For some systems, old versions of GNU binutils may also be useful,
4947 and are available from @file{pub/binutils/old-releases} on
4948 @uref{http://sourceware.org/mirrors.html,,sourceware.org mirror sites}.
4950 Some of the information on specific systems above relates to
4951 such older systems, but much of the information
4952 about GCC on such systems (which may no longer be applicable to
4953 current GCC) is to be found in the GCC texinfo manual.
4959 @heading all ELF targets (SVR4, Solaris 2, etc.)
4960 C++ support is significantly better on ELF targets if you use the
4961 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
4962 inlines, vtables and template instantiations will be discarded
4971 @uref{./index.html,,Return to the GCC Installation page}
4975 @c ***Old documentation******************************************************
4977 @include install-old.texi
4983 @uref{./index.html,,Return to the GCC Installation page}
4987 @c ***GFDL********************************************************************
4995 @uref{./index.html,,Return to the GCC Installation page}
4999 @c ***************************************************************************
5000 @c Part 6 The End of the Document
5002 @comment node-name, next, previous, up
5003 @node Concept Index, , GNU Free Documentation License, Top
5007 @unnumbered Concept Index