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, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
48 @c 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
49 @c 2010, 2011 Free Software Foundation, Inc.
50 @c *** Converted to texinfo by Dean Wakerley, dean@wakerley.com
52 @c IMPORTANT: whenever you modify this file, run `install.texi2html' to
53 @c test the generation of HTML documents for the gcc.gnu.org web pages.
55 @c Do not use @footnote{} in this file as it breaks install.texi2html!
57 @c Include everything if we're not making html
61 @set prerequisiteshtml
72 @c Part 2 Summary Description and Copyright
74 Copyright @copyright{} 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
75 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
76 2010 Free Software Foundation, Inc.
78 Permission is granted to copy, distribute and/or modify this document
79 under the terms of the GNU Free Documentation License, Version 1.3 or
80 any later version published by the Free Software Foundation; with no
81 Invariant Sections, the Front-Cover texts being (a) (see below), and
82 with the Back-Cover Texts being (b) (see below). A copy of the
83 license is included in the section entitled ``@uref{./gfdl.html,,GNU
84 Free Documentation License}''.
86 (a) The FSF's Front-Cover Text is:
90 (b) The FSF's Back-Cover Text is:
92 You have freedom to copy and modify this GNU Manual, like GNU
93 software. Copies published by the Free Software Foundation raise
94 funds for GNU development.
99 @dircategory Software development
101 * gccinstall: (gccinstall). Installing the GNU Compiler Collection.
104 @c Part 3 Titlepage and Copyright
106 @title Installing GCC
109 @c The following two commands start the copyright page.
111 @vskip 0pt plus 1filll
115 @c Part 4 Top node, Master Menu, and/or Table of Contents
118 @comment node-name, next, Previous, up
121 * Installing GCC:: This document describes the generic installation
122 procedure for GCC as well as detailing some target
123 specific installation instructions.
125 * Specific:: Host/target specific installation notes for GCC.
126 * Binaries:: Where to get pre-compiled binaries.
128 * Old:: Old installation documentation.
130 * GNU Free Documentation License:: How you can copy and share this manual.
131 * Concept Index:: This index has two entries.
139 @c Part 5 The Body of the Document
140 @c ***Installing GCC**********************************************************
142 @comment node-name, next, previous, up
143 @node Installing GCC, Binaries, , Top
147 @chapter Installing GCC
150 The latest version of this document is always available at
151 @uref{http://gcc.gnu.org/install/,,http://gcc.gnu.org/install/}.
153 This document describes the generic installation procedure for GCC as well
154 as detailing some target specific installation instructions.
156 GCC includes several components that previously were separate distributions
157 with their own installation instructions. This document supersedes all
158 package specific installation instructions.
160 @emph{Before} starting the build/install procedure please check the
162 @ref{Specific, host/target specific installation notes}.
165 @uref{specific.html,,host/target specific installation notes}.
167 We recommend you browse the entire generic installation instructions before
170 Lists of successful builds for released versions of GCC are
171 available at @uref{http://gcc.gnu.org/buildstat.html}.
172 These lists are updated as new information becomes available.
174 The installation procedure itself is broken into five steps.
179 * Downloading the source::
182 * Testing:: (optional)
189 @uref{prerequisites.html,,Prerequisites}
191 @uref{download.html,,Downloading the source}
193 @uref{configure.html,,Configuration}
195 @uref{build.html,,Building}
197 @uref{test.html,,Testing} (optional)
199 @uref{finalinstall.html,,Final install}
203 Please note that GCC does not support @samp{make uninstall} and probably
204 won't do so in the near future as this would open a can of worms. Instead,
205 we suggest that you install GCC into a directory of its own and simply
206 remove that directory when you do not need that specific version of GCC
207 any longer, and, if shared libraries are installed there as well, no
208 more binaries exist that use them.
211 There are also some @uref{old.html,,old installation instructions},
212 which are mostly obsolete but still contain some information which has
213 not yet been merged into the main part of this manual.
221 @uref{./index.html,,Return to the GCC Installation page}
227 @c ***Prerequisites**************************************************
229 @comment node-name, next, previous, up
230 @node Prerequisites, Downloading the source, , Installing GCC
232 @ifset prerequisiteshtml
234 @chapter Prerequisites
236 @cindex Prerequisites
238 GCC requires that various tools and packages be available for use in the
239 build procedure. Modifying GCC sources requires additional tools
242 @heading Tools/packages necessary for building GCC
244 @item ISO C90 compiler
245 Necessary to bootstrap GCC, although versions of GCC prior
246 to 3.4 also allow bootstrapping with a traditional (K&R) C compiler.
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 2.95 or later) because source code for language
251 frontends other than C might use GCC extensions.
255 In order to build the Ada compiler (GNAT) you must already have GNAT
256 installed because portions of the Ada frontend are written in Ada (with
257 GNAT extensions.) Refer to the Ada installation instructions for more
258 specific information.
260 @item A ``working'' POSIX compatible shell, or GNU bash
262 Necessary when running @command{configure} because some
263 @command{/bin/sh} shells have bugs and may crash when configuring the
264 target libraries. In other cases, @command{/bin/sh} or @command{ksh}
265 have disastrous corner-case performance problems. This
266 can cause target @command{configure} runs to literally take days to
267 complete in some cases.
269 So on some platforms @command{/bin/ksh} is sufficient, on others it
270 isn't. See the host/target specific instructions for your platform, or
271 use @command{bash} to be sure. Then set @env{CONFIG_SHELL} in your
272 environment to your ``good'' shell prior to running
273 @command{configure}/@command{make}.
275 @command{zsh} is not a fully compliant POSIX shell and will not
276 work when configuring GCC@.
278 @item A POSIX or SVR4 awk
280 Necessary for creating some of the generated source files for GCC@.
281 If in doubt, use a recent GNU awk version, as some of the older ones
282 are broken. GNU awk version 3.1.5 is known to work.
286 Necessary in some circumstances, optional in others. See the
287 host/target specific instructions for your platform for the exact
290 @item gzip version 1.2.4 (or later) or
291 @itemx bzip2 version 1.0.2 (or later)
293 Necessary to uncompress GCC @command{tar} files when source code is
294 obtained via FTP mirror sites.
296 @item GNU make version 3.80 (or later)
298 You must have GNU make installed to build GCC@.
300 @item GNU tar version 1.14 (or later)
302 Necessary (only on some platforms) to untar the source code. Many
303 systems' @command{tar} programs will also work, only try GNU
304 @command{tar} if you have problems.
306 @item Perl version 5.6.1 (or later)
308 Necessary when targetting Darwin, building @samp{libstdc++},
309 and not using @option{--disable-symvers}.
310 Necessary when targetting Solaris 2 with Sun @command{ld} and not using
311 @option{--disable-symvers}. The bundled @command{perl} in Solaris@tie{}8
314 Necessary when regenerating @file{Makefile} dependencies in libiberty.
315 Necessary when regenerating @file{libiberty/functions.texi}.
316 Necessary when generating manpages from Texinfo manuals.
317 Used by various scripts to generate some files included in SVN (mainly
318 Unicode-related and rarely changing) from source tables.
320 @item @command{jar}, or InfoZIP (@command{zip} and @command{unzip})
322 Necessary to build libgcj, the GCJ runtime.
326 Several support libraries are necessary to build GCC, some are required,
327 others optional. While any sufficiently new version of required tools
328 usually work, library requirements are generally stricter. Newer
329 versions may work in some cases, but it's safer to use the exact
330 versions documented. We appreciate bug reports about problems with
331 newer versions, though.
334 @item GNU Multiple Precision Library (GMP) version 4.3.2 (or later)
336 Necessary to build GCC@. If you do not have it installed in your
337 library search path, you will have to configure with the
338 @option{--with-gmp} configure option. See also @option{--with-gmp-lib}
339 and @option{--with-gmp-include}. Alternatively, if a GMP source
340 distribution is found in a subdirectory of your GCC sources named
341 @file{gmp}, it will be built together with GCC@.
343 @item MPFR Library version 2.4.2 (or later)
345 Necessary to build GCC@. It can be downloaded from
346 @uref{http://www.mpfr.org/}. The @option{--with-mpfr} configure
347 option should be used if your MPFR Library is not installed in your
348 default library search path. See also @option{--with-mpfr-lib} and
349 @option{--with-mpfr-include}. Alternatively, if a MPFR source
350 distribution is found in a subdirectory of your GCC sources named
351 @file{mpfr}, it will be built together with GCC@.
353 @item MPC Library version 0.8.1 (or later)
355 Necessary to build GCC@. It can be downloaded from
356 @uref{http://www.multiprecision.org/}. The @option{--with-mpc}
357 configure option should be used if your MPC Library is not installed
358 in your default library search path. See also @option{--with-mpc-lib}
359 and @option{--with-mpc-include}. Alternatively, if an MPC source
360 distribution is found in a subdirectory of your GCC sources named
361 @file{mpc}, it will be built together with GCC@.
363 @item Parma Polyhedra Library (PPL) version 0.11
365 Necessary to build GCC with the Graphite loop optimizations.
366 It can be downloaded from @uref{http://www.cs.unipr.it/ppl/Download/}.
368 The @option{--with-ppl} configure option should be used if PPL is not
369 installed in your default library search path.
371 @item CLooG-PPL version 0.15 or CLooG 0.16
373 Necessary to build GCC with the Graphite loop optimizations. There
374 are two versions available. CLooG-PPL 0.15 as well as CLooG 0.16.
375 The former is the default right now. It can be downloaded from
376 @uref{ftp://gcc.gnu.org/pub/gcc/infrastructure/} as
377 @file{cloog-ppl-0.15.tar.gz}.
379 CLooG 0.16 support is still in testing stage, but will be the
380 default in future GCC releases. It is also available at
381 @uref{ftp://gcc.gnu.org/pub/gcc/infrastructure/} as
382 @file{cloog-0.16.1.tar.gz}. To use it add the additional configure
383 option @option{--enable-cloog-backend=isl}. Even if CLooG 0.16
384 does not use PPL, PPL is still required for Graphite.
386 In both cases @option{--with-cloog} configure option should be used
387 if CLooG is not installed in your default library search path.
391 @heading Tools/packages necessary for modifying GCC
393 @item autoconf version 2.64
394 @itemx GNU m4 version 1.4.6 (or later)
396 Necessary when modifying @file{configure.ac}, @file{aclocal.m4}, etc.@:
397 to regenerate @file{configure} and @file{config.in} files.
399 @item automake version 1.11.1
401 Necessary when modifying a @file{Makefile.am} file to regenerate its
402 associated @file{Makefile.in}.
404 Much of GCC does not use automake, so directly edit the @file{Makefile.in}
405 file. Specifically this applies to the @file{gcc}, @file{intl},
406 @file{libcpp}, @file{libiberty}, @file{libobjc} directories as well
407 as any of their subdirectories.
409 For directories that use automake, GCC requires the latest release in
410 the 1.11 series, which is currently 1.11.1. When regenerating a directory
411 to a newer version, please update all the directories using an older 1.11
412 to the latest released version.
414 @item gettext version 0.14.5 (or later)
416 Needed to regenerate @file{gcc.pot}.
418 @item gperf version 2.7.2 (or later)
420 Necessary when modifying @command{gperf} input files, e.g.@:
421 @file{gcc/cp/cfns.gperf} to regenerate its associated header file, e.g.@:
422 @file{gcc/cp/cfns.h}.
428 Necessary to run the GCC testsuite; see the section on testing for details.
430 @item autogen version 5.5.4 (or later) and
431 @itemx guile version 1.4.1 (or later)
433 Necessary to regenerate @file{fixinc/fixincl.x} from
434 @file{fixinc/inclhack.def} and @file{fixinc/*.tpl}.
436 Necessary to run @samp{make check} for @file{fixinc}.
438 Necessary to regenerate the top level @file{Makefile.in} file from
439 @file{Makefile.tpl} and @file{Makefile.def}.
441 @item Flex version 2.5.4 (or later)
443 Necessary when modifying @file{*.l} files.
445 Necessary to build GCC during development because the generated output
446 files are not included in the SVN repository. They are included in
449 @item Texinfo version 4.7 (or later)
451 Necessary for running @command{makeinfo} when modifying @file{*.texi}
452 files to test your changes.
454 Necessary for running @command{make dvi} or @command{make pdf} to
455 create printable documentation in DVI or PDF format. Texinfo version
456 4.8 or later is required for @command{make pdf}.
458 Necessary to build GCC documentation during development because the
459 generated output files are not included in the SVN repository. They are
460 included in releases.
462 @item @TeX{} (any working version)
464 Necessary for running @command{texi2dvi} and @command{texi2pdf}, which
465 are used when running @command{make dvi} or @command{make pdf} to create
466 DVI or PDF files, respectively.
468 @item SVN (any version)
469 @itemx SSH (any version)
471 Necessary to access the SVN repository. Public releases and weekly
472 snapshots of the development sources are also available via FTP@.
474 @item GNU diffutils version 2.7 (or later)
476 Useful when submitting patches for the GCC source code.
478 @item patch version 2.5.4 (or later)
480 Necessary when applying patches, created with @command{diff}, to one's
486 If you wish to modify @file{.java} files in libjava, you will need to
487 configure with @option{--enable-java-maintainer-mode}, and you will need
488 to have executables named @command{ecj1} and @command{gjavah} in your path.
489 The @command{ecj1} executable should run the Eclipse Java compiler via
490 the GCC-specific entry point. You can download a suitable jar from
491 @uref{ftp://sourceware.org/pub/java/}, or by running the script
492 @command{contrib/download_ecj}.
494 @item antlr.jar version 2.7.1 (or later)
497 If you wish to build the @command{gjdoc} binary in libjava, you will
498 need to have an @file{antlr.jar} library available. The library is
499 searched in system locations but can be configured with
500 @option{--with-antlr-jar=} instead. When configuring with
501 @option{--enable-java-maintainer-mode}, you will need to have one of
502 the executables named @command{cantlr}, @command{runantlr} or
503 @command{antlr} in your path.
512 @uref{./index.html,,Return to the GCC Installation page}
516 @c ***Downloading the source**************************************************
518 @comment node-name, next, previous, up
519 @node Downloading the source, Configuration, Prerequisites, Installing GCC
523 @chapter Downloading GCC
525 @cindex Downloading GCC
526 @cindex Downloading the Source
528 GCC is distributed via @uref{http://gcc.gnu.org/svn.html,,SVN} and FTP
529 tarballs compressed with @command{gzip} or
530 @command{bzip2}. It is possible to download a full distribution or specific
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 full distribution includes the C, C++, Objective-C, Fortran, Java,
537 and Ada (in the case of GCC 3.1 and later) compilers. The full
538 distribution also includes runtime libraries for C++, Objective-C,
539 Fortran, and Java. In GCC 3.0 and later versions, the GNU compiler
540 testsuites are also included in the full distribution.
542 If you choose to download specific components, you must download the core
543 GCC distribution plus any language specific distributions you wish to
544 use. The core distribution includes the C language front end as well as the
545 shared components. Each language has a tarball which includes the language
546 front end as well as the language runtime (when appropriate).
548 Unpack the core distribution as well as any language specific
549 distributions in the same directory.
551 If you also intend to build binutils (either to upgrade an existing
552 installation or for use in place of the corresponding tools of your
553 OS), unpack the binutils distribution either in the same directory or
554 a separate one. In the latter case, add symbolic links to any
555 components of the binutils you intend to build alongside the compiler
556 (@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld},
557 @file{opcodes}, @dots{}) to the directory containing the GCC sources.
559 Likewise the GMP, MPFR and MPC libraries can be automatically built
560 together with GCC. Unpack the GMP, MPFR and/or MPC source
561 distributions in the directory containing the GCC sources and rename
562 their directories to @file{gmp}, @file{mpfr} and @file{mpc},
563 respectively (or use symbolic links with the same name).
570 @uref{./index.html,,Return to the GCC Installation page}
574 @c ***Configuration***********************************************************
576 @comment node-name, next, previous, up
577 @node Configuration, Building, Downloading the source, Installing GCC
581 @chapter Installing GCC: Configuration
583 @cindex Configuration
584 @cindex Installing GCC: Configuration
586 Like most GNU software, GCC must be configured before it can be built.
587 This document describes the recommended configuration procedure
588 for both native and cross targets.
590 We use @var{srcdir} to refer to the toplevel source directory for
591 GCC; we use @var{objdir} to refer to the toplevel build/object directory.
593 If you obtained the sources via SVN, @var{srcdir} must refer to the top
594 @file{gcc} directory, the one where the @file{MAINTAINERS} file can be
595 found, and not its @file{gcc} subdirectory, otherwise the build will fail.
597 If either @var{srcdir} or @var{objdir} is located on an automounted NFS
598 file system, the shell's built-in @command{pwd} command will return
599 temporary pathnames. Using these can lead to various sorts of build
600 problems. To avoid this issue, set the @env{PWDCMD} environment
601 variable to an automounter-aware @command{pwd} command, e.g.,
602 @command{pawd} or @samp{amq -w}, during the configuration and build
605 First, we @strong{highly} recommend that GCC be built into a
606 separate directory from the sources which does @strong{not} reside
607 within the source tree. This is how we generally build GCC; building
608 where @var{srcdir} == @var{objdir} should still work, but doesn't
609 get extensive testing; building where @var{objdir} is a subdirectory
610 of @var{srcdir} is unsupported.
612 If you have previously built GCC in the same directory for a
613 different target machine, do @samp{make distclean} to delete all files
614 that might be invalid. One of the files this deletes is @file{Makefile};
615 if @samp{make distclean} complains that @file{Makefile} does not exist
616 or issues a message like ``don't know how to make distclean'' it probably
617 means that the directory is already suitably clean. However, with the
618 recommended method of building in a separate @var{objdir}, you should
619 simply use a different @var{objdir} for each target.
621 Second, when configuring a native system, either @command{cc} or
622 @command{gcc} must be in your path or you must set @env{CC} in
623 your environment before running configure. Otherwise the configuration
627 Note that the bootstrap compiler and the resulting GCC must be link
628 compatible, else the bootstrap will fail with linker errors about
629 incompatible object file formats. Several multilibed targets are
630 affected by this requirement, see
632 @ref{Specific, host/target specific installation notes}.
635 @uref{specific.html,,host/target specific installation notes}.
644 % @var{srcdir}/configure [@var{options}] [@var{target}]
647 @heading Distributor options
649 If you will be distributing binary versions of GCC, with modifications
650 to the source code, you should use the options described in this
651 section to make clear that your version contains modifications.
654 @item --with-pkgversion=@var{version}
655 Specify a string that identifies your package. You may wish
656 to include a build number or build date. This version string will be
657 included in the output of @command{gcc --version}. This suffix does
658 not replace the default version string, only the @samp{GCC} part.
660 The default value is @samp{GCC}.
662 @item --with-bugurl=@var{url}
663 Specify the URL that users should visit if they wish to report a bug.
664 You are of course welcome to forward bugs reported to you to the FSF,
665 if you determine that they are not bugs in your modifications.
667 The default value refers to the FSF's GCC bug tracker.
671 @heading Target specification
674 GCC has code to correctly determine the correct value for @var{target}
675 for nearly all native systems. Therefore, we highly recommend you do
676 not provide a configure target when configuring a native compiler.
679 @var{target} must be specified as @option{--target=@var{target}}
680 when configuring a cross compiler; examples of valid targets would be
681 m68k-elf, sh-elf, etc.
684 Specifying just @var{target} instead of @option{--target=@var{target}}
685 implies that the host defaults to @var{target}.
689 @heading Options specification
691 Use @var{options} to override several configure time options for
692 GCC@. A list of supported @var{options} follows; @samp{configure
693 --help} may list other options, but those not listed below may not
694 work and should not normally be used.
696 Note that each @option{--enable} option has a corresponding
697 @option{--disable} option and that each @option{--with} option has a
698 corresponding @option{--without} option.
701 @item --prefix=@var{dirname}
702 Specify the toplevel installation
703 directory. This is the recommended way to install the tools into a directory
704 other than the default. The toplevel installation directory defaults to
707 We @strong{highly} recommend against @var{dirname} being the same or a
708 subdirectory of @var{objdir} or vice versa. If specifying a directory
709 beneath a user's home directory tree, some shells will not expand
710 @var{dirname} correctly if it contains the @samp{~} metacharacter; use
713 The following standard @command{autoconf} options are supported. Normally you
714 should not need to use these options.
716 @item --exec-prefix=@var{dirname}
717 Specify the toplevel installation directory for architecture-dependent
718 files. The default is @file{@var{prefix}}.
720 @item --bindir=@var{dirname}
721 Specify the installation directory for the executables called by users
722 (such as @command{gcc} and @command{g++}). The default is
723 @file{@var{exec-prefix}/bin}.
725 @item --libdir=@var{dirname}
726 Specify the installation directory for object code libraries and
727 internal data files of GCC@. The default is @file{@var{exec-prefix}/lib}.
729 @item --libexecdir=@var{dirname}
730 Specify the installation directory for internal executables of GCC@.
731 The default is @file{@var{exec-prefix}/libexec}.
733 @item --with-slibdir=@var{dirname}
734 Specify the installation directory for the shared libgcc library. The
735 default is @file{@var{libdir}}.
737 @item --datarootdir=@var{dirname}
738 Specify the root of the directory tree for read-only architecture-independent
739 data files referenced by GCC@. The default is @file{@var{prefix}/share}.
741 @item --infodir=@var{dirname}
742 Specify the installation directory for documentation in info format.
743 The default is @file{@var{datarootdir}/info}.
745 @item --datadir=@var{dirname}
746 Specify the installation directory for some architecture-independent
747 data files referenced by GCC@. The default is @file{@var{datarootdir}}.
749 @item --docdir=@var{dirname}
750 Specify the installation directory for documentation files (other
751 than Info) for GCC@. The default is @file{@var{datarootdir}/doc}.
753 @item --htmldir=@var{dirname}
754 Specify the installation directory for HTML documentation files.
755 The default is @file{@var{docdir}}.
757 @item --pdfdir=@var{dirname}
758 Specify the installation directory for PDF documentation files.
759 The default is @file{@var{docdir}}.
761 @item --mandir=@var{dirname}
762 Specify the installation directory for manual pages. The default is
763 @file{@var{datarootdir}/man}. (Note that the manual pages are only extracts
764 from the full GCC manuals, which are provided in Texinfo format. The manpages
765 are derived by an automatic conversion process from parts of the full
768 @item --with-gxx-include-dir=@var{dirname}
770 the installation directory for G++ header files. The default depends
771 on other configuration options, and differs between cross and native
774 @item --with-specs=@var{specs}
775 Specify additional command line driver SPECS.
776 This can be useful if you need to turn on a non-standard feature by
777 default without modifying the compiler's source code, for instance
778 @option{--with-specs=%@{!fcommon:%@{!fno-common:-fno-common@}@}}.
780 @xref{Spec Files,, Specifying subprocesses and the switches to pass to them,
781 gcc, Using the GNU Compiler Collection (GCC)},
784 See ``Spec Files'' in the main manual
789 @item --program-prefix=@var{prefix}
790 GCC supports some transformations of the names of its programs when
791 installing them. This option prepends @var{prefix} to the names of
792 programs to install in @var{bindir} (see above). For example, specifying
793 @option{--program-prefix=foo-} would result in @samp{gcc}
794 being installed as @file{/usr/local/bin/foo-gcc}.
796 @item --program-suffix=@var{suffix}
797 Appends @var{suffix} to the names of programs to install in @var{bindir}
798 (see above). For example, specifying @option{--program-suffix=-3.1}
799 would result in @samp{gcc} being installed as
800 @file{/usr/local/bin/gcc-3.1}.
802 @item --program-transform-name=@var{pattern}
803 Applies the @samp{sed} script @var{pattern} to be applied to the names
804 of programs to install in @var{bindir} (see above). @var{pattern} has to
805 consist of one or more basic @samp{sed} editing commands, separated by
806 semicolons. For example, if you want the @samp{gcc} program name to be
807 transformed to the installed program @file{/usr/local/bin/myowngcc} and
808 the @samp{g++} program name to be transformed to
809 @file{/usr/local/bin/gspecial++} without changing other program names,
810 you could use the pattern
811 @option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'}
812 to achieve this effect.
814 All three options can be combined and used together, resulting in more
815 complex conversion patterns. As a basic rule, @var{prefix} (and
816 @var{suffix}) are prepended (appended) before further transformations
817 can happen with a special transformation script @var{pattern}.
819 As currently implemented, this option only takes effect for native
820 builds; cross compiler binaries' names are not transformed even when a
821 transformation is explicitly asked for by one of these options.
823 For native builds, some of the installed programs are also installed
824 with the target alias in front of their name, as in
825 @samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen
826 before the target alias is prepended to the name---so, specifying
827 @option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the
828 resulting binary would be installed as
829 @file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}.
831 As a last shortcoming, none of the installed Ada programs are
832 transformed yet, which will be fixed in some time.
834 @item --with-local-prefix=@var{dirname}
836 installation directory for local include files. The default is
837 @file{/usr/local}. Specify this option if you want the compiler to
838 search directory @file{@var{dirname}/include} for locally installed
839 header files @emph{instead} of @file{/usr/local/include}.
841 You should specify @option{--with-local-prefix} @strong{only} if your
842 site has a different convention (not @file{/usr/local}) for where to put
845 The default value for @option{--with-local-prefix} is @file{/usr/local}
846 regardless of the value of @option{--prefix}. Specifying
847 @option{--prefix} has no effect on which directory GCC searches for
848 local header files. This may seem counterintuitive, but actually it is
851 The purpose of @option{--prefix} is to specify where to @emph{install
852 GCC}. The local header files in @file{/usr/local/include}---if you put
853 any in that directory---are not part of GCC@. They are part of other
854 programs---perhaps many others. (GCC installs its own header files in
855 another directory which is based on the @option{--prefix} value.)
857 Both the local-prefix include directory and the GCC-prefix include
858 directory are part of GCC's ``system include'' directories. Although these
859 two directories are not fixed, they need to be searched in the proper
860 order for the correct processing of the include_next directive. The
861 local-prefix include directory is searched before the GCC-prefix
862 include directory. Another characteristic of system include directories
863 is that pedantic warnings are turned off for headers in these directories.
865 Some autoconf macros add @option{-I @var{directory}} options to the
866 compiler command line, to ensure that directories containing installed
867 packages' headers are searched. When @var{directory} is one of GCC's
868 system include directories, GCC will ignore the option so that system
869 directories continue to be processed in the correct order. This
870 may result in a search order different from what was specified but the
871 directory will still be searched.
873 GCC automatically searches for ordinary libraries using
874 @env{GCC_EXEC_PREFIX}. Thus, when the same installation prefix is
875 used for both GCC and packages, GCC will automatically search for
876 both headers and libraries. This provides a configuration that is
877 easy to use. GCC behaves in a manner similar to that when it is
878 installed as a system compiler in @file{/usr}.
880 Sites that need to install multiple versions of GCC may not want to
881 use the above simple configuration. It is possible to use the
882 @option{--program-prefix}, @option{--program-suffix} and
883 @option{--program-transform-name} options to install multiple versions
884 into a single directory, but it may be simpler to use different prefixes
885 and the @option{--with-local-prefix} option to specify the location of the
886 site-specific files for each version. It will then be necessary for
887 users to specify explicitly the location of local site libraries
888 (e.g., with @env{LIBRARY_PATH}).
890 The same value can be used for both @option{--with-local-prefix} and
891 @option{--prefix} provided it is not @file{/usr}. This can be used
892 to avoid the default search of @file{/usr/local/include}.
894 @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
895 The directory you use for @option{--with-local-prefix} @strong{must not}
896 contain any of the system's standard header files. If it did contain
897 them, certain programs would be miscompiled (including GNU Emacs, on
898 certain targets), because this would override and nullify the header
899 file corrections made by the @command{fixincludes} script.
901 Indications are that people who use this option use it based on mistaken
902 ideas of what it is for. People use it as if it specified where to
903 install part of GCC@. Perhaps they make this assumption because
904 installing GCC creates the directory.
906 @item --with-native-system-header-dir=@var{dirname}
907 Specifies that @var{dirname} is the directory that contains native system
908 header files, rather than @file{/usr/include}. This option is most useful
909 if you are creating a compiler that should be isolated from the system
910 as much as possible. It is most commonly used with the
911 @option{--with-sysroot} option and will cause GCC to search
912 @var{dirname} inside the system root specified by that option.
914 @item --enable-shared[=@var{package}[,@dots{}]]
915 Build shared versions of libraries, if shared libraries are supported on
916 the target platform. Unlike GCC 2.95.x and earlier, shared libraries
917 are enabled by default on all platforms that support shared libraries.
919 If a list of packages is given as an argument, build shared libraries
920 only for the listed packages. For other packages, only static libraries
921 will be built. Package names currently recognized in the GCC tree are
922 @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not
923 @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc},
924 @samp{ada}, @samp{libada}, @samp{libjava}, @samp{libgo}, and @samp{libobjc}.
925 Note @samp{libiberty} does not support shared libraries at all.
927 Use @option{--disable-shared} to build only static libraries. Note that
928 @option{--disable-shared} does not accept a list of package names as
929 argument, only @option{--enable-shared} does.
931 @item @anchor{with-gnu-as}--with-gnu-as
932 Specify that the compiler should assume that the
933 assembler it finds is the GNU assembler. However, this does not modify
934 the rules to find an assembler and will result in confusion if the
935 assembler found is not actually the GNU assembler. (Confusion may also
936 result if the compiler finds the GNU assembler but has not been
937 configured with @option{--with-gnu-as}.) If you have more than one
938 assembler installed on your system, you may want to use this option in
939 connection with @option{--with-as=@var{pathname}} or
940 @option{--with-build-time-tools=@var{pathname}}.
942 The following systems are the only ones where it makes a difference
943 whether you use the GNU assembler. On any other system,
944 @option{--with-gnu-as} has no effect.
947 @item @samp{hppa1.0-@var{any}-@var{any}}
948 @item @samp{hppa1.1-@var{any}-@var{any}}
949 @item @samp{sparc-sun-solaris2.@var{any}}
950 @item @samp{sparc64-@var{any}-solaris2.@var{any}}
953 @item @anchor{with-as}--with-as=@var{pathname}
954 Specify that the compiler should use the assembler pointed to by
955 @var{pathname}, rather than the one found by the standard rules to find
956 an assembler, which are:
959 Unless GCC is being built with a cross compiler, check the
960 @file{@var{libexec}/gcc/@var{target}/@var{version}} directory.
961 @var{libexec} defaults to @file{@var{exec-prefix}/libexec};
962 @var{exec-prefix} defaults to @var{prefix}, which
963 defaults to @file{/usr/local} unless overridden by the
964 @option{--prefix=@var{pathname}} switch described above. @var{target}
965 is the target system triple, such as @samp{sparc-sun-solaris2.7}, and
966 @var{version} denotes the GCC version, such as 3.0.
969 If the target system is the same that you are building on, check
970 operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
974 Check in the @env{PATH} for a tool whose name is prefixed by the
975 target system triple.
978 Check in the @env{PATH} for a tool whose name is not prefixed by the
979 target system triple, if the host and target system triple are
980 the same (in other words, we use a host tool if it can be used for
984 You may want to use @option{--with-as} if no assembler
985 is installed in the directories listed above, or if you have multiple
986 assemblers installed and want to choose one that is not found by the
989 @item @anchor{with-gnu-ld}--with-gnu-ld
990 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
993 @item --with-ld=@var{pathname}
994 Same as @uref{#with-as,,@option{--with-as}}
998 Specify that stabs debugging
999 information should be used instead of whatever format the host normally
1000 uses. Normally GCC uses the same debug format as the host system.
1002 On MIPS based systems and on Alphas, you must specify whether you want
1003 GCC to create the normal ECOFF debugging format, or to use BSD-style
1004 stabs passed through the ECOFF symbol table. The normal ECOFF debug
1005 format cannot fully handle languages other than C@. BSD stabs format can
1006 handle other languages, but it only works with the GNU debugger GDB@.
1008 Normally, GCC uses the ECOFF debugging format by default; if you
1009 prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@.
1011 No matter which default you choose when you configure GCC, the user
1012 can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
1013 the debug format for a particular compilation.
1015 @option{--with-stabs} is meaningful on the ISC system on the 386, also, if
1016 @option{--with-gas} is used. It selects use of stabs debugging
1017 information embedded in COFF output. This kind of debugging information
1018 supports C++ well; ordinary COFF debugging information does not.
1020 @option{--with-stabs} is also meaningful on 386 systems running SVR4. It
1021 selects use of stabs debugging information embedded in ELF output. The
1022 C++ compiler currently (2.6.0) does not support the DWARF debugging
1023 information normally used on 386 SVR4 platforms; stabs provide a
1024 workable alternative. This requires gas and gdb, as the normal SVR4
1025 tools can not generate or interpret stabs.
1027 @item --with-tls=@var{dialect}
1028 Specify the default TLS dialect, for systems were there is a choice.
1029 For ARM targets, possible values for @var{dialect} are @code{gnu} or
1030 @code{gnu2}, which select between the original GNU dialect and the GNU TLS
1031 descriptor-based dialect.
1033 @item --disable-multilib
1034 Specify that multiple target
1035 libraries to support different target variants, calling
1036 conventions, etc.@: should not be built. The default is to build a
1037 predefined set of them.
1039 Some targets provide finer-grained control over which multilibs are built
1040 (e.g., @option{--disable-softfloat}):
1043 fpu, 26bit, underscore, interwork, biendian, nofmult.
1046 softfloat, m68881, m68000, m68020.
1049 single-float, biendian, softfloat.
1051 @item powerpc*-*-*, rs6000*-*-*
1052 aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
1057 @item --with-multilib-list=@var{list}
1058 @itemx --without-multilib-list
1059 Specify what multilibs to build.
1060 Currently only implemented for sh*-*-* and x86-64-*-linux*.
1064 @var{list} is a comma separated list of CPU names. These must be of the
1065 form @code{sh*} or @code{m*} (in which case they match the compiler option
1066 for that processor). The list should not contain any endian options -
1067 these are handled by @option{--with-endian}.
1069 If @var{list} is empty, then there will be no multilibs for extra
1070 processors. The multilib for the secondary endian remains enabled.
1072 As a special case, if an entry in the list starts with a @code{!}
1073 (exclamation point), then it is added to the list of excluded multilibs.
1074 Entries of this sort should be compatible with @samp{MULTILIB_EXCLUDES}
1075 (once the leading @code{!} has been stripped).
1077 If @option{--with-multilib-list} is not given, then a default set of
1078 multilibs is selected based on the value of @option{--target}. This is
1079 usually the complete set of libraries, but some targets imply a more
1082 Example 1: to configure a compiler for SH4A only, but supporting both
1083 endians, with little endian being the default:
1085 --with-cpu=sh4a --with-endian=little,big --with-multilib-list=
1088 Example 2: to configure a compiler for both SH4A and SH4AL-DSP, but with
1089 only little endian SH4AL:
1091 --with-cpu=sh4a --with-endian=little,big \
1092 --with-multilib-list=sh4al,!mb/m4al
1095 @item x86-64-*-linux*
1096 @var{list} is a comma separated list of @code{m32}, @code{m64} and
1097 @code{mx32} to enable 32-bit, 64-bit and x32 run-time libraries,
1098 respectively. If @var{list} is empty, then there will be no multilibs
1099 and only the default run-time library will be enabled.
1101 If @option{--with-multilib-list} is not given, then only 32-bit and
1102 64-bit run-time libraries will be enabled.
1105 @item --with-endian=@var{endians}
1106 Specify what endians to use.
1107 Currently only implemented for sh*-*-*.
1109 @var{endians} may be one of the following:
1112 Use big endian exclusively.
1114 Use little endian exclusively.
1116 Use big endian by default. Provide a multilib for little endian.
1118 Use little endian by default. Provide a multilib for big endian.
1121 @item --enable-threads
1122 Specify that the target
1123 supports threads. This affects the Objective-C compiler and runtime
1124 library, and exception handling for other languages like C++ and Java.
1125 On some systems, this is the default.
1127 In general, the best (and, in many cases, the only known) threading
1128 model available will be configured for use. Beware that on some
1129 systems, GCC has not been taught what threading models are generally
1130 available for the system. In this case, @option{--enable-threads} is an
1131 alias for @option{--enable-threads=single}.
1133 @item --disable-threads
1134 Specify that threading support should be disabled for the system.
1135 This is an alias for @option{--enable-threads=single}.
1137 @item --enable-threads=@var{lib}
1139 @var{lib} is the thread support library. This affects the Objective-C
1140 compiler and runtime library, and exception handling for other languages
1141 like C++ and Java. The possibilities for @var{lib} are:
1149 LynxOS thread support.
1151 MIPS SDE thread support.
1153 This is an alias for @samp{single}.
1155 Generic POSIX/Unix98 thread support.
1157 RTEMS thread support.
1159 Disable thread support, should work for all platforms.
1163 VxWorks thread support.
1165 Microsoft Win32 API thread support.
1169 Specify that the target supports TLS (Thread Local Storage). Usually
1170 configure can correctly determine if TLS is supported. In cases where
1171 it guesses incorrectly, TLS can be explicitly enabled or disabled with
1172 @option{--enable-tls} or @option{--disable-tls}. This can happen if
1173 the assembler supports TLS but the C library does not, or if the
1174 assumptions made by the configure test are incorrect.
1177 Specify that the target does not support TLS.
1178 This is an alias for @option{--enable-tls=no}.
1180 @item --with-cpu=@var{cpu}
1181 @itemx --with-cpu-32=@var{cpu}
1182 @itemx --with-cpu-64=@var{cpu}
1183 Specify which cpu variant the compiler should generate code for by default.
1184 @var{cpu} will be used as the default value of the @option{-mcpu=} switch.
1185 This option is only supported on some targets, including ARM, i386, M68k,
1186 PowerPC, and SPARC@. The @option{--with-cpu-32} and
1187 @option{--with-cpu-64} options specify separate default CPUs for
1188 32-bit and 64-bit modes; these options are only supported for i386,
1191 @item --with-schedule=@var{cpu}
1192 @itemx --with-arch=@var{cpu}
1193 @itemx --with-arch-32=@var{cpu}
1194 @itemx --with-arch-64=@var{cpu}
1195 @itemx --with-tune=@var{cpu}
1196 @itemx --with-tune-32=@var{cpu}
1197 @itemx --with-tune-64=@var{cpu}
1198 @itemx --with-abi=@var{abi}
1199 @itemx --with-fpu=@var{type}
1200 @itemx --with-float=@var{type}
1201 These configure options provide default values for the @option{-mschedule=},
1202 @option{-march=}, @option{-mtune=}, @option{-mabi=}, and @option{-mfpu=}
1203 options and for @option{-mhard-float} or @option{-msoft-float}. As with
1204 @option{--with-cpu}, which switches will be accepted and acceptable values
1205 of the arguments depend on the target.
1207 @item --with-mode=@var{mode}
1208 Specify if the compiler should default to @option{-marm} or @option{-mthumb}.
1209 This option is only supported on ARM targets.
1211 @item --with-stack-offset=@var{num}
1212 This option sets the default for the -mstack-offset=@var{num} option,
1213 and will thus generally also control the setting of this option for
1214 libraries. This option is only supported on Epiphany targets.
1216 @item --with-fpmath=@var{isa}
1217 This options sets @option{-mfpmath=sse} by default and specifies the default
1218 ISA for floating-point arithmetics. You can select either @samp{sse} which
1219 enables @option{-msse2} or @samp{avx} which enables @option{-mavx} by default.
1220 This option is only supported on i386 and x86-64 targets.
1222 @item --with-divide=@var{type}
1223 Specify how the compiler should generate code for checking for
1224 division by zero. This option is only supported on the MIPS target.
1225 The possibilities for @var{type} are:
1228 Division by zero checks use conditional traps (this is the default on
1229 systems that support conditional traps).
1231 Division by zero checks use the break instruction.
1234 @c If you make --with-llsc the default for additional targets,
1235 @c update the --with-llsc description in the MIPS section below.
1238 On MIPS targets, make @option{-mllsc} the default when no
1239 @option{-mno-lsc} option is passed. This is the default for
1240 Linux-based targets, as the kernel will emulate them if the ISA does
1243 @item --without-llsc
1244 On MIPS targets, make @option{-mno-llsc} the default when no
1245 @option{-mllsc} option is passed.
1248 On MIPS targets, make @option{-msynci} the default when no
1249 @option{-mno-synci} option is passed.
1251 @item --without-synci
1252 On MIPS targets, make @option{-mno-synci} the default when no
1253 @option{-msynci} option is passed. This is the default.
1255 @item --with-mips-plt
1256 On MIPS targets, make use of copy relocations and PLTs.
1257 These features are extensions to the traditional
1258 SVR4-based MIPS ABIs and require support from GNU binutils
1259 and the runtime C library.
1261 @item --enable-__cxa_atexit
1262 Define if you want to use __cxa_atexit, rather than atexit, to
1263 register C++ destructors for local statics and global objects.
1264 This is essential for fully standards-compliant handling of
1265 destructors, but requires __cxa_atexit in libc. This option is currently
1266 only available on systems with GNU libc. When enabled, this will cause
1267 @option{-fuse-cxa-atexit} to be passed by default.
1269 @item --enable-gnu-indirect-function
1270 Define if you want to enable the @code{ifunc} attribute. This option is
1271 currently only available on systems with GNU libc on certain targets.
1273 @item --enable-target-optspace
1275 libraries should be optimized for code space instead of code speed.
1276 This is the default for the m32r platform.
1278 @item --with-cpp-install-dir=@var{dirname}
1279 Specify that the user visible @command{cpp} program should be installed
1280 in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
1282 @item --enable-comdat
1283 Enable COMDAT group support. This is primarily used to override the
1284 automatically detected value.
1286 @item --enable-initfini-array
1287 Force the use of sections @code{.init_array} and @code{.fini_array}
1288 (instead of @code{.init} and @code{.fini}) for constructors and
1289 destructors. Option @option{--disable-initfini-array} has the
1290 opposite effect. If neither option is specified, the configure script
1291 will try to guess whether the @code{.init_array} and
1292 @code{.fini_array} sections are supported and, if they are, use them.
1294 @item --enable-build-with-cxx
1295 Build GCC using a C++ compiler rather than a C compiler. This is an
1296 experimental option which may become the default in a later release.
1298 @item --enable-build-poststage1-with-cxx
1299 When bootstrapping, build stages 2 and 3 of GCC using a C++ compiler
1300 rather than a C compiler. Stage 1 is still built with a C compiler.
1301 This is enabled by default and may be disabled using
1302 @option{--disable-build-poststage1-with-cxx}.
1304 @item --enable-maintainer-mode
1305 The build rules that regenerate the Autoconf and Automake output files as
1306 well as the GCC master message catalog @file{gcc.pot} are normally
1307 disabled. This is because it can only be rebuilt if the complete source
1308 tree is present. If you have changed the sources and want to rebuild the
1309 catalog, configuring with @option{--enable-maintainer-mode} will enable
1310 this. Note that you need a recent version of the @code{gettext} tools
1313 @item --disable-bootstrap
1314 For a native build, the default configuration is to perform
1315 a 3-stage bootstrap of the compiler when @samp{make} is invoked,
1316 testing that GCC can compile itself correctly. If you want to disable
1317 this process, you can configure with @option{--disable-bootstrap}.
1319 @item --enable-bootstrap
1320 In special cases, you may want to perform a 3-stage build
1321 even if the target and host triplets are different.
1322 This is possible when the host can run code compiled for
1323 the target (e.g.@: host is i686-linux, target is i486-linux).
1324 Starting from GCC 4.2, to do this you have to configure explicitly
1325 with @option{--enable-bootstrap}.
1327 @item --enable-generated-files-in-srcdir
1328 Neither the .c and .h files that are generated from Bison and flex nor the
1329 info manuals and man pages that are built from the .texi files are present
1330 in the SVN development tree. When building GCC from that development tree,
1331 or from one of our snapshots, those generated files are placed in your
1332 build directory, which allows for the source to be in a readonly
1335 If you configure with @option{--enable-generated-files-in-srcdir} then those
1336 generated files will go into the source directory. This is mainly intended
1337 for generating release or prerelease tarballs of the GCC sources, since it
1338 is not a requirement that the users of source releases to have flex, Bison,
1341 @item --enable-version-specific-runtime-libs
1343 that runtime libraries should be installed in the compiler specific
1344 subdirectory (@file{@var{libdir}/gcc}) rather than the usual places. In
1345 addition, @samp{libstdc++}'s include files will be installed into
1346 @file{@var{libdir}} unless you overruled it by using
1347 @option{--with-gxx-include-dir=@var{dirname}}. Using this option is
1348 particularly useful if you intend to use several versions of GCC in
1349 parallel. This is currently supported by @samp{libgfortran},
1350 @samp{libjava}, @samp{libmudflap}, @samp{libstdc++}, and @samp{libobjc}.
1352 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
1353 Specify that only a particular subset of compilers and
1354 their runtime libraries should be built. For a list of valid values for
1355 @var{langN} you can issue the following command in the
1356 @file{gcc} directory of your GCC source tree:@*
1358 grep language= */config-lang.in
1360 Currently, you can use any of the following:
1361 @code{all}, @code{ada}, @code{c}, @code{c++}, @code{fortran},
1362 @code{go}, @code{java}, @code{objc}, @code{obj-c++}.
1363 Building the Ada compiler has special requirements, see below.
1364 If you do not pass this flag, or specify the option @code{all}, then all
1365 default languages available in the @file{gcc} sub-tree will be configured.
1366 Ada, Go and Objective-C++ are not default languages; the rest are.
1368 @item --enable-stage1-languages=@var{lang1},@var{lang2},@dots{}
1369 Specify that a particular subset of compilers and their runtime
1370 libraries should be built with the system C compiler during stage 1 of
1371 the bootstrap process, rather than only in later stages with the
1372 bootstrapped C compiler. The list of valid values is the same as for
1373 @option{--enable-languages}, and the option @code{all} will select all
1374 of the languages enabled by @option{--enable-languages}. This option is
1375 primarily useful for GCC development; for instance, when a development
1376 version of the compiler cannot bootstrap due to compiler bugs, or when
1377 one is debugging front ends other than the C front end. When this
1378 option is used, one can then build the target libraries for the
1379 specified languages with the stage-1 compiler by using @command{make
1380 stage1-bubble all-target}, or run the testsuite on the stage-1 compiler
1381 for the specified languages using @command{make stage1-start check-gcc}.
1383 @item --disable-libada
1384 Specify that the run-time libraries and tools used by GNAT should not
1385 be built. This can be useful for debugging, or for compatibility with
1386 previous Ada build procedures, when it was required to explicitly
1387 do a @samp{make -C gcc gnatlib_and_tools}.
1389 @item --disable-libssp
1390 Specify that the run-time libraries for stack smashing protection
1391 should not be built.
1393 @item --disable-libquadmath
1394 Specify that the GCC quad-precision math library should not be built.
1395 On some systems, the library is required to be linkable when building
1396 the Fortran front end, unless @option{--disable-libquadmath-support}
1399 @item --disable-libquadmath-support
1400 Specify that the Fortran front end and @code{libgfortran} do not add
1401 support for @code{libquadmath} on systems supporting it.
1403 @item --disable-libgomp
1404 Specify that the run-time libraries used by GOMP should not be built.
1407 Specify that the compiler should
1408 use DWARF 2 debugging information as the default.
1410 @item --enable-targets=all
1411 @itemx --enable-targets=@var{target_list}
1412 Some GCC targets, e.g.@: powerpc64-linux, build bi-arch compilers.
1413 These are compilers that are able to generate either 64-bit or 32-bit
1414 code. Typically, the corresponding 32-bit target, e.g.@:
1415 powerpc-linux for powerpc64-linux, only generates 32-bit code. This
1416 option enables the 32-bit target to be a bi-arch compiler, which is
1417 useful when you want a bi-arch compiler that defaults to 32-bit, and
1418 you are building a bi-arch or multi-arch binutils in a combined tree.
1419 On mips-linux, this will build a tri-arch compiler (ABI o32/n32/64),
1421 Currently, this option only affects sparc-linux, powerpc-linux, x86-linux,
1422 mips-linux and s390-linux.
1424 @item --enable-secureplt
1425 This option enables @option{-msecure-plt} by default for powerpc-linux.
1427 @xref{RS/6000 and PowerPC Options,, RS/6000 and PowerPC Options, gcc,
1428 Using the GNU Compiler Collection (GCC)},
1431 See ``RS/6000 and PowerPC Options'' in the main manual
1435 This option enables @option{-mcld} by default for 32-bit x86 targets.
1437 @xref{i386 and x86-64 Options,, i386 and x86-64 Options, gcc,
1438 Using the GNU Compiler Collection (GCC)},
1441 See ``i386 and x86-64 Options'' in the main manual
1444 @item --enable-win32-registry
1445 @itemx --enable-win32-registry=@var{key}
1446 @itemx --disable-win32-registry
1447 The @option{--enable-win32-registry} option enables Microsoft Windows-hosted GCC
1448 to look up installations paths in the registry using the following key:
1451 @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
1454 @var{key} defaults to GCC version number, and can be overridden by the
1455 @option{--enable-win32-registry=@var{key}} option. Vendors and distributors
1456 who use custom installers are encouraged to provide a different key,
1457 perhaps one comprised of vendor name and GCC version number, to
1458 avoid conflict with existing installations. This feature is enabled
1459 by default, and can be disabled by @option{--disable-win32-registry}
1460 option. This option has no effect on the other hosts.
1463 Specify that the machine does not have a floating point unit. This
1464 option only applies to @samp{m68k-sun-sunos@var{n}}. On any other
1465 system, @option{--nfp} has no effect.
1467 @item --enable-werror
1468 @itemx --disable-werror
1469 @itemx --enable-werror=yes
1470 @itemx --enable-werror=no
1471 When you specify this option, it controls whether certain files in the
1472 compiler are built with @option{-Werror} in bootstrap stage2 and later.
1473 If you don't specify it, @option{-Werror} is turned on for the main
1474 development trunk. However it defaults to off for release branches and
1475 final releases. The specific files which get @option{-Werror} are
1476 controlled by the Makefiles.
1478 @item --enable-checking
1479 @itemx --enable-checking=@var{list}
1480 When you specify this option, the compiler is built to perform internal
1481 consistency checks of the requested complexity. This does not change the
1482 generated code, but adds error checking within the compiler. This will
1483 slow down the compiler and may only work properly if you are building
1484 the compiler with GCC@. This is @samp{yes} by default when building
1485 from SVN or snapshots, but @samp{release} for releases. The default
1486 for building the stage1 compiler is @samp{yes}. More control
1487 over the checks may be had by specifying @var{list}. The categories of
1488 checks available are @samp{yes} (most common checks
1489 @samp{assert,misc,tree,gc,rtlflag,runtime}), @samp{no} (no checks at
1490 all), @samp{all} (all but @samp{valgrind}), @samp{release} (cheapest
1491 checks @samp{assert,runtime}) or @samp{none} (same as @samp{no}).
1492 Individual checks can be enabled with these flags @samp{assert},
1493 @samp{df}, @samp{fold}, @samp{gc}, @samp{gcac} @samp{misc}, @samp{rtl},
1494 @samp{rtlflag}, @samp{runtime}, @samp{tree}, and @samp{valgrind}.
1496 The @samp{valgrind} check requires the external @command{valgrind}
1497 simulator, available from @uref{http://valgrind.org/}. The
1498 @samp{df}, @samp{rtl}, @samp{gcac} and @samp{valgrind} checks are very expensive.
1499 To disable all checking, @samp{--disable-checking} or
1500 @samp{--enable-checking=none} must be explicitly requested. Disabling
1501 assertions will make the compiler and runtime slightly faster but
1502 increase the risk of undetected internal errors causing wrong code to be
1505 @item --disable-stage1-checking
1506 @itemx --enable-stage1-checking
1507 @itemx --enable-stage1-checking=@var{list}
1508 If no @option{--enable-checking} option is specified the stage1
1509 compiler will be built with @samp{yes} checking enabled, otherwise
1510 the stage1 checking flags are the same as specified by
1511 @option{--enable-checking}. To build the stage1 compiler with
1512 different checking options use @option{--enable-stage1-checking}.
1513 The list of checking options is the same as for @option{--enable-checking}.
1514 If your system is too slow or too small to bootstrap a released compiler
1515 with checking for stage1 enabled, you can use @samp{--disable-stage1-checking}
1516 to disable checking for the stage1 compiler.
1518 @item --enable-coverage
1519 @itemx --enable-coverage=@var{level}
1520 With this option, the compiler is built to collect self coverage
1521 information, every time it is run. This is for internal development
1522 purposes, and only works when the compiler is being built with gcc. The
1523 @var{level} argument controls whether the compiler is built optimized or
1524 not, values are @samp{opt} and @samp{noopt}. For coverage analysis you
1525 want to disable optimization, for performance analysis you want to
1526 enable optimization. When coverage is enabled, the default level is
1527 without optimization.
1529 @item --enable-gather-detailed-mem-stats
1530 When this option is specified more detailed information on memory
1531 allocation is gathered. This information is printed when using
1532 @option{-fmem-report}.
1535 @itemx --with-gc=@var{choice}
1536 With this option you can specify the garbage collector implementation
1537 used during the compilation process. @var{choice} can be one of
1538 @samp{page} and @samp{zone}, where @samp{page} is the default.
1541 @itemx --disable-nls
1542 The @option{--enable-nls} option enables Native Language Support (NLS),
1543 which lets GCC output diagnostics in languages other than American
1544 English. Native Language Support is enabled by default if not doing a
1545 canadian cross build. The @option{--disable-nls} option disables NLS@.
1547 @item --with-included-gettext
1548 If NLS is enabled, the @option{--with-included-gettext} option causes the build
1549 procedure to prefer its copy of GNU @command{gettext}.
1551 @item --with-catgets
1552 If NLS is enabled, and if the host lacks @code{gettext} but has the
1553 inferior @code{catgets} interface, the GCC build procedure normally
1554 ignores @code{catgets} and instead uses GCC's copy of the GNU
1555 @code{gettext} library. The @option{--with-catgets} option causes the
1556 build procedure to use the host's @code{catgets} in this situation.
1558 @item --with-libiconv-prefix=@var{dir}
1559 Search for libiconv header files in @file{@var{dir}/include} and
1560 libiconv library files in @file{@var{dir}/lib}.
1562 @item --enable-obsolete
1563 Enable configuration for an obsoleted system. If you attempt to
1564 configure GCC for a system (build, host, or target) which has been
1565 obsoleted, and you do not specify this flag, configure will halt with an
1568 All support for systems which have been obsoleted in one release of GCC
1569 is removed entirely in the next major release, unless someone steps
1570 forward to maintain the port.
1572 @item --enable-decimal-float
1573 @itemx --enable-decimal-float=yes
1574 @itemx --enable-decimal-float=no
1575 @itemx --enable-decimal-float=bid
1576 @itemx --enable-decimal-float=dpd
1577 @itemx --disable-decimal-float
1578 Enable (or disable) support for the C decimal floating point extension
1579 that is in the IEEE 754-2008 standard. This is enabled by default only
1580 on PowerPC, i386, and x86_64 GNU/Linux systems. Other systems may also
1581 support it, but require the user to specifically enable it. You can
1582 optionally control which decimal floating point format is used (either
1583 @samp{bid} or @samp{dpd}). The @samp{bid} (binary integer decimal)
1584 format is default on i386 and x86_64 systems, and the @samp{dpd}
1585 (densely packed decimal) format is default on PowerPC systems.
1587 @item --enable-fixed-point
1588 @itemx --disable-fixed-point
1589 Enable (or disable) support for C fixed-point arithmetic.
1590 This option is enabled by default for some targets (such as MIPS) which
1591 have hardware-support for fixed-point operations. On other targets, you
1592 may enable this option manually.
1594 @item --with-long-double-128
1595 Specify if @code{long double} type should be 128-bit by default on selected
1596 GNU/Linux architectures. If using @code{--without-long-double-128},
1597 @code{long double} will be by default 64-bit, the same as @code{double} type.
1598 When neither of these configure options are used, the default will be
1599 128-bit @code{long double} when built against GNU C Library 2.4 and later,
1600 64-bit @code{long double} otherwise.
1602 @item --with-gmp=@var{pathname}
1603 @itemx --with-gmp-include=@var{pathname}
1604 @itemx --with-gmp-lib=@var{pathname}
1605 @itemx --with-mpfr=@var{pathname}
1606 @itemx --with-mpfr-include=@var{pathname}
1607 @itemx --with-mpfr-lib=@var{pathname}
1608 @itemx --with-mpc=@var{pathname}
1609 @itemx --with-mpc-include=@var{pathname}
1610 @itemx --with-mpc-lib=@var{pathname}
1611 If you do not have GMP (the GNU Multiple Precision library), the MPFR
1612 library and/or the MPC library installed in a standard location and
1613 you want to build GCC, you can explicitly specify the directory where
1614 they are installed (@samp{--with-gmp=@var{gmpinstalldir}},
1615 @samp{--with-mpfr=@/@var{mpfrinstalldir}},
1616 @samp{--with-mpc=@/@var{mpcinstalldir}}). The
1617 @option{--with-gmp=@/@var{gmpinstalldir}} option is shorthand for
1618 @option{--with-gmp-lib=@/@var{gmpinstalldir}/lib} and
1619 @option{--with-gmp-include=@/@var{gmpinstalldir}/include}. Likewise the
1620 @option{--with-mpfr=@/@var{mpfrinstalldir}} option is shorthand for
1621 @option{--with-mpfr-lib=@/@var{mpfrinstalldir}/lib} and
1622 @option{--with-mpfr-include=@/@var{mpfrinstalldir}/include}, also the
1623 @option{--with-mpc=@/@var{mpcinstalldir}} option is shorthand for
1624 @option{--with-mpc-lib=@/@var{mpcinstalldir}/lib} and
1625 @option{--with-mpc-include=@/@var{mpcinstalldir}/include}. If these
1626 shorthand assumptions are not correct, you can use the explicit
1627 include and lib options directly. You might also need to ensure the
1628 shared libraries can be found by the dynamic linker when building and
1629 using GCC, for example by setting the runtime shared library path
1630 variable (@env{LD_LIBRARY_PATH} on GNU/Linux and Solaris systems).
1632 These flags are applicable to the host platform only. When building
1633 a cross compiler, they will not be used to configure target libraries.
1635 @item --with-ppl=@var{pathname}
1636 @itemx --with-ppl-include=@var{pathname}
1637 @itemx --with-ppl-lib=@var{pathname}
1638 @itemx --with-cloog=@var{pathname}
1639 @itemx --with-cloog-include=@var{pathname}
1640 @itemx --with-cloog-lib=@var{pathname}
1641 If you do not have PPL (the Parma Polyhedra Library) and the CLooG
1642 libraries installed in a standard location and you want to build GCC,
1643 you can explicitly specify the directory where they are installed
1644 (@samp{--with-ppl=@/@var{pplinstalldir}},
1645 @samp{--with-cloog=@/@var{clooginstalldir}}). The
1646 @option{--with-ppl=@/@var{pplinstalldir}} option is shorthand for
1647 @option{--with-ppl-lib=@/@var{pplinstalldir}/lib} and
1648 @option{--with-ppl-include=@/@var{pplinstalldir}/include}. Likewise the
1649 @option{--with-cloog=@/@var{clooginstalldir}} option is shorthand for
1650 @option{--with-cloog-lib=@/@var{clooginstalldir}/lib} and
1651 @option{--with-cloog-include=@/@var{clooginstalldir}/include}. If these
1652 shorthand assumptions are not correct, you can use the explicit
1653 include and lib options directly.
1655 These flags are applicable to the host platform only. When building
1656 a cross compiler, they will not be used to configure target libraries.
1658 @item --with-host-libstdcxx=@var{linker-args}
1659 If you are linking with a static copy of PPL, you can use this option
1660 to specify how the linker should find the standard C++ library used
1661 internally by PPL. Typical values of @var{linker-args} might be
1662 @samp{-lstdc++} or @samp{-Wl,-Bstatic,-lstdc++,-Bdynamic -lm}. If you are
1663 linking with a shared copy of PPL, you probably do not need this
1664 option; shared library dependencies will cause the linker to search
1665 for the standard C++ library automatically.
1667 @item --with-stage1-ldflags=@var{flags}
1668 This option may be used to set linker flags to be used when linking
1669 stage 1 of GCC. These are also used when linking GCC if configured with
1670 @option{--disable-bootstrap}. By default no special flags are used.
1672 @item --with-stage1-libs=@var{libs}
1673 This option may be used to set libraries to be used when linking stage 1
1674 of GCC. These are also used when linking GCC if configured with
1675 @option{--disable-bootstrap}. The default is the argument to
1676 @option{--with-host-libstdcxx}, if specified.
1678 @item --with-boot-ldflags=@var{flags}
1679 This option may be used to set linker flags to be used when linking
1680 stage 2 and later when bootstrapping GCC. If neither --with-boot-libs
1681 nor --with-host-libstdcxx is set to a value, then the default is
1682 @samp{-static-libstdc++ -static-libgcc}.
1684 @item --with-boot-libs=@var{libs}
1685 This option may be used to set libraries to be used when linking stage 2
1686 and later when bootstrapping GCC. The default is the argument to
1687 @option{--with-host-libstdcxx}, if specified.
1689 @item --with-debug-prefix-map=@var{map}
1690 Convert source directory names using @option{-fdebug-prefix-map} when
1691 building runtime libraries. @samp{@var{map}} is a space-separated
1692 list of maps of the form @samp{@var{old}=@var{new}}.
1694 @item --enable-linker-build-id
1695 Tells GCC to pass @option{--build-id} option to the linker for all final
1696 links (links performed without the @option{-r} or @option{--relocatable}
1697 option), if the linker supports it. If you specify
1698 @option{--enable-linker-build-id}, but your linker does not
1699 support @option{--build-id} option, a warning is issued and the
1700 @option{--enable-linker-build-id} option is ignored. The default is off.
1702 @item --with-linker-hash-style=@var{choice}
1703 Tells GCC to pass @option{--hash-style=@var{choice}} option to the
1704 linker for all final links. @var{choice} can be one of
1705 @samp{sysv}, @samp{gnu}, and @samp{both} where @samp{sysv} is the default.
1707 @item --enable-gnu-unique-object
1708 @itemx --disable-gnu-unique-object
1709 Tells GCC to use the gnu_unique_object relocation for C++ template
1710 static data members and inline function local statics. Enabled by
1711 default for a native toolchain with an assembler that accepts it and
1712 GLIBC 2.11 or above, otherwise disabled.
1715 @itemx --disable-lto
1716 Enable support for link-time optimization (LTO). This is enabled by
1717 default, and may be disabled using @option{--disable-lto}.
1719 @item --with-plugin-ld=@var{pathname}
1720 Enable an alternate linker to be used at link-time optimization (LTO)
1721 link time when @option{-fuse-linker-plugin} is enabled.
1722 This linker should have plugin support such as gold starting with
1723 version 2.20 or GNU ld starting with version 2.21.
1724 See @option{-fuse-linker-plugin} for details.
1727 @subheading Cross-Compiler-Specific Options
1728 The following options only apply to building cross compilers.
1731 @item --with-sysroot
1732 @itemx --with-sysroot=@var{dir}
1733 Tells GCC to consider @var{dir} as the root of a tree that contains
1734 (a subset of) the root filesystem of the target operating system.
1735 Target system headers, libraries and run-time object files will be
1736 searched in there. More specifically, this acts as if
1737 @option{--sysroot=@var{dir}} was added to the default options of the built
1738 compiler. The specified directory is not copied into the
1739 install tree, unlike the options @option{--with-headers} and
1740 @option{--with-libs} that this option obsoletes. The default value,
1741 in case @option{--with-sysroot} is not given an argument, is
1742 @option{$@{gcc_tooldir@}/sys-root}. If the specified directory is a
1743 subdirectory of @option{$@{exec_prefix@}}, then it will be found relative to
1744 the GCC binaries if the installation tree is moved.
1746 This option affects the system root for the compiler used to build
1747 target libraries (which runs on the build system) and the compiler newly
1748 installed with @code{make install}; it does not affect the compiler which is
1749 used to build GCC itself.
1751 If you specify the @option{--with-native-system-header-dir=@var{dirname}}
1752 option then the compiler will search that directory within @var{dirname} for
1753 native system headers rather than the default @file{/usr/include}.
1755 @item --with-build-sysroot
1756 @itemx --with-build-sysroot=@var{dir}
1757 Tells GCC to consider @var{dir} as the system root (see
1758 @option{--with-sysroot}) while building target libraries, instead of
1759 the directory specified with @option{--with-sysroot}. This option is
1760 only useful when you are already using @option{--with-sysroot}. You
1761 can use @option{--with-build-sysroot} when you are configuring with
1762 @option{--prefix} set to a directory that is different from the one in
1763 which you are installing GCC and your target libraries.
1765 This option affects the system root for the compiler used to build
1766 target libraries (which runs on the build system); it does not affect
1767 the compiler which is 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-headers
1774 @itemx --with-headers=@var{dir}
1775 Deprecated in favor of @option{--with-sysroot}.
1776 Specifies that target headers are available when building a cross compiler.
1777 The @var{dir} argument specifies a directory which has the target include
1778 files. These include files will be copied into the @file{gcc} install
1779 directory. @emph{This option with the @var{dir} argument is required} when
1780 building a cross compiler, if @file{@var{prefix}/@var{target}/sys-include}
1781 doesn't pre-exist. If @file{@var{prefix}/@var{target}/sys-include} does
1782 pre-exist, the @var{dir} argument may be omitted. @command{fixincludes}
1783 will be run on these files to make them compatible with GCC@.
1785 @item --without-headers
1786 Tells GCC not use any target headers from a libc when building a cross
1787 compiler. When crossing to GNU/Linux, you need the headers so GCC
1788 can build the exception handling for libgcc.
1791 @itemx --with-libs="@var{dir1} @var{dir2} @dots{} @var{dirN}"
1792 Deprecated in favor of @option{--with-sysroot}.
1793 Specifies a list of directories which contain the target runtime
1794 libraries. These libraries will be copied into the @file{gcc} install
1795 directory. If the directory list is omitted, this option has no
1799 Specifies that @samp{newlib} is
1800 being used as the target C library. This causes @code{__eprintf} to be
1801 omitted from @file{libgcc.a} on the assumption that it will be provided by
1804 @item --with-build-time-tools=@var{dir}
1805 Specifies where to find the set of target tools (assembler, linker, etc.)
1806 that will be used while building GCC itself. This option can be useful
1807 if the directory layouts are different between the system you are building
1808 GCC on, and the system where you will deploy it.
1810 For example, on an @samp{ia64-hp-hpux} system, you may have the GNU
1811 assembler and linker in @file{/usr/bin}, and the native tools in a
1812 different path, and build a toolchain that expects to find the
1813 native tools in @file{/usr/bin}.
1815 When you use this option, you should ensure that @var{dir} includes
1816 @command{ar}, @command{as}, @command{ld}, @command{nm},
1817 @command{ranlib} and @command{strip} if necessary, and possibly
1818 @command{objdump}. Otherwise, GCC may use an inconsistent set of
1822 @subheading Java-Specific Options
1824 The following option applies to the build of the Java front end.
1827 @item --disable-libgcj
1828 Specify that the run-time libraries
1829 used by GCJ should not be built. This is useful in case you intend
1830 to use GCJ with some other run-time, or you're going to install it
1831 separately, or it just happens not to build on your particular
1832 machine. In general, if the Java front end is enabled, the GCJ
1833 libraries will be enabled too, unless they're known to not work on
1834 the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
1835 may need to port it; in this case, before modifying the top-level
1836 @file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
1837 you may use @option{--enable-libgcj} to override the default.
1841 The following options apply to building @samp{libgcj}.
1843 @subsubheading General Options
1846 @item --enable-java-maintainer-mode
1847 By default the @samp{libjava} build will not attempt to compile the
1848 @file{.java} source files to @file{.class}. Instead, it will use the
1849 @file{.class} files from the source tree. If you use this option you
1850 must have executables named @command{ecj1} and @command{gjavah} in your path
1851 for use by the build. You must use this option if you intend to
1852 modify any @file{.java} files in @file{libjava}.
1854 @item --with-java-home=@var{dirname}
1855 This @samp{libjava} option overrides the default value of the
1856 @samp{java.home} system property. It is also used to set
1857 @samp{sun.boot.class.path} to @file{@var{dirname}/lib/rt.jar}. By
1858 default @samp{java.home} is set to @file{@var{prefix}} and
1859 @samp{sun.boot.class.path} to
1860 @file{@var{datadir}/java/libgcj-@var{version}.jar}.
1862 @item --with-ecj-jar=@var{filename}
1863 This option can be used to specify the location of an external jar
1864 file containing the Eclipse Java compiler. A specially modified
1865 version of this compiler is used by @command{gcj} to parse
1866 @file{.java} source files. If this option is given, the
1867 @samp{libjava} build will create and install an @file{ecj1} executable
1868 which uses this jar file at runtime.
1870 If this option is not given, but an @file{ecj.jar} file is found in
1871 the topmost source tree at configure time, then the @samp{libgcj}
1872 build will create and install @file{ecj1}, and will also install the
1873 discovered @file{ecj.jar} into a suitable place in the install tree.
1875 If @file{ecj1} is not installed, then the user will have to supply one
1876 on his path in order for @command{gcj} to properly parse @file{.java}
1877 source files. A suitable jar is available from
1878 @uref{ftp://sourceware.org/pub/java/}.
1880 @item --disable-getenv-properties
1881 Don't set system properties from @env{GCJ_PROPERTIES}.
1883 @item --enable-hash-synchronization
1884 Use a global hash table for monitor locks. Ordinarily,
1885 @samp{libgcj}'s @samp{configure} script automatically makes
1886 the correct choice for this option for your platform. Only use
1887 this if you know you need the library to be configured differently.
1889 @item --enable-interpreter
1890 Enable the Java interpreter. The interpreter is automatically
1891 enabled by default on all platforms that support it. This option
1892 is really only useful if you want to disable the interpreter
1893 (using @option{--disable-interpreter}).
1895 @item --disable-java-net
1896 Disable java.net. This disables the native part of java.net only,
1897 using non-functional stubs for native method implementations.
1899 @item --disable-jvmpi
1900 Disable JVMPI support.
1902 @item --disable-libgcj-bc
1903 Disable BC ABI compilation of certain parts of libgcj. By default,
1904 some portions of libgcj are compiled with @option{-findirect-dispatch}
1905 and @option{-fno-indirect-classes}, allowing them to be overridden at
1908 If @option{--disable-libgcj-bc} is specified, libgcj is built without
1909 these options. This allows the compile-time linker to resolve
1910 dependencies when statically linking to libgcj. However it makes it
1911 impossible to override the affected portions of libgcj at run-time.
1913 @item --enable-reduced-reflection
1914 Build most of libgcj with @option{-freduced-reflection}. This reduces
1915 the size of libgcj at the expense of not being able to do accurate
1916 reflection on the classes it contains. This option is safe if you
1917 know that code using libgcj will never use reflection on the standard
1918 runtime classes in libgcj (including using serialization, RMI or CORBA).
1921 Enable runtime eCos target support.
1923 @item --without-libffi
1924 Don't use @samp{libffi}. This will disable the interpreter and JNI
1925 support as well, as these require @samp{libffi} to work.
1927 @item --enable-libgcj-debug
1928 Enable runtime debugging code.
1930 @item --enable-libgcj-multifile
1931 If specified, causes all @file{.java} source files to be
1932 compiled into @file{.class} files in one invocation of
1933 @samp{gcj}. This can speed up build time, but is more
1934 resource-intensive. If this option is unspecified or
1935 disabled, @samp{gcj} is invoked once for each @file{.java}
1936 file to compile into a @file{.class} file.
1938 @item --with-libiconv-prefix=DIR
1939 Search for libiconv in @file{DIR/include} and @file{DIR/lib}.
1941 @item --enable-sjlj-exceptions
1942 Force use of the @code{setjmp}/@code{longjmp}-based scheme for exceptions.
1943 @samp{configure} ordinarily picks the correct value based on the platform.
1944 Only use this option if you are sure you need a different setting.
1946 @item --with-system-zlib
1947 Use installed @samp{zlib} rather than that included with GCC@.
1949 @item --with-win32-nlsapi=ansi, unicows or unicode
1950 Indicates how MinGW @samp{libgcj} translates between UNICODE
1951 characters and the Win32 API@.
1953 @item --enable-java-home
1954 If enabled, this creates a JPackage compatible SDK environment during install.
1955 Note that if --enable-java-home is used, --with-arch-directory=ARCH must also
1958 @item --with-arch-directory=ARCH
1959 Specifies the name to use for the @file{jre/lib/ARCH} directory in the SDK
1960 environment created when --enable-java-home is passed. Typical names for this
1961 directory include i386, amd64, ia64, etc.
1963 @item --with-os-directory=DIR
1964 Specifies the OS directory for the SDK include directory. This is set to auto
1965 detect, and is typically 'linux'.
1967 @item --with-origin-name=NAME
1968 Specifies the JPackage origin name. This defaults to the 'gcj' in
1971 @item --with-arch-suffix=SUFFIX
1972 Specifies the suffix for the sdk directory. Defaults to the empty string.
1973 Examples include '.x86_64' in 'java-1.5.0-gcj-1.5.0.0.x86_64'.
1975 @item --with-jvm-root-dir=DIR
1976 Specifies where to install the SDK. Default is $(prefix)/lib/jvm.
1978 @item --with-jvm-jar-dir=DIR
1979 Specifies where to install jars. Default is $(prefix)/lib/jvm-exports.
1981 @item --with-python-dir=DIR
1982 Specifies where to install the Python modules used for aot-compile. DIR should
1983 not include the prefix used in installation. For example, if the Python modules
1984 are to be installed in /usr/lib/python2.5/site-packages, then
1985 --with-python-dir=/lib/python2.5/site-packages should be passed. If this is
1986 not specified, then the Python modules are installed in $(prefix)/share/python.
1988 @item --enable-aot-compile-rpm
1989 Adds aot-compile-rpm to the list of installed scripts.
1991 @item --enable-browser-plugin
1992 Build the gcjwebplugin web browser plugin.
1994 @item --enable-static-libjava
1995 Build static libraries in libjava. The default is to only build shared
2000 Use the single-byte @code{char} and the Win32 A functions natively,
2001 translating to and from UNICODE when using these functions. If
2002 unspecified, this is the default.
2005 Use the @code{WCHAR} and Win32 W functions natively. Adds
2006 @code{-lunicows} to @file{libgcj.spec} to link with @samp{libunicows}.
2007 @file{unicows.dll} needs to be deployed on Microsoft Windows 9X machines
2008 running built executables. @file{libunicows.a}, an open-source
2009 import library around Microsoft's @code{unicows.dll}, is obtained from
2010 @uref{http://libunicows.sourceforge.net/}, which also gives details
2011 on getting @file{unicows.dll} from Microsoft.
2014 Use the @code{WCHAR} and Win32 W functions natively. Does @emph{not}
2015 add @code{-lunicows} to @file{libgcj.spec}. The built executables will
2016 only run on Microsoft Windows NT and above.
2020 @subsubheading AWT-Specific Options
2024 Use the X Window System.
2026 @item --enable-java-awt=PEER(S)
2027 Specifies the AWT peer library or libraries to build alongside
2028 @samp{libgcj}. If this option is unspecified or disabled, AWT
2029 will be non-functional. Current valid values are @option{gtk} and
2030 @option{xlib}. Multiple libraries should be separated by a
2031 comma (i.e.@: @option{--enable-java-awt=gtk,xlib}).
2033 @item --enable-gtk-cairo
2034 Build the cairo Graphics2D implementation on GTK@.
2036 @item --enable-java-gc=TYPE
2037 Choose garbage collector. Defaults to @option{boehm} if unspecified.
2039 @item --disable-gtktest
2040 Do not try to compile and run a test GTK+ program.
2042 @item --disable-glibtest
2043 Do not try to compile and run a test GLIB program.
2045 @item --with-libart-prefix=PFX
2046 Prefix where libart is installed (optional).
2048 @item --with-libart-exec-prefix=PFX
2049 Exec prefix where libart is installed (optional).
2051 @item --disable-libarttest
2052 Do not try to compile and run a test libart program.
2056 @subsubheading Overriding @command{configure} test results
2058 Sometimes, it might be necessary to override the result of some
2059 @command{configure} test, for example in order to ease porting to a new
2060 system or work around a bug in a test. The toplevel @command{configure}
2061 script provides three variables for this:
2065 @item build_configargs
2066 @cindex @code{build_configargs}
2067 The contents of this variable is passed to all build @command{configure}
2070 @item host_configargs
2071 @cindex @code{host_configargs}
2072 The contents of this variable is passed to all host @command{configure}
2075 @item target_configargs
2076 @cindex @code{target_configargs}
2077 The contents of this variable is passed to all target @command{configure}
2082 In order to avoid shell and @command{make} quoting issues for complex
2083 overrides, you can pass a setting for @env{CONFIG_SITE} and set
2084 variables in the site file.
2091 @uref{./index.html,,Return to the GCC Installation page}
2095 @c ***Building****************************************************************
2097 @comment node-name, next, previous, up
2098 @node Building, Testing, Configuration, Installing GCC
2104 @cindex Installing GCC: Building
2106 Now that GCC is configured, you are ready to build the compiler and
2109 Some commands executed when making the compiler may fail (return a
2110 nonzero status) and be ignored by @command{make}. These failures, which
2111 are often due to files that were not found, are expected, and can safely
2114 It is normal to have compiler warnings when compiling certain files.
2115 Unless you are a GCC developer, you can generally ignore these warnings
2116 unless they cause compilation to fail. Developers should attempt to fix
2117 any warnings encountered, however they can temporarily continue past
2118 warnings-as-errors by specifying the configure flag
2119 @option{--disable-werror}.
2121 On certain old systems, defining certain environment variables such as
2122 @env{CC} can interfere with the functioning of @command{make}.
2124 If you encounter seemingly strange errors when trying to build the
2125 compiler in a directory other than the source directory, it could be
2126 because you have previously configured the compiler in the source
2127 directory. Make sure you have done all the necessary preparations.
2129 If you build GCC on a BSD system using a directory stored in an old System
2130 V file system, problems may occur in running @command{fixincludes} if the
2131 System V file system doesn't support symbolic links. These problems
2132 result in a failure to fix the declaration of @code{size_t} in
2133 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
2134 that type mismatches occur, this could be the cause.
2136 The solution is not to use such a directory for building GCC@.
2138 Similarly, when building from SVN or snapshots, or if you modify
2139 @file{*.l} files, you need the Flex lexical analyzer generator
2140 installed. If you do not modify @file{*.l} files, releases contain
2141 the Flex-generated files and you do not need Flex installed to build
2142 them. There is still one Flex-based lexical analyzer (part of the
2143 build machinery, not of GCC itself) that is used even if you only
2144 build the C front end.
2146 When building from SVN or snapshots, or if you modify Texinfo
2147 documentation, you need version 4.7 or later of Texinfo installed if you
2148 want Info documentation to be regenerated. Releases contain Info
2149 documentation pre-built for the unmodified documentation in the release.
2151 @section Building a native compiler
2153 For a native build, the default configuration is to perform
2154 a 3-stage bootstrap of the compiler when @samp{make} is invoked.
2155 This will build the entire GCC system and ensure that it compiles
2156 itself correctly. It can be disabled with the @option{--disable-bootstrap}
2157 parameter to @samp{configure}, but bootstrapping is suggested because
2158 the compiler will be tested more completely and could also have
2161 The bootstrapping process will complete the following steps:
2165 Build tools necessary to build the compiler.
2168 Perform a 3-stage bootstrap of the compiler. This includes building
2169 three times the target tools for use by the compiler such as binutils
2170 (bfd, binutils, gas, gprof, ld, and opcodes) if they have been
2171 individually linked or moved into the top level GCC source tree before
2175 Perform a comparison test of the stage2 and stage3 compilers.
2178 Build runtime libraries using the stage3 compiler from the previous step.
2182 If you are short on disk space you might consider @samp{make
2183 bootstrap-lean} instead. The sequence of compilation is the
2184 same described above, but object files from the stage1 and
2185 stage2 of the 3-stage bootstrap of the compiler are deleted as
2186 soon as they are no longer needed.
2188 If you wish to use non-default GCC flags when compiling the stage2
2189 and stage3 compilers, set @code{BOOT_CFLAGS} on the command line when
2190 doing @samp{make}. For example, if you want to save additional space
2191 during the bootstrap and in the final installation as well, you can
2192 build the compiler binaries without debugging information as in the
2193 following example. This will save roughly 40% of disk space both for
2194 the bootstrap and the final installation. (Libraries will still contain
2195 debugging information.)
2198 make BOOT_CFLAGS='-O' bootstrap
2201 You can place non-default optimization flags into @code{BOOT_CFLAGS}; they
2202 are less well tested here than the default of @samp{-g -O2}, but should
2203 still work. In a few cases, you may find that you need to specify special
2204 flags such as @option{-msoft-float} here to complete the bootstrap; or,
2205 if the native compiler miscompiles the stage1 compiler, you may need
2206 to work around this, by choosing @code{BOOT_CFLAGS} to avoid the parts
2207 of the stage1 compiler that were miscompiled, or by using @samp{make
2208 bootstrap4} to increase the number of stages of bootstrap.
2210 @code{BOOT_CFLAGS} does not apply to bootstrapped target libraries.
2211 Since these are always compiled with the compiler currently being
2212 bootstrapped, you can use @code{CFLAGS_FOR_TARGET} to modify their
2213 compilation flags, as for non-bootstrapped target libraries.
2214 Again, if the native compiler miscompiles the stage1 compiler, you may
2215 need to work around this by avoiding non-working parts of the stage1
2216 compiler. Use @code{STAGE1_TFLAGS} to this end.
2218 If you used the flag @option{--enable-languages=@dots{}} to restrict
2219 the compilers to be built, only those you've actually enabled will be
2220 built. This will of course only build those runtime libraries, for
2221 which the particular compiler has been built. Please note,
2222 that re-defining @env{LANGUAGES} when calling @samp{make}
2223 @strong{does not} work anymore!
2225 If the comparison of stage2 and stage3 fails, this normally indicates
2226 that the stage2 compiler has compiled GCC incorrectly, and is therefore
2227 a potentially serious bug which you should investigate and report. (On
2228 a few systems, meaningful comparison of object files is impossible; they
2229 always appear ``different''. If you encounter this problem, you will
2230 need to disable comparison in the @file{Makefile}.)
2232 If you do not want to bootstrap your compiler, you can configure with
2233 @option{--disable-bootstrap}. In particular cases, you may want to
2234 bootstrap your compiler even if the target system is not the same as
2235 the one you are building on: for example, you could build a
2236 @code{powerpc-unknown-linux-gnu} toolchain on a
2237 @code{powerpc64-unknown-linux-gnu} host. In this case, pass
2238 @option{--enable-bootstrap} to the configure script.
2240 @code{BUILD_CONFIG} can be used to bring in additional customization
2241 to the build. It can be set to a whitespace-separated list of names.
2242 For each such @code{NAME}, top-level @file{config/@code{NAME}.mk} will
2243 be included by the top-level @file{Makefile}, bringing in any settings
2244 it contains. The default @code{BUILD_CONFIG} can be set using the
2245 configure option @option{--with-build-config=@code{NAME}...}. Some
2246 examples of supported build configurations are:
2249 @item @samp{bootstrap-O1}
2250 Removes any @option{-O}-started option from @code{BOOT_CFLAGS}, and adds
2251 @option{-O1} to it. @samp{BUILD_CONFIG=bootstrap-O1} is equivalent to
2252 @samp{BOOT_CFLAGS='-g -O1'}.
2254 @item @samp{bootstrap-O3}
2255 Analogous to @code{bootstrap-O1}.
2257 @item @samp{bootstrap-lto}
2258 Enables Link-Time Optimization for host tools during bootstrapping.
2259 @samp{BUILD_CONFIG=bootstrap-lto} is equivalent to adding
2260 @option{-flto} to @samp{BOOT_CFLAGS}.
2262 @item @samp{bootstrap-debug}
2263 Verifies that the compiler generates the same executable code, whether
2264 or not it is asked to emit debug information. To this end, this
2265 option builds stage2 host programs without debug information, and uses
2266 @file{contrib/compare-debug} to compare them with the stripped stage3
2267 object files. If @code{BOOT_CFLAGS} is overridden so as to not enable
2268 debug information, stage2 will have it, and stage3 won't. This option
2269 is enabled by default when GCC bootstrapping is enabled, if
2270 @code{strip} can turn object files compiled with and without debug
2271 info into identical object files. In addition to better test
2272 coverage, this option makes default bootstraps faster and leaner.
2274 @item @samp{bootstrap-debug-big}
2275 Rather than comparing stripped object files, as in
2276 @code{bootstrap-debug}, this option saves internal compiler dumps
2277 during stage2 and stage3 and compares them as well, which helps catch
2278 additional potential problems, but at a great cost in terms of disk
2279 space. It can be specified in addition to @samp{bootstrap-debug}.
2281 @item @samp{bootstrap-debug-lean}
2282 This option saves disk space compared with @code{bootstrap-debug-big},
2283 but at the expense of some recompilation. Instead of saving the dumps
2284 of stage2 and stage3 until the final compare, it uses
2285 @option{-fcompare-debug} to generate, compare and remove the dumps
2286 during stage3, repeating the compilation that already took place in
2287 stage2, whose dumps were not saved.
2289 @item @samp{bootstrap-debug-lib}
2290 This option tests executable code invariance over debug information
2291 generation on target libraries, just like @code{bootstrap-debug-lean}
2292 tests it on host programs. It builds stage3 libraries with
2293 @option{-fcompare-debug}, and it can be used along with any of the
2294 @code{bootstrap-debug} options above.
2296 There aren't @code{-lean} or @code{-big} counterparts to this option
2297 because most libraries are only build in stage3, so bootstrap compares
2298 would not get significant coverage. Moreover, the few libraries built
2299 in stage2 are used in stage3 host programs, so we wouldn't want to
2300 compile stage2 libraries with different options for comparison purposes.
2302 @item @samp{bootstrap-debug-ckovw}
2303 Arranges for error messages to be issued if the compiler built on any
2304 stage is run without the option @option{-fcompare-debug}. This is
2305 useful to verify the full @option{-fcompare-debug} testing coverage. It
2306 must be used along with @code{bootstrap-debug-lean} and
2307 @code{bootstrap-debug-lib}.
2309 @item @samp{bootstrap-time}
2310 Arranges for the run time of each program started by the GCC driver,
2311 built in any stage, to be logged to @file{time.log}, in the top level of
2316 @section Building a cross compiler
2318 When building a cross compiler, it is not generally possible to do a
2319 3-stage bootstrap of the compiler. This makes for an interesting problem
2320 as parts of GCC can only be built with GCC@.
2322 To build a cross compiler, we recommend first building and installing a
2323 native compiler. You can then use the native GCC compiler to build the
2324 cross compiler. The installed native compiler needs to be GCC version
2327 If the cross compiler is to be built with support for the Java
2328 programming language and the ability to compile .java source files is
2329 desired, the installed native compiler used to build the cross
2330 compiler needs to be the same GCC version as the cross compiler. In
2331 addition the cross compiler needs to be configured with
2332 @option{--with-ecj-jar=@dots{}}.
2334 Assuming you have already installed a native copy of GCC and configured
2335 your cross compiler, issue the command @command{make}, which performs the
2340 Build host tools necessary to build the compiler.
2343 Build target tools for use by the compiler such as binutils (bfd,
2344 binutils, gas, gprof, ld, and opcodes)
2345 if they have been individually linked or moved into the top level GCC source
2346 tree before configuring.
2349 Build the compiler (single stage only).
2352 Build runtime libraries using the compiler from the previous step.
2355 Note that if an error occurs in any step the make process will exit.
2357 If you are not building GNU binutils in the same source tree as GCC,
2358 you will need a cross-assembler and cross-linker installed before
2359 configuring GCC@. Put them in the directory
2360 @file{@var{prefix}/@var{target}/bin}. Here is a table of the tools
2361 you should put in this directory:
2365 This should be the cross-assembler.
2368 This should be the cross-linker.
2371 This should be the cross-archiver: a program which can manipulate
2372 archive files (linker libraries) in the target machine's format.
2375 This should be a program to construct a symbol table in an archive file.
2378 The installation of GCC will find these programs in that directory,
2379 and copy or link them to the proper place to for the cross-compiler to
2380 find them when run later.
2382 The easiest way to provide these files is to build the Binutils package.
2383 Configure it with the same @option{--host} and @option{--target}
2384 options that you use for configuring GCC, then build and install
2385 them. They install their executables automatically into the proper
2386 directory. Alas, they do not support all the targets that GCC
2389 If you are not building a C library in the same source tree as GCC,
2390 you should also provide the target libraries and headers before
2391 configuring GCC, specifying the directories with
2392 @option{--with-sysroot} or @option{--with-headers} and
2393 @option{--with-libs}. Many targets also require ``start files'' such
2394 as @file{crt0.o} and
2395 @file{crtn.o} which are linked into each executable. There may be several
2396 alternatives for @file{crt0.o}, for use with profiling or other
2397 compilation options. Check your target's definition of
2398 @code{STARTFILE_SPEC} to find out what start files it uses.
2400 @section Building in parallel
2402 GNU Make 3.80 and above, which is necessary to build GCC, support
2403 building in parallel. To activate this, you can use @samp{make -j 2}
2404 instead of @samp{make}. You can also specify a bigger number, and
2405 in most cases using a value greater than the number of processors in
2406 your machine will result in fewer and shorter I/O latency hits, thus
2407 improving overall throughput; this is especially true for slow drives
2408 and network filesystems.
2410 @section Building the Ada compiler
2412 In order to build GNAT, the Ada compiler, you need a working GNAT
2413 compiler (GCC version 4.0 or later).
2414 This includes GNAT tools such as @command{gnatmake} and
2415 @command{gnatlink}, since the Ada front end is written in Ada and
2416 uses some GNAT-specific extensions.
2418 In order to build a cross compiler, it is suggested to install
2419 the new compiler as native first, and then use it to build the cross
2422 @command{configure} does not test whether the GNAT installation works
2423 and has a sufficiently recent version; if too old a GNAT version is
2424 installed, the build will fail unless @option{--enable-languages} is
2425 used to disable building the Ada front end.
2427 @env{ADA_INCLUDE_PATH} and @env{ADA_OBJECT_PATH} environment variables
2428 must not be set when building the Ada compiler, the Ada tools, or the
2429 Ada runtime libraries. You can check that your build environment is clean
2430 by verifying that @samp{gnatls -v} lists only one explicit path in each
2433 @section Building with profile feedback
2435 It is possible to use profile feedback to optimize the compiler itself. This
2436 should result in a faster compiler binary. Experiments done on x86 using gcc
2437 3.3 showed approximately 7 percent speedup on compiling C programs. To
2438 bootstrap the compiler with profile feedback, use @code{make profiledbootstrap}.
2440 When @samp{make profiledbootstrap} is run, it will first build a @code{stage1}
2441 compiler. This compiler is used to build a @code{stageprofile} compiler
2442 instrumented to collect execution counts of instruction and branch
2443 probabilities. Then runtime libraries are compiled with profile collected.
2444 Finally a @code{stagefeedback} compiler is built using the information collected.
2446 Unlike standard bootstrap, several additional restrictions apply. The
2447 compiler used to build @code{stage1} needs to support a 64-bit integral type.
2448 It is recommended to only use GCC for this. Also parallel make is currently
2449 not supported since collisions in profile collecting may occur.
2456 @uref{./index.html,,Return to the GCC Installation page}
2460 @c ***Testing*****************************************************************
2462 @comment node-name, next, previous, up
2463 @node Testing, Final install, Building, Installing GCC
2467 @chapter Installing GCC: Testing
2470 @cindex Installing GCC: Testing
2473 Before you install GCC, we encourage you to run the testsuites and to
2474 compare your results with results from a similar configuration that have
2475 been submitted to the
2476 @uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
2477 Some of these archived results are linked from the build status lists
2478 at @uref{http://gcc.gnu.org/buildstat.html}, although not everyone who
2479 reports a successful build runs the testsuites and submits the results.
2480 This step is optional and may require you to download additional software,
2481 but it can give you confidence in your new GCC installation or point out
2482 problems before you install and start using your new GCC@.
2484 First, you must have @uref{download.html,,downloaded the testsuites}.
2485 These are part of the full distribution, but if you downloaded the
2486 ``core'' compiler plus any front ends, you must download the testsuites
2489 Second, you must have the testing tools installed. This includes
2490 @uref{http://www.gnu.org/software/dejagnu/,,DejaGnu}, Tcl, and Expect;
2491 the DejaGnu site has links to these.
2493 If the directories where @command{runtest} and @command{expect} were
2494 installed are not in the @env{PATH}, you may need to set the following
2495 environment variables appropriately, as in the following example (which
2496 assumes that DejaGnu has been installed under @file{/usr/local}):
2499 TCL_LIBRARY = /usr/local/share/tcl8.0
2500 DEJAGNULIBS = /usr/local/share/dejagnu
2503 (On systems such as Cygwin, these paths are required to be actual
2504 paths, not mounts or links; presumably this is due to some lack of
2505 portability in the DejaGnu code.)
2508 Finally, you can run the testsuite (which may take a long time):
2510 cd @var{objdir}; make -k check
2513 This will test various components of GCC, such as compiler
2514 front ends and runtime libraries. While running the testsuite, DejaGnu
2515 might emit some harmless messages resembling
2516 @samp{WARNING: Couldn't find the global config file.} or
2517 @samp{WARNING: Couldn't find tool init file} that can be ignored.
2519 If you are testing a cross-compiler, you may want to run the testsuite
2520 on a simulator as described at @uref{http://gcc.gnu.org/simtest-howto.html}.
2522 @section How can you run the testsuite on selected tests?
2524 In order to run sets of tests selectively, there are targets
2525 @samp{make check-gcc} and @samp{make check-g++}
2526 in the @file{gcc} subdirectory of the object directory. You can also
2527 just run @samp{make check} in a subdirectory of the object directory.
2530 A more selective way to just run all @command{gcc} execute tests in the
2534 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
2537 Likewise, in order to run only the @command{g++} ``old-deja'' tests in
2538 the testsuite with filenames matching @samp{9805*}, you would use
2541 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
2544 The @file{*.exp} files are located in the testsuite directories of the GCC
2545 source, the most important ones being @file{compile.exp},
2546 @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
2547 To get a list of the possible @file{*.exp} files, pipe the
2548 output of @samp{make check} into a file and look at the
2549 @samp{Running @dots{} .exp} lines.
2551 @section Passing options and running multiple testsuites
2553 You can pass multiple options to the testsuite using the
2554 @samp{--target_board} option of DejaGNU, either passed as part of
2555 @samp{RUNTESTFLAGS}, or directly to @command{runtest} if you prefer to
2556 work outside the makefiles. For example,
2559 make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fmerge-constants"
2562 will run the standard @command{g++} testsuites (``unix'' is the target name
2563 for a standard native testsuite situation), passing
2564 @samp{-O3 -fmerge-constants} to the compiler on every test, i.e.,
2565 slashes separate options.
2567 You can run the testsuites multiple times using combinations of options
2568 with a syntax similar to the brace expansion of popular shells:
2571 @dots{}"--target_board=arm-sim\@{-mhard-float,-msoft-float\@}\@{-O1,-O2,-O3,\@}"
2574 (Note the empty option caused by the trailing comma in the final group.)
2575 The following will run each testsuite eight times using the @samp{arm-sim}
2576 target, as if you had specified all possible combinations yourself:
2579 --target_board=arm-sim/-mhard-float/-O1
2580 --target_board=arm-sim/-mhard-float/-O2
2581 --target_board=arm-sim/-mhard-float/-O3
2582 --target_board=arm-sim/-mhard-float
2583 --target_board=arm-sim/-msoft-float/-O1
2584 --target_board=arm-sim/-msoft-float/-O2
2585 --target_board=arm-sim/-msoft-float/-O3
2586 --target_board=arm-sim/-msoft-float
2589 They can be combined as many times as you wish, in arbitrary ways. This
2593 @dots{}"--target_board=unix/-Wextra\@{-O3,-fno-strength\@}\@{-fomit-frame,\@}"
2596 will generate four combinations, all involving @samp{-Wextra}.
2598 The disadvantage to this method is that the testsuites are run in serial,
2599 which is a waste on multiprocessor systems. For users with GNU Make and
2600 a shell which performs brace expansion, you can run the testsuites in
2601 parallel by having the shell perform the combinations and @command{make}
2602 do the parallel runs. Instead of using @samp{--target_board}, use a
2603 special makefile target:
2606 make -j@var{N} check-@var{testsuite}//@var{test-target}/@var{option1}/@var{option2}/@dots{}
2612 make -j3 check-gcc//sh-hms-sim/@{-m1,-m2,-m3,-m3e,-m4@}/@{,-nofpu@}
2615 will run three concurrent ``make-gcc'' testsuites, eventually testing all
2616 ten combinations as described above. Note that this is currently only
2617 supported in the @file{gcc} subdirectory. (To see how this works, try
2618 typing @command{echo} before the example given here.)
2621 @section Additional testing for Java Class Libraries
2623 The Java runtime tests can be executed via @samp{make check}
2624 in the @file{@var{target}/libjava/testsuite} directory in
2627 The @uref{http://sourceware.org/mauve/,,Mauve Project} provides
2628 a suite of tests for the Java Class Libraries. This suite can be run
2629 as part of libgcj testing by placing the Mauve tree within the libjava
2630 testsuite at @file{libjava/testsuite/libjava.mauve/mauve}, or by
2631 specifying the location of that tree when invoking @samp{make}, as in
2632 @samp{make MAUVEDIR=~/mauve check}.
2634 @section How to interpret test results
2636 The result of running the testsuite are various @file{*.sum} and @file{*.log}
2637 files in the testsuite subdirectories. The @file{*.log} files contain a
2638 detailed log of the compiler invocations and the corresponding
2639 results, the @file{*.sum} files summarize the results. These summaries
2640 contain status codes for all tests:
2644 PASS: the test passed as expected
2646 XPASS: the test unexpectedly passed
2648 FAIL: the test unexpectedly failed
2650 XFAIL: the test failed as expected
2652 UNSUPPORTED: the test is not supported on this platform
2654 ERROR: the testsuite detected an error
2656 WARNING: the testsuite detected a possible problem
2659 It is normal for some tests to report unexpected failures. At the
2660 current time the testing harness does not allow fine grained control
2661 over whether or not a test is expected to fail. This problem should
2662 be fixed in future releases.
2665 @section Submitting test results
2667 If you want to report the results to the GCC project, use the
2668 @file{contrib/test_summary} shell script. Start it in the @var{objdir} with
2671 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
2672 -m gcc-testresults@@gcc.gnu.org |sh
2675 This script uses the @command{Mail} program to send the results, so
2676 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
2677 prepended to the testsuite summary and should contain any special
2678 remarks you have on your results or your build environment. Please
2679 do not edit the testsuite result block or the subject line, as these
2680 messages may be automatically processed.
2687 @uref{./index.html,,Return to the GCC Installation page}
2691 @c ***Final install***********************************************************
2693 @comment node-name, next, previous, up
2694 @node Final install, , Testing, Installing GCC
2696 @ifset finalinstallhtml
2698 @chapter Installing GCC: Final installation
2701 Now that GCC has been built (and optionally tested), you can install it with
2703 cd @var{objdir} && make install
2706 We strongly recommend to install into a target directory where there is
2707 no previous version of GCC present. Also, the GNAT runtime should not
2708 be stripped, as this would break certain features of the debugger that
2709 depend on this debugging information (catching Ada exceptions for
2712 That step completes the installation of GCC; user level binaries can
2713 be found in @file{@var{prefix}/bin} where @var{prefix} is the value
2714 you specified with the @option{--prefix} to configure (or
2715 @file{/usr/local} by default). (If you specified @option{--bindir},
2716 that directory will be used instead; otherwise, if you specified
2717 @option{--exec-prefix}, @file{@var{exec-prefix}/bin} will be used.)
2718 Headers for the C++ and Java libraries are installed in
2719 @file{@var{prefix}/include}; libraries in @file{@var{libdir}}
2720 (normally @file{@var{prefix}/lib}); internal parts of the compiler in
2721 @file{@var{libdir}/gcc} and @file{@var{libexecdir}/gcc}; documentation
2722 in info format in @file{@var{infodir}} (normally
2723 @file{@var{prefix}/info}).
2725 When installing cross-compilers, GCC's executables
2726 are not only installed into @file{@var{bindir}}, that
2727 is, @file{@var{exec-prefix}/bin}, but additionally into
2728 @file{@var{exec-prefix}/@var{target-alias}/bin}, if that directory
2729 exists. Typically, such @dfn{tooldirs} hold target-specific
2730 binutils, including assembler and linker.
2732 Installation into a temporary staging area or into a @command{chroot}
2733 jail can be achieved with the command
2736 make DESTDIR=@var{path-to-rootdir} install
2740 where @var{path-to-rootdir} is the absolute path of
2741 a directory relative to which all installation paths will be
2742 interpreted. Note that the directory specified by @code{DESTDIR}
2743 need not exist yet; it will be created if necessary.
2745 There is a subtle point with tooldirs and @code{DESTDIR}:
2746 If you relocate a cross-compiler installation with
2747 e.g.@: @samp{DESTDIR=@var{rootdir}}, then the directory
2748 @file{@var{rootdir}/@var{exec-prefix}/@var{target-alias}/bin} will
2749 be filled with duplicated GCC executables only if it already exists,
2750 it will not be created otherwise. This is regarded as a feature,
2751 not as a bug, because it gives slightly more control to the packagers
2752 using the @code{DESTDIR} feature.
2754 You can install stripped programs and libraries with
2760 If you are bootstrapping a released version of GCC then please
2761 quickly review the build status page for your release, available from
2762 @uref{http://gcc.gnu.org/buildstat.html}.
2763 If your system is not listed for the version of GCC that you built,
2765 @email{gcc@@gcc.gnu.org} indicating
2766 that you successfully built and installed GCC@.
2767 Include the following information:
2771 Output from running @file{@var{srcdir}/config.guess}. Do not send
2772 that file itself, just the one-line output from running it.
2775 The output of @samp{gcc -v} for your newly installed @command{gcc}.
2776 This tells us which version of GCC you built and the options you passed to
2780 Whether you enabled all languages or a subset of them. If you used a
2781 full distribution then this information is part of the configure
2782 options in the output of @samp{gcc -v}, but if you downloaded the
2783 ``core'' compiler plus additional front ends then it isn't apparent
2784 which ones you built unless you tell us about it.
2787 If the build was for GNU/Linux, also include:
2790 The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
2791 this information should be available from @file{/etc/issue}.
2794 The version of the Linux kernel, available from @samp{uname --version}
2798 The version of glibc you used; for RPM-based systems like Red Hat,
2799 Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
2800 and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
2802 For other systems, you can include similar information if you think it is
2806 Any other information that you think would be useful to people building
2807 GCC on the same configuration. The new entry in the build status list
2808 will include a link to the archived copy of your message.
2811 We'd also like to know if the
2813 @ref{Specific, host/target specific installation notes}
2816 @uref{specific.html,,host/target specific installation notes}
2818 didn't include your host/target information or if that information is
2819 incomplete or out of date. Send a note to
2820 @email{gcc@@gcc.gnu.org} detailing how the information should be changed.
2822 If you find a bug, please report it following the
2823 @uref{../bugs/,,bug reporting guidelines}.
2825 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
2826 dvi}. You will need to have @command{texi2dvi} (version at least 4.7)
2827 and @TeX{} installed. This creates a number of @file{.dvi} files in
2828 subdirectories of @file{@var{objdir}}; these may be converted for
2829 printing with programs such as @command{dvips}. Alternately, by using
2830 @samp{make pdf} in place of @samp{make dvi}, you can create documentation
2831 in the form of @file{.pdf} files; this requires @command{texi2pdf}, which
2832 is included with Texinfo version 4.8 and later. You can also
2833 @uref{http://shop.fsf.org/,,buy printed manuals from the
2834 Free Software Foundation}, though such manuals may not be for the most
2835 recent version of GCC@.
2837 If you would like to generate online HTML documentation, do @samp{cd
2838 @var{objdir}; make html} and HTML will be generated for the gcc manuals in
2839 @file{@var{objdir}/gcc/HTML}.
2846 @uref{./index.html,,Return to the GCC Installation page}
2850 @c ***Binaries****************************************************************
2852 @comment node-name, next, previous, up
2853 @node Binaries, Specific, Installing GCC, Top
2857 @chapter Installing GCC: Binaries
2860 @cindex Installing GCC: Binaries
2862 We are often asked about pre-compiled versions of GCC@. While we cannot
2863 provide these for all platforms, below you'll find links to binaries for
2864 various platforms where creating them by yourself is not easy due to various
2867 Please note that we did not create these binaries, nor do we
2868 support them. If you have any problems installing them, please
2869 contact their makers.
2876 @uref{http://www.bullfreeware.com,,Bull's Freeware and Shareware Archive for AIX};
2879 @uref{http://pware.hvcc.edu,,Hudson Valley Community College Open Source Software for IBM System p};
2882 @uref{http://www.perzl.org/aix/,,AIX 5L and 6 Open Source Packages}.
2886 DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}.
2889 Renesas H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
2890 Development Tools for the Renesas H8/300[HS] Series}.
2896 @uref{http://hpux.connect.org.uk/,,HP-UX Porting Center};
2899 @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}.
2903 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
2904 OpenServer/Unixware}.
2907 Solaris 2 (SPARC, Intel):
2910 @uref{http://www.sunfreeware.com/,,Sunfreeware}
2913 @uref{http://www.blastwave.org/,,Blastwave}
2916 @uref{http://www.opencsw.org/,,OpenCSW}
2919 @uref{http://jupiterrise.com/tgcware/,,TGCware}
2926 @uref{http://nekochan.net/,,Nekoware}
2929 @uref{http://jupiterrise.com/tgcware/,,TGCware}
2936 The @uref{http://sourceware.org/cygwin/,,Cygwin} project;
2938 The @uref{http://www.mingw.org/,,MinGW} project.
2942 @uref{ftp://ftp.thewrittenword.com/packages/by-name/,,The
2943 Written Word} offers binaries for
2944 AIX 4.3.3, 5.1 and 5.2,
2946 Tru64 UNIX 4.0D and 5.1,
2948 HP-UX 10.20, 11.00, and 11.11, and
2949 Solaris/SPARC 2.5.1, 2.6, 7, 8, 9 and 10.
2952 @uref{http://www.openpkg.org/,,OpenPKG} offers binaries for quite a
2953 number of platforms.
2956 The @uref{http://gcc.gnu.org/wiki/GFortranBinaries,,GFortran Wiki} has
2957 links to GNU Fortran binaries for several platforms.
2965 @uref{./index.html,,Return to the GCC Installation page}
2969 @c ***Specific****************************************************************
2971 @comment node-name, next, previous, up
2972 @node Specific, Old, Binaries, Top
2976 @chapter Host/target specific installation notes for GCC
2979 @cindex Specific installation notes
2980 @cindex Target specific installation
2981 @cindex Host specific installation
2982 @cindex Target specific installation notes
2984 Please read this document carefully @emph{before} installing the
2985 GNU Compiler Collection on your machine.
2987 Note that this list of install notes is @emph{not} a list of supported
2988 hosts or targets. Not all supported hosts and targets are listed
2989 here, only the ones that require host-specific or target-specific
2995 @uref{#alpha-x-x,,alpha*-*-*}
2997 @uref{#alpha-dec-osf51,,alpha*-dec-osf5.1}
2999 @uref{#amd64-x-solaris210,,amd64-*-solaris2.10}
3001 @uref{#arm-x-elf,,arm-*-elf}
3005 @uref{#bfin,,Blackfin}
3009 @uref{#x-x-freebsd,,*-*-freebsd*}
3011 @uref{#h8300-hms,,h8300-hms}
3013 @uref{#hppa-hp-hpux,,hppa*-hp-hpux*}
3015 @uref{#hppa-hp-hpux10,,hppa*-hp-hpux10}
3017 @uref{#hppa-hp-hpux11,,hppa*-hp-hpux11}
3019 @uref{#x-x-linux-gnu,,*-*-linux-gnu}
3021 @uref{#ix86-x-linux,,i?86-*-linux*}
3023 @uref{#ix86-x-solaris289,,i?86-*-solaris2.[89]}
3025 @uref{#ix86-x-solaris210,,i?86-*-solaris2.10}
3027 @uref{#ia64-x-linux,,ia64-*-linux}
3029 @uref{#ia64-x-hpux,,ia64-*-hpux*}
3031 @uref{#x-ibm-aix,,*-ibm-aix*}
3033 @uref{#iq2000-x-elf,,iq2000-*-elf}
3035 @uref{#lm32-x-elf,,lm32-*-elf}
3037 @uref{#lm32-x-uclinux,,lm32-*-uclinux}
3039 @uref{#m32c-x-elf,,m32c-*-elf}
3041 @uref{#m32r-x-elf,,m32r-*-elf}
3043 @uref{#m68k-x-x,,m68k-*-*}
3045 @uref{#m68k-uclinux,,m68k-uclinux}
3047 @uref{#mep-x-elf,,mep-*-elf}
3049 @uref{#microblaze-x-elf,,microblaze-*-elf}
3051 @uref{#mips-x-x,,mips-*-*}
3053 @uref{#mips-sgi-irix5,,mips-sgi-irix5}
3055 @uref{#mips-sgi-irix6,,mips-sgi-irix6}
3057 @uref{#powerpc-x-x,,powerpc*-*-*}
3059 @uref{#powerpc-x-darwin,,powerpc-*-darwin*}
3061 @uref{#powerpc-x-elf,,powerpc-*-elf}
3063 @uref{#powerpc-x-linux-gnu,,powerpc*-*-linux-gnu*}
3065 @uref{#powerpc-x-netbsd,,powerpc-*-netbsd*}
3067 @uref{#powerpc-x-eabisim,,powerpc-*-eabisim}
3069 @uref{#powerpc-x-eabi,,powerpc-*-eabi}
3071 @uref{#powerpcle-x-elf,,powerpcle-*-elf}
3073 @uref{#powerpcle-x-eabisim,,powerpcle-*-eabisim}
3075 @uref{#powerpcle-x-eabi,,powerpcle-*-eabi}
3077 @uref{#s390-x-linux,,s390-*-linux*}
3079 @uref{#s390x-x-linux,,s390x-*-linux*}
3081 @uref{#s390x-ibm-tpf,,s390x-ibm-tpf*}
3083 @uref{#x-x-solaris2,,*-*-solaris2*}
3085 @uref{#sparc-x-x,,sparc*-*-*}
3087 @uref{#sparc-sun-solaris2,,sparc-sun-solaris2*}
3089 @uref{#sparc-sun-solaris210,,sparc-sun-solaris2.10}
3091 @uref{#sparc-x-linux,,sparc-*-linux*}
3093 @uref{#sparc64-x-solaris2,,sparc64-*-solaris2*}
3095 @uref{#sparcv9-x-solaris2,,sparcv9-*-solaris2*}
3097 @uref{#c6x-x-x,,c6x-*-*}
3099 @uref{#x-x-vxworks,,*-*-vxworks*}
3101 @uref{#x86-64-x-x,,x86_64-*-*, amd64-*-*}
3103 @uref{#x86-64-x-solaris210,,x86_64-*-solaris2.1[0-9]*}
3105 @uref{#xtensa-x-elf,,xtensa*-*-elf}
3107 @uref{#xtensa-x-linux,,xtensa*-*-linux*}
3109 @uref{#windows,,Microsoft Windows}
3111 @uref{#x-x-cygwin,,*-*-cygwin}
3113 @uref{#x-x-interix,,*-*-interix}
3115 @uref{#x-x-mingw32,,*-*-mingw32}
3119 @uref{#older,,Older systems}
3124 @uref{#elf,,all ELF targets} (SVR4, Solaris 2, etc.)
3130 <!-- -------- host/target specific issues start here ---------------- -->
3133 @heading @anchor{alpha-x-x}alpha*-*-*
3135 This section contains general configuration information for all
3136 alpha-based platforms using ELF (in particular, ignore this section for
3137 DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
3138 section, please read all other sections that match your target.
3140 We require binutils 2.11.2 or newer.
3141 Previous binutils releases had a number of problems with DWARF 2
3142 debugging information, not the least of which is incorrect linking of
3148 @heading @anchor{alpha-dec-osf51}alpha*-dec-osf5.1
3149 Systems using processors that implement the DEC Alpha architecture and
3150 are running the DEC/Compaq/HP Unix (DEC OSF/1, Digital UNIX, or Compaq/HP
3151 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
3153 Support for Tru64 UNIX V5.1 has been obsoleted in GCC 4.7, but can still
3154 be enabled by configuring with @option{--enable-obsolete}. Support will
3155 be removed in GCC 4.8. As of GCC 4.6, support for Tru64 UNIX V4.0 and
3156 V5.0 has been removed. As of GCC 3.2, versions before
3157 @code{alpha*-dec-osf4} are no longer supported. (These are the versions
3158 which identify themselves as DEC OSF/1.)
3160 On Tru64 UNIX, virtual memory exhausted bootstrap failures
3161 may be fixed by reconfiguring Kernel Virtual Memory and Swap parameters
3162 per the @command{/usr/sbin/sys_check} Tuning Suggestions,
3163 or applying the patch in
3164 @uref{http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html}. Depending on
3165 the OS version used, you need a data segment size between 512 MB and
3166 1 GB, so simply use @command{ulimit -Sd unlimited}.
3168 As of GNU binutils 2.21, neither GNU @command{as} nor GNU @command{ld}
3169 are supported on Tru64 UNIX, so you must not configure GCC with
3170 @option{--with-gnu-as} or @option{--with-gnu-ld}.
3172 Cross-compilers for the Tru64 UNIX target currently do not work because
3173 the auxiliary programs @command{mips-tdump} and @command{mips-tfile} can't
3174 be compiled on anything but Tru64 UNIX.
3176 GCC writes a @samp{.verstamp} directive to the assembler output file
3177 unless it is built as a cross-compiler. It gets the version to use from
3178 the system header file @file{/usr/include/stamp.h}. If you install a
3179 new version of Tru64 UNIX, you should rebuild GCC to pick up the new version
3182 GCC now supports both the native (ECOFF) debugging format used by DBX
3183 and GDB and an encapsulated STABS format for use only with GDB@. See the
3184 discussion of the @option{--with-stabs} option of @file{configure} above
3185 for more information on these formats and how to select them.
3186 @c FIXME: does this work at all? If so, perhaps make default.
3188 There is a bug in DEC's assembler that produces incorrect line numbers
3189 for ECOFF format when the @samp{.align} directive is used. To work
3190 around this problem, GCC will not emit such alignment directives
3191 while writing ECOFF format debugging information even if optimization is
3192 being performed. Unfortunately, this has the very undesirable
3193 side-effect that code addresses when @option{-O} is specified are
3194 different depending on whether or not @option{-g} is also specified.
3196 To avoid this behavior, specify @option{-gstabs+} and use GDB instead of
3197 DBX@. DEC is now aware of this problem with the assembler and hopes to
3198 provide a fix shortly.
3200 @c FIXME: still applicable?
3205 @heading @anchor{amd64-x-solaris210}amd64-*-solaris2.1[0-9]*
3207 This is a synonym for @samp{x86_64-*-solaris2.1[0-9]*}.
3212 @heading @anchor{arm-x-elf}arm-*-elf
3213 ARM-family processors. Subtargets that use the ELF object format
3214 require GNU binutils 2.13 or newer. Such subtargets include:
3215 @code{arm-*-freebsd}, @code{arm-*-netbsdelf}, @code{arm-*-*linux}
3216 and @code{arm-*-rtems}.
3221 @heading @anchor{avr}avr
3223 ATMEL AVR-family micro controllers. These are used in embedded
3224 applications. There are no standard Unix configurations.
3226 @xref{AVR Options,, AVR Options, gcc, Using the GNU Compiler
3230 See ``AVR Options'' in the main manual
3232 for the list of supported MCU types.
3234 Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
3236 Further installation notes and other useful information about AVR tools
3237 can also be obtained from:
3241 @uref{http://www.nongnu.org/avr/,,http://www.nongnu.org/avr/}
3243 @uref{http://www.amelek.gda.pl/avr/,,http://www.amelek.gda.pl/avr/}
3246 We @emph{strongly} recommend using binutils 2.13 or newer.
3248 The following error:
3250 Error: register required
3253 indicates that you should upgrade to a newer version of the binutils.
3258 @heading @anchor{bfin}Blackfin
3260 The Blackfin processor, an Analog Devices DSP.
3262 @xref{Blackfin Options,, Blackfin Options, gcc, Using the GNU Compiler
3266 See ``Blackfin Options'' in the main manual
3269 More information, and a version of binutils with support for this processor,
3270 is available at @uref{http://blackfin.uclinux.org}
3275 @heading @anchor{cr16}CR16
3277 The CR16 CompactRISC architecture is a 16-bit architecture. This architecture is
3278 used in embedded applications.
3281 @xref{CR16 Options,, CR16 Options, gcc, Using and Porting the GNU Compiler
3286 See ``CR16 Options'' in the main manual for a list of CR16-specific options.
3289 Use @samp{configure --target=cr16-elf --enable-languages=c,c++} to configure
3290 GCC@ for building a CR16 elf cross-compiler.
3292 Use @samp{configure --target=cr16-uclinux --enable-languages=c,c++} to configure
3293 GCC@ for building a CR16 uclinux cross-compiler.
3298 @heading @anchor{cris}CRIS
3300 CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
3301 series. These are used in embedded applications.
3304 @xref{CRIS Options,, CRIS Options, gcc, Using the GNU Compiler
3308 See ``CRIS Options'' in the main manual
3310 for a list of CRIS-specific options.
3312 There are a few different CRIS targets:
3315 Mainly for monolithic embedded systems. Includes a multilib for the
3316 @samp{v10} core used in @samp{ETRAX 100 LX}.
3317 @item cris-axis-linux-gnu
3318 A GNU/Linux port for the CRIS architecture, currently targeting
3319 @samp{ETRAX 100 LX} by default.
3322 For @code{cris-axis-elf} you need binutils 2.11
3323 or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer.
3325 Pre-packaged tools can be obtained from
3326 @uref{ftp://ftp.axis.com/@/pub/@/axis/@/tools/@/cris/@/compiler-kit/}. More
3327 information about this platform is available at
3328 @uref{http://developer.axis.com/}.
3333 @heading @anchor{dos}DOS
3335 Please have a look at the @uref{binaries.html,,binaries page}.
3337 You cannot install GCC by itself on MSDOS; it will not compile under
3338 any MSDOS compiler except itself. You need to get the complete
3339 compilation package DJGPP, which includes binaries as well as sources,
3340 and includes all the necessary compilation tools and libraries.
3345 @heading @anchor{epiphany-x-elf}epiphany-*-elf
3347 This configuration is intended for embedded systems.
3352 @heading @anchor{x-x-freebsd}*-*-freebsd*
3354 Support for FreeBSD 1 was discontinued in GCC 3.2. Support for
3355 FreeBSD 2 (and any mutant a.out variants of FreeBSD 3) was
3356 discontinued in GCC 4.0.
3358 In order to better utilize FreeBSD base system functionality and match
3359 the configuration of the system compiler, GCC 4.5 and above as well as
3360 GCC 4.4 past 2010-06-20 leverage SSP support in libc (which is present
3361 on FreeBSD 7 or later) and the use of @code{__cxa_atexit} by default
3362 (on FreeBSD 6 or later). The use of @code{dl_iterate_phdr} inside
3363 @file{libgcc_s.so.1} and boehm-gc (on FreeBSD 7 or later) is enabled
3364 by GCC 4.5 and above.
3366 We support FreeBSD using the ELF file format with DWARF 2 debugging
3367 for all CPU architectures. You may use @option{-gstabs} instead of
3368 @option{-g}, if you really want the old debugging format. There are
3369 no known issues with mixing object files and libraries with different
3370 debugging formats. Otherwise, this release of GCC should now match
3371 more of the configuration used in the stock FreeBSD configuration of
3372 GCC@. In particular, @option{--enable-threads} is now configured by
3373 default. However, as a general user, do not attempt to replace the
3374 system compiler with this release. Known to bootstrap and check with
3375 good results on FreeBSD 7.2-STABLE@. In the past, known to bootstrap
3376 and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4,
3377 4.5, 4.8, 4.9 and 5-CURRENT@.
3379 The version of binutils installed in @file{/usr/bin} probably works
3380 with this release of GCC@. Bootstrapping against the latest GNU
3381 binutils and/or the version found in @file{/usr/ports/devel/binutils} has
3382 been known to enable additional features and improve overall testsuite
3383 results. However, it is currently known that boehm-gc (which itself
3384 is required for java) may not configure properly on FreeBSD prior to
3385 the FreeBSD 7.0 release with GNU binutils after 2.16.1.
3390 @heading @anchor{h8300-hms}h8300-hms
3391 Renesas H8/300 series of processors.
3393 Please have a look at the @uref{binaries.html,,binaries page}.
3395 The calling convention and structure layout has changed in release 2.6.
3396 All code must be recompiled. The calling convention now passes the
3397 first three arguments in function calls in registers. Structures are no
3398 longer a multiple of 2 bytes.
3403 @heading @anchor{hppa-hp-hpux}hppa*-hp-hpux*
3404 Support for HP-UX version 9 and older was discontinued in GCC 3.4.
3406 We require using gas/binutils on all hppa platforms. Version 2.19 or
3407 later is recommended.
3409 It may be helpful to configure GCC with the
3410 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
3411 @option{--with-as=@dots{}} options to ensure that GCC can find GAS@.
3413 The HP assembler should not be used with GCC. It is rarely tested and may
3414 not work. It shouldn't be used with any languages other than C due to its
3417 Specifically, @option{-g} does not work (HP-UX uses a peculiar debugging
3418 format which GCC does not know about). It also inserts timestamps
3419 into each object file it creates, causing the 3-stage comparison test to
3420 fail during a bootstrap. You should be able to continue by saying
3421 @samp{make all-host all-target} after getting the failure from @samp{make}.
3423 Various GCC features are not supported. For example, it does not support weak
3424 symbols or alias definitions. As a result, explicit template instantiations
3425 are required when using C++. This makes it difficult if not impossible to
3426 build many C++ applications.
3428 There are two default scheduling models for instructions. These are
3429 PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
3430 architecture specified for the target machine when configuring.
3431 PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
3432 the target is a @samp{hppa1*} machine.
3434 The PROCESSOR_8000 model is not well suited to older processors. Thus,
3435 it is important to completely specify the machine architecture when
3436 configuring if you want a model other than PROCESSOR_8000. The macro
3437 TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
3438 default scheduling model is desired.
3440 As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10
3441 through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later.
3442 This namespace change might cause problems when bootstrapping with
3443 an earlier version of GCC or the HP compiler as essentially the same
3444 namespace is required for an entire build. This problem can be avoided
3445 in a number of ways. With HP cc, @env{UNIX_STD} can be set to @samp{95}
3446 or @samp{98}. Another way is to add an appropriate set of predefines
3447 to @env{CC}. The description for the @option{munix=} option contains
3448 a list of the predefines used with each standard.
3450 More specific information to @samp{hppa*-hp-hpux*} targets follows.
3455 @heading @anchor{hppa-hp-hpux10}hppa*-hp-hpux10
3457 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
3458 @code{PHCO_19798} from HP@.
3460 The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces are
3461 used for one-only code and data. This resolves many of the previous
3462 problems in using C++ on this target. However, the ABI is not compatible
3463 with the one implemented under HP-UX 11 using secondary definitions.
3468 @heading @anchor{hppa-hp-hpux11}hppa*-hp-hpux11
3470 GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot
3471 be used to compile GCC 3.0 and up.
3473 The libffi and libjava libraries haven't been ported to 64-bit HP-UX@
3476 Refer to @uref{binaries.html,,binaries} for information about obtaining
3477 precompiled GCC binaries for HP-UX@. Precompiled binaries must be obtained
3478 to build the Ada language as it can't be bootstrapped using C@. Ada is
3479 only available for the 32-bit PA-RISC runtime.
3481 Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The
3482 bundled compiler supports only traditional C; you will need either HP's
3483 unbundled compiler, or a binary distribution of GCC@.
3485 It is possible to build GCC 3.3 starting with the bundled HP compiler,
3486 but the process requires several steps. GCC 3.3 can then be used to
3487 build later versions. The fastjar program contains ISO C code and
3488 can't be built with the HP bundled compiler. This problem can be
3489 avoided by not building the Java language. For example, use the
3490 @option{--enable-languages="c,c++,f77,objc"} option in your configure
3493 There are several possible approaches to building the distribution.
3494 Binutils can be built first using the HP tools. Then, the GCC
3495 distribution can be built. The second approach is to build GCC
3496 first using the HP tools, then build binutils, then rebuild GCC@.
3497 There have been problems with various binary distributions, so it
3498 is best not to start from a binary distribution.
3500 On 64-bit capable systems, there are two distinct targets. Different
3501 installation prefixes must be used if both are to be installed on
3502 the same system. The @samp{hppa[1-2]*-hp-hpux11*} target generates code
3503 for the 32-bit PA-RISC runtime architecture and uses the HP linker.
3504 The @samp{hppa64-hp-hpux11*} target generates 64-bit code for the
3505 PA-RISC 2.0 architecture.
3507 The script config.guess now selects the target type based on the compiler
3508 detected during configuration. You must define @env{PATH} or @env{CC} so
3509 that configure finds an appropriate compiler for the initial bootstrap.
3510 When @env{CC} is used, the definition should contain the options that are
3511 needed whenever @env{CC} is used.
3513 Specifically, options that determine the runtime architecture must be
3514 in @env{CC} to correctly select the target for the build. It is also
3515 convenient to place many other compiler options in @env{CC}. For example,
3516 @env{CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"}
3517 can be used to bootstrap the GCC 3.3 branch with the HP compiler in
3518 64-bit K&R/bundled mode. The @option{+DA2.0W} option will result in
3519 the automatic selection of the @samp{hppa64-hp-hpux11*} target. The
3520 macro definition table of cpp needs to be increased for a successful
3521 build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to
3522 be defined when building with the bundled compiler, or when using the
3523 @option{-Ac} option. These defines aren't necessary with @option{-Ae}.
3525 It is best to explicitly configure the @samp{hppa64-hp-hpux11*} target
3526 with the @option{--with-ld=@dots{}} option. This overrides the standard
3527 search for ld. The two linkers supported on this target require different
3528 commands. The default linker is determined during configuration. As a
3529 result, it's not possible to switch linkers in the middle of a GCC build.
3530 This has been reported to sometimes occur in unified builds of binutils
3533 A recent linker patch must be installed for the correct operation of
3534 GCC 3.3 and later. @code{PHSS_26559} and @code{PHSS_24304} are the
3535 oldest linker patches that are known to work. They are for HP-UX
3536 11.00 and 11.11, respectively. @code{PHSS_24303}, the companion to
3537 @code{PHSS_24304}, might be usable but it hasn't been tested. These
3538 patches have been superseded. Consult the HP patch database to obtain
3539 the currently recommended linker patch for your system.
3541 The patches are necessary for the support of weak symbols on the
3542 32-bit port, and for the running of initializers and finalizers. Weak
3543 symbols are implemented using SOM secondary definition symbols. Prior
3544 to HP-UX 11, there are bugs in the linker support for secondary symbols.
3545 The patches correct a problem of linker core dumps creating shared
3546 libraries containing secondary symbols, as well as various other
3547 linking issues involving secondary symbols.
3549 GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
3550 run initializers and finalizers on the 64-bit port. The 32-bit port
3551 uses the linker @option{+init} and @option{+fini} options for the same
3552 purpose. The patches correct various problems with the +init/+fini
3553 options, including program core dumps. Binutils 2.14 corrects a
3554 problem on the 64-bit port resulting from HP's non-standard use of
3555 the .init and .fini sections for array initializers and finalizers.
3557 Although the HP and GNU linkers are both supported for the
3558 @samp{hppa64-hp-hpux11*} target, it is strongly recommended that the
3559 HP linker be used for link editing on this target.
3561 At this time, the GNU linker does not support the creation of long
3562 branch stubs. As a result, it can't successfully link binaries
3563 containing branch offsets larger than 8 megabytes. In addition,
3564 there are problems linking shared libraries, linking executables
3565 with @option{-static}, and with dwarf2 unwind and exception support.
3566 It also doesn't provide stubs for internal calls to global functions
3567 in shared libraries, so these calls can't be overloaded.
3569 The HP dynamic loader does not support GNU symbol versioning, so symbol
3570 versioning is not supported. It may be necessary to disable symbol
3571 versioning with @option{--disable-symvers} when using GNU ld.
3573 POSIX threads are the default. The optional DCE thread library is not
3574 supported, so @option{--enable-threads=dce} does not work.
3579 @heading @anchor{x-x-linux-gnu}*-*-linux-gnu
3581 Versions of libstdc++-v3 starting with 3.2.1 require bug fixes present
3582 in glibc 2.2.5 and later. More information is available in the
3583 libstdc++-v3 documentation.
3588 @heading @anchor{ix86-x-linux}i?86-*-linux*
3590 As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
3591 See @uref{http://gcc.gnu.org/PR10877,,bug 10877} for more information.
3593 If you receive Signal 11 errors when building on GNU/Linux, then it is
3594 possible you have a hardware problem. Further information on this can be
3595 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
3600 @heading @anchor{ix86-x-solaris289}i?86-*-solaris2.[89]
3601 The Sun assembler in Solaris 8 and 9 has several bugs and limitations.
3602 While GCC works around them, several features are missing, so it is
3603 @c FIXME: which ones?
3604 recommended to use the GNU assembler instead. There is no bundled
3605 version, but the current version, from GNU binutils 2.21, is known to
3608 Solaris@tie{}2/x86 doesn't support the execution of SSE/SSE2 instructions
3609 before Solaris@tie{}9 4/04, even if the CPU supports them. Programs will
3610 receive @code{SIGILL} if they try. The fix is available both in
3611 Solaris@tie{}9 Update@tie{}6 and kernel patch 112234-12 or newer. There is no
3612 corresponding patch for Solaris 8. To avoid this problem,
3613 @option{-march} defaults to @samp{pentiumpro} on Solaris 8 and 9. If
3614 you have the patch installed, you can configure GCC with an appropriate
3615 @option{--with-arch} option, but need GNU @command{as} for SSE2 support.
3620 @heading @anchor{ix86-x-solaris210}i?86-*-solaris2.10
3621 Use this for Solaris 10 or later on x86 and x86-64 systems. This
3622 configuration is supported by GCC 4.0 and later versions only. Starting
3623 with GCC 4.7, there is also a 64-bit @samp{amd64-*-solaris2.1[0-9]*} or
3624 @samp{x86_64-*-solaris2.1[0-9]*} configuration that corresponds to
3625 @samp{sparcv9-sun-solaris2*}.
3627 It is recommended that you configure GCC to use the GNU assembler, in
3628 @file{/usr/sfw/bin/gas}. The versions included in Solaris 10, from GNU
3629 binutils 2.15, and Solaris 11, from GNU binutils 2.19, work fine,
3630 although the current version, from GNU binutils
3631 2.21, is known to work, too. Recent versions of the Sun assembler in
3632 @file{/usr/ccs/bin/as} work almost as well, though.
3633 @c FIXME: as patch requirements?
3635 For linking, the Sun linker, is preferred. If you want to use the GNU
3636 linker instead, which is available in @file{/usr/sfw/bin/gld}, note that
3637 due to a packaging bug the version in Solaris 10, from GNU binutils
3638 2.15, cannot be used, while the version in Solaris 11, from GNU binutils
3639 2.19, works, as does the latest version, from GNU binutils 2.21.
3641 To use GNU @command{as}, configure with the options
3642 @option{--with-gnu-as --with-as=@//usr/@/sfw/@/bin/@/gas}. It may be necessary
3643 to configure with @option{--without-gnu-ld --with-ld=@//usr/@/ccs/@/bin/@/ld} to
3644 guarantee use of Sun @command{ld}.
3645 @c FIXME: why --without-gnu-ld --with-ld?
3650 @heading @anchor{ia64-x-linux}ia64-*-linux
3651 IA-64 processor (also known as IPF, or Itanium Processor Family)
3654 If you are using the installed system libunwind library with
3655 @option{--with-system-libunwind}, then you must use libunwind 0.98 or
3658 None of the following versions of GCC has an ABI that is compatible
3659 with any of the other versions in this list, with the exception that
3660 Red Hat 2.96 and Trillian 000171 are compatible with each other:
3661 3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
3662 This primarily affects C++ programs and programs that create shared libraries.
3663 GCC 3.1 or later is recommended for compiling linux, the kernel.
3664 As of version 3.1 GCC is believed to be fully ABI compliant, and hence no
3665 more major ABI changes are expected.
3670 @heading @anchor{ia64-x-hpux}ia64-*-hpux*
3671 Building GCC on this target requires the GNU Assembler. The bundled HP
3672 assembler will not work. To prevent GCC from using the wrong assembler,
3673 the option @option{--with-gnu-as} may be necessary.
3675 The GCC libunwind library has not been ported to HPUX@. This means that for
3676 GCC versions 3.2.3 and earlier, @option{--enable-libunwind-exceptions}
3677 is required to build GCC@. For GCC 3.3 and later, this is the default.
3678 For gcc 3.4.3 and later, @option{--enable-libunwind-exceptions} is
3679 removed and the system libunwind library will always be used.
3683 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
3685 @heading @anchor{x-ibm-aix}*-ibm-aix*
3686 Support for AIX version 3 and older was discontinued in GCC 3.4.
3687 Support for AIX version 4.2 and older was discontinued in GCC 4.5.
3689 ``out of memory'' bootstrap failures may indicate a problem with
3690 process resource limits (ulimit). Hard limits are configured in the
3691 @file{/etc/security/limits} system configuration file.
3693 GCC can bootstrap with recent versions of IBM XLC, but bootstrapping
3694 with an earlier release of GCC is recommended. Bootstrapping with XLC
3695 requires a larger data segment, which can be enabled through the
3696 @var{LDR_CNTRL} environment variable, e.g.,
3699 % LDR_CNTRL=MAXDATA=0x50000000
3703 One can start with a pre-compiled version of GCC to build from
3704 sources. One may delete GCC's ``fixed'' header files when starting
3705 with a version of GCC built for an earlier release of AIX.
3707 To speed up the configuration phases of bootstrapping and installing GCC,
3708 one may use GNU Bash instead of AIX @command{/bin/sh}, e.g.,
3711 % CONFIG_SHELL=/opt/freeware/bin/bash
3712 % export CONFIG_SHELL
3715 and then proceed as described in @uref{build.html,,the build
3716 instructions}, where we strongly recommend specifying an absolute path
3717 to invoke @var{srcdir}/configure.
3719 Because GCC on AIX is built as a 32-bit executable by default,
3720 (although it can generate 64-bit programs) the GMP and MPFR libraries
3721 required by gfortran must be 32-bit libraries. Building GMP and MPFR
3722 as static archive libraries works better than shared libraries.
3724 Errors involving @code{alloca} when building GCC generally are due
3725 to an incorrect definition of @code{CC} in the Makefile or mixing files
3726 compiled with the native C compiler and GCC@. During the stage1 phase of
3727 the build, the native AIX compiler @strong{must} be invoked as @command{cc}
3728 (not @command{xlc}). Once @command{configure} has been informed of
3729 @command{xlc}, one needs to use @samp{make distclean} to remove the
3730 configure cache files and ensure that @env{CC} environment variable
3731 does not provide a definition that will confuse @command{configure}.
3732 If this error occurs during stage2 or later, then the problem most likely
3733 is the version of Make (see above).
3735 The native @command{as} and @command{ld} are recommended for bootstrapping
3736 on AIX@. The GNU Assembler, GNU Linker, and GNU Binutils version 2.20
3737 is required to bootstrap on AIX 5@. The native AIX tools do
3738 interoperate with GCC@.
3740 AIX 5.3 TL10, AIX 6.1 TL05 and AIX 7.1 TL00 introduced an AIX
3741 assembler change that sometimes produces corrupt assembly files
3742 causing AIX linker errors. The bug breaks GCC bootstrap on AIX and
3743 can cause compilation failures with existing GCC installations. An
3744 AIX iFix for AIX 5.3 is available (APAR IZ98385 for AIX 5.3 TL10, APAR
3745 IZ98477 for AIX 5.3 TL11 and IZ98134 for AIX 5.3 TL12). Fixes for AIX
3746 6.1 (APAR IZ98732 for AIX 6.1 TL05 and APAR IZ98861 for AIX 6.1 TL06)
3747 and AIX 7.1 are in verification and packaging phases.
3749 Building @file{libstdc++.a} requires a fix for an AIX Assembler bug
3750 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a
3751 fix for another AIX Assembler bug and a co-dependent AIX Archiver fix
3752 referenced as APAR IY53606 (AIX 5.2) or as APAR IY54774 (AIX 5.1)
3754 @samp{libstdc++} in GCC 3.4 increments the major version number of the
3755 shared object and GCC installation places the @file{libstdc++.a}
3756 shared library in a common location which will overwrite the and GCC
3757 3.3 version of the shared library. Applications either need to be
3758 re-linked against the new shared library or the GCC 3.1 and GCC 3.3
3759 versions of the @samp{libstdc++} shared object needs to be available
3760 to the AIX runtime loader. The GCC 3.1 @samp{libstdc++.so.4}, if
3761 present, and GCC 3.3 @samp{libstdc++.so.5} shared objects can be
3762 installed for runtime dynamic loading using the following steps to set
3763 the @samp{F_LOADONLY} flag in the shared object for @emph{each}
3764 multilib @file{libstdc++.a} installed:
3766 Extract the shared objects from the currently installed
3767 @file{libstdc++.a} archive:
3769 % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
3772 Enable the @samp{F_LOADONLY} flag so that the shared object will be
3773 available for runtime dynamic loading, but not linking:
3775 % strip -e libstdc++.so.4 libstdc++.so.5
3778 Archive the runtime-only shared object in the GCC 3.4
3779 @file{libstdc++.a} archive:
3781 % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
3784 Linking executables and shared libraries may produce warnings of
3785 duplicate symbols. The assembly files generated by GCC for AIX always
3786 have included multiple symbol definitions for certain global variable
3787 and function declarations in the original program. The warnings should
3788 not prevent the linker from producing a correct library or runnable
3791 AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
3792 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
3793 to parse archive libraries did not handle the new format correctly.
3794 These routines are used by GCC and result in error messages during
3795 linking such as ``not a COFF file''. The version of the routines shipped
3796 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
3797 option of the archive command may be used to create archives of 32-bit
3798 objects using the original ``small format''. A correct version of the
3799 routines is shipped with AIX 4.3.2 and above.
3801 Some versions of the AIX binder (linker) can fail with a relocation
3802 overflow severe error when the @option{-bbigtoc} option is used to link
3803 GCC-produced object files into an executable that overflows the TOC@. A fix
3804 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
3805 available from IBM Customer Support and from its
3806 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3807 website as PTF U455193.
3809 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
3810 with a segmentation fault when invoked by any version of GCC@. A fix for
3811 APAR IX87327 is available from IBM Customer Support and from its
3812 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3813 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
3815 The initial assembler shipped with AIX 4.3.0 generates incorrect object
3816 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
3817 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
3818 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3819 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
3821 AIX provides National Language Support (NLS)@. Compilers and assemblers
3822 use NLS to support locale-specific representations of various data
3823 formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
3824 separating decimal fractions). There have been problems reported where
3825 GCC does not produce the same floating-point formats that the assembler
3826 expects. If one encounters this problem, set the @env{LANG}
3827 environment variable to @samp{C} or @samp{En_US}.
3829 A default can be specified with the @option{-mcpu=@var{cpu_type}}
3830 switch and using the configure option @option{--with-cpu-@var{cpu_type}}.
3835 @heading @anchor{iq2000-x-elf}iq2000-*-elf
3836 Vitesse IQ2000 processors. These are used in embedded
3837 applications. There are no standard Unix configurations.
3842 @heading @anchor{lm32-x-elf}lm32-*-elf
3843 Lattice Mico32 processor.
3844 This configuration is intended for embedded systems.
3849 @heading @anchor{lm32-x-uclinux}lm32-*-uclinux
3850 Lattice Mico32 processor.
3851 This configuration is intended for embedded systems running uClinux.
3856 @heading @anchor{m32c-x-elf}m32c-*-elf
3857 Renesas M32C processor.
3858 This configuration is intended for embedded systems.
3863 @heading @anchor{m32r-x-elf}m32r-*-elf
3864 Renesas M32R processor.
3865 This configuration is intended for embedded systems.
3870 @heading @anchor{m68k-x-x}m68k-*-*
3872 @samp{m68k-*-elf*}, @samp{m68k-*-rtems}, @samp{m68k-*-uclinux} and
3874 build libraries for both M680x0 and ColdFire processors. If you only
3875 need the M680x0 libraries, you can omit the ColdFire ones by passing
3876 @option{--with-arch=m68k} to @command{configure}. Alternatively, you
3877 can omit the M680x0 libraries by passing @option{--with-arch=cf} to
3878 @command{configure}. These targets default to 5206 or 5475 code as
3879 appropriate for the target system when
3880 configured with @option{--with-arch=cf} and 68020 code otherwise.
3882 The @samp{m68k-*-netbsd} and
3883 @samp{m68k-*-openbsd} targets also support the @option{--with-arch}
3884 option. They will generate ColdFire CFV4e code when configured with
3885 @option{--with-arch=cf} and 68020 code otherwise.
3887 You can override the default processors listed above by configuring
3888 with @option{--with-cpu=@var{target}}. This @var{target} can either
3889 be a @option{-mcpu} argument or one of the following values:
3890 @samp{m68000}, @samp{m68010}, @samp{m68020}, @samp{m68030},
3891 @samp{m68040}, @samp{m68060}, @samp{m68020-40} and @samp{m68020-60}.
3893 GCC requires at least binutils version 2.17 on these targets.
3898 @heading @anchor{m68k-x-uclinux}m68k-*-uclinux
3899 GCC 4.3 changed the uClinux configuration so that it uses the
3900 @samp{m68k-linux-gnu} ABI rather than the @samp{m68k-elf} ABI.
3901 It also added improved support for C++ and flat shared libraries,
3902 both of which were ABI changes.
3908 @heading @anchor{mep-x-elf}mep-*-elf
3909 Toshiba Media embedded Processor.
3910 This configuration is intended for embedded systems.
3915 @heading @anchor{microblaze-x-elf}microblaze-*-elf
3916 Xilinx MicroBlaze processor.
3917 This configuration is intended for embedded systems.
3922 @heading @anchor{mips-x-x}mips-*-*
3923 If on a MIPS system you get an error message saying ``does not have gp
3924 sections for all it's [sic] sectons [sic]'', don't worry about it. This
3925 happens whenever you use GAS with the MIPS linker, but there is not
3926 really anything wrong, and it is okay to use the output file. You can
3927 stop such warnings by installing the GNU linker.
3929 It would be nice to extend GAS to produce the gp tables, but they are
3930 optional, and there should not be a warning about their absence.
3932 The libstdc++ atomic locking routines for MIPS targets requires MIPS II
3933 and later. A patch went in just after the GCC 3.3 release to
3934 make @samp{mips*-*-*} use the generic implementation instead. You can also
3935 configure for @samp{mipsel-elf} as a workaround. The
3936 @samp{mips*-*-linux*} target continues to use the MIPS II routines. More
3937 work on this is expected in future releases.
3939 @c If you make --with-llsc the default for another target, please also
3940 @c update the description of the --with-llsc option.
3942 The built-in @code{__sync_*} functions are available on MIPS II and
3943 later systems and others that support the @samp{ll}, @samp{sc} and
3944 @samp{sync} instructions. This can be overridden by passing
3945 @option{--with-llsc} or @option{--without-llsc} when configuring GCC.
3946 Since the Linux kernel emulates these instructions if they are
3947 missing, the default for @samp{mips*-*-linux*} targets is
3948 @option{--with-llsc}. The @option{--with-llsc} and
3949 @option{--without-llsc} configure options may be overridden at compile
3950 time by passing the @option{-mllsc} or @option{-mno-llsc} options to
3953 MIPS systems check for division by zero (unless
3954 @option{-mno-check-zero-division} is passed to the compiler) by
3955 generating either a conditional trap or a break instruction. Using
3956 trap results in smaller code, but is only supported on MIPS II and
3957 later. Also, some versions of the Linux kernel have a bug that
3958 prevents trap from generating the proper signal (@code{SIGFPE}). To enable
3959 the use of break, use the @option{--with-divide=breaks}
3960 @command{configure} option when configuring GCC@. The default is to
3961 use traps on systems that support them.
3963 The assembler from GNU binutils 2.17 and earlier has a bug in the way
3964 it sorts relocations for REL targets (o32, o64, EABI). This can cause
3965 bad code to be generated for simple C++ programs. Also the linker
3966 from GNU binutils versions prior to 2.17 has a bug which causes the
3967 runtime linker stubs in very large programs, like @file{libgcj.so}, to
3968 be incorrectly generated. GNU Binutils 2.18 and later (and snapshots
3969 made after Nov. 9, 2006) should be free from both of these problems.
3974 @heading @anchor{mips-sgi-irix5}mips-sgi-irix5
3976 Support for IRIX 5 has been removed in GCC 4.6.
3981 @heading @anchor{mips-sgi-irix6}mips-sgi-irix6
3983 Support for IRIX 6.5 has been obsoleted in GCC 4.7, but can still be
3984 enabled by configuring with @option{--enable-obsolete}. Support will be
3985 removed in GCC 4.8. Support for IRIX 6 releases before 6.5 has been
3986 removed in GCC 4.6, as well as support for the O32 ABI. It is
3987 @emph{strongly} recommended to upgrade to at least IRIX 6.5.18. This
3988 release introduced full ISO C99 support, though for the N32 and N64 ABIs
3991 To build and use GCC on IRIX 6.5, you need the IRIX Development Foundation
3992 (IDF) and IRIX Development Libraries (IDL). They are included with the
3995 If you are using SGI's MIPSpro @command{cc} as your bootstrap compiler, you must
3996 ensure that the N32 ABI is in use. To test this, compile a simple C
3997 file with @command{cc} and then run @command{file} on the
3998 resulting object file. The output should look like:
4001 test.o: ELF N32 MSB @dots{}
4008 test.o: ELF 32-bit MSB @dots{}
4015 test.o: ELF 64-bit MSB @dots{}
4019 then your version of @command{cc} uses the O32 or N64 ABI by default. You
4020 should set the environment variable @env{CC} to @samp{cc -n32}
4021 before configuring GCC@.
4023 If you want the resulting @command{gcc} to run on old 32-bit systems
4024 with the MIPS R4400 CPU, you need to ensure that only code for the @samp{mips3}
4025 instruction set architecture (ISA) is generated. While GCC 3.x does
4026 this correctly, both GCC 2.95 and SGI's MIPSpro @command{cc} may change
4027 the ISA depending on the machine where GCC is built. Using one of them
4028 as the bootstrap compiler may result in @samp{mips4} code, which won't run at
4029 all on @samp{mips3}-only systems. For the test program above, you should see:
4032 test.o: ELF N32 MSB mips-3 @dots{}
4039 test.o: ELF N32 MSB mips-4 @dots{}
4043 instead, you should set the environment variable @env{CC} to @samp{cc
4044 -n32 -mips3} or @samp{gcc -mips3} respectively before configuring GCC@.
4046 MIPSpro C 7.4 may cause bootstrap failures, due to a bug when inlining
4047 @code{memcmp}. Either add @code{-U__INLINE_INTRINSICS} to the @env{CC}
4048 environment variable as a workaround or upgrade to MIPSpro C 7.4.1m.
4050 GCC on IRIX 6.5 is usually built to support the N32 and N64 ABIs. If
4051 you build GCC on a system that doesn't have the N64 libraries installed
4052 or cannot run 64-bit binaries,
4053 you need to configure with @option{--disable-multilib} so GCC doesn't
4055 Look for @file{/usr/lib64/libc.so.1} to see if you
4056 have the 64-bit libraries installed.
4058 GCC must be configured with GNU @command{as}. The latest version, from GNU
4059 binutils 2.21, is known to work. On the other hand, bootstrap fails
4060 with GNU @command{ld} at least since GNU binutils 2.17.
4062 The @option{--enable-libgcj}
4063 option is disabled by default: IRIX 6 uses a very low default limit
4064 (20480) for the command line length. Although @command{libtool} contains a
4065 workaround for this problem, at least the N64 @samp{libgcj} is known not
4066 to build despite this, running into an internal error of the native
4067 @command{ld}. A sure fix is to increase this limit (@samp{ncargs}) to
4068 its maximum of 262144 bytes. If you have root access, you can use the
4069 @command{systune} command to do this.
4070 @c FIXME: does this work with current libtool?
4072 @code{wchar_t} support in @samp{libstdc++} is not available for old
4073 IRIX 6.5.x releases, @math{x < 19}. The problem cannot be autodetected
4074 and in order to build GCC for such targets you need to configure with
4075 @option{--disable-wchar_t}.
4080 @heading @anchor{moxie-x-elf}moxie-*-elf
4081 The moxie processor. See @uref{http://moxielogic.org/} for more
4082 information about this processor.
4087 @heading @anchor{powerpc-x-x}powerpc-*-*
4089 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
4090 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
4093 @uref{ftp://ftp.kernel.org/pub/linux/devel/binutils,,binutils 2.15}
4094 or newer for a working GCC@.
4099 @heading @anchor{powerpc-x-darwin}powerpc-*-darwin*
4100 PowerPC running Darwin (Mac OS X kernel).
4102 Pre-installed versions of Mac OS X may not include any developer tools,
4103 meaning that you will not be able to build GCC from source. Tool
4104 binaries are available at
4105 @uref{http://opensource.apple.com/}.
4107 This version of GCC requires at least cctools-590.36. The
4108 cctools-590.36 package referenced from
4109 @uref{http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html} will not work
4110 on systems older than 10.3.9 (aka darwin7.9.0).
4115 @heading @anchor{powerpc-x-elf}powerpc-*-elf
4116 PowerPC system in big endian mode, running System V.4.
4121 @heading @anchor{powerpc-x-linux-gnu}powerpc*-*-linux-gnu*
4123 PowerPC system in big endian mode running Linux.
4128 @heading @anchor{powerpc-x-netbsd}powerpc-*-netbsd*
4129 PowerPC system in big endian mode running NetBSD@.
4134 @heading @anchor{powerpc-x-eabisim}powerpc-*-eabisim
4135 Embedded PowerPC system in big endian mode for use in running under the
4141 @heading @anchor{powerpc-x-eabi}powerpc-*-eabi
4142 Embedded PowerPC system in big endian mode.
4147 @heading @anchor{powerpcle-x-elf}powerpcle-*-elf
4148 PowerPC system in little endian mode, running System V.4.
4153 @heading @anchor{powerpcle-x-eabisim}powerpcle-*-eabisim
4154 Embedded PowerPC system in little endian mode for use in running under
4160 @heading @anchor{powerpcle-x-eabi}powerpcle-*-eabi
4161 Embedded PowerPC system in little endian mode.
4166 @heading @anchor{rl78-x-elf}rl78-*-elf
4167 The Renesas RL78 processor.
4168 This configuration is intended for embedded systems.
4173 @heading @anchor{rx-x-elf}rx-*-elf
4174 The Renesas RX processor. See
4175 @uref{http://eu.renesas.com/fmwk.jsp?cnt=rx600_series_landing.jsp&fp=/products/mpumcu/rx_family/rx600_series}
4176 for more information about this processor.
4181 @heading @anchor{s390-x-linux}s390-*-linux*
4182 S/390 system running GNU/Linux for S/390@.
4187 @heading @anchor{s390x-x-linux}s390x-*-linux*
4188 zSeries system (64-bit) running GNU/Linux for zSeries@.
4193 @heading @anchor{s390x-ibm-tpf}s390x-ibm-tpf*
4194 zSeries system (64-bit) running TPF@. This platform is
4195 supported as cross-compilation target only.
4200 @c Please use Solaris 2 to refer to all release of Solaris, starting
4201 @c with 2.0 until 2.6, 7, 8, etc. Solaris 1 was a marketing name for
4202 @c SunOS 4 releases which we don't use to avoid confusion. Solaris
4203 @c alone is too unspecific and must be avoided.
4204 @heading @anchor{x-x-solaris2}*-*-solaris2*
4206 Support for Solaris 8 has been obsoleted in GCC 4.7, but can still be
4207 enabled by configuring with @option{--enable-obsolete}. Support will be
4208 removed in GCC 4.8. Support for Solaris 7 has been removed in GCC 4.6.
4210 Sun does not ship a C compiler with Solaris 2, though you can download
4211 the Sun Studio compilers for free. Alternatively,
4212 you can install a pre-built GCC to bootstrap and install GCC. See the
4213 @uref{binaries.html,,binaries page} for details.
4215 The Solaris 2 @command{/bin/sh} will often fail to configure
4216 @samp{libstdc++-v3}, @samp{boehm-gc} or @samp{libjava}. We therefore
4217 recommend using the following initial sequence of commands
4220 % CONFIG_SHELL=/bin/ksh
4221 % export CONFIG_SHELL
4225 and proceed as described in @uref{configure.html,,the configure instructions}.
4226 In addition we strongly recommend specifying an absolute path to invoke
4227 @command{@var{srcdir}/configure}.
4229 Solaris 2 comes with a number of optional OS packages. Some of these
4230 are needed to use GCC fully, namely @code{SUNWarc},
4231 @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
4232 @code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all
4233 optional packages when installing Solaris 2, you will need to verify that
4234 the packages that GCC needs are installed.
4236 To check whether an optional package is installed, use
4237 the @command{pkginfo} command. To add an optional package, use the
4238 @command{pkgadd} command. For further details, see the Solaris 2
4241 Trying to use the linker and other tools in
4242 @file{/usr/ucb} to install GCC has been observed to cause trouble.
4243 For example, the linker may hang indefinitely. The fix is to remove
4244 @file{/usr/ucb} from your @env{PATH}.
4246 The build process works more smoothly with the legacy Sun tools so, if you
4247 have @file{/usr/xpg4/bin} in your @env{PATH}, we recommend that you place
4248 @file{/usr/bin} before @file{/usr/xpg4/bin} for the duration of the build.
4250 We recommend the use of the Sun assembler or the GNU assembler, in
4251 conjunction with the Sun linker. The GNU @command{as}
4252 versions included in Solaris 10, from GNU binutils 2.15, and Solaris 11,
4253 from GNU binutils 2.19, are known to work. They can be found in
4254 @file{/usr/sfw/bin/gas}. Current versions of GNU binutils (2.21)
4255 are known to work as well. Note that your mileage may vary
4256 if you use a combination of the GNU tools and the Sun tools: while the
4257 combination GNU @command{as} + Sun @command{ld} should reasonably work,
4258 the reverse combination Sun @command{as} + GNU @command{ld} is known to
4259 cause memory corruption at runtime in some cases for C++ programs.
4261 GNU @command{ld} usually works as well, although the version included in
4262 Solaris 10 cannot be used due to several bugs. Again, the current
4263 version (2.21) is known to work, but generally lacks platform specific
4264 features, so better stay with Sun @command{ld}.
4266 To enable symbol versioning in @samp{libstdc++} with Sun @command{ld},
4267 you need to have any version of GNU @command{c++filt}, which is part of
4268 GNU binutils. @samp{libstdc++} symbol versioning will be disabled if no
4269 appropriate version is found. Sun @command{c++filt} from the Sun Studio
4270 compilers does @emph{not} work.
4272 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
4273 newer: @command{g++} will complain that types are missing. These headers
4274 assume that omitting the type means @code{int}; this assumption worked for
4275 C90 but is wrong for C++, and is now wrong for C99 also.
4277 @command{g++} accepts such (invalid) constructs with the option
4278 @option{-fpermissive}; it will assume that any missing type is @code{int}
4279 (as defined by C90).
4281 There are patches for Solaris 8 (108652-24 or newer for SPARC,
4282 108653-22 for Intel) that fix this bug.
4284 Sun bug 4927647 sometimes causes random spurious testsuite failures
4285 related to missing diagnostic output. This bug doesn't affect GCC
4286 itself, rather it is a kernel bug triggered by the @command{expect}
4287 program which is used only by the GCC testsuite driver. When the bug
4288 causes the @command{expect} program to miss anticipated output, extra
4289 testsuite failures appear.
4291 There are patches for Solaris 8 (117350-12 or newer for SPARC,
4292 117351-12 or newer for Intel) and Solaris 9 (117171-11 or newer for
4293 SPARC, 117172-11 or newer for Intel) that address this problem.
4295 Solaris@tie{}8 provides an alternate implementation of the thread libraries,
4296 @samp{libpthread} and @samp{libthread}. They are required for TLS
4297 support and have been made the default in Solaris@tie{}9, so they are always
4298 used on Solaris@tie{}8.
4300 Thread-local storage (TLS) is supported in Solaris@tie{}8 and 9, but requires
4301 some patches. The @samp{libthread} patches provide the
4302 @code{__tls_get_addr} (SPARC, 64-bit x86) resp.@ @code{___tls_get_addr}
4303 (32-bit x86) functions. On Solaris@tie{}8, you need 108993-26 or newer on
4304 SPARC, 108994-26 or newer on Intel. On Solaris@tie{}9, the necessary support
4305 on SPARC is present since FCS, while 114432-05 or newer is required on
4306 Intel. Additionally, on Solaris@tie{}8, patch 109147-14 or newer on SPARC or
4307 109148-22 or newer on Intel are required for the Sun @command{ld} and
4308 runtime linker (@command{ld.so.1}) support. Again, Solaris@tie{}9/SPARC
4309 works since FCS, while 113986-02 is required on Intel. The linker
4310 patches must be installed even if GNU @command{ld} is used. Sun
4311 @command{as} in Solaris@tie{}8 and 9 doesn't support the necessary
4312 relocations, so GNU @command{as} must be used. The @command{configure}
4313 script checks for those prerequisites and automatically enables TLS
4314 support if they are met. Although those minimal patch versions should
4315 work, it is recommended to use the latest patch versions which include
4316 additional bug fixes.
4321 @heading @anchor{sparc-x-x}sparc*-*-*
4323 This section contains general configuration information for all
4324 SPARC-based platforms. In addition to reading this section, please
4325 read all other sections that match your target.
4327 Newer versions of the GNU Multiple Precision Library (GMP), the MPFR
4328 library and the MPC library are known to be miscompiled by earlier
4329 versions of GCC on these platforms. We therefore recommend the use
4330 of the exact versions of these libraries listed as minimal versions
4331 in @uref{prerequisites.html,,the prerequisites}.
4336 @heading @anchor{sparc-sun-solaris2}sparc-sun-solaris2*
4338 When GCC is configured to use GNU binutils 2.14 or later, the binaries
4339 produced are smaller than the ones produced using Sun's native tools;
4340 this difference is quite significant for binaries containing debugging
4343 Starting with Solaris 7, the operating system is capable of executing
4344 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
4345 this; the @option{-m64} option enables 64-bit code generation.
4346 However, if all you want is code tuned for the UltraSPARC CPU, you
4347 should try the @option{-mtune=ultrasparc} option instead, which produces
4348 code that, unlike full 64-bit code, can still run on non-UltraSPARC
4351 When configuring on a Solaris 7 or later system that is running a kernel
4352 that supports only 32-bit binaries, one must configure with
4353 @option{--disable-multilib}, since we will not be able to build the
4354 64-bit target libraries.
4356 GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of
4357 the GNU compiler (especially GCC 3.0.x versions), which lead to the
4358 miscompilation of the stage1 compiler and the subsequent failure of the
4359 bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary
4360 stage, i.e.@: to bootstrap that compiler with the base compiler and then
4361 use it to bootstrap the final compiler.
4363 GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE Studio 7)
4364 and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a bootstrap
4365 failure in form of a miscompilation of the stage1 compiler by the Sun
4366 compiler. This is Sun bug 4974440. This is fixed with patch 112760-07.
4368 GCC 3.4 changed the default debugging format from Stabs to DWARF-2 for
4369 32-bit code on Solaris 7 and later. If you use the Sun assembler, this
4370 change apparently runs afoul of Sun bug 4910101 (which is referenced as
4371 an x86-only problem by Sun, probably because they do not use DWARF-2).
4372 A symptom of the problem is that you cannot compile C++ programs like
4373 @command{groff} 1.19.1 without getting messages similar to the following:
4376 ld: warning: relocation error: R_SPARC_UA32: @dots{}
4377 external symbolic relocation against non-allocatable section
4378 .debug_info cannot be processed at runtime: relocation ignored.
4382 To work around this problem, compile with @option{-gstabs+} instead of
4385 When configuring the GNU Multiple Precision Library (GMP), the MPFR
4386 library or the MPC library on a Solaris 7 or later system, the canonical
4387 target triplet must be specified as the @command{build} parameter on the
4388 configure line. This target triplet can be obtained by invoking @command{./config.guess} in the toplevel source directory of GCC (and
4389 not that of GMP or MPFR or MPC). For example on a Solaris 9 system:
4392 % ./configure --build=sparc-sun-solaris2.9 --prefix=xxx
4398 @heading @anchor{sparc-sun-solaris210}sparc-sun-solaris2.10
4400 There is a bug in older versions of the Sun assembler which breaks
4401 thread-local storage (TLS). A typical error message is
4404 ld: fatal: relocation error: R_SPARC_TLS_LE_HIX22: file /var/tmp//ccamPA1v.o:
4405 symbol <unknown>: bad symbol type SECT: symbol type must be TLS
4409 This bug is fixed in Sun patch 118683-03 or later.
4414 @heading @anchor{sparc-x-linux}sparc-*-linux*
4416 GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
4417 or newer on this platform. All earlier binutils and glibc
4418 releases mishandled unaligned relocations on @code{sparc-*-*} targets.
4424 @heading @anchor{sparc64-x-solaris2}sparc64-*-solaris2*
4426 When configuring the GNU Multiple Precision Library (GMP) or the
4427 MPFR library, the canonical target triplet must be specified as
4428 the @command{build} parameter on the configure line. For example
4429 on a Solaris 9 system:
4432 % ./configure --build=sparc64-sun-solaris2.9 --prefix=xxx
4435 The following compiler flags must be specified in the configure
4436 step in order to bootstrap this target with the Sun compiler:
4439 % CC="cc -xarch=v9 -xildoff" @var{srcdir}/configure [@var{options}] [@var{target}]
4443 @option{-xarch=v9} specifies the SPARC-V9 architecture to the Sun toolchain
4444 and @option{-xildoff} turns off the incremental linker.
4449 @heading @anchor{sparcv9-x-solaris2}sparcv9-*-solaris2*
4451 This is a synonym for @samp{sparc64-*-solaris2*}.
4456 @heading @anchor{c6x-x-x}c6x-*-*
4458 The C6X family of processors. This port requires binutils-2.22 or newer.
4463 @heading @anchor{x-x-vxworks}*-*-vxworks*
4464 Support for VxWorks is in flux. At present GCC supports @emph{only} the
4465 very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC@.
4466 We welcome patches for other architectures supported by VxWorks 5.5.
4467 Support for VxWorks AE would also be welcome; we believe this is merely
4468 a matter of writing an appropriate ``configlette'' (see below). We are
4469 not interested in supporting older, a.out or COFF-based, versions of
4472 VxWorks comes with an older version of GCC installed in
4473 @file{@var{$WIND_BASE}/host}; we recommend you do not overwrite it.
4474 Choose an installation @var{prefix} entirely outside @var{$WIND_BASE}.
4475 Before running @command{configure}, create the directories @file{@var{prefix}}
4476 and @file{@var{prefix}/bin}. Link or copy the appropriate assembler,
4477 linker, etc.@: into @file{@var{prefix}/bin}, and set your @var{PATH} to
4478 include that directory while running both @command{configure} and
4481 You must give @command{configure} the
4482 @option{--with-headers=@var{$WIND_BASE}/target/h} switch so that it can
4483 find the VxWorks system headers. Since VxWorks is a cross compilation
4484 target only, you must also specify @option{--target=@var{target}}.
4485 @command{configure} will attempt to create the directory
4486 @file{@var{prefix}/@var{target}/sys-include} and copy files into it;
4487 make sure the user running @command{configure} has sufficient privilege
4490 GCC's exception handling runtime requires a special ``configlette''
4491 module, @file{contrib/gthr_supp_vxw_5x.c}. Follow the instructions in
4492 that file to add the module to your kernel build. (Future versions of
4493 VxWorks will incorporate this module.)
4498 @heading @anchor{x86-64-x-x}x86_64-*-*, amd64-*-*
4500 GCC supports the x86-64 architecture implemented by the AMD64 processor
4501 (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD@.
4502 On GNU/Linux the default is a bi-arch compiler which is able to generate
4503 both 64-bit x86-64 and 32-bit x86 code (via the @option{-m32} switch).
4508 @heading @anchor{x86-64-x-solaris210}x86_64-*-solaris2.1[0-9]*
4510 GCC also supports the x86-64 architecture implemented by the AMD64
4511 processor (@samp{amd64-*-*} is an alias for @samp{x86_64-*-*}) on
4512 Solaris 10 or later. Unlike other systems, without special options a
4513 bi-arch compiler is built which generates 32-bit code by default, but
4514 can generate 64-bit x86-64 code with the @option{-m64} switch. Since
4515 GCC 4.7, there is also configuration that defaults to 64-bit code, but
4516 can generate 32-bit code with @option{-m32}. To configure and build
4517 this way, you have to provide all support libraries like @file{libgmp}
4518 as 64-bit code, configure with @option{--target=x86_64-pc-solaris2.1x}
4519 and @samp{CC=gcc -m64}.
4524 @heading @anchor{xtensa-x-elf}xtensa*-*-elf
4526 This target is intended for embedded Xtensa systems using the
4527 @samp{newlib} C library. It uses ELF but does not support shared
4528 objects. Designed-defined instructions specified via the
4529 Tensilica Instruction Extension (TIE) language are only supported
4530 through inline assembly.
4532 The Xtensa configuration information must be specified prior to
4533 building GCC@. The @file{include/xtensa-config.h} header
4534 file contains the configuration information. If you created your
4535 own Xtensa configuration with the Xtensa Processor Generator, the
4536 downloaded files include a customized copy of this header file,
4537 which you can use to replace the default header file.
4542 @heading @anchor{xtensa-x-linux}xtensa*-*-linux*
4544 This target is for Xtensa systems running GNU/Linux. It supports ELF
4545 shared objects and the GNU C library (glibc). It also generates
4546 position-independent code (PIC) regardless of whether the
4547 @option{-fpic} or @option{-fPIC} options are used. In other
4548 respects, this target is the same as the
4549 @uref{#xtensa*-*-elf,,@samp{xtensa*-*-elf}} target.
4554 @heading @anchor{windows}Microsoft Windows
4556 @subheading Intel 16-bit versions
4557 The 16-bit versions of Microsoft Windows, such as Windows 3.1, are not
4560 However, the 32-bit port has limited support for Microsoft
4561 Windows 3.11 in the Win32s environment, as a target only. See below.
4563 @subheading Intel 32-bit versions
4565 The 32-bit versions of Windows, including Windows 95, Windows NT, Windows
4566 XP, and Windows Vista, are supported by several different target
4567 platforms. These targets differ in which Windows subsystem they target
4568 and which C libraries are used.
4571 @item Cygwin @uref{#x-x-cygwin,,*-*-cygwin}: Cygwin provides a user-space
4572 Linux API emulation layer in the Win32 subsystem.
4573 @item Interix @uref{#x-x-interix,,*-*-interix}: The Interix subsystem
4574 provides native support for POSIX.
4575 @item MinGW @uref{#x-x-mingw32,,*-*-mingw32}: MinGW is a native GCC port for
4576 the Win32 subsystem that provides a subset of POSIX.
4577 @item MKS i386-pc-mks: NuTCracker from MKS. See
4578 @uref{http://www.mkssoftware.com/} for more information.
4581 @subheading Intel 64-bit versions
4583 GCC contains support for x86-64 using the mingw-w64
4584 runtime library, available from @uref{http://mingw-w64.sourceforge.net/}.
4585 This library should be used with the target triple x86_64-pc-mingw32.
4587 Presently Windows for Itanium is not supported.
4589 @subheading Windows CE
4591 Windows CE is supported as a target only on ARM (arm-wince-pe), Hitachi
4592 SuperH (sh-wince-pe), and MIPS (mips-wince-pe).
4594 @subheading Other Windows Platforms
4596 GCC no longer supports Windows NT on the Alpha or PowerPC.
4598 GCC no longer supports the Windows POSIX subsystem. However, it does
4599 support the Interix subsystem. See above.
4601 Old target names including *-*-winnt and *-*-windowsnt are no longer used.
4603 PW32 (i386-pc-pw32) support was never completed, and the project seems to
4604 be inactive. See @uref{http://pw32.sourceforge.net/} for more information.
4606 UWIN support has been removed due to a lack of maintenance.
4611 @heading @anchor{x-x-cygwin}*-*-cygwin
4613 Ports of GCC are included with the
4614 @uref{http://www.cygwin.com/,,Cygwin environment}.
4616 GCC will build under Cygwin without modification; it does not build
4617 with Microsoft's C++ compiler and there are no plans to make it do so.
4619 The Cygwin native compiler can be configured to target any 32-bit x86
4620 cpu architecture desired; the default is i686-pc-cygwin. It should be
4621 used with as up-to-date a version of binutils as possible; use either
4622 the latest official GNU binutils release in the Cygwin distribution,
4623 or version 2.20 or above if building your own.
4628 @heading @anchor{x-x-interix}*-*-interix
4630 The Interix target is used by OpenNT, Interix, Services For UNIX (SFU),
4631 and Subsystem for UNIX-based Applications (SUA). Applications compiled
4632 with this target run in the Interix subsystem, which is separate from
4633 the Win32 subsystem. This target was last known to work in GCC 3.3.
4638 @heading @anchor{x-x-mingw32}*-*-mingw32
4640 GCC will build with and support only MinGW runtime 3.12 and later.
4641 Earlier versions of headers are incompatible with the new default semantics
4642 of @code{extern inline} in @code{-std=c99} and @code{-std=gnu99} modes.
4647 @heading @anchor{older}Older systems
4649 GCC contains support files for many older (1980s and early
4650 1990s) Unix variants. For the most part, support for these systems
4651 has not been deliberately removed, but it has not been maintained for
4652 several years and may suffer from bitrot.
4654 Starting with GCC 3.1, each release has a list of ``obsoleted'' systems.
4655 Support for these systems is still present in that release, but
4656 @command{configure} will fail unless the @option{--enable-obsolete}
4657 option is given. Unless a maintainer steps forward, support for these
4658 systems will be removed from the next release of GCC@.
4660 Support for old systems as hosts for GCC can cause problems if the
4661 workarounds for compiler, library and operating system bugs affect the
4662 cleanliness or maintainability of the rest of GCC@. In some cases, to
4663 bring GCC up on such a system, if still possible with current GCC, may
4664 require first installing an old version of GCC which did work on that
4665 system, and using it to compile a more recent GCC, to avoid bugs in the
4666 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
4667 @file{old-releases} directory on the @uref{../mirrors.html,,GCC mirror
4668 sites}. Header bugs may generally be avoided using
4669 @command{fixincludes}, but bugs or deficiencies in libraries and the
4670 operating system may still cause problems.
4672 Support for older systems as targets for cross-compilation is less
4673 problematic than support for them as hosts for GCC; if an enthusiast
4674 wishes to make such a target work again (including resurrecting any of
4675 the targets that never worked with GCC 2, starting from the last
4676 version before they were removed), patches
4677 @uref{../contribute.html,,following the usual requirements} would be
4678 likely to be accepted, since they should not affect the support for more
4681 For some systems, old versions of GNU binutils may also be useful,
4682 and are available from @file{pub/binutils/old-releases} on
4683 @uref{http://sourceware.org/mirrors.html,,sourceware.org mirror sites}.
4685 Some of the information on specific systems above relates to
4686 such older systems, but much of the information
4687 about GCC on such systems (which may no longer be applicable to
4688 current GCC) is to be found in the GCC texinfo manual.
4693 @heading @anchor{elf}all ELF targets (SVR4, Solaris 2, etc.)
4695 C++ support is significantly better on ELF targets if you use the
4696 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
4697 inlines, vtables and template instantiations will be discarded
4706 @uref{./index.html,,Return to the GCC Installation page}
4710 @c ***Old documentation******************************************************
4712 @include install-old.texi
4718 @uref{./index.html,,Return to the GCC Installation page}
4722 @c ***GFDL********************************************************************
4730 @uref{./index.html,,Return to the GCC Installation page}
4734 @c ***************************************************************************
4735 @c Part 6 The End of the Document
4737 @comment node-name, next, previous, up
4738 @node Concept Index, , GNU Free Documentation License, Top
4742 @unnumbered Concept Index