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-2013 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-2013 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
260 In order to build the Ada compiler (GNAT) you must already have GNAT
261 installed because portions of the Ada frontend are written in Ada (with
262 GNAT extensions.) Refer to the Ada installation instructions for more
263 specific information.
265 @item A ``working'' POSIX compatible shell, or GNU bash
267 Necessary when running @command{configure} because some
268 @command{/bin/sh} shells have bugs and may crash when configuring the
269 target libraries. In other cases, @command{/bin/sh} or @command{ksh}
270 have disastrous corner-case performance problems. This
271 can cause target @command{configure} runs to literally take days to
272 complete in some cases.
274 So on some platforms @command{/bin/ksh} is sufficient, on others it
275 isn't. See the host/target specific instructions for your platform, or
276 use @command{bash} to be sure. Then set @env{CONFIG_SHELL} in your
277 environment to your ``good'' shell prior to running
278 @command{configure}/@command{make}.
280 @command{zsh} is not a fully compliant POSIX shell and will not
281 work when configuring GCC@.
283 @item A POSIX or SVR4 awk
285 Necessary for creating some of the generated source files for GCC@.
286 If in doubt, use a recent GNU awk version, as some of the older ones
287 are broken. GNU awk version 3.1.5 is known to work.
291 Necessary in some circumstances, optional in others. See the
292 host/target specific instructions for your platform for the exact
295 @item gzip version 1.2.4 (or later) or
296 @itemx bzip2 version 1.0.2 (or later)
298 Necessary to uncompress GCC @command{tar} files when source code is
299 obtained via FTP mirror sites.
301 @item GNU make version 3.80 (or later)
303 You must have GNU make installed to build GCC@.
305 @item GNU tar version 1.14 (or later)
307 Necessary (only on some platforms) to untar the source code. Many
308 systems' @command{tar} programs will also work, only try GNU
309 @command{tar} if you have problems.
311 @item Perl version 5.6.1 (or later)
313 Necessary when targeting Darwin, building @samp{libstdc++},
314 and not using @option{--disable-symvers}.
315 Necessary when targeting Solaris 2 with Sun @command{ld} and not using
316 @option{--disable-symvers}. The bundled @command{perl} in Solaris@tie{}8
319 Necessary when regenerating @file{Makefile} dependencies in libiberty.
320 Necessary when regenerating @file{libiberty/functions.texi}.
321 Necessary when generating manpages from Texinfo manuals.
322 Used by various scripts to generate some files included in SVN (mainly
323 Unicode-related and rarely changing) from source tables.
325 @item @command{jar}, or InfoZIP (@command{zip} and @command{unzip})
327 Necessary to build libgcj, the GCJ runtime.
331 Several support libraries are necessary to build GCC, some are required,
332 others optional. While any sufficiently new version of required tools
333 usually work, library requirements are generally stricter. Newer
334 versions may work in some cases, but it's safer to use the exact
335 versions documented. We appreciate bug reports about problems with
336 newer versions, though. If your OS vendor provides packages for the
337 support libraries then using those packages may be the simplest way to
338 install the libraries.
341 @item GNU Multiple Precision Library (GMP) version 4.3.2 (or later)
343 Necessary to build GCC@. If a GMP source distribution is found in a
344 subdirectory of your GCC sources named @file{gmp}, it will be built
345 together with GCC. Alternatively, if GMP is already installed but it
346 is not in your library search path, you will have to configure with the
347 @option{--with-gmp} configure option. See also @option{--with-gmp-lib}
348 and @option{--with-gmp-include}.
350 @item MPFR Library version 2.4.2 (or later)
352 Necessary to build GCC@. It can be downloaded from
353 @uref{http://www.mpfr.org/}. If an MPFR source distribution is found
354 in a subdirectory of your GCC sources named @file{mpfr}, it will be
355 built together with GCC. Alternatively, if MPFR is already installed
356 but it is not in your default library search path, the
357 @option{--with-mpfr} configure option should be used. See also
358 @option{--with-mpfr-lib} and @option{--with-mpfr-include}.
360 @item MPC Library version 0.8.1 (or later)
362 Necessary to build GCC@. It can be downloaded from
363 @uref{http://www.multiprecision.org/}. If an MPC source distribution
364 is found in a subdirectory of your GCC sources named @file{mpc}, it
365 will be built together with GCC. Alternatively, if MPC is already
366 installed but it is not in your default library search path, the
367 @option{--with-mpc} configure option should be used. See also
368 @option{--with-mpc-lib} and @option{--with-mpc-include}.
370 @item ISL Library version 0.11.1
372 Necessary to build GCC with the Graphite loop optimizations.
373 It can be downloaded from @uref{ftp://gcc.gnu.org/pub/gcc/infrastructure/}
374 as @file{isl-0.11.1.tar.bz2}.
376 The @option{--with-isl} configure option should be used if ISL is not
377 installed in your default library search path.
381 Necessary to build GCC with the Graphite loop optimizations. It can be
382 downloaded from @uref{ftp://gcc.gnu.org/pub/gcc/infrastructure/} as
383 @file{cloog-0.18.0.tar.gz}. The @option{--with-cloog} configure option should
384 be used if CLooG is not installed in your default library search path.
385 CLooG needs to be built against ISL 0.11.1. Use @option{--with-isl=system}
386 to direct CLooG to pick up an already installed ISL, otherwise it will use
387 ISL 0.11.1 as bundled with CLooG. CLooG needs to be configured to use GMP
388 internally, use @option{--with-bits=gmp} to direct it to do that.
392 @heading Tools/packages necessary for modifying GCC
394 @item autoconf version 2.64
395 @itemx GNU m4 version 1.4.6 (or later)
397 Necessary when modifying @file{configure.ac}, @file{aclocal.m4}, etc.@:
398 to regenerate @file{configure} and @file{config.in} files.
400 @item automake version 1.11.1
402 Necessary when modifying a @file{Makefile.am} file to regenerate its
403 associated @file{Makefile.in}.
405 Much of GCC does not use automake, so directly edit the @file{Makefile.in}
406 file. Specifically this applies to the @file{gcc}, @file{intl},
407 @file{libcpp}, @file{libiberty}, @file{libobjc} directories as well
408 as any of their subdirectories.
410 For directories that use automake, GCC requires the latest release in
411 the 1.11 series, which is currently 1.11.1. When regenerating a directory
412 to a newer version, please update all the directories using an older 1.11
413 to the latest released version.
415 @item gettext version 0.14.5 (or later)
417 Needed to regenerate @file{gcc.pot}.
419 @item gperf version 2.7.2 (or later)
421 Necessary when modifying @command{gperf} input files, e.g.@:
422 @file{gcc/cp/cfns.gperf} to regenerate its associated header file, e.g.@:
423 @file{gcc/cp/cfns.h}.
429 Necessary to run the GCC testsuite; see the section on testing for details.
431 @item autogen version 5.5.4 (or later) and
432 @itemx guile version 1.4.1 (or later)
434 Necessary to regenerate @file{fixinc/fixincl.x} from
435 @file{fixinc/inclhack.def} and @file{fixinc/*.tpl}.
437 Necessary to run @samp{make check} for @file{fixinc}.
439 Necessary to regenerate the top level @file{Makefile.in} file from
440 @file{Makefile.tpl} and @file{Makefile.def}.
442 @item Flex version 2.5.4 (or later)
444 Necessary when modifying @file{*.l} files.
446 Necessary to build GCC during development because the generated output
447 files are not included in the SVN repository. They are included in
450 @item Texinfo version 4.7 (or later)
452 Necessary for running @command{makeinfo} when modifying @file{*.texi}
453 files to test your changes.
455 Necessary for running @command{make dvi} or @command{make pdf} to
456 create printable documentation in DVI or PDF format. Texinfo version
457 4.8 or later is required for @command{make pdf}.
459 Necessary to build GCC documentation during development because the
460 generated output files are not included in the SVN repository. They are
461 included in releases.
463 @item @TeX{} (any working version)
465 Necessary for running @command{texi2dvi} and @command{texi2pdf}, which
466 are used when running @command{make dvi} or @command{make pdf} to create
467 DVI or PDF files, respectively.
469 @item SVN (any version)
470 @itemx SSH (any version)
472 Necessary to access the SVN repository. Public releases and weekly
473 snapshots of the development sources are also available via FTP@.
475 @item GNU diffutils version 2.7 (or later)
477 Useful when submitting patches for the GCC source code.
479 @item patch version 2.5.4 (or later)
481 Necessary when applying patches, created with @command{diff}, to one's
487 If you wish to modify @file{.java} files in libjava, you will need to
488 configure with @option{--enable-java-maintainer-mode}, and you will need
489 to have executables named @command{ecj1} and @command{gjavah} in your path.
490 The @command{ecj1} executable should run the Eclipse Java compiler via
491 the GCC-specific entry point. You can download a suitable jar from
492 @uref{ftp://sourceware.org/pub/java/}, or by running the script
493 @command{contrib/download_ecj}.
495 @item antlr.jar version 2.7.1 (or later)
498 If you wish to build the @command{gjdoc} binary in libjava, you will
499 need to have an @file{antlr.jar} library available. The library is
500 searched for in system locations but can be specified with
501 @option{--with-antlr-jar=} instead. When configuring with
502 @option{--enable-java-maintainer-mode}, you will need to have one of
503 the executables named @command{cantlr}, @command{runantlr} or
504 @command{antlr} in your path.
513 @uref{./index.html,,Return to the GCC Installation page}
517 @c ***Downloading the source**************************************************
519 @comment node-name, next, previous, up
520 @node Downloading the source, Configuration, Prerequisites, Installing GCC
524 @chapter Downloading GCC
526 @cindex Downloading GCC
527 @cindex Downloading the Source
529 GCC is distributed via @uref{http://gcc.gnu.org/svn.html,,SVN} and FTP
530 tarballs compressed with @command{gzip} or
531 @command{bzip2}. It is possible to download a full distribution or specific
534 Please refer to the @uref{http://gcc.gnu.org/releases.html,,releases web page}
535 for information on how to obtain GCC@.
537 The full distribution includes the C, C++, Objective-C, Fortran, Java,
538 and Ada (in the case of GCC 3.1 and later) compilers. The full
539 distribution also includes runtime libraries for C++, Objective-C,
540 Fortran, and Java. In GCC 3.0 and later versions, the GNU compiler
541 testsuites are also included in the full distribution.
543 If you choose to download specific components, you must download the core
544 GCC distribution plus any language specific distributions you wish to
545 use. The core distribution includes the C language front end as well as the
546 shared components. Each language has a tarball which includes the language
547 front end as well as the language runtime (when appropriate).
549 Unpack the core distribution as well as any language specific
550 distributions in the same directory.
552 If you also intend to build binutils (either to upgrade an existing
553 installation or for use in place of the corresponding tools of your
554 OS), unpack the binutils distribution either in the same directory or
555 a separate one. In the latter case, add symbolic links to any
556 components of the binutils you intend to build alongside the compiler
557 (@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld},
558 @file{opcodes}, @dots{}) to the directory containing the GCC sources.
560 Likewise the GMP, MPFR and MPC libraries can be automatically built
561 together with GCC. Unpack the GMP, MPFR and/or MPC source
562 distributions in the directory containing the GCC sources and rename
563 their directories to @file{gmp}, @file{mpfr} and @file{mpc},
564 respectively (or use symbolic links with the same name).
571 @uref{./index.html,,Return to the GCC Installation page}
575 @c ***Configuration***********************************************************
577 @comment node-name, next, previous, up
578 @node Configuration, Building, Downloading the source, Installing GCC
582 @chapter Installing GCC: Configuration
584 @cindex Configuration
585 @cindex Installing GCC: Configuration
587 Like most GNU software, GCC must be configured before it can be built.
588 This document describes the recommended configuration procedure
589 for both native and cross targets.
591 We use @var{srcdir} to refer to the toplevel source directory for
592 GCC; we use @var{objdir} to refer to the toplevel build/object directory.
594 If you obtained the sources via SVN, @var{srcdir} must refer to the top
595 @file{gcc} directory, the one where the @file{MAINTAINERS} file can be
596 found, and not its @file{gcc} subdirectory, otherwise the build will fail.
598 If either @var{srcdir} or @var{objdir} is located on an automounted NFS
599 file system, the shell's built-in @command{pwd} command will return
600 temporary pathnames. Using these can lead to various sorts of build
601 problems. To avoid this issue, set the @env{PWDCMD} environment
602 variable to an automounter-aware @command{pwd} command, e.g.,
603 @command{pawd} or @samp{amq -w}, during the configuration and build
606 First, we @strong{highly} recommend that GCC be built into a
607 separate directory from the sources which does @strong{not} reside
608 within the source tree. This is how we generally build GCC; building
609 where @var{srcdir} == @var{objdir} should still work, but doesn't
610 get extensive testing; building where @var{objdir} is a subdirectory
611 of @var{srcdir} is unsupported.
613 If you have previously built GCC in the same directory for a
614 different target machine, do @samp{make distclean} to delete all files
615 that might be invalid. One of the files this deletes is @file{Makefile};
616 if @samp{make distclean} complains that @file{Makefile} does not exist
617 or issues a message like ``don't know how to make distclean'' it probably
618 means that the directory is already suitably clean. However, with the
619 recommended method of building in a separate @var{objdir}, you should
620 simply use a different @var{objdir} for each target.
622 Second, when configuring a native system, either @command{cc} or
623 @command{gcc} must be in your path or you must set @env{CC} in
624 your environment before running configure. Otherwise the configuration
628 Note that the bootstrap compiler and the resulting GCC must be link
629 compatible, else the bootstrap will fail with linker errors about
630 incompatible object file formats. Several multilibed targets are
631 affected by this requirement, see
633 @ref{Specific, host/target specific installation notes}.
636 @uref{specific.html,,host/target specific installation notes}.
645 % @var{srcdir}/configure [@var{options}] [@var{target}]
648 @heading Distributor options
650 If you will be distributing binary versions of GCC, with modifications
651 to the source code, you should use the options described in this
652 section to make clear that your version contains modifications.
655 @item --with-pkgversion=@var{version}
656 Specify a string that identifies your package. You may wish
657 to include a build number or build date. This version string will be
658 included in the output of @command{gcc --version}. This suffix does
659 not replace the default version string, only the @samp{GCC} part.
661 The default value is @samp{GCC}.
663 @item --with-bugurl=@var{url}
664 Specify the URL that users should visit if they wish to report a bug.
665 You are of course welcome to forward bugs reported to you to the FSF,
666 if you determine that they are not bugs in your modifications.
668 The default value refers to the FSF's GCC bug tracker.
672 @heading Target specification
675 GCC has code to correctly determine the correct value for @var{target}
676 for nearly all native systems. Therefore, we highly recommend you do
677 not provide a configure target when configuring a native compiler.
680 @var{target} must be specified as @option{--target=@var{target}}
681 when configuring a cross compiler; examples of valid targets would be
682 m68k-elf, sh-elf, etc.
685 Specifying just @var{target} instead of @option{--target=@var{target}}
686 implies that the host defaults to @var{target}.
690 @heading Options specification
692 Use @var{options} to override several configure time options for
693 GCC@. A list of supported @var{options} follows; @samp{configure
694 --help} may list other options, but those not listed below may not
695 work and should not normally be used.
697 Note that each @option{--enable} option has a corresponding
698 @option{--disable} option and that each @option{--with} option has a
699 corresponding @option{--without} option.
702 @item --prefix=@var{dirname}
703 Specify the toplevel installation
704 directory. This is the recommended way to install the tools into a directory
705 other than the default. The toplevel installation directory defaults to
708 We @strong{highly} recommend against @var{dirname} being the same or a
709 subdirectory of @var{objdir} or vice versa. If specifying a directory
710 beneath a user's home directory tree, some shells will not expand
711 @var{dirname} correctly if it contains the @samp{~} metacharacter; use
714 The following standard @command{autoconf} options are supported. Normally you
715 should not need to use these options.
717 @item --exec-prefix=@var{dirname}
718 Specify the toplevel installation directory for architecture-dependent
719 files. The default is @file{@var{prefix}}.
721 @item --bindir=@var{dirname}
722 Specify the installation directory for the executables called by users
723 (such as @command{gcc} and @command{g++}). The default is
724 @file{@var{exec-prefix}/bin}.
726 @item --libdir=@var{dirname}
727 Specify the installation directory for object code libraries and
728 internal data files of GCC@. The default is @file{@var{exec-prefix}/lib}.
730 @item --libexecdir=@var{dirname}
731 Specify the installation directory for internal executables of GCC@.
732 The default is @file{@var{exec-prefix}/libexec}.
734 @item --with-slibdir=@var{dirname}
735 Specify the installation directory for the shared libgcc library. The
736 default is @file{@var{libdir}}.
738 @item --datarootdir=@var{dirname}
739 Specify the root of the directory tree for read-only architecture-independent
740 data files referenced by GCC@. The default is @file{@var{prefix}/share}.
742 @item --infodir=@var{dirname}
743 Specify the installation directory for documentation in info format.
744 The default is @file{@var{datarootdir}/info}.
746 @item --datadir=@var{dirname}
747 Specify the installation directory for some architecture-independent
748 data files referenced by GCC@. The default is @file{@var{datarootdir}}.
750 @item --docdir=@var{dirname}
751 Specify the installation directory for documentation files (other
752 than Info) for GCC@. The default is @file{@var{datarootdir}/doc}.
754 @item --htmldir=@var{dirname}
755 Specify the installation directory for HTML documentation files.
756 The default is @file{@var{docdir}}.
758 @item --pdfdir=@var{dirname}
759 Specify the installation directory for PDF documentation files.
760 The default is @file{@var{docdir}}.
762 @item --mandir=@var{dirname}
763 Specify the installation directory for manual pages. The default is
764 @file{@var{datarootdir}/man}. (Note that the manual pages are only extracts
765 from the full GCC manuals, which are provided in Texinfo format. The manpages
766 are derived by an automatic conversion process from parts of the full
769 @item --with-gxx-include-dir=@var{dirname}
771 the installation directory for G++ header files. The default depends
772 on other configuration options, and differs between cross and native
775 @item --with-specs=@var{specs}
776 Specify additional command line driver SPECS.
777 This can be useful if you need to turn on a non-standard feature by
778 default without modifying the compiler's source code, for instance
779 @option{--with-specs=%@{!fcommon:%@{!fno-common:-fno-common@}@}}.
781 @xref{Spec Files,, Specifying subprocesses and the switches to pass to them,
782 gcc, Using the GNU Compiler Collection (GCC)},
785 See ``Spec Files'' in the main manual
790 @item --program-prefix=@var{prefix}
791 GCC supports some transformations of the names of its programs when
792 installing them. This option prepends @var{prefix} to the names of
793 programs to install in @var{bindir} (see above). For example, specifying
794 @option{--program-prefix=foo-} would result in @samp{gcc}
795 being installed as @file{/usr/local/bin/foo-gcc}.
797 @item --program-suffix=@var{suffix}
798 Appends @var{suffix} to the names of programs to install in @var{bindir}
799 (see above). For example, specifying @option{--program-suffix=-3.1}
800 would result in @samp{gcc} being installed as
801 @file{/usr/local/bin/gcc-3.1}.
803 @item --program-transform-name=@var{pattern}
804 Applies the @samp{sed} script @var{pattern} to be applied to the names
805 of programs to install in @var{bindir} (see above). @var{pattern} has to
806 consist of one or more basic @samp{sed} editing commands, separated by
807 semicolons. For example, if you want the @samp{gcc} program name to be
808 transformed to the installed program @file{/usr/local/bin/myowngcc} and
809 the @samp{g++} program name to be transformed to
810 @file{/usr/local/bin/gspecial++} without changing other program names,
811 you could use the pattern
812 @option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'}
813 to achieve this effect.
815 All three options can be combined and used together, resulting in more
816 complex conversion patterns. As a basic rule, @var{prefix} (and
817 @var{suffix}) are prepended (appended) before further transformations
818 can happen with a special transformation script @var{pattern}.
820 As currently implemented, this option only takes effect for native
821 builds; cross compiler binaries' names are not transformed even when a
822 transformation is explicitly asked for by one of these options.
824 For native builds, some of the installed programs are also installed
825 with the target alias in front of their name, as in
826 @samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen
827 before the target alias is prepended to the name---so, specifying
828 @option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the
829 resulting binary would be installed as
830 @file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}.
832 As a last shortcoming, none of the installed Ada programs are
833 transformed yet, which will be fixed in some time.
835 @item --with-local-prefix=@var{dirname}
837 installation directory for local include files. The default is
838 @file{/usr/local}. Specify this option if you want the compiler to
839 search directory @file{@var{dirname}/include} for locally installed
840 header files @emph{instead} of @file{/usr/local/include}.
842 You should specify @option{--with-local-prefix} @strong{only} if your
843 site has a different convention (not @file{/usr/local}) for where to put
846 The default value for @option{--with-local-prefix} is @file{/usr/local}
847 regardless of the value of @option{--prefix}. Specifying
848 @option{--prefix} has no effect on which directory GCC searches for
849 local header files. This may seem counterintuitive, but actually it is
852 The purpose of @option{--prefix} is to specify where to @emph{install
853 GCC}. The local header files in @file{/usr/local/include}---if you put
854 any in that directory---are not part of GCC@. They are part of other
855 programs---perhaps many others. (GCC installs its own header files in
856 another directory which is based on the @option{--prefix} value.)
858 Both the local-prefix include directory and the GCC-prefix include
859 directory are part of GCC's ``system include'' directories. Although these
860 two directories are not fixed, they need to be searched in the proper
861 order for the correct processing of the include_next directive. The
862 local-prefix include directory is searched before the GCC-prefix
863 include directory. Another characteristic of system include directories
864 is that pedantic warnings are turned off for headers in these directories.
866 Some autoconf macros add @option{-I @var{directory}} options to the
867 compiler command line, to ensure that directories containing installed
868 packages' headers are searched. When @var{directory} is one of GCC's
869 system include directories, GCC will ignore the option so that system
870 directories continue to be processed in the correct order. This
871 may result in a search order different from what was specified but the
872 directory will still be searched.
874 GCC automatically searches for ordinary libraries using
875 @env{GCC_EXEC_PREFIX}. Thus, when the same installation prefix is
876 used for both GCC and packages, GCC will automatically search for
877 both headers and libraries. This provides a configuration that is
878 easy to use. GCC behaves in a manner similar to that when it is
879 installed as a system compiler in @file{/usr}.
881 Sites that need to install multiple versions of GCC may not want to
882 use the above simple configuration. It is possible to use the
883 @option{--program-prefix}, @option{--program-suffix} and
884 @option{--program-transform-name} options to install multiple versions
885 into a single directory, but it may be simpler to use different prefixes
886 and the @option{--with-local-prefix} option to specify the location of the
887 site-specific files for each version. It will then be necessary for
888 users to specify explicitly the location of local site libraries
889 (e.g., with @env{LIBRARY_PATH}).
891 The same value can be used for both @option{--with-local-prefix} and
892 @option{--prefix} provided it is not @file{/usr}. This can be used
893 to avoid the default search of @file{/usr/local/include}.
895 @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
896 The directory you use for @option{--with-local-prefix} @strong{must not}
897 contain any of the system's standard header files. If it did contain
898 them, certain programs would be miscompiled (including GNU Emacs, on
899 certain targets), because this would override and nullify the header
900 file corrections made by the @command{fixincludes} script.
902 Indications are that people who use this option use it based on mistaken
903 ideas of what it is for. People use it as if it specified where to
904 install part of GCC@. Perhaps they make this assumption because
905 installing GCC creates the directory.
907 @item --with-native-system-header-dir=@var{dirname}
908 Specifies that @var{dirname} is the directory that contains native system
909 header files, rather than @file{/usr/include}. This option is most useful
910 if you are creating a compiler that should be isolated from the system
911 as much as possible. It is most commonly used with the
912 @option{--with-sysroot} option and will cause GCC to search
913 @var{dirname} inside the system root specified by that option.
915 @item --enable-shared[=@var{package}[,@dots{}]]
916 Build shared versions of libraries, if shared libraries are supported on
917 the target platform. Unlike GCC 2.95.x and earlier, shared libraries
918 are enabled by default on all platforms that support shared libraries.
920 If a list of packages is given as an argument, build shared libraries
921 only for the listed packages. For other packages, only static libraries
922 will be built. Package names currently recognized in the GCC tree are
923 @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not
924 @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc},
925 @samp{ada}, @samp{libada}, @samp{libjava}, @samp{libgo}, and @samp{libobjc}.
926 Note @samp{libiberty} does not support shared libraries at all.
928 Use @option{--disable-shared} to build only static libraries. Note that
929 @option{--disable-shared} does not accept a list of package names as
930 argument, only @option{--enable-shared} does.
932 @item @anchor{with-gnu-as}--with-gnu-as
933 Specify that the compiler should assume that the
934 assembler it finds is the GNU assembler. However, this does not modify
935 the rules to find an assembler and will result in confusion if the
936 assembler found is not actually the GNU assembler. (Confusion may also
937 result if the compiler finds the GNU assembler but has not been
938 configured with @option{--with-gnu-as}.) If you have more than one
939 assembler installed on your system, you may want to use this option in
940 connection with @option{--with-as=@var{pathname}} or
941 @option{--with-build-time-tools=@var{pathname}}.
943 The following systems are the only ones where it makes a difference
944 whether you use the GNU assembler. On any other system,
945 @option{--with-gnu-as} has no effect.
948 @item @samp{hppa1.0-@var{any}-@var{any}}
949 @item @samp{hppa1.1-@var{any}-@var{any}}
950 @item @samp{sparc-sun-solaris2.@var{any}}
951 @item @samp{sparc64-@var{any}-solaris2.@var{any}}
954 @item @anchor{with-as}--with-as=@var{pathname}
955 Specify that the compiler should use the assembler pointed to by
956 @var{pathname}, rather than the one found by the standard rules to find
957 an assembler, which are:
960 Unless GCC is being built with a cross compiler, check the
961 @file{@var{libexec}/gcc/@var{target}/@var{version}} directory.
962 @var{libexec} defaults to @file{@var{exec-prefix}/libexec};
963 @var{exec-prefix} defaults to @var{prefix}, which
964 defaults to @file{/usr/local} unless overridden by the
965 @option{--prefix=@var{pathname}} switch described above. @var{target}
966 is the target system triple, such as @samp{sparc-sun-solaris2.7}, and
967 @var{version} denotes the GCC version, such as 3.0.
970 If the target system is the same that you are building on, check
971 operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
975 Check in the @env{PATH} for a tool whose name is prefixed by the
976 target system triple.
979 Check in the @env{PATH} for a tool whose name is not prefixed by the
980 target system triple, if the host and target system triple are
981 the same (in other words, we use a host tool if it can be used for
985 You may want to use @option{--with-as} if no assembler
986 is installed in the directories listed above, or if you have multiple
987 assemblers installed and want to choose one that is not found by the
990 @item @anchor{with-gnu-ld}--with-gnu-ld
991 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
994 @item --with-ld=@var{pathname}
995 Same as @uref{#with-as,,@option{--with-as}}
999 Specify that stabs debugging
1000 information should be used instead of whatever format the host normally
1001 uses. Normally GCC uses the same debug format as the host system.
1003 On MIPS based systems and on Alphas, you must specify whether you want
1004 GCC to create the normal ECOFF debugging format, or to use BSD-style
1005 stabs passed through the ECOFF symbol table. The normal ECOFF debug
1006 format cannot fully handle languages other than C@. BSD stabs format can
1007 handle other languages, but it only works with the GNU debugger GDB@.
1009 Normally, GCC uses the ECOFF debugging format by default; if you
1010 prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@.
1012 No matter which default you choose when you configure GCC, the user
1013 can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
1014 the debug format for a particular compilation.
1016 @option{--with-stabs} is meaningful on the ISC system on the 386, also, if
1017 @option{--with-gas} is used. It selects use of stabs debugging
1018 information embedded in COFF output. This kind of debugging information
1019 supports C++ well; ordinary COFF debugging information does not.
1021 @option{--with-stabs} is also meaningful on 386 systems running SVR4. It
1022 selects use of stabs debugging information embedded in ELF output. The
1023 C++ compiler currently (2.6.0) does not support the DWARF debugging
1024 information normally used on 386 SVR4 platforms; stabs provide a
1025 workable alternative. This requires gas and gdb, as the normal SVR4
1026 tools can not generate or interpret stabs.
1028 @item --with-tls=@var{dialect}
1029 Specify the default TLS dialect, for systems were there is a choice.
1030 For ARM targets, possible values for @var{dialect} are @code{gnu} or
1031 @code{gnu2}, which select between the original GNU dialect and the GNU TLS
1032 descriptor-based dialect.
1034 @item --enable-multiarch
1035 Specify whether to enable or disable multiarch support. The default is
1036 to check for glibc start files in a multiarch location, and enable it
1037 if the files are found. The auto detection is enabled for native builds,
1038 and for cross builds configured with @option{--with-sysroot}, and without
1039 @option{--with-native-system-header-dir}.
1040 More documentation about multiarch can be found at
1041 @uref{http://wiki.debian.org/Multiarch}.
1043 @item --disable-multilib
1044 Specify that multiple target
1045 libraries to support different target variants, calling
1046 conventions, etc.@: should not be built. The default is to build a
1047 predefined set of them.
1049 Some targets provide finer-grained control over which multilibs are built
1050 (e.g., @option{--disable-softfloat}):
1053 fpu, 26bit, underscore, interwork, biendian, nofmult.
1056 softfloat, m68881, m68000, m68020.
1059 single-float, biendian, softfloat.
1061 @item powerpc*-*-*, rs6000*-*-*
1062 aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
1067 @item --with-multilib-list=@var{list}
1068 @itemx --without-multilib-list
1069 Specify what multilibs to build.
1070 Currently only implemented for sh*-*-* and x86-64-*-linux*.
1074 @var{list} is a comma separated list of CPU names. These must be of the
1075 form @code{sh*} or @code{m*} (in which case they match the compiler option
1076 for that processor). The list should not contain any endian options -
1077 these are handled by @option{--with-endian}.
1079 If @var{list} is empty, then there will be no multilibs for extra
1080 processors. The multilib for the secondary endian remains enabled.
1082 As a special case, if an entry in the list starts with a @code{!}
1083 (exclamation point), then it is added to the list of excluded multilibs.
1084 Entries of this sort should be compatible with @samp{MULTILIB_EXCLUDES}
1085 (once the leading @code{!} has been stripped).
1087 If @option{--with-multilib-list} is not given, then a default set of
1088 multilibs is selected based on the value of @option{--target}. This is
1089 usually the complete set of libraries, but some targets imply a more
1092 Example 1: to configure a compiler for SH4A only, but supporting both
1093 endians, with little endian being the default:
1095 --with-cpu=sh4a --with-endian=little,big --with-multilib-list=
1098 Example 2: to configure a compiler for both SH4A and SH4AL-DSP, but with
1099 only little endian SH4AL:
1101 --with-cpu=sh4a --with-endian=little,big \
1102 --with-multilib-list=sh4al,!mb/m4al
1105 @item x86-64-*-linux*
1106 @var{list} is a comma separated list of @code{m32}, @code{m64} and
1107 @code{mx32} to enable 32-bit, 64-bit and x32 run-time libraries,
1108 respectively. If @var{list} is empty, then there will be no multilibs
1109 and only the default run-time library will be enabled.
1111 If @option{--with-multilib-list} is not given, then only 32-bit and
1112 64-bit run-time libraries will be enabled.
1115 @item --with-endian=@var{endians}
1116 Specify what endians to use.
1117 Currently only implemented for sh*-*-*.
1119 @var{endians} may be one of the following:
1122 Use big endian exclusively.
1124 Use little endian exclusively.
1126 Use big endian by default. Provide a multilib for little endian.
1128 Use little endian by default. Provide a multilib for big endian.
1131 @item --enable-threads
1132 Specify that the target
1133 supports threads. This affects the Objective-C compiler and runtime
1134 library, and exception handling for other languages like C++ and Java.
1135 On some systems, this is the default.
1137 In general, the best (and, in many cases, the only known) threading
1138 model available will be configured for use. Beware that on some
1139 systems, GCC has not been taught what threading models are generally
1140 available for the system. In this case, @option{--enable-threads} is an
1141 alias for @option{--enable-threads=single}.
1143 @item --disable-threads
1144 Specify that threading support should be disabled for the system.
1145 This is an alias for @option{--enable-threads=single}.
1147 @item --enable-threads=@var{lib}
1149 @var{lib} is the thread support library. This affects the Objective-C
1150 compiler and runtime library, and exception handling for other languages
1151 like C++ and Java. The possibilities for @var{lib} are:
1159 LynxOS thread support.
1161 MIPS SDE thread support.
1163 This is an alias for @samp{single}.
1165 Generic POSIX/Unix98 thread support.
1167 RTEMS thread support.
1169 Disable thread support, should work for all platforms.
1173 VxWorks thread support.
1175 Microsoft Win32 API thread support.
1179 Specify that the target supports TLS (Thread Local Storage). Usually
1180 configure can correctly determine if TLS is supported. In cases where
1181 it guesses incorrectly, TLS can be explicitly enabled or disabled with
1182 @option{--enable-tls} or @option{--disable-tls}. This can happen if
1183 the assembler supports TLS but the C library does not, or if the
1184 assumptions made by the configure test are incorrect.
1187 Specify that the target does not support TLS.
1188 This is an alias for @option{--enable-tls=no}.
1190 @item --with-cpu=@var{cpu}
1191 @itemx --with-cpu-32=@var{cpu}
1192 @itemx --with-cpu-64=@var{cpu}
1193 Specify which cpu variant the compiler should generate code for by default.
1194 @var{cpu} will be used as the default value of the @option{-mcpu=} switch.
1195 This option is only supported on some targets, including ARM, i386, M68k,
1196 PowerPC, and SPARC@. The @option{--with-cpu-32} and
1197 @option{--with-cpu-64} options specify separate default CPUs for
1198 32-bit and 64-bit modes; these options are only supported for i386,
1201 @item --with-schedule=@var{cpu}
1202 @itemx --with-arch=@var{cpu}
1203 @itemx --with-arch-32=@var{cpu}
1204 @itemx --with-arch-64=@var{cpu}
1205 @itemx --with-tune=@var{cpu}
1206 @itemx --with-tune-32=@var{cpu}
1207 @itemx --with-tune-64=@var{cpu}
1208 @itemx --with-abi=@var{abi}
1209 @itemx --with-fpu=@var{type}
1210 @itemx --with-float=@var{type}
1211 These configure options provide default values for the @option{-mschedule=},
1212 @option{-march=}, @option{-mtune=}, @option{-mabi=}, and @option{-mfpu=}
1213 options and for @option{-mhard-float} or @option{-msoft-float}. As with
1214 @option{--with-cpu}, which switches will be accepted and acceptable values
1215 of the arguments depend on the target.
1217 @item --with-mode=@var{mode}
1218 Specify if the compiler should default to @option{-marm} or @option{-mthumb}.
1219 This option is only supported on ARM targets.
1221 @item --with-stack-offset=@var{num}
1222 This option sets the default for the -mstack-offset=@var{num} option,
1223 and will thus generally also control the setting of this option for
1224 libraries. This option is only supported on Epiphany targets.
1226 @item --with-fpmath=@var{isa}
1227 This options sets @option{-mfpmath=sse} by default and specifies the default
1228 ISA for floating-point arithmetics. You can select either @samp{sse} which
1229 enables @option{-msse2} or @samp{avx} which enables @option{-mavx} by default.
1230 This option is only supported on i386 and x86-64 targets.
1232 @item --with-divide=@var{type}
1233 Specify how the compiler should generate code for checking for
1234 division by zero. This option is only supported on the MIPS target.
1235 The possibilities for @var{type} are:
1238 Division by zero checks use conditional traps (this is the default on
1239 systems that support conditional traps).
1241 Division by zero checks use the break instruction.
1244 @c If you make --with-llsc the default for additional targets,
1245 @c update the --with-llsc description in the MIPS section below.
1248 On MIPS targets, make @option{-mllsc} the default when no
1249 @option{-mno-llsc} option is passed. This is the default for
1250 Linux-based targets, as the kernel will emulate them if the ISA does
1253 @item --without-llsc
1254 On MIPS targets, make @option{-mno-llsc} the default when no
1255 @option{-mllsc} option is passed.
1258 On MIPS targets, make @option{-msynci} the default when no
1259 @option{-mno-synci} option is passed.
1261 @item --without-synci
1262 On MIPS targets, make @option{-mno-synci} the default when no
1263 @option{-msynci} option is passed. This is the default.
1265 @item --with-mips-plt
1266 On MIPS targets, make use of copy relocations and PLTs.
1267 These features are extensions to the traditional
1268 SVR4-based MIPS ABIs and require support from GNU binutils
1269 and the runtime C library.
1271 @item --enable-__cxa_atexit
1272 Define if you want to use __cxa_atexit, rather than atexit, to
1273 register C++ destructors for local statics and global objects.
1274 This is essential for fully standards-compliant handling of
1275 destructors, but requires __cxa_atexit in libc. This option is currently
1276 only available on systems with GNU libc. When enabled, this will cause
1277 @option{-fuse-cxa-atexit} to be passed by default.
1279 @item --enable-gnu-indirect-function
1280 Define if you want to enable the @code{ifunc} attribute. This option is
1281 currently only available on systems with GNU libc on certain targets.
1283 @item --enable-target-optspace
1285 libraries should be optimized for code space instead of code speed.
1286 This is the default for the m32r platform.
1288 @item --with-cpp-install-dir=@var{dirname}
1289 Specify that the user visible @command{cpp} program should be installed
1290 in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
1292 @item --enable-comdat
1293 Enable COMDAT group support. This is primarily used to override the
1294 automatically detected value.
1296 @item --enable-initfini-array
1297 Force the use of sections @code{.init_array} and @code{.fini_array}
1298 (instead of @code{.init} and @code{.fini}) for constructors and
1299 destructors. Option @option{--disable-initfini-array} has the
1300 opposite effect. If neither option is specified, the configure script
1301 will try to guess whether the @code{.init_array} and
1302 @code{.fini_array} sections are supported and, if they are, use them.
1304 @item --enable-maintainer-mode
1305 The build rules that regenerate the Autoconf and Automake output files as
1306 well as the GCC master message catalog @file{gcc.pot} are normally
1307 disabled. This is because it can only be rebuilt if the complete source
1308 tree is present. If you have changed the sources and want to rebuild the
1309 catalog, configuring with @option{--enable-maintainer-mode} will enable
1310 this. Note that you need a recent version of the @code{gettext} tools
1313 @item --disable-bootstrap
1314 For a native build, the default configuration is to perform
1315 a 3-stage bootstrap of the compiler when @samp{make} is invoked,
1316 testing that GCC can compile itself correctly. If you want to disable
1317 this process, you can configure with @option{--disable-bootstrap}.
1319 @item --enable-bootstrap
1320 In special cases, you may want to perform a 3-stage build
1321 even if the target and host triplets are different.
1322 This is possible when the host can run code compiled for
1323 the target (e.g.@: host is i686-linux, target is i486-linux).
1324 Starting from GCC 4.2, to do this you have to configure explicitly
1325 with @option{--enable-bootstrap}.
1327 @item --enable-generated-files-in-srcdir
1328 Neither the .c and .h files that are generated from Bison and flex nor the
1329 info manuals and man pages that are built from the .texi files are present
1330 in the SVN development tree. When building GCC from that development tree,
1331 or from one of our snapshots, those generated files are placed in your
1332 build directory, which allows for the source to be in a readonly
1335 If you configure with @option{--enable-generated-files-in-srcdir} then those
1336 generated files will go into the source directory. This is mainly intended
1337 for generating release or prerelease tarballs of the GCC sources, since it
1338 is not a requirement that the users of source releases to have flex, Bison,
1341 @item --enable-version-specific-runtime-libs
1343 that runtime libraries should be installed in the compiler specific
1344 subdirectory (@file{@var{libdir}/gcc}) rather than the usual places. In
1345 addition, @samp{libstdc++}'s include files will be installed into
1346 @file{@var{libdir}} unless you overruled it by using
1347 @option{--with-gxx-include-dir=@var{dirname}}. Using this option is
1348 particularly useful if you intend to use several versions of GCC in
1349 parallel. This is currently supported by @samp{libgfortran},
1350 @samp{libjava}, @samp{libmudflap}, @samp{libstdc++}, and @samp{libobjc}.
1352 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
1353 Specify that only a particular subset of compilers and
1354 their runtime libraries should be built. For a list of valid values for
1355 @var{langN} you can issue the following command in the
1356 @file{gcc} directory of your GCC source tree:@*
1358 grep language= */config-lang.in
1360 Currently, you can use any of the following:
1361 @code{all}, @code{ada}, @code{c}, @code{c++}, @code{fortran},
1362 @code{go}, @code{java}, @code{objc}, @code{obj-c++}.
1363 Building the Ada compiler has special requirements, see below.
1364 If you do not pass this flag, or specify the option @code{all}, then all
1365 default languages available in the @file{gcc} sub-tree will be configured.
1366 Ada, Go and Objective-C++ are not default languages; the rest are.
1368 @item --enable-stage1-languages=@var{lang1},@var{lang2},@dots{}
1369 Specify that a particular subset of compilers and their runtime
1370 libraries should be built with the system C compiler during stage 1 of
1371 the bootstrap process, rather than only in later stages with the
1372 bootstrapped C compiler. The list of valid values is the same as for
1373 @option{--enable-languages}, and the option @code{all} will select all
1374 of the languages enabled by @option{--enable-languages}. This option is
1375 primarily useful for GCC development; for instance, when a development
1376 version of the compiler cannot bootstrap due to compiler bugs, or when
1377 one is debugging front ends other than the C front end. When this
1378 option is used, one can then build the target libraries for the
1379 specified languages with the stage-1 compiler by using @command{make
1380 stage1-bubble all-target}, or run the testsuite on the stage-1 compiler
1381 for the specified languages using @command{make stage1-start check-gcc}.
1383 @item --disable-libada
1384 Specify that the run-time libraries and tools used by GNAT should not
1385 be built. This can be useful for debugging, or for compatibility with
1386 previous Ada build procedures, when it was required to explicitly
1387 do a @samp{make -C gcc gnatlib_and_tools}.
1389 @item --disable-libssp
1390 Specify that the run-time libraries for stack smashing protection
1391 should not be built.
1393 @item --disable-libquadmath
1394 Specify that the GCC quad-precision math library should not be built.
1395 On some systems, the library is required to be linkable when building
1396 the Fortran front end, unless @option{--disable-libquadmath-support}
1399 @item --disable-libquadmath-support
1400 Specify that the Fortran front end and @code{libgfortran} do not add
1401 support for @code{libquadmath} on systems supporting it.
1403 @item --disable-libgomp
1404 Specify that the run-time libraries used by GOMP should not be built.
1407 Specify that the compiler should
1408 use DWARF 2 debugging information as the default.
1410 @item --enable-targets=all
1411 @itemx --enable-targets=@var{target_list}
1412 Some GCC targets, e.g.@: powerpc64-linux, build bi-arch compilers.
1413 These are compilers that are able to generate either 64-bit or 32-bit
1414 code. Typically, the corresponding 32-bit target, e.g.@:
1415 powerpc-linux for powerpc64-linux, only generates 32-bit code. This
1416 option enables the 32-bit target to be a bi-arch compiler, which is
1417 useful when you want a bi-arch compiler that defaults to 32-bit, and
1418 you are building a bi-arch or multi-arch binutils in a combined tree.
1419 On mips-linux, this will build a tri-arch compiler (ABI o32/n32/64),
1421 Currently, this option only affects sparc-linux, powerpc-linux, x86-linux,
1422 mips-linux and s390-linux.
1424 @item --enable-secureplt
1425 This option enables @option{-msecure-plt} by default for powerpc-linux.
1427 @xref{RS/6000 and PowerPC Options,, RS/6000 and PowerPC Options, gcc,
1428 Using the GNU Compiler Collection (GCC)},
1431 See ``RS/6000 and PowerPC Options'' in the main manual
1435 This option enables @option{-mcld} by default for 32-bit x86 targets.
1437 @xref{i386 and x86-64 Options,, i386 and x86-64 Options, gcc,
1438 Using the GNU Compiler Collection (GCC)},
1441 See ``i386 and x86-64 Options'' in the main manual
1444 @item --enable-win32-registry
1445 @itemx --enable-win32-registry=@var{key}
1446 @itemx --disable-win32-registry
1447 The @option{--enable-win32-registry} option enables Microsoft Windows-hosted GCC
1448 to look up installations paths in the registry using the following key:
1451 @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
1454 @var{key} defaults to GCC version number, and can be overridden by the
1455 @option{--enable-win32-registry=@var{key}} option. Vendors and distributors
1456 who use custom installers are encouraged to provide a different key,
1457 perhaps one comprised of vendor name and GCC version number, to
1458 avoid conflict with existing installations. This feature is enabled
1459 by default, and can be disabled by @option{--disable-win32-registry}
1460 option. This option has no effect on the other hosts.
1463 Specify that the machine does not have a floating point unit. This
1464 option only applies to @samp{m68k-sun-sunos@var{n}}. On any other
1465 system, @option{--nfp} has no effect.
1467 @item --enable-werror
1468 @itemx --disable-werror
1469 @itemx --enable-werror=yes
1470 @itemx --enable-werror=no
1471 When you specify this option, it controls whether certain files in the
1472 compiler are built with @option{-Werror} in bootstrap stage2 and later.
1473 If you don't specify it, @option{-Werror} is turned on for the main
1474 development trunk. However it defaults to off for release branches and
1475 final releases. The specific files which get @option{-Werror} are
1476 controlled by the Makefiles.
1478 @item --enable-checking
1479 @itemx --enable-checking=@var{list}
1480 When you specify this option, the compiler is built to perform internal
1481 consistency checks of the requested complexity. This does not change the
1482 generated code, but adds error checking within the compiler. This will
1483 slow down the compiler and may only work properly if you are building
1484 the compiler with GCC@. This is @samp{yes} by default when building
1485 from SVN or snapshots, but @samp{release} for releases. The default
1486 for building the stage1 compiler is @samp{yes}. More control
1487 over the checks may be had by specifying @var{list}. The categories of
1488 checks available are @samp{yes} (most common checks
1489 @samp{assert,misc,tree,gc,rtlflag,runtime}), @samp{no} (no checks at
1490 all), @samp{all} (all but @samp{valgrind}), @samp{release} (cheapest
1491 checks @samp{assert,runtime}) or @samp{none} (same as @samp{no}).
1492 Individual checks can be enabled with these flags @samp{assert},
1493 @samp{df}, @samp{fold}, @samp{gc}, @samp{gcac} @samp{misc}, @samp{rtl},
1494 @samp{rtlflag}, @samp{runtime}, @samp{tree}, and @samp{valgrind}.
1496 The @samp{valgrind} check requires the external @command{valgrind}
1497 simulator, available from @uref{http://valgrind.org/}. The
1498 @samp{df}, @samp{rtl}, @samp{gcac} and @samp{valgrind} checks are very expensive.
1499 To disable all checking, @samp{--disable-checking} or
1500 @samp{--enable-checking=none} must be explicitly requested. Disabling
1501 assertions will make the compiler and runtime slightly faster but
1502 increase the risk of undetected internal errors causing wrong code to be
1505 @item --disable-stage1-checking
1506 @itemx --enable-stage1-checking
1507 @itemx --enable-stage1-checking=@var{list}
1508 If no @option{--enable-checking} option is specified the stage1
1509 compiler will be built with @samp{yes} checking enabled, otherwise
1510 the stage1 checking flags are the same as specified by
1511 @option{--enable-checking}. To build the stage1 compiler with
1512 different checking options use @option{--enable-stage1-checking}.
1513 The list of checking options is the same as for @option{--enable-checking}.
1514 If your system is too slow or too small to bootstrap a released compiler
1515 with checking for stage1 enabled, you can use @samp{--disable-stage1-checking}
1516 to disable checking for the stage1 compiler.
1518 @item --enable-coverage
1519 @itemx --enable-coverage=@var{level}
1520 With this option, the compiler is built to collect self coverage
1521 information, every time it is run. This is for internal development
1522 purposes, and only works when the compiler is being built with gcc. The
1523 @var{level} argument controls whether the compiler is built optimized or
1524 not, values are @samp{opt} and @samp{noopt}. For coverage analysis you
1525 want to disable optimization, for performance analysis you want to
1526 enable optimization. When coverage is enabled, the default level is
1527 without optimization.
1529 @item --enable-gather-detailed-mem-stats
1530 When this option is specified more detailed information on memory
1531 allocation is gathered. This information is printed when using
1532 @option{-fmem-report}.
1535 @itemx --with-gc=@var{choice}
1536 With this option you can specify the garbage collector implementation
1537 used during the compilation process. @var{choice} can be one of
1538 @samp{page} and @samp{zone}, where @samp{page} is the default.
1541 @itemx --disable-nls
1542 The @option{--enable-nls} option enables Native Language Support (NLS),
1543 which lets GCC output diagnostics in languages other than American
1544 English. Native Language Support is enabled by default if not doing a
1545 canadian cross build. The @option{--disable-nls} option disables NLS@.
1547 @item --with-included-gettext
1548 If NLS is enabled, the @option{--with-included-gettext} option causes the build
1549 procedure to prefer its copy of GNU @command{gettext}.
1551 @item --with-catgets
1552 If NLS is enabled, and if the host lacks @code{gettext} but has the
1553 inferior @code{catgets} interface, the GCC build procedure normally
1554 ignores @code{catgets} and instead uses GCC's copy of the GNU
1555 @code{gettext} library. The @option{--with-catgets} option causes the
1556 build procedure to use the host's @code{catgets} in this situation.
1558 @item --with-libiconv-prefix=@var{dir}
1559 Search for libiconv header files in @file{@var{dir}/include} and
1560 libiconv library files in @file{@var{dir}/lib}.
1562 @item --enable-obsolete
1563 Enable configuration for an obsoleted system. If you attempt to
1564 configure GCC for a system (build, host, or target) which has been
1565 obsoleted, and you do not specify this flag, configure will halt with an
1568 All support for systems which have been obsoleted in one release of GCC
1569 is removed entirely in the next major release, unless someone steps
1570 forward to maintain the port.
1572 @item --enable-decimal-float
1573 @itemx --enable-decimal-float=yes
1574 @itemx --enable-decimal-float=no
1575 @itemx --enable-decimal-float=bid
1576 @itemx --enable-decimal-float=dpd
1577 @itemx --disable-decimal-float
1578 Enable (or disable) support for the C decimal floating point extension
1579 that is in the IEEE 754-2008 standard. This is enabled by default only
1580 on PowerPC, i386, and x86_64 GNU/Linux systems. Other systems may also
1581 support it, but require the user to specifically enable it. You can
1582 optionally control which decimal floating point format is used (either
1583 @samp{bid} or @samp{dpd}). The @samp{bid} (binary integer decimal)
1584 format is default on i386 and x86_64 systems, and the @samp{dpd}
1585 (densely packed decimal) format is default on PowerPC systems.
1587 @item --enable-fixed-point
1588 @itemx --disable-fixed-point
1589 Enable (or disable) support for C fixed-point arithmetic.
1590 This option is enabled by default for some targets (such as MIPS) which
1591 have hardware-support for fixed-point operations. On other targets, you
1592 may enable this option manually.
1594 @item --with-long-double-128
1595 Specify if @code{long double} type should be 128-bit by default on selected
1596 GNU/Linux architectures. If using @code{--without-long-double-128},
1597 @code{long double} will be by default 64-bit, the same as @code{double} type.
1598 When neither of these configure options are used, the default will be
1599 128-bit @code{long double} when built against GNU C Library 2.4 and later,
1600 64-bit @code{long double} otherwise.
1602 @item --with-gmp=@var{pathname}
1603 @itemx --with-gmp-include=@var{pathname}
1604 @itemx --with-gmp-lib=@var{pathname}
1605 @itemx --with-mpfr=@var{pathname}
1606 @itemx --with-mpfr-include=@var{pathname}
1607 @itemx --with-mpfr-lib=@var{pathname}
1608 @itemx --with-mpc=@var{pathname}
1609 @itemx --with-mpc-include=@var{pathname}
1610 @itemx --with-mpc-lib=@var{pathname}
1611 If you want to build GCC but do not have the GMP library, the MPFR
1612 library and/or the MPC library installed in a standard location and
1613 do not have their sources present in the GCC source tree then you
1614 can explicitly specify the directory where they are installed
1615 (@samp{--with-gmp=@var{gmpinstalldir}},
1616 @samp{--with-mpfr=@/@var{mpfrinstalldir}},
1617 @samp{--with-mpc=@/@var{mpcinstalldir}}). The
1618 @option{--with-gmp=@/@var{gmpinstalldir}} option is shorthand for
1619 @option{--with-gmp-lib=@/@var{gmpinstalldir}/lib} and
1620 @option{--with-gmp-include=@/@var{gmpinstalldir}/include}. Likewise the
1621 @option{--with-mpfr=@/@var{mpfrinstalldir}} option is shorthand for
1622 @option{--with-mpfr-lib=@/@var{mpfrinstalldir}/lib} and
1623 @option{--with-mpfr-include=@/@var{mpfrinstalldir}/include}, also the
1624 @option{--with-mpc=@/@var{mpcinstalldir}} option is shorthand for
1625 @option{--with-mpc-lib=@/@var{mpcinstalldir}/lib} and
1626 @option{--with-mpc-include=@/@var{mpcinstalldir}/include}. If these
1627 shorthand assumptions are not correct, you can use the explicit
1628 include and lib options directly. You might also need to ensure the
1629 shared libraries can be found by the dynamic linker when building and
1630 using GCC, for example by setting the runtime shared library path
1631 variable (@env{LD_LIBRARY_PATH} on GNU/Linux and Solaris systems).
1633 These flags are applicable to the host platform only. When building
1634 a cross compiler, they will not be used to configure target libraries.
1636 @item --with-ppl=@var{pathname}
1637 @itemx --with-ppl-include=@var{pathname}
1638 @itemx --with-ppl-lib=@var{pathname}
1639 @itemx --with-cloog=@var{pathname}
1640 @itemx --with-cloog-include=@var{pathname}
1641 @itemx --with-cloog-lib=@var{pathname}
1642 If you do not have ISL and the CLooG
1643 libraries installed in a standard location and you want to build GCC,
1644 you can explicitly specify the directory where they are installed
1645 (@samp{--with-isl=@/@var{islinstalldir}},
1646 @samp{--with-cloog=@/@var{clooginstalldir}}). The
1647 @option{--with-isl=@/@var{islinstalldir}} option is shorthand for
1648 @option{--with-isl-lib=@/@var{islinstalldir}/lib} and
1649 @option{--with-isl-include=@/@var{islinstalldir}/include}. Likewise the
1650 @option{--with-cloog=@/@var{clooginstalldir}} option is shorthand for
1651 @option{--with-cloog-lib=@/@var{clooginstalldir}/lib} and
1652 @option{--with-cloog-include=@/@var{clooginstalldir}/include}. If these
1653 shorthand assumptions are not correct, you can use the explicit
1654 include and lib options directly.
1656 These flags are applicable to the host platform only. When building
1657 a cross compiler, they will not be used to configure target libraries.
1659 @item --with-host-libstdcxx=@var{linker-args}
1660 If you are linking with a static copy of PPL, you can use this option
1661 to specify how the linker should find the standard C++ library used
1662 internally by PPL. Typical values of @var{linker-args} might be
1663 @samp{-lstdc++} or @samp{-Wl,-Bstatic,-lstdc++,-Bdynamic -lm}. If you are
1664 linking with a shared copy of PPL, you probably do not need this
1665 option; shared library dependencies will cause the linker to search
1666 for the standard C++ library automatically.
1668 @item --with-stage1-ldflags=@var{flags}
1669 This option may be used to set linker flags to be used when linking
1670 stage 1 of GCC. These are also used when linking GCC if configured with
1671 @option{--disable-bootstrap}. By default no special flags are used.
1673 @item --with-stage1-libs=@var{libs}
1674 This option may be used to set libraries to be used when linking stage 1
1675 of GCC. These are also used when linking GCC if configured with
1676 @option{--disable-bootstrap}. The default is the argument to
1677 @option{--with-host-libstdcxx}, if specified.
1679 @item --with-boot-ldflags=@var{flags}
1680 This option may be used to set linker flags to be used when linking
1681 stage 2 and later when bootstrapping GCC. If neither --with-boot-libs
1682 nor --with-host-libstdcxx is set to a value, then the default is
1683 @samp{-static-libstdc++ -static-libgcc}.
1685 @item --with-boot-libs=@var{libs}
1686 This option may be used to set libraries to be used when linking stage 2
1687 and later when bootstrapping GCC. The default is the argument to
1688 @option{--with-host-libstdcxx}, if specified.
1690 @item --with-debug-prefix-map=@var{map}
1691 Convert source directory names using @option{-fdebug-prefix-map} when
1692 building runtime libraries. @samp{@var{map}} is a space-separated
1693 list of maps of the form @samp{@var{old}=@var{new}}.
1695 @item --enable-linker-build-id
1696 Tells GCC to pass @option{--build-id} option to the linker for all final
1697 links (links performed without the @option{-r} or @option{--relocatable}
1698 option), if the linker supports it. If you specify
1699 @option{--enable-linker-build-id}, but your linker does not
1700 support @option{--build-id} option, a warning is issued and the
1701 @option{--enable-linker-build-id} option is ignored. The default is off.
1703 @item --with-linker-hash-style=@var{choice}
1704 Tells GCC to pass @option{--hash-style=@var{choice}} option to the
1705 linker for all final links. @var{choice} can be one of
1706 @samp{sysv}, @samp{gnu}, and @samp{both} where @samp{sysv} is the default.
1708 @item --enable-gnu-unique-object
1709 @itemx --disable-gnu-unique-object
1710 Tells GCC to use the gnu_unique_object relocation for C++ template
1711 static data members and inline function local statics. Enabled by
1712 default for a native toolchain with an assembler that accepts it and
1713 GLIBC 2.11 or above, otherwise disabled.
1716 @itemx --disable-lto
1717 Enable support for link-time optimization (LTO). This is enabled by
1718 default, and may be disabled using @option{--disable-lto}.
1720 @item --with-plugin-ld=@var{pathname}
1721 Enable an alternate linker to be used at link-time optimization (LTO)
1722 link time when @option{-fuse-linker-plugin} is enabled.
1723 This linker should have plugin support such as gold starting with
1724 version 2.20 or GNU ld starting with version 2.21.
1725 See @option{-fuse-linker-plugin} for details.
1727 @item --enable-canonical-system-headers
1728 @itemx --disable-canonical-system-headers
1729 Enable system header path canonicalization for @file{libcpp}. This can
1730 produce shorter header file paths in diagnostics and dependency output
1731 files, but these changed header paths may conflict with some compilation
1732 environments. Enabled by default, and may be disabled using
1733 @option{--disable-canonical-system-headers}.
1736 @subheading Cross-Compiler-Specific Options
1737 The following options only apply to building cross compilers.
1740 @item --with-sysroot
1741 @itemx --with-sysroot=@var{dir}
1742 Tells GCC to consider @var{dir} as the root of a tree that contains
1743 (a subset of) the root filesystem of the target operating system.
1744 Target system headers, libraries and run-time object files will be
1745 searched for in there. More specifically, this acts as if
1746 @option{--sysroot=@var{dir}} was added to the default options of the built
1747 compiler. The specified directory is not copied into the
1748 install tree, unlike the options @option{--with-headers} and
1749 @option{--with-libs} that this option obsoletes. The default value,
1750 in case @option{--with-sysroot} is not given an argument, is
1751 @option{$@{gcc_tooldir@}/sys-root}. If the specified directory is a
1752 subdirectory of @option{$@{exec_prefix@}}, then it will be found relative to
1753 the GCC binaries if the installation tree is moved.
1755 This option affects the system root for the compiler used to build
1756 target libraries (which runs on the build system) and the compiler newly
1757 installed with @code{make install}; it does not affect the compiler which is
1758 used to build GCC itself.
1760 If you specify the @option{--with-native-system-header-dir=@var{dirname}}
1761 option then the compiler will search that directory within @var{dirname} for
1762 native system headers rather than the default @file{/usr/include}.
1764 @item --with-build-sysroot
1765 @itemx --with-build-sysroot=@var{dir}
1766 Tells GCC to consider @var{dir} as the system root (see
1767 @option{--with-sysroot}) while building target libraries, instead of
1768 the directory specified with @option{--with-sysroot}. This option is
1769 only useful when you are already using @option{--with-sysroot}. You
1770 can use @option{--with-build-sysroot} when you are configuring with
1771 @option{--prefix} set to a directory that is different from the one in
1772 which you are installing GCC and your target libraries.
1774 This option affects the system root for the compiler used to build
1775 target libraries (which runs on the build system); it does not affect
1776 the compiler which is used to build GCC itself.
1778 If you specify the @option{--with-native-system-header-dir=@var{dirname}}
1779 option then the compiler will search that directory within @var{dirname} for
1780 native system headers rather than the default @file{/usr/include}.
1782 @item --with-headers
1783 @itemx --with-headers=@var{dir}
1784 Deprecated in favor of @option{--with-sysroot}.
1785 Specifies that target headers are available when building a cross compiler.
1786 The @var{dir} argument specifies a directory which has the target include
1787 files. These include files will be copied into the @file{gcc} install
1788 directory. @emph{This option with the @var{dir} argument is required} when
1789 building a cross compiler, if @file{@var{prefix}/@var{target}/sys-include}
1790 doesn't pre-exist. If @file{@var{prefix}/@var{target}/sys-include} does
1791 pre-exist, the @var{dir} argument may be omitted. @command{fixincludes}
1792 will be run on these files to make them compatible with GCC@.
1794 @item --without-headers
1795 Tells GCC not use any target headers from a libc when building a cross
1796 compiler. When crossing to GNU/Linux, you need the headers so GCC
1797 can build the exception handling for libgcc.
1800 @itemx --with-libs="@var{dir1} @var{dir2} @dots{} @var{dirN}"
1801 Deprecated in favor of @option{--with-sysroot}.
1802 Specifies a list of directories which contain the target runtime
1803 libraries. These libraries will be copied into the @file{gcc} install
1804 directory. If the directory list is omitted, this option has no
1808 Specifies that @samp{newlib} is
1809 being used as the target C library. This causes @code{__eprintf} to be
1810 omitted from @file{libgcc.a} on the assumption that it will be provided by
1813 @item --with-avrlibc
1814 Specifies that @samp{AVR-Libc} is
1815 being used as the target C library. This causes float support
1816 functions like @code{__addsf3} to be omitted from @file{libgcc.a} on
1817 the assumption that it will be provided by @file{libm.a}. For more
1818 technical details, cf. @uref{http://gcc.gnu.org/PR54461,,PR54461}.
1819 This option is only supported for the AVR target. It is not supported for
1820 RTEMS configurations, which currently use newlib. The option is
1821 supported since version 4.7.2 and is the default in 4.8.0 and newer.
1823 @item --with-build-time-tools=@var{dir}
1824 Specifies where to find the set of target tools (assembler, linker, etc.)
1825 that will be used while building GCC itself. This option can be useful
1826 if the directory layouts are different between the system you are building
1827 GCC on, and the system where you will deploy it.
1829 For example, on an @samp{ia64-hp-hpux} system, you may have the GNU
1830 assembler and linker in @file{/usr/bin}, and the native tools in a
1831 different path, and build a toolchain that expects to find the
1832 native tools in @file{/usr/bin}.
1834 When you use this option, you should ensure that @var{dir} includes
1835 @command{ar}, @command{as}, @command{ld}, @command{nm},
1836 @command{ranlib} and @command{strip} if necessary, and possibly
1837 @command{objdump}. Otherwise, GCC may use an inconsistent set of
1841 @subheading Java-Specific Options
1843 The following option applies to the build of the Java front end.
1846 @item --disable-libgcj
1847 Specify that the run-time libraries
1848 used by GCJ should not be built. This is useful in case you intend
1849 to use GCJ with some other run-time, or you're going to install it
1850 separately, or it just happens not to build on your particular
1851 machine. In general, if the Java front end is enabled, the GCJ
1852 libraries will be enabled too, unless they're known to not work on
1853 the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
1854 may need to port it; in this case, before modifying the top-level
1855 @file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
1856 you may use @option{--enable-libgcj} to override the default.
1860 The following options apply to building @samp{libgcj}.
1862 @subsubheading General Options
1865 @item --enable-java-maintainer-mode
1866 By default the @samp{libjava} build will not attempt to compile the
1867 @file{.java} source files to @file{.class}. Instead, it will use the
1868 @file{.class} files from the source tree. If you use this option you
1869 must have executables named @command{ecj1} and @command{gjavah} in your path
1870 for use by the build. You must use this option if you intend to
1871 modify any @file{.java} files in @file{libjava}.
1873 @item --with-java-home=@var{dirname}
1874 This @samp{libjava} option overrides the default value of the
1875 @samp{java.home} system property. It is also used to set
1876 @samp{sun.boot.class.path} to @file{@var{dirname}/lib/rt.jar}. By
1877 default @samp{java.home} is set to @file{@var{prefix}} and
1878 @samp{sun.boot.class.path} to
1879 @file{@var{datadir}/java/libgcj-@var{version}.jar}.
1881 @item --with-ecj-jar=@var{filename}
1882 This option can be used to specify the location of an external jar
1883 file containing the Eclipse Java compiler. A specially modified
1884 version of this compiler is used by @command{gcj} to parse
1885 @file{.java} source files. If this option is given, the
1886 @samp{libjava} build will create and install an @file{ecj1} executable
1887 which uses this jar file at runtime.
1889 If this option is not given, but an @file{ecj.jar} file is found in
1890 the topmost source tree at configure time, then the @samp{libgcj}
1891 build will create and install @file{ecj1}, and will also install the
1892 discovered @file{ecj.jar} into a suitable place in the install tree.
1894 If @file{ecj1} is not installed, then the user will have to supply one
1895 on his path in order for @command{gcj} to properly parse @file{.java}
1896 source files. A suitable jar is available from
1897 @uref{ftp://sourceware.org/pub/java/}.
1899 @item --disable-getenv-properties
1900 Don't set system properties from @env{GCJ_PROPERTIES}.
1902 @item --enable-hash-synchronization
1903 Use a global hash table for monitor locks. Ordinarily,
1904 @samp{libgcj}'s @samp{configure} script automatically makes
1905 the correct choice for this option for your platform. Only use
1906 this if you know you need the library to be configured differently.
1908 @item --enable-interpreter
1909 Enable the Java interpreter. The interpreter is automatically
1910 enabled by default on all platforms that support it. This option
1911 is really only useful if you want to disable the interpreter
1912 (using @option{--disable-interpreter}).
1914 @item --disable-java-net
1915 Disable java.net. This disables the native part of java.net only,
1916 using non-functional stubs for native method implementations.
1918 @item --disable-jvmpi
1919 Disable JVMPI support.
1921 @item --disable-libgcj-bc
1922 Disable BC ABI compilation of certain parts of libgcj. By default,
1923 some portions of libgcj are compiled with @option{-findirect-dispatch}
1924 and @option{-fno-indirect-classes}, allowing them to be overridden at
1927 If @option{--disable-libgcj-bc} is specified, libgcj is built without
1928 these options. This allows the compile-time linker to resolve
1929 dependencies when statically linking to libgcj. However it makes it
1930 impossible to override the affected portions of libgcj at run-time.
1932 @item --enable-reduced-reflection
1933 Build most of libgcj with @option{-freduced-reflection}. This reduces
1934 the size of libgcj at the expense of not being able to do accurate
1935 reflection on the classes it contains. This option is safe if you
1936 know that code using libgcj will never use reflection on the standard
1937 runtime classes in libgcj (including using serialization, RMI or CORBA).
1940 Enable runtime eCos target support.
1942 @item --without-libffi
1943 Don't use @samp{libffi}. This will disable the interpreter and JNI
1944 support as well, as these require @samp{libffi} to work.
1946 @item --enable-libgcj-debug
1947 Enable runtime debugging code.
1949 @item --enable-libgcj-multifile
1950 If specified, causes all @file{.java} source files to be
1951 compiled into @file{.class} files in one invocation of
1952 @samp{gcj}. This can speed up build time, but is more
1953 resource-intensive. If this option is unspecified or
1954 disabled, @samp{gcj} is invoked once for each @file{.java}
1955 file to compile into a @file{.class} file.
1957 @item --with-libiconv-prefix=DIR
1958 Search for libiconv in @file{DIR/include} and @file{DIR/lib}.
1960 @item --enable-sjlj-exceptions
1961 Force use of the @code{setjmp}/@code{longjmp}-based scheme for exceptions.
1962 @samp{configure} ordinarily picks the correct value based on the platform.
1963 Only use this option if you are sure you need a different setting.
1965 @item --with-system-zlib
1966 Use installed @samp{zlib} rather than that included with GCC@.
1968 @item --with-win32-nlsapi=ansi, unicows or unicode
1969 Indicates how MinGW @samp{libgcj} translates between UNICODE
1970 characters and the Win32 API@.
1972 @item --enable-java-home
1973 If enabled, this creates a JPackage compatible SDK environment during install.
1974 Note that if --enable-java-home is used, --with-arch-directory=ARCH must also
1977 @item --with-arch-directory=ARCH
1978 Specifies the name to use for the @file{jre/lib/ARCH} directory in the SDK
1979 environment created when --enable-java-home is passed. Typical names for this
1980 directory include i386, amd64, ia64, etc.
1982 @item --with-os-directory=DIR
1983 Specifies the OS directory for the SDK include directory. This is set to auto
1984 detect, and is typically 'linux'.
1986 @item --with-origin-name=NAME
1987 Specifies the JPackage origin name. This defaults to the 'gcj' in
1990 @item --with-arch-suffix=SUFFIX
1991 Specifies the suffix for the sdk directory. Defaults to the empty string.
1992 Examples include '.x86_64' in 'java-1.5.0-gcj-1.5.0.0.x86_64'.
1994 @item --with-jvm-root-dir=DIR
1995 Specifies where to install the SDK. Default is $(prefix)/lib/jvm.
1997 @item --with-jvm-jar-dir=DIR
1998 Specifies where to install jars. Default is $(prefix)/lib/jvm-exports.
2000 @item --with-python-dir=DIR
2001 Specifies where to install the Python modules used for aot-compile. DIR should
2002 not include the prefix used in installation. For example, if the Python modules
2003 are to be installed in /usr/lib/python2.5/site-packages, then
2004 --with-python-dir=/lib/python2.5/site-packages should be passed. If this is
2005 not specified, then the Python modules are installed in $(prefix)/share/python.
2007 @item --enable-aot-compile-rpm
2008 Adds aot-compile-rpm to the list of installed scripts.
2010 @item --enable-browser-plugin
2011 Build the gcjwebplugin web browser plugin.
2013 @item --enable-static-libjava
2014 Build static libraries in libjava. The default is to only build shared
2019 Use the single-byte @code{char} and the Win32 A functions natively,
2020 translating to and from UNICODE when using these functions. If
2021 unspecified, this is the default.
2024 Use the @code{WCHAR} and Win32 W functions natively. Adds
2025 @code{-lunicows} to @file{libgcj.spec} to link with @samp{libunicows}.
2026 @file{unicows.dll} needs to be deployed on Microsoft Windows 9X machines
2027 running built executables. @file{libunicows.a}, an open-source
2028 import library around Microsoft's @code{unicows.dll}, is obtained from
2029 @uref{http://libunicows.sourceforge.net/}, which also gives details
2030 on getting @file{unicows.dll} from Microsoft.
2033 Use the @code{WCHAR} and Win32 W functions natively. Does @emph{not}
2034 add @code{-lunicows} to @file{libgcj.spec}. The built executables will
2035 only run on Microsoft Windows NT and above.
2039 @subsubheading AWT-Specific Options
2043 Use the X Window System.
2045 @item --enable-java-awt=PEER(S)
2046 Specifies the AWT peer library or libraries to build alongside
2047 @samp{libgcj}. If this option is unspecified or disabled, AWT
2048 will be non-functional. Current valid values are @option{gtk} and
2049 @option{xlib}. Multiple libraries should be separated by a
2050 comma (i.e.@: @option{--enable-java-awt=gtk,xlib}).
2052 @item --enable-gtk-cairo
2053 Build the cairo Graphics2D implementation on GTK@.
2055 @item --enable-java-gc=TYPE
2056 Choose garbage collector. Defaults to @option{boehm} if unspecified.
2058 @item --disable-gtktest
2059 Do not try to compile and run a test GTK+ program.
2061 @item --disable-glibtest
2062 Do not try to compile and run a test GLIB program.
2064 @item --with-libart-prefix=PFX
2065 Prefix where libart is installed (optional).
2067 @item --with-libart-exec-prefix=PFX
2068 Exec prefix where libart is installed (optional).
2070 @item --disable-libarttest
2071 Do not try to compile and run a test libart program.
2075 @subsubheading Overriding @command{configure} test results
2077 Sometimes, it might be necessary to override the result of some
2078 @command{configure} test, for example in order to ease porting to a new
2079 system or work around a bug in a test. The toplevel @command{configure}
2080 script provides three variables for this:
2084 @item build_configargs
2085 @cindex @code{build_configargs}
2086 The contents of this variable is passed to all build @command{configure}
2089 @item host_configargs
2090 @cindex @code{host_configargs}
2091 The contents of this variable is passed to all host @command{configure}
2094 @item target_configargs
2095 @cindex @code{target_configargs}
2096 The contents of this variable is passed to all target @command{configure}
2101 In order to avoid shell and @command{make} quoting issues for complex
2102 overrides, you can pass a setting for @env{CONFIG_SITE} and set
2103 variables in the site file.
2110 @uref{./index.html,,Return to the GCC Installation page}
2114 @c ***Building****************************************************************
2116 @comment node-name, next, previous, up
2117 @node Building, Testing, Configuration, Installing GCC
2123 @cindex Installing GCC: Building
2125 Now that GCC is configured, you are ready to build the compiler and
2128 Some commands executed when making the compiler may fail (return a
2129 nonzero status) and be ignored by @command{make}. These failures, which
2130 are often due to files that were not found, are expected, and can safely
2133 It is normal to have compiler warnings when compiling certain files.
2134 Unless you are a GCC developer, you can generally ignore these warnings
2135 unless they cause compilation to fail. Developers should attempt to fix
2136 any warnings encountered, however they can temporarily continue past
2137 warnings-as-errors by specifying the configure flag
2138 @option{--disable-werror}.
2140 On certain old systems, defining certain environment variables such as
2141 @env{CC} can interfere with the functioning of @command{make}.
2143 If you encounter seemingly strange errors when trying to build the
2144 compiler in a directory other than the source directory, it could be
2145 because you have previously configured the compiler in the source
2146 directory. Make sure you have done all the necessary preparations.
2148 If you build GCC on a BSD system using a directory stored in an old System
2149 V file system, problems may occur in running @command{fixincludes} if the
2150 System V file system doesn't support symbolic links. These problems
2151 result in a failure to fix the declaration of @code{size_t} in
2152 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
2153 that type mismatches occur, this could be the cause.
2155 The solution is not to use such a directory for building GCC@.
2157 Similarly, when building from SVN or snapshots, or if you modify
2158 @file{*.l} files, you need the Flex lexical analyzer generator
2159 installed. If you do not modify @file{*.l} files, releases contain
2160 the Flex-generated files and you do not need Flex installed to build
2161 them. There is still one Flex-based lexical analyzer (part of the
2162 build machinery, not of GCC itself) that is used even if you only
2163 build the C front end.
2165 When building from SVN or snapshots, or if you modify Texinfo
2166 documentation, you need version 4.7 or later of Texinfo installed if you
2167 want Info documentation to be regenerated. Releases contain Info
2168 documentation pre-built for the unmodified documentation in the release.
2170 @section Building a native compiler
2172 For a native build, the default configuration is to perform
2173 a 3-stage bootstrap of the compiler when @samp{make} is invoked.
2174 This will build the entire GCC system and ensure that it compiles
2175 itself correctly. It can be disabled with the @option{--disable-bootstrap}
2176 parameter to @samp{configure}, but bootstrapping is suggested because
2177 the compiler will be tested more completely and could also have
2180 The bootstrapping process will complete the following steps:
2184 Build tools necessary to build the compiler.
2187 Perform a 3-stage bootstrap of the compiler. This includes building
2188 three times the target tools for use by the compiler such as binutils
2189 (bfd, binutils, gas, gprof, ld, and opcodes) if they have been
2190 individually linked or moved into the top level GCC source tree before
2194 Perform a comparison test of the stage2 and stage3 compilers.
2197 Build runtime libraries using the stage3 compiler from the previous step.
2201 If you are short on disk space you might consider @samp{make
2202 bootstrap-lean} instead. The sequence of compilation is the
2203 same described above, but object files from the stage1 and
2204 stage2 of the 3-stage bootstrap of the compiler are deleted as
2205 soon as they are no longer needed.
2207 If you wish to use non-default GCC flags when compiling the stage2
2208 and stage3 compilers, set @code{BOOT_CFLAGS} on the command line when
2209 doing @samp{make}. For example, if you want to save additional space
2210 during the bootstrap and in the final installation as well, you can
2211 build the compiler binaries without debugging information as in the
2212 following example. This will save roughly 40% of disk space both for
2213 the bootstrap and the final installation. (Libraries will still contain
2214 debugging information.)
2217 make BOOT_CFLAGS='-O' bootstrap
2220 You can place non-default optimization flags into @code{BOOT_CFLAGS}; they
2221 are less well tested here than the default of @samp{-g -O2}, but should
2222 still work. In a few cases, you may find that you need to specify special
2223 flags such as @option{-msoft-float} here to complete the bootstrap; or,
2224 if the native compiler miscompiles the stage1 compiler, you may need
2225 to work around this, by choosing @code{BOOT_CFLAGS} to avoid the parts
2226 of the stage1 compiler that were miscompiled, or by using @samp{make
2227 bootstrap4} to increase the number of stages of bootstrap.
2229 @code{BOOT_CFLAGS} does not apply to bootstrapped target libraries.
2230 Since these are always compiled with the compiler currently being
2231 bootstrapped, you can use @code{CFLAGS_FOR_TARGET} to modify their
2232 compilation flags, as for non-bootstrapped target libraries.
2233 Again, if the native compiler miscompiles the stage1 compiler, you may
2234 need to work around this by avoiding non-working parts of the stage1
2235 compiler. Use @code{STAGE1_TFLAGS} to this end.
2237 If you used the flag @option{--enable-languages=@dots{}} to restrict
2238 the compilers to be built, only those you've actually enabled will be
2239 built. This will of course only build those runtime libraries, for
2240 which the particular compiler has been built. Please note,
2241 that re-defining @env{LANGUAGES} when calling @samp{make}
2242 @strong{does not} work anymore!
2244 If the comparison of stage2 and stage3 fails, this normally indicates
2245 that the stage2 compiler has compiled GCC incorrectly, and is therefore
2246 a potentially serious bug which you should investigate and report. (On
2247 a few systems, meaningful comparison of object files is impossible; they
2248 always appear ``different''. If you encounter this problem, you will
2249 need to disable comparison in the @file{Makefile}.)
2251 If you do not want to bootstrap your compiler, you can configure with
2252 @option{--disable-bootstrap}. In particular cases, you may want to
2253 bootstrap your compiler even if the target system is not the same as
2254 the one you are building on: for example, you could build a
2255 @code{powerpc-unknown-linux-gnu} toolchain on a
2256 @code{powerpc64-unknown-linux-gnu} host. In this case, pass
2257 @option{--enable-bootstrap} to the configure script.
2259 @code{BUILD_CONFIG} can be used to bring in additional customization
2260 to the build. It can be set to a whitespace-separated list of names.
2261 For each such @code{NAME}, top-level @file{config/@code{NAME}.mk} will
2262 be included by the top-level @file{Makefile}, bringing in any settings
2263 it contains. The default @code{BUILD_CONFIG} can be set using the
2264 configure option @option{--with-build-config=@code{NAME}...}. Some
2265 examples of supported build configurations are:
2268 @item @samp{bootstrap-O1}
2269 Removes any @option{-O}-started option from @code{BOOT_CFLAGS}, and adds
2270 @option{-O1} to it. @samp{BUILD_CONFIG=bootstrap-O1} is equivalent to
2271 @samp{BOOT_CFLAGS='-g -O1'}.
2273 @item @samp{bootstrap-O3}
2274 Analogous to @code{bootstrap-O1}.
2276 @item @samp{bootstrap-lto}
2277 Enables Link-Time Optimization for host tools during bootstrapping.
2278 @samp{BUILD_CONFIG=bootstrap-lto} is equivalent to adding
2279 @option{-flto} to @samp{BOOT_CFLAGS}.
2281 @item @samp{bootstrap-debug}
2282 Verifies that the compiler generates the same executable code, whether
2283 or not it is asked to emit debug information. To this end, this
2284 option builds stage2 host programs without debug information, and uses
2285 @file{contrib/compare-debug} to compare them with the stripped stage3
2286 object files. If @code{BOOT_CFLAGS} is overridden so as to not enable
2287 debug information, stage2 will have it, and stage3 won't. This option
2288 is enabled by default when GCC bootstrapping is enabled, if
2289 @code{strip} can turn object files compiled with and without debug
2290 info into identical object files. In addition to better test
2291 coverage, this option makes default bootstraps faster and leaner.
2293 @item @samp{bootstrap-debug-big}
2294 Rather than comparing stripped object files, as in
2295 @code{bootstrap-debug}, this option saves internal compiler dumps
2296 during stage2 and stage3 and compares them as well, which helps catch
2297 additional potential problems, but at a great cost in terms of disk
2298 space. It can be specified in addition to @samp{bootstrap-debug}.
2300 @item @samp{bootstrap-debug-lean}
2301 This option saves disk space compared with @code{bootstrap-debug-big},
2302 but at the expense of some recompilation. Instead of saving the dumps
2303 of stage2 and stage3 until the final compare, it uses
2304 @option{-fcompare-debug} to generate, compare and remove the dumps
2305 during stage3, repeating the compilation that already took place in
2306 stage2, whose dumps were not saved.
2308 @item @samp{bootstrap-debug-lib}
2309 This option tests executable code invariance over debug information
2310 generation on target libraries, just like @code{bootstrap-debug-lean}
2311 tests it on host programs. It builds stage3 libraries with
2312 @option{-fcompare-debug}, and it can be used along with any of the
2313 @code{bootstrap-debug} options above.
2315 There aren't @code{-lean} or @code{-big} counterparts to this option
2316 because most libraries are only build in stage3, so bootstrap compares
2317 would not get significant coverage. Moreover, the few libraries built
2318 in stage2 are used in stage3 host programs, so we wouldn't want to
2319 compile stage2 libraries with different options for comparison purposes.
2321 @item @samp{bootstrap-debug-ckovw}
2322 Arranges for error messages to be issued if the compiler built on any
2323 stage is run without the option @option{-fcompare-debug}. This is
2324 useful to verify the full @option{-fcompare-debug} testing coverage. It
2325 must be used along with @code{bootstrap-debug-lean} and
2326 @code{bootstrap-debug-lib}.
2328 @item @samp{bootstrap-time}
2329 Arranges for the run time of each program started by the GCC driver,
2330 built in any stage, to be logged to @file{time.log}, in the top level of
2335 @section Building a cross compiler
2337 When building a cross compiler, it is not generally possible to do a
2338 3-stage bootstrap of the compiler. This makes for an interesting problem
2339 as parts of GCC can only be built with GCC@.
2341 To build a cross compiler, we recommend first building and installing a
2342 native compiler. You can then use the native GCC compiler to build the
2343 cross compiler. The installed native compiler needs to be GCC version
2346 If the cross compiler is to be built with support for the Java
2347 programming language and the ability to compile .java source files is
2348 desired, the installed native compiler used to build the cross
2349 compiler needs to be the same GCC version as the cross compiler. In
2350 addition the cross compiler needs to be configured with
2351 @option{--with-ecj-jar=@dots{}}.
2353 Assuming you have already installed a native copy of GCC and configured
2354 your cross compiler, issue the command @command{make}, which performs the
2359 Build host tools necessary to build the compiler.
2362 Build target tools for use by the compiler such as binutils (bfd,
2363 binutils, gas, gprof, ld, and opcodes)
2364 if they have been individually linked or moved into the top level GCC source
2365 tree before configuring.
2368 Build the compiler (single stage only).
2371 Build runtime libraries using the compiler from the previous step.
2374 Note that if an error occurs in any step the make process will exit.
2376 If you are not building GNU binutils in the same source tree as GCC,
2377 you will need a cross-assembler and cross-linker installed before
2378 configuring GCC@. Put them in the directory
2379 @file{@var{prefix}/@var{target}/bin}. Here is a table of the tools
2380 you should put in this directory:
2384 This should be the cross-assembler.
2387 This should be the cross-linker.
2390 This should be the cross-archiver: a program which can manipulate
2391 archive files (linker libraries) in the target machine's format.
2394 This should be a program to construct a symbol table in an archive file.
2397 The installation of GCC will find these programs in that directory,
2398 and copy or link them to the proper place to for the cross-compiler to
2399 find them when run later.
2401 The easiest way to provide these files is to build the Binutils package.
2402 Configure it with the same @option{--host} and @option{--target}
2403 options that you use for configuring GCC, then build and install
2404 them. They install their executables automatically into the proper
2405 directory. Alas, they do not support all the targets that GCC
2408 If you are not building a C library in the same source tree as GCC,
2409 you should also provide the target libraries and headers before
2410 configuring GCC, specifying the directories with
2411 @option{--with-sysroot} or @option{--with-headers} and
2412 @option{--with-libs}. Many targets also require ``start files'' such
2413 as @file{crt0.o} and
2414 @file{crtn.o} which are linked into each executable. There may be several
2415 alternatives for @file{crt0.o}, for use with profiling or other
2416 compilation options. Check your target's definition of
2417 @code{STARTFILE_SPEC} to find out what start files it uses.
2419 @section Building in parallel
2421 GNU Make 3.80 and above, which is necessary to build GCC, support
2422 building in parallel. To activate this, you can use @samp{make -j 2}
2423 instead of @samp{make}. You can also specify a bigger number, and
2424 in most cases using a value greater than the number of processors in
2425 your machine will result in fewer and shorter I/O latency hits, thus
2426 improving overall throughput; this is especially true for slow drives
2427 and network filesystems.
2429 @section Building the Ada compiler
2431 In order to build GNAT, the Ada compiler, you need a working GNAT
2432 compiler (GCC version 4.0 or later).
2433 This includes GNAT tools such as @command{gnatmake} and
2434 @command{gnatlink}, since the Ada front end is written in Ada and
2435 uses some GNAT-specific extensions.
2437 In order to build a cross compiler, it is suggested to install
2438 the new compiler as native first, and then use it to build the cross
2441 @command{configure} does not test whether the GNAT installation works
2442 and has a sufficiently recent version; if too old a GNAT version is
2443 installed, the build will fail unless @option{--enable-languages} is
2444 used to disable building the Ada front end.
2446 @env{ADA_INCLUDE_PATH} and @env{ADA_OBJECT_PATH} environment variables
2447 must not be set when building the Ada compiler, the Ada tools, or the
2448 Ada runtime libraries. You can check that your build environment is clean
2449 by verifying that @samp{gnatls -v} lists only one explicit path in each
2452 @section Building with profile feedback
2454 It is possible to use profile feedback to optimize the compiler itself. This
2455 should result in a faster compiler binary. Experiments done on x86 using gcc
2456 3.3 showed approximately 7 percent speedup on compiling C programs. To
2457 bootstrap the compiler with profile feedback, use @code{make profiledbootstrap}.
2459 When @samp{make profiledbootstrap} is run, it will first build a @code{stage1}
2460 compiler. This compiler is used to build a @code{stageprofile} compiler
2461 instrumented to collect execution counts of instruction and branch
2462 probabilities. Then runtime libraries are compiled with profile collected.
2463 Finally a @code{stagefeedback} compiler is built using the information collected.
2465 Unlike standard bootstrap, several additional restrictions apply. The
2466 compiler used to build @code{stage1} needs to support a 64-bit integral type.
2467 It is recommended to only use GCC for this. Also parallel make is currently
2468 not supported since collisions in profile collecting may occur.
2475 @uref{./index.html,,Return to the GCC Installation page}
2479 @c ***Testing*****************************************************************
2481 @comment node-name, next, previous, up
2482 @node Testing, Final install, Building, Installing GCC
2486 @chapter Installing GCC: Testing
2489 @cindex Installing GCC: Testing
2492 Before you install GCC, we encourage you to run the testsuites and to
2493 compare your results with results from a similar configuration that have
2494 been submitted to the
2495 @uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
2496 Some of these archived results are linked from the build status lists
2497 at @uref{http://gcc.gnu.org/buildstat.html}, although not everyone who
2498 reports a successful build runs the testsuites and submits the results.
2499 This step is optional and may require you to download additional software,
2500 but it can give you confidence in your new GCC installation or point out
2501 problems before you install and start using your new GCC@.
2503 First, you must have @uref{download.html,,downloaded the testsuites}.
2504 These are part of the full distribution, but if you downloaded the
2505 ``core'' compiler plus any front ends, you must download the testsuites
2508 Second, you must have the testing tools installed. This includes
2509 @uref{http://www.gnu.org/software/dejagnu/,,DejaGnu}, Tcl, and Expect;
2510 the DejaGnu site has links to these.
2512 If the directories where @command{runtest} and @command{expect} were
2513 installed are not in the @env{PATH}, you may need to set the following
2514 environment variables appropriately, as in the following example (which
2515 assumes that DejaGnu has been installed under @file{/usr/local}):
2518 TCL_LIBRARY = /usr/local/share/tcl8.0
2519 DEJAGNULIBS = /usr/local/share/dejagnu
2522 (On systems such as Cygwin, these paths are required to be actual
2523 paths, not mounts or links; presumably this is due to some lack of
2524 portability in the DejaGnu code.)
2527 Finally, you can run the testsuite (which may take a long time):
2529 cd @var{objdir}; make -k check
2532 This will test various components of GCC, such as compiler
2533 front ends and runtime libraries. While running the testsuite, DejaGnu
2534 might emit some harmless messages resembling
2535 @samp{WARNING: Couldn't find the global config file.} or
2536 @samp{WARNING: Couldn't find tool init file} that can be ignored.
2538 If you are testing a cross-compiler, you may want to run the testsuite
2539 on a simulator as described at @uref{http://gcc.gnu.org/simtest-howto.html}.
2541 @section How can you run the testsuite on selected tests?
2543 In order to run sets of tests selectively, there are targets
2544 @samp{make check-gcc} and language specific @samp{make check-c},
2545 @samp{make check-c++}, @samp{make check-fortran}, @samp{make check-java},
2546 @samp{make check-ada}, @samp{make check-objc}, @samp{make check-obj-c++},
2547 @samp{make check-lto}
2548 in the @file{gcc} subdirectory of the object directory. You can also
2549 just run @samp{make check} in a subdirectory of the object directory.
2552 A more selective way to just run all @command{gcc} execute tests in the
2556 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
2559 Likewise, in order to run only the @command{g++} ``old-deja'' tests in
2560 the testsuite with filenames matching @samp{9805*}, you would use
2563 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
2566 The @file{*.exp} files are located in the testsuite directories of the GCC
2567 source, the most important ones being @file{compile.exp},
2568 @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
2569 To get a list of the possible @file{*.exp} files, pipe the
2570 output of @samp{make check} into a file and look at the
2571 @samp{Running @dots{} .exp} lines.
2573 @section Passing options and running multiple testsuites
2575 You can pass multiple options to the testsuite using the
2576 @samp{--target_board} option of DejaGNU, either passed as part of
2577 @samp{RUNTESTFLAGS}, or directly to @command{runtest} if you prefer to
2578 work outside the makefiles. For example,
2581 make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fmerge-constants"
2584 will run the standard @command{g++} testsuites (``unix'' is the target name
2585 for a standard native testsuite situation), passing
2586 @samp{-O3 -fmerge-constants} to the compiler on every test, i.e.,
2587 slashes separate options.
2589 You can run the testsuites multiple times using combinations of options
2590 with a syntax similar to the brace expansion of popular shells:
2593 @dots{}"--target_board=arm-sim\@{-mhard-float,-msoft-float\@}\@{-O1,-O2,-O3,\@}"
2596 (Note the empty option caused by the trailing comma in the final group.)
2597 The following will run each testsuite eight times using the @samp{arm-sim}
2598 target, as if you had specified all possible combinations yourself:
2601 --target_board='arm-sim/-mhard-float/-O1 \
2602 arm-sim/-mhard-float/-O2 \
2603 arm-sim/-mhard-float/-O3 \
2604 arm-sim/-mhard-float \
2605 arm-sim/-msoft-float/-O1 \
2606 arm-sim/-msoft-float/-O2 \
2607 arm-sim/-msoft-float/-O3 \
2608 arm-sim/-msoft-float'
2611 They can be combined as many times as you wish, in arbitrary ways. This
2615 @dots{}"--target_board=unix/-Wextra\@{-O3,-fno-strength\@}\@{-fomit-frame,\@}"
2618 will generate four combinations, all involving @samp{-Wextra}.
2620 The disadvantage to this method is that the testsuites are run in serial,
2621 which is a waste on multiprocessor systems. For users with GNU Make and
2622 a shell which performs brace expansion, you can run the testsuites in
2623 parallel by having the shell perform the combinations and @command{make}
2624 do the parallel runs. Instead of using @samp{--target_board}, use a
2625 special makefile target:
2628 make -j@var{N} check-@var{testsuite}//@var{test-target}/@var{option1}/@var{option2}/@dots{}
2634 make -j3 check-gcc//sh-hms-sim/@{-m1,-m2,-m3,-m3e,-m4@}/@{,-nofpu@}
2637 will run three concurrent ``make-gcc'' testsuites, eventually testing all
2638 ten combinations as described above. Note that this is currently only
2639 supported in the @file{gcc} subdirectory. (To see how this works, try
2640 typing @command{echo} before the example given here.)
2643 @section Additional testing for Java Class Libraries
2645 The Java runtime tests can be executed via @samp{make check}
2646 in the @file{@var{target}/libjava/testsuite} directory in
2649 The @uref{http://sourceware.org/mauve/,,Mauve Project} provides
2650 a suite of tests for the Java Class Libraries. This suite can be run
2651 as part of libgcj testing by placing the Mauve tree within the libjava
2652 testsuite at @file{libjava/testsuite/libjava.mauve/mauve}, or by
2653 specifying the location of that tree when invoking @samp{make}, as in
2654 @samp{make MAUVEDIR=~/mauve check}.
2656 @section How to interpret test results
2658 The result of running the testsuite are various @file{*.sum} and @file{*.log}
2659 files in the testsuite subdirectories. The @file{*.log} files contain a
2660 detailed log of the compiler invocations and the corresponding
2661 results, the @file{*.sum} files summarize the results. These summaries
2662 contain status codes for all tests:
2666 PASS: the test passed as expected
2668 XPASS: the test unexpectedly passed
2670 FAIL: the test unexpectedly failed
2672 XFAIL: the test failed as expected
2674 UNSUPPORTED: the test is not supported on this platform
2676 ERROR: the testsuite detected an error
2678 WARNING: the testsuite detected a possible problem
2681 It is normal for some tests to report unexpected failures. At the
2682 current time the testing harness does not allow fine grained control
2683 over whether or not a test is expected to fail. This problem should
2684 be fixed in future releases.
2687 @section Submitting test results
2689 If you want to report the results to the GCC project, use the
2690 @file{contrib/test_summary} shell script. Start it in the @var{objdir} with
2693 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
2694 -m gcc-testresults@@gcc.gnu.org |sh
2697 This script uses the @command{Mail} program to send the results, so
2698 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
2699 prepended to the testsuite summary and should contain any special
2700 remarks you have on your results or your build environment. Please
2701 do not edit the testsuite result block or the subject line, as these
2702 messages may be automatically processed.
2709 @uref{./index.html,,Return to the GCC Installation page}
2713 @c ***Final install***********************************************************
2715 @comment node-name, next, previous, up
2716 @node Final install, , Testing, Installing GCC
2718 @ifset finalinstallhtml
2720 @chapter Installing GCC: Final installation
2723 Now that GCC has been built (and optionally tested), you can install it with
2725 cd @var{objdir} && make install
2728 We strongly recommend to install into a target directory where there is
2729 no previous version of GCC present. Also, the GNAT runtime should not
2730 be stripped, as this would break certain features of the debugger that
2731 depend on this debugging information (catching Ada exceptions for
2734 That step completes the installation of GCC; user level binaries can
2735 be found in @file{@var{prefix}/bin} where @var{prefix} is the value
2736 you specified with the @option{--prefix} to configure (or
2737 @file{/usr/local} by default). (If you specified @option{--bindir},
2738 that directory will be used instead; otherwise, if you specified
2739 @option{--exec-prefix}, @file{@var{exec-prefix}/bin} will be used.)
2740 Headers for the C++ and Java libraries are installed in
2741 @file{@var{prefix}/include}; libraries in @file{@var{libdir}}
2742 (normally @file{@var{prefix}/lib}); internal parts of the compiler in
2743 @file{@var{libdir}/gcc} and @file{@var{libexecdir}/gcc}; documentation
2744 in info format in @file{@var{infodir}} (normally
2745 @file{@var{prefix}/info}).
2747 When installing cross-compilers, GCC's executables
2748 are not only installed into @file{@var{bindir}}, that
2749 is, @file{@var{exec-prefix}/bin}, but additionally into
2750 @file{@var{exec-prefix}/@var{target-alias}/bin}, if that directory
2751 exists. Typically, such @dfn{tooldirs} hold target-specific
2752 binutils, including assembler and linker.
2754 Installation into a temporary staging area or into a @command{chroot}
2755 jail can be achieved with the command
2758 make DESTDIR=@var{path-to-rootdir} install
2762 where @var{path-to-rootdir} is the absolute path of
2763 a directory relative to which all installation paths will be
2764 interpreted. Note that the directory specified by @code{DESTDIR}
2765 need not exist yet; it will be created if necessary.
2767 There is a subtle point with tooldirs and @code{DESTDIR}:
2768 If you relocate a cross-compiler installation with
2769 e.g.@: @samp{DESTDIR=@var{rootdir}}, then the directory
2770 @file{@var{rootdir}/@var{exec-prefix}/@var{target-alias}/bin} will
2771 be filled with duplicated GCC executables only if it already exists,
2772 it will not be created otherwise. This is regarded as a feature,
2773 not as a bug, because it gives slightly more control to the packagers
2774 using the @code{DESTDIR} feature.
2776 You can install stripped programs and libraries with
2782 If you are bootstrapping a released version of GCC then please
2783 quickly review the build status page for your release, available from
2784 @uref{http://gcc.gnu.org/buildstat.html}.
2785 If your system is not listed for the version of GCC that you built,
2787 @email{gcc@@gcc.gnu.org} indicating
2788 that you successfully built and installed GCC@.
2789 Include the following information:
2793 Output from running @file{@var{srcdir}/config.guess}. Do not send
2794 that file itself, just the one-line output from running it.
2797 The output of @samp{gcc -v} for your newly installed @command{gcc}.
2798 This tells us which version of GCC you built and the options you passed to
2802 Whether you enabled all languages or a subset of them. If you used a
2803 full distribution then this information is part of the configure
2804 options in the output of @samp{gcc -v}, but if you downloaded the
2805 ``core'' compiler plus additional front ends then it isn't apparent
2806 which ones you built unless you tell us about it.
2809 If the build was for GNU/Linux, also include:
2812 The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
2813 this information should be available from @file{/etc/issue}.
2816 The version of the Linux kernel, available from @samp{uname --version}
2820 The version of glibc you used; for RPM-based systems like Red Hat,
2821 Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
2822 and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
2824 For other systems, you can include similar information if you think it is
2828 Any other information that you think would be useful to people building
2829 GCC on the same configuration. The new entry in the build status list
2830 will include a link to the archived copy of your message.
2833 We'd also like to know if the
2835 @ref{Specific, host/target specific installation notes}
2838 @uref{specific.html,,host/target specific installation notes}
2840 didn't include your host/target information or if that information is
2841 incomplete or out of date. Send a note to
2842 @email{gcc@@gcc.gnu.org} detailing how the information should be changed.
2844 If you find a bug, please report it following the
2845 @uref{../bugs/,,bug reporting guidelines}.
2847 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
2848 dvi}. You will need to have @command{texi2dvi} (version at least 4.7)
2849 and @TeX{} installed. This creates a number of @file{.dvi} files in
2850 subdirectories of @file{@var{objdir}}; these may be converted for
2851 printing with programs such as @command{dvips}. Alternately, by using
2852 @samp{make pdf} in place of @samp{make dvi}, you can create documentation
2853 in the form of @file{.pdf} files; this requires @command{texi2pdf}, which
2854 is included with Texinfo version 4.8 and later. You can also
2855 @uref{http://shop.fsf.org/,,buy printed manuals from the
2856 Free Software Foundation}, though such manuals may not be for the most
2857 recent version of GCC@.
2859 If you would like to generate online HTML documentation, do @samp{cd
2860 @var{objdir}; make html} and HTML will be generated for the gcc manuals in
2861 @file{@var{objdir}/gcc/HTML}.
2868 @uref{./index.html,,Return to the GCC Installation page}
2872 @c ***Binaries****************************************************************
2874 @comment node-name, next, previous, up
2875 @node Binaries, Specific, Installing GCC, Top
2879 @chapter Installing GCC: Binaries
2882 @cindex Installing GCC: Binaries
2884 We are often asked about pre-compiled versions of GCC@. While we cannot
2885 provide these for all platforms, below you'll find links to binaries for
2886 various platforms where creating them by yourself is not easy due to various
2889 Please note that we did not create these binaries, nor do we
2890 support them. If you have any problems installing them, please
2891 contact their makers.
2898 @uref{http://www.bullfreeware.com,,Bull's Freeware and Shareware Archive for AIX};
2901 @uref{http://pware.hvcc.edu,,Hudson Valley Community College Open Source Software for IBM System p};
2904 @uref{http://www.perzl.org/aix/,,AIX 5L and 6 Open Source Packages}.
2908 DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}.
2911 Renesas H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
2912 Development Tools for the Renesas H8/300[HS] Series}.
2918 @uref{http://hpux.connect.org.uk/,,HP-UX Porting Center};
2921 @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}.
2925 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
2926 OpenServer/Unixware}.
2929 Solaris 2 (SPARC, Intel):
2932 @uref{http://www.sunfreeware.com/,,Sunfreeware}
2935 @uref{http://www.blastwave.org/,,Blastwave}
2938 @uref{http://www.opencsw.org/,,OpenCSW}
2941 @uref{http://jupiterrise.com/tgcware/,,TGCware}
2948 The @uref{http://sourceware.org/cygwin/,,Cygwin} project;
2950 The @uref{http://www.mingw.org/,,MinGW} project.
2954 @uref{ftp://ftp.thewrittenword.com/packages/by-name/,,The
2955 Written Word} offers binaries for
2956 AIX 4.3.3, 5.1 and 5.2,
2958 HP-UX 10.20, 11.00, and 11.11, and
2959 Solaris/SPARC 2.5.1, 2.6, 7, 8, 9 and 10.
2962 @uref{http://www.openpkg.org/,,OpenPKG} offers binaries for quite a
2963 number of platforms.
2966 The @uref{http://gcc.gnu.org/wiki/GFortranBinaries,,GFortran Wiki} has
2967 links to GNU Fortran binaries for several platforms.
2975 @uref{./index.html,,Return to the GCC Installation page}
2979 @c ***Specific****************************************************************
2981 @comment node-name, next, previous, up
2982 @node Specific, Old, Binaries, Top
2986 @chapter Host/target specific installation notes for GCC
2989 @cindex Specific installation notes
2990 @cindex Target specific installation
2991 @cindex Host specific installation
2992 @cindex Target specific installation notes
2994 Please read this document carefully @emph{before} installing the
2995 GNU Compiler Collection on your machine.
2997 Note that this list of install notes is @emph{not} a list of supported
2998 hosts or targets. Not all supported hosts and targets are listed
2999 here, only the ones that require host-specific or target-specific
3000 information have to.
3005 @uref{#alpha-x-x,,alpha*-*-*}
3007 @uref{#alpha-dec-osf51,,alpha*-dec-osf5.1}
3009 @uref{#amd64-x-solaris210,,amd64-*-solaris2.10}
3011 @uref{#arm-x-eabi,,arm-*-eabi}
3015 @uref{#bfin,,Blackfin}
3019 @uref{#x-x-freebsd,,*-*-freebsd*}
3021 @uref{#h8300-hms,,h8300-hms}
3023 @uref{#hppa-hp-hpux,,hppa*-hp-hpux*}
3025 @uref{#hppa-hp-hpux10,,hppa*-hp-hpux10}
3027 @uref{#hppa-hp-hpux11,,hppa*-hp-hpux11}
3029 @uref{#x-x-linux-gnu,,*-*-linux-gnu}
3031 @uref{#ix86-x-linux,,i?86-*-linux*}
3033 @uref{#ix86-x-solaris289,,i?86-*-solaris2.9}
3035 @uref{#ix86-x-solaris210,,i?86-*-solaris2.10}
3037 @uref{#ia64-x-linux,,ia64-*-linux}
3039 @uref{#ia64-x-hpux,,ia64-*-hpux*}
3041 @uref{#x-ibm-aix,,*-ibm-aix*}
3043 @uref{#iq2000-x-elf,,iq2000-*-elf}
3045 @uref{#lm32-x-elf,,lm32-*-elf}
3047 @uref{#lm32-x-uclinux,,lm32-*-uclinux}
3049 @uref{#m32c-x-elf,,m32c-*-elf}
3051 @uref{#m32r-x-elf,,m32r-*-elf}
3053 @uref{#m68k-x-x,,m68k-*-*}
3055 @uref{#m68k-uclinux,,m68k-uclinux}
3057 @uref{#mep-x-elf,,mep-*-elf}
3059 @uref{#microblaze-x-elf,,microblaze-*-elf}
3061 @uref{#mips-x-x,,mips-*-*}
3063 @uref{#mips-sgi-irix5,,mips-sgi-irix5}
3065 @uref{#mips-sgi-irix6,,mips-sgi-irix6}
3067 @uref{#powerpc-x-x,,powerpc*-*-*}
3069 @uref{#powerpc-x-darwin,,powerpc-*-darwin*}
3071 @uref{#powerpc-x-elf,,powerpc-*-elf}
3073 @uref{#powerpc-x-linux-gnu,,powerpc*-*-linux-gnu*}
3075 @uref{#powerpc-x-netbsd,,powerpc-*-netbsd*}
3077 @uref{#powerpc-x-eabisim,,powerpc-*-eabisim}
3079 @uref{#powerpc-x-eabi,,powerpc-*-eabi}
3081 @uref{#powerpcle-x-elf,,powerpcle-*-elf}
3083 @uref{#powerpcle-x-eabisim,,powerpcle-*-eabisim}
3085 @uref{#powerpcle-x-eabi,,powerpcle-*-eabi}
3087 @uref{#s390-x-linux,,s390-*-linux*}
3089 @uref{#s390x-x-linux,,s390x-*-linux*}
3091 @uref{#s390x-ibm-tpf,,s390x-ibm-tpf*}
3093 @uref{#x-x-solaris2,,*-*-solaris2*}
3095 @uref{#sparc-x-x,,sparc*-*-*}
3097 @uref{#sparc-sun-solaris2,,sparc-sun-solaris2*}
3099 @uref{#sparc-sun-solaris210,,sparc-sun-solaris2.10}
3101 @uref{#sparc-x-linux,,sparc-*-linux*}
3103 @uref{#sparc64-x-solaris2,,sparc64-*-solaris2*}
3105 @uref{#sparcv9-x-solaris2,,sparcv9-*-solaris2*}
3107 @uref{#c6x-x-x,,c6x-*-*}
3109 @uref{#tilegx-x-linux,,tilegx-*-linux*}
3111 @uref{#tilepro-x-linux,,tilepro-*-linux*}
3113 @uref{#x-x-vxworks,,*-*-vxworks*}
3115 @uref{#x86-64-x-x,,x86_64-*-*, amd64-*-*}
3117 @uref{#x86-64-x-solaris210,,x86_64-*-solaris2.1[0-9]*}
3119 @uref{#xtensa-x-elf,,xtensa*-*-elf}
3121 @uref{#xtensa-x-linux,,xtensa*-*-linux*}
3123 @uref{#windows,,Microsoft Windows}
3125 @uref{#x-x-cygwin,,*-*-cygwin}
3127 @uref{#x-x-interix,,*-*-interix}
3129 @uref{#x-x-mingw32,,*-*-mingw32}
3133 @uref{#older,,Older systems}
3138 @uref{#elf,,all ELF targets} (SVR4, Solaris 2, etc.)
3144 <!-- -------- host/target specific issues start here ---------------- -->
3147 @heading @anchor{alpha-x-x}alpha*-*-*
3149 This section contains general configuration information for all
3150 alpha-based platforms using ELF (in particular, ignore this section for
3151 DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
3152 section, please read all other sections that match your target.
3154 We require binutils 2.11.2 or newer.
3155 Previous binutils releases had a number of problems with DWARF 2
3156 debugging information, not the least of which is incorrect linking of
3162 @heading @anchor{alpha-dec-osf51}alpha*-dec-osf5.1
3163 Systems using processors that implement the DEC Alpha architecture and
3164 are running the DEC/Compaq/HP Unix (DEC OSF/1, Digital UNIX, or Compaq/HP
3165 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
3167 Support for Tru64 UNIX V5.1 has been removed in GCC 4.8. As of GCC 4.6,
3168 support for Tru64 UNIX V4.0 and V5.0 has been removed. As of GCC 3.2,
3169 versions before @code{alpha*-dec-osf4} are no longer supported. (These
3170 are the versions which identify themselves as DEC OSF/1.)
3175 @heading @anchor{amd64-x-solaris210}amd64-*-solaris2.1[0-9]*
3177 This is a synonym for @samp{x86_64-*-solaris2.1[0-9]*}.
3182 @heading @anchor{arm-x-eabi}arm-*-eabi
3183 ARM-family processors. Subtargets that use the ELF object format
3184 require GNU binutils 2.13 or newer. Such subtargets include:
3185 @code{arm-*-netbsdelf}, @code{arm-*-*linux-*}
3186 and @code{arm-*-rtemseabi}.
3191 @heading @anchor{avr}avr
3193 ATMEL AVR-family micro controllers. These are used in embedded
3194 applications. There are no standard Unix configurations.
3196 @xref{AVR Options,, AVR Options, gcc, Using the GNU Compiler
3200 See ``AVR Options'' in the main manual
3202 for the list of supported MCU types.
3204 Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
3206 Further installation notes and other useful information about AVR tools
3207 can also be obtained from:
3211 @uref{http://www.nongnu.org/avr/,,http://www.nongnu.org/avr/}
3213 @uref{http://www.amelek.gda.pl/avr/,,http://www.amelek.gda.pl/avr/}
3216 We @emph{strongly} recommend using binutils 2.13 or newer.
3218 The following error:
3220 Error: register required
3223 indicates that you should upgrade to a newer version of the binutils.
3228 @heading @anchor{bfin}Blackfin
3230 The Blackfin processor, an Analog Devices DSP.
3232 @xref{Blackfin Options,, Blackfin Options, gcc, Using the GNU Compiler
3236 See ``Blackfin Options'' in the main manual
3239 More information, and a version of binutils with support for this processor,
3240 is available at @uref{http://blackfin.uclinux.org}
3245 @heading @anchor{cr16}CR16
3247 The CR16 CompactRISC architecture is a 16-bit architecture. This architecture is
3248 used in embedded applications.
3251 @xref{CR16 Options,, CR16 Options, gcc, Using and Porting the GNU Compiler
3256 See ``CR16 Options'' in the main manual for a list of CR16-specific options.
3259 Use @samp{configure --target=cr16-elf --enable-languages=c,c++} to configure
3260 GCC@ for building a CR16 elf cross-compiler.
3262 Use @samp{configure --target=cr16-uclinux --enable-languages=c,c++} to configure
3263 GCC@ for building a CR16 uclinux cross-compiler.
3268 @heading @anchor{cris}CRIS
3270 CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
3271 series. These are used in embedded applications.
3274 @xref{CRIS Options,, CRIS Options, gcc, Using the GNU Compiler
3278 See ``CRIS Options'' in the main manual
3280 for a list of CRIS-specific options.
3282 There are a few different CRIS targets:
3285 Mainly for monolithic embedded systems. Includes a multilib for the
3286 @samp{v10} core used in @samp{ETRAX 100 LX}.
3287 @item cris-axis-linux-gnu
3288 A GNU/Linux port for the CRIS architecture, currently targeting
3289 @samp{ETRAX 100 LX} by default.
3292 For @code{cris-axis-elf} you need binutils 2.11
3293 or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer.
3295 Pre-packaged tools can be obtained from
3296 @uref{ftp://ftp.axis.com/@/pub/@/axis/@/tools/@/cris/@/compiler-kit/}. More
3297 information about this platform is available at
3298 @uref{http://developer.axis.com/}.
3303 @heading @anchor{dos}DOS
3305 Please have a look at the @uref{binaries.html,,binaries page}.
3307 You cannot install GCC by itself on MSDOS; it will not compile under
3308 any MSDOS compiler except itself. You need to get the complete
3309 compilation package DJGPP, which includes binaries as well as sources,
3310 and includes all the necessary compilation tools and libraries.
3315 @heading @anchor{epiphany-x-elf}epiphany-*-elf
3317 This configuration is intended for embedded systems.
3322 @heading @anchor{x-x-freebsd}*-*-freebsd*
3324 Support for FreeBSD 1 was discontinued in GCC 3.2. Support for
3325 FreeBSD 2 (and any mutant a.out variants of FreeBSD 3) was
3326 discontinued in GCC 4.0.
3328 In order to better utilize FreeBSD base system functionality and match
3329 the configuration of the system compiler, GCC 4.5 and above as well as
3330 GCC 4.4 past 2010-06-20 leverage SSP support in libc (which is present
3331 on FreeBSD 7 or later) and the use of @code{__cxa_atexit} by default
3332 (on FreeBSD 6 or later). The use of @code{dl_iterate_phdr} inside
3333 @file{libgcc_s.so.1} and boehm-gc (on FreeBSD 7 or later) is enabled
3334 by GCC 4.5 and above.
3336 We support FreeBSD using the ELF file format with DWARF 2 debugging
3337 for all CPU architectures. You may use @option{-gstabs} instead of
3338 @option{-g}, if you really want the old debugging format. There are
3339 no known issues with mixing object files and libraries with different
3340 debugging formats. Otherwise, this release of GCC should now match
3341 more of the configuration used in the stock FreeBSD configuration of
3342 GCC@. In particular, @option{--enable-threads} is now configured by
3343 default. However, as a general user, do not attempt to replace the
3344 system compiler with this release. Known to bootstrap and check with
3345 good results on FreeBSD 7.2-STABLE@. In the past, known to bootstrap
3346 and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4,
3347 4.5, 4.8, 4.9 and 5-CURRENT@.
3349 The version of binutils installed in @file{/usr/bin} probably works
3350 with this release of GCC@. Bootstrapping against the latest GNU
3351 binutils and/or the version found in @file{/usr/ports/devel/binutils} has
3352 been known to enable additional features and improve overall testsuite
3353 results. However, it is currently known that boehm-gc (which itself
3354 is required for java) may not configure properly on FreeBSD prior to
3355 the FreeBSD 7.0 release with GNU binutils after 2.16.1.
3360 @heading @anchor{h8300-hms}h8300-hms
3361 Renesas H8/300 series of processors.
3363 Please have a look at the @uref{binaries.html,,binaries page}.
3365 The calling convention and structure layout has changed in release 2.6.
3366 All code must be recompiled. The calling convention now passes the
3367 first three arguments in function calls in registers. Structures are no
3368 longer a multiple of 2 bytes.
3373 @heading @anchor{hppa-hp-hpux}hppa*-hp-hpux*
3374 Support for HP-UX version 9 and older was discontinued in GCC 3.4.
3376 We require using gas/binutils on all hppa platforms. Version 2.19 or
3377 later is recommended.
3379 It may be helpful to configure GCC with the
3380 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
3381 @option{--with-as=@dots{}} options to ensure that GCC can find GAS@.
3383 The HP assembler should not be used with GCC. It is rarely tested and may
3384 not work. It shouldn't be used with any languages other than C due to its
3387 Specifically, @option{-g} does not work (HP-UX uses a peculiar debugging
3388 format which GCC does not know about). It also inserts timestamps
3389 into each object file it creates, causing the 3-stage comparison test to
3390 fail during a bootstrap. You should be able to continue by saying
3391 @samp{make all-host all-target} after getting the failure from @samp{make}.
3393 Various GCC features are not supported. For example, it does not support weak
3394 symbols or alias definitions. As a result, explicit template instantiations
3395 are required when using C++. This makes it difficult if not impossible to
3396 build many C++ applications.
3398 There are two default scheduling models for instructions. These are
3399 PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
3400 architecture specified for the target machine when configuring.
3401 PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
3402 the target is a @samp{hppa1*} machine.
3404 The PROCESSOR_8000 model is not well suited to older processors. Thus,
3405 it is important to completely specify the machine architecture when
3406 configuring if you want a model other than PROCESSOR_8000. The macro
3407 TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
3408 default scheduling model is desired.
3410 As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10
3411 through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later.
3412 This namespace change might cause problems when bootstrapping with
3413 an earlier version of GCC or the HP compiler as essentially the same
3414 namespace is required for an entire build. This problem can be avoided
3415 in a number of ways. With HP cc, @env{UNIX_STD} can be set to @samp{95}
3416 or @samp{98}. Another way is to add an appropriate set of predefines
3417 to @env{CC}. The description for the @option{munix=} option contains
3418 a list of the predefines used with each standard.
3420 More specific information to @samp{hppa*-hp-hpux*} targets follows.
3425 @heading @anchor{hppa-hp-hpux10}hppa*-hp-hpux10
3427 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
3428 @code{PHCO_19798} from HP@.
3430 The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces are
3431 used for one-only code and data. This resolves many of the previous
3432 problems in using C++ on this target. However, the ABI is not compatible
3433 with the one implemented under HP-UX 11 using secondary definitions.
3438 @heading @anchor{hppa-hp-hpux11}hppa*-hp-hpux11
3440 GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot
3441 be used to compile GCC 3.0 and up.
3443 The libffi and libjava libraries haven't been ported to 64-bit HP-UX@
3446 Refer to @uref{binaries.html,,binaries} for information about obtaining
3447 precompiled GCC binaries for HP-UX@. Precompiled binaries must be obtained
3448 to build the Ada language as it can't be bootstrapped using C@. Ada is
3449 only available for the 32-bit PA-RISC runtime.
3451 Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The
3452 bundled compiler supports only traditional C; you will need either HP's
3453 unbundled compiler, or a binary distribution of GCC@.
3455 It is possible to build GCC 3.3 starting with the bundled HP compiler,
3456 but the process requires several steps. GCC 3.3 can then be used to
3457 build later versions. The fastjar program contains ISO C code and
3458 can't be built with the HP bundled compiler. This problem can be
3459 avoided by not building the Java language. For example, use the
3460 @option{--enable-languages="c,c++,f77,objc"} option in your configure
3463 There are several possible approaches to building the distribution.
3464 Binutils can be built first using the HP tools. Then, the GCC
3465 distribution can be built. The second approach is to build GCC
3466 first using the HP tools, then build binutils, then rebuild GCC@.
3467 There have been problems with various binary distributions, so it
3468 is best not to start from a binary distribution.
3470 On 64-bit capable systems, there are two distinct targets. Different
3471 installation prefixes must be used if both are to be installed on
3472 the same system. The @samp{hppa[1-2]*-hp-hpux11*} target generates code
3473 for the 32-bit PA-RISC runtime architecture and uses the HP linker.
3474 The @samp{hppa64-hp-hpux11*} target generates 64-bit code for the
3475 PA-RISC 2.0 architecture.
3477 The script config.guess now selects the target type based on the compiler
3478 detected during configuration. You must define @env{PATH} or @env{CC} so
3479 that configure finds an appropriate compiler for the initial bootstrap.
3480 When @env{CC} is used, the definition should contain the options that are
3481 needed whenever @env{CC} is used.
3483 Specifically, options that determine the runtime architecture must be
3484 in @env{CC} to correctly select the target for the build. It is also
3485 convenient to place many other compiler options in @env{CC}. For example,
3486 @env{CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"}
3487 can be used to bootstrap the GCC 3.3 branch with the HP compiler in
3488 64-bit K&R/bundled mode. The @option{+DA2.0W} option will result in
3489 the automatic selection of the @samp{hppa64-hp-hpux11*} target. The
3490 macro definition table of cpp needs to be increased for a successful
3491 build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to
3492 be defined when building with the bundled compiler, or when using the
3493 @option{-Ac} option. These defines aren't necessary with @option{-Ae}.
3495 It is best to explicitly configure the @samp{hppa64-hp-hpux11*} target
3496 with the @option{--with-ld=@dots{}} option. This overrides the standard
3497 search for ld. The two linkers supported on this target require different
3498 commands. The default linker is determined during configuration. As a
3499 result, it's not possible to switch linkers in the middle of a GCC build.
3500 This has been reported to sometimes occur in unified builds of binutils
3503 A recent linker patch must be installed for the correct operation of
3504 GCC 3.3 and later. @code{PHSS_26559} and @code{PHSS_24304} are the
3505 oldest linker patches that are known to work. They are for HP-UX
3506 11.00 and 11.11, respectively. @code{PHSS_24303}, the companion to
3507 @code{PHSS_24304}, might be usable but it hasn't been tested. These
3508 patches have been superseded. Consult the HP patch database to obtain
3509 the currently recommended linker patch for your system.
3511 The patches are necessary for the support of weak symbols on the
3512 32-bit port, and for the running of initializers and finalizers. Weak
3513 symbols are implemented using SOM secondary definition symbols. Prior
3514 to HP-UX 11, there are bugs in the linker support for secondary symbols.
3515 The patches correct a problem of linker core dumps creating shared
3516 libraries containing secondary symbols, as well as various other
3517 linking issues involving secondary symbols.
3519 GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
3520 run initializers and finalizers on the 64-bit port. The 32-bit port
3521 uses the linker @option{+init} and @option{+fini} options for the same
3522 purpose. The patches correct various problems with the +init/+fini
3523 options, including program core dumps. Binutils 2.14 corrects a
3524 problem on the 64-bit port resulting from HP's non-standard use of
3525 the .init and .fini sections for array initializers and finalizers.
3527 Although the HP and GNU linkers are both supported for the
3528 @samp{hppa64-hp-hpux11*} target, it is strongly recommended that the
3529 HP linker be used for link editing on this target.
3531 At this time, the GNU linker does not support the creation of long
3532 branch stubs. As a result, it can't successfully link binaries
3533 containing branch offsets larger than 8 megabytes. In addition,
3534 there are problems linking shared libraries, linking executables
3535 with @option{-static}, and with dwarf2 unwind and exception support.
3536 It also doesn't provide stubs for internal calls to global functions
3537 in shared libraries, so these calls can't be overloaded.
3539 The HP dynamic loader does not support GNU symbol versioning, so symbol
3540 versioning is not supported. It may be necessary to disable symbol
3541 versioning with @option{--disable-symvers} when using GNU ld.
3543 POSIX threads are the default. The optional DCE thread library is not
3544 supported, so @option{--enable-threads=dce} does not work.
3549 @heading @anchor{x-x-linux-gnu}*-*-linux-gnu
3551 Versions of libstdc++-v3 starting with 3.2.1 require bug fixes present
3552 in glibc 2.2.5 and later. More information is available in the
3553 libstdc++-v3 documentation.
3558 @heading @anchor{ix86-x-linux}i?86-*-linux*
3560 As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
3561 See @uref{http://gcc.gnu.org/PR10877,,bug 10877} for more information.
3563 If you receive Signal 11 errors when building on GNU/Linux, then it is
3564 possible you have a hardware problem. Further information on this can be
3565 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
3570 @heading @anchor{ix86-x-solaris29}i?86-*-solaris2.9
3571 The Sun assembler in Solaris 9 has several bugs and limitations.
3572 While GCC works around them, several features are missing, so it is
3573 @c FIXME: which ones?
3574 recommended to use the GNU assembler instead. There is no bundled
3575 version, but the current version, from GNU binutils 2.22, is known to
3578 Solaris@tie{}2/x86 doesn't support the execution of SSE/SSE2 instructions
3579 before Solaris@tie{}9 4/04, even if the CPU supports them. Programs will
3580 receive @code{SIGILL} if they try. The fix is available both in
3581 Solaris@tie{}9 Update@tie{}6 and kernel patch 112234-12 or newer. To
3583 @option{-march} defaults to @samp{pentiumpro} on Solaris 9. If
3584 you have the patch installed, you can configure GCC with an appropriate
3585 @option{--with-arch} option, but need GNU @command{as} for SSE2 support.
3590 @heading @anchor{ix86-x-solaris210}i?86-*-solaris2.10
3591 Use this for Solaris 10 or later on x86 and x86-64 systems. Starting
3592 with GCC 4.7, there is also a 64-bit @samp{amd64-*-solaris2.1[0-9]*} or
3593 @samp{x86_64-*-solaris2.1[0-9]*} configuration that corresponds to
3594 @samp{sparcv9-sun-solaris2*}.
3596 It is recommended that you configure GCC to use the GNU assembler, in
3597 @file{/usr/sfw/bin/gas}. The versions included in Solaris 10, from GNU
3598 binutils 2.15, and Solaris 11, from GNU binutils 2.19, work fine,
3599 although the current version, from GNU binutils
3600 2.22, is known to work, too. Recent versions of the Sun assembler in
3601 @file{/usr/ccs/bin/as} work almost as well, though.
3602 @c FIXME: as patch requirements?
3604 For linking, the Sun linker, is preferred. If you want to use the GNU
3605 linker instead, which is available in @file{/usr/sfw/bin/gld}, note that
3606 due to a packaging bug the version in Solaris 10, from GNU binutils
3607 2.15, cannot be used, while the version in Solaris 11, from GNU binutils
3608 2.19, works, as does the latest version, from GNU binutils 2.22.
3610 To use GNU @command{as}, configure with the options
3611 @option{--with-gnu-as --with-as=@//usr/@/sfw/@/bin/@/gas}. It may be necessary
3612 to configure with @option{--without-gnu-ld --with-ld=@//usr/@/ccs/@/bin/@/ld} to
3613 guarantee use of Sun @command{ld}.
3614 @c FIXME: why --without-gnu-ld --with-ld?
3619 @heading @anchor{ia64-x-linux}ia64-*-linux
3620 IA-64 processor (also known as IPF, or Itanium Processor Family)
3623 If you are using the installed system libunwind library with
3624 @option{--with-system-libunwind}, then you must use libunwind 0.98 or
3627 None of the following versions of GCC has an ABI that is compatible
3628 with any of the other versions in this list, with the exception that
3629 Red Hat 2.96 and Trillian 000171 are compatible with each other:
3630 3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
3631 This primarily affects C++ programs and programs that create shared libraries.
3632 GCC 3.1 or later is recommended for compiling linux, the kernel.
3633 As of version 3.1 GCC is believed to be fully ABI compliant, and hence no
3634 more major ABI changes are expected.
3639 @heading @anchor{ia64-x-hpux}ia64-*-hpux*
3640 Building GCC on this target requires the GNU Assembler. The bundled HP
3641 assembler will not work. To prevent GCC from using the wrong assembler,
3642 the option @option{--with-gnu-as} may be necessary.
3644 The GCC libunwind library has not been ported to HPUX@. This means that for
3645 GCC versions 3.2.3 and earlier, @option{--enable-libunwind-exceptions}
3646 is required to build GCC@. For GCC 3.3 and later, this is the default.
3647 For gcc 3.4.3 and later, @option{--enable-libunwind-exceptions} is
3648 removed and the system libunwind library will always be used.
3652 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
3654 @heading @anchor{x-ibm-aix}*-ibm-aix*
3655 Support for AIX version 3 and older was discontinued in GCC 3.4.
3656 Support for AIX version 4.2 and older was discontinued in GCC 4.5.
3658 ``out of memory'' bootstrap failures may indicate a problem with
3659 process resource limits (ulimit). Hard limits are configured in the
3660 @file{/etc/security/limits} system configuration file.
3662 GCC can bootstrap with recent versions of IBM XLC, but bootstrapping
3663 with an earlier release of GCC is recommended. Bootstrapping with XLC
3664 requires a larger data segment, which can be enabled through the
3665 @var{LDR_CNTRL} environment variable, e.g.,
3668 % LDR_CNTRL=MAXDATA=0x50000000
3672 One can start with a pre-compiled version of GCC to build from
3673 sources. One may delete GCC's ``fixed'' header files when starting
3674 with a version of GCC built for an earlier release of AIX.
3676 To speed up the configuration phases of bootstrapping and installing GCC,
3677 one may use GNU Bash instead of AIX @command{/bin/sh}, e.g.,
3680 % CONFIG_SHELL=/opt/freeware/bin/bash
3681 % export CONFIG_SHELL
3684 and then proceed as described in @uref{build.html,,the build
3685 instructions}, where we strongly recommend specifying an absolute path
3686 to invoke @var{srcdir}/configure.
3688 Because GCC on AIX is built as a 32-bit executable by default,
3689 (although it can generate 64-bit programs) the GMP and MPFR libraries
3690 required by gfortran must be 32-bit libraries. Building GMP and MPFR
3691 as static archive libraries works better than shared libraries.
3693 Errors involving @code{alloca} when building GCC generally are due
3694 to an incorrect definition of @code{CC} in the Makefile or mixing files
3695 compiled with the native C compiler and GCC@. During the stage1 phase of
3696 the build, the native AIX compiler @strong{must} be invoked as @command{cc}
3697 (not @command{xlc}). Once @command{configure} has been informed of
3698 @command{xlc}, one needs to use @samp{make distclean} to remove the
3699 configure cache files and ensure that @env{CC} environment variable
3700 does not provide a definition that will confuse @command{configure}.
3701 If this error occurs during stage2 or later, then the problem most likely
3702 is the version of Make (see above).
3704 The native @command{as} and @command{ld} are recommended for
3705 bootstrapping on AIX@. The GNU Assembler, GNU Linker, and GNU
3706 Binutils version 2.20 is the minimum level that supports bootstrap on
3707 AIX 5@. The GNU Assembler has not been updated to support AIX 6@ or
3708 AIX 7. The native AIX tools do interoperate with GCC@.
3710 AIX 5.3 TL10, AIX 6.1 TL05 and AIX 7.1 TL00 introduced an AIX
3711 assembler change that sometimes produces corrupt assembly files
3712 causing AIX linker errors. The bug breaks GCC bootstrap on AIX and
3713 can cause compilation failures with existing GCC installations. An
3714 AIX iFix for AIX 5.3 is available (APAR IZ98385 for AIX 5.3 TL10, APAR
3715 IZ98477 for AIX 5.3 TL11 and IZ98134 for AIX 5.3 TL12). AIX 5.3 TL11 SP8,
3716 AIX 5.3 TL12 SP5, AIX 6.1 TL04 SP11, AIX 6.1 TL05 SP7, AIX 6.1 TL06 SP6,
3717 AIX 6.1 TL07 and AIX 7.1 TL01 should include the fix.
3719 Building @file{libstdc++.a} requires a fix for an AIX Assembler bug
3720 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a
3721 fix for another AIX Assembler bug and a co-dependent AIX Archiver fix
3722 referenced as APAR IY53606 (AIX 5.2) or as APAR IY54774 (AIX 5.1)
3724 @samp{libstdc++} in GCC 3.4 increments the major version number of the
3725 shared object and GCC installation places the @file{libstdc++.a}
3726 shared library in a common location which will overwrite the and GCC
3727 3.3 version of the shared library. Applications either need to be
3728 re-linked against the new shared library or the GCC 3.1 and GCC 3.3
3729 versions of the @samp{libstdc++} shared object needs to be available
3730 to the AIX runtime loader. The GCC 3.1 @samp{libstdc++.so.4}, if
3731 present, and GCC 3.3 @samp{libstdc++.so.5} shared objects can be
3732 installed for runtime dynamic loading using the following steps to set
3733 the @samp{F_LOADONLY} flag in the shared object for @emph{each}
3734 multilib @file{libstdc++.a} installed:
3736 Extract the shared objects from the currently installed
3737 @file{libstdc++.a} archive:
3739 % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
3742 Enable the @samp{F_LOADONLY} flag so that the shared object will be
3743 available for runtime dynamic loading, but not linking:
3745 % strip -e libstdc++.so.4 libstdc++.so.5
3748 Archive the runtime-only shared object in the GCC 3.4
3749 @file{libstdc++.a} archive:
3751 % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
3754 Linking executables and shared libraries may produce warnings of
3755 duplicate symbols. The assembly files generated by GCC for AIX always
3756 have included multiple symbol definitions for certain global variable
3757 and function declarations in the original program. The warnings should
3758 not prevent the linker from producing a correct library or runnable
3761 AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
3762 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
3763 to parse archive libraries did not handle the new format correctly.
3764 These routines are used by GCC and result in error messages during
3765 linking such as ``not a COFF file''. The version of the routines shipped
3766 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
3767 option of the archive command may be used to create archives of 32-bit
3768 objects using the original ``small format''. A correct version of the
3769 routines is shipped with AIX 4.3.2 and above.
3771 Some versions of the AIX binder (linker) can fail with a relocation
3772 overflow severe error when the @option{-bbigtoc} option is used to link
3773 GCC-produced object files into an executable that overflows the TOC@. A fix
3774 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
3775 available from IBM Customer Support and from its
3776 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3777 website as PTF U455193.
3779 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
3780 with a segmentation fault when invoked by any version of GCC@. A fix for
3781 APAR IX87327 is available from IBM Customer Support and from its
3782 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3783 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
3785 The initial assembler shipped with AIX 4.3.0 generates incorrect object
3786 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
3787 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
3788 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3789 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
3791 AIX provides National Language Support (NLS)@. Compilers and assemblers
3792 use NLS to support locale-specific representations of various data
3793 formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
3794 separating decimal fractions). There have been problems reported where
3795 GCC does not produce the same floating-point formats that the assembler
3796 expects. If one encounters this problem, set the @env{LANG}
3797 environment variable to @samp{C} or @samp{En_US}.
3799 A default can be specified with the @option{-mcpu=@var{cpu_type}}
3800 switch and using the configure option @option{--with-cpu-@var{cpu_type}}.
3805 @heading @anchor{iq2000-x-elf}iq2000-*-elf
3806 Vitesse IQ2000 processors. These are used in embedded
3807 applications. There are no standard Unix configurations.
3812 @heading @anchor{lm32-x-elf}lm32-*-elf
3813 Lattice Mico32 processor.
3814 This configuration is intended for embedded systems.
3819 @heading @anchor{lm32-x-uclinux}lm32-*-uclinux
3820 Lattice Mico32 processor.
3821 This configuration is intended for embedded systems running uClinux.
3826 @heading @anchor{m32c-x-elf}m32c-*-elf
3827 Renesas M32C processor.
3828 This configuration is intended for embedded systems.
3833 @heading @anchor{m32r-x-elf}m32r-*-elf
3834 Renesas M32R processor.
3835 This configuration is intended for embedded systems.
3840 @heading @anchor{m68k-x-x}m68k-*-*
3842 @samp{m68k-*-elf*}, @samp{m68k-*-rtems}, @samp{m68k-*-uclinux} and
3844 build libraries for both M680x0 and ColdFire processors. If you only
3845 need the M680x0 libraries, you can omit the ColdFire ones by passing
3846 @option{--with-arch=m68k} to @command{configure}. Alternatively, you
3847 can omit the M680x0 libraries by passing @option{--with-arch=cf} to
3848 @command{configure}. These targets default to 5206 or 5475 code as
3849 appropriate for the target system when
3850 configured with @option{--with-arch=cf} and 68020 code otherwise.
3852 The @samp{m68k-*-netbsd} and
3853 @samp{m68k-*-openbsd} targets also support the @option{--with-arch}
3854 option. They will generate ColdFire CFV4e code when configured with
3855 @option{--with-arch=cf} and 68020 code otherwise.
3857 You can override the default processors listed above by configuring
3858 with @option{--with-cpu=@var{target}}. This @var{target} can either
3859 be a @option{-mcpu} argument or one of the following values:
3860 @samp{m68000}, @samp{m68010}, @samp{m68020}, @samp{m68030},
3861 @samp{m68040}, @samp{m68060}, @samp{m68020-40} and @samp{m68020-60}.
3863 GCC requires at least binutils version 2.17 on these targets.
3868 @heading @anchor{m68k-x-uclinux}m68k-*-uclinux
3869 GCC 4.3 changed the uClinux configuration so that it uses the
3870 @samp{m68k-linux-gnu} ABI rather than the @samp{m68k-elf} ABI.
3871 It also added improved support for C++ and flat shared libraries,
3872 both of which were ABI changes.
3878 @heading @anchor{mep-x-elf}mep-*-elf
3879 Toshiba Media embedded Processor.
3880 This configuration is intended for embedded systems.
3885 @heading @anchor{microblaze-x-elf}microblaze-*-elf
3886 Xilinx MicroBlaze processor.
3887 This configuration is intended for embedded systems.
3892 @heading @anchor{mips-x-x}mips-*-*
3893 If on a MIPS system you get an error message saying ``does not have gp
3894 sections for all it's [sic] sectons [sic]'', don't worry about it. This
3895 happens whenever you use GAS with the MIPS linker, but there is not
3896 really anything wrong, and it is okay to use the output file. You can
3897 stop such warnings by installing the GNU linker.
3899 It would be nice to extend GAS to produce the gp tables, but they are
3900 optional, and there should not be a warning about their absence.
3902 The libstdc++ atomic locking routines for MIPS targets requires MIPS II
3903 and later. A patch went in just after the GCC 3.3 release to
3904 make @samp{mips*-*-*} use the generic implementation instead. You can also
3905 configure for @samp{mipsel-elf} as a workaround. The
3906 @samp{mips*-*-linux*} target continues to use the MIPS II routines. More
3907 work on this is expected in future releases.
3909 @c If you make --with-llsc the default for another target, please also
3910 @c update the description of the --with-llsc option.
3912 The built-in @code{__sync_*} functions are available on MIPS II and
3913 later systems and others that support the @samp{ll}, @samp{sc} and
3914 @samp{sync} instructions. This can be overridden by passing
3915 @option{--with-llsc} or @option{--without-llsc} when configuring GCC.
3916 Since the Linux kernel emulates these instructions if they are
3917 missing, the default for @samp{mips*-*-linux*} targets is
3918 @option{--with-llsc}. The @option{--with-llsc} and
3919 @option{--without-llsc} configure options may be overridden at compile
3920 time by passing the @option{-mllsc} or @option{-mno-llsc} options to
3923 MIPS systems check for division by zero (unless
3924 @option{-mno-check-zero-division} is passed to the compiler) by
3925 generating either a conditional trap or a break instruction. Using
3926 trap results in smaller code, but is only supported on MIPS II and
3927 later. Also, some versions of the Linux kernel have a bug that
3928 prevents trap from generating the proper signal (@code{SIGFPE}). To enable
3929 the use of break, use the @option{--with-divide=breaks}
3930 @command{configure} option when configuring GCC@. The default is to
3931 use traps on systems that support them.
3933 The assembler from GNU binutils 2.17 and earlier has a bug in the way
3934 it sorts relocations for REL targets (o32, o64, EABI). This can cause
3935 bad code to be generated for simple C++ programs. Also the linker
3936 from GNU binutils versions prior to 2.17 has a bug which causes the
3937 runtime linker stubs in very large programs, like @file{libgcj.so}, to
3938 be incorrectly generated. GNU Binutils 2.18 and later (and snapshots
3939 made after Nov. 9, 2006) should be free from both of these problems.
3944 @heading @anchor{mips-sgi-irix5}mips-sgi-irix5
3946 Support for IRIX 5 has been removed in GCC 4.6.
3951 @heading @anchor{mips-sgi-irix6}mips-sgi-irix6
3953 Support for IRIX 6.5 has been removed in GCC 4.8. Support for IRIX 6
3954 releases before 6.5 has been removed in GCC 4.6, as well as support for
3960 @heading @anchor{moxie-x-elf}moxie-*-elf
3961 The moxie processor.
3966 @heading @anchor{powerpc-x-x}powerpc-*-*
3968 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
3969 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
3972 @uref{ftp://ftp.kernel.org/pub/linux/devel/binutils,,binutils 2.15}
3973 or newer for a working GCC@.
3978 @heading @anchor{powerpc-x-darwin}powerpc-*-darwin*
3979 PowerPC running Darwin (Mac OS X kernel).
3981 Pre-installed versions of Mac OS X may not include any developer tools,
3982 meaning that you will not be able to build GCC from source. Tool
3983 binaries are available at
3984 @uref{http://opensource.apple.com/}.
3986 This version of GCC requires at least cctools-590.36. The
3987 cctools-590.36 package referenced from
3988 @uref{http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html} will not work
3989 on systems older than 10.3.9 (aka darwin7.9.0).
3994 @heading @anchor{powerpc-x-elf}powerpc-*-elf
3995 PowerPC system in big endian mode, running System V.4.
4000 @heading @anchor{powerpc-x-linux-gnu}powerpc*-*-linux-gnu*
4002 PowerPC system in big endian mode running Linux.
4007 @heading @anchor{powerpc-x-netbsd}powerpc-*-netbsd*
4008 PowerPC system in big endian mode running NetBSD@.
4013 @heading @anchor{powerpc-x-eabisim}powerpc-*-eabisim
4014 Embedded PowerPC system in big endian mode for use in running under the
4020 @heading @anchor{powerpc-x-eabi}powerpc-*-eabi
4021 Embedded PowerPC system in big endian mode.
4026 @heading @anchor{powerpcle-x-elf}powerpcle-*-elf
4027 PowerPC system in little endian mode, running System V.4.
4032 @heading @anchor{powerpcle-x-eabisim}powerpcle-*-eabisim
4033 Embedded PowerPC system in little endian mode for use in running under
4039 @heading @anchor{powerpcle-x-eabi}powerpcle-*-eabi
4040 Embedded PowerPC system in little endian mode.
4045 @heading @anchor{rl78-x-elf}rl78-*-elf
4046 The Renesas RL78 processor.
4047 This configuration is intended for embedded systems.
4052 @heading @anchor{rx-x-elf}rx-*-elf
4053 The Renesas RX processor. See
4054 @uref{http://eu.renesas.com/fmwk.jsp?cnt=rx600_series_landing.jsp&fp=/products/mpumcu/rx_family/rx600_series}
4055 for more information about this processor.
4060 @heading @anchor{s390-x-linux}s390-*-linux*
4061 S/390 system running GNU/Linux for S/390@.
4066 @heading @anchor{s390x-x-linux}s390x-*-linux*
4067 zSeries system (64-bit) running GNU/Linux for zSeries@.
4072 @heading @anchor{s390x-ibm-tpf}s390x-ibm-tpf*
4073 zSeries system (64-bit) running TPF@. This platform is
4074 supported as cross-compilation target only.
4079 @c Please use Solaris 2 to refer to all release of Solaris, starting
4080 @c with 2.0 until 2.6, 7, 8, etc. Solaris 1 was a marketing name for
4081 @c SunOS 4 releases which we don't use to avoid confusion. Solaris
4082 @c alone is too unspecific and must be avoided.
4083 @heading @anchor{x-x-solaris2}*-*-solaris2*
4085 Support for Solaris 8 has removed in GCC 4.8. Support for Solaris 7 has
4086 been removed in GCC 4.6.
4088 Sun does not ship a C compiler with Solaris 2 before Solaris 10, though
4089 you can download the Sun Studio compilers for free. In Solaris 10 and
4090 11, GCC 3.4.3 is available as @command{/usr/sfw/bin/gcc}. Solaris 11
4091 also provides GCC 4.5.2 as @command{/usr/gcc/4.5/bin/gcc}. Alternatively,
4092 you can install a pre-built GCC to bootstrap and install GCC. See the
4093 @uref{binaries.html,,binaries page} for details.
4095 The Solaris 2 @command{/bin/sh} will often fail to configure
4096 @samp{libstdc++-v3}, @samp{boehm-gc} or @samp{libjava}. We therefore
4097 recommend using the following initial sequence of commands
4100 % CONFIG_SHELL=/bin/ksh
4101 % export CONFIG_SHELL
4105 and proceed as described in @uref{configure.html,,the configure instructions}.
4106 In addition we strongly recommend specifying an absolute path to invoke
4107 @command{@var{srcdir}/configure}.
4109 Solaris 2 comes with a number of optional OS packages. Some of these
4110 are needed to use GCC fully, namely @code{SUNWarc},
4111 @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
4112 @code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all
4113 optional packages when installing Solaris 2, you will need to verify that
4114 the packages that GCC needs are installed.
4116 To check whether an optional package is installed, use
4117 the @command{pkginfo} command. To add an optional package, use the
4118 @command{pkgadd} command. For further details, see the Solaris 2
4121 Trying to use the linker and other tools in
4122 @file{/usr/ucb} to install GCC has been observed to cause trouble.
4123 For example, the linker may hang indefinitely. The fix is to remove
4124 @file{/usr/ucb} from your @env{PATH}.
4126 The build process works more smoothly with the legacy Sun tools so, if you
4127 have @file{/usr/xpg4/bin} in your @env{PATH}, we recommend that you place
4128 @file{/usr/bin} before @file{/usr/xpg4/bin} for the duration of the build.
4130 We recommend the use of the Sun assembler or the GNU assembler, in
4131 conjunction with the Sun linker. The GNU @command{as}
4132 versions included in Solaris 10, from GNU binutils 2.15, and Solaris 11,
4133 from GNU binutils 2.19, are known to work. They can be found in
4134 @file{/usr/sfw/bin/gas}. Current versions of GNU binutils (2.22)
4135 are known to work as well. Note that your mileage may vary
4136 if you use a combination of the GNU tools and the Sun tools: while the
4137 combination GNU @command{as} + Sun @command{ld} should reasonably work,
4138 the reverse combination Sun @command{as} + GNU @command{ld} may fail to
4139 build or cause memory corruption at runtime in some cases for C++ programs.
4141 GNU @command{ld} usually works as well, although the version included in
4142 Solaris 10 cannot be used due to several bugs. Again, the current
4143 version (2.22) is known to work, but generally lacks platform specific
4144 features, so better stay with Sun @command{ld}. To use the LTO linker
4145 plugin (@option{-fuse-linker-plugin}) with GNU @command{ld}, GNU
4146 binutils @emph{must} be configured with @option{--enable-largefile}.
4148 To enable symbol versioning in @samp{libstdc++} with Sun @command{ld},
4149 you need to have any version of GNU @command{c++filt}, which is part of
4150 GNU binutils. @samp{libstdc++} symbol versioning will be disabled if no
4151 appropriate version is found. Sun @command{c++filt} from the Sun Studio
4152 compilers does @emph{not} work.
4154 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
4155 newer: @command{g++} will complain that types are missing. These headers
4156 assume that omitting the type means @code{int}; this assumption worked for
4157 C90 but is wrong for C++, and is now wrong for C99 also.
4159 Sun bug 4927647 sometimes causes random spurious testsuite failures
4160 related to missing diagnostic output. This bug doesn't affect GCC
4161 itself, rather it is a kernel bug triggered by the @command{expect}
4162 program which is used only by the GCC testsuite driver. When the bug
4163 causes the @command{expect} program to miss anticipated output, extra
4164 testsuite failures appear.
4166 There are patches for Solaris 9 (117171-11 or newer for
4167 SPARC, 117172-11 or newer for Intel) that address this problem.
4169 Thread-local storage (TLS) is supported in Solaris@tie{}9, but requires
4170 some patches. The @samp{libthread} patches provide the
4171 @code{__tls_get_addr} (SPARC, 64-bit x86) resp.@ @code{___tls_get_addr}
4172 (32-bit x86) functions. On Solaris@tie{}9, the necessary support
4173 on SPARC is present since FCS, while 114432-05 or newer is required on
4174 Intel. Additionally, on Solaris@tie{}9/x86, patch 113986-02 or newer is
4175 required for the Sun @command{ld} and runtime linker (@command{ld.so.1})
4176 support, while Solaris@tie{}9/SPARC works since FCS. The linker
4177 patches must be installed even if GNU @command{ld} is used. Sun
4178 @command{as} in Solaris@tie{}9 doesn't support the necessary
4179 relocations, so GNU @command{as} must be used. The @command{configure}
4180 script checks for those prerequisites and automatically enables TLS
4181 support if they are met. Although those minimal patch versions should
4182 work, it is recommended to use the latest patch versions which include
4183 additional bug fixes.
4188 @heading @anchor{sparc-x-x}sparc*-*-*
4190 This section contains general configuration information for all
4191 SPARC-based platforms. In addition to reading this section, please
4192 read all other sections that match your target.
4194 Newer versions of the GNU Multiple Precision Library (GMP), the MPFR
4195 library and the MPC library are known to be miscompiled by earlier
4196 versions of GCC on these platforms. We therefore recommend the use
4197 of the exact versions of these libraries listed as minimal versions
4198 in @uref{prerequisites.html,,the prerequisites}.
4203 @heading @anchor{sparc-sun-solaris2}sparc-sun-solaris2*
4205 When GCC is configured to use GNU binutils 2.14 or later, the binaries
4206 produced are smaller than the ones produced using Sun's native tools;
4207 this difference is quite significant for binaries containing debugging
4210 Starting with Solaris 7, the operating system is capable of executing
4211 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
4212 this; the @option{-m64} option enables 64-bit code generation.
4213 However, if all you want is code tuned for the UltraSPARC CPU, you
4214 should try the @option{-mtune=ultrasparc} option instead, which produces
4215 code that, unlike full 64-bit code, can still run on non-UltraSPARC
4218 When configuring on a Solaris 7 or later system that is running a kernel
4219 that supports only 32-bit binaries, one must configure with
4220 @option{--disable-multilib}, since we will not be able to build the
4221 64-bit target libraries.
4223 GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of
4224 the GNU compiler (especially GCC 3.0.x versions), which lead to the
4225 miscompilation of the stage1 compiler and the subsequent failure of the
4226 bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary
4227 stage, i.e.@: to bootstrap that compiler with the base compiler and then
4228 use it to bootstrap the final compiler.
4230 GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE Studio 7)
4231 and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a bootstrap
4232 failure in form of a miscompilation of the stage1 compiler by the Sun
4233 compiler. This is Sun bug 4974440. This is fixed with patch 112760-07.
4235 GCC 3.4 changed the default debugging format from Stabs to DWARF-2 for
4236 32-bit code on Solaris 7 and later. If you use the Sun assembler, this
4237 change apparently runs afoul of Sun bug 4910101 (which is referenced as
4238 an x86-only problem by Sun, probably because they do not use DWARF-2).
4239 A symptom of the problem is that you cannot compile C++ programs like
4240 @command{groff} 1.19.1 without getting messages similar to the following:
4243 ld: warning: relocation error: R_SPARC_UA32: @dots{}
4244 external symbolic relocation against non-allocatable section
4245 .debug_info cannot be processed at runtime: relocation ignored.
4249 To work around this problem, compile with @option{-gstabs+} instead of
4252 When configuring the GNU Multiple Precision Library (GMP), the MPFR
4253 library or the MPC library on a Solaris 7 or later system, the canonical
4254 target triplet must be specified as the @command{build} parameter on the
4255 configure line. This target triplet can be obtained by invoking @command{./config.guess} in the toplevel source directory of GCC (and
4256 not that of GMP or MPFR or MPC). For example on a Solaris 9 system:
4259 % ./configure --build=sparc-sun-solaris2.9 --prefix=xxx
4265 @heading @anchor{sparc-sun-solaris210}sparc-sun-solaris2.10
4267 There is a bug in older versions of the Sun assembler which breaks
4268 thread-local storage (TLS). A typical error message is
4271 ld: fatal: relocation error: R_SPARC_TLS_LE_HIX22: file /var/tmp//ccamPA1v.o:
4272 symbol <unknown>: bad symbol type SECT: symbol type must be TLS
4276 This bug is fixed in Sun patch 118683-03 or later.
4281 @heading @anchor{sparc-x-linux}sparc-*-linux*
4283 GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
4284 or newer on this platform. All earlier binutils and glibc
4285 releases mishandled unaligned relocations on @code{sparc-*-*} targets.
4291 @heading @anchor{sparc64-x-solaris2}sparc64-*-solaris2*
4293 When configuring the GNU Multiple Precision Library (GMP), the MPFR
4294 library or the MPC library, the canonical target triplet must be specified
4295 as the @command{build} parameter on the configure line. For example
4296 on a Solaris 9 system:
4299 % ./configure --build=sparc64-sun-solaris2.9 --prefix=xxx
4302 The following compiler flags must be specified in the configure
4303 step in order to bootstrap this target with the Sun compiler:
4306 % CC="cc -xarch=v9 -xildoff" @var{srcdir}/configure [@var{options}] [@var{target}]
4310 @option{-xarch=v9} specifies the SPARC-V9 architecture to the Sun toolchain
4311 and @option{-xildoff} turns off the incremental linker.
4316 @heading @anchor{sparcv9-x-solaris2}sparcv9-*-solaris2*
4318 This is a synonym for @samp{sparc64-*-solaris2*}.
4323 @heading @anchor{c6x-x-x}c6x-*-*
4325 The C6X family of processors. This port requires binutils-2.22 or newer.
4330 @heading @anchor{tilegx-*-linux}tilegx-*-linux*
4332 The TILE-Gx processor running GNU/Linux. This port requires
4333 binutils-2.22 or newer.
4338 @heading @anchor{tilepro-*-linux}tilepro-*-linux*
4340 The TILEPro processor running GNU/Linux. This port requires
4341 binutils-2.22 or newer.
4346 @heading @anchor{x-x-vxworks}*-*-vxworks*
4347 Support for VxWorks is in flux. At present GCC supports @emph{only} the
4348 very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC@.
4349 We welcome patches for other architectures supported by VxWorks 5.5.
4350 Support for VxWorks AE would also be welcome; we believe this is merely
4351 a matter of writing an appropriate ``configlette'' (see below). We are
4352 not interested in supporting older, a.out or COFF-based, versions of
4355 VxWorks comes with an older version of GCC installed in
4356 @file{@var{$WIND_BASE}/host}; we recommend you do not overwrite it.
4357 Choose an installation @var{prefix} entirely outside @var{$WIND_BASE}.
4358 Before running @command{configure}, create the directories @file{@var{prefix}}
4359 and @file{@var{prefix}/bin}. Link or copy the appropriate assembler,
4360 linker, etc.@: into @file{@var{prefix}/bin}, and set your @var{PATH} to
4361 include that directory while running both @command{configure} and
4364 You must give @command{configure} the
4365 @option{--with-headers=@var{$WIND_BASE}/target/h} switch so that it can
4366 find the VxWorks system headers. Since VxWorks is a cross compilation
4367 target only, you must also specify @option{--target=@var{target}}.
4368 @command{configure} will attempt to create the directory
4369 @file{@var{prefix}/@var{target}/sys-include} and copy files into it;
4370 make sure the user running @command{configure} has sufficient privilege
4373 GCC's exception handling runtime requires a special ``configlette''
4374 module, @file{contrib/gthr_supp_vxw_5x.c}. Follow the instructions in
4375 that file to add the module to your kernel build. (Future versions of
4376 VxWorks will incorporate this module.)
4381 @heading @anchor{x86-64-x-x}x86_64-*-*, amd64-*-*
4383 GCC supports the x86-64 architecture implemented by the AMD64 processor
4384 (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD@.
4385 On GNU/Linux the default is a bi-arch compiler which is able to generate
4386 both 64-bit x86-64 and 32-bit x86 code (via the @option{-m32} switch).
4391 @heading @anchor{x86-64-x-solaris210}x86_64-*-solaris2.1[0-9]*
4393 GCC also supports the x86-64 architecture implemented by the AMD64
4394 processor (@samp{amd64-*-*} is an alias for @samp{x86_64-*-*}) on
4395 Solaris 10 or later. Unlike other systems, without special options a
4396 bi-arch compiler is built which generates 32-bit code by default, but
4397 can generate 64-bit x86-64 code with the @option{-m64} switch. Since
4398 GCC 4.7, there is also configuration that defaults to 64-bit code, but
4399 can generate 32-bit code with @option{-m32}. To configure and build
4400 this way, you have to provide all support libraries like @file{libgmp}
4401 as 64-bit code, configure with @option{--target=x86_64-pc-solaris2.1x}
4402 and @samp{CC=gcc -m64}.
4407 @heading @anchor{xtensa-x-elf}xtensa*-*-elf
4409 This target is intended for embedded Xtensa systems using the
4410 @samp{newlib} C library. It uses ELF but does not support shared
4411 objects. Designed-defined instructions specified via the
4412 Tensilica Instruction Extension (TIE) language are only supported
4413 through inline assembly.
4415 The Xtensa configuration information must be specified prior to
4416 building GCC@. The @file{include/xtensa-config.h} header
4417 file contains the configuration information. If you created your
4418 own Xtensa configuration with the Xtensa Processor Generator, the
4419 downloaded files include a customized copy of this header file,
4420 which you can use to replace the default header file.
4425 @heading @anchor{xtensa-x-linux}xtensa*-*-linux*
4427 This target is for Xtensa systems running GNU/Linux. It supports ELF
4428 shared objects and the GNU C library (glibc). It also generates
4429 position-independent code (PIC) regardless of whether the
4430 @option{-fpic} or @option{-fPIC} options are used. In other
4431 respects, this target is the same as the
4432 @uref{#xtensa*-*-elf,,@samp{xtensa*-*-elf}} target.
4437 @heading @anchor{windows}Microsoft Windows
4439 @subheading Intel 16-bit versions
4440 The 16-bit versions of Microsoft Windows, such as Windows 3.1, are not
4443 However, the 32-bit port has limited support for Microsoft
4444 Windows 3.11 in the Win32s environment, as a target only. See below.
4446 @subheading Intel 32-bit versions
4448 The 32-bit versions of Windows, including Windows 95, Windows NT, Windows
4449 XP, and Windows Vista, are supported by several different target
4450 platforms. These targets differ in which Windows subsystem they target
4451 and which C libraries are used.
4454 @item Cygwin @uref{#x-x-cygwin,,*-*-cygwin}: Cygwin provides a user-space
4455 Linux API emulation layer in the Win32 subsystem.
4456 @item Interix @uref{#x-x-interix,,*-*-interix}: The Interix subsystem
4457 provides native support for POSIX.
4458 @item MinGW @uref{#x-x-mingw32,,*-*-mingw32}: MinGW is a native GCC port for
4459 the Win32 subsystem that provides a subset of POSIX.
4460 @item MKS i386-pc-mks: NuTCracker from MKS. See
4461 @uref{http://www.mkssoftware.com/} for more information.
4464 @subheading Intel 64-bit versions
4466 GCC contains support for x86-64 using the mingw-w64
4467 runtime library, available from @uref{http://mingw-w64.sourceforge.net/}.
4468 This library should be used with the target triple x86_64-pc-mingw32.
4470 Presently Windows for Itanium is not supported.
4472 @subheading Windows CE
4474 Windows CE is supported as a target only on Hitachi
4475 SuperH (sh-wince-pe), and MIPS (mips-wince-pe).
4477 @subheading Other Windows Platforms
4479 GCC no longer supports Windows NT on the Alpha or PowerPC.
4481 GCC no longer supports the Windows POSIX subsystem. However, it does
4482 support the Interix subsystem. See above.
4484 Old target names including *-*-winnt and *-*-windowsnt are no longer used.
4486 PW32 (i386-pc-pw32) support was never completed, and the project seems to
4487 be inactive. See @uref{http://pw32.sourceforge.net/} for more information.
4489 UWIN support has been removed due to a lack of maintenance.
4494 @heading @anchor{x-x-cygwin}*-*-cygwin
4496 Ports of GCC are included with the
4497 @uref{http://www.cygwin.com/,,Cygwin environment}.
4499 GCC will build under Cygwin without modification; it does not build
4500 with Microsoft's C++ compiler and there are no plans to make it do so.
4502 The Cygwin native compiler can be configured to target any 32-bit x86
4503 cpu architecture desired; the default is i686-pc-cygwin. It should be
4504 used with as up-to-date a version of binutils as possible; use either
4505 the latest official GNU binutils release in the Cygwin distribution,
4506 or version 2.20 or above if building your own.
4511 @heading @anchor{x-x-interix}*-*-interix
4513 The Interix target is used by OpenNT, Interix, Services For UNIX (SFU),
4514 and Subsystem for UNIX-based Applications (SUA). Applications compiled
4515 with this target run in the Interix subsystem, which is separate from
4516 the Win32 subsystem. This target was last known to work in GCC 3.3.
4521 @heading @anchor{x-x-mingw32}*-*-mingw32
4523 GCC will build with and support only MinGW runtime 3.12 and later.
4524 Earlier versions of headers are incompatible with the new default semantics
4525 of @code{extern inline} in @code{-std=c99} and @code{-std=gnu99} modes.
4530 @heading @anchor{older}Older systems
4532 GCC contains support files for many older (1980s and early
4533 1990s) Unix variants. For the most part, support for these systems
4534 has not been deliberately removed, but it has not been maintained for
4535 several years and may suffer from bitrot.
4537 Starting with GCC 3.1, each release has a list of ``obsoleted'' systems.
4538 Support for these systems is still present in that release, but
4539 @command{configure} will fail unless the @option{--enable-obsolete}
4540 option is given. Unless a maintainer steps forward, support for these
4541 systems will be removed from the next release of GCC@.
4543 Support for old systems as hosts for GCC can cause problems if the
4544 workarounds for compiler, library and operating system bugs affect the
4545 cleanliness or maintainability of the rest of GCC@. In some cases, to
4546 bring GCC up on such a system, if still possible with current GCC, may
4547 require first installing an old version of GCC which did work on that
4548 system, and using it to compile a more recent GCC, to avoid bugs in the
4549 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
4550 @file{old-releases} directory on the @uref{../mirrors.html,,GCC mirror
4551 sites}. Header bugs may generally be avoided using
4552 @command{fixincludes}, but bugs or deficiencies in libraries and the
4553 operating system may still cause problems.
4555 Support for older systems as targets for cross-compilation is less
4556 problematic than support for them as hosts for GCC; if an enthusiast
4557 wishes to make such a target work again (including resurrecting any of
4558 the targets that never worked with GCC 2, starting from the last
4559 version before they were removed), patches
4560 @uref{../contribute.html,,following the usual requirements} would be
4561 likely to be accepted, since they should not affect the support for more
4564 For some systems, old versions of GNU binutils may also be useful,
4565 and are available from @file{pub/binutils/old-releases} on
4566 @uref{http://sourceware.org/mirrors.html,,sourceware.org mirror sites}.
4568 Some of the information on specific systems above relates to
4569 such older systems, but much of the information
4570 about GCC on such systems (which may no longer be applicable to
4571 current GCC) is to be found in the GCC texinfo manual.
4576 @heading @anchor{elf}all ELF targets (SVR4, Solaris 2, etc.)
4578 C++ support is significantly better on ELF targets if you use the
4579 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
4580 inlines, vtables and template instantiations will be discarded
4589 @uref{./index.html,,Return to the GCC Installation page}
4593 @c ***Old documentation******************************************************
4595 @include install-old.texi
4601 @uref{./index.html,,Return to the GCC Installation page}
4605 @c ***GFDL********************************************************************
4613 @uref{./index.html,,Return to the GCC Installation page}
4617 @c ***************************************************************************
4618 @c Part 6 The End of the Document
4620 @comment node-name, next, previous, up
4621 @node Concept Index, , GNU Free Documentation License, Top
4625 @unnumbered Concept Index