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
533 Please refer to the @uref{http://gcc.gnu.org/releases.html,,releases web page}
534 for information on how to obtain GCC@.
536 The source distribution includes the C, C++, Objective-C, Fortran, Java,
537 and Ada (in the case of GCC 3.1 and later) compilers, as well as
538 runtime libraries for C++, Objective-C, Fortran, and Java.
539 For previous versions these were downloadable as separate components such
540 as the core GCC distribution, which included the C language front end and
541 shared components, and language-specific distributions including the
542 language front end and the language runtime (where appropriate).
544 If you also intend to build binutils (either to upgrade an existing
545 installation or for use in place of the corresponding tools of your
546 OS), unpack the binutils distribution either in the same directory or
547 a separate one. In the latter case, add symbolic links to any
548 components of the binutils you intend to build alongside the compiler
549 (@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld},
550 @file{opcodes}, @dots{}) to the directory containing the GCC sources.
552 Likewise the GMP, MPFR and MPC libraries can be automatically built
553 together with GCC. Unpack the GMP, MPFR and/or MPC source
554 distributions in the directory containing the GCC sources and rename
555 their directories to @file{gmp}, @file{mpfr} and @file{mpc},
556 respectively (or use symbolic links with the same name).
563 @uref{./index.html,,Return to the GCC Installation page}
567 @c ***Configuration***********************************************************
569 @comment node-name, next, previous, up
570 @node Configuration, Building, Downloading the source, Installing GCC
574 @chapter Installing GCC: Configuration
576 @cindex Configuration
577 @cindex Installing GCC: Configuration
579 Like most GNU software, GCC must be configured before it can be built.
580 This document describes the recommended configuration procedure
581 for both native and cross targets.
583 We use @var{srcdir} to refer to the toplevel source directory for
584 GCC; we use @var{objdir} to refer to the toplevel build/object directory.
586 If you obtained the sources via SVN, @var{srcdir} must refer to the top
587 @file{gcc} directory, the one where the @file{MAINTAINERS} file can be
588 found, and not its @file{gcc} subdirectory, otherwise the build will fail.
590 If either @var{srcdir} or @var{objdir} is located on an automounted NFS
591 file system, the shell's built-in @command{pwd} command will return
592 temporary pathnames. Using these can lead to various sorts of build
593 problems. To avoid this issue, set the @env{PWDCMD} environment
594 variable to an automounter-aware @command{pwd} command, e.g.,
595 @command{pawd} or @samp{amq -w}, during the configuration and build
598 First, we @strong{highly} recommend that GCC be built into a
599 separate directory from the sources which does @strong{not} reside
600 within the source tree. This is how we generally build GCC; building
601 where @var{srcdir} == @var{objdir} should still work, but doesn't
602 get extensive testing; building where @var{objdir} is a subdirectory
603 of @var{srcdir} is unsupported.
605 If you have previously built GCC in the same directory for a
606 different target machine, do @samp{make distclean} to delete all files
607 that might be invalid. One of the files this deletes is @file{Makefile};
608 if @samp{make distclean} complains that @file{Makefile} does not exist
609 or issues a message like ``don't know how to make distclean'' it probably
610 means that the directory is already suitably clean. However, with the
611 recommended method of building in a separate @var{objdir}, you should
612 simply use a different @var{objdir} for each target.
614 Second, when configuring a native system, either @command{cc} or
615 @command{gcc} must be in your path or you must set @env{CC} in
616 your environment before running configure. Otherwise the configuration
620 Note that the bootstrap compiler and the resulting GCC must be link
621 compatible, else the bootstrap will fail with linker errors about
622 incompatible object file formats. Several multilibed targets are
623 affected by this requirement, see
625 @ref{Specific, host/target specific installation notes}.
628 @uref{specific.html,,host/target specific installation notes}.
637 % @var{srcdir}/configure [@var{options}] [@var{target}]
640 @heading Distributor options
642 If you will be distributing binary versions of GCC, with modifications
643 to the source code, you should use the options described in this
644 section to make clear that your version contains modifications.
647 @item --with-pkgversion=@var{version}
648 Specify a string that identifies your package. You may wish
649 to include a build number or build date. This version string will be
650 included in the output of @command{gcc --version}. This suffix does
651 not replace the default version string, only the @samp{GCC} part.
653 The default value is @samp{GCC}.
655 @item --with-bugurl=@var{url}
656 Specify the URL that users should visit if they wish to report a bug.
657 You are of course welcome to forward bugs reported to you to the FSF,
658 if you determine that they are not bugs in your modifications.
660 The default value refers to the FSF's GCC bug tracker.
664 @heading Target specification
667 GCC has code to correctly determine the correct value for @var{target}
668 for nearly all native systems. Therefore, we highly recommend you do
669 not provide a configure target when configuring a native compiler.
672 @var{target} must be specified as @option{--target=@var{target}}
673 when configuring a cross compiler; examples of valid targets would be
674 m68k-elf, sh-elf, etc.
677 Specifying just @var{target} instead of @option{--target=@var{target}}
678 implies that the host defaults to @var{target}.
682 @heading Options specification
684 Use @var{options} to override several configure time options for
685 GCC@. A list of supported @var{options} follows; @samp{configure
686 --help} may list other options, but those not listed below may not
687 work and should not normally be used.
689 Note that each @option{--enable} option has a corresponding
690 @option{--disable} option and that each @option{--with} option has a
691 corresponding @option{--without} option.
694 @item --prefix=@var{dirname}
695 Specify the toplevel installation
696 directory. This is the recommended way to install the tools into a directory
697 other than the default. The toplevel installation directory defaults to
700 We @strong{highly} recommend against @var{dirname} being the same or a
701 subdirectory of @var{objdir} or vice versa. If specifying a directory
702 beneath a user's home directory tree, some shells will not expand
703 @var{dirname} correctly if it contains the @samp{~} metacharacter; use
706 The following standard @command{autoconf} options are supported. Normally you
707 should not need to use these options.
709 @item --exec-prefix=@var{dirname}
710 Specify the toplevel installation directory for architecture-dependent
711 files. The default is @file{@var{prefix}}.
713 @item --bindir=@var{dirname}
714 Specify the installation directory for the executables called by users
715 (such as @command{gcc} and @command{g++}). The default is
716 @file{@var{exec-prefix}/bin}.
718 @item --libdir=@var{dirname}
719 Specify the installation directory for object code libraries and
720 internal data files of GCC@. The default is @file{@var{exec-prefix}/lib}.
722 @item --libexecdir=@var{dirname}
723 Specify the installation directory for internal executables of GCC@.
724 The default is @file{@var{exec-prefix}/libexec}.
726 @item --with-slibdir=@var{dirname}
727 Specify the installation directory for the shared libgcc library. The
728 default is @file{@var{libdir}}.
730 @item --datarootdir=@var{dirname}
731 Specify the root of the directory tree for read-only architecture-independent
732 data files referenced by GCC@. The default is @file{@var{prefix}/share}.
734 @item --infodir=@var{dirname}
735 Specify the installation directory for documentation in info format.
736 The default is @file{@var{datarootdir}/info}.
738 @item --datadir=@var{dirname}
739 Specify the installation directory for some architecture-independent
740 data files referenced by GCC@. The default is @file{@var{datarootdir}}.
742 @item --docdir=@var{dirname}
743 Specify the installation directory for documentation files (other
744 than Info) for GCC@. The default is @file{@var{datarootdir}/doc}.
746 @item --htmldir=@var{dirname}
747 Specify the installation directory for HTML documentation files.
748 The default is @file{@var{docdir}}.
750 @item --pdfdir=@var{dirname}
751 Specify the installation directory for PDF documentation files.
752 The default is @file{@var{docdir}}.
754 @item --mandir=@var{dirname}
755 Specify the installation directory for manual pages. The default is
756 @file{@var{datarootdir}/man}. (Note that the manual pages are only extracts
757 from the full GCC manuals, which are provided in Texinfo format. The manpages
758 are derived by an automatic conversion process from parts of the full
761 @item --with-gxx-include-dir=@var{dirname}
763 the installation directory for G++ header files. The default depends
764 on other configuration options, and differs between cross and native
767 @item --with-specs=@var{specs}
768 Specify additional command line driver SPECS.
769 This can be useful if you need to turn on a non-standard feature by
770 default without modifying the compiler's source code, for instance
771 @option{--with-specs=%@{!fcommon:%@{!fno-common:-fno-common@}@}}.
773 @xref{Spec Files,, Specifying subprocesses and the switches to pass to them,
774 gcc, Using the GNU Compiler Collection (GCC)},
777 See ``Spec Files'' in the main manual
782 @item --program-prefix=@var{prefix}
783 GCC supports some transformations of the names of its programs when
784 installing them. This option prepends @var{prefix} to the names of
785 programs to install in @var{bindir} (see above). For example, specifying
786 @option{--program-prefix=foo-} would result in @samp{gcc}
787 being installed as @file{/usr/local/bin/foo-gcc}.
789 @item --program-suffix=@var{suffix}
790 Appends @var{suffix} to the names of programs to install in @var{bindir}
791 (see above). For example, specifying @option{--program-suffix=-3.1}
792 would result in @samp{gcc} being installed as
793 @file{/usr/local/bin/gcc-3.1}.
795 @item --program-transform-name=@var{pattern}
796 Applies the @samp{sed} script @var{pattern} to be applied to the names
797 of programs to install in @var{bindir} (see above). @var{pattern} has to
798 consist of one or more basic @samp{sed} editing commands, separated by
799 semicolons. For example, if you want the @samp{gcc} program name to be
800 transformed to the installed program @file{/usr/local/bin/myowngcc} and
801 the @samp{g++} program name to be transformed to
802 @file{/usr/local/bin/gspecial++} without changing other program names,
803 you could use the pattern
804 @option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'}
805 to achieve this effect.
807 All three options can be combined and used together, resulting in more
808 complex conversion patterns. As a basic rule, @var{prefix} (and
809 @var{suffix}) are prepended (appended) before further transformations
810 can happen with a special transformation script @var{pattern}.
812 As currently implemented, this option only takes effect for native
813 builds; cross compiler binaries' names are not transformed even when a
814 transformation is explicitly asked for by one of these options.
816 For native builds, some of the installed programs are also installed
817 with the target alias in front of their name, as in
818 @samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen
819 before the target alias is prepended to the name---so, specifying
820 @option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the
821 resulting binary would be installed as
822 @file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}.
824 As a last shortcoming, none of the installed Ada programs are
825 transformed yet, which will be fixed in some time.
827 @item --with-local-prefix=@var{dirname}
829 installation directory for local include files. The default is
830 @file{/usr/local}. Specify this option if you want the compiler to
831 search directory @file{@var{dirname}/include} for locally installed
832 header files @emph{instead} of @file{/usr/local/include}.
834 You should specify @option{--with-local-prefix} @strong{only} if your
835 site has a different convention (not @file{/usr/local}) for where to put
838 The default value for @option{--with-local-prefix} is @file{/usr/local}
839 regardless of the value of @option{--prefix}. Specifying
840 @option{--prefix} has no effect on which directory GCC searches for
841 local header files. This may seem counterintuitive, but actually it is
844 The purpose of @option{--prefix} is to specify where to @emph{install
845 GCC}. The local header files in @file{/usr/local/include}---if you put
846 any in that directory---are not part of GCC@. They are part of other
847 programs---perhaps many others. (GCC installs its own header files in
848 another directory which is based on the @option{--prefix} value.)
850 Both the local-prefix include directory and the GCC-prefix include
851 directory are part of GCC's ``system include'' directories. Although these
852 two directories are not fixed, they need to be searched in the proper
853 order for the correct processing of the include_next directive. The
854 local-prefix include directory is searched before the GCC-prefix
855 include directory. Another characteristic of system include directories
856 is that pedantic warnings are turned off for headers in these directories.
858 Some autoconf macros add @option{-I @var{directory}} options to the
859 compiler command line, to ensure that directories containing installed
860 packages' headers are searched. When @var{directory} is one of GCC's
861 system include directories, GCC will ignore the option so that system
862 directories continue to be processed in the correct order. This
863 may result in a search order different from what was specified but the
864 directory will still be searched.
866 GCC automatically searches for ordinary libraries using
867 @env{GCC_EXEC_PREFIX}. Thus, when the same installation prefix is
868 used for both GCC and packages, GCC will automatically search for
869 both headers and libraries. This provides a configuration that is
870 easy to use. GCC behaves in a manner similar to that when it is
871 installed as a system compiler in @file{/usr}.
873 Sites that need to install multiple versions of GCC may not want to
874 use the above simple configuration. It is possible to use the
875 @option{--program-prefix}, @option{--program-suffix} and
876 @option{--program-transform-name} options to install multiple versions
877 into a single directory, but it may be simpler to use different prefixes
878 and the @option{--with-local-prefix} option to specify the location of the
879 site-specific files for each version. It will then be necessary for
880 users to specify explicitly the location of local site libraries
881 (e.g., with @env{LIBRARY_PATH}).
883 The same value can be used for both @option{--with-local-prefix} and
884 @option{--prefix} provided it is not @file{/usr}. This can be used
885 to avoid the default search of @file{/usr/local/include}.
887 @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
888 The directory you use for @option{--with-local-prefix} @strong{must not}
889 contain any of the system's standard header files. If it did contain
890 them, certain programs would be miscompiled (including GNU Emacs, on
891 certain targets), because this would override and nullify the header
892 file corrections made by the @command{fixincludes} script.
894 Indications are that people who use this option use it based on mistaken
895 ideas of what it is for. People use it as if it specified where to
896 install part of GCC@. Perhaps they make this assumption because
897 installing GCC creates the directory.
899 @item --with-native-system-header-dir=@var{dirname}
900 Specifies that @var{dirname} is the directory that contains native system
901 header files, rather than @file{/usr/include}. This option is most useful
902 if you are creating a compiler that should be isolated from the system
903 as much as possible. It is most commonly used with the
904 @option{--with-sysroot} option and will cause GCC to search
905 @var{dirname} inside the system root specified by that option.
907 @item --enable-shared[=@var{package}[,@dots{}]]
908 Build shared versions of libraries, if shared libraries are supported on
909 the target platform. Unlike GCC 2.95.x and earlier, shared libraries
910 are enabled by default on all platforms that support shared libraries.
912 If a list of packages is given as an argument, build shared libraries
913 only for the listed packages. For other packages, only static libraries
914 will be built. Package names currently recognized in the GCC tree are
915 @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not
916 @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc},
917 @samp{ada}, @samp{libada}, @samp{libjava}, @samp{libgo}, and @samp{libobjc}.
918 Note @samp{libiberty} does not support shared libraries at all.
920 Use @option{--disable-shared} to build only static libraries. Note that
921 @option{--disable-shared} does not accept a list of package names as
922 argument, only @option{--enable-shared} does.
924 @item @anchor{with-gnu-as}--with-gnu-as
925 Specify that the compiler should assume that the
926 assembler it finds is the GNU assembler. However, this does not modify
927 the rules to find an assembler and will result in confusion if the
928 assembler found is not actually the GNU assembler. (Confusion may also
929 result if the compiler finds the GNU assembler but has not been
930 configured with @option{--with-gnu-as}.) If you have more than one
931 assembler installed on your system, you may want to use this option in
932 connection with @option{--with-as=@var{pathname}} or
933 @option{--with-build-time-tools=@var{pathname}}.
935 The following systems are the only ones where it makes a difference
936 whether you use the GNU assembler. On any other system,
937 @option{--with-gnu-as} has no effect.
940 @item @samp{hppa1.0-@var{any}-@var{any}}
941 @item @samp{hppa1.1-@var{any}-@var{any}}
942 @item @samp{sparc-sun-solaris2.@var{any}}
943 @item @samp{sparc64-@var{any}-solaris2.@var{any}}
946 @item @anchor{with-as}--with-as=@var{pathname}
947 Specify that the compiler should use the assembler pointed to by
948 @var{pathname}, rather than the one found by the standard rules to find
949 an assembler, which are:
952 Unless GCC is being built with a cross compiler, check the
953 @file{@var{libexec}/gcc/@var{target}/@var{version}} directory.
954 @var{libexec} defaults to @file{@var{exec-prefix}/libexec};
955 @var{exec-prefix} defaults to @var{prefix}, which
956 defaults to @file{/usr/local} unless overridden by the
957 @option{--prefix=@var{pathname}} switch described above. @var{target}
958 is the target system triple, such as @samp{sparc-sun-solaris2.7}, and
959 @var{version} denotes the GCC version, such as 3.0.
962 If the target system is the same that you are building on, check
963 operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
967 Check in the @env{PATH} for a tool whose name is prefixed by the
968 target system triple.
971 Check in the @env{PATH} for a tool whose name is not prefixed by the
972 target system triple, if the host and target system triple are
973 the same (in other words, we use a host tool if it can be used for
977 You may want to use @option{--with-as} if no assembler
978 is installed in the directories listed above, or if you have multiple
979 assemblers installed and want to choose one that is not found by the
982 @item @anchor{with-gnu-ld}--with-gnu-ld
983 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
986 @item --with-ld=@var{pathname}
987 Same as @uref{#with-as,,@option{--with-as}}
991 Specify that stabs debugging
992 information should be used instead of whatever format the host normally
993 uses. Normally GCC uses the same debug format as the host system.
995 On MIPS based systems and on Alphas, you must specify whether you want
996 GCC to create the normal ECOFF debugging format, or to use BSD-style
997 stabs passed through the ECOFF symbol table. The normal ECOFF debug
998 format cannot fully handle languages other than C@. BSD stabs format can
999 handle other languages, but it only works with the GNU debugger GDB@.
1001 Normally, GCC uses the ECOFF debugging format by default; if you
1002 prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@.
1004 No matter which default you choose when you configure GCC, the user
1005 can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
1006 the debug format for a particular compilation.
1008 @option{--with-stabs} is meaningful on the ISC system on the 386, also, if
1009 @option{--with-gas} is used. It selects use of stabs debugging
1010 information embedded in COFF output. This kind of debugging information
1011 supports C++ well; ordinary COFF debugging information does not.
1013 @option{--with-stabs} is also meaningful on 386 systems running SVR4. It
1014 selects use of stabs debugging information embedded in ELF output. The
1015 C++ compiler currently (2.6.0) does not support the DWARF debugging
1016 information normally used on 386 SVR4 platforms; stabs provide a
1017 workable alternative. This requires gas and gdb, as the normal SVR4
1018 tools can not generate or interpret stabs.
1020 @item --with-tls=@var{dialect}
1021 Specify the default TLS dialect, for systems were there is a choice.
1022 For ARM targets, possible values for @var{dialect} are @code{gnu} or
1023 @code{gnu2}, which select between the original GNU dialect and the GNU TLS
1024 descriptor-based dialect.
1026 @item --enable-multiarch
1027 Specify whether to enable or disable multiarch support. The default is
1028 to check for glibc start files in a multiarch location, and enable it
1029 if the files are found. The auto detection is enabled for native builds,
1030 and for cross builds configured with @option{--with-sysroot}, and without
1031 @option{--with-native-system-header-dir}.
1032 More documentation about multiarch can be found at
1033 @uref{http://wiki.debian.org/Multiarch}.
1035 @item --disable-multilib
1036 Specify that multiple target
1037 libraries to support different target variants, calling
1038 conventions, etc.@: should not be built. The default is to build a
1039 predefined set of them.
1041 Some targets provide finer-grained control over which multilibs are built
1042 (e.g., @option{--disable-softfloat}):
1045 fpu, 26bit, underscore, interwork, biendian, nofmult.
1048 softfloat, m68881, m68000, m68020.
1051 single-float, biendian, softfloat.
1053 @item powerpc*-*-*, rs6000*-*-*
1054 aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
1059 @item --with-multilib-list=@var{list}
1060 @itemx --without-multilib-list
1061 Specify what multilibs to build.
1062 Currently only implemented for sh*-*-* and x86-64-*-linux*.
1066 @var{list} is a comma separated list of CPU names. These must be of the
1067 form @code{sh*} or @code{m*} (in which case they match the compiler option
1068 for that processor). The list should not contain any endian options -
1069 these are handled by @option{--with-endian}.
1071 If @var{list} is empty, then there will be no multilibs for extra
1072 processors. The multilib for the secondary endian remains enabled.
1074 As a special case, if an entry in the list starts with a @code{!}
1075 (exclamation point), then it is added to the list of excluded multilibs.
1076 Entries of this sort should be compatible with @samp{MULTILIB_EXCLUDES}
1077 (once the leading @code{!} has been stripped).
1079 If @option{--with-multilib-list} is not given, then a default set of
1080 multilibs is selected based on the value of @option{--target}. This is
1081 usually the complete set of libraries, but some targets imply a more
1084 Example 1: to configure a compiler for SH4A only, but supporting both
1085 endians, with little endian being the default:
1087 --with-cpu=sh4a --with-endian=little,big --with-multilib-list=
1090 Example 2: to configure a compiler for both SH4A and SH4AL-DSP, but with
1091 only little endian SH4AL:
1093 --with-cpu=sh4a --with-endian=little,big \
1094 --with-multilib-list=sh4al,!mb/m4al
1097 @item x86-64-*-linux*
1098 @var{list} is a comma separated list of @code{m32}, @code{m64} and
1099 @code{mx32} to enable 32-bit, 64-bit and x32 run-time libraries,
1100 respectively. If @var{list} is empty, then there will be no multilibs
1101 and only the default run-time library will be enabled.
1103 If @option{--with-multilib-list} is not given, then only 32-bit and
1104 64-bit run-time libraries will be enabled.
1107 @item --with-endian=@var{endians}
1108 Specify what endians to use.
1109 Currently only implemented for sh*-*-*.
1111 @var{endians} may be one of the following:
1114 Use big endian exclusively.
1116 Use little endian exclusively.
1118 Use big endian by default. Provide a multilib for little endian.
1120 Use little endian by default. Provide a multilib for big endian.
1123 @item --enable-threads
1124 Specify that the target
1125 supports threads. This affects the Objective-C compiler and runtime
1126 library, and exception handling for other languages like C++ and Java.
1127 On some systems, this is the default.
1129 In general, the best (and, in many cases, the only known) threading
1130 model available will be configured for use. Beware that on some
1131 systems, GCC has not been taught what threading models are generally
1132 available for the system. In this case, @option{--enable-threads} is an
1133 alias for @option{--enable-threads=single}.
1135 @item --disable-threads
1136 Specify that threading support should be disabled for the system.
1137 This is an alias for @option{--enable-threads=single}.
1139 @item --enable-threads=@var{lib}
1141 @var{lib} is the thread support library. This affects the Objective-C
1142 compiler and runtime library, and exception handling for other languages
1143 like C++ and Java. The possibilities for @var{lib} are:
1151 LynxOS thread support.
1153 MIPS SDE thread support.
1155 This is an alias for @samp{single}.
1157 Generic POSIX/Unix98 thread support.
1159 RTEMS thread support.
1161 Disable thread support, should work for all platforms.
1165 VxWorks thread support.
1167 Microsoft Win32 API thread support.
1171 Specify that the target supports TLS (Thread Local Storage). Usually
1172 configure can correctly determine if TLS is supported. In cases where
1173 it guesses incorrectly, TLS can be explicitly enabled or disabled with
1174 @option{--enable-tls} or @option{--disable-tls}. This can happen if
1175 the assembler supports TLS but the C library does not, or if the
1176 assumptions made by the configure test are incorrect.
1179 Specify that the target does not support TLS.
1180 This is an alias for @option{--enable-tls=no}.
1182 @item --with-cpu=@var{cpu}
1183 @itemx --with-cpu-32=@var{cpu}
1184 @itemx --with-cpu-64=@var{cpu}
1185 Specify which cpu variant the compiler should generate code for by default.
1186 @var{cpu} will be used as the default value of the @option{-mcpu=} switch.
1187 This option is only supported on some targets, including ARM, i386, M68k,
1188 PowerPC, and SPARC@. The @option{--with-cpu-32} and
1189 @option{--with-cpu-64} options specify separate default CPUs for
1190 32-bit and 64-bit modes; these options are only supported for i386,
1193 @item --with-schedule=@var{cpu}
1194 @itemx --with-arch=@var{cpu}
1195 @itemx --with-arch-32=@var{cpu}
1196 @itemx --with-arch-64=@var{cpu}
1197 @itemx --with-tune=@var{cpu}
1198 @itemx --with-tune-32=@var{cpu}
1199 @itemx --with-tune-64=@var{cpu}
1200 @itemx --with-abi=@var{abi}
1201 @itemx --with-fpu=@var{type}
1202 @itemx --with-float=@var{type}
1203 These configure options provide default values for the @option{-mschedule=},
1204 @option{-march=}, @option{-mtune=}, @option{-mabi=}, and @option{-mfpu=}
1205 options and for @option{-mhard-float} or @option{-msoft-float}. As with
1206 @option{--with-cpu}, which switches will be accepted and acceptable values
1207 of the arguments depend on the target.
1209 @item --with-mode=@var{mode}
1210 Specify if the compiler should default to @option{-marm} or @option{-mthumb}.
1211 This option is only supported on ARM targets.
1213 @item --with-stack-offset=@var{num}
1214 This option sets the default for the -mstack-offset=@var{num} option,
1215 and will thus generally also control the setting of this option for
1216 libraries. This option is only supported on Epiphany targets.
1218 @item --with-fpmath=@var{isa}
1219 This options sets @option{-mfpmath=sse} by default and specifies the default
1220 ISA for floating-point arithmetics. You can select either @samp{sse} which
1221 enables @option{-msse2} or @samp{avx} which enables @option{-mavx} by default.
1222 This option is only supported on i386 and x86-64 targets.
1224 @item --with-nan=@var{encoding}
1225 On MIPS targets, set the default encoding convention to use for the
1226 special not-a-number (NaN) IEEE 754 floating-point data. The
1227 possibilities for @var{encoding} are:
1230 Use the legacy encoding, as with the @option{-mnan=legacy} command-line
1233 Use the 754-2008 encoding, as with the @option{-mnan=2008} command-line
1236 To use this configuration option you must have an assembler version
1237 installed that supports the @option{-mnan=} command-line option too.
1238 In the absence of this configuration option the default convention is
1239 the legacy encoding, as when neither of the @option{-mnan=2008} and
1240 @option{-mnan=legacy} command-line options has been used.
1242 @item --with-divide=@var{type}
1243 Specify how the compiler should generate code for checking for
1244 division by zero. This option is only supported on the MIPS target.
1245 The possibilities for @var{type} are:
1248 Division by zero checks use conditional traps (this is the default on
1249 systems that support conditional traps).
1251 Division by zero checks use the break instruction.
1254 @c If you make --with-llsc the default for additional targets,
1255 @c update the --with-llsc description in the MIPS section below.
1258 On MIPS targets, make @option{-mllsc} the default when no
1259 @option{-mno-llsc} option is passed. This is the default for
1260 Linux-based targets, as the kernel will emulate them if the ISA does
1263 @item --without-llsc
1264 On MIPS targets, make @option{-mno-llsc} the default when no
1265 @option{-mllsc} option is passed.
1268 On MIPS targets, make @option{-msynci} the default when no
1269 @option{-mno-synci} option is passed.
1271 @item --without-synci
1272 On MIPS targets, make @option{-mno-synci} the default when no
1273 @option{-msynci} option is passed. This is the default.
1275 @item --with-mips-plt
1276 On MIPS targets, make use of copy relocations and PLTs.
1277 These features are extensions to the traditional
1278 SVR4-based MIPS ABIs and require support from GNU binutils
1279 and the runtime C library.
1281 @item --enable-__cxa_atexit
1282 Define if you want to use __cxa_atexit, rather than atexit, to
1283 register C++ destructors for local statics and global objects.
1284 This is essential for fully standards-compliant handling of
1285 destructors, but requires __cxa_atexit in libc. This option is currently
1286 only available on systems with GNU libc. When enabled, this will cause
1287 @option{-fuse-cxa-atexit} to be passed by default.
1289 @item --enable-gnu-indirect-function
1290 Define if you want to enable the @code{ifunc} attribute. This option is
1291 currently only available on systems with GNU libc on certain targets.
1293 @item --enable-target-optspace
1295 libraries should be optimized for code space instead of code speed.
1296 This is the default for the m32r platform.
1298 @item --with-cpp-install-dir=@var{dirname}
1299 Specify that the user visible @command{cpp} program should be installed
1300 in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
1302 @item --enable-comdat
1303 Enable COMDAT group support. This is primarily used to override the
1304 automatically detected value.
1306 @item --enable-initfini-array
1307 Force the use of sections @code{.init_array} and @code{.fini_array}
1308 (instead of @code{.init} and @code{.fini}) for constructors and
1309 destructors. Option @option{--disable-initfini-array} has the
1310 opposite effect. If neither option is specified, the configure script
1311 will try to guess whether the @code{.init_array} and
1312 @code{.fini_array} sections are supported and, if they are, use them.
1314 @item --enable-link-mutex
1315 When building GCC, use a mutex to avoid linking the compilers for
1316 multiple languages at the same time, to avoid thrashing on build
1317 systems with limited free memory. The default is not to use such a mutex.
1319 @item --enable-maintainer-mode
1320 The build rules that regenerate the Autoconf and Automake output files as
1321 well as the GCC master message catalog @file{gcc.pot} are normally
1322 disabled. This is because it can only be rebuilt if the complete source
1323 tree is present. If you have changed the sources and want to rebuild the
1324 catalog, configuring with @option{--enable-maintainer-mode} will enable
1325 this. Note that you need a recent version of the @code{gettext} tools
1328 @item --disable-bootstrap
1329 For a native build, the default configuration is to perform
1330 a 3-stage bootstrap of the compiler when @samp{make} is invoked,
1331 testing that GCC can compile itself correctly. If you want to disable
1332 this process, you can configure with @option{--disable-bootstrap}.
1334 @item --enable-bootstrap
1335 In special cases, you may want to perform a 3-stage build
1336 even if the target and host triplets are different.
1337 This is possible when the host can run code compiled for
1338 the target (e.g.@: host is i686-linux, target is i486-linux).
1339 Starting from GCC 4.2, to do this you have to configure explicitly
1340 with @option{--enable-bootstrap}.
1342 @item --enable-generated-files-in-srcdir
1343 Neither the .c and .h files that are generated from Bison and flex nor the
1344 info manuals and man pages that are built from the .texi files are present
1345 in the SVN development tree. When building GCC from that development tree,
1346 or from one of our snapshots, those generated files are placed in your
1347 build directory, which allows for the source to be in a readonly
1350 If you configure with @option{--enable-generated-files-in-srcdir} then those
1351 generated files will go into the source directory. This is mainly intended
1352 for generating release or prerelease tarballs of the GCC sources, since it
1353 is not a requirement that the users of source releases to have flex, Bison,
1356 @item --enable-version-specific-runtime-libs
1358 that runtime libraries should be installed in the compiler specific
1359 subdirectory (@file{@var{libdir}/gcc}) rather than the usual places. In
1360 addition, @samp{libstdc++}'s include files will be installed into
1361 @file{@var{libdir}} unless you overruled it by using
1362 @option{--with-gxx-include-dir=@var{dirname}}. Using this option is
1363 particularly useful if you intend to use several versions of GCC in
1364 parallel. This is currently supported by @samp{libgfortran},
1365 @samp{libjava}, @samp{libmudflap}, @samp{libstdc++}, and @samp{libobjc}.
1367 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
1368 Specify that only a particular subset of compilers and
1369 their runtime libraries should be built. For a list of valid values for
1370 @var{langN} you can issue the following command in the
1371 @file{gcc} directory of your GCC source tree:@*
1373 grep language= */config-lang.in
1375 Currently, you can use any of the following:
1376 @code{all}, @code{ada}, @code{c}, @code{c++}, @code{fortran},
1377 @code{go}, @code{java}, @code{objc}, @code{obj-c++}.
1378 Building the Ada compiler has special requirements, see below.
1379 If you do not pass this flag, or specify the option @code{all}, then all
1380 default languages available in the @file{gcc} sub-tree will be configured.
1381 Ada, Go and Objective-C++ are not default languages; the rest are.
1383 @item --enable-stage1-languages=@var{lang1},@var{lang2},@dots{}
1384 Specify that a particular subset of compilers and their runtime
1385 libraries should be built with the system C compiler during stage 1 of
1386 the bootstrap process, rather than only in later stages with the
1387 bootstrapped C compiler. The list of valid values is the same as for
1388 @option{--enable-languages}, and the option @code{all} will select all
1389 of the languages enabled by @option{--enable-languages}. This option is
1390 primarily useful for GCC development; for instance, when a development
1391 version of the compiler cannot bootstrap due to compiler bugs, or when
1392 one is debugging front ends other than the C front end. When this
1393 option is used, one can then build the target libraries for the
1394 specified languages with the stage-1 compiler by using @command{make
1395 stage1-bubble all-target}, or run the testsuite on the stage-1 compiler
1396 for the specified languages using @command{make stage1-start check-gcc}.
1398 @item --disable-libada
1399 Specify that the run-time libraries and tools used by GNAT should not
1400 be built. This can be useful for debugging, or for compatibility with
1401 previous Ada build procedures, when it was required to explicitly
1402 do a @samp{make -C gcc gnatlib_and_tools}.
1404 @item --disable-libssp
1405 Specify that the run-time libraries for stack smashing protection
1406 should not be built.
1408 @item --disable-libquadmath
1409 Specify that the GCC quad-precision math library should not be built.
1410 On some systems, the library is required to be linkable when building
1411 the Fortran front end, unless @option{--disable-libquadmath-support}
1414 @item --disable-libquadmath-support
1415 Specify that the Fortran front end and @code{libgfortran} do not add
1416 support for @code{libquadmath} on systems supporting it.
1418 @item --disable-libgomp
1419 Specify that the run-time libraries used by GOMP should not be built.
1422 Specify that the compiler should
1423 use DWARF 2 debugging information as the default.
1425 @item --enable-targets=all
1426 @itemx --enable-targets=@var{target_list}
1427 Some GCC targets, e.g.@: powerpc64-linux, build bi-arch compilers.
1428 These are compilers that are able to generate either 64-bit or 32-bit
1429 code. Typically, the corresponding 32-bit target, e.g.@:
1430 powerpc-linux for powerpc64-linux, only generates 32-bit code. This
1431 option enables the 32-bit target to be a bi-arch compiler, which is
1432 useful when you want a bi-arch compiler that defaults to 32-bit, and
1433 you are building a bi-arch or multi-arch binutils in a combined tree.
1434 On mips-linux, this will build a tri-arch compiler (ABI o32/n32/64),
1436 Currently, this option only affects sparc-linux, powerpc-linux, x86-linux,
1437 mips-linux and s390-linux.
1439 @item --enable-secureplt
1440 This option enables @option{-msecure-plt} by default for powerpc-linux.
1442 @xref{RS/6000 and PowerPC Options,, RS/6000 and PowerPC Options, gcc,
1443 Using the GNU Compiler Collection (GCC)},
1446 See ``RS/6000 and PowerPC Options'' in the main manual
1450 This option enables @option{-mcld} by default for 32-bit x86 targets.
1452 @xref{i386 and x86-64 Options,, i386 and x86-64 Options, gcc,
1453 Using the GNU Compiler Collection (GCC)},
1456 See ``i386 and x86-64 Options'' in the main manual
1459 @item --enable-win32-registry
1460 @itemx --enable-win32-registry=@var{key}
1461 @itemx --disable-win32-registry
1462 The @option{--enable-win32-registry} option enables Microsoft Windows-hosted GCC
1463 to look up installations paths in the registry using the following key:
1466 @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
1469 @var{key} defaults to GCC version number, and can be overridden by the
1470 @option{--enable-win32-registry=@var{key}} option. Vendors and distributors
1471 who use custom installers are encouraged to provide a different key,
1472 perhaps one comprised of vendor name and GCC version number, to
1473 avoid conflict with existing installations. This feature is enabled
1474 by default, and can be disabled by @option{--disable-win32-registry}
1475 option. This option has no effect on the other hosts.
1478 Specify that the machine does not have a floating point unit. This
1479 option only applies to @samp{m68k-sun-sunos@var{n}}. On any other
1480 system, @option{--nfp} has no effect.
1482 @item --enable-werror
1483 @itemx --disable-werror
1484 @itemx --enable-werror=yes
1485 @itemx --enable-werror=no
1486 When you specify this option, it controls whether certain files in the
1487 compiler are built with @option{-Werror} in bootstrap stage2 and later.
1488 If you don't specify it, @option{-Werror} is turned on for the main
1489 development trunk. However it defaults to off for release branches and
1490 final releases. The specific files which get @option{-Werror} are
1491 controlled by the Makefiles.
1493 @item --enable-checking
1494 @itemx --enable-checking=@var{list}
1495 When you specify this option, the compiler is built to perform internal
1496 consistency checks of the requested complexity. This does not change the
1497 generated code, but adds error checking within the compiler. This will
1498 slow down the compiler and may only work properly if you are building
1499 the compiler with GCC@. This is @samp{yes} by default when building
1500 from SVN or snapshots, but @samp{release} for releases. The default
1501 for building the stage1 compiler is @samp{yes}. More control
1502 over the checks may be had by specifying @var{list}. The categories of
1503 checks available are @samp{yes} (most common checks
1504 @samp{assert,misc,tree,gc,rtlflag,runtime}), @samp{no} (no checks at
1505 all), @samp{all} (all but @samp{valgrind}), @samp{release} (cheapest
1506 checks @samp{assert,runtime}) or @samp{none} (same as @samp{no}).
1507 Individual checks can be enabled with these flags @samp{assert},
1508 @samp{df}, @samp{fold}, @samp{gc}, @samp{gcac} @samp{misc}, @samp{rtl},
1509 @samp{rtlflag}, @samp{runtime}, @samp{tree}, and @samp{valgrind}.
1511 The @samp{valgrind} check requires the external @command{valgrind}
1512 simulator, available from @uref{http://valgrind.org/}. The
1513 @samp{df}, @samp{rtl}, @samp{gcac} and @samp{valgrind} checks are very expensive.
1514 To disable all checking, @samp{--disable-checking} or
1515 @samp{--enable-checking=none} must be explicitly requested. Disabling
1516 assertions will make the compiler and runtime slightly faster but
1517 increase the risk of undetected internal errors causing wrong code to be
1520 @item --disable-stage1-checking
1521 @itemx --enable-stage1-checking
1522 @itemx --enable-stage1-checking=@var{list}
1523 If no @option{--enable-checking} option is specified the stage1
1524 compiler will be built with @samp{yes} checking enabled, otherwise
1525 the stage1 checking flags are the same as specified by
1526 @option{--enable-checking}. To build the stage1 compiler with
1527 different checking options use @option{--enable-stage1-checking}.
1528 The list of checking options is the same as for @option{--enable-checking}.
1529 If your system is too slow or too small to bootstrap a released compiler
1530 with checking for stage1 enabled, you can use @samp{--disable-stage1-checking}
1531 to disable checking for the stage1 compiler.
1533 @item --enable-coverage
1534 @itemx --enable-coverage=@var{level}
1535 With this option, the compiler is built to collect self coverage
1536 information, every time it is run. This is for internal development
1537 purposes, and only works when the compiler is being built with gcc. The
1538 @var{level} argument controls whether the compiler is built optimized or
1539 not, values are @samp{opt} and @samp{noopt}. For coverage analysis you
1540 want to disable optimization, for performance analysis you want to
1541 enable optimization. When coverage is enabled, the default level is
1542 without optimization.
1544 @item --enable-gather-detailed-mem-stats
1545 When this option is specified more detailed information on memory
1546 allocation is gathered. This information is printed when using
1547 @option{-fmem-report}.
1550 @itemx --disable-nls
1551 The @option{--enable-nls} option enables Native Language Support (NLS),
1552 which lets GCC output diagnostics in languages other than American
1553 English. Native Language Support is enabled by default if not doing a
1554 canadian cross build. The @option{--disable-nls} option disables NLS@.
1556 @item --with-included-gettext
1557 If NLS is enabled, the @option{--with-included-gettext} option causes the build
1558 procedure to prefer its copy of GNU @command{gettext}.
1560 @item --with-catgets
1561 If NLS is enabled, and if the host lacks @code{gettext} but has the
1562 inferior @code{catgets} interface, the GCC build procedure normally
1563 ignores @code{catgets} and instead uses GCC's copy of the GNU
1564 @code{gettext} library. The @option{--with-catgets} option causes the
1565 build procedure to use the host's @code{catgets} in this situation.
1567 @item --with-libiconv-prefix=@var{dir}
1568 Search for libiconv header files in @file{@var{dir}/include} and
1569 libiconv library files in @file{@var{dir}/lib}.
1571 @item --enable-obsolete
1572 Enable configuration for an obsoleted system. If you attempt to
1573 configure GCC for a system (build, host, or target) which has been
1574 obsoleted, and you do not specify this flag, configure will halt with an
1577 All support for systems which have been obsoleted in one release of GCC
1578 is removed entirely in the next major release, unless someone steps
1579 forward to maintain the port.
1581 @item --enable-decimal-float
1582 @itemx --enable-decimal-float=yes
1583 @itemx --enable-decimal-float=no
1584 @itemx --enable-decimal-float=bid
1585 @itemx --enable-decimal-float=dpd
1586 @itemx --disable-decimal-float
1587 Enable (or disable) support for the C decimal floating point extension
1588 that is in the IEEE 754-2008 standard. This is enabled by default only
1589 on PowerPC, i386, and x86_64 GNU/Linux systems. Other systems may also
1590 support it, but require the user to specifically enable it. You can
1591 optionally control which decimal floating point format is used (either
1592 @samp{bid} or @samp{dpd}). The @samp{bid} (binary integer decimal)
1593 format is default on i386 and x86_64 systems, and the @samp{dpd}
1594 (densely packed decimal) format is default on PowerPC systems.
1596 @item --enable-fixed-point
1597 @itemx --disable-fixed-point
1598 Enable (or disable) support for C fixed-point arithmetic.
1599 This option is enabled by default for some targets (such as MIPS) which
1600 have hardware-support for fixed-point operations. On other targets, you
1601 may enable this option manually.
1603 @item --with-long-double-128
1604 Specify if @code{long double} type should be 128-bit by default on selected
1605 GNU/Linux architectures. If using @code{--without-long-double-128},
1606 @code{long double} will be by default 64-bit, the same as @code{double} type.
1607 When neither of these configure options are used, the default will be
1608 128-bit @code{long double} when built against GNU C Library 2.4 and later,
1609 64-bit @code{long double} otherwise.
1611 @item --with-gmp=@var{pathname}
1612 @itemx --with-gmp-include=@var{pathname}
1613 @itemx --with-gmp-lib=@var{pathname}
1614 @itemx --with-mpfr=@var{pathname}
1615 @itemx --with-mpfr-include=@var{pathname}
1616 @itemx --with-mpfr-lib=@var{pathname}
1617 @itemx --with-mpc=@var{pathname}
1618 @itemx --with-mpc-include=@var{pathname}
1619 @itemx --with-mpc-lib=@var{pathname}
1620 If you want to build GCC but do not have the GMP library, the MPFR
1621 library and/or the MPC library installed in a standard location and
1622 do not have their sources present in the GCC source tree then you
1623 can explicitly specify the directory where they are installed
1624 (@samp{--with-gmp=@var{gmpinstalldir}},
1625 @samp{--with-mpfr=@/@var{mpfrinstalldir}},
1626 @samp{--with-mpc=@/@var{mpcinstalldir}}). The
1627 @option{--with-gmp=@/@var{gmpinstalldir}} option is shorthand for
1628 @option{--with-gmp-lib=@/@var{gmpinstalldir}/lib} and
1629 @option{--with-gmp-include=@/@var{gmpinstalldir}/include}. Likewise the
1630 @option{--with-mpfr=@/@var{mpfrinstalldir}} option is shorthand for
1631 @option{--with-mpfr-lib=@/@var{mpfrinstalldir}/lib} and
1632 @option{--with-mpfr-include=@/@var{mpfrinstalldir}/include}, also the
1633 @option{--with-mpc=@/@var{mpcinstalldir}} option is shorthand for
1634 @option{--with-mpc-lib=@/@var{mpcinstalldir}/lib} and
1635 @option{--with-mpc-include=@/@var{mpcinstalldir}/include}. If these
1636 shorthand assumptions are not correct, you can use the explicit
1637 include and lib options directly. You might also need to ensure the
1638 shared libraries can be found by the dynamic linker when building and
1639 using GCC, for example by setting the runtime shared library path
1640 variable (@env{LD_LIBRARY_PATH} on GNU/Linux and Solaris systems).
1642 These flags are applicable to the host platform only. When building
1643 a cross compiler, they will not be used to configure target libraries.
1645 @item --with-isl=@var{pathname}
1646 @itemx --with-isl-include=@var{pathname}
1647 @itemx --with-isl-lib=@var{pathname}
1648 @itemx --with-cloog=@var{pathname}
1649 @itemx --with-cloog-include=@var{pathname}
1650 @itemx --with-cloog-lib=@var{pathname}
1651 If you do not have ISL and the CLooG
1652 libraries installed in a standard location and you want to build GCC,
1653 you can explicitly specify the directory where they are installed
1654 (@samp{--with-isl=@/@var{islinstalldir}},
1655 @samp{--with-cloog=@/@var{clooginstalldir}}). The
1656 @option{--with-isl=@/@var{islinstalldir}} option is shorthand for
1657 @option{--with-isl-lib=@/@var{islinstalldir}/lib} and
1658 @option{--with-isl-include=@/@var{islinstalldir}/include}. Likewise the
1659 @option{--with-cloog=@/@var{clooginstalldir}} option is shorthand for
1660 @option{--with-cloog-lib=@/@var{clooginstalldir}/lib} and
1661 @option{--with-cloog-include=@/@var{clooginstalldir}/include}. If these
1662 shorthand assumptions are not correct, you can use the explicit
1663 include and lib options directly.
1665 These flags are applicable to the host platform only. When building
1666 a cross compiler, they will not be used to configure target libraries.
1668 @item --with-host-libstdcxx=@var{linker-args}
1669 If you are linking with a static copy of PPL, you can use this option
1670 to specify how the linker should find the standard C++ library used
1671 internally by PPL. Typical values of @var{linker-args} might be
1672 @samp{-lstdc++} or @samp{-Wl,-Bstatic,-lstdc++,-Bdynamic -lm}. If you are
1673 linking with a shared copy of PPL, you probably do not need this
1674 option; shared library dependencies will cause the linker to search
1675 for the standard C++ library automatically.
1677 @item --with-stage1-ldflags=@var{flags}
1678 This option may be used to set linker flags to be used when linking
1679 stage 1 of GCC. These are also used when linking GCC if configured with
1680 @option{--disable-bootstrap}. By default no special flags are used.
1682 @item --with-stage1-libs=@var{libs}
1683 This option may be used to set libraries to be used when linking stage 1
1684 of GCC. These are also used when linking GCC if configured with
1685 @option{--disable-bootstrap}. The default is the argument to
1686 @option{--with-host-libstdcxx}, if specified.
1688 @item --with-boot-ldflags=@var{flags}
1689 This option may be used to set linker flags to be used when linking
1690 stage 2 and later when bootstrapping GCC. If neither --with-boot-libs
1691 nor --with-host-libstdcxx is set to a value, then the default is
1692 @samp{-static-libstdc++ -static-libgcc}.
1694 @item --with-boot-libs=@var{libs}
1695 This option may be used to set libraries to be used when linking stage 2
1696 and later when bootstrapping GCC. The default is the argument to
1697 @option{--with-host-libstdcxx}, if specified.
1699 @item --with-debug-prefix-map=@var{map}
1700 Convert source directory names using @option{-fdebug-prefix-map} when
1701 building runtime libraries. @samp{@var{map}} is a space-separated
1702 list of maps of the form @samp{@var{old}=@var{new}}.
1704 @item --enable-linker-build-id
1705 Tells GCC to pass @option{--build-id} option to the linker for all final
1706 links (links performed without the @option{-r} or @option{--relocatable}
1707 option), if the linker supports it. If you specify
1708 @option{--enable-linker-build-id}, but your linker does not
1709 support @option{--build-id} option, a warning is issued and the
1710 @option{--enable-linker-build-id} option is ignored. The default is off.
1712 @item --with-linker-hash-style=@var{choice}
1713 Tells GCC to pass @option{--hash-style=@var{choice}} option to the
1714 linker for all final links. @var{choice} can be one of
1715 @samp{sysv}, @samp{gnu}, and @samp{both} where @samp{sysv} is the default.
1717 @item --enable-gnu-unique-object
1718 @itemx --disable-gnu-unique-object
1719 Tells GCC to use the gnu_unique_object relocation for C++ template
1720 static data members and inline function local statics. Enabled by
1721 default for a native toolchain with an assembler that accepts it and
1722 GLIBC 2.11 or above, otherwise disabled.
1725 @itemx --disable-lto
1726 Enable support for link-time optimization (LTO). This is enabled by
1727 default, and may be disabled using @option{--disable-lto}.
1729 @item --with-plugin-ld=@var{pathname}
1730 Enable an alternate linker to be used at link-time optimization (LTO)
1731 link time when @option{-fuse-linker-plugin} is enabled.
1732 This linker should have plugin support such as gold starting with
1733 version 2.20 or GNU ld starting with version 2.21.
1734 See @option{-fuse-linker-plugin} for details.
1736 @item --enable-canonical-system-headers
1737 @itemx --disable-canonical-system-headers
1738 Enable system header path canonicalization for @file{libcpp}. This can
1739 produce shorter header file paths in diagnostics and dependency output
1740 files, but these changed header paths may conflict with some compilation
1741 environments. Enabled by default, and may be disabled using
1742 @option{--disable-canonical-system-headers}.
1745 @subheading Cross-Compiler-Specific Options
1746 The following options only apply to building cross compilers.
1749 @item --with-sysroot
1750 @itemx --with-sysroot=@var{dir}
1751 Tells GCC to consider @var{dir} as the root of a tree that contains
1752 (a subset of) the root filesystem of the target operating system.
1753 Target system headers, libraries and run-time object files will be
1754 searched for in there. More specifically, this acts as if
1755 @option{--sysroot=@var{dir}} was added to the default options of the built
1756 compiler. The specified directory is not copied into the
1757 install tree, unlike the options @option{--with-headers} and
1758 @option{--with-libs} that this option obsoletes. The default value,
1759 in case @option{--with-sysroot} is not given an argument, is
1760 @option{$@{gcc_tooldir@}/sys-root}. If the specified directory is a
1761 subdirectory of @option{$@{exec_prefix@}}, then it will be found relative to
1762 the GCC binaries if the installation tree is moved.
1764 This option affects the system root for the compiler used to build
1765 target libraries (which runs on the build system) and the compiler newly
1766 installed with @code{make install}; it does not affect the compiler which is
1767 used to build GCC itself.
1769 If you specify the @option{--with-native-system-header-dir=@var{dirname}}
1770 option then the compiler will search that directory within @var{dirname} for
1771 native system headers rather than the default @file{/usr/include}.
1773 @item --with-build-sysroot
1774 @itemx --with-build-sysroot=@var{dir}
1775 Tells GCC to consider @var{dir} as the system root (see
1776 @option{--with-sysroot}) while building target libraries, instead of
1777 the directory specified with @option{--with-sysroot}. This option is
1778 only useful when you are already using @option{--with-sysroot}. You
1779 can use @option{--with-build-sysroot} when you are configuring with
1780 @option{--prefix} set to a directory that is different from the one in
1781 which you are installing GCC and your target libraries.
1783 This option affects the system root for the compiler used to build
1784 target libraries (which runs on the build system); it does not affect
1785 the compiler which is used to build GCC itself.
1787 If you specify the @option{--with-native-system-header-dir=@var{dirname}}
1788 option then the compiler will search that directory within @var{dirname} for
1789 native system headers rather than the default @file{/usr/include}.
1791 @item --with-headers
1792 @itemx --with-headers=@var{dir}
1793 Deprecated in favor of @option{--with-sysroot}.
1794 Specifies that target headers are available when building a cross compiler.
1795 The @var{dir} argument specifies a directory which has the target include
1796 files. These include files will be copied into the @file{gcc} install
1797 directory. @emph{This option with the @var{dir} argument is required} when
1798 building a cross compiler, if @file{@var{prefix}/@var{target}/sys-include}
1799 doesn't pre-exist. If @file{@var{prefix}/@var{target}/sys-include} does
1800 pre-exist, the @var{dir} argument may be omitted. @command{fixincludes}
1801 will be run on these files to make them compatible with GCC@.
1803 @item --without-headers
1804 Tells GCC not use any target headers from a libc when building a cross
1805 compiler. When crossing to GNU/Linux, you need the headers so GCC
1806 can build the exception handling for libgcc.
1809 @itemx --with-libs="@var{dir1} @var{dir2} @dots{} @var{dirN}"
1810 Deprecated in favor of @option{--with-sysroot}.
1811 Specifies a list of directories which contain the target runtime
1812 libraries. These libraries will be copied into the @file{gcc} install
1813 directory. If the directory list is omitted, this option has no
1817 Specifies that @samp{newlib} is
1818 being used as the target C library. This causes @code{__eprintf} to be
1819 omitted from @file{libgcc.a} on the assumption that it will be provided by
1822 @item --with-avrlibc
1823 Specifies that @samp{AVR-Libc} is
1824 being used as the target C library. This causes float support
1825 functions like @code{__addsf3} to be omitted from @file{libgcc.a} on
1826 the assumption that it will be provided by @file{libm.a}. For more
1827 technical details, cf. @uref{http://gcc.gnu.org/PR54461,,PR54461}.
1828 This option is only supported for the AVR target. It is not supported for
1829 RTEMS configurations, which currently use newlib. The option is
1830 supported since version 4.7.2 and is the default in 4.8.0 and newer.
1832 @item --with-build-time-tools=@var{dir}
1833 Specifies where to find the set of target tools (assembler, linker, etc.)
1834 that will be used while building GCC itself. This option can be useful
1835 if the directory layouts are different between the system you are building
1836 GCC on, and the system where you will deploy it.
1838 For example, on an @samp{ia64-hp-hpux} system, you may have the GNU
1839 assembler and linker in @file{/usr/bin}, and the native tools in a
1840 different path, and build a toolchain that expects to find the
1841 native tools in @file{/usr/bin}.
1843 When you use this option, you should ensure that @var{dir} includes
1844 @command{ar}, @command{as}, @command{ld}, @command{nm},
1845 @command{ranlib} and @command{strip} if necessary, and possibly
1846 @command{objdump}. Otherwise, GCC may use an inconsistent set of
1850 @subheading Java-Specific Options
1852 The following option applies to the build of the Java front end.
1855 @item --disable-libgcj
1856 Specify that the run-time libraries
1857 used by GCJ should not be built. This is useful in case you intend
1858 to use GCJ with some other run-time, or you're going to install it
1859 separately, or it just happens not to build on your particular
1860 machine. In general, if the Java front end is enabled, the GCJ
1861 libraries will be enabled too, unless they're known to not work on
1862 the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
1863 may need to port it; in this case, before modifying the top-level
1864 @file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
1865 you may use @option{--enable-libgcj} to override the default.
1869 The following options apply to building @samp{libgcj}.
1871 @subsubheading General Options
1874 @item --enable-java-maintainer-mode
1875 By default the @samp{libjava} build will not attempt to compile the
1876 @file{.java} source files to @file{.class}. Instead, it will use the
1877 @file{.class} files from the source tree. If you use this option you
1878 must have executables named @command{ecj1} and @command{gjavah} in your path
1879 for use by the build. You must use this option if you intend to
1880 modify any @file{.java} files in @file{libjava}.
1882 @item --with-java-home=@var{dirname}
1883 This @samp{libjava} option overrides the default value of the
1884 @samp{java.home} system property. It is also used to set
1885 @samp{sun.boot.class.path} to @file{@var{dirname}/lib/rt.jar}. By
1886 default @samp{java.home} is set to @file{@var{prefix}} and
1887 @samp{sun.boot.class.path} to
1888 @file{@var{datadir}/java/libgcj-@var{version}.jar}.
1890 @item --with-ecj-jar=@var{filename}
1891 This option can be used to specify the location of an external jar
1892 file containing the Eclipse Java compiler. A specially modified
1893 version of this compiler is used by @command{gcj} to parse
1894 @file{.java} source files. If this option is given, the
1895 @samp{libjava} build will create and install an @file{ecj1} executable
1896 which uses this jar file at runtime.
1898 If this option is not given, but an @file{ecj.jar} file is found in
1899 the topmost source tree at configure time, then the @samp{libgcj}
1900 build will create and install @file{ecj1}, and will also install the
1901 discovered @file{ecj.jar} into a suitable place in the install tree.
1903 If @file{ecj1} is not installed, then the user will have to supply one
1904 on his path in order for @command{gcj} to properly parse @file{.java}
1905 source files. A suitable jar is available from
1906 @uref{ftp://sourceware.org/pub/java/}.
1908 @item --disable-getenv-properties
1909 Don't set system properties from @env{GCJ_PROPERTIES}.
1911 @item --enable-hash-synchronization
1912 Use a global hash table for monitor locks. Ordinarily,
1913 @samp{libgcj}'s @samp{configure} script automatically makes
1914 the correct choice for this option for your platform. Only use
1915 this if you know you need the library to be configured differently.
1917 @item --enable-interpreter
1918 Enable the Java interpreter. The interpreter is automatically
1919 enabled by default on all platforms that support it. This option
1920 is really only useful if you want to disable the interpreter
1921 (using @option{--disable-interpreter}).
1923 @item --disable-java-net
1924 Disable java.net. This disables the native part of java.net only,
1925 using non-functional stubs for native method implementations.
1927 @item --disable-jvmpi
1928 Disable JVMPI support.
1930 @item --disable-libgcj-bc
1931 Disable BC ABI compilation of certain parts of libgcj. By default,
1932 some portions of libgcj are compiled with @option{-findirect-dispatch}
1933 and @option{-fno-indirect-classes}, allowing them to be overridden at
1936 If @option{--disable-libgcj-bc} is specified, libgcj is built without
1937 these options. This allows the compile-time linker to resolve
1938 dependencies when statically linking to libgcj. However it makes it
1939 impossible to override the affected portions of libgcj at run-time.
1941 @item --enable-reduced-reflection
1942 Build most of libgcj with @option{-freduced-reflection}. This reduces
1943 the size of libgcj at the expense of not being able to do accurate
1944 reflection on the classes it contains. This option is safe if you
1945 know that code using libgcj will never use reflection on the standard
1946 runtime classes in libgcj (including using serialization, RMI or CORBA).
1949 Enable runtime eCos target support.
1951 @item --without-libffi
1952 Don't use @samp{libffi}. This will disable the interpreter and JNI
1953 support as well, as these require @samp{libffi} to work.
1955 @item --enable-libgcj-debug
1956 Enable runtime debugging code.
1958 @item --enable-libgcj-multifile
1959 If specified, causes all @file{.java} source files to be
1960 compiled into @file{.class} files in one invocation of
1961 @samp{gcj}. This can speed up build time, but is more
1962 resource-intensive. If this option is unspecified or
1963 disabled, @samp{gcj} is invoked once for each @file{.java}
1964 file to compile into a @file{.class} file.
1966 @item --with-libiconv-prefix=DIR
1967 Search for libiconv in @file{DIR/include} and @file{DIR/lib}.
1969 @item --enable-sjlj-exceptions
1970 Force use of the @code{setjmp}/@code{longjmp}-based scheme for exceptions.
1971 @samp{configure} ordinarily picks the correct value based on the platform.
1972 Only use this option if you are sure you need a different setting.
1974 @item --with-system-zlib
1975 Use installed @samp{zlib} rather than that included with GCC@.
1977 @item --with-win32-nlsapi=ansi, unicows or unicode
1978 Indicates how MinGW @samp{libgcj} translates between UNICODE
1979 characters and the Win32 API@.
1981 @item --enable-java-home
1982 If enabled, this creates a JPackage compatible SDK environment during install.
1983 Note that if --enable-java-home is used, --with-arch-directory=ARCH must also
1986 @item --with-arch-directory=ARCH
1987 Specifies the name to use for the @file{jre/lib/ARCH} directory in the SDK
1988 environment created when --enable-java-home is passed. Typical names for this
1989 directory include i386, amd64, ia64, etc.
1991 @item --with-os-directory=DIR
1992 Specifies the OS directory for the SDK include directory. This is set to auto
1993 detect, and is typically 'linux'.
1995 @item --with-origin-name=NAME
1996 Specifies the JPackage origin name. This defaults to the 'gcj' in
1999 @item --with-arch-suffix=SUFFIX
2000 Specifies the suffix for the sdk directory. Defaults to the empty string.
2001 Examples include '.x86_64' in 'java-1.5.0-gcj-1.5.0.0.x86_64'.
2003 @item --with-jvm-root-dir=DIR
2004 Specifies where to install the SDK. Default is $(prefix)/lib/jvm.
2006 @item --with-jvm-jar-dir=DIR
2007 Specifies where to install jars. Default is $(prefix)/lib/jvm-exports.
2009 @item --with-python-dir=DIR
2010 Specifies where to install the Python modules used for aot-compile. DIR should
2011 not include the prefix used in installation. For example, if the Python modules
2012 are to be installed in /usr/lib/python2.5/site-packages, then
2013 --with-python-dir=/lib/python2.5/site-packages should be passed. If this is
2014 not specified, then the Python modules are installed in $(prefix)/share/python.
2016 @item --enable-aot-compile-rpm
2017 Adds aot-compile-rpm to the list of installed scripts.
2019 @item --enable-browser-plugin
2020 Build the gcjwebplugin web browser plugin.
2022 @item --enable-static-libjava
2023 Build static libraries in libjava. The default is to only build shared
2028 Use the single-byte @code{char} and the Win32 A functions natively,
2029 translating to and from UNICODE when using these functions. If
2030 unspecified, this is the default.
2033 Use the @code{WCHAR} and Win32 W functions natively. Adds
2034 @code{-lunicows} to @file{libgcj.spec} to link with @samp{libunicows}.
2035 @file{unicows.dll} needs to be deployed on Microsoft Windows 9X machines
2036 running built executables. @file{libunicows.a}, an open-source
2037 import library around Microsoft's @code{unicows.dll}, is obtained from
2038 @uref{http://libunicows.sourceforge.net/}, which also gives details
2039 on getting @file{unicows.dll} from Microsoft.
2042 Use the @code{WCHAR} and Win32 W functions natively. Does @emph{not}
2043 add @code{-lunicows} to @file{libgcj.spec}. The built executables will
2044 only run on Microsoft Windows NT and above.
2048 @subsubheading AWT-Specific Options
2052 Use the X Window System.
2054 @item --enable-java-awt=PEER(S)
2055 Specifies the AWT peer library or libraries to build alongside
2056 @samp{libgcj}. If this option is unspecified or disabled, AWT
2057 will be non-functional. Current valid values are @option{gtk} and
2058 @option{xlib}. Multiple libraries should be separated by a
2059 comma (i.e.@: @option{--enable-java-awt=gtk,xlib}).
2061 @item --enable-gtk-cairo
2062 Build the cairo Graphics2D implementation on GTK@.
2064 @item --enable-java-gc=TYPE
2065 Choose garbage collector. Defaults to @option{boehm} if unspecified.
2067 @item --disable-gtktest
2068 Do not try to compile and run a test GTK+ program.
2070 @item --disable-glibtest
2071 Do not try to compile and run a test GLIB program.
2073 @item --with-libart-prefix=PFX
2074 Prefix where libart is installed (optional).
2076 @item --with-libart-exec-prefix=PFX
2077 Exec prefix where libart is installed (optional).
2079 @item --disable-libarttest
2080 Do not try to compile and run a test libart program.
2084 @subsubheading Overriding @command{configure} test results
2086 Sometimes, it might be necessary to override the result of some
2087 @command{configure} test, for example in order to ease porting to a new
2088 system or work around a bug in a test. The toplevel @command{configure}
2089 script provides three variables for this:
2093 @item build_configargs
2094 @cindex @code{build_configargs}
2095 The contents of this variable is passed to all build @command{configure}
2098 @item host_configargs
2099 @cindex @code{host_configargs}
2100 The contents of this variable is passed to all host @command{configure}
2103 @item target_configargs
2104 @cindex @code{target_configargs}
2105 The contents of this variable is passed to all target @command{configure}
2110 In order to avoid shell and @command{make} quoting issues for complex
2111 overrides, you can pass a setting for @env{CONFIG_SITE} and set
2112 variables in the site file.
2119 @uref{./index.html,,Return to the GCC Installation page}
2123 @c ***Building****************************************************************
2125 @comment node-name, next, previous, up
2126 @node Building, Testing, Configuration, Installing GCC
2132 @cindex Installing GCC: Building
2134 Now that GCC is configured, you are ready to build the compiler and
2137 Some commands executed when making the compiler may fail (return a
2138 nonzero status) and be ignored by @command{make}. These failures, which
2139 are often due to files that were not found, are expected, and can safely
2142 It is normal to have compiler warnings when compiling certain files.
2143 Unless you are a GCC developer, you can generally ignore these warnings
2144 unless they cause compilation to fail. Developers should attempt to fix
2145 any warnings encountered, however they can temporarily continue past
2146 warnings-as-errors by specifying the configure flag
2147 @option{--disable-werror}.
2149 On certain old systems, defining certain environment variables such as
2150 @env{CC} can interfere with the functioning of @command{make}.
2152 If you encounter seemingly strange errors when trying to build the
2153 compiler in a directory other than the source directory, it could be
2154 because you have previously configured the compiler in the source
2155 directory. Make sure you have done all the necessary preparations.
2157 If you build GCC on a BSD system using a directory stored in an old System
2158 V file system, problems may occur in running @command{fixincludes} if the
2159 System V file system doesn't support symbolic links. These problems
2160 result in a failure to fix the declaration of @code{size_t} in
2161 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
2162 that type mismatches occur, this could be the cause.
2164 The solution is not to use such a directory for building GCC@.
2166 Similarly, when building from SVN or snapshots, or if you modify
2167 @file{*.l} files, you need the Flex lexical analyzer generator
2168 installed. If you do not modify @file{*.l} files, releases contain
2169 the Flex-generated files and you do not need Flex installed to build
2170 them. There is still one Flex-based lexical analyzer (part of the
2171 build machinery, not of GCC itself) that is used even if you only
2172 build the C front end.
2174 When building from SVN or snapshots, or if you modify Texinfo
2175 documentation, you need version 4.7 or later of Texinfo installed if you
2176 want Info documentation to be regenerated. Releases contain Info
2177 documentation pre-built for the unmodified documentation in the release.
2179 @section Building a native compiler
2181 For a native build, the default configuration is to perform
2182 a 3-stage bootstrap of the compiler when @samp{make} is invoked.
2183 This will build the entire GCC system and ensure that it compiles
2184 itself correctly. It can be disabled with the @option{--disable-bootstrap}
2185 parameter to @samp{configure}, but bootstrapping is suggested because
2186 the compiler will be tested more completely and could also have
2189 The bootstrapping process will complete the following steps:
2193 Build tools necessary to build the compiler.
2196 Perform a 3-stage bootstrap of the compiler. This includes building
2197 three times the target tools for use by the compiler such as binutils
2198 (bfd, binutils, gas, gprof, ld, and opcodes) if they have been
2199 individually linked or moved into the top level GCC source tree before
2203 Perform a comparison test of the stage2 and stage3 compilers.
2206 Build runtime libraries using the stage3 compiler from the previous step.
2210 If you are short on disk space you might consider @samp{make
2211 bootstrap-lean} instead. The sequence of compilation is the
2212 same described above, but object files from the stage1 and
2213 stage2 of the 3-stage bootstrap of the compiler are deleted as
2214 soon as they are no longer needed.
2216 If you wish to use non-default GCC flags when compiling the stage2
2217 and stage3 compilers, set @code{BOOT_CFLAGS} on the command line when
2218 doing @samp{make}. For example, if you want to save additional space
2219 during the bootstrap and in the final installation as well, you can
2220 build the compiler binaries without debugging information as in the
2221 following example. This will save roughly 40% of disk space both for
2222 the bootstrap and the final installation. (Libraries will still contain
2223 debugging information.)
2226 make BOOT_CFLAGS='-O' bootstrap
2229 You can place non-default optimization flags into @code{BOOT_CFLAGS}; they
2230 are less well tested here than the default of @samp{-g -O2}, but should
2231 still work. In a few cases, you may find that you need to specify special
2232 flags such as @option{-msoft-float} here to complete the bootstrap; or,
2233 if the native compiler miscompiles the stage1 compiler, you may need
2234 to work around this, by choosing @code{BOOT_CFLAGS} to avoid the parts
2235 of the stage1 compiler that were miscompiled, or by using @samp{make
2236 bootstrap4} to increase the number of stages of bootstrap.
2238 @code{BOOT_CFLAGS} does not apply to bootstrapped target libraries.
2239 Since these are always compiled with the compiler currently being
2240 bootstrapped, you can use @code{CFLAGS_FOR_TARGET} to modify their
2241 compilation flags, as for non-bootstrapped target libraries.
2242 Again, if the native compiler miscompiles the stage1 compiler, you may
2243 need to work around this by avoiding non-working parts of the stage1
2244 compiler. Use @code{STAGE1_TFLAGS} to this end.
2246 If you used the flag @option{--enable-languages=@dots{}} to restrict
2247 the compilers to be built, only those you've actually enabled will be
2248 built. This will of course only build those runtime libraries, for
2249 which the particular compiler has been built. Please note,
2250 that re-defining @env{LANGUAGES} when calling @samp{make}
2251 @strong{does not} work anymore!
2253 If the comparison of stage2 and stage3 fails, this normally indicates
2254 that the stage2 compiler has compiled GCC incorrectly, and is therefore
2255 a potentially serious bug which you should investigate and report. (On
2256 a few systems, meaningful comparison of object files is impossible; they
2257 always appear ``different''. If you encounter this problem, you will
2258 need to disable comparison in the @file{Makefile}.)
2260 If you do not want to bootstrap your compiler, you can configure with
2261 @option{--disable-bootstrap}. In particular cases, you may want to
2262 bootstrap your compiler even if the target system is not the same as
2263 the one you are building on: for example, you could build a
2264 @code{powerpc-unknown-linux-gnu} toolchain on a
2265 @code{powerpc64-unknown-linux-gnu} host. In this case, pass
2266 @option{--enable-bootstrap} to the configure script.
2268 @code{BUILD_CONFIG} can be used to bring in additional customization
2269 to the build. It can be set to a whitespace-separated list of names.
2270 For each such @code{NAME}, top-level @file{config/@code{NAME}.mk} will
2271 be included by the top-level @file{Makefile}, bringing in any settings
2272 it contains. The default @code{BUILD_CONFIG} can be set using the
2273 configure option @option{--with-build-config=@code{NAME}...}. Some
2274 examples of supported build configurations are:
2277 @item @samp{bootstrap-O1}
2278 Removes any @option{-O}-started option from @code{BOOT_CFLAGS}, and adds
2279 @option{-O1} to it. @samp{BUILD_CONFIG=bootstrap-O1} is equivalent to
2280 @samp{BOOT_CFLAGS='-g -O1'}.
2282 @item @samp{bootstrap-O3}
2283 Analogous to @code{bootstrap-O1}.
2285 @item @samp{bootstrap-lto}
2286 Enables Link-Time Optimization for host tools during bootstrapping.
2287 @samp{BUILD_CONFIG=bootstrap-lto} is equivalent to adding
2288 @option{-flto} to @samp{BOOT_CFLAGS}.
2290 @item @samp{bootstrap-debug}
2291 Verifies that the compiler generates the same executable code, whether
2292 or not it is asked to emit debug information. To this end, this
2293 option builds stage2 host programs without debug information, and uses
2294 @file{contrib/compare-debug} to compare them with the stripped stage3
2295 object files. If @code{BOOT_CFLAGS} is overridden so as to not enable
2296 debug information, stage2 will have it, and stage3 won't. This option
2297 is enabled by default when GCC bootstrapping is enabled, if
2298 @code{strip} can turn object files compiled with and without debug
2299 info into identical object files. In addition to better test
2300 coverage, this option makes default bootstraps faster and leaner.
2302 @item @samp{bootstrap-debug-big}
2303 Rather than comparing stripped object files, as in
2304 @code{bootstrap-debug}, this option saves internal compiler dumps
2305 during stage2 and stage3 and compares them as well, which helps catch
2306 additional potential problems, but at a great cost in terms of disk
2307 space. It can be specified in addition to @samp{bootstrap-debug}.
2309 @item @samp{bootstrap-debug-lean}
2310 This option saves disk space compared with @code{bootstrap-debug-big},
2311 but at the expense of some recompilation. Instead of saving the dumps
2312 of stage2 and stage3 until the final compare, it uses
2313 @option{-fcompare-debug} to generate, compare and remove the dumps
2314 during stage3, repeating the compilation that already took place in
2315 stage2, whose dumps were not saved.
2317 @item @samp{bootstrap-debug-lib}
2318 This option tests executable code invariance over debug information
2319 generation on target libraries, just like @code{bootstrap-debug-lean}
2320 tests it on host programs. It builds stage3 libraries with
2321 @option{-fcompare-debug}, and it can be used along with any of the
2322 @code{bootstrap-debug} options above.
2324 There aren't @code{-lean} or @code{-big} counterparts to this option
2325 because most libraries are only build in stage3, so bootstrap compares
2326 would not get significant coverage. Moreover, the few libraries built
2327 in stage2 are used in stage3 host programs, so we wouldn't want to
2328 compile stage2 libraries with different options for comparison purposes.
2330 @item @samp{bootstrap-debug-ckovw}
2331 Arranges for error messages to be issued if the compiler built on any
2332 stage is run without the option @option{-fcompare-debug}. This is
2333 useful to verify the full @option{-fcompare-debug} testing coverage. It
2334 must be used along with @code{bootstrap-debug-lean} and
2335 @code{bootstrap-debug-lib}.
2337 @item @samp{bootstrap-time}
2338 Arranges for the run time of each program started by the GCC driver,
2339 built in any stage, to be logged to @file{time.log}, in the top level of
2344 @section Building a cross compiler
2346 When building a cross compiler, it is not generally possible to do a
2347 3-stage bootstrap of the compiler. This makes for an interesting problem
2348 as parts of GCC can only be built with GCC@.
2350 To build a cross compiler, we recommend first building and installing a
2351 native compiler. You can then use the native GCC compiler to build the
2352 cross compiler. The installed native compiler needs to be GCC version
2355 If the cross compiler is to be built with support for the Java
2356 programming language and the ability to compile .java source files is
2357 desired, the installed native compiler used to build the cross
2358 compiler needs to be the same GCC version as the cross compiler. In
2359 addition the cross compiler needs to be configured with
2360 @option{--with-ecj-jar=@dots{}}.
2362 Assuming you have already installed a native copy of GCC and configured
2363 your cross compiler, issue the command @command{make}, which performs the
2368 Build host tools necessary to build the compiler.
2371 Build target tools for use by the compiler such as binutils (bfd,
2372 binutils, gas, gprof, ld, and opcodes)
2373 if they have been individually linked or moved into the top level GCC source
2374 tree before configuring.
2377 Build the compiler (single stage only).
2380 Build runtime libraries using the compiler from the previous step.
2383 Note that if an error occurs in any step the make process will exit.
2385 If you are not building GNU binutils in the same source tree as GCC,
2386 you will need a cross-assembler and cross-linker installed before
2387 configuring GCC@. Put them in the directory
2388 @file{@var{prefix}/@var{target}/bin}. Here is a table of the tools
2389 you should put in this directory:
2393 This should be the cross-assembler.
2396 This should be the cross-linker.
2399 This should be the cross-archiver: a program which can manipulate
2400 archive files (linker libraries) in the target machine's format.
2403 This should be a program to construct a symbol table in an archive file.
2406 The installation of GCC will find these programs in that directory,
2407 and copy or link them to the proper place to for the cross-compiler to
2408 find them when run later.
2410 The easiest way to provide these files is to build the Binutils package.
2411 Configure it with the same @option{--host} and @option{--target}
2412 options that you use for configuring GCC, then build and install
2413 them. They install their executables automatically into the proper
2414 directory. Alas, they do not support all the targets that GCC
2417 If you are not building a C library in the same source tree as GCC,
2418 you should also provide the target libraries and headers before
2419 configuring GCC, specifying the directories with
2420 @option{--with-sysroot} or @option{--with-headers} and
2421 @option{--with-libs}. Many targets also require ``start files'' such
2422 as @file{crt0.o} and
2423 @file{crtn.o} which are linked into each executable. There may be several
2424 alternatives for @file{crt0.o}, for use with profiling or other
2425 compilation options. Check your target's definition of
2426 @code{STARTFILE_SPEC} to find out what start files it uses.
2428 @section Building in parallel
2430 GNU Make 3.80 and above, which is necessary to build GCC, support
2431 building in parallel. To activate this, you can use @samp{make -j 2}
2432 instead of @samp{make}. You can also specify a bigger number, and
2433 in most cases using a value greater than the number of processors in
2434 your machine will result in fewer and shorter I/O latency hits, thus
2435 improving overall throughput; this is especially true for slow drives
2436 and network filesystems.
2438 @section Building the Ada compiler
2440 In order to build GNAT, the Ada compiler, you need a working GNAT
2441 compiler (GCC version 4.0 or later).
2442 This includes GNAT tools such as @command{gnatmake} and
2443 @command{gnatlink}, since the Ada front end is written in Ada and
2444 uses some GNAT-specific extensions.
2446 In order to build a cross compiler, it is suggested to install
2447 the new compiler as native first, and then use it to build the cross
2450 @command{configure} does not test whether the GNAT installation works
2451 and has a sufficiently recent version; if too old a GNAT version is
2452 installed, the build will fail unless @option{--enable-languages} is
2453 used to disable building the Ada front end.
2455 @env{ADA_INCLUDE_PATH} and @env{ADA_OBJECT_PATH} environment variables
2456 must not be set when building the Ada compiler, the Ada tools, or the
2457 Ada runtime libraries. You can check that your build environment is clean
2458 by verifying that @samp{gnatls -v} lists only one explicit path in each
2461 @section Building with profile feedback
2463 It is possible to use profile feedback to optimize the compiler itself. This
2464 should result in a faster compiler binary. Experiments done on x86 using gcc
2465 3.3 showed approximately 7 percent speedup on compiling C programs. To
2466 bootstrap the compiler with profile feedback, use @code{make profiledbootstrap}.
2468 When @samp{make profiledbootstrap} is run, it will first build a @code{stage1}
2469 compiler. This compiler is used to build a @code{stageprofile} compiler
2470 instrumented to collect execution counts of instruction and branch
2471 probabilities. Then runtime libraries are compiled with profile collected.
2472 Finally a @code{stagefeedback} compiler is built using the information collected.
2474 Unlike standard bootstrap, several additional restrictions apply. The
2475 compiler used to build @code{stage1} needs to support a 64-bit integral type.
2476 It is recommended to only use GCC for this. Also parallel make is currently
2477 not supported since collisions in profile collecting may occur.
2484 @uref{./index.html,,Return to the GCC Installation page}
2488 @c ***Testing*****************************************************************
2490 @comment node-name, next, previous, up
2491 @node Testing, Final install, Building, Installing GCC
2495 @chapter Installing GCC: Testing
2498 @cindex Installing GCC: Testing
2501 Before you install GCC, we encourage you to run the testsuites and to
2502 compare your results with results from a similar configuration that have
2503 been submitted to the
2504 @uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
2505 Some of these archived results are linked from the build status lists
2506 at @uref{http://gcc.gnu.org/buildstat.html}, although not everyone who
2507 reports a successful build runs the testsuites and submits the results.
2508 This step is optional and may require you to download additional software,
2509 but it can give you confidence in your new GCC installation or point out
2510 problems before you install and start using your new GCC@.
2512 First, you must have @uref{download.html,,downloaded the testsuites}.
2513 These are part of the full distribution, but if you downloaded the
2514 ``core'' compiler plus any front ends, you must download the testsuites
2517 Second, you must have the testing tools installed. This includes
2518 @uref{http://www.gnu.org/software/dejagnu/,,DejaGnu}, Tcl, and Expect;
2519 the DejaGnu site has links to these.
2521 If the directories where @command{runtest} and @command{expect} were
2522 installed are not in the @env{PATH}, you may need to set the following
2523 environment variables appropriately, as in the following example (which
2524 assumes that DejaGnu has been installed under @file{/usr/local}):
2527 TCL_LIBRARY = /usr/local/share/tcl8.0
2528 DEJAGNULIBS = /usr/local/share/dejagnu
2531 (On systems such as Cygwin, these paths are required to be actual
2532 paths, not mounts or links; presumably this is due to some lack of
2533 portability in the DejaGnu code.)
2536 Finally, you can run the testsuite (which may take a long time):
2538 cd @var{objdir}; make -k check
2541 This will test various components of GCC, such as compiler
2542 front ends and runtime libraries. While running the testsuite, DejaGnu
2543 might emit some harmless messages resembling
2544 @samp{WARNING: Couldn't find the global config file.} or
2545 @samp{WARNING: Couldn't find tool init file} that can be ignored.
2547 If you are testing a cross-compiler, you may want to run the testsuite
2548 on a simulator as described at @uref{http://gcc.gnu.org/simtest-howto.html}.
2550 @section How can you run the testsuite on selected tests?
2552 In order to run sets of tests selectively, there are targets
2553 @samp{make check-gcc} and language specific @samp{make check-c},
2554 @samp{make check-c++}, @samp{make check-fortran}, @samp{make check-java},
2555 @samp{make check-ada}, @samp{make check-objc}, @samp{make check-obj-c++},
2556 @samp{make check-lto}
2557 in the @file{gcc} subdirectory of the object directory. You can also
2558 just run @samp{make check} in a subdirectory of the object directory.
2561 A more selective way to just run all @command{gcc} execute tests in the
2565 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
2568 Likewise, in order to run only the @command{g++} ``old-deja'' tests in
2569 the testsuite with filenames matching @samp{9805*}, you would use
2572 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
2575 The @file{*.exp} files are located in the testsuite directories of the GCC
2576 source, the most important ones being @file{compile.exp},
2577 @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
2578 To get a list of the possible @file{*.exp} files, pipe the
2579 output of @samp{make check} into a file and look at the
2580 @samp{Running @dots{} .exp} lines.
2582 @section Passing options and running multiple testsuites
2584 You can pass multiple options to the testsuite using the
2585 @samp{--target_board} option of DejaGNU, either passed as part of
2586 @samp{RUNTESTFLAGS}, or directly to @command{runtest} if you prefer to
2587 work outside the makefiles. For example,
2590 make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fmerge-constants"
2593 will run the standard @command{g++} testsuites (``unix'' is the target name
2594 for a standard native testsuite situation), passing
2595 @samp{-O3 -fmerge-constants} to the compiler on every test, i.e.,
2596 slashes separate options.
2598 You can run the testsuites multiple times using combinations of options
2599 with a syntax similar to the brace expansion of popular shells:
2602 @dots{}"--target_board=arm-sim\@{-mhard-float,-msoft-float\@}\@{-O1,-O2,-O3,\@}"
2605 (Note the empty option caused by the trailing comma in the final group.)
2606 The following will run each testsuite eight times using the @samp{arm-sim}
2607 target, as if you had specified all possible combinations yourself:
2610 --target_board='arm-sim/-mhard-float/-O1 \
2611 arm-sim/-mhard-float/-O2 \
2612 arm-sim/-mhard-float/-O3 \
2613 arm-sim/-mhard-float \
2614 arm-sim/-msoft-float/-O1 \
2615 arm-sim/-msoft-float/-O2 \
2616 arm-sim/-msoft-float/-O3 \
2617 arm-sim/-msoft-float'
2620 They can be combined as many times as you wish, in arbitrary ways. This
2624 @dots{}"--target_board=unix/-Wextra\@{-O3,-fno-strength\@}\@{-fomit-frame,\@}"
2627 will generate four combinations, all involving @samp{-Wextra}.
2629 The disadvantage to this method is that the testsuites are run in serial,
2630 which is a waste on multiprocessor systems. For users with GNU Make and
2631 a shell which performs brace expansion, you can run the testsuites in
2632 parallel by having the shell perform the combinations and @command{make}
2633 do the parallel runs. Instead of using @samp{--target_board}, use a
2634 special makefile target:
2637 make -j@var{N} check-@var{testsuite}//@var{test-target}/@var{option1}/@var{option2}/@dots{}
2643 make -j3 check-gcc//sh-hms-sim/@{-m1,-m2,-m3,-m3e,-m4@}/@{,-nofpu@}
2646 will run three concurrent ``make-gcc'' testsuites, eventually testing all
2647 ten combinations as described above. Note that this is currently only
2648 supported in the @file{gcc} subdirectory. (To see how this works, try
2649 typing @command{echo} before the example given here.)
2652 @section Additional testing for Java Class Libraries
2654 The Java runtime tests can be executed via @samp{make check}
2655 in the @file{@var{target}/libjava/testsuite} directory in
2658 The @uref{http://sourceware.org/mauve/,,Mauve Project} provides
2659 a suite of tests for the Java Class Libraries. This suite can be run
2660 as part of libgcj testing by placing the Mauve tree within the libjava
2661 testsuite at @file{libjava/testsuite/libjava.mauve/mauve}, or by
2662 specifying the location of that tree when invoking @samp{make}, as in
2663 @samp{make MAUVEDIR=~/mauve check}.
2665 @section How to interpret test results
2667 The result of running the testsuite are various @file{*.sum} and @file{*.log}
2668 files in the testsuite subdirectories. The @file{*.log} files contain a
2669 detailed log of the compiler invocations and the corresponding
2670 results, the @file{*.sum} files summarize the results. These summaries
2671 contain status codes for all tests:
2675 PASS: the test passed as expected
2677 XPASS: the test unexpectedly passed
2679 FAIL: the test unexpectedly failed
2681 XFAIL: the test failed as expected
2683 UNSUPPORTED: the test is not supported on this platform
2685 ERROR: the testsuite detected an error
2687 WARNING: the testsuite detected a possible problem
2690 It is normal for some tests to report unexpected failures. At the
2691 current time the testing harness does not allow fine grained control
2692 over whether or not a test is expected to fail. This problem should
2693 be fixed in future releases.
2696 @section Submitting test results
2698 If you want to report the results to the GCC project, use the
2699 @file{contrib/test_summary} shell script. Start it in the @var{objdir} with
2702 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
2703 -m gcc-testresults@@gcc.gnu.org |sh
2706 This script uses the @command{Mail} program to send the results, so
2707 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
2708 prepended to the testsuite summary and should contain any special
2709 remarks you have on your results or your build environment. Please
2710 do not edit the testsuite result block or the subject line, as these
2711 messages may be automatically processed.
2718 @uref{./index.html,,Return to the GCC Installation page}
2722 @c ***Final install***********************************************************
2724 @comment node-name, next, previous, up
2725 @node Final install, , Testing, Installing GCC
2727 @ifset finalinstallhtml
2729 @chapter Installing GCC: Final installation
2732 Now that GCC has been built (and optionally tested), you can install it with
2734 cd @var{objdir} && make install
2737 We strongly recommend to install into a target directory where there is
2738 no previous version of GCC present. Also, the GNAT runtime should not
2739 be stripped, as this would break certain features of the debugger that
2740 depend on this debugging information (catching Ada exceptions for
2743 That step completes the installation of GCC; user level binaries can
2744 be found in @file{@var{prefix}/bin} where @var{prefix} is the value
2745 you specified with the @option{--prefix} to configure (or
2746 @file{/usr/local} by default). (If you specified @option{--bindir},
2747 that directory will be used instead; otherwise, if you specified
2748 @option{--exec-prefix}, @file{@var{exec-prefix}/bin} will be used.)
2749 Headers for the C++ and Java libraries are installed in
2750 @file{@var{prefix}/include}; libraries in @file{@var{libdir}}
2751 (normally @file{@var{prefix}/lib}); internal parts of the compiler in
2752 @file{@var{libdir}/gcc} and @file{@var{libexecdir}/gcc}; documentation
2753 in info format in @file{@var{infodir}} (normally
2754 @file{@var{prefix}/info}).
2756 When installing cross-compilers, GCC's executables
2757 are not only installed into @file{@var{bindir}}, that
2758 is, @file{@var{exec-prefix}/bin}, but additionally into
2759 @file{@var{exec-prefix}/@var{target-alias}/bin}, if that directory
2760 exists. Typically, such @dfn{tooldirs} hold target-specific
2761 binutils, including assembler and linker.
2763 Installation into a temporary staging area or into a @command{chroot}
2764 jail can be achieved with the command
2767 make DESTDIR=@var{path-to-rootdir} install
2771 where @var{path-to-rootdir} is the absolute path of
2772 a directory relative to which all installation paths will be
2773 interpreted. Note that the directory specified by @code{DESTDIR}
2774 need not exist yet; it will be created if necessary.
2776 There is a subtle point with tooldirs and @code{DESTDIR}:
2777 If you relocate a cross-compiler installation with
2778 e.g.@: @samp{DESTDIR=@var{rootdir}}, then the directory
2779 @file{@var{rootdir}/@var{exec-prefix}/@var{target-alias}/bin} will
2780 be filled with duplicated GCC executables only if it already exists,
2781 it will not be created otherwise. This is regarded as a feature,
2782 not as a bug, because it gives slightly more control to the packagers
2783 using the @code{DESTDIR} feature.
2785 You can install stripped programs and libraries with
2791 If you are bootstrapping a released version of GCC then please
2792 quickly review the build status page for your release, available from
2793 @uref{http://gcc.gnu.org/buildstat.html}.
2794 If your system is not listed for the version of GCC that you built,
2796 @email{gcc@@gcc.gnu.org} indicating
2797 that you successfully built and installed GCC@.
2798 Include the following information:
2802 Output from running @file{@var{srcdir}/config.guess}. Do not send
2803 that file itself, just the one-line output from running it.
2806 The output of @samp{gcc -v} for your newly installed @command{gcc}.
2807 This tells us which version of GCC you built and the options you passed to
2811 Whether you enabled all languages or a subset of them. If you used a
2812 full distribution then this information is part of the configure
2813 options in the output of @samp{gcc -v}, but if you downloaded the
2814 ``core'' compiler plus additional front ends then it isn't apparent
2815 which ones you built unless you tell us about it.
2818 If the build was for GNU/Linux, also include:
2821 The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
2822 this information should be available from @file{/etc/issue}.
2825 The version of the Linux kernel, available from @samp{uname --version}
2829 The version of glibc you used; for RPM-based systems like Red Hat,
2830 Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
2831 and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
2833 For other systems, you can include similar information if you think it is
2837 Any other information that you think would be useful to people building
2838 GCC on the same configuration. The new entry in the build status list
2839 will include a link to the archived copy of your message.
2842 We'd also like to know if the
2844 @ref{Specific, host/target specific installation notes}
2847 @uref{specific.html,,host/target specific installation notes}
2849 didn't include your host/target information or if that information is
2850 incomplete or out of date. Send a note to
2851 @email{gcc@@gcc.gnu.org} detailing how the information should be changed.
2853 If you find a bug, please report it following the
2854 @uref{../bugs/,,bug reporting guidelines}.
2856 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
2857 dvi}. You will need to have @command{texi2dvi} (version at least 4.7)
2858 and @TeX{} installed. This creates a number of @file{.dvi} files in
2859 subdirectories of @file{@var{objdir}}; these may be converted for
2860 printing with programs such as @command{dvips}. Alternately, by using
2861 @samp{make pdf} in place of @samp{make dvi}, you can create documentation
2862 in the form of @file{.pdf} files; this requires @command{texi2pdf}, which
2863 is included with Texinfo version 4.8 and later. You can also
2864 @uref{http://shop.fsf.org/,,buy printed manuals from the
2865 Free Software Foundation}, though such manuals may not be for the most
2866 recent version of GCC@.
2868 If you would like to generate online HTML documentation, do @samp{cd
2869 @var{objdir}; make html} and HTML will be generated for the gcc manuals in
2870 @file{@var{objdir}/gcc/HTML}.
2877 @uref{./index.html,,Return to the GCC Installation page}
2881 @c ***Binaries****************************************************************
2883 @comment node-name, next, previous, up
2884 @node Binaries, Specific, Installing GCC, Top
2888 @chapter Installing GCC: Binaries
2891 @cindex Installing GCC: Binaries
2893 We are often asked about pre-compiled versions of GCC@. While we cannot
2894 provide these for all platforms, below you'll find links to binaries for
2895 various platforms where creating them by yourself is not easy due to various
2898 Please note that we did not create these binaries, nor do we
2899 support them. If you have any problems installing them, please
2900 contact their makers.
2907 @uref{http://www.bullfreeware.com,,Bull's Freeware and Shareware Archive for AIX};
2910 @uref{http://pware.hvcc.edu,,Hudson Valley Community College Open Source Software for IBM System p};
2913 @uref{http://www.perzl.org/aix/,,AIX 5L and 6 Open Source Packages}.
2917 DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}.
2920 Renesas H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
2921 Development Tools for the Renesas H8/300[HS] Series}.
2927 @uref{http://hpux.connect.org.uk/,,HP-UX Porting Center};
2930 @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}.
2934 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
2935 OpenServer/Unixware}.
2938 Solaris 2 (SPARC, Intel):
2941 @uref{http://www.sunfreeware.com/,,Sunfreeware}
2944 @uref{http://www.blastwave.org/,,Blastwave}
2947 @uref{http://www.opencsw.org/,,OpenCSW}
2950 @uref{http://jupiterrise.com/tgcware/,,TGCware}
2957 The @uref{http://sourceware.org/cygwin/,,Cygwin} project;
2959 The @uref{http://www.mingw.org/,,MinGW} project.
2963 @uref{ftp://ftp.thewrittenword.com/packages/by-name/,,The
2964 Written Word} offers binaries for
2965 AIX 4.3.3, 5.1 and 5.2,
2967 HP-UX 10.20, 11.00, and 11.11, and
2968 Solaris/SPARC 2.5.1, 2.6, 7, 8, 9 and 10.
2971 @uref{http://www.openpkg.org/,,OpenPKG} offers binaries for quite a
2972 number of platforms.
2975 The @uref{http://gcc.gnu.org/wiki/GFortranBinaries,,GFortran Wiki} has
2976 links to GNU Fortran binaries for several platforms.
2984 @uref{./index.html,,Return to the GCC Installation page}
2988 @c ***Specific****************************************************************
2990 @comment node-name, next, previous, up
2991 @node Specific, Old, Binaries, Top
2995 @chapter Host/target specific installation notes for GCC
2998 @cindex Specific installation notes
2999 @cindex Target specific installation
3000 @cindex Host specific installation
3001 @cindex Target specific installation notes
3003 Please read this document carefully @emph{before} installing the
3004 GNU Compiler Collection on your machine.
3006 Note that this list of install notes is @emph{not} a list of supported
3007 hosts or targets. Not all supported hosts and targets are listed
3008 here, only the ones that require host-specific or target-specific
3009 information have to.
3014 @uref{#alpha-x-x,,alpha*-*-*}
3016 @uref{#alpha-dec-osf51,,alpha*-dec-osf5.1}
3018 @uref{#amd64-x-solaris210,,amd64-*-solaris2.10}
3020 @uref{#arm-x-eabi,,arm-*-eabi}
3024 @uref{#bfin,,Blackfin}
3028 @uref{#x-x-freebsd,,*-*-freebsd*}
3030 @uref{#h8300-hms,,h8300-hms}
3032 @uref{#hppa-hp-hpux,,hppa*-hp-hpux*}
3034 @uref{#hppa-hp-hpux10,,hppa*-hp-hpux10}
3036 @uref{#hppa-hp-hpux11,,hppa*-hp-hpux11}
3038 @uref{#x-x-linux-gnu,,*-*-linux-gnu}
3040 @uref{#ix86-x-linux,,i?86-*-linux*}
3042 @uref{#ix86-x-solaris289,,i?86-*-solaris2.9}
3044 @uref{#ix86-x-solaris210,,i?86-*-solaris2.10}
3046 @uref{#ia64-x-linux,,ia64-*-linux}
3048 @uref{#ia64-x-hpux,,ia64-*-hpux*}
3050 @uref{#x-ibm-aix,,*-ibm-aix*}
3052 @uref{#iq2000-x-elf,,iq2000-*-elf}
3054 @uref{#lm32-x-elf,,lm32-*-elf}
3056 @uref{#lm32-x-uclinux,,lm32-*-uclinux}
3058 @uref{#m32c-x-elf,,m32c-*-elf}
3060 @uref{#m32r-x-elf,,m32r-*-elf}
3062 @uref{#m68k-x-x,,m68k-*-*}
3064 @uref{#m68k-uclinux,,m68k-uclinux}
3066 @uref{#mep-x-elf,,mep-*-elf}
3068 @uref{#microblaze-x-elf,,microblaze-*-elf}
3070 @uref{#mips-x-x,,mips-*-*}
3072 @uref{#mips-sgi-irix5,,mips-sgi-irix5}
3074 @uref{#mips-sgi-irix6,,mips-sgi-irix6}
3076 @uref{#powerpc-x-x,,powerpc*-*-*}
3078 @uref{#powerpc-x-darwin,,powerpc-*-darwin*}
3080 @uref{#powerpc-x-elf,,powerpc-*-elf}
3082 @uref{#powerpc-x-linux-gnu,,powerpc*-*-linux-gnu*}
3084 @uref{#powerpc-x-netbsd,,powerpc-*-netbsd*}
3086 @uref{#powerpc-x-eabisim,,powerpc-*-eabisim}
3088 @uref{#powerpc-x-eabi,,powerpc-*-eabi}
3090 @uref{#powerpcle-x-elf,,powerpcle-*-elf}
3092 @uref{#powerpcle-x-eabisim,,powerpcle-*-eabisim}
3094 @uref{#powerpcle-x-eabi,,powerpcle-*-eabi}
3096 @uref{#s390-x-linux,,s390-*-linux*}
3098 @uref{#s390x-x-linux,,s390x-*-linux*}
3100 @uref{#s390x-ibm-tpf,,s390x-ibm-tpf*}
3102 @uref{#x-x-solaris2,,*-*-solaris2*}
3104 @uref{#sparc-x-x,,sparc*-*-*}
3106 @uref{#sparc-sun-solaris2,,sparc-sun-solaris2*}
3108 @uref{#sparc-sun-solaris210,,sparc-sun-solaris2.10}
3110 @uref{#sparc-x-linux,,sparc-*-linux*}
3112 @uref{#sparc64-x-solaris2,,sparc64-*-solaris2*}
3114 @uref{#sparcv9-x-solaris2,,sparcv9-*-solaris2*}
3116 @uref{#c6x-x-x,,c6x-*-*}
3118 @uref{#tilegx-x-linux,,tilegx-*-linux*}
3120 @uref{#tilepro-x-linux,,tilepro-*-linux*}
3122 @uref{#x-x-vxworks,,*-*-vxworks*}
3124 @uref{#x86-64-x-x,,x86_64-*-*, amd64-*-*}
3126 @uref{#x86-64-x-solaris210,,x86_64-*-solaris2.1[0-9]*}
3128 @uref{#xtensa-x-elf,,xtensa*-*-elf}
3130 @uref{#xtensa-x-linux,,xtensa*-*-linux*}
3132 @uref{#windows,,Microsoft Windows}
3134 @uref{#x-x-cygwin,,*-*-cygwin}
3136 @uref{#x-x-interix,,*-*-interix}
3138 @uref{#x-x-mingw32,,*-*-mingw32}
3142 @uref{#older,,Older systems}
3147 @uref{#elf,,all ELF targets} (SVR4, Solaris 2, etc.)
3153 <!-- -------- host/target specific issues start here ---------------- -->
3156 @heading @anchor{alpha-x-x}alpha*-*-*
3158 This section contains general configuration information for all
3159 alpha-based platforms using ELF (in particular, ignore this section for
3160 DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
3161 section, please read all other sections that match your target.
3163 We require binutils 2.11.2 or newer.
3164 Previous binutils releases had a number of problems with DWARF 2
3165 debugging information, not the least of which is incorrect linking of
3171 @heading @anchor{alpha-dec-osf51}alpha*-dec-osf5.1
3172 Systems using processors that implement the DEC Alpha architecture and
3173 are running the DEC/Compaq/HP Unix (DEC OSF/1, Digital UNIX, or Compaq/HP
3174 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
3176 Support for Tru64 UNIX V5.1 has been removed in GCC 4.8. As of GCC 4.6,
3177 support for Tru64 UNIX V4.0 and V5.0 has been removed. As of GCC 3.2,
3178 versions before @code{alpha*-dec-osf4} are no longer supported. (These
3179 are the versions which identify themselves as DEC OSF/1.)
3184 @heading @anchor{amd64-x-solaris210}amd64-*-solaris2.1[0-9]*
3186 This is a synonym for @samp{x86_64-*-solaris2.1[0-9]*}.
3191 @heading @anchor{arm-x-eabi}arm-*-eabi
3192 ARM-family processors. Subtargets that use the ELF object format
3193 require GNU binutils 2.13 or newer. Such subtargets include:
3194 @code{arm-*-netbsdelf}, @code{arm-*-*linux-*}
3195 and @code{arm-*-rtemseabi}.
3200 @heading @anchor{avr}avr
3202 ATMEL AVR-family micro controllers. These are used in embedded
3203 applications. There are no standard Unix configurations.
3205 @xref{AVR Options,, AVR Options, gcc, Using the GNU Compiler
3209 See ``AVR Options'' in the main manual
3211 for the list of supported MCU types.
3213 Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
3215 Further installation notes and other useful information about AVR tools
3216 can also be obtained from:
3220 @uref{http://www.nongnu.org/avr/,,http://www.nongnu.org/avr/}
3222 @uref{http://www.amelek.gda.pl/avr/,,http://www.amelek.gda.pl/avr/}
3225 We @emph{strongly} recommend using binutils 2.13 or newer.
3227 The following error:
3229 Error: register required
3232 indicates that you should upgrade to a newer version of the binutils.
3237 @heading @anchor{bfin}Blackfin
3239 The Blackfin processor, an Analog Devices DSP.
3241 @xref{Blackfin Options,, Blackfin Options, gcc, Using the GNU Compiler
3245 See ``Blackfin Options'' in the main manual
3248 More information, and a version of binutils with support for this processor,
3249 is available at @uref{http://blackfin.uclinux.org}
3254 @heading @anchor{cr16}CR16
3256 The CR16 CompactRISC architecture is a 16-bit architecture. This architecture is
3257 used in embedded applications.
3260 @xref{CR16 Options,, CR16 Options, gcc, Using and Porting the GNU Compiler
3265 See ``CR16 Options'' in the main manual for a list of CR16-specific options.
3268 Use @samp{configure --target=cr16-elf --enable-languages=c,c++} to configure
3269 GCC@ for building a CR16 elf cross-compiler.
3271 Use @samp{configure --target=cr16-uclinux --enable-languages=c,c++} to configure
3272 GCC@ for building a CR16 uclinux cross-compiler.
3277 @heading @anchor{cris}CRIS
3279 CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
3280 series. These are used in embedded applications.
3283 @xref{CRIS Options,, CRIS Options, gcc, Using the GNU Compiler
3287 See ``CRIS Options'' in the main manual
3289 for a list of CRIS-specific options.
3291 There are a few different CRIS targets:
3294 Mainly for monolithic embedded systems. Includes a multilib for the
3295 @samp{v10} core used in @samp{ETRAX 100 LX}.
3296 @item cris-axis-linux-gnu
3297 A GNU/Linux port for the CRIS architecture, currently targeting
3298 @samp{ETRAX 100 LX} by default.
3301 For @code{cris-axis-elf} you need binutils 2.11
3302 or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer.
3304 Pre-packaged tools can be obtained from
3305 @uref{ftp://ftp.axis.com/@/pub/@/axis/@/tools/@/cris/@/compiler-kit/}. More
3306 information about this platform is available at
3307 @uref{http://developer.axis.com/}.
3312 @heading @anchor{dos}DOS
3314 Please have a look at the @uref{binaries.html,,binaries page}.
3316 You cannot install GCC by itself on MSDOS; it will not compile under
3317 any MSDOS compiler except itself. You need to get the complete
3318 compilation package DJGPP, which includes binaries as well as sources,
3319 and includes all the necessary compilation tools and libraries.
3324 @heading @anchor{epiphany-x-elf}epiphany-*-elf
3326 This configuration is intended for embedded systems.
3331 @heading @anchor{x-x-freebsd}*-*-freebsd*
3333 Support for FreeBSD 1 was discontinued in GCC 3.2. Support for
3334 FreeBSD 2 (and any mutant a.out variants of FreeBSD 3) was
3335 discontinued in GCC 4.0.
3337 In order to better utilize FreeBSD base system functionality and match
3338 the configuration of the system compiler, GCC 4.5 and above as well as
3339 GCC 4.4 past 2010-06-20 leverage SSP support in libc (which is present
3340 on FreeBSD 7 or later) and the use of @code{__cxa_atexit} by default
3341 (on FreeBSD 6 or later). The use of @code{dl_iterate_phdr} inside
3342 @file{libgcc_s.so.1} and boehm-gc (on FreeBSD 7 or later) is enabled
3343 by GCC 4.5 and above.
3345 We support FreeBSD using the ELF file format with DWARF 2 debugging
3346 for all CPU architectures. You may use @option{-gstabs} instead of
3347 @option{-g}, if you really want the old debugging format. There are
3348 no known issues with mixing object files and libraries with different
3349 debugging formats. Otherwise, this release of GCC should now match
3350 more of the configuration used in the stock FreeBSD configuration of
3351 GCC@. In particular, @option{--enable-threads} is now configured by
3352 default. However, as a general user, do not attempt to replace the
3353 system compiler with this release. Known to bootstrap and check with
3354 good results on FreeBSD 7.2-STABLE@. In the past, known to bootstrap
3355 and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4,
3356 4.5, 4.8, 4.9 and 5-CURRENT@.
3358 The version of binutils installed in @file{/usr/bin} probably works
3359 with this release of GCC@. Bootstrapping against the latest GNU
3360 binutils and/or the version found in @file{/usr/ports/devel/binutils} has
3361 been known to enable additional features and improve overall testsuite
3362 results. However, it is currently known that boehm-gc (which itself
3363 is required for java) may not configure properly on FreeBSD prior to
3364 the FreeBSD 7.0 release with GNU binutils after 2.16.1.
3369 @heading @anchor{h8300-hms}h8300-hms
3370 Renesas H8/300 series of processors.
3372 Please have a look at the @uref{binaries.html,,binaries page}.
3374 The calling convention and structure layout has changed in release 2.6.
3375 All code must be recompiled. The calling convention now passes the
3376 first three arguments in function calls in registers. Structures are no
3377 longer a multiple of 2 bytes.
3382 @heading @anchor{hppa-hp-hpux}hppa*-hp-hpux*
3383 Support for HP-UX version 9 and older was discontinued in GCC 3.4.
3385 We require using gas/binutils on all hppa platforms. Version 2.19 or
3386 later is recommended.
3388 It may be helpful to configure GCC with the
3389 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
3390 @option{--with-as=@dots{}} options to ensure that GCC can find GAS@.
3392 The HP assembler should not be used with GCC. It is rarely tested and may
3393 not work. It shouldn't be used with any languages other than C due to its
3396 Specifically, @option{-g} does not work (HP-UX uses a peculiar debugging
3397 format which GCC does not know about). It also inserts timestamps
3398 into each object file it creates, causing the 3-stage comparison test to
3399 fail during a bootstrap. You should be able to continue by saying
3400 @samp{make all-host all-target} after getting the failure from @samp{make}.
3402 Various GCC features are not supported. For example, it does not support weak
3403 symbols or alias definitions. As a result, explicit template instantiations
3404 are required when using C++. This makes it difficult if not impossible to
3405 build many C++ applications.
3407 There are two default scheduling models for instructions. These are
3408 PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
3409 architecture specified for the target machine when configuring.
3410 PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
3411 the target is a @samp{hppa1*} machine.
3413 The PROCESSOR_8000 model is not well suited to older processors. Thus,
3414 it is important to completely specify the machine architecture when
3415 configuring if you want a model other than PROCESSOR_8000. The macro
3416 TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
3417 default scheduling model is desired.
3419 As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10
3420 through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later.
3421 This namespace change might cause problems when bootstrapping with
3422 an earlier version of GCC or the HP compiler as essentially the same
3423 namespace is required for an entire build. This problem can be avoided
3424 in a number of ways. With HP cc, @env{UNIX_STD} can be set to @samp{95}
3425 or @samp{98}. Another way is to add an appropriate set of predefines
3426 to @env{CC}. The description for the @option{munix=} option contains
3427 a list of the predefines used with each standard.
3429 More specific information to @samp{hppa*-hp-hpux*} targets follows.
3434 @heading @anchor{hppa-hp-hpux10}hppa*-hp-hpux10
3436 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
3437 @code{PHCO_19798} from HP@.
3439 The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces are
3440 used for one-only code and data. This resolves many of the previous
3441 problems in using C++ on this target. However, the ABI is not compatible
3442 with the one implemented under HP-UX 11 using secondary definitions.
3447 @heading @anchor{hppa-hp-hpux11}hppa*-hp-hpux11
3449 GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot
3450 be used to compile GCC 3.0 and up.
3452 The libffi and libjava libraries haven't been ported to 64-bit HP-UX@
3455 Refer to @uref{binaries.html,,binaries} for information about obtaining
3456 precompiled GCC binaries for HP-UX@. Precompiled binaries must be obtained
3457 to build the Ada language as it can't be bootstrapped using C@. Ada is
3458 only available for the 32-bit PA-RISC runtime.
3460 Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The
3461 bundled compiler supports only traditional C; you will need either HP's
3462 unbundled compiler, or a binary distribution of GCC@.
3464 It is possible to build GCC 3.3 starting with the bundled HP compiler,
3465 but the process requires several steps. GCC 3.3 can then be used to
3466 build later versions. The fastjar program contains ISO C code and
3467 can't be built with the HP bundled compiler. This problem can be
3468 avoided by not building the Java language. For example, use the
3469 @option{--enable-languages="c,c++,f77,objc"} option in your configure
3472 There are several possible approaches to building the distribution.
3473 Binutils can be built first using the HP tools. Then, the GCC
3474 distribution can be built. The second approach is to build GCC
3475 first using the HP tools, then build binutils, then rebuild GCC@.
3476 There have been problems with various binary distributions, so it
3477 is best not to start from a binary distribution.
3479 On 64-bit capable systems, there are two distinct targets. Different
3480 installation prefixes must be used if both are to be installed on
3481 the same system. The @samp{hppa[1-2]*-hp-hpux11*} target generates code
3482 for the 32-bit PA-RISC runtime architecture and uses the HP linker.
3483 The @samp{hppa64-hp-hpux11*} target generates 64-bit code for the
3484 PA-RISC 2.0 architecture.
3486 The script config.guess now selects the target type based on the compiler
3487 detected during configuration. You must define @env{PATH} or @env{CC} so
3488 that configure finds an appropriate compiler for the initial bootstrap.
3489 When @env{CC} is used, the definition should contain the options that are
3490 needed whenever @env{CC} is used.
3492 Specifically, options that determine the runtime architecture must be
3493 in @env{CC} to correctly select the target for the build. It is also
3494 convenient to place many other compiler options in @env{CC}. For example,
3495 @env{CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"}
3496 can be used to bootstrap the GCC 3.3 branch with the HP compiler in
3497 64-bit K&R/bundled mode. The @option{+DA2.0W} option will result in
3498 the automatic selection of the @samp{hppa64-hp-hpux11*} target. The
3499 macro definition table of cpp needs to be increased for a successful
3500 build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to
3501 be defined when building with the bundled compiler, or when using the
3502 @option{-Ac} option. These defines aren't necessary with @option{-Ae}.
3504 It is best to explicitly configure the @samp{hppa64-hp-hpux11*} target
3505 with the @option{--with-ld=@dots{}} option. This overrides the standard
3506 search for ld. The two linkers supported on this target require different
3507 commands. The default linker is determined during configuration. As a
3508 result, it's not possible to switch linkers in the middle of a GCC build.
3509 This has been reported to sometimes occur in unified builds of binutils
3512 A recent linker patch must be installed for the correct operation of
3513 GCC 3.3 and later. @code{PHSS_26559} and @code{PHSS_24304} are the
3514 oldest linker patches that are known to work. They are for HP-UX
3515 11.00 and 11.11, respectively. @code{PHSS_24303}, the companion to
3516 @code{PHSS_24304}, might be usable but it hasn't been tested. These
3517 patches have been superseded. Consult the HP patch database to obtain
3518 the currently recommended linker patch for your system.
3520 The patches are necessary for the support of weak symbols on the
3521 32-bit port, and for the running of initializers and finalizers. Weak
3522 symbols are implemented using SOM secondary definition symbols. Prior
3523 to HP-UX 11, there are bugs in the linker support for secondary symbols.
3524 The patches correct a problem of linker core dumps creating shared
3525 libraries containing secondary symbols, as well as various other
3526 linking issues involving secondary symbols.
3528 GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
3529 run initializers and finalizers on the 64-bit port. The 32-bit port
3530 uses the linker @option{+init} and @option{+fini} options for the same
3531 purpose. The patches correct various problems with the +init/+fini
3532 options, including program core dumps. Binutils 2.14 corrects a
3533 problem on the 64-bit port resulting from HP's non-standard use of
3534 the .init and .fini sections for array initializers and finalizers.
3536 Although the HP and GNU linkers are both supported for the
3537 @samp{hppa64-hp-hpux11*} target, it is strongly recommended that the
3538 HP linker be used for link editing on this target.
3540 At this time, the GNU linker does not support the creation of long
3541 branch stubs. As a result, it can't successfully link binaries
3542 containing branch offsets larger than 8 megabytes. In addition,
3543 there are problems linking shared libraries, linking executables
3544 with @option{-static}, and with dwarf2 unwind and exception support.
3545 It also doesn't provide stubs for internal calls to global functions
3546 in shared libraries, so these calls can't be overloaded.
3548 The HP dynamic loader does not support GNU symbol versioning, so symbol
3549 versioning is not supported. It may be necessary to disable symbol
3550 versioning with @option{--disable-symvers} when using GNU ld.
3552 POSIX threads are the default. The optional DCE thread library is not
3553 supported, so @option{--enable-threads=dce} does not work.
3558 @heading @anchor{x-x-linux-gnu}*-*-linux-gnu
3560 Versions of libstdc++-v3 starting with 3.2.1 require bug fixes present
3561 in glibc 2.2.5 and later. More information is available in the
3562 libstdc++-v3 documentation.
3567 @heading @anchor{ix86-x-linux}i?86-*-linux*
3569 As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
3570 See @uref{http://gcc.gnu.org/PR10877,,bug 10877} for more information.
3572 If you receive Signal 11 errors when building on GNU/Linux, then it is
3573 possible you have a hardware problem. Further information on this can be
3574 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
3579 @heading @anchor{ix86-x-solaris29}i?86-*-solaris2.9
3580 The Sun assembler in Solaris 9 has several bugs and limitations.
3581 While GCC works around them, several features are missing, so it is
3582 @c FIXME: which ones?
3583 recommended to use the GNU assembler instead. There is no bundled
3584 version, but the current version, from GNU binutils 2.22, is known to
3587 Solaris@tie{}2/x86 doesn't support the execution of SSE/SSE2 instructions
3588 before Solaris@tie{}9 4/04, even if the CPU supports them. Programs will
3589 receive @code{SIGILL} if they try. The fix is available both in
3590 Solaris@tie{}9 Update@tie{}6 and kernel patch 112234-12 or newer. To
3592 @option{-march} defaults to @samp{pentiumpro} on Solaris 9. If
3593 you have the patch installed, you can configure GCC with an appropriate
3594 @option{--with-arch} option, but need GNU @command{as} for SSE2 support.
3599 @heading @anchor{ix86-x-solaris210}i?86-*-solaris2.10
3600 Use this for Solaris 10 or later on x86 and x86-64 systems. Starting
3601 with GCC 4.7, there is also a 64-bit @samp{amd64-*-solaris2.1[0-9]*} or
3602 @samp{x86_64-*-solaris2.1[0-9]*} configuration that corresponds to
3603 @samp{sparcv9-sun-solaris2*}.
3605 It is recommended that you configure GCC to use the GNU assembler, in
3606 @file{/usr/sfw/bin/gas}. The versions included in Solaris 10, from GNU
3607 binutils 2.15, and Solaris 11, from GNU binutils 2.19, work fine,
3608 although the current version, from GNU binutils
3609 2.22, is known to work, too. Recent versions of the Sun assembler in
3610 @file{/usr/ccs/bin/as} work almost as well, though.
3611 @c FIXME: as patch requirements?
3613 For linking, the Sun linker, is preferred. If you want to use the GNU
3614 linker instead, which is available in @file{/usr/sfw/bin/gld}, note that
3615 due to a packaging bug the version in Solaris 10, from GNU binutils
3616 2.15, cannot be used, while the version in Solaris 11, from GNU binutils
3617 2.19, works, as does the latest version, from GNU binutils 2.22.
3619 To use GNU @command{as}, configure with the options
3620 @option{--with-gnu-as --with-as=@//usr/@/sfw/@/bin/@/gas}. It may be necessary
3621 to configure with @option{--without-gnu-ld --with-ld=@//usr/@/ccs/@/bin/@/ld} to
3622 guarantee use of Sun @command{ld}.
3623 @c FIXME: why --without-gnu-ld --with-ld?
3628 @heading @anchor{ia64-x-linux}ia64-*-linux
3629 IA-64 processor (also known as IPF, or Itanium Processor Family)
3632 If you are using the installed system libunwind library with
3633 @option{--with-system-libunwind}, then you must use libunwind 0.98 or
3636 None of the following versions of GCC has an ABI that is compatible
3637 with any of the other versions in this list, with the exception that
3638 Red Hat 2.96 and Trillian 000171 are compatible with each other:
3639 3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
3640 This primarily affects C++ programs and programs that create shared libraries.
3641 GCC 3.1 or later is recommended for compiling linux, the kernel.
3642 As of version 3.1 GCC is believed to be fully ABI compliant, and hence no
3643 more major ABI changes are expected.
3648 @heading @anchor{ia64-x-hpux}ia64-*-hpux*
3649 Building GCC on this target requires the GNU Assembler. The bundled HP
3650 assembler will not work. To prevent GCC from using the wrong assembler,
3651 the option @option{--with-gnu-as} may be necessary.
3653 The GCC libunwind library has not been ported to HPUX@. This means that for
3654 GCC versions 3.2.3 and earlier, @option{--enable-libunwind-exceptions}
3655 is required to build GCC@. For GCC 3.3 and later, this is the default.
3656 For gcc 3.4.3 and later, @option{--enable-libunwind-exceptions} is
3657 removed and the system libunwind library will always be used.
3661 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
3663 @heading @anchor{x-ibm-aix}*-ibm-aix*
3664 Support for AIX version 3 and older was discontinued in GCC 3.4.
3665 Support for AIX version 4.2 and older was discontinued in GCC 4.5.
3667 ``out of memory'' bootstrap failures may indicate a problem with
3668 process resource limits (ulimit). Hard limits are configured in the
3669 @file{/etc/security/limits} system configuration file.
3671 GCC can bootstrap with recent versions of IBM XLC, but bootstrapping
3672 with an earlier release of GCC is recommended. Bootstrapping with XLC
3673 requires a larger data segment, which can be enabled through the
3674 @var{LDR_CNTRL} environment variable, e.g.,
3677 % LDR_CNTRL=MAXDATA=0x50000000
3681 One can start with a pre-compiled version of GCC to build from
3682 sources. One may delete GCC's ``fixed'' header files when starting
3683 with a version of GCC built for an earlier release of AIX.
3685 To speed up the configuration phases of bootstrapping and installing GCC,
3686 one may use GNU Bash instead of AIX @command{/bin/sh}, e.g.,
3689 % CONFIG_SHELL=/opt/freeware/bin/bash
3690 % export CONFIG_SHELL
3693 and then proceed as described in @uref{build.html,,the build
3694 instructions}, where we strongly recommend specifying an absolute path
3695 to invoke @var{srcdir}/configure.
3697 Because GCC on AIX is built as a 32-bit executable by default,
3698 (although it can generate 64-bit programs) the GMP and MPFR libraries
3699 required by gfortran must be 32-bit libraries. Building GMP and MPFR
3700 as static archive libraries works better than shared libraries.
3702 Errors involving @code{alloca} when building GCC generally are due
3703 to an incorrect definition of @code{CC} in the Makefile or mixing files
3704 compiled with the native C compiler and GCC@. During the stage1 phase of
3705 the build, the native AIX compiler @strong{must} be invoked as @command{cc}
3706 (not @command{xlc}). Once @command{configure} has been informed of
3707 @command{xlc}, one needs to use @samp{make distclean} to remove the
3708 configure cache files and ensure that @env{CC} environment variable
3709 does not provide a definition that will confuse @command{configure}.
3710 If this error occurs during stage2 or later, then the problem most likely
3711 is the version of Make (see above).
3713 The native @command{as} and @command{ld} are recommended for
3714 bootstrapping on AIX@. The GNU Assembler, GNU Linker, and GNU
3715 Binutils version 2.20 is the minimum level that supports bootstrap on
3716 AIX 5@. The GNU Assembler has not been updated to support AIX 6@ or
3717 AIX 7. The native AIX tools do interoperate with GCC@.
3719 AIX 5.3 TL10, AIX 6.1 TL05 and AIX 7.1 TL00 introduced an AIX
3720 assembler change that sometimes produces corrupt assembly files
3721 causing AIX linker errors. The bug breaks GCC bootstrap on AIX and
3722 can cause compilation failures with existing GCC installations. An
3723 AIX iFix for AIX 5.3 is available (APAR IZ98385 for AIX 5.3 TL10, APAR
3724 IZ98477 for AIX 5.3 TL11 and IZ98134 for AIX 5.3 TL12). AIX 5.3 TL11 SP8,
3725 AIX 5.3 TL12 SP5, AIX 6.1 TL04 SP11, AIX 6.1 TL05 SP7, AIX 6.1 TL06 SP6,
3726 AIX 6.1 TL07 and AIX 7.1 TL01 should include the fix.
3728 Building @file{libstdc++.a} requires a fix for an AIX Assembler bug
3729 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a
3730 fix for another AIX Assembler bug and a co-dependent AIX Archiver fix
3731 referenced as APAR IY53606 (AIX 5.2) or as APAR IY54774 (AIX 5.1)
3733 @samp{libstdc++} in GCC 3.4 increments the major version number of the
3734 shared object and GCC installation places the @file{libstdc++.a}
3735 shared library in a common location which will overwrite the and GCC
3736 3.3 version of the shared library. Applications either need to be
3737 re-linked against the new shared library or the GCC 3.1 and GCC 3.3
3738 versions of the @samp{libstdc++} shared object needs to be available
3739 to the AIX runtime loader. The GCC 3.1 @samp{libstdc++.so.4}, if
3740 present, and GCC 3.3 @samp{libstdc++.so.5} shared objects can be
3741 installed for runtime dynamic loading using the following steps to set
3742 the @samp{F_LOADONLY} flag in the shared object for @emph{each}
3743 multilib @file{libstdc++.a} installed:
3745 Extract the shared objects from the currently installed
3746 @file{libstdc++.a} archive:
3748 % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
3751 Enable the @samp{F_LOADONLY} flag so that the shared object will be
3752 available for runtime dynamic loading, but not linking:
3754 % strip -e libstdc++.so.4 libstdc++.so.5
3757 Archive the runtime-only shared object in the GCC 3.4
3758 @file{libstdc++.a} archive:
3760 % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
3763 Linking executables and shared libraries may produce warnings of
3764 duplicate symbols. The assembly files generated by GCC for AIX always
3765 have included multiple symbol definitions for certain global variable
3766 and function declarations in the original program. The warnings should
3767 not prevent the linker from producing a correct library or runnable
3770 AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
3771 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
3772 to parse archive libraries did not handle the new format correctly.
3773 These routines are used by GCC and result in error messages during
3774 linking such as ``not a COFF file''. The version of the routines shipped
3775 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
3776 option of the archive command may be used to create archives of 32-bit
3777 objects using the original ``small format''. A correct version of the
3778 routines is shipped with AIX 4.3.2 and above.
3780 Some versions of the AIX binder (linker) can fail with a relocation
3781 overflow severe error when the @option{-bbigtoc} option is used to link
3782 GCC-produced object files into an executable that overflows the TOC@. A fix
3783 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
3784 available from IBM Customer Support and from its
3785 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3786 website as PTF U455193.
3788 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
3789 with a segmentation fault when invoked by any version of GCC@. A fix for
3790 APAR IX87327 is available from IBM Customer Support and from its
3791 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3792 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
3794 The initial assembler shipped with AIX 4.3.0 generates incorrect object
3795 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
3796 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
3797 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3798 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
3800 AIX provides National Language Support (NLS)@. Compilers and assemblers
3801 use NLS to support locale-specific representations of various data
3802 formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
3803 separating decimal fractions). There have been problems reported where
3804 GCC does not produce the same floating-point formats that the assembler
3805 expects. If one encounters this problem, set the @env{LANG}
3806 environment variable to @samp{C} or @samp{En_US}.
3808 A default can be specified with the @option{-mcpu=@var{cpu_type}}
3809 switch and using the configure option @option{--with-cpu-@var{cpu_type}}.
3814 @heading @anchor{iq2000-x-elf}iq2000-*-elf
3815 Vitesse IQ2000 processors. These are used in embedded
3816 applications. There are no standard Unix configurations.
3821 @heading @anchor{lm32-x-elf}lm32-*-elf
3822 Lattice Mico32 processor.
3823 This configuration is intended for embedded systems.
3828 @heading @anchor{lm32-x-uclinux}lm32-*-uclinux
3829 Lattice Mico32 processor.
3830 This configuration is intended for embedded systems running uClinux.
3835 @heading @anchor{m32c-x-elf}m32c-*-elf
3836 Renesas M32C processor.
3837 This configuration is intended for embedded systems.
3842 @heading @anchor{m32r-x-elf}m32r-*-elf
3843 Renesas M32R processor.
3844 This configuration is intended for embedded systems.
3849 @heading @anchor{m68k-x-x}m68k-*-*
3851 @samp{m68k-*-elf*}, @samp{m68k-*-rtems}, @samp{m68k-*-uclinux} and
3853 build libraries for both M680x0 and ColdFire processors. If you only
3854 need the M680x0 libraries, you can omit the ColdFire ones by passing
3855 @option{--with-arch=m68k} to @command{configure}. Alternatively, you
3856 can omit the M680x0 libraries by passing @option{--with-arch=cf} to
3857 @command{configure}. These targets default to 5206 or 5475 code as
3858 appropriate for the target system when
3859 configured with @option{--with-arch=cf} and 68020 code otherwise.
3861 The @samp{m68k-*-netbsd} and
3862 @samp{m68k-*-openbsd} targets also support the @option{--with-arch}
3863 option. They will generate ColdFire CFV4e code when configured with
3864 @option{--with-arch=cf} and 68020 code otherwise.
3866 You can override the default processors listed above by configuring
3867 with @option{--with-cpu=@var{target}}. This @var{target} can either
3868 be a @option{-mcpu} argument or one of the following values:
3869 @samp{m68000}, @samp{m68010}, @samp{m68020}, @samp{m68030},
3870 @samp{m68040}, @samp{m68060}, @samp{m68020-40} and @samp{m68020-60}.
3872 GCC requires at least binutils version 2.17 on these targets.
3877 @heading @anchor{m68k-x-uclinux}m68k-*-uclinux
3878 GCC 4.3 changed the uClinux configuration so that it uses the
3879 @samp{m68k-linux-gnu} ABI rather than the @samp{m68k-elf} ABI.
3880 It also added improved support for C++ and flat shared libraries,
3881 both of which were ABI changes.
3887 @heading @anchor{mep-x-elf}mep-*-elf
3888 Toshiba Media embedded Processor.
3889 This configuration is intended for embedded systems.
3894 @heading @anchor{microblaze-x-elf}microblaze-*-elf
3895 Xilinx MicroBlaze processor.
3896 This configuration is intended for embedded systems.
3901 @heading @anchor{mips-x-x}mips-*-*
3902 If on a MIPS system you get an error message saying ``does not have gp
3903 sections for all it's [sic] sectons [sic]'', don't worry about it. This
3904 happens whenever you use GAS with the MIPS linker, but there is not
3905 really anything wrong, and it is okay to use the output file. You can
3906 stop such warnings by installing the GNU linker.
3908 It would be nice to extend GAS to produce the gp tables, but they are
3909 optional, and there should not be a warning about their absence.
3911 The libstdc++ atomic locking routines for MIPS targets requires MIPS II
3912 and later. A patch went in just after the GCC 3.3 release to
3913 make @samp{mips*-*-*} use the generic implementation instead. You can also
3914 configure for @samp{mipsel-elf} as a workaround. The
3915 @samp{mips*-*-linux*} target continues to use the MIPS II routines. More
3916 work on this is expected in future releases.
3918 @c If you make --with-llsc the default for another target, please also
3919 @c update the description of the --with-llsc option.
3921 The built-in @code{__sync_*} functions are available on MIPS II and
3922 later systems and others that support the @samp{ll}, @samp{sc} and
3923 @samp{sync} instructions. This can be overridden by passing
3924 @option{--with-llsc} or @option{--without-llsc} when configuring GCC.
3925 Since the Linux kernel emulates these instructions if they are
3926 missing, the default for @samp{mips*-*-linux*} targets is
3927 @option{--with-llsc}. The @option{--with-llsc} and
3928 @option{--without-llsc} configure options may be overridden at compile
3929 time by passing the @option{-mllsc} or @option{-mno-llsc} options to
3932 MIPS systems check for division by zero (unless
3933 @option{-mno-check-zero-division} is passed to the compiler) by
3934 generating either a conditional trap or a break instruction. Using
3935 trap results in smaller code, but is only supported on MIPS II and
3936 later. Also, some versions of the Linux kernel have a bug that
3937 prevents trap from generating the proper signal (@code{SIGFPE}). To enable
3938 the use of break, use the @option{--with-divide=breaks}
3939 @command{configure} option when configuring GCC@. The default is to
3940 use traps on systems that support them.
3942 The assembler from GNU binutils 2.17 and earlier has a bug in the way
3943 it sorts relocations for REL targets (o32, o64, EABI). This can cause
3944 bad code to be generated for simple C++ programs. Also the linker
3945 from GNU binutils versions prior to 2.17 has a bug which causes the
3946 runtime linker stubs in very large programs, like @file{libgcj.so}, to
3947 be incorrectly generated. GNU Binutils 2.18 and later (and snapshots
3948 made after Nov. 9, 2006) should be free from both of these problems.
3953 @heading @anchor{mips-sgi-irix5}mips-sgi-irix5
3955 Support for IRIX 5 has been removed in GCC 4.6.
3960 @heading @anchor{mips-sgi-irix6}mips-sgi-irix6
3962 Support for IRIX 6.5 has been removed in GCC 4.8. Support for IRIX 6
3963 releases before 6.5 has been removed in GCC 4.6, as well as support for
3969 @heading @anchor{moxie-x-elf}moxie-*-elf
3970 The moxie processor.
3975 @heading @anchor{powerpc-x-x}powerpc-*-*
3977 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
3978 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
3981 @uref{ftp://ftp.kernel.org/pub/linux/devel/binutils,,binutils 2.15}
3982 or newer for a working GCC@.
3987 @heading @anchor{powerpc-x-darwin}powerpc-*-darwin*
3988 PowerPC running Darwin (Mac OS X kernel).
3990 Pre-installed versions of Mac OS X may not include any developer tools,
3991 meaning that you will not be able to build GCC from source. Tool
3992 binaries are available at
3993 @uref{http://opensource.apple.com/}.
3995 This version of GCC requires at least cctools-590.36. The
3996 cctools-590.36 package referenced from
3997 @uref{http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html} will not work
3998 on systems older than 10.3.9 (aka darwin7.9.0).
4003 @heading @anchor{powerpc-x-elf}powerpc-*-elf
4004 PowerPC system in big endian mode, running System V.4.
4009 @heading @anchor{powerpc-x-linux-gnu}powerpc*-*-linux-gnu*
4011 PowerPC system in big endian mode running Linux.
4016 @heading @anchor{powerpc-x-netbsd}powerpc-*-netbsd*
4017 PowerPC system in big endian mode running NetBSD@.
4022 @heading @anchor{powerpc-x-eabisim}powerpc-*-eabisim
4023 Embedded PowerPC system in big endian mode for use in running under the
4029 @heading @anchor{powerpc-x-eabi}powerpc-*-eabi
4030 Embedded PowerPC system in big endian mode.
4035 @heading @anchor{powerpcle-x-elf}powerpcle-*-elf
4036 PowerPC system in little endian mode, running System V.4.
4041 @heading @anchor{powerpcle-x-eabisim}powerpcle-*-eabisim
4042 Embedded PowerPC system in little endian mode for use in running under
4048 @heading @anchor{powerpcle-x-eabi}powerpcle-*-eabi
4049 Embedded PowerPC system in little endian mode.
4054 @heading @anchor{rl78-x-elf}rl78-*-elf
4055 The Renesas RL78 processor.
4056 This configuration is intended for embedded systems.
4061 @heading @anchor{rx-x-elf}rx-*-elf
4062 The Renesas RX processor. See
4063 @uref{http://eu.renesas.com/fmwk.jsp?cnt=rx600_series_landing.jsp&fp=/products/mpumcu/rx_family/rx600_series}
4064 for more information about this processor.
4069 @heading @anchor{s390-x-linux}s390-*-linux*
4070 S/390 system running GNU/Linux for S/390@.
4075 @heading @anchor{s390x-x-linux}s390x-*-linux*
4076 zSeries system (64-bit) running GNU/Linux for zSeries@.
4081 @heading @anchor{s390x-ibm-tpf}s390x-ibm-tpf*
4082 zSeries system (64-bit) running TPF@. This platform is
4083 supported as cross-compilation target only.
4088 @c Please use Solaris 2 to refer to all release of Solaris, starting
4089 @c with 2.0 until 2.6, 7, 8, etc. Solaris 1 was a marketing name for
4090 @c SunOS 4 releases which we don't use to avoid confusion. Solaris
4091 @c alone is too unspecific and must be avoided.
4092 @heading @anchor{x-x-solaris2}*-*-solaris2*
4094 Support for Solaris 9 has been obsoleted in GCC 4.9, but can still be
4095 enabled by configuring with @option{--enable-obsolete}. Support will be
4096 removed in GCC 4.10. Support for Solaris 8 has removed in GCC 4.8.
4097 Support for Solaris 7 has been removed in GCC 4.6.
4099 Sun does not ship a C compiler with Solaris 2 before Solaris 10, though
4100 you can download the Sun Studio compilers for free. In Solaris 10 and
4101 11, GCC 3.4.3 is available as @command{/usr/sfw/bin/gcc}. Solaris 11
4102 also provides GCC 4.5.2 as @command{/usr/gcc/4.5/bin/gcc}. Alternatively,
4103 you can install a pre-built GCC to bootstrap and install GCC. See the
4104 @uref{binaries.html,,binaries page} for details.
4106 The Solaris 2 @command{/bin/sh} will often fail to configure
4107 @samp{libstdc++-v3}, @samp{boehm-gc} or @samp{libjava}. We therefore
4108 recommend using the following initial sequence of commands
4111 % CONFIG_SHELL=/bin/ksh
4112 % export CONFIG_SHELL
4116 and proceed as described in @uref{configure.html,,the configure instructions}.
4117 In addition we strongly recommend specifying an absolute path to invoke
4118 @command{@var{srcdir}/configure}.
4120 Solaris 2 comes with a number of optional OS packages. Some of these
4121 are needed to use GCC fully, namely @code{SUNWarc},
4122 @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
4123 @code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all
4124 optional packages when installing Solaris 2, you will need to verify that
4125 the packages that GCC needs are installed.
4127 To check whether an optional package is installed, use
4128 the @command{pkginfo} command. To add an optional package, use the
4129 @command{pkgadd} command. For further details, see the Solaris 2
4132 Trying to use the linker and other tools in
4133 @file{/usr/ucb} to install GCC has been observed to cause trouble.
4134 For example, the linker may hang indefinitely. The fix is to remove
4135 @file{/usr/ucb} from your @env{PATH}.
4137 The build process works more smoothly with the legacy Sun tools so, if you
4138 have @file{/usr/xpg4/bin} in your @env{PATH}, we recommend that you place
4139 @file{/usr/bin} before @file{/usr/xpg4/bin} for the duration of the build.
4141 We recommend the use of the Sun assembler or the GNU assembler, in
4142 conjunction with the Sun linker. The GNU @command{as}
4143 versions included in Solaris 10, from GNU binutils 2.15, and Solaris 11,
4144 from GNU binutils 2.19, are known to work. They can be found in
4145 @file{/usr/sfw/bin/gas}. Current versions of GNU binutils (2.22)
4146 are known to work as well. Note that your mileage may vary
4147 if you use a combination of the GNU tools and the Sun tools: while the
4148 combination GNU @command{as} + Sun @command{ld} should reasonably work,
4149 the reverse combination Sun @command{as} + GNU @command{ld} may fail to
4150 build or cause memory corruption at runtime in some cases for C++ programs.
4152 GNU @command{ld} usually works as well, although the version included in
4153 Solaris 10 cannot be used due to several bugs. Again, the current
4154 version (2.22) is known to work, but generally lacks platform specific
4155 features, so better stay with Sun @command{ld}. To use the LTO linker
4156 plugin (@option{-fuse-linker-plugin}) with GNU @command{ld}, GNU
4157 binutils @emph{must} be configured with @option{--enable-largefile}.
4159 To enable symbol versioning in @samp{libstdc++} with Sun @command{ld},
4160 you need to have any version of GNU @command{c++filt}, which is part of
4161 GNU binutils. @samp{libstdc++} symbol versioning will be disabled if no
4162 appropriate version is found. Sun @command{c++filt} from the Sun Studio
4163 compilers does @emph{not} work.
4165 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
4166 newer: @command{g++} will complain that types are missing. These headers
4167 assume that omitting the type means @code{int}; this assumption worked for
4168 C90 but is wrong for C++, and is now wrong for C99 also.
4170 Sun bug 4927647 sometimes causes random spurious testsuite failures
4171 related to missing diagnostic output. This bug doesn't affect GCC
4172 itself, rather it is a kernel bug triggered by the @command{expect}
4173 program which is used only by the GCC testsuite driver. When the bug
4174 causes the @command{expect} program to miss anticipated output, extra
4175 testsuite failures appear.
4177 There are patches for Solaris 9 (117171-11 or newer for
4178 SPARC, 117172-11 or newer for Intel) that address this problem.
4180 Thread-local storage (TLS) is supported in Solaris@tie{}9, but requires
4181 some patches. The @samp{libthread} patches provide the
4182 @code{__tls_get_addr} (SPARC, 64-bit x86) resp.@ @code{___tls_get_addr}
4183 (32-bit x86) functions. On Solaris@tie{}9, the necessary support
4184 on SPARC is present since FCS, while 114432-05 or newer is required on
4185 Intel. Additionally, on Solaris@tie{}9/x86, patch 113986-02 or newer is
4186 required for the Sun @command{ld} and runtime linker (@command{ld.so.1})
4187 support, while Solaris@tie{}9/SPARC works since FCS. The linker
4188 patches must be installed even if GNU @command{ld} is used. Sun
4189 @command{as} in Solaris@tie{}9 doesn't support the necessary
4190 relocations, so GNU @command{as} must be used. The @command{configure}
4191 script checks for those prerequisites and automatically enables TLS
4192 support if they are met. Although those minimal patch versions should
4193 work, it is recommended to use the latest patch versions which include
4194 additional bug fixes.
4199 @heading @anchor{sparc-x-x}sparc*-*-*
4201 This section contains general configuration information for all
4202 SPARC-based platforms. In addition to reading this section, please
4203 read all other sections that match your target.
4205 Newer versions of the GNU Multiple Precision Library (GMP), the MPFR
4206 library and the MPC library are known to be miscompiled by earlier
4207 versions of GCC on these platforms. We therefore recommend the use
4208 of the exact versions of these libraries listed as minimal versions
4209 in @uref{prerequisites.html,,the prerequisites}.
4214 @heading @anchor{sparc-sun-solaris2}sparc-sun-solaris2*
4216 When GCC is configured to use GNU binutils 2.14 or later, the binaries
4217 produced are smaller than the ones produced using Sun's native tools;
4218 this difference is quite significant for binaries containing debugging
4221 Starting with Solaris 7, the operating system is capable of executing
4222 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
4223 this; the @option{-m64} option enables 64-bit code generation.
4224 However, if all you want is code tuned for the UltraSPARC CPU, you
4225 should try the @option{-mtune=ultrasparc} option instead, which produces
4226 code that, unlike full 64-bit code, can still run on non-UltraSPARC
4229 When configuring on a Solaris 7 or later system that is running a kernel
4230 that supports only 32-bit binaries, one must configure with
4231 @option{--disable-multilib}, since we will not be able to build the
4232 64-bit target libraries.
4234 GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of
4235 the GNU compiler (especially GCC 3.0.x versions), which lead to the
4236 miscompilation of the stage1 compiler and the subsequent failure of the
4237 bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary
4238 stage, i.e.@: to bootstrap that compiler with the base compiler and then
4239 use it to bootstrap the final compiler.
4241 GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE Studio 7)
4242 and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a bootstrap
4243 failure in form of a miscompilation of the stage1 compiler by the Sun
4244 compiler. This is Sun bug 4974440. This is fixed with patch 112760-07.
4246 GCC 3.4 changed the default debugging format from Stabs to DWARF-2 for
4247 32-bit code on Solaris 7 and later. If you use the Sun assembler, this
4248 change apparently runs afoul of Sun bug 4910101 (which is referenced as
4249 an x86-only problem by Sun, probably because they do not use DWARF-2).
4250 A symptom of the problem is that you cannot compile C++ programs like
4251 @command{groff} 1.19.1 without getting messages similar to the following:
4254 ld: warning: relocation error: R_SPARC_UA32: @dots{}
4255 external symbolic relocation against non-allocatable section
4256 .debug_info cannot be processed at runtime: relocation ignored.
4260 To work around this problem, compile with @option{-gstabs+} instead of
4263 When configuring the GNU Multiple Precision Library (GMP), the MPFR
4264 library or the MPC library on a Solaris 7 or later system, the canonical
4265 target triplet must be specified as the @command{build} parameter on the
4266 configure line. This target triplet can be obtained by invoking @command{./config.guess} in the toplevel source directory of GCC (and
4267 not that of GMP or MPFR or MPC). For example on a Solaris 9 system:
4270 % ./configure --build=sparc-sun-solaris2.9 --prefix=xxx
4276 @heading @anchor{sparc-sun-solaris210}sparc-sun-solaris2.10
4278 There is a bug in older versions of the Sun assembler which breaks
4279 thread-local storage (TLS). A typical error message is
4282 ld: fatal: relocation error: R_SPARC_TLS_LE_HIX22: file /var/tmp//ccamPA1v.o:
4283 symbol <unknown>: bad symbol type SECT: symbol type must be TLS
4287 This bug is fixed in Sun patch 118683-03 or later.
4292 @heading @anchor{sparc-x-linux}sparc-*-linux*
4294 GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
4295 or newer on this platform. All earlier binutils and glibc
4296 releases mishandled unaligned relocations on @code{sparc-*-*} targets.
4302 @heading @anchor{sparc64-x-solaris2}sparc64-*-solaris2*
4304 When configuring the GNU Multiple Precision Library (GMP), the MPFR
4305 library or the MPC library, the canonical target triplet must be specified
4306 as the @command{build} parameter on the configure line. For example
4307 on a Solaris 9 system:
4310 % ./configure --build=sparc64-sun-solaris2.9 --prefix=xxx
4313 The following compiler flags must be specified in the configure
4314 step in order to bootstrap this target with the Sun compiler:
4317 % CC="cc -xarch=v9 -xildoff" @var{srcdir}/configure [@var{options}] [@var{target}]
4321 @option{-xarch=v9} specifies the SPARC-V9 architecture to the Sun toolchain
4322 and @option{-xildoff} turns off the incremental linker.
4327 @heading @anchor{sparcv9-x-solaris2}sparcv9-*-solaris2*
4329 This is a synonym for @samp{sparc64-*-solaris2*}.
4334 @heading @anchor{c6x-x-x}c6x-*-*
4336 The C6X family of processors. This port requires binutils-2.22 or newer.
4341 @heading @anchor{tilegx-*-linux}tilegx-*-linux*
4343 The TILE-Gx processor running GNU/Linux. This port requires
4344 binutils-2.22 or newer.
4349 @heading @anchor{tilepro-*-linux}tilepro-*-linux*
4351 The TILEPro processor running GNU/Linux. This port requires
4352 binutils-2.22 or newer.
4357 @heading @anchor{x-x-vxworks}*-*-vxworks*
4358 Support for VxWorks is in flux. At present GCC supports @emph{only} the
4359 very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC@.
4360 We welcome patches for other architectures supported by VxWorks 5.5.
4361 Support for VxWorks AE would also be welcome; we believe this is merely
4362 a matter of writing an appropriate ``configlette'' (see below). We are
4363 not interested in supporting older, a.out or COFF-based, versions of
4366 VxWorks comes with an older version of GCC installed in
4367 @file{@var{$WIND_BASE}/host}; we recommend you do not overwrite it.
4368 Choose an installation @var{prefix} entirely outside @var{$WIND_BASE}.
4369 Before running @command{configure}, create the directories @file{@var{prefix}}
4370 and @file{@var{prefix}/bin}. Link or copy the appropriate assembler,
4371 linker, etc.@: into @file{@var{prefix}/bin}, and set your @var{PATH} to
4372 include that directory while running both @command{configure} and
4375 You must give @command{configure} the
4376 @option{--with-headers=@var{$WIND_BASE}/target/h} switch so that it can
4377 find the VxWorks system headers. Since VxWorks is a cross compilation
4378 target only, you must also specify @option{--target=@var{target}}.
4379 @command{configure} will attempt to create the directory
4380 @file{@var{prefix}/@var{target}/sys-include} and copy files into it;
4381 make sure the user running @command{configure} has sufficient privilege
4384 GCC's exception handling runtime requires a special ``configlette''
4385 module, @file{contrib/gthr_supp_vxw_5x.c}. Follow the instructions in
4386 that file to add the module to your kernel build. (Future versions of
4387 VxWorks will incorporate this module.)
4392 @heading @anchor{x86-64-x-x}x86_64-*-*, amd64-*-*
4394 GCC supports the x86-64 architecture implemented by the AMD64 processor
4395 (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD@.
4396 On GNU/Linux the default is a bi-arch compiler which is able to generate
4397 both 64-bit x86-64 and 32-bit x86 code (via the @option{-m32} switch).
4402 @heading @anchor{x86-64-x-solaris210}x86_64-*-solaris2.1[0-9]*
4404 GCC also supports the x86-64 architecture implemented by the AMD64
4405 processor (@samp{amd64-*-*} is an alias for @samp{x86_64-*-*}) on
4406 Solaris 10 or later. Unlike other systems, without special options a
4407 bi-arch compiler is built which generates 32-bit code by default, but
4408 can generate 64-bit x86-64 code with the @option{-m64} switch. Since
4409 GCC 4.7, there is also configuration that defaults to 64-bit code, but
4410 can generate 32-bit code with @option{-m32}. To configure and build
4411 this way, you have to provide all support libraries like @file{libgmp}
4412 as 64-bit code, configure with @option{--target=x86_64-pc-solaris2.1x}
4413 and @samp{CC=gcc -m64}.
4418 @heading @anchor{xtensa-x-elf}xtensa*-*-elf
4420 This target is intended for embedded Xtensa systems using the
4421 @samp{newlib} C library. It uses ELF but does not support shared
4422 objects. Designed-defined instructions specified via the
4423 Tensilica Instruction Extension (TIE) language are only supported
4424 through inline assembly.
4426 The Xtensa configuration information must be specified prior to
4427 building GCC@. The @file{include/xtensa-config.h} header
4428 file contains the configuration information. If you created your
4429 own Xtensa configuration with the Xtensa Processor Generator, the
4430 downloaded files include a customized copy of this header file,
4431 which you can use to replace the default header file.
4436 @heading @anchor{xtensa-x-linux}xtensa*-*-linux*
4438 This target is for Xtensa systems running GNU/Linux. It supports ELF
4439 shared objects and the GNU C library (glibc). It also generates
4440 position-independent code (PIC) regardless of whether the
4441 @option{-fpic} or @option{-fPIC} options are used. In other
4442 respects, this target is the same as the
4443 @uref{#xtensa*-*-elf,,@samp{xtensa*-*-elf}} target.
4448 @heading @anchor{windows}Microsoft Windows
4450 @subheading Intel 16-bit versions
4451 The 16-bit versions of Microsoft Windows, such as Windows 3.1, are not
4454 However, the 32-bit port has limited support for Microsoft
4455 Windows 3.11 in the Win32s environment, as a target only. See below.
4457 @subheading Intel 32-bit versions
4459 The 32-bit versions of Windows, including Windows 95, Windows NT, Windows
4460 XP, and Windows Vista, are supported by several different target
4461 platforms. These targets differ in which Windows subsystem they target
4462 and which C libraries are used.
4465 @item Cygwin @uref{#x-x-cygwin,,*-*-cygwin}: Cygwin provides a user-space
4466 Linux API emulation layer in the Win32 subsystem.
4467 @item Interix @uref{#x-x-interix,,*-*-interix}: The Interix subsystem
4468 provides native support for POSIX.
4469 @item MinGW @uref{#x-x-mingw32,,*-*-mingw32}: MinGW is a native GCC port for
4470 the Win32 subsystem that provides a subset of POSIX.
4471 @item MKS i386-pc-mks: NuTCracker from MKS. See
4472 @uref{http://www.mkssoftware.com/} for more information.
4475 @subheading Intel 64-bit versions
4477 GCC contains support for x86-64 using the mingw-w64
4478 runtime library, available from @uref{http://mingw-w64.sourceforge.net/}.
4479 This library should be used with the target triple x86_64-pc-mingw32.
4481 Presently Windows for Itanium is not supported.
4483 @subheading Windows CE
4485 Windows CE is supported as a target only on Hitachi
4486 SuperH (sh-wince-pe), and MIPS (mips-wince-pe).
4488 @subheading Other Windows Platforms
4490 GCC no longer supports Windows NT on the Alpha or PowerPC.
4492 GCC no longer supports the Windows POSIX subsystem. However, it does
4493 support the Interix subsystem. See above.
4495 Old target names including *-*-winnt and *-*-windowsnt are no longer used.
4497 PW32 (i386-pc-pw32) support was never completed, and the project seems to
4498 be inactive. See @uref{http://pw32.sourceforge.net/} for more information.
4500 UWIN support has been removed due to a lack of maintenance.
4505 @heading @anchor{x-x-cygwin}*-*-cygwin
4507 Ports of GCC are included with the
4508 @uref{http://www.cygwin.com/,,Cygwin environment}.
4510 GCC will build under Cygwin without modification; it does not build
4511 with Microsoft's C++ compiler and there are no plans to make it do so.
4513 The Cygwin native compiler can be configured to target any 32-bit x86
4514 cpu architecture desired; the default is i686-pc-cygwin. It should be
4515 used with as up-to-date a version of binutils as possible; use either
4516 the latest official GNU binutils release in the Cygwin distribution,
4517 or version 2.20 or above if building your own.
4522 @heading @anchor{x-x-interix}*-*-interix
4524 The Interix target is used by OpenNT, Interix, Services For UNIX (SFU),
4525 and Subsystem for UNIX-based Applications (SUA). Applications compiled
4526 with this target run in the Interix subsystem, which is separate from
4527 the Win32 subsystem. This target was last known to work in GCC 3.3.
4532 @heading @anchor{x-x-mingw32}*-*-mingw32
4534 GCC will build with and support only MinGW runtime 3.12 and later.
4535 Earlier versions of headers are incompatible with the new default semantics
4536 of @code{extern inline} in @code{-std=c99} and @code{-std=gnu99} modes.
4541 @heading @anchor{older}Older systems
4543 GCC contains support files for many older (1980s and early
4544 1990s) Unix variants. For the most part, support for these systems
4545 has not been deliberately removed, but it has not been maintained for
4546 several years and may suffer from bitrot.
4548 Starting with GCC 3.1, each release has a list of ``obsoleted'' systems.
4549 Support for these systems is still present in that release, but
4550 @command{configure} will fail unless the @option{--enable-obsolete}
4551 option is given. Unless a maintainer steps forward, support for these
4552 systems will be removed from the next release of GCC@.
4554 Support for old systems as hosts for GCC can cause problems if the
4555 workarounds for compiler, library and operating system bugs affect the
4556 cleanliness or maintainability of the rest of GCC@. In some cases, to
4557 bring GCC up on such a system, if still possible with current GCC, may
4558 require first installing an old version of GCC which did work on that
4559 system, and using it to compile a more recent GCC, to avoid bugs in the
4560 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
4561 @file{old-releases} directory on the @uref{../mirrors.html,,GCC mirror
4562 sites}. Header bugs may generally be avoided using
4563 @command{fixincludes}, but bugs or deficiencies in libraries and the
4564 operating system may still cause problems.
4566 Support for older systems as targets for cross-compilation is less
4567 problematic than support for them as hosts for GCC; if an enthusiast
4568 wishes to make such a target work again (including resurrecting any of
4569 the targets that never worked with GCC 2, starting from the last
4570 version before they were removed), patches
4571 @uref{../contribute.html,,following the usual requirements} would be
4572 likely to be accepted, since they should not affect the support for more
4575 For some systems, old versions of GNU binutils may also be useful,
4576 and are available from @file{pub/binutils/old-releases} on
4577 @uref{http://sourceware.org/mirrors.html,,sourceware.org mirror sites}.
4579 Some of the information on specific systems above relates to
4580 such older systems, but much of the information
4581 about GCC on such systems (which may no longer be applicable to
4582 current GCC) is to be found in the GCC texinfo manual.
4587 @heading @anchor{elf}all ELF targets (SVR4, Solaris 2, etc.)
4589 C++ support is significantly better on ELF targets if you use the
4590 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
4591 inlines, vtables and template instantiations will be discarded
4600 @uref{./index.html,,Return to the GCC Installation page}
4604 @c ***Old documentation******************************************************
4606 @include install-old.texi
4612 @uref{./index.html,,Return to the GCC Installation page}
4616 @c ***GFDL********************************************************************
4624 @uref{./index.html,,Return to the GCC Installation page}
4628 @c ***************************************************************************
4629 @c Part 6 The End of the Document
4631 @comment node-name, next, previous, up
4632 @node Concept Index, , GNU Free Documentation License, Top
4636 @unnumbered Concept Index