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 Free Software Foundation, Inc.
49 @c *** Converted to texinfo by Dean Wakerley, dean@wakerley.com
51 @c IMPORTANT: whenever you modify this file, run `install.texi2html' to
52 @c test the generation of HTML documents for the gcc.gnu.org web pages.
54 @c Do not use @footnote{} in this file as it breaks install.texi2html!
56 @c Include everything if we're not making html
60 @set prerequisiteshtml
71 @c Part 2 Summary Description and Copyright
73 Copyright @copyright{} 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
74 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
76 Permission is granted to copy, distribute and/or modify this document
77 under the terms of the GNU Free Documentation License, Version 1.2 or
78 any later version published by the Free Software Foundation; with no
79 Invariant Sections, the Front-Cover texts being (a) (see below), and
80 with the Back-Cover Texts being (b) (see below). A copy of the
81 license is included in the section entitled ``@uref{./gfdl.html,,GNU
82 Free Documentation License}''.
84 (a) The FSF's Front-Cover Text is:
88 (b) The FSF's Back-Cover Text is:
90 You have freedom to copy and modify this GNU Manual, like GNU
91 software. Copies published by the Free Software Foundation raise
92 funds for GNU development.
97 @dircategory Software development
99 * gccinstall: (gccinstall). Installing the GNU Compiler Collection.
102 @c Part 3 Titlepage and Copyright
104 @title Installing GCC
107 @c The following two commands start the copyright page.
109 @vskip 0pt plus 1filll
113 @c Part 4 Top node, Master Menu, and/or Table of Contents
116 @comment node-name, next, Previous, up
119 * Installing GCC:: This document describes the generic installation
120 procedure for GCC as well as detailing some target
121 specific installation instructions.
123 * Specific:: Host/target specific installation notes for GCC.
124 * Binaries:: Where to get pre-compiled binaries.
126 * Old:: Old installation documentation.
128 * GNU Free Documentation License:: How you can copy and share this manual.
129 * Concept Index:: This index has two entries.
137 @c Part 5 The Body of the Document
138 @c ***Installing GCC**********************************************************
140 @comment node-name, next, previous, up
141 @node Installing GCC, Binaries, , Top
145 @chapter Installing GCC
148 The latest version of this document is always available at
149 @uref{http://gcc.gnu.org/install/,,http://gcc.gnu.org/install/}.
151 This document describes the generic installation procedure for GCC as well
152 as detailing some target specific installation instructions.
154 GCC includes several components that previously were separate distributions
155 with their own installation instructions. This document supersedes all
156 package specific installation instructions.
158 @emph{Before} starting the build/install procedure please check the
160 @ref{Specific, host/target specific installation notes}.
163 @uref{specific.html,,host/target specific installation notes}.
165 We recommend you browse the entire generic installation instructions before
168 Lists of successful builds for released versions of GCC are
169 available at @uref{http://gcc.gnu.org/buildstat.html}.
170 These lists are updated as new information becomes available.
172 The installation procedure itself is broken into five steps.
177 * Downloading the source::
180 * Testing:: (optional)
187 @uref{prerequisites.html,,Prerequisites}
189 @uref{download.html,,Downloading the source}
191 @uref{configure.html,,Configuration}
193 @uref{build.html,,Building}
195 @uref{test.html,,Testing} (optional)
197 @uref{finalinstall.html,,Final install}
201 Please note that GCC does not support @samp{make uninstall} and probably
202 won't do so in the near future as this would open a can of worms. Instead,
203 we suggest that you install GCC into a directory of its own and simply
204 remove that directory when you do not need that specific version of GCC
205 any longer, and, if shared libraries are installed there as well, no
206 more binaries exist that use them.
209 There are also some @uref{old.html,,old installation instructions},
210 which are mostly obsolete but still contain some information which has
211 not yet been merged into the main part of this manual.
219 @uref{./index.html,,Return to the GCC Installation page}
225 @c ***Prerequisites**************************************************
227 @comment node-name, next, previous, up
228 @node Prerequisites, Downloading the source, , Installing GCC
230 @ifset prerequisiteshtml
232 @chapter Prerequisites
234 @cindex Prerequisites
236 GCC requires that various tools and packages be available for use in the
237 build procedure. Modifying GCC sources requires additional tools
240 @heading Tools/packages necessary for building GCC
242 @item ISO C90 compiler
243 Necessary to bootstrap GCC, although versions of GCC prior
244 to 3.4 also allow bootstrapping with a traditional (K&R) C compiler.
246 To build all languages in a cross-compiler or other configuration where
247 3-stage bootstrap is not performed, you need to start with an existing
248 GCC binary (version 2.95 or later) because source code for language
249 frontends other than C might use GCC extensions.
253 In order to build the Ada compiler (GNAT) you must already have GNAT
254 installed because portions of the Ada frontend are written in Ada (with
255 GNAT extensions.) Refer to the Ada installation instructions for more
256 specific information.
258 @item A ``working'' POSIX compatible shell, or GNU bash
260 Necessary when running @command{configure} because some
261 @command{/bin/sh} shells have bugs and may crash when configuring the
262 target libraries. In other cases, @command{/bin/sh} or @command{ksh}
263 have disastrous corner-case performance problems. This
264 can cause target @command{configure} runs to literally take days to
265 complete in some cases.
267 So on some platforms @command{/bin/ksh} is sufficient, on others it
268 isn't. See the host/target specific instructions for your platform, or
269 use @command{bash} to be sure. Then set @env{CONFIG_SHELL} in your
270 environment to your ``good'' shell prior to running
271 @command{configure}/@command{make}.
273 @command{zsh} is not a fully compliant POSIX shell and will not
274 work when configuring GCC@.
276 @item A POSIX or SVR4 awk
278 Necessary for creating some of the generated source files for GCC@.
279 If in doubt, use a recent GNU awk version, as some of the older ones
280 are broken. GNU awk version 3.1.5 is known to work.
284 Necessary in some circumstances, optional in others. See the
285 host/target specific instructions for your platform for the exact
288 @item gzip version 1.2.4 (or later) or
289 @itemx bzip2 version 1.0.2 (or later)
291 Necessary to uncompress GCC @command{tar} files when source code is
292 obtained via FTP mirror sites.
294 @item GNU make version 3.80 (or later)
296 You must have GNU make installed to build GCC@.
298 @item GNU tar version 1.14 (or later)
300 Necessary (only on some platforms) to untar the source code. Many
301 systems' @command{tar} programs will also work, only try GNU
302 @command{tar} if you have problems.
304 @item GNU Multiple Precision Library (GMP) version 4.1 (or later)
306 Necessary to build GCC@. If you do not have it installed in your
307 library search path, you will have to configure with the
308 @option{--with-gmp} configure option. See also
309 @option{--with-gmp-lib} and @option{--with-gmp-include}.
311 @item MPFR Library version 2.3.0 (or later)
313 Necessary to build GCC@. It can be downloaded from
314 @uref{http://www.mpfr.org/}. The version of MPFR that is bundled with
315 GMP 4.1.x contains numerous bugs. Although GCC may appear to function
316 with the buggy versions of MPFR, there are a few bugs that will not be
317 fixed when using this version. It is strongly recommended to upgrade
318 to the recommended version of MPFR.
320 The @option{--with-mpfr} configure option should be used if your MPFR
321 Library is not installed in your default library search path. See
322 also @option{--with-mpfr-lib} and @option{--with-mpfr-include}.
324 @item @command{jar}, or InfoZIP (@command{zip} and @command{unzip})
326 Necessary to build libgcj, the GCJ runtime.
331 @heading Tools/packages necessary for modifying GCC
333 @item autoconf version 2.59
334 @itemx GNU m4 version 1.4 (or later)
336 Necessary when modifying @file{configure.ac}, @file{aclocal.m4}, etc.@:
337 to regenerate @file{configure} and @file{config.in} files.
339 @item automake version 1.9.6
341 Necessary when modifying a @file{Makefile.am} file to regenerate its
342 associated @file{Makefile.in}.
344 Much of GCC does not use automake, so directly edit the @file{Makefile.in}
345 file. Specifically this applies to the @file{gcc}, @file{intl},
346 @file{libcpp}, @file{libiberty}, @file{libobjc} directories as well
347 as any of their subdirectories.
349 For directories that use automake, GCC requires the latest release in
350 the 1.9.x series, which is currently 1.9.6. When regenerating a directory
351 to a newer version, please update all the directories using an older 1.9.x
352 to the latest released version.
354 @item gettext version 0.14.5 (or later)
356 Needed to regenerate @file{gcc.pot}.
358 @item gperf version 2.7.2 (or later)
360 Necessary when modifying @command{gperf} input files, e.g.@:
361 @file{gcc/cp/cfns.gperf} to regenerate its associated header file, e.g.@:
362 @file{gcc/cp/cfns.h}.
368 Necessary to run the GCC testsuite; see the section on testing for details.
370 @item autogen version 5.5.4 (or later) and
371 @itemx guile version 1.4.1 (or later)
373 Necessary to regenerate @file{fixinc/fixincl.x} from
374 @file{fixinc/inclhack.def} and @file{fixinc/*.tpl}.
376 Necessary to run @samp{make check} for @file{fixinc}.
378 Necessary to regenerate the top level @file{Makefile.in} file from
379 @file{Makefile.tpl} and @file{Makefile.def}.
381 @item Flex version 2.5.4 (or later)
383 Necessary when modifying @file{*.l} files.
385 Necessary to build GCC during development because the generated output
386 files are not included in the SVN repository. They are included in
389 @item Texinfo version 4.4 (or later)
391 Necessary for running @command{makeinfo} when modifying @file{*.texi}
392 files to test your changes.
394 Necessary for running @command{make dvi} or @command{make pdf} to
395 create printable documentation in DVI or PDF format. Texinfo version
396 4.8 or later is required for @command{make pdf}.
398 Necessary to build GCC documentation during development because the
399 generated output files are not included in the SVN repository. They are
400 included in releases.
402 @item @TeX{} (any working version)
404 Necessary for running @command{texi2dvi} and @command{texi2pdf}, which
405 are used when running @command{make dvi} or @command{make pdf} to create
406 DVI or PDF files, respectively.
408 @item SVN (any version)
409 @itemx SSH (any version)
411 Necessary to access the SVN repository. Public releases and weekly
412 snapshots of the development sources are also available via FTP@.
414 @item Perl version 5.6.1 (or later)
416 Necessary when regenerating @file{Makefile} dependencies in libiberty.
417 Necessary when regenerating @file{libiberty/functions.texi}.
418 Necessary when generating manpages from Texinfo manuals.
419 Necessary when targetting Darwin, building libstdc++,
420 and not using @option{--disable-symvers}.
421 Used by various scripts to generate some files included in SVN (mainly
422 Unicode-related and rarely changing) from source tables.
424 @item GNU diffutils version 2.7 (or later)
426 Useful when submitting patches for the GCC source code.
428 @item patch version 2.5.4 (or later)
430 Necessary when applying patches, created with @command{diff}, to one's
436 If you wish to modify @file{.java} files in libjava, you will need to
437 configure with @option{--enable-java-maintainer-mode}, and you will need
438 to have executables named @command{ecj1} and @command{gjavah} in your path.
439 The @command{ecj1} executable should run the Eclipse Java compiler via
440 the GCC-specific entry point. You can download a suitable jar from
441 @uref{ftp://sourceware.org/pub/java/}, or by running the script
442 @command{contrib/download_ecj}.
451 @uref{./index.html,,Return to the GCC Installation page}
455 @c ***Downloading the source**************************************************
457 @comment node-name, next, previous, up
458 @node Downloading the source, Configuration, Prerequisites, Installing GCC
462 @chapter Downloading GCC
464 @cindex Downloading GCC
465 @cindex Downloading the Source
467 GCC is distributed via @uref{http://gcc.gnu.org/svn.html,,SVN} and FTP
468 tarballs compressed with @command{gzip} or
469 @command{bzip2}. It is possible to download a full distribution or specific
472 Please refer to the @uref{http://gcc.gnu.org/releases.html,,releases web page}
473 for information on how to obtain GCC@.
475 The full distribution includes the C, C++, Objective-C, Fortran, Java,
476 and Ada (in the case of GCC 3.1 and later) compilers. The full
477 distribution also includes runtime libraries for C++, Objective-C,
478 Fortran, and Java. In GCC 3.0 and later versions, the GNU compiler
479 testsuites are also included in the full distribution.
481 If you choose to download specific components, you must download the core
482 GCC distribution plus any language specific distributions you wish to
483 use. The core distribution includes the C language front end as well as the
484 shared components. Each language has a tarball which includes the language
485 front end as well as the language runtime (when appropriate).
487 Unpack the core distribution as well as any language specific
488 distributions in the same directory.
490 If you also intend to build binutils (either to upgrade an existing
491 installation or for use in place of the corresponding tools of your
492 OS), unpack the binutils distribution either in the same directory or
493 a separate one. In the latter case, add symbolic links to any
494 components of the binutils you intend to build alongside the compiler
495 (@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld},
496 @file{opcodes}, @dots{}) to the directory containing the GCC sources.
503 @uref{./index.html,,Return to the GCC Installation page}
507 @c ***Configuration***********************************************************
509 @comment node-name, next, previous, up
510 @node Configuration, Building, Downloading the source, Installing GCC
514 @chapter Installing GCC: Configuration
516 @cindex Configuration
517 @cindex Installing GCC: Configuration
519 Like most GNU software, GCC must be configured before it can be built.
520 This document describes the recommended configuration procedure
521 for both native and cross targets.
523 We use @var{srcdir} to refer to the toplevel source directory for
524 GCC; we use @var{objdir} to refer to the toplevel build/object directory.
526 If you obtained the sources via SVN, @var{srcdir} must refer to the top
527 @file{gcc} directory, the one where the @file{MAINTAINERS} can be found,
528 and not its @file{gcc} subdirectory, otherwise the build will fail.
530 If either @var{srcdir} or @var{objdir} is located on an automounted NFS
531 file system, the shell's built-in @command{pwd} command will return
532 temporary pathnames. Using these can lead to various sorts of build
533 problems. To avoid this issue, set the @env{PWDCMD} environment
534 variable to an automounter-aware @command{pwd} command, e.g.,
535 @command{pawd} or @samp{amq -w}, during the configuration and build
538 First, we @strong{highly} recommend that GCC be built into a
539 separate directory than the sources which does @strong{not} reside
540 within the source tree. This is how we generally build GCC; building
541 where @var{srcdir} == @var{objdir} should still work, but doesn't
542 get extensive testing; building where @var{objdir} is a subdirectory
543 of @var{srcdir} is unsupported.
545 If you have previously built GCC in the same directory for a
546 different target machine, do @samp{make distclean} to delete all files
547 that might be invalid. One of the files this deletes is @file{Makefile};
548 if @samp{make distclean} complains that @file{Makefile} does not exist
549 or issues a message like ``don't know how to make distclean'' it probably
550 means that the directory is already suitably clean. However, with the
551 recommended method of building in a separate @var{objdir}, you should
552 simply use a different @var{objdir} for each target.
554 Second, when configuring a native system, either @command{cc} or
555 @command{gcc} must be in your path or you must set @env{CC} in
556 your environment before running configure. Otherwise the configuration
560 Note that the bootstrap compiler and the resulting GCC must be link
561 compatible, else the bootstrap will fail with linker errors about
562 incompatible object file formats. Several multilibed targets are
563 affected by this requirement, see
565 @ref{Specific, host/target specific installation notes}.
568 @uref{specific.html,,host/target specific installation notes}.
577 % @var{srcdir}/configure [@var{options}] [@var{target}]
580 @heading Distributor options
582 If you will be distributing binary versions of GCC, with modifications
583 to the source code, you should use the options described in this
584 section to make clear that your version contains modifications.
587 @item --with-pkgversion=@var{version}
588 Specify a string that identifies your package. You may wish
589 to include a build number or build date. This version string will be
590 included in the output of @command{gcc --version}. This suffix does
591 not replace the default version string, only the @samp{GCC} part.
593 The default value is @samp{GCC}.
595 @item --with-bugurl=@var{url}
596 Specify the URL that users should visit if they wish to report a bug.
597 You are of course welcome to forward bugs reported to you to the FSF,
598 if you determine that they are not bugs in your modifications.
600 The default value refers to the FSF's GCC bug tracker.
604 @heading Target specification
607 GCC has code to correctly determine the correct value for @var{target}
608 for nearly all native systems. Therefore, we highly recommend you not
609 provide a configure target when configuring a native compiler.
612 @var{target} must be specified as @option{--target=@var{target}}
613 when configuring a cross compiler; examples of valid targets would be
614 m68k-coff, sh-elf, etc.
617 Specifying just @var{target} instead of @option{--target=@var{target}}
618 implies that the host defaults to @var{target}.
622 @heading Options specification
624 Use @var{options} to override several configure time options for
625 GCC@. A list of supported @var{options} follows; @samp{configure
626 --help} may list other options, but those not listed below may not
627 work and should not normally be used.
629 Note that each @option{--enable} option has a corresponding
630 @option{--disable} option and that each @option{--with} option has a
631 corresponding @option{--without} option.
634 @item --prefix=@var{dirname}
635 Specify the toplevel installation
636 directory. This is the recommended way to install the tools into a directory
637 other than the default. The toplevel installation directory defaults to
640 We @strong{highly} recommend against @var{dirname} being the same or a
641 subdirectory of @var{objdir} or vice versa. If specifying a directory
642 beneath a user's home directory tree, some shells will not expand
643 @var{dirname} correctly if it contains the @samp{~} metacharacter; use
646 The following standard @command{autoconf} options are supported. Normally you
647 should not need to use these options.
649 @item --exec-prefix=@var{dirname}
650 Specify the toplevel installation directory for architecture-dependent
651 files. The default is @file{@var{prefix}}.
653 @item --bindir=@var{dirname}
654 Specify the installation directory for the executables called by users
655 (such as @command{gcc} and @command{g++}). The default is
656 @file{@var{exec-prefix}/bin}.
658 @item --libdir=@var{dirname}
659 Specify the installation directory for object code libraries and
660 internal data files of GCC@. The default is @file{@var{exec-prefix}/lib}.
662 @item --libexecdir=@var{dirname}
663 Specify the installation directory for internal executables of GCC@.
664 The default is @file{@var{exec-prefix}/libexec}.
666 @item --with-slibdir=@var{dirname}
667 Specify the installation directory for the shared libgcc library. The
668 default is @file{@var{libdir}}.
670 @item --infodir=@var{dirname}
671 Specify the installation directory for documentation in info format.
672 The default is @file{@var{prefix}/info}.
674 @item --datadir=@var{dirname}
675 Specify the installation directory for some architecture-independent
676 data files referenced by GCC@. The default is @file{@var{prefix}/share}.
678 @item --mandir=@var{dirname}
679 Specify the installation directory for manual pages. The default is
680 @file{@var{prefix}/man}. (Note that the manual pages are only extracts from
681 the full GCC manuals, which are provided in Texinfo format. The manpages
682 are derived by an automatic conversion process from parts of the full
685 @item --with-gxx-include-dir=@var{dirname}
687 the installation directory for G++ header files. The default is
688 @file{@var{prefix}/include/c++/@var{version}}.
692 @item --program-prefix=@var{prefix}
693 GCC supports some transformations of the names of its programs when
694 installing them. This option prepends @var{prefix} to the names of
695 programs to install in @var{bindir} (see above). For example, specifying
696 @option{--program-prefix=foo-} would result in @samp{gcc}
697 being installed as @file{/usr/local/bin/foo-gcc}.
699 @item --program-suffix=@var{suffix}
700 Appends @var{suffix} to the names of programs to install in @var{bindir}
701 (see above). For example, specifying @option{--program-suffix=-3.1}
702 would result in @samp{gcc} being installed as
703 @file{/usr/local/bin/gcc-3.1}.
705 @item --program-transform-name=@var{pattern}
706 Applies the @samp{sed} script @var{pattern} to be applied to the names
707 of programs to install in @var{bindir} (see above). @var{pattern} has to
708 consist of one or more basic @samp{sed} editing commands, separated by
709 semicolons. For example, if you want the @samp{gcc} program name to be
710 transformed to the installed program @file{/usr/local/bin/myowngcc} and
711 the @samp{g++} program name to be transformed to
712 @file{/usr/local/bin/gspecial++} without changing other program names,
713 you could use the pattern
714 @option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'}
715 to achieve this effect.
717 All three options can be combined and used together, resulting in more
718 complex conversion patterns. As a basic rule, @var{prefix} (and
719 @var{suffix}) are prepended (appended) before further transformations
720 can happen with a special transformation script @var{pattern}.
722 As currently implemented, this option only takes effect for native
723 builds; cross compiler binaries' names are not transformed even when a
724 transformation is explicitly asked for by one of these options.
726 For native builds, some of the installed programs are also installed
727 with the target alias in front of their name, as in
728 @samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen
729 before the target alias is prepended to the name---so, specifying
730 @option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the
731 resulting binary would be installed as
732 @file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}.
734 As a last shortcoming, none of the installed Ada programs are
735 transformed yet, which will be fixed in some time.
737 @item --with-local-prefix=@var{dirname}
739 installation directory for local include files. The default is
740 @file{/usr/local}. Specify this option if you want the compiler to
741 search directory @file{@var{dirname}/include} for locally installed
742 header files @emph{instead} of @file{/usr/local/include}.
744 You should specify @option{--with-local-prefix} @strong{only} if your
745 site has a different convention (not @file{/usr/local}) for where to put
748 The default value for @option{--with-local-prefix} is @file{/usr/local}
749 regardless of the value of @option{--prefix}. Specifying
750 @option{--prefix} has no effect on which directory GCC searches for
751 local header files. This may seem counterintuitive, but actually it is
754 The purpose of @option{--prefix} is to specify where to @emph{install
755 GCC}. The local header files in @file{/usr/local/include}---if you put
756 any in that directory---are not part of GCC@. They are part of other
757 programs---perhaps many others. (GCC installs its own header files in
758 another directory which is based on the @option{--prefix} value.)
760 Both the local-prefix include directory and the GCC-prefix include
761 directory are part of GCC's ``system include'' directories. Although these
762 two directories are not fixed, they need to be searched in the proper
763 order for the correct processing of the include_next directive. The
764 local-prefix include directory is searched before the GCC-prefix
765 include directory. Another characteristic of system include directories
766 is that pedantic warnings are turned off for headers in these directories.
768 Some autoconf macros add @option{-I @var{directory}} options to the
769 compiler command line, to ensure that directories containing installed
770 packages' headers are searched. When @var{directory} is one of GCC's
771 system include directories, GCC will ignore the option so that system
772 directories continue to be processed in the correct order. This
773 may result in a search order different from what was specified but the
774 directory will still be searched.
776 GCC automatically searches for ordinary libraries using
777 @env{GCC_EXEC_PREFIX}. Thus, when the same installation prefix is
778 used for both GCC and packages, GCC will automatically search for
779 both headers and libraries. This provides a configuration that is
780 easy to use. GCC behaves in a manner similar to that when it is
781 installed as a system compiler in @file{/usr}.
783 Sites that need to install multiple versions of GCC may not want to
784 use the above simple configuration. It is possible to use the
785 @option{--program-prefix}, @option{--program-suffix} and
786 @option{--program-transform-name} options to install multiple versions
787 into a single directory, but it may be simpler to use different prefixes
788 and the @option{--with-local-prefix} option to specify the location of the
789 site-specific files for each version. It will then be necessary for
790 users to specify explicitly the location of local site libraries
791 (e.g., with @env{LIBRARY_PATH}).
793 The same value can be used for both @option{--with-local-prefix} and
794 @option{--prefix} provided it is not @file{/usr}. This can be used
795 to avoid the default search of @file{/usr/local/include}.
797 @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
798 The directory you use for @option{--with-local-prefix} @strong{must not}
799 contain any of the system's standard header files. If it did contain
800 them, certain programs would be miscompiled (including GNU Emacs, on
801 certain targets), because this would override and nullify the header
802 file corrections made by the @command{fixincludes} script.
804 Indications are that people who use this option use it based on mistaken
805 ideas of what it is for. People use it as if it specified where to
806 install part of GCC@. Perhaps they make this assumption because
807 installing GCC creates the directory.
809 @item --enable-shared[=@var{package}[,@dots{}]]
810 Build shared versions of libraries, if shared libraries are supported on
811 the target platform. Unlike GCC 2.95.x and earlier, shared libraries
812 are enabled by default on all platforms that support shared libraries.
814 If a list of packages is given as an argument, build shared libraries
815 only for the listed packages. For other packages, only static libraries
816 will be built. Package names currently recognized in the GCC tree are
817 @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not
818 @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc},
819 @samp{ada}, @samp{libada}, @samp{libjava} and @samp{libobjc}.
820 Note @samp{libiberty} does not support shared libraries at all.
822 Use @option{--disable-shared} to build only static libraries. Note that
823 @option{--disable-shared} does not accept a list of package names as
824 argument, only @option{--enable-shared} does.
826 @item @anchor{with-gnu-as}--with-gnu-as
827 Specify that the compiler should assume that the
828 assembler it finds is the GNU assembler. However, this does not modify
829 the rules to find an assembler and will result in confusion if the
830 assembler found is not actually the GNU assembler. (Confusion may also
831 result if the compiler finds the GNU assembler but has not been
832 configured with @option{--with-gnu-as}.) If you have more than one
833 assembler installed on your system, you may want to use this option in
834 connection with @option{--with-as=@var{pathname}} or
835 @option{--with-build-time-tools=@var{pathname}}.
837 The following systems are the only ones where it makes a difference
838 whether you use the GNU assembler. On any other system,
839 @option{--with-gnu-as} has no effect.
842 @item @samp{hppa1.0-@var{any}-@var{any}}
843 @item @samp{hppa1.1-@var{any}-@var{any}}
844 @item @samp{sparc-sun-solaris2.@var{any}}
845 @item @samp{sparc64-@var{any}-solaris2.@var{any}}
848 On the systems listed above (except for the HP-PA, the SPARC, for ISC on
849 the 386, if you use the GNU assembler, you should also use the GNU linker
850 (and specify @option{--with-gnu-ld}).
852 @item @anchor{with-as}--with-as=@var{pathname}
853 Specify that the compiler should use the assembler pointed to by
854 @var{pathname}, rather than the one found by the standard rules to find
855 an assembler, which are:
858 Unless GCC is being built with a cross compiler, check the
859 @file{@var{libexec}/gcc/@var{target}/@var{version}} directory.
860 @var{libexec} defaults to @file{@var{exec-prefix}/libexec};
861 @var{exec-prefix} defaults to @var{prefix}, which
862 defaults to @file{/usr/local} unless overridden by the
863 @option{--prefix=@var{pathname}} switch described above. @var{target}
864 is the target system triple, such as @samp{sparc-sun-solaris2.7}, and
865 @var{version} denotes the GCC version, such as 3.0.
868 If the target system is the same that you are building on, check
869 operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
873 Check in the @env{PATH} for a tool whose name is prefixed by the
874 target system triple.
877 Check in the @env{PATH} for a tool whose name is not prefixed by the
878 target system triple, if the host and target system triple are
879 the same (in other words, we use a host tool if it can be used for
883 You may want to use @option{--with-as} if no assembler
884 is installed in the directories listed above, or if you have multiple
885 assemblers installed and want to choose one that is not found by the
888 @item @anchor{with-gnu-ld}--with-gnu-ld
889 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
892 @item --with-ld=@var{pathname}
893 Same as @uref{#with-as,,@option{--with-as}}
897 Specify that stabs debugging
898 information should be used instead of whatever format the host normally
899 uses. Normally GCC uses the same debug format as the host system.
901 On MIPS based systems and on Alphas, you must specify whether you want
902 GCC to create the normal ECOFF debugging format, or to use BSD-style
903 stabs passed through the ECOFF symbol table. The normal ECOFF debug
904 format cannot fully handle languages other than C@. BSD stabs format can
905 handle other languages, but it only works with the GNU debugger GDB@.
907 Normally, GCC uses the ECOFF debugging format by default; if you
908 prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@.
910 No matter which default you choose when you configure GCC, the user
911 can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
912 the debug format for a particular compilation.
914 @option{--with-stabs} is meaningful on the ISC system on the 386, also, if
915 @option{--with-gas} is used. It selects use of stabs debugging
916 information embedded in COFF output. This kind of debugging information
917 supports C++ well; ordinary COFF debugging information does not.
919 @option{--with-stabs} is also meaningful on 386 systems running SVR4. It
920 selects use of stabs debugging information embedded in ELF output. The
921 C++ compiler currently (2.6.0) does not support the DWARF debugging
922 information normally used on 386 SVR4 platforms; stabs provide a
923 workable alternative. This requires gas and gdb, as the normal SVR4
924 tools can not generate or interpret stabs.
926 @item --disable-multilib
927 Specify that multiple target
928 libraries to support different target variants, calling
929 conventions, etc.@: should not be built. The default is to build a
930 predefined set of them.
932 Some targets provide finer-grained control over which multilibs are built
933 (e.g., @option{--disable-softfloat}):
939 fpu, 26bit, underscore, interwork, biendian, nofmult.
942 softfloat, m68881, m68000, m68020.
945 single-float, biendian, softfloat.
947 @item powerpc*-*-*, rs6000*-*-*
948 aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
953 @item --enable-threads
954 Specify that the target
955 supports threads. This affects the Objective-C compiler and runtime
956 library, and exception handling for other languages like C++ and Java.
957 On some systems, this is the default.
959 In general, the best (and, in many cases, the only known) threading
960 model available will be configured for use. Beware that on some
961 systems, GCC has not been taught what threading models are generally
962 available for the system. In this case, @option{--enable-threads} is an
963 alias for @option{--enable-threads=single}.
965 @item --disable-threads
966 Specify that threading support should be disabled for the system.
967 This is an alias for @option{--enable-threads=single}.
969 @item --enable-threads=@var{lib}
971 @var{lib} is the thread support library. This affects the Objective-C
972 compiler and runtime library, and exception handling for other languages
973 like C++ and Java. The possibilities for @var{lib} are:
981 Ada tasking support. For non-Ada programs, this setting is equivalent
982 to @samp{single}. When used in conjunction with the Ada run time, it
983 causes GCC to use the same thread primitives as Ada uses. This option
984 is necessary when using both Ada and the back end exception handling,
985 which is the default for most Ada targets.
987 Generic MACH thread support, known to work on NeXTSTEP@. (Please note
988 that the file needed to support this configuration, @file{gthr-mach.h}, is
989 missing and thus this setting will cause a known bootstrap failure.)
991 This is an alias for @samp{single}.
993 Generic POSIX/Unix98 thread support.
995 Generic POSIX/Unix95 thread support.
997 RTEMS thread support.
999 Disable thread support, should work for all platforms.
1001 Sun Solaris 2 thread support.
1003 VxWorks thread support.
1005 Microsoft Win32 API thread support.
1007 Novell Kernel Services thread support.
1011 Specify that the target supports TLS (Thread Local Storage). Usually
1012 configure can correctly determine if TLS is supported. In cases where
1013 it guesses incorrectly, TLS can be explicitly enabled or disabled with
1014 @option{--enable-tls} or @option{--disable-tls}. This can happen if
1015 the assembler supports TLS but the C library does not, or if the
1016 assumptions made by the configure test are incorrect.
1019 Specify that the target does not support TLS.
1020 This is an alias for @option{--enable-tls=no}.
1022 @item --with-cpu=@var{cpu}
1023 @itemx --with-cpu-32=@var{cpu}
1024 @itemx --with-cpu-64=@var{cpu}
1025 Specify which cpu variant the compiler should generate code for by default.
1026 @var{cpu} will be used as the default value of the @option{-mcpu=} switch.
1027 This option is only supported on some targets, including ARM, i386, M68k,
1028 PowerPC, and SPARC@. The @option{--with-cpu-32} and
1029 @option{--with-cpu-64} options specify separate default CPUs for
1030 32-bit and 64-bit modes; these options are only supported for i386 and
1033 @item --with-schedule=@var{cpu}
1034 @itemx --with-arch=@var{cpu}
1035 @itemx --with-arch-32=@var{cpu}
1036 @itemx --with-arch-64=@var{cpu}
1037 @itemx --with-tune=@var{cpu}
1038 @itemx --with-tune-32=@var{cpu}
1039 @itemx --with-tune-64=@var{cpu}
1040 @itemx --with-abi=@var{abi}
1041 @itemx --with-fpu=@var{type}
1042 @itemx --with-float=@var{type}
1043 These configure options provide default values for the @option{-mschedule=},
1044 @option{-march=}, @option{-mtune=}, @option{-mabi=}, and @option{-mfpu=}
1045 options and for @option{-mhard-float} or @option{-msoft-float}. As with
1046 @option{--with-cpu}, which switches will be accepted and acceptable values
1047 of the arguments depend on the target.
1049 @item --with-mode=@var{mode}
1050 Specify if the compiler should default to @option{-marm} or @option{-mthumb}.
1051 This option is only supported on ARM targets.
1053 @item --with-divide=@var{type}
1054 Specify how the compiler should generate code for checking for
1055 division by zero. This option is only supported on the MIPS target.
1056 The possibilities for @var{type} are:
1059 Division by zero checks use conditional traps (this is the default on
1060 systems that support conditional traps).
1062 Division by zero checks use the break instruction.
1065 @c If you make --with-llsc the default for additional targets,
1066 @c update the --with-llsc description in the MIPS section below.
1069 On MIPS targets, make @option{-mllsc} the default when no
1070 @option{-mno-lsc} option is passed. This is the default for
1071 Linux-based targets, as the kernel will emulate them if the ISA does
1074 @item --without-llsc
1075 On MIPS targets, make @option{-mno-llsc} the default when no
1076 @option{-mllsc} option is passed.
1078 @item --enable-__cxa_atexit
1079 Define if you want to use __cxa_atexit, rather than atexit, to
1080 register C++ destructors for local statics and global objects.
1081 This is essential for fully standards-compliant handling of
1082 destructors, but requires __cxa_atexit in libc. This option is currently
1083 only available on systems with GNU libc. When enabled, this will cause
1084 @option{-fuse-cxa-atexit} to be passed by default.
1086 @item --enable-target-optspace
1088 libraries should be optimized for code space instead of code speed.
1089 This is the default for the m32r platform.
1092 Specify that a user visible @command{cpp} program should not be installed.
1094 @item --with-cpp-install-dir=@var{dirname}
1095 Specify that the user visible @command{cpp} program should be installed
1096 in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
1098 @item --enable-initfini-array
1099 Force the use of sections @code{.init_array} and @code{.fini_array}
1100 (instead of @code{.init} and @code{.fini}) for constructors and
1101 destructors. Option @option{--disable-initfini-array} has the
1102 opposite effect. If neither option is specified, the configure script
1103 will try to guess whether the @code{.init_array} and
1104 @code{.fini_array} sections are supported and, if they are, use them.
1106 @item --enable-maintainer-mode
1107 The build rules that
1108 regenerate the GCC master message catalog @file{gcc.pot} are normally
1109 disabled. This is because it can only be rebuilt if the complete source
1110 tree is present. If you have changed the sources and want to rebuild the
1111 catalog, configuring with @option{--enable-maintainer-mode} will enable
1112 this. Note that you need a recent version of the @code{gettext} tools
1115 @item --disable-bootstrap
1116 For a native build, the default configuration is to perform
1117 a 3-stage bootstrap of the compiler when @samp{make} is invoked,
1118 testing that GCC can compile itself correctly. If you want to disable
1119 this process, you can configure with @option{--disable-bootstrap}.
1121 @item --enable-bootstrap
1122 In special cases, you may want to perform a 3-stage build
1123 even if the target and host triplets are different.
1124 This could happen when the host can run code compiled for
1125 the target (e.g.@: host is i686-linux, target is i486-linux).
1126 Starting from GCC 4.2, to do this you have to configure explicitly
1127 with @option{--enable-bootstrap}.
1129 @item --enable-generated-files-in-srcdir
1130 Neither the .c and .h files that are generated from Bison and flex nor the
1131 info manuals and man pages that are built from the .texi files are present
1132 in the SVN development tree. When building GCC from that development tree,
1133 or from one of our snapshots, those generated files are placed in your
1134 build directory, which allows for the source to be in a readonly
1137 If you configure with @option{--enable-generated-files-in-srcdir} then those
1138 generated files will go into the source directory. This is mainly intended
1139 for generating release or prerelease tarballs of the GCC sources, since it
1140 is not a requirement that the users of source releases to have flex, Bison,
1143 @item --enable-version-specific-runtime-libs
1145 that runtime libraries should be installed in the compiler specific
1146 subdirectory (@file{@var{libdir}/gcc}) rather than the usual places. In
1147 addition, @samp{libstdc++}'s include files will be installed into
1148 @file{@var{libdir}} unless you overruled it by using
1149 @option{--with-gxx-include-dir=@var{dirname}}. Using this option is
1150 particularly useful if you intend to use several versions of GCC in
1151 parallel. This is currently supported by @samp{libgfortran},
1152 @samp{libjava}, @samp{libmudflap}, @samp{libstdc++}, and @samp{libobjc}.
1154 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
1155 Specify that only a particular subset of compilers and
1156 their runtime libraries should be built. For a list of valid values for
1157 @var{langN} you can issue the following command in the
1158 @file{gcc} directory of your GCC source tree:@*
1160 grep language= */config-lang.in
1162 Currently, you can use any of the following:
1163 @code{all}, @code{ada}, @code{c}, @code{c++}, @code{fortran}, @code{java},
1164 @code{objc}, @code{obj-c++}.
1165 Building the Ada compiler has special requirements, see below.
1166 If you do not pass this flag, or specify the option @code{all}, then all
1167 default languages available in the @file{gcc} sub-tree will be configured.
1168 Ada and Objective-C++ are not default languages; the rest are.
1169 Re-defining @code{LANGUAGES} when calling @samp{make} @strong{does not}
1170 work anymore, as those language sub-directories might not have been
1173 @item --enable-stage1-languages=@var{lang1},@var{lang2},@dots{}
1174 Specify that a particular subset of compilers and their runtime
1175 libraries should be built with the system C compiler during stage 1 of
1176 the bootstrap process, rather than only in later stages with the
1177 bootstrapped C compiler. The list of valid values is the same as for
1178 @option{--enable-languages}, and the option @code{all} will select all
1179 of the languages enabled by @option{--enable-languages}. This option is
1180 primarily useful for GCC development; for instance, when a development
1181 version of the compiler cannot bootstrap due to compiler bugs, or when
1182 one is debugging front ends other than the C front end. When this
1183 option is used, one can then build the target libraries for the
1184 specified languages with the stage-1 compiler by using @command{make
1185 stage1-bubble all-target}, or run the testsuite on the stage-1 compiler
1186 for the specified languages using @command{make stage1-start check-gcc}.
1188 @item --disable-libada
1189 Specify that the run-time libraries and tools used by GNAT should not
1190 be built. This can be useful for debugging, or for compatibility with
1191 previous Ada build procedures, when it was required to explicitly
1192 do a @samp{make -C gcc gnatlib_and_tools}.
1194 @item --disable-libssp
1195 Specify that the run-time libraries for stack smashing protection
1196 should not be built.
1198 @item --disable-libgomp
1199 Specify that the run-time libraries used by GOMP should not be built.
1202 Specify that the compiler should
1203 use DWARF 2 debugging information as the default.
1205 @item --enable-targets=all
1206 @itemx --enable-targets=@var{target_list}
1207 Some GCC targets, e.g.@: powerpc64-linux, build bi-arch compilers.
1208 These are compilers that are able to generate either 64-bit or 32-bit
1209 code. Typically, the corresponding 32-bit target, e.g.@:
1210 powerpc-linux for powerpc64-linux, only generates 32-bit code. This
1211 option enables the 32-bit target to be a bi-arch compiler, which is
1212 useful when you want a bi-arch compiler that defaults to 32-bit, and
1213 you are building a bi-arch or multi-arch binutils in a combined tree.
1214 Currently, this option only affects sparc-linux, powerpc-linux and
1217 @item --enable-secureplt
1218 This option enables @option{-msecure-plt} by default for powerpc-linux.
1220 @xref{RS/6000 and PowerPC Options,, RS/6000 and PowerPC Options, gcc,
1221 Using the GNU Compiler Collection (GCC)},
1224 See ``RS/6000 and PowerPC Options'' in the main manual
1228 This option enables @option{-mcld} by default for 32-bit x86 targets.
1230 @xref{i386 and x86-64 Options,, i386 and x86-64 Options, gcc,
1231 Using the GNU Compiler Collection (GCC)},
1234 See ``i386 and x86-64 Options'' in the main manual
1237 @item --enable-win32-registry
1238 @itemx --enable-win32-registry=@var{key}
1239 @itemx --disable-win32-registry
1240 The @option{--enable-win32-registry} option enables Microsoft Windows-hosted GCC
1241 to look up installations paths in the registry using the following key:
1244 @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
1247 @var{key} defaults to GCC version number, and can be overridden by the
1248 @option{--enable-win32-registry=@var{key}} option. Vendors and distributors
1249 who use custom installers are encouraged to provide a different key,
1250 perhaps one comprised of vendor name and GCC version number, to
1251 avoid conflict with existing installations. This feature is enabled
1252 by default, and can be disabled by @option{--disable-win32-registry}
1253 option. This option has no effect on the other hosts.
1256 Specify that the machine does not have a floating point unit. This
1257 option only applies to @samp{m68k-sun-sunos@var{n}}. On any other
1258 system, @option{--nfp} has no effect.
1260 @item --enable-werror
1261 @itemx --disable-werror
1262 @itemx --enable-werror=yes
1263 @itemx --enable-werror=no
1264 When you specify this option, it controls whether certain files in the
1265 compiler are built with @option{-Werror} in bootstrap stage2 and later.
1266 If you don't specify it, @option{-Werror} is turned on for the main
1267 development trunk. However it defaults to off for release branches and
1268 final releases. The specific files which get @option{-Werror} are
1269 controlled by the Makefiles.
1271 @item --enable-checking
1272 @itemx --enable-checking=@var{list}
1273 When you specify this option, the compiler is built to perform internal
1274 consistency checks of the requested complexity. This does not change the
1275 generated code, but adds error checking within the compiler. This will
1276 slow down the compiler and may only work properly if you are building
1277 the compiler with GCC@. This is @samp{yes} by default when building
1278 from SVN or snapshots, but @samp{release} for releases. More control
1279 over the checks may be had by specifying @var{list}. The categories of
1280 checks available are @samp{yes} (most common checks
1281 @samp{assert,misc,tree,gc,rtlflag,runtime}), @samp{no} (no checks at
1282 all), @samp{all} (all but @samp{valgrind}), @samp{release} (cheapest
1283 checks @samp{assert,runtime}) or @samp{none} (same as @samp{no}).
1284 Individual checks can be enabled with these flags @samp{assert},
1285 @samp{df}, @samp{fold}, @samp{gc}, @samp{gcac} @samp{misc}, @samp{rtl},
1286 @samp{rtlflag}, @samp{runtime}, @samp{tree}, and @samp{valgrind}.
1288 The @samp{valgrind} check requires the external @command{valgrind}
1289 simulator, available from @uref{http://valgrind.org/}. The
1290 @samp{df}, @samp{rtl}, @samp{gcac} and @samp{valgrind} checks are very expensive.
1291 To disable all checking, @samp{--disable-checking} or
1292 @samp{--enable-checking=none} must be explicitly requested. Disabling
1293 assertions will make the compiler and runtime slightly faster but
1294 increase the risk of undetected internal errors causing wrong code to be
1297 @item --enable-coverage
1298 @itemx --enable-coverage=@var{level}
1299 With this option, the compiler is built to collect self coverage
1300 information, every time it is run. This is for internal development
1301 purposes, and only works when the compiler is being built with gcc. The
1302 @var{level} argument controls whether the compiler is built optimized or
1303 not, values are @samp{opt} and @samp{noopt}. For coverage analysis you
1304 want to disable optimization, for performance analysis you want to
1305 enable optimization. When coverage is enabled, the default level is
1306 without optimization.
1308 @item --enable-gather-detailed-mem-stats
1309 When this option is specified more detailed information on memory
1310 allocation is gathered. This information is printed when using
1311 @option{-fmem-report}.
1314 @itemx --with-gc=@var{choice}
1315 With this option you can specify the garbage collector implementation
1316 used during the compilation process. @var{choice} can be one of
1317 @samp{page} and @samp{zone}, where @samp{page} is the default.
1320 @itemx --disable-nls
1321 The @option{--enable-nls} option enables Native Language Support (NLS),
1322 which lets GCC output diagnostics in languages other than American
1323 English. Native Language Support is enabled by default if not doing a
1324 canadian cross build. The @option{--disable-nls} option disables NLS@.
1326 @item --with-included-gettext
1327 If NLS is enabled, the @option{--with-included-gettext} option causes the build
1328 procedure to prefer its copy of GNU @command{gettext}.
1330 @item --with-catgets
1331 If NLS is enabled, and if the host lacks @code{gettext} but has the
1332 inferior @code{catgets} interface, the GCC build procedure normally
1333 ignores @code{catgets} and instead uses GCC's copy of the GNU
1334 @code{gettext} library. The @option{--with-catgets} option causes the
1335 build procedure to use the host's @code{catgets} in this situation.
1337 @item --with-libiconv-prefix=@var{dir}
1338 Search for libiconv header files in @file{@var{dir}/include} and
1339 libiconv library files in @file{@var{dir}/lib}.
1341 @item --enable-obsolete
1342 Enable configuration for an obsoleted system. If you attempt to
1343 configure GCC for a system (build, host, or target) which has been
1344 obsoleted, and you do not specify this flag, configure will halt with an
1347 All support for systems which have been obsoleted in one release of GCC
1348 is removed entirely in the next major release, unless someone steps
1349 forward to maintain the port.
1351 @item --enable-decimal-float
1352 @itemx --enable-decimal-float=yes
1353 @itemx --enable-decimal-float=no
1354 @itemx --enable-decimal-float=bid
1355 @itemx --enable-decimal-float=dpd
1356 @itemx --disable-decimal-float
1357 Enable (or disable) support for the C decimal floating point extension
1358 that is in the IEEE 754-2008 standard. This is enabled by default only
1359 on PowerPC, i386, and x86_64 GNU/Linux systems. Other systems may also
1360 support it, but require the user to specifically enable it. You can
1361 optionally control which decimal floating point format is used (either
1362 @samp{bid} or @samp{dpd}). The @samp{bid} (binary integer decimal)
1363 format is default on i386 and x86_64 systems, and the @samp{dpd}
1364 (densely packed decimal) format is default on PowerPC systems.
1366 @item --enable-fixed-point
1367 @itemx --disable-fixed-point
1368 Enable (or disable) support for C fixed-point arithmetic.
1369 This option is enabled by default for some targets (such as MIPS) which
1370 have hardware-support for fixed-point operations. On other targets, you
1371 may enable this option manually.
1373 @item --with-long-double-128
1374 Specify if @code{long double} type should be 128-bit by default on selected
1375 GNU/Linux architectures. If using @code{--without-long-double-128},
1376 @code{long double} will be by default 64-bit, the same as @code{double} type.
1377 When neither of these configure options are used, the default will be
1378 128-bit @code{long double} when built against GNU C Library 2.4 and later,
1379 64-bit @code{long double} otherwise.
1381 @item --with-gmp=@var{pathname}
1382 @itemx --with-gmp-include=@var{pathname}
1383 @itemx --with-gmp-lib=@var{pathname}
1384 @itemx --with-mpfr=@var{pathname}
1385 @itemx --with-mpfr-include=@var{pathname}
1386 @itemx --with-mpfr-lib=@var{pathname}
1387 If you do not have GMP (the GNU Multiple Precision library) and the
1388 MPFR Libraries installed in a standard location and you want to build
1389 GCC, you can explicitly specify the directory where they are installed
1390 (@samp{--with-gmp=@var{gmpinstalldir}},
1391 @samp{--with-mpfr=@var{mpfrinstalldir}}). The
1392 @option{--with-gmp=@var{gmpinstalldir}} option is shorthand for
1393 @option{--with-gmp-lib=@var{gmpinstalldir}/lib} and
1394 @option{--with-gmp-include=@var{gmpinstalldir}/include}. Likewise the
1395 @option{--with-mpfr=@var{mpfrinstalldir}} option is shorthand for
1396 @option{--with-mpfr-lib=@var{mpfrinstalldir}/lib} and
1397 @option{--with-mpfr-include=@var{mpfrinstalldir}/include}. If these
1398 shorthand assumptions are not correct, you can use the explicit
1399 include and lib options directly.
1401 @item --with-debug-prefix-map=@var{map}
1402 Convert source directory names using @option{-fdebug-prefix-map} when
1403 building runtime libraries. @samp{@var{map}} is a space-separated
1404 list of maps of the form @samp{@var{old}=@var{new}}.
1408 @subheading Cross-Compiler-Specific Options
1409 The following options only apply to building cross compilers.
1411 @item --with-sysroot
1412 @itemx --with-sysroot=@var{dir}
1413 Tells GCC to consider @var{dir} as the root of a tree that contains a
1414 (subset of) the root filesystem of the target operating system.
1415 Target system headers, libraries and run-time object files will be
1416 searched in there. The specified directory is not copied into the
1417 install tree, unlike the options @option{--with-headers} and
1418 @option{--with-libs} that this option obsoletes. The default value,
1419 in case @option{--with-sysroot} is not given an argument, is
1420 @option{$@{gcc_tooldir@}/sys-root}. If the specified directory is a
1421 subdirectory of @option{$@{exec_prefix@}}, then it will be found relative to
1422 the GCC binaries if the installation tree is moved.
1424 @item --with-build-sysroot
1425 @itemx --with-build-sysroot=@var{dir}
1426 Tells GCC to consider @var{dir} as the system root (see
1427 @option{--with-sysroot}) while building target libraries, instead of
1428 the directory specified with @option{--with-sysroot}. This option is
1429 only useful when you are already using @option{--with-sysroot}. You
1430 can use @option{--with-build-sysroot} when you are configuring with
1431 @option{--prefix} set to a directory that is different from the one in
1432 which you are installing GCC and your target libraries.
1434 This option affects the system root for the compiler used to build
1435 target libraries (which runs on the build system); it does not affect
1436 the compiler which is used to build GCC itself.
1438 @item --with-headers
1439 @itemx --with-headers=@var{dir}
1440 Deprecated in favor of @option{--with-sysroot}.
1441 Specifies that target headers are available when building a cross compiler.
1442 The @var{dir} argument specifies a directory which has the target include
1443 files. These include files will be copied into the @file{gcc} install
1444 directory. @emph{This option with the @var{dir} argument is required} when
1445 building a cross compiler, if @file{@var{prefix}/@var{target}/sys-include}
1446 doesn't pre-exist. If @file{@var{prefix}/@var{target}/sys-include} does
1447 pre-exist, the @var{dir} argument may be omitted. @command{fixincludes}
1448 will be run on these files to make them compatible with GCC@.
1450 @item --without-headers
1451 Tells GCC not use any target headers from a libc when building a cross
1452 compiler. When crossing to GNU/Linux, you need the headers so GCC
1453 can build the exception handling for libgcc.
1456 @itemx --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}''
1457 Deprecated in favor of @option{--with-sysroot}.
1458 Specifies a list of directories which contain the target runtime
1459 libraries. These libraries will be copied into the @file{gcc} install
1460 directory. If the directory list is omitted, this option has no
1464 Specifies that @samp{newlib} is
1465 being used as the target C library. This causes @code{__eprintf} to be
1466 omitted from @file{libgcc.a} on the assumption that it will be provided by
1469 @item --with-build-time-tools=@var{dir}
1470 Specifies where to find the set of target tools (assembler, linker, etc.)
1471 that will be used while building GCC itself. This option can be useful
1472 if the directory layouts are different between the system you are building
1473 GCC on, and the system where you will deploy it.
1475 For example, on a @option{ia64-hp-hpux} system, you may have the GNU
1476 assembler and linker in @file{/usr/bin}, and the native tools in a
1477 different path, and build a toolchain that expects to find the
1478 native tools in @file{/usr/bin}.
1480 When you use this option, you should ensure that @var{dir} includes
1481 @command{ar}, @command{as}, @command{ld}, @command{nm},
1482 @command{ranlib} and @command{strip} if necessary, and possibly
1483 @command{objdump}. Otherwise, GCC may use an inconsistent set of
1487 @subheading Java-Specific Options
1489 The following option applies to the build of the Java front end.
1492 @item --disable-libgcj
1493 Specify that the run-time libraries
1494 used by GCJ should not be built. This is useful in case you intend
1495 to use GCJ with some other run-time, or you're going to install it
1496 separately, or it just happens not to build on your particular
1497 machine. In general, if the Java front end is enabled, the GCJ
1498 libraries will be enabled too, unless they're known to not work on
1499 the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
1500 may need to port it; in this case, before modifying the top-level
1501 @file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
1502 you may use @option{--enable-libgcj} to override the default.
1506 The following options apply to building @samp{libgcj}.
1508 @subsubheading General Options
1511 @item --enable-java-maintainer-mode
1512 By default the @samp{libjava} build will not attempt to compile the
1513 @file{.java} source files to @file{.class}. Instead, it will use the
1514 @file{.class} files from the source tree. If you use this option you
1515 must have executables named @command{ecj1} and @command{gjavah} in your path
1516 for use by the build. You must use this option if you intend to
1517 modify any @file{.java} files in @file{libjava}.
1519 @item --with-java-home=@var{dirname}
1520 This @samp{libjava} option overrides the default value of the
1521 @samp{java.home} system property. It is also used to set
1522 @samp{sun.boot.class.path} to @file{@var{dirname}/lib/rt.jar}. By
1523 default @samp{java.home} is set to @file{@var{prefix}} and
1524 @samp{sun.boot.class.path} to
1525 @file{@var{datadir}/java/libgcj-@var{version}.jar}.
1527 @item --with-ecj-jar=@var{filename}
1528 This option can be used to specify the location of an external jar
1529 file containing the Eclipse Java compiler. A specially modified
1530 version of this compiler is used by @command{gcj} to parse
1531 @file{.java} source files. If this option is given, the
1532 @samp{libjava} build will create and install an @file{ecj1} executable
1533 which uses this jar file at runtime.
1535 If this option is not given, but an @file{ecj.jar} file is found in
1536 the topmost source tree at configure time, then the @samp{libgcj}
1537 build will create and install @file{ecj1}, and will also install the
1538 discovered @file{ecj.jar} into a suitable place in the install tree.
1540 If @file{ecj1} is not installed, then the user will have to supply one
1541 on his path in order for @command{gcj} to properly parse @file{.java}
1542 source files. A suitable jar is available from
1543 @uref{ftp://sourceware.org/pub/java/}.
1545 @item --disable-getenv-properties
1546 Don't set system properties from @env{GCJ_PROPERTIES}.
1548 @item --enable-hash-synchronization
1549 Use a global hash table for monitor locks. Ordinarily,
1550 @samp{libgcj}'s @samp{configure} script automatically makes
1551 the correct choice for this option for your platform. Only use
1552 this if you know you need the library to be configured differently.
1554 @item --enable-interpreter
1555 Enable the Java interpreter. The interpreter is automatically
1556 enabled by default on all platforms that support it. This option
1557 is really only useful if you want to disable the interpreter
1558 (using @option{--disable-interpreter}).
1560 @item --disable-java-net
1561 Disable java.net. This disables the native part of java.net only,
1562 using non-functional stubs for native method implementations.
1564 @item --disable-jvmpi
1565 Disable JVMPI support.
1567 @item --disable-libgcj-bc
1568 Disable BC ABI compilation of certain parts of libgcj. By default,
1569 some portions of libgcj are compiled with @option{-findirect-dispatch}
1570 and @option{-fno-indirect-classes}, allowing them to be overridden at
1573 If @option{--disable-libgcj-bc} is specified, libgcj is built without
1574 these options. This allows the compile-time linker to resolve
1575 dependencies when statically linking to libgcj. However it makes it
1576 impossible to override the affected portions of libgcj at run-time.
1579 Enable runtime eCos target support.
1581 @item --without-libffi
1582 Don't use @samp{libffi}. This will disable the interpreter and JNI
1583 support as well, as these require @samp{libffi} to work.
1585 @item --enable-libgcj-debug
1586 Enable runtime debugging code.
1588 @item --enable-libgcj-multifile
1589 If specified, causes all @file{.java} source files to be
1590 compiled into @file{.class} files in one invocation of
1591 @samp{gcj}. This can speed up build time, but is more
1592 resource-intensive. If this option is unspecified or
1593 disabled, @samp{gcj} is invoked once for each @file{.java}
1594 file to compile into a @file{.class} file.
1596 @item --with-libiconv-prefix=DIR
1597 Search for libiconv in @file{DIR/include} and @file{DIR/lib}.
1599 @item --enable-sjlj-exceptions
1600 Force use of the @code{setjmp}/@code{longjmp}-based scheme for exceptions.
1601 @samp{configure} ordinarily picks the correct value based on the platform.
1602 Only use this option if you are sure you need a different setting.
1604 @item --with-system-zlib
1605 Use installed @samp{zlib} rather than that included with GCC@.
1607 @item --with-win32-nlsapi=ansi, unicows or unicode
1608 Indicates how MinGW @samp{libgcj} translates between UNICODE
1609 characters and the Win32 API@.
1612 Use the single-byte @code{char} and the Win32 A functions natively,
1613 translating to and from UNICODE when using these functions. If
1614 unspecified, this is the default.
1617 Use the @code{WCHAR} and Win32 W functions natively. Adds
1618 @code{-lunicows} to @file{libgcj.spec} to link with @samp{libunicows}.
1619 @file{unicows.dll} needs to be deployed on Microsoft Windows 9X machines
1620 running built executables. @file{libunicows.a}, an open-source
1621 import library around Microsoft's @code{unicows.dll}, is obtained from
1622 @uref{http://libunicows.sourceforge.net/}, which also gives details
1623 on getting @file{unicows.dll} from Microsoft.
1626 Use the @code{WCHAR} and Win32 W functions natively. Does @emph{not}
1627 add @code{-lunicows} to @file{libgcj.spec}. The built executables will
1628 only run on Microsoft Windows NT and above.
1632 @subsubheading AWT-Specific Options
1636 Use the X Window System.
1638 @item --enable-java-awt=PEER(S)
1639 Specifies the AWT peer library or libraries to build alongside
1640 @samp{libgcj}. If this option is unspecified or disabled, AWT
1641 will be non-functional. Current valid values are @option{gtk} and
1642 @option{xlib}. Multiple libraries should be separated by a
1643 comma (i.e.@: @option{--enable-java-awt=gtk,xlib}).
1645 @item --enable-gtk-cairo
1646 Build the cairo Graphics2D implementation on GTK@.
1648 @item --enable-java-gc=TYPE
1649 Choose garbage collector. Defaults to @option{boehm} if unspecified.
1651 @item --disable-gtktest
1652 Do not try to compile and run a test GTK+ program.
1654 @item --disable-glibtest
1655 Do not try to compile and run a test GLIB program.
1657 @item --with-libart-prefix=PFX
1658 Prefix where libart is installed (optional).
1660 @item --with-libart-exec-prefix=PFX
1661 Exec prefix where libart is installed (optional).
1663 @item --disable-libarttest
1664 Do not try to compile and run a test libart program.
1673 @uref{./index.html,,Return to the GCC Installation page}
1677 @c ***Building****************************************************************
1679 @comment node-name, next, previous, up
1680 @node Building, Testing, Configuration, Installing GCC
1686 @cindex Installing GCC: Building
1688 Now that GCC is configured, you are ready to build the compiler and
1691 Some commands executed when making the compiler may fail (return a
1692 nonzero status) and be ignored by @command{make}. These failures, which
1693 are often due to files that were not found, are expected, and can safely
1696 It is normal to have compiler warnings when compiling certain files.
1697 Unless you are a GCC developer, you can generally ignore these warnings
1698 unless they cause compilation to fail. Developers should attempt to fix
1699 any warnings encountered, however they can temporarily continue past
1700 warnings-as-errors by specifying the configure flag
1701 @option{--disable-werror}.
1703 On certain old systems, defining certain environment variables such as
1704 @env{CC} can interfere with the functioning of @command{make}.
1706 If you encounter seemingly strange errors when trying to build the
1707 compiler in a directory other than the source directory, it could be
1708 because you have previously configured the compiler in the source
1709 directory. Make sure you have done all the necessary preparations.
1711 If you build GCC on a BSD system using a directory stored in an old System
1712 V file system, problems may occur in running @command{fixincludes} if the
1713 System V file system doesn't support symbolic links. These problems
1714 result in a failure to fix the declaration of @code{size_t} in
1715 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
1716 that type mismatches occur, this could be the cause.
1718 The solution is not to use such a directory for building GCC@.
1720 Similarly, when building from SVN or snapshots, or if you modify
1721 @file{*.l} files, you need the Flex lexical analyzer generator
1722 installed. If you do not modify @file{*.l} files, releases contain
1723 the Flex-generated files and you do not need Flex installed to build
1724 them. There is still one Flex-based lexical analyzer (part of the
1725 build machinery, not of GCC itself) that is used even if you only
1726 build the C front end.
1728 When building from SVN or snapshots, or if you modify Texinfo
1729 documentation, you need version 4.4 or later of Texinfo installed if you
1730 want Info documentation to be regenerated. Releases contain Info
1731 documentation pre-built for the unmodified documentation in the release.
1733 @section Building a native compiler
1735 For a native build, the default configuration is to perform
1736 a 3-stage bootstrap of the compiler when @samp{make} is invoked.
1737 This will build the entire GCC system and ensure that it compiles
1738 itself correctly. It can be disabled with the @option{--disable-bootstrap}
1739 parameter to @samp{configure}, but bootstrapping is suggested because
1740 the compiler will be tested more completely and could also have
1743 The bootstrapping process will complete the following steps:
1747 Build tools necessary to build the compiler.
1750 Perform a 3-stage bootstrap of the compiler. This includes building
1751 three times the target tools for use by the compiler such as binutils
1752 (bfd, binutils, gas, gprof, ld, and opcodes) if they have been
1753 individually linked or moved into the top level GCC source tree before
1757 Perform a comparison test of the stage2 and stage3 compilers.
1760 Build runtime libraries using the stage3 compiler from the previous step.
1764 If you are short on disk space you might consider @samp{make
1765 bootstrap-lean} instead. The sequence of compilation is the
1766 same described above, but object files from the stage1 and
1767 stage2 of the 3-stage bootstrap of the compiler are deleted as
1768 soon as they are no longer needed.
1770 If you wish to use non-default GCC flags when compiling the stage2
1771 and stage3 compilers, set @code{BOOT_CFLAGS} on the command line when
1772 doing @samp{make}. For example, if you want to save additional space
1773 during the bootstrap and in the final installation as well, you can
1774 build the compiler binaries without debugging information as in the
1775 following example. This will save roughly 40% of disk space both for
1776 the bootstrap and the final installation. (Libraries will still contain
1777 debugging information.)
1780 make BOOT_CFLAGS='-O' bootstrap
1783 You can place non-default optimization flags into @code{BOOT_CFLAGS}; they
1784 are less well tested here than the default of @samp{-g -O2}, but should
1785 still work. In a few cases, you may find that you need to specify special
1786 flags such as @option{-msoft-float} here to complete the bootstrap; or,
1787 if the native compiler miscompiles the stage1 compiler, you may need
1788 to work around this, by choosing @code{BOOT_CFLAGS} to avoid the parts
1789 of the stage1 compiler that were miscompiled, or by using @samp{make
1790 bootstrap4} to increase the number of stages of bootstrap.
1792 @code{BOOT_CFLAGS} does not apply to bootstrapped target libraries.
1793 Since these are always compiled with the compiler currently being
1794 bootstrapped, you can use @code{CFLAGS_FOR_TARGET} to modify their
1795 compilation flags, as for non-bootstrapped target libraries.
1796 Again, if the native compiler miscompiles the stage1 compiler, you may
1797 need to work around this by avoiding non-working parts of the stage1
1798 compiler. Use @code{STAGE1_LIBCFLAGS} to this end.
1800 If you used the flag @option{--enable-languages=@dots{}} to restrict
1801 the compilers to be built, only those you've actually enabled will be
1802 built. This will of course only build those runtime libraries, for
1803 which the particular compiler has been built. Please note,
1804 that re-defining @env{LANGUAGES} when calling @samp{make}
1805 @strong{does not} work anymore!
1807 If the comparison of stage2 and stage3 fails, this normally indicates
1808 that the stage2 compiler has compiled GCC incorrectly, and is therefore
1809 a potentially serious bug which you should investigate and report. (On
1810 a few systems, meaningful comparison of object files is impossible; they
1811 always appear ``different''. If you encounter this problem, you will
1812 need to disable comparison in the @file{Makefile}.)
1814 If you do not want to bootstrap your compiler, you can configure with
1815 @option{--disable-bootstrap}. In particular cases, you may want to
1816 bootstrap your compiler even if the target system is not the same as
1817 the one you are building on: for example, you could build a
1818 @code{powerpc-unknown-linux-gnu} toolchain on a
1819 @code{powerpc64-unknown-linux-gnu} host. In this case, pass
1820 @option{--enable-bootstrap} to the configure script.
1823 @section Building a cross compiler
1825 When building a cross compiler, it is not generally possible to do a
1826 3-stage bootstrap of the compiler. This makes for an interesting problem
1827 as parts of GCC can only be built with GCC@.
1829 To build a cross compiler, we first recommend building and installing a
1830 native compiler. You can then use the native GCC compiler to build the
1831 cross compiler. The installed native compiler needs to be GCC version
1834 If the cross compiler is to be built with support for the Java
1835 programming language and the ability to compile .java source files is
1836 desired, the installed native compiler used to build the cross
1837 compiler needs to be the same GCC version as the cross compiler. In
1838 addition the cross compiler needs to be configured with
1839 @option{--with-ecj-jar=@dots{}}.
1841 Assuming you have already installed a native copy of GCC and configured
1842 your cross compiler, issue the command @command{make}, which performs the
1847 Build host tools necessary to build the compiler.
1850 Build target tools for use by the compiler such as binutils (bfd,
1851 binutils, gas, gprof, ld, and opcodes)
1852 if they have been individually linked or moved into the top level GCC source
1853 tree before configuring.
1856 Build the compiler (single stage only).
1859 Build runtime libraries using the compiler from the previous step.
1862 Note that if an error occurs in any step the make process will exit.
1864 If you are not building GNU binutils in the same source tree as GCC,
1865 you will need a cross-assembler and cross-linker installed before
1866 configuring GCC@. Put them in the directory
1867 @file{@var{prefix}/@var{target}/bin}. Here is a table of the tools
1868 you should put in this directory:
1872 This should be the cross-assembler.
1875 This should be the cross-linker.
1878 This should be the cross-archiver: a program which can manipulate
1879 archive files (linker libraries) in the target machine's format.
1882 This should be a program to construct a symbol table in an archive file.
1885 The installation of GCC will find these programs in that directory,
1886 and copy or link them to the proper place to for the cross-compiler to
1887 find them when run later.
1889 The easiest way to provide these files is to build the Binutils package.
1890 Configure it with the same @option{--host} and @option{--target}
1891 options that you use for configuring GCC, then build and install
1892 them. They install their executables automatically into the proper
1893 directory. Alas, they do not support all the targets that GCC
1896 If you are not building a C library in the same source tree as GCC,
1897 you should also provide the target libraries and headers before
1898 configuring GCC, specifying the directories with
1899 @option{--with-sysroot} or @option{--with-headers} and
1900 @option{--with-libs}. Many targets also require ``start files'' such
1901 as @file{crt0.o} and
1902 @file{crtn.o} which are linked into each executable. There may be several
1903 alternatives for @file{crt0.o}, for use with profiling or other
1904 compilation options. Check your target's definition of
1905 @code{STARTFILE_SPEC} to find out what start files it uses.
1907 @section Building in parallel
1909 GNU Make 3.79 and above, which is necessary to build GCC, support
1910 building in parallel. To activate this, you can use @samp{make -j 2}
1911 instead of @samp{make}. You can also specify a bigger number, and
1912 in most cases using a value greater than the number of processors in
1913 your machine will result in fewer and shorter I/O latency hits, thus
1914 improving overall throughput; this is especially true for slow drives
1915 and network filesystems.
1917 @section Building the Ada compiler
1919 In order to build GNAT, the Ada compiler, you need a working GNAT
1920 compiler (GCC version 3.4 or later).
1921 This includes GNAT tools such as @command{gnatmake} and
1922 @command{gnatlink}, since the Ada front end is written in Ada and
1923 uses some GNAT-specific extensions.
1925 In order to build a cross compiler, it is suggested to install
1926 the new compiler as native first, and then use it to build the cross
1929 @command{configure} does not test whether the GNAT installation works
1930 and has a sufficiently recent version; if too old a GNAT version is
1931 installed, the build will fail unless @option{--enable-languages} is
1932 used to disable building the Ada front end.
1934 @env{ADA_INCLUDE_PATH} and @env{ADA_OBJECT_PATH} environment variables
1935 must not be set when building the Ada compiler, the Ada tools, or the
1936 Ada runtime libraries. You can check that your build environment is clean
1937 by verifying that @samp{gnatls -v} lists only one explicit path in each
1940 @section Building with profile feedback
1942 It is possible to use profile feedback to optimize the compiler itself. This
1943 should result in a faster compiler binary. Experiments done on x86 using gcc
1944 3.3 showed approximately 7 percent speedup on compiling C programs. To
1945 bootstrap the compiler with profile feedback, use @code{make profiledbootstrap}.
1947 When @samp{make profiledbootstrap} is run, it will first build a @code{stage1}
1948 compiler. This compiler is used to build a @code{stageprofile} compiler
1949 instrumented to collect execution counts of instruction and branch
1950 probabilities. Then runtime libraries are compiled with profile collected.
1951 Finally a @code{stagefeedback} compiler is built using the information collected.
1953 Unlike standard bootstrap, several additional restrictions apply. The
1954 compiler used to build @code{stage1} needs to support a 64-bit integral type.
1955 It is recommended to only use GCC for this. Also parallel make is currently
1956 not supported since collisions in profile collecting may occur.
1963 @uref{./index.html,,Return to the GCC Installation page}
1967 @c ***Testing*****************************************************************
1969 @comment node-name, next, previous, up
1970 @node Testing, Final install, Building, Installing GCC
1974 @chapter Installing GCC: Testing
1977 @cindex Installing GCC: Testing
1980 Before you install GCC, we encourage you to run the testsuites and to
1981 compare your results with results from a similar configuration that have
1982 been submitted to the
1983 @uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
1984 Some of these archived results are linked from the build status lists
1985 at @uref{http://gcc.gnu.org/buildstat.html}, although not everyone who
1986 reports a successful build runs the testsuites and submits the results.
1987 This step is optional and may require you to download additional software,
1988 but it can give you confidence in your new GCC installation or point out
1989 problems before you install and start using your new GCC@.
1991 First, you must have @uref{download.html,,downloaded the testsuites}.
1992 These are part of the full distribution, but if you downloaded the
1993 ``core'' compiler plus any front ends, you must download the testsuites
1996 Second, you must have the testing tools installed. This includes
1997 @uref{http://www.gnu.org/software/dejagnu/,,DejaGnu}, Tcl, and Expect;
1998 the DejaGnu site has links to these.
2000 If the directories where @command{runtest} and @command{expect} were
2001 installed are not in the @env{PATH}, you may need to set the following
2002 environment variables appropriately, as in the following example (which
2003 assumes that DejaGnu has been installed under @file{/usr/local}):
2006 TCL_LIBRARY = /usr/local/share/tcl8.0
2007 DEJAGNULIBS = /usr/local/share/dejagnu
2010 (On systems such as Cygwin, these paths are required to be actual
2011 paths, not mounts or links; presumably this is due to some lack of
2012 portability in the DejaGnu code.)
2015 Finally, you can run the testsuite (which may take a long time):
2017 cd @var{objdir}; make -k check
2020 This will test various components of GCC, such as compiler
2021 front ends and runtime libraries. While running the testsuite, DejaGnu
2022 might emit some harmless messages resembling
2023 @samp{WARNING: Couldn't find the global config file.} or
2024 @samp{WARNING: Couldn't find tool init file} that can be ignored.
2026 If you are testing a cross-compiler, you may want to run the testsuite
2027 on a simulator as described at @uref{http://gcc.gnu.org/simtest-howto.html}.
2029 @section How can you run the testsuite on selected tests?
2031 In order to run sets of tests selectively, there are targets
2032 @samp{make check-gcc} and @samp{make check-g++}
2033 in the @file{gcc} subdirectory of the object directory. You can also
2034 just run @samp{make check} in a subdirectory of the object directory.
2037 A more selective way to just run all @command{gcc} execute tests in the
2041 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
2044 Likewise, in order to run only the @command{g++} ``old-deja'' tests in
2045 the testsuite with filenames matching @samp{9805*}, you would use
2048 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
2051 The @file{*.exp} files are located in the testsuite directories of the GCC
2052 source, the most important ones being @file{compile.exp},
2053 @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
2054 To get a list of the possible @file{*.exp} files, pipe the
2055 output of @samp{make check} into a file and look at the
2056 @samp{Running @dots{} .exp} lines.
2058 @section Passing options and running multiple testsuites
2060 You can pass multiple options to the testsuite using the
2061 @samp{--target_board} option of DejaGNU, either passed as part of
2062 @samp{RUNTESTFLAGS}, or directly to @command{runtest} if you prefer to
2063 work outside the makefiles. For example,
2066 make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fmerge-constants"
2069 will run the standard @command{g++} testsuites (``unix'' is the target name
2070 for a standard native testsuite situation), passing
2071 @samp{-O3 -fmerge-constants} to the compiler on every test, i.e.,
2072 slashes separate options.
2074 You can run the testsuites multiple times using combinations of options
2075 with a syntax similar to the brace expansion of popular shells:
2078 @dots{}"--target_board=arm-sim\@{-mhard-float,-msoft-float\@}\@{-O1,-O2,-O3,\@}"
2081 (Note the empty option caused by the trailing comma in the final group.)
2082 The following will run each testsuite eight times using the @samp{arm-sim}
2083 target, as if you had specified all possible combinations yourself:
2086 --target_board=arm-sim/-mhard-float/-O1
2087 --target_board=arm-sim/-mhard-float/-O2
2088 --target_board=arm-sim/-mhard-float/-O3
2089 --target_board=arm-sim/-mhard-float
2090 --target_board=arm-sim/-msoft-float/-O1
2091 --target_board=arm-sim/-msoft-float/-O2
2092 --target_board=arm-sim/-msoft-float/-O3
2093 --target_board=arm-sim/-msoft-float
2096 They can be combined as many times as you wish, in arbitrary ways. This
2100 @dots{}"--target_board=unix/-Wextra\@{-O3,-fno-strength\@}\@{-fomit-frame,\@}"
2103 will generate four combinations, all involving @samp{-Wextra}.
2105 The disadvantage to this method is that the testsuites are run in serial,
2106 which is a waste on multiprocessor systems. For users with GNU Make and
2107 a shell which performs brace expansion, you can run the testsuites in
2108 parallel by having the shell perform the combinations and @command{make}
2109 do the parallel runs. Instead of using @samp{--target_board}, use a
2110 special makefile target:
2113 make -j@var{N} check-@var{testsuite}//@var{test-target}/@var{option1}/@var{option2}/@dots{}
2119 make -j3 check-gcc//sh-hms-sim/@{-m1,-m2,-m3,-m3e,-m4@}/@{,-nofpu@}
2122 will run three concurrent ``make-gcc'' testsuites, eventually testing all
2123 ten combinations as described above. Note that this is currently only
2124 supported in the @file{gcc} subdirectory. (To see how this works, try
2125 typing @command{echo} before the example given here.)
2128 @section Additional testing for Java Class Libraries
2130 The Java runtime tests can be executed via @samp{make check}
2131 in the @file{@var{target}/libjava/testsuite} directory in
2134 The @uref{http://sourceware.org/mauve/,,Mauve Project} provides
2135 a suite of tests for the Java Class Libraries. This suite can be run
2136 as part of libgcj testing by placing the Mauve tree within the libjava
2137 testsuite at @file{libjava/testsuite/libjava.mauve/mauve}, or by
2138 specifying the location of that tree when invoking @samp{make}, as in
2139 @samp{make MAUVEDIR=~/mauve check}.
2141 @section How to interpret test results
2143 The result of running the testsuite are various @file{*.sum} and @file{*.log}
2144 files in the testsuite subdirectories. The @file{*.log} files contain a
2145 detailed log of the compiler invocations and the corresponding
2146 results, the @file{*.sum} files summarize the results. These summaries
2147 contain status codes for all tests:
2151 PASS: the test passed as expected
2153 XPASS: the test unexpectedly passed
2155 FAIL: the test unexpectedly failed
2157 XFAIL: the test failed as expected
2159 UNSUPPORTED: the test is not supported on this platform
2161 ERROR: the testsuite detected an error
2163 WARNING: the testsuite detected a possible problem
2166 It is normal for some tests to report unexpected failures. At the
2167 current time the testing harness does not allow fine grained control
2168 over whether or not a test is expected to fail. This problem should
2169 be fixed in future releases.
2172 @section Submitting test results
2174 If you want to report the results to the GCC project, use the
2175 @file{contrib/test_summary} shell script. Start it in the @var{objdir} with
2178 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
2179 -m gcc-testresults@@gcc.gnu.org |sh
2182 This script uses the @command{Mail} program to send the results, so
2183 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
2184 prepended to the testsuite summary and should contain any special
2185 remarks you have on your results or your build environment. Please
2186 do not edit the testsuite result block or the subject line, as these
2187 messages may be automatically processed.
2194 @uref{./index.html,,Return to the GCC Installation page}
2198 @c ***Final install***********************************************************
2200 @comment node-name, next, previous, up
2201 @node Final install, , Testing, Installing GCC
2203 @ifset finalinstallhtml
2205 @chapter Installing GCC: Final installation
2208 Now that GCC has been built (and optionally tested), you can install it with
2210 cd @var{objdir}; make install
2213 We strongly recommend to install into a target directory where there is
2214 no previous version of GCC present. Also, the GNAT runtime should not
2215 be stripped, as this would break certain features of the debugger that
2216 depend on this debugging information (catching Ada exceptions for
2219 That step completes the installation of GCC; user level binaries can
2220 be found in @file{@var{prefix}/bin} where @var{prefix} is the value
2221 you specified with the @option{--prefix} to configure (or
2222 @file{/usr/local} by default). (If you specified @option{--bindir},
2223 that directory will be used instead; otherwise, if you specified
2224 @option{--exec-prefix}, @file{@var{exec-prefix}/bin} will be used.)
2225 Headers for the C++ and Java libraries are installed in
2226 @file{@var{prefix}/include}; libraries in @file{@var{libdir}}
2227 (normally @file{@var{prefix}/lib}); internal parts of the compiler in
2228 @file{@var{libdir}/gcc} and @file{@var{libexecdir}/gcc}; documentation
2229 in info format in @file{@var{infodir}} (normally
2230 @file{@var{prefix}/info}).
2232 When installing cross-compilers, GCC's executables
2233 are not only installed into @file{@var{bindir}}, that
2234 is, @file{@var{exec-prefix}/bin}, but additionally into
2235 @file{@var{exec-prefix}/@var{target-alias}/bin}, if that directory
2236 exists. Typically, such @dfn{tooldirs} hold target-specific
2237 binutils, including assembler and linker.
2239 Installation into a temporary staging area or into a @command{chroot}
2240 jail can be achieved with the command
2243 make DESTDIR=@var{path-to-rootdir} install
2246 @noindent where @var{path-to-rootdir} is the absolute path of
2247 a directory relative to which all installation paths will be
2248 interpreted. Note that the directory specified by @code{DESTDIR}
2249 need not exist yet; it will be created if necessary.
2251 There is a subtle point with tooldirs and @code{DESTDIR}:
2252 If you relocate a cross-compiler installation with
2253 e.g.@: @samp{DESTDIR=@var{rootdir}}, then the directory
2254 @file{@var{rootdir}/@var{exec-prefix}/@var{target-alias}/bin} will
2255 be filled with duplicated GCC executables only if it already exists,
2256 it will not be created otherwise. This is regarded as a feature,
2257 not as a bug, because it gives slightly more control to the packagers
2258 using the @code{DESTDIR} feature.
2260 If you are bootstrapping a released version of GCC then please
2261 quickly review the build status page for your release, available from
2262 @uref{http://gcc.gnu.org/buildstat.html}.
2263 If your system is not listed for the version of GCC that you built,
2265 @email{gcc@@gcc.gnu.org} indicating
2266 that you successfully built and installed GCC@.
2267 Include the following information:
2271 Output from running @file{@var{srcdir}/config.guess}. Do not send
2272 that file itself, just the one-line output from running it.
2275 The output of @samp{gcc -v} for your newly installed @command{gcc}.
2276 This tells us which version of GCC you built and the options you passed to
2280 Whether you enabled all languages or a subset of them. If you used a
2281 full distribution then this information is part of the configure
2282 options in the output of @samp{gcc -v}, but if you downloaded the
2283 ``core'' compiler plus additional front ends then it isn't apparent
2284 which ones you built unless you tell us about it.
2287 If the build was for GNU/Linux, also include:
2290 The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
2291 this information should be available from @file{/etc/issue}.
2294 The version of the Linux kernel, available from @samp{uname --version}
2298 The version of glibc you used; for RPM-based systems like Red Hat,
2299 Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
2300 and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
2302 For other systems, you can include similar information if you think it is
2306 Any other information that you think would be useful to people building
2307 GCC on the same configuration. The new entry in the build status list
2308 will include a link to the archived copy of your message.
2311 We'd also like to know if the
2313 @ref{Specific, host/target specific installation notes}
2316 @uref{specific.html,,host/target specific installation notes}
2318 didn't include your host/target information or if that information is
2319 incomplete or out of date. Send a note to
2320 @email{gcc@@gcc.gnu.org} detailing how the information should be changed.
2322 If you find a bug, please report it following the
2323 @uref{../bugs.html,,bug reporting guidelines}.
2325 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
2326 dvi}. You will need to have @command{texi2dvi} (version at least 4.4)
2327 and @TeX{} installed. This creates a number of @file{.dvi} files in
2328 subdirectories of @file{@var{objdir}}; these may be converted for
2329 printing with programs such as @command{dvips}. Alternately, by using
2330 @samp{make pdf} in place of @samp{make dvi}, you can create documentation
2331 in the form of @file{.pdf} files; this requires @command{texi2pdf}, which
2332 is included with Texinfo version 4.8 and later. You can also
2333 @uref{http://www.gnu.org/order/order.html,,buy printed manuals from the
2334 Free Software Foundation}, though such manuals may not be for the most
2335 recent version of GCC@.
2337 If you would like to generate online HTML documentation, do @samp{cd
2338 @var{objdir}; make html} and HTML will be generated for the gcc manuals in
2339 @file{@var{objdir}/gcc/HTML}.
2346 @uref{./index.html,,Return to the GCC Installation page}
2350 @c ***Binaries****************************************************************
2352 @comment node-name, next, previous, up
2353 @node Binaries, Specific, Installing GCC, Top
2357 @chapter Installing GCC: Binaries
2360 @cindex Installing GCC: Binaries
2362 We are often asked about pre-compiled versions of GCC@. While we cannot
2363 provide these for all platforms, below you'll find links to binaries for
2364 various platforms where creating them by yourself is not easy due to various
2367 Please note that we did not create these binaries, nor do we
2368 support them. If you have any problems installing them, please
2369 contact their makers.
2376 @uref{http://www.bullfreeware.com,,Bull's Freeware and Shareware Archive for AIX};
2379 @uref{http://pware.hvcc.edu,,Hudson Valley Community College Open Source Softeware for IBM System p};
2382 @uref{http://www.perzl.org/aix,,AIX 5L and 6 Open Source Packages}.
2386 DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}.
2389 Renesas H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
2390 Development Tools for the Renesas H8/300[HS] Series}.
2396 @uref{http://hpux.cs.utah.edu/,,HP-UX Porting Center};
2399 @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}.
2403 Motorola 68HC11/68HC12---@uref{http://www.gnu-m68hc11.org,,GNU
2404 Development Tools for the Motorola 68HC11/68HC12}.
2407 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
2408 OpenServer/Unixware}.
2411 Solaris 2 (SPARC, Intel)---@uref{http://www.sunfreeware.com/,,Sunfreeware}.
2414 SGI---@uref{http://freeware.sgi.com/,,SGI Freeware}.
2420 The @uref{http://sourceware.org/cygwin/,,Cygwin} project;
2422 The @uref{http://www.mingw.org/,,MinGW} project.
2426 @uref{ftp://ftp.thewrittenword.com/packages/by-name/,,The
2427 Written Word} offers binaries for
2428 AIX 4.3.3, 5.1 and 5.2,
2430 Tru64 UNIX 4.0D and 5.1,
2432 HP-UX 10.20, 11.00, and 11.11, and
2433 Solaris/SPARC 2.5.1, 2.6, 7, 8, 9 and 10.
2436 @uref{http://www.openpkg.org/,,OpenPKG} offers binaries for quite a
2437 number of platforms.
2440 The @uref{http://gcc.gnu.org/wiki/GFortranBinaries,,GFortran Wiki} has
2441 links to GNU Fortran binaries for several platforms.
2444 In addition to those specific offerings, you can get a binary
2445 distribution CD-ROM from the
2446 @uref{http://www.gnu.org/order/order.html,,Free Software Foundation}.
2447 It contains binaries for a number of platforms, and
2448 includes not only GCC, but other stuff as well. The current CD does
2449 not contain the latest version of GCC, but it should allow
2450 bootstrapping the compiler. An updated version of that disk is in the
2458 @uref{./index.html,,Return to the GCC Installation page}
2462 @c ***Specific****************************************************************
2464 @comment node-name, next, previous, up
2465 @node Specific, Old, Binaries, Top
2469 @chapter Host/target specific installation notes for GCC
2472 @cindex Specific installation notes
2473 @cindex Target specific installation
2474 @cindex Host specific installation
2475 @cindex Target specific installation notes
2477 Please read this document carefully @emph{before} installing the
2478 GNU Compiler Collection on your machine.
2480 Note that this list of install notes is @emph{not} a list of supported
2481 hosts or targets. Not all supported hosts and targets are listed
2482 here, only the ones that require host-specific or target-specific
2488 @uref{#alpha-x-x,,alpha*-*-*}
2490 @uref{#alpha-dec-osf,,alpha*-dec-osf*}
2492 @uref{#arc-x-elf,,arc-*-elf}
2494 @uref{#arm-x-elf,,arm-*-elf}
2495 @uref{#arm-x-coff,,arm-*-coff}
2496 @uref{#arm-x-aout,,arm-*-aout}
2500 @uref{#bfin,,Blackfin}
2504 @uref{#x-x-freebsd,,*-*-freebsd*}
2506 @uref{#h8300-hms,,h8300-hms}
2508 @uref{#hppa-hp-hpux,,hppa*-hp-hpux*}
2510 @uref{#hppa-hp-hpux10,,hppa*-hp-hpux10}
2512 @uref{#hppa-hp-hpux11,,hppa*-hp-hpux11}
2514 @uref{#x-x-linux-gnu,,*-*-linux-gnu}
2516 @uref{#ix86-x-linux,,i?86-*-linux*}
2518 @uref{#ix86-x-solaris210,,i?86-*-solaris2.10}
2520 @uref{#ia64-x-linux,,ia64-*-linux}
2522 @uref{#ia64-x-hpux,,ia64-*-hpux*}
2524 @uref{#x-ibm-aix,,*-ibm-aix*}
2526 @uref{#iq2000-x-elf,,iq2000-*-elf}
2528 @uref{#m32c-x-elf,,m32c-*-elf}
2530 @uref{#m32r-x-elf,,m32r-*-elf}
2532 @uref{#m6811-elf,,m6811-elf}
2534 @uref{#m6812-elf,,m6812-elf}
2536 @uref{#m68k-x-x,,m68k-*-*}
2538 @uref{#m68k-uclinux,,m68k-uclinux}
2540 @uref{#mips-x-x,,mips-*-*}
2542 @uref{#mips-sgi-irix5,,mips-sgi-irix5}
2544 @uref{#mips-sgi-irix6,,mips-sgi-irix6}
2546 @uref{#powerpc-x-x,,powerpc*-*-*}
2548 @uref{#powerpc-x-darwin,,powerpc-*-darwin*}
2550 @uref{#powerpc-x-elf,,powerpc-*-elf}
2552 @uref{#powerpc-x-linux-gnu,,powerpc*-*-linux-gnu*}
2554 @uref{#powerpc-x-netbsd,,powerpc-*-netbsd*}
2556 @uref{#powerpc-x-eabisim,,powerpc-*-eabisim}
2558 @uref{#powerpc-x-eabi,,powerpc-*-eabi}
2560 @uref{#powerpcle-x-elf,,powerpcle-*-elf}
2562 @uref{#powerpcle-x-eabisim,,powerpcle-*-eabisim}
2564 @uref{#powerpcle-x-eabi,,powerpcle-*-eabi}
2566 @uref{#s390-x-linux,,s390-*-linux*}
2568 @uref{#s390x-x-linux,,s390x-*-linux*}
2570 @uref{#s390x-ibm-tpf,,s390x-ibm-tpf*}
2572 @uref{#x-x-solaris2,,*-*-solaris2*}
2574 @uref{#sparc-sun-solaris2,,sparc-sun-solaris2*}
2576 @uref{#sparc-sun-solaris27,,sparc-sun-solaris2.7}
2578 @uref{#sparc-x-linux,,sparc-*-linux*}
2580 @uref{#sparc64-x-solaris2,,sparc64-*-solaris2*}
2582 @uref{#sparcv9-x-solaris2,,sparcv9-*-solaris2*}
2584 @uref{#x-x-vxworks,,*-*-vxworks*}
2586 @uref{#x86-64-x-x,,x86_64-*-*, amd64-*-*}
2588 @uref{#xtensa-x-elf,,xtensa-*-elf}
2590 @uref{#xtensa-x-linux,,xtensa-*-linux*}
2592 @uref{#windows,,Microsoft Windows}
2596 @uref{#older,,Older systems}
2601 @uref{#elf,,all ELF targets} (SVR4, Solaris 2, etc.)
2607 <!-- -------- host/target specific issues start here ---------------- -->
2610 @heading @anchor{alpha-x-x}alpha*-*-*
2612 This section contains general configuration information for all
2613 alpha-based platforms using ELF (in particular, ignore this section for
2614 DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
2615 section, please read all other sections that match your target.
2617 We require binutils 2.11.2 or newer.
2618 Previous binutils releases had a number of problems with DWARF 2
2619 debugging information, not the least of which is incorrect linking of
2625 @heading @anchor{alpha-dec-osf}alpha*-dec-osf*
2626 Systems using processors that implement the DEC Alpha architecture and
2627 are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq
2628 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
2630 As of GCC 3.2, versions before @code{alpha*-dec-osf4} are no longer
2631 supported. (These are the versions which identify themselves as DEC
2634 In Digital Unix V4.0, virtual memory exhausted bootstrap failures
2635 may be fixed by configuring with @option{--with-gc=simple},
2636 reconfiguring Kernel Virtual Memory and Swap parameters
2637 per the @command{/usr/sbin/sys_check} Tuning Suggestions,
2638 or applying the patch in
2639 @uref{http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html}.
2641 In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
2642 currently (2001-06-13) work with @command{mips-tfile}. As a workaround,
2643 we need to use the old assembler, invoked via the barely documented
2644 @option{-oldas} option. To bootstrap GCC, you either need to use the
2648 % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}]
2651 or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
2654 % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}]
2657 As of GNU binutils 2.11.2, neither GNU @command{as} nor GNU @command{ld}
2658 are supported on Tru64 UNIX, so you must not configure GCC with
2659 @option{--with-gnu-as} or @option{--with-gnu-ld}.
2661 GCC writes a @samp{.verstamp} directive to the assembler output file
2662 unless it is built as a cross-compiler. It gets the version to use from
2663 the system header file @file{/usr/include/stamp.h}. If you install a
2664 new version of DEC Unix, you should rebuild GCC to pick up the new version
2667 Note that since the Alpha is a 64-bit architecture, cross-compilers from
2668 32-bit machines will not generate code as efficient as that generated
2669 when the compiler is running on a 64-bit machine because many
2670 optimizations that depend on being able to represent a word on the
2671 target in an integral value on the host cannot be performed. Building
2672 cross-compilers on the Alpha for 32-bit machines has only been tested in
2673 a few cases and may not work properly.
2675 @samp{make compare} may fail on old versions of DEC Unix unless you add
2676 @option{-save-temps} to @code{BOOT_CFLAGS}. On these systems, the name
2677 of the assembler input file is stored in the object file, and that makes
2678 comparison fail if it differs between the @code{stage1} and
2679 @code{stage2} compilations. The option @option{-save-temps} forces a
2680 fixed name to be used for the assembler input file, instead of a
2681 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
2682 unless the comparisons fail without that option. If you add
2683 @option{-save-temps}, you will have to manually delete the @samp{.i} and
2684 @samp{.s} files after each series of compilations.
2686 GCC now supports both the native (ECOFF) debugging format used by DBX
2687 and GDB and an encapsulated STABS format for use only with GDB@. See the
2688 discussion of the @option{--with-stabs} option of @file{configure} above
2689 for more information on these formats and how to select them.
2691 There is a bug in DEC's assembler that produces incorrect line numbers
2692 for ECOFF format when the @samp{.align} directive is used. To work
2693 around this problem, GCC will not emit such alignment directives
2694 while writing ECOFF format debugging information even if optimization is
2695 being performed. Unfortunately, this has the very undesirable
2696 side-effect that code addresses when @option{-O} is specified are
2697 different depending on whether or not @option{-g} is also specified.
2699 To avoid this behavior, specify @option{-gstabs+} and use GDB instead of
2700 DBX@. DEC is now aware of this problem with the assembler and hopes to
2701 provide a fix shortly.
2706 @heading @anchor{arc-x-elf}arc-*-elf
2707 Argonaut ARC processor.
2708 This configuration is intended for embedded systems.
2713 @heading @anchor{arm-x-elf}arm-*-elf
2714 ARM-family processors. Subtargets that use the ELF object format
2715 require GNU binutils 2.13 or newer. Such subtargets include:
2716 @code{arm-*-freebsd}, @code{arm-*-netbsdelf}, @code{arm-*-*linux}
2717 and @code{arm-*-rtems}.
2722 @heading @anchor{arm-x-coff}arm-*-coff
2723 ARM-family processors. Note that there are two different varieties
2724 of PE format subtarget supported: @code{arm-wince-pe} and
2725 @code{arm-pe} as well as a standard COFF target @code{arm-*-coff}.
2730 @heading @anchor{arm-x-aout}arm-*-aout
2731 ARM-family processors. These targets support the AOUT file format:
2732 @code{arm-*-aout}, @code{arm-*-netbsd}.
2737 @heading @anchor{avr}avr
2739 ATMEL AVR-family micro controllers. These are used in embedded
2740 applications. There are no standard Unix configurations.
2742 @xref{AVR Options,, AVR Options, gcc, Using the GNU Compiler
2746 See ``AVR Options'' in the main manual
2748 for the list of supported MCU types.
2750 Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
2752 Further installation notes and other useful information about AVR tools
2753 can also be obtained from:
2757 @uref{http://www.nongnu.org/avr/,,http://www.nongnu.org/avr/}
2759 @uref{http://home.overta.ru/users/denisc/,,http://home.overta.ru/users/denisc/}
2761 @uref{http://www.amelek.gda.pl/avr/,,http://www.amelek.gda.pl/avr/}
2764 We @emph{strongly} recommend using binutils 2.13 or newer.
2766 The following error:
2768 Error: register required
2771 indicates that you should upgrade to a newer version of the binutils.
2776 @heading @anchor{bfin}Blackfin
2778 The Blackfin processor, an Analog Devices DSP.
2780 @xref{Blackfin Options,, Blackfin Options, gcc, Using the GNU Compiler
2784 See ``Blackfin Options'' in the main manual
2787 More information, and a version of binutils with support for this processor,
2788 is available at @uref{http://blackfin.uclinux.org}
2793 @heading @anchor{cris}CRIS
2795 CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
2796 series. These are used in embedded applications.
2799 @xref{CRIS Options,, CRIS Options, gcc, Using the GNU Compiler
2803 See ``CRIS Options'' in the main manual
2805 for a list of CRIS-specific options.
2807 There are a few different CRIS targets:
2810 Mainly for monolithic embedded systems. Includes a multilib for the
2811 @samp{v10} core used in @samp{ETRAX 100 LX}.
2812 @item cris-axis-linux-gnu
2813 A GNU/Linux port for the CRIS architecture, currently targeting
2814 @samp{ETRAX 100 LX} by default.
2817 For @code{cris-axis-elf} you need binutils 2.11
2818 or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer.
2820 Pre-packaged tools can be obtained from
2821 @uref{ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/}. More
2822 information about this platform is available at
2823 @uref{http://developer.axis.com/}.
2828 @heading @anchor{crx}CRX
2830 The CRX CompactRISC architecture is a low-power 32-bit architecture with
2831 fast context switching and architectural extensibility features.
2834 @xref{CRX Options,, CRX Options, gcc, Using and Porting the GNU Compiler
2839 See ``CRX Options'' in the main manual for a list of CRX-specific options.
2842 Use @samp{configure --target=crx-elf --enable-languages=c,c++} to configure
2843 GCC@ for building a CRX cross-compiler. The option @samp{--target=crx-elf}
2844 is also used to build the @samp{newlib} C library for CRX.
2846 It is also possible to build libstdc++-v3 for the CRX architecture. This
2847 needs to be done in a separate step with the following configure settings:
2848 @samp{gcc/libstdc++-v3/configure --host=crx-elf --with-newlib
2849 --enable-sjlj-exceptions --enable-cxx-flags='-fexceptions -frtti'}
2854 @heading @anchor{dos}DOS
2856 Please have a look at the @uref{binaries.html,,binaries page}.
2858 You cannot install GCC by itself on MSDOS; it will not compile under
2859 any MSDOS compiler except itself. You need to get the complete
2860 compilation package DJGPP, which includes binaries as well as sources,
2861 and includes all the necessary compilation tools and libraries.
2866 @heading @anchor{x-x-freebsd}*-*-freebsd*
2868 The version of binutils installed in @file{/usr/bin} probably works with
2869 this release of GCC@. However, on FreeBSD 4, bootstrapping against the
2870 latest FSF binutils is known to improve overall testsuite results; and,
2871 on FreeBSD/alpha, using binutils 2.14 or later is required to build libjava.
2873 Support for FreeBSD 1 was discontinued in GCC 3.2.
2875 Support for FreeBSD 2 will be discontinued after GCC 3.4. The
2876 following was true for GCC 3.1 but the current status is unknown.
2877 For FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
2878 configuration support and files as shipped with GCC 2.95 are still in
2879 place. FreeBSD 2.2.7 has been known to bootstrap completely; however,
2880 it is unknown which version of binutils was used (it is assumed that it
2881 was the system copy in @file{/usr/bin}) and C++ EH failures were noted.
2883 For FreeBSD using the ELF file format: DWARF 2 debugging is now the
2884 default for all CPU architectures. It had been the default on
2885 FreeBSD/alpha since its inception. You may use @option{-gstabs} instead
2886 of @option{-g}, if you really want the old debugging format. There are
2887 no known issues with mixing object files and libraries with different
2888 debugging formats. Otherwise, this release of GCC should now match more
2889 of the configuration used in the stock FreeBSD configuration of GCC@. In
2890 particular, @option{--enable-threads} is now configured by default.
2891 However, as a general user, do not attempt to replace the system
2892 compiler with this release. Known to bootstrap and check with good
2893 results on FreeBSD 4.9-STABLE and 5-CURRENT@. In the past, known to
2894 bootstrap and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2,
2895 4.3, 4.4, 4.5, 4.8-STABLE@.
2897 In principle, @option{--enable-threads} is now compatible with
2898 @option{--enable-libgcj} on FreeBSD@. However, it has only been built
2899 and tested on @samp{i386-*-freebsd[45]} and @samp{alpha-*-freebsd[45]}.
2901 library may be incorrectly built (symbols are missing at link time).
2902 There is a rare timing-based startup hang (probably involves an
2903 assumption about the thread library). Multi-threaded boehm-gc (required for
2904 libjava) exposes severe threaded signal-handling bugs on FreeBSD before
2905 4.5-RELEASE@. Other CPU architectures
2906 supported by FreeBSD will require additional configuration tuning in, at
2907 the very least, both boehm-gc and libffi.
2909 Shared @file{libgcc_s.so} is now built and installed by default.
2914 @heading @anchor{h8300-hms}h8300-hms
2915 Renesas H8/300 series of processors.
2917 Please have a look at the @uref{binaries.html,,binaries page}.
2919 The calling convention and structure layout has changed in release 2.6.
2920 All code must be recompiled. The calling convention now passes the
2921 first three arguments in function calls in registers. Structures are no
2922 longer a multiple of 2 bytes.
2927 @heading @anchor{hppa-hp-hpux}hppa*-hp-hpux*
2928 Support for HP-UX version 9 and older was discontinued in GCC 3.4.
2930 We require using gas/binutils on all hppa platforms;
2931 you may encounter a variety of problems if you try to use the HP assembler.
2933 Specifically, @option{-g} does not work on HP-UX (since that system
2934 uses a peculiar debugging format which GCC does not know about), unless
2935 you use GAS and GDB@. It may be helpful to configure GCC with the
2936 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
2937 @option{--with-as=@dots{}} options to ensure that GCC can find GAS@.
2939 If you wish to use the pa-risc 2.0 architecture support with a 32-bit
2940 runtime, you must use gas/binutils 2.11 or newer.
2942 There are two default scheduling models for instructions. These are
2943 PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
2944 architecture specified for the target machine when configuring.
2945 PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
2946 the target is a @samp{hppa1*} machine.
2948 The PROCESSOR_8000 model is not well suited to older processors. Thus,
2949 it is important to completely specify the machine architecture when
2950 configuring if you want a model other than PROCESSOR_8000. The macro
2951 TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
2952 default scheduling model is desired.
2954 As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10
2955 through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later.
2956 This namespace change might cause problems when bootstrapping with
2957 an earlier version of GCC or the HP compiler as essentially the same
2958 namespace is required for an entire build. This problem can be avoided
2959 in a number of ways. With HP cc, @env{UNIX_STD} can be set to @samp{95}
2960 or @samp{98}. Another way is to add an appropriate set of predefines
2961 to @env{CC}. The description for the @option{munix=} option contains
2962 a list of the predefines used with each standard.
2964 As of GCC 4.1, @env{DWARF2} exception handling is available on HP-UX@.
2965 It is now the default. This exposed a bug in the handling of data
2966 relocations in the GAS assembler. The handling of 64-bit data relocations
2967 was seriously broken, affecting debugging and exception support on all
2968 @samp{hppa64-*-*} targets. Under some circumstances, 32-bit data relocations
2969 could also be handled incorrectly. This problem is fixed in GAS version
2972 GCC versions prior to 4.1 incorrectly passed and returned complex
2973 values. They are now passed in the same manner as aggregates.
2975 More specific information to @samp{hppa*-hp-hpux*} targets follows.
2980 @heading @anchor{hppa-hp-hpux10}hppa*-hp-hpux10
2982 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
2983 @code{PHCO_19798} from HP@. HP has two sites which provide patches free of
2989 <a href="http://us.itrc.hp.com/service/home/home.do">US, Canada, Asia-Pacific, and
2993 @uref{http://us.itrc.hp.com/service/home/home.do,,} US, Canada, Asia-Pacific,
2997 @uref{http://europe.itrc.hp.com/service/home/home.do,,} Europe.
3000 The HP assembler on these systems has some problems. Most notably the
3001 assembler inserts timestamps into each object file it creates, causing
3002 the 3-stage comparison test to fail during a bootstrap.
3003 You should be able to continue by saying @samp{make all-host all-target}
3004 after getting the failure from @samp{make}.
3006 GCC 4.0 requires CVS binutils as of April 28, 2004 or later. Earlier
3007 versions require binutils 2.8 or later.
3009 The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces are
3010 used for one-only code and data. This resolves many of the previous
3011 problems in using C++ on this target. However, the ABI is not compatible
3012 with the one implemented under HP-UX 11 using secondary definitions.
3017 @heading @anchor{hppa-hp-hpux11}hppa*-hp-hpux11
3019 GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot
3020 be used to compile GCC 3.0 and up.
3022 Refer to @uref{binaries.html,,binaries} for information about obtaining
3023 precompiled GCC binaries for HP-UX@. Precompiled binaries must be obtained
3024 to build the Ada language as it can't be bootstrapped using C@. Ada is
3025 only available for the 32-bit PA-RISC runtime. The libffi and libjava
3026 haven't been ported to HP-UX and don't build.
3028 Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The
3029 bundled compiler supports only traditional C; you will need either HP's
3030 unbundled compiler, or a binary distribution of GCC@.
3032 It is possible to build GCC 3.3 starting with the bundled HP compiler,
3033 but the process requires several steps. GCC 3.3 can then be used to
3034 build later versions. The fastjar program contains ISO C code and
3035 can't be built with the HP bundled compiler. This problem can be
3036 avoided by not building the Java language. For example, use the
3037 @option{--enable-languages="c,c++,f77,objc"} option in your configure
3040 There are several possible approaches to building the distribution.
3041 Binutils can be built first using the HP tools. Then, the GCC
3042 distribution can be built. The second approach is to build GCC
3043 first using the HP tools, then build binutils, then rebuild GCC@.
3044 There have been problems with various binary distributions, so it
3045 is best not to start from a binary distribution.
3047 On 64-bit capable systems, there are two distinct targets. Different
3048 installation prefixes must be used if both are to be installed on
3049 the same system. The @samp{hppa[1-2]*-hp-hpux11*} target generates code
3050 for the 32-bit PA-RISC runtime architecture and uses the HP linker.
3051 The @samp{hppa64-hp-hpux11*} target generates 64-bit code for the
3052 PA-RISC 2.0 architecture. The HP and GNU linkers are both supported
3055 The script config.guess now selects the target type based on the compiler
3056 detected during configuration. You must define @env{PATH} or @env{CC} so
3057 that configure finds an appropriate compiler for the initial bootstrap.
3058 When @env{CC} is used, the definition should contain the options that are
3059 needed whenever @env{CC} is used.
3061 Specifically, options that determine the runtime architecture must be
3062 in @env{CC} to correctly select the target for the build. It is also
3063 convenient to place many other compiler options in @env{CC}. For example,
3064 @env{CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"}
3065 can be used to bootstrap the GCC 3.3 branch with the HP compiler in
3066 64-bit K&R/bundled mode. The @option{+DA2.0W} option will result in
3067 the automatic selection of the @samp{hppa64-hp-hpux11*} target. The
3068 macro definition table of cpp needs to be increased for a successful
3069 build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to
3070 be defined when building with the bundled compiler, or when using the
3071 @option{-Ac} option. These defines aren't necessary with @option{-Ae}.
3073 It is best to explicitly configure the @samp{hppa64-hp-hpux11*} target
3074 with the @option{--with-ld=@dots{}} option. This overrides the standard
3075 search for ld. The two linkers supported on this target require different
3076 commands. The default linker is determined during configuration. As a
3077 result, it's not possible to switch linkers in the middle of a GCC build.
3078 This has been been reported to sometimes occur in unified builds of
3081 GCC 3.0 through 3.2 require binutils 2.11 or above. GCC 3.3 through
3082 GCC 4.0 require binutils 2.14 or later.
3084 Although the HP assembler can be used for an initial build, it shouldn't
3085 be used with any languages other than C and perhaps Fortran due to its
3086 many limitations. For example, it does not support weak symbols or alias
3087 definitions. As a result, explicit template instantiations are required
3088 when using C++. This makes it difficult if not impossible to build many
3089 C++ applications. You can't generate debugging information when using
3090 the HP assembler. Finally, bootstrapping fails in the final
3091 comparison of object modules due to the time stamps that it inserts into
3092 the modules. The bootstrap can be continued from this point with
3093 @samp{make all-host all-target}.
3095 A recent linker patch must be installed for the correct operation of
3096 GCC 3.3 and later. @code{PHSS_26559} and @code{PHSS_24304} are the
3097 oldest linker patches that are known to work. They are for HP-UX
3098 11.00 and 11.11, respectively. @code{PHSS_24303}, the companion to
3099 @code{PHSS_24304}, might be usable but it hasn't been tested. These
3100 patches have been superseded. Consult the HP patch database to obtain
3101 the currently recommended linker patch for your system.
3103 The patches are necessary for the support of weak symbols on the
3104 32-bit port, and for the running of initializers and finalizers. Weak
3105 symbols are implemented using SOM secondary definition symbols. Prior
3106 to HP-UX 11, there are bugs in the linker support for secondary symbols.
3107 The patches correct a problem of linker core dumps creating shared
3108 libraries containing secondary symbols, as well as various other
3109 linking issues involving secondary symbols.
3111 GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
3112 run initializers and finalizers on the 64-bit port. The 32-bit port
3113 uses the linker @option{+init} and @option{+fini} options for the same
3114 purpose. The patches correct various problems with the +init/+fini
3115 options, including program core dumps. Binutils 2.14 corrects a
3116 problem on the 64-bit port resulting from HP's non-standard use of
3117 the .init and .fini sections for array initializers and finalizers.
3119 There are a number of issues to consider in selecting which linker to
3120 use with the 64-bit port. The GNU 64-bit linker can only create dynamic
3121 binaries. The @option{-static} option causes linking with archive
3122 libraries but doesn't produce a truly static binary. Dynamic binaries
3123 still require final binding by the dynamic loader to resolve a set of
3124 dynamic-loader-defined symbols. The default behavior of the HP linker
3125 is the same as the GNU linker. However, it can generate true 64-bit
3126 static binaries using the @option{+compat} option.
3128 The HP 64-bit linker doesn't support linkonce semantics. As a
3129 result, C++ programs have many more sections than they should.
3131 The GNU 64-bit linker has some issues with shared library support
3132 and exceptions. As a result, we only support libgcc in archive
3133 format. For similar reasons, dwarf2 unwind and exception support
3134 are disabled. The GNU linker also has problems creating binaries
3135 with @option{-static}. It doesn't provide stubs for internal
3136 calls to global functions in shared libraries, so these calls
3137 can't be overloaded.
3139 Thread support is not implemented in GCC 3.0 through 3.2, so the
3140 @option{--enable-threads} configure option does not work. In 3.3
3141 and later, POSIX threads are supported. The optional DCE thread
3142 library is not supported.
3144 This port still is undergoing significant development.
3149 @heading @anchor{x-x-linux-gnu}*-*-linux-gnu
3151 Versions of libstdc++-v3 starting with 3.2.1 require bug fixes present
3152 in glibc 2.2.5 and later. More information is available in the
3153 libstdc++-v3 documentation.
3158 @heading @anchor{ix86-x-linux}i?86-*-linux*
3160 As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
3161 See @uref{http://gcc.gnu.org/PR10877,,bug 10877} for more information.
3163 If you receive Signal 11 errors when building on GNU/Linux, then it is
3164 possible you have a hardware problem. Further information on this can be
3165 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
3170 @heading @anchor{ix86-x-solaris210}i?86-*-solaris2.10
3171 Use this for Solaris 10 or later on x86 and x86-64 systems. This
3172 configuration is supported by GCC 4.0 and later versions only.
3174 It is recommended that you configure GCC to use the GNU assembler in
3175 @file{/usr/sfw/bin/gas} but the Sun linker, using the options
3176 @option{--with-gnu-as --with-as=/usr/sfw/bin/gas --without-gnu-ld
3177 --with-ld=/usr/ccs/bin/ld}.
3182 @heading @anchor{ia64-x-linux}ia64-*-linux
3183 IA-64 processor (also known as IPF, or Itanium Processor Family)
3186 If you are using the installed system libunwind library with
3187 @option{--with-system-libunwind}, then you must use libunwind 0.98 or
3190 None of the following versions of GCC has an ABI that is compatible
3191 with any of the other versions in this list, with the exception that
3192 Red Hat 2.96 and Trillian 000171 are compatible with each other:
3193 3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
3194 This primarily affects C++ programs and programs that create shared libraries.
3195 GCC 3.1 or later is recommended for compiling linux, the kernel.
3196 As of version 3.1 GCC is believed to be fully ABI compliant, and hence no
3197 more major ABI changes are expected.
3202 @heading @anchor{ia64-x-hpux}ia64-*-hpux*
3203 Building GCC on this target requires the GNU Assembler. The bundled HP
3204 assembler will not work. To prevent GCC from using the wrong assembler,
3205 the option @option{--with-gnu-as} may be necessary.
3207 The GCC libunwind library has not been ported to HPUX@. This means that for
3208 GCC versions 3.2.3 and earlier, @option{--enable-libunwind-exceptions}
3209 is required to build GCC@. For GCC 3.3 and later, this is the default.
3210 For gcc 3.4.3 and later, @option{--enable-libunwind-exceptions} is
3211 removed and the system libunwind library will always be used.
3215 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
3217 @heading @anchor{x-ibm-aix}*-ibm-aix*
3218 Support for AIX version 3 and older was discontinued in GCC 3.4.
3220 ``out of memory'' bootstrap failures may indicate a problem with
3221 process resource limits (ulimit). Hard limits are configured in the
3222 @file{/etc/security/limits} system configuration file.
3224 To speed up the configuration phases of bootstrapping and installing GCC,
3225 one may use GNU Bash instead of AIX @command{/bin/sh}, e.g.,
3228 % CONFIG_SHELL=/opt/freeware/bin/bash
3229 % export CONFIG_SHELL
3232 and then proceed as described in @uref{build.html,,the build
3233 instructions}, where we strongly recommend specifying an absolute path
3234 to invoke @var{srcdir}/configure.
3236 Because GCC on AIX is built as a 32-bit executable by default,
3237 (although it can generate 64-bit programs) the GMP and MPFR libraries
3238 required by gfortran must be 32-bit libraries. Building GMP and MPFR
3239 as static archive libraries works better than shared libraries.
3241 Errors involving @code{alloca} when building GCC generally are due
3242 to an incorrect definition of @code{CC} in the Makefile or mixing files
3243 compiled with the native C compiler and GCC@. During the stage1 phase of
3244 the build, the native AIX compiler @strong{must} be invoked as @command{cc}
3245 (not @command{xlc}). Once @command{configure} has been informed of
3246 @command{xlc}, one needs to use @samp{make distclean} to remove the
3247 configure cache files and ensure that @env{CC} environment variable
3248 does not provide a definition that will confuse @command{configure}.
3249 If this error occurs during stage2 or later, then the problem most likely
3250 is the version of Make (see above).
3252 The native @command{as} and @command{ld} are recommended for bootstrapping
3253 on AIX 4 and required for bootstrapping on AIX 5L@. The GNU Assembler
3254 reports that it supports WEAK symbols on AIX 4, which causes GCC to try to
3255 utilize weak symbol functionality although it is not supported. The GNU
3256 Assembler and Linker do not support AIX 5L sufficiently to bootstrap GCC@.
3257 The native AIX tools do interoperate with GCC@.
3259 Building @file{libstdc++.a} requires a fix for an AIX Assembler bug
3260 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a
3261 fix for another AIX Assembler bug and a co-dependent AIX Archiver fix
3262 referenced as APAR IY53606 (AIX 5.2) or a APAR IY54774 (AIX 5.1)
3264 @samp{libstdc++} in GCC 3.4 increments the major version number of the
3265 shared object and GCC installation places the @file{libstdc++.a}
3266 shared library in a common location which will overwrite the and GCC
3267 3.3 version of the shared library. Applications either need to be
3268 re-linked against the new shared library or the GCC 3.1 and GCC 3.3
3269 versions of the @samp{libstdc++} shared object needs to be available
3270 to the AIX runtime loader. The GCC 3.1 @samp{libstdc++.so.4}, if
3271 present, and GCC 3.3 @samp{libstdc++.so.5} shared objects can be
3272 installed for runtime dynamic loading using the following steps to set
3273 the @samp{F_LOADONLY} flag in the shared object for @emph{each}
3274 multilib @file{libstdc++.a} installed:
3276 Extract the shared objects from the currently installed
3277 @file{libstdc++.a} archive:
3279 % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
3282 Enable the @samp{F_LOADONLY} flag so that the shared object will be
3283 available for runtime dynamic loading, but not linking:
3285 % strip -e libstdc++.so.4 libstdc++.so.5
3288 Archive the runtime-only shared object in the GCC 3.4
3289 @file{libstdc++.a} archive:
3291 % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
3294 Linking executables and shared libraries may produce warnings of
3295 duplicate symbols. The assembly files generated by GCC for AIX always
3296 have included multiple symbol definitions for certain global variable
3297 and function declarations in the original program. The warnings should
3298 not prevent the linker from producing a correct library or runnable
3301 AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
3302 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
3303 to parse archive libraries did not handle the new format correctly.
3304 These routines are used by GCC and result in error messages during
3305 linking such as ``not a COFF file''. The version of the routines shipped
3306 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
3307 option of the archive command may be used to create archives of 32-bit
3308 objects using the original ``small format''. A correct version of the
3309 routines is shipped with AIX 4.3.2 and above.
3311 Some versions of the AIX binder (linker) can fail with a relocation
3312 overflow severe error when the @option{-bbigtoc} option is used to link
3313 GCC-produced object files into an executable that overflows the TOC@. A fix
3314 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
3315 available from IBM Customer Support and from its
3316 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3317 website as PTF U455193.
3319 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
3320 with a segmentation fault when invoked by any version of GCC@. A fix for
3321 APAR IX87327 is available from IBM Customer Support and from its
3322 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3323 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
3325 The initial assembler shipped with AIX 4.3.0 generates incorrect object
3326 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
3327 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
3328 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3329 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
3331 AIX provides National Language Support (NLS)@. Compilers and assemblers
3332 use NLS to support locale-specific representations of various data
3333 formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
3334 separating decimal fractions). There have been problems reported where
3335 GCC does not produce the same floating-point formats that the assembler
3336 expects. If one encounters this problem, set the @env{LANG}
3337 environment variable to @samp{C} or @samp{En_US}.
3339 By default, GCC for AIX 4.1 and above produces code that can be used on
3340 both Power or PowerPC processors.
3342 A default can be specified with the @option{-mcpu=@var{cpu_type}}
3343 switch and using the configure option @option{--with-cpu-@var{cpu_type}}.
3348 @heading @anchor{iq2000-x-elf}iq2000-*-elf
3349 Vitesse IQ2000 processors. These are used in embedded
3350 applications. There are no standard Unix configurations.
3355 @heading @anchor{m32c-x-elf}m32c-*-elf
3356 Renesas M32C processor.
3357 This configuration is intended for embedded systems.
3362 @heading @anchor{m32r-x-elf}m32r-*-elf
3363 Renesas M32R processor.
3364 This configuration is intended for embedded systems.
3369 @heading @anchor{m6811-elf}m6811-elf
3370 Motorola 68HC11 family micro controllers. These are used in embedded
3371 applications. There are no standard Unix configurations.
3376 @heading @anchor{m6812-elf}m6812-elf
3377 Motorola 68HC12 family micro controllers. These are used in embedded
3378 applications. There are no standard Unix configurations.
3383 @heading @anchor{m68k-x-x}m68k-*-*
3384 By default, @samp{m68k-*-aout}, @samp{m68k-*-coff*},
3385 @samp{m68k-*-elf*}, @samp{m68k-*-rtems} and @samp{m68k-*-uclinux}
3386 build libraries for both M680x0 and ColdFire processors. If you only
3387 need the M680x0 libraries, you can omit the ColdFire ones by passing
3388 @option{--with-arch=m68k} to @command{configure}. Alternatively, you
3389 can omit the M680x0 libraries by passing @option{--with-arch=cf} to
3390 @command{configure}. These targets default to 5206 code when
3391 configured with @option{--with-arch=cf} and 68020 code otherwise.
3393 The @samp{m68k-*-linux-gnu}, @samp{m68k-*-netbsd} and
3394 @samp{m68k-*-openbsd} targets also support the @option{--with-arch}
3395 option. They will generate ColdFire CFV4e code when configured with
3396 @option{--with-arch=cf} and 68020 code otherwise.
3398 You can override the default processors listed above by configuring
3399 with @option{--with-cpu=@var{target}}. This @var{target} can either
3400 be a @option{-mcpu} argument or one of the following values:
3401 @samp{m68000}, @samp{m68010}, @samp{m68020}, @samp{m68030},
3402 @samp{m68040}, @samp{m68060}, @samp{m68020-40} and @samp{m68020-60}.
3407 @heading @anchor{m68k-x-uclinux}m68k-*-uclinux
3408 GCC 4.3 changed the uClinux configuration so that it uses the
3409 @samp{m68k-linux-gnu} ABI rather than the @samp{m68k-elf} ABI.
3410 It also added improved support for C++ and flat shared libraries,
3411 both of which were ABI changes. However, you can still use the
3412 original ABI by configuring for @samp{m68k-uclinuxoldabi} or
3413 @samp{m68k-@var{vendor}-uclinuxoldabi}.
3418 @heading @anchor{mips-x-x}mips-*-*
3419 If on a MIPS system you get an error message saying ``does not have gp
3420 sections for all it's [sic] sectons [sic]'', don't worry about it. This
3421 happens whenever you use GAS with the MIPS linker, but there is not
3422 really anything wrong, and it is okay to use the output file. You can
3423 stop such warnings by installing the GNU linker.
3425 It would be nice to extend GAS to produce the gp tables, but they are
3426 optional, and there should not be a warning about their absence.
3428 The libstdc++ atomic locking routines for MIPS targets requires MIPS II
3429 and later. A patch went in just after the GCC 3.3 release to
3430 make @samp{mips*-*-*} use the generic implementation instead. You can also
3431 configure for @samp{mipsel-elf} as a workaround. The
3432 @samp{mips*-*-linux*} target continues to use the MIPS II routines. More
3433 work on this is expected in future releases.
3435 @c If you make --with-llsc the default for another target, please also
3436 @c update the description of the --with-llsc option.
3438 The built-in @code{__sync_*} functions are available on MIPS II and
3439 later systems and others that support the @samp{ll}, @samp{sc} and
3440 @samp{sync} instructions. This can be overridden by passing
3441 @option{--with-llsc} or @option{--without-llsc} when configuring GCC.
3442 Since the Linux kernel emulates these instructions if they are
3443 missing, the default for @samp{mips*-*-linux*} targets is
3444 @option{--with-llsc}. The @option{--with-llsc} and
3445 @option{--without-llsc} configure options may be overridden at compile
3446 time by passing the @option{-mllsc} or @option{-mno-llsc} options to
3449 MIPS systems check for division by zero (unless
3450 @option{-mno-check-zero-division} is passed to the compiler) by
3451 generating either a conditional trap or a break instruction. Using
3452 trap results in smaller code, but is only supported on MIPS II and
3453 later. Also, some versions of the Linux kernel have a bug that
3454 prevents trap from generating the proper signal (@code{SIGFPE}). To enable
3455 the use of break, use the @option{--with-divide=breaks}
3456 @command{configure} option when configuring GCC@. The default is to
3457 use traps on systems that support them.
3459 Cross-compilers for the MIPS as target using the MIPS assembler
3460 currently do not work, because the auxiliary programs
3461 @file{mips-tdump.c} and @file{mips-tfile.c} can't be compiled on
3462 anything but a MIPS@. It does work to cross compile for a MIPS
3463 if you use the GNU assembler and linker.
3465 The assembler from GNU binutils 2.17 and earlier has a bug in the way
3466 it sorts relocations for REL targets (o32, o64, EABI). This can cause
3467 bad code to be generated for simple C++ programs. Also the linker
3468 from GNU binutils versions prior to 2.17 has a bug which causes the
3469 runtime linker stubs in very large programs, like @file{libgcj.so}, to
3470 be incorrectly generated. GNU Binutils 2.18 and later (and snapshots
3471 made after Nov. 9, 2006) should be free from both of these problems.
3476 @heading @anchor{mips-sgi-irix5}mips-sgi-irix5
3478 In order to compile GCC on an SGI running IRIX 5, the @samp{compiler_dev.hdr}
3479 subsystem must be installed from the IDO CD-ROM supplied by SGI@.
3480 It is also available for download from
3481 @uref{ftp://ftp.sgi.com/sgi/IRIX5.3/iris-development-option-5.3.tardist}.
3483 If you use the MIPS C compiler to bootstrap, it may be necessary
3484 to increase its table size for switch statements with the
3485 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
3486 optimization option, you also need to use @option{-Olimit 3000}.
3488 To enable debugging under IRIX 5, you must use GNU binutils 2.15 or
3489 later, and use the @option{--with-gnu-ld} @command{configure} option
3490 when configuring GCC@. You need to use GNU @command{ar} and @command{nm},
3491 also distributed with GNU binutils.
3493 Some users have reported that @command{/bin/sh} will hang during bootstrap.
3494 This problem can be avoided by running the commands:
3497 % CONFIG_SHELL=/bin/ksh
3498 % export CONFIG_SHELL
3501 before starting the build.
3506 @heading @anchor{mips-sgi-irix6}mips-sgi-irix6
3508 If you are using SGI's MIPSpro @command{cc} as your bootstrap compiler, you must
3509 ensure that the N32 ABI is in use. To test this, compile a simple C
3510 file with @command{cc} and then run @command{file} on the
3511 resulting object file. The output should look like:
3514 test.o: ELF N32 MSB @dots{}
3520 test.o: ELF 32-bit MSB @dots{}
3526 test.o: ELF 64-bit MSB @dots{}
3529 then your version of @command{cc} uses the O32 or N64 ABI by default. You
3530 should set the environment variable @env{CC} to @samp{cc -n32}
3531 before configuring GCC@.
3533 If you want the resulting @command{gcc} to run on old 32-bit systems
3534 with the MIPS R4400 CPU, you need to ensure that only code for the @samp{mips3}
3535 instruction set architecture (ISA) is generated. While GCC 3.x does
3536 this correctly, both GCC 2.95 and SGI's MIPSpro @command{cc} may change
3537 the ISA depending on the machine where GCC is built. Using one of them
3538 as the bootstrap compiler may result in @samp{mips4} code, which won't run at
3539 all on @samp{mips3}-only systems. For the test program above, you should see:
3542 test.o: ELF N32 MSB mips-3 @dots{}
3548 test.o: ELF N32 MSB mips-4 @dots{}
3551 instead, you should set the environment variable @env{CC} to @samp{cc
3552 -n32 -mips3} or @samp{gcc -mips3} respectively before configuring GCC@.
3554 MIPSpro C 7.4 may cause bootstrap failures, due to a bug when inlining
3555 @code{memcmp}. Either add @code{-U__INLINE_INTRINSICS} to the @env{CC}
3556 environment variable as a workaround or upgrade to MIPSpro C 7.4.1m.
3558 GCC on IRIX 6 is usually built to support the N32, O32 and N64 ABIs. If
3559 you build GCC on a system that doesn't have the N64 libraries installed
3560 or cannot run 64-bit binaries,
3561 you need to configure with @option{--disable-multilib} so GCC doesn't
3562 try to use them. This will disable building the O32 libraries, too.
3563 Look for @file{/usr/lib64/libc.so.1} to see if you
3564 have the 64-bit libraries installed.
3566 To enable debugging for the O32 ABI, you must use GNU @command{as} from
3567 GNU binutils 2.15 or later. You may also use GNU @command{ld}, but
3568 this is not required and currently causes some problems with Ada.
3570 The @option{--enable-libgcj}
3571 option is disabled by default: IRIX 6 uses a very low default limit
3572 (20480) for the command line length. Although @command{libtool} contains a
3573 workaround for this problem, at least the N64 @samp{libgcj} is known not
3574 to build despite this, running into an internal error of the native
3575 @command{ld}. A sure fix is to increase this limit (@samp{ncargs}) to
3576 its maximum of 262144 bytes. If you have root access, you can use the
3577 @command{systune} command to do this.
3579 @code{wchar_t} support in @samp{libstdc++} is not available for old
3580 IRIX 6.5.x releases, @math{x < 19}. The problem cannot be autodetected
3581 and in order to build GCC for such targets you need to configure with
3582 @option{--disable-wchar_t}.
3584 See @uref{http://freeware.sgi.com/} for more
3585 information about using GCC on IRIX platforms.
3590 @heading @anchor{powerpc-x-x}powerpc-*-*
3592 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
3593 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
3598 @heading @anchor{powerpc-x-darwin}powerpc-*-darwin*
3599 PowerPC running Darwin (Mac OS X kernel).
3601 Pre-installed versions of Mac OS X may not include any developer tools,
3602 meaning that you will not be able to build GCC from source. Tool
3603 binaries are available at
3604 @uref{http://developer.apple.com/darwin/projects/compiler/} (free
3605 registration required).
3607 This version of GCC requires at least cctools-590.36. The
3608 cctools-590.36 package referenced from
3609 @uref{http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html} will not work
3610 on systems older than 10.3.9 (aka darwin7.9.0).
3615 @heading @anchor{powerpc-x-elf}powerpc-*-elf
3616 PowerPC system in big endian mode, running System V.4.
3621 @heading @anchor{powerpc-x-linux-gnu}powerpc*-*-linux-gnu*
3624 @uref{ftp://ftp.kernel.org/pub/linux/devel/binutils,,binutils 2.15}
3625 or newer for a working GCC@.
3630 @heading @anchor{powerpc-x-netbsd}powerpc-*-netbsd*
3631 PowerPC system in big endian mode running NetBSD@. To build the
3632 documentation you will need Texinfo version 4.4 (NetBSD 1.5.1 included
3633 Texinfo version 3.12).
3638 @heading @anchor{powerpc-x-eabisim}powerpc-*-eabisim
3639 Embedded PowerPC system in big endian mode for use in running under the
3645 @heading @anchor{powerpc-x-eabi}powerpc-*-eabi
3646 Embedded PowerPC system in big endian mode.
3651 @heading @anchor{powerpcle-x-elf}powerpcle-*-elf
3652 PowerPC system in little endian mode, running System V.4.
3657 @heading @anchor{powerpcle-x-eabisim}powerpcle-*-eabisim
3658 Embedded PowerPC system in little endian mode for use in running under
3664 @heading @anchor{powerpcle-x-eabi}powerpcle-*-eabi
3665 Embedded PowerPC system in little endian mode.
3670 @heading @anchor{s390-x-linux}s390-*-linux*
3671 S/390 system running GNU/Linux for S/390@.
3676 @heading @anchor{s390x-x-linux}s390x-*-linux*
3677 zSeries system (64-bit) running GNU/Linux for zSeries@.
3682 @heading @anchor{s390x-ibm-tpf}s390x-ibm-tpf*
3683 zSeries system (64-bit) running TPF@. This platform is
3684 supported as cross-compilation target only.
3689 @c Please use Solaris 2 to refer to all release of Solaris, starting
3690 @c with 2.0 until 2.6, 7, 8, etc. Solaris 1 was a marketing name for
3691 @c SunOS 4 releases which we don't use to avoid confusion. Solaris
3692 @c alone is too unspecific and must be avoided.
3693 @heading @anchor{x-x-solaris2}*-*-solaris2*
3695 Sun does not ship a C compiler with Solaris 2. To bootstrap and install
3696 GCC you first have to install a pre-built compiler, see the
3697 @uref{binaries.html,,binaries page} for details.
3699 The Solaris 2 @command{/bin/sh} will often fail to configure
3700 @file{libstdc++-v3}, @file{boehm-gc} or @file{libjava}. We therefore
3701 recommend using the following initial sequence of commands
3704 % CONFIG_SHELL=/bin/ksh
3705 % export CONFIG_SHELL
3708 and proceed as described in @uref{configure.html,,the configure instructions}.
3709 In addition we strongly recommend specifying an absolute path to invoke
3710 @var{srcdir}/configure.
3712 Solaris 2 comes with a number of optional OS packages. Some of these
3713 are needed to use GCC fully, namely @code{SUNWarc},
3714 @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
3715 @code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all
3716 optional packages when installing Solaris 2, you will need to verify that
3717 the packages that GCC needs are installed.
3719 To check whether an optional package is installed, use
3720 the @command{pkginfo} command. To add an optional package, use the
3721 @command{pkgadd} command. For further details, see the Solaris 2
3724 Trying to use the linker and other tools in
3725 @file{/usr/ucb} to install GCC has been observed to cause trouble.
3726 For example, the linker may hang indefinitely. The fix is to remove
3727 @file{/usr/ucb} from your @env{PATH}.
3729 The build process works more smoothly with the legacy Sun tools so, if you
3730 have @file{/usr/xpg4/bin} in your @env{PATH}, we recommend that you place
3731 @file{/usr/bin} before @file{/usr/xpg4/bin} for the duration of the build.
3733 We recommend the use of GNU binutils 2.14 or later, or the vendor tools
3734 (Sun @command{as}, Sun @command{ld}). Note that your mileage may vary
3735 if you use a combination of the GNU tools and the Sun tools: while the
3736 combination GNU @command{as} + Sun @command{ld} should reasonably work,
3737 the reverse combination Sun @command{as} + GNU @command{ld} is known to
3738 cause memory corruption at runtime in some cases for C++ programs.
3740 The stock GNU binutils 2.15 release is broken on this platform because of a
3741 single bug. It has been fixed on the 2.15 branch in the CVS repository.
3742 You can obtain a working version by checking out the binutils-2_15-branch
3743 from the CVS repository or applying the patch
3744 @uref{http://sourceware.org/ml/binutils-cvs/2004-09/msg00036.html} to the
3747 We recommend the use of GNU binutils 2.16 or later in conjunction with GCC
3748 4.x, or the vendor tools (Sun @command{as}, Sun @command{ld}). However,
3749 for Solaris 10 and above, an additional patch is required in order for the
3750 GNU linker to be able to cope with a new flavor of shared libraries. You
3751 can obtain a working version by checking out the binutils-2_16-branch from
3752 the CVS repository or applying the patch
3753 @uref{http://sourceware.org/ml/binutils-cvs/2005-07/msg00122.html} to the
3756 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
3757 newer: @command{g++} will complain that types are missing. These headers
3758 assume that omitting the type means @code{int}; this assumption worked for
3759 C89 but is wrong for C++, and is now wrong for C99 also.
3761 @command{g++} accepts such (invalid) constructs with the option
3762 @option{-fpermissive}; it will assume that any missing type is @code{int}
3763 (as defined by C89).
3765 There are patches for Solaris 7 (108376-21 or newer for SPARC,
3766 108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC,
3767 108653-22 for Intel) that fix this bug.
3769 Sun bug 4927647 sometimes causes random spurious testsuite failures
3770 related to missing diagnostic output. This bug doesn't affect GCC
3771 itself, rather it is a kernel bug triggered by the @command{expect}
3772 program which is used only by the GCC testsuite driver. When the bug
3773 causes the @command{expect} program to miss anticipated output, extra
3774 testsuite failures appear.
3776 There are patches for Solaris 8 (117350-12 or newer for SPARC,
3777 117351-12 or newer for Intel) and Solaris 9 (117171-11 or newer for
3778 SPARC, 117172-11 or newer for Intel) that address this problem.
3783 @heading @anchor{sparc-sun-solaris2}sparc-sun-solaris2*
3785 When GCC is configured to use binutils 2.14 or later the binaries
3786 produced are smaller than the ones produced using Sun's native tools;
3787 this difference is quite significant for binaries containing debugging
3790 Starting with Solaris 7, the operating system is capable of executing
3791 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
3792 this; the @option{-m64} option enables 64-bit code generation.
3793 However, if all you want is code tuned for the UltraSPARC CPU, you
3794 should try the @option{-mtune=ultrasparc} option instead, which produces
3795 code that, unlike full 64-bit code, can still run on non-UltraSPARC
3798 When configuring on a Solaris 7 or later system that is running a kernel
3799 that supports only 32-bit binaries, one must configure with
3800 @option{--disable-multilib}, since we will not be able to build the
3801 64-bit target libraries.
3803 GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of
3804 the GNU compiler (especially GCC 3.0.x versions), which lead to the
3805 miscompilation of the stage1 compiler and the subsequent failure of the
3806 bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary
3807 stage, i.e.@: to bootstrap that compiler with the base compiler and then
3808 use it to bootstrap the final compiler.
3810 GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE Studio 7)
3811 and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a bootstrap
3812 failure in form of a miscompilation of the stage1 compiler by the Sun
3813 compiler. This is Sun bug 4974440. This is fixed with patch 112760-07.
3815 GCC 3.4 changed the default debugging format from STABS to DWARF-2 for
3816 32-bit code on Solaris 7 and later. If you use the Sun assembler, this
3817 change apparently runs afoul of Sun bug 4910101 (which is referenced as
3818 a x86-only problem by Sun, probably because they do not use DWARF-2).
3819 A symptom of the problem is that you cannot compile C++ programs like
3820 @command{groff} 1.19.1 without getting messages similar to the following:
3823 ld: warning: relocation error: R_SPARC_UA32: @dots{}
3824 external symbolic relocation against non-allocatable section
3825 .debug_info cannot be processed at runtime: relocation ignored.
3828 To work around this problem, compile with @option{-gstabs+} instead of
3831 When configuring the GNU Multiple Precision Library (GMP) or the MPFR
3832 library on a Solaris 7 or later system, the canonical target triplet
3833 must be specified as the @command{build} parameter on the configure
3834 line. This triplet can be obtained by invoking ./config.guess in
3835 the toplevel source directory of GCC (and not that of GMP or MPFR).
3836 For example on a Solaris 7 system:
3839 % ./configure --build=sparc-sun-solaris2.7 --prefix=xxx
3845 @heading @anchor{sparc-sun-solaris27}sparc-sun-solaris2.7
3847 Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in
3848 the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8
3849 and later, including all EGCS releases. Sun formerly recommended
3850 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to
3851 recommend it only for people who use Sun's compilers.
3853 Here are some workarounds to this problem:
3856 Do not install Sun patch 107058-01 until after Sun releases a
3857 complete patch for bug 4210064. This is the simplest course to take,
3858 unless you must also use Sun's C compiler. Unfortunately 107058-01
3859 is preinstalled on some new Solaris 7-based hosts, so you may have to
3863 Copy the original, unpatched Solaris 7
3864 @command{/usr/ccs/bin/as} into
3865 @command{/usr/local/libexec/gcc/sparc-sun-solaris2.7/3.4/as},
3866 adjusting the latter name to fit your local conventions and software
3870 Install Sun patch 106950-03 (1999-05-25) or later. Nobody with
3871 both 107058-01 and 106950-03 installed has reported the bug with GCC
3872 and Sun's dynamic linker. This last course of action is riskiest,
3873 for two reasons. First, you must install 106950 on all hosts that
3874 run code generated by GCC; it doesn't suffice to install it only on
3875 the hosts that run GCC itself. Second, Sun says that 106950-03 is
3876 only a partial fix for bug 4210064, but Sun doesn't know whether the
3877 partial fix is adequate for GCC@. Revision -08 or later should fix
3878 the bug. The current (as of 2004-05-23) revision is -24, and is included in
3879 the Solaris 7 Recommended Patch Cluster.
3882 GCC 3.3 triggers a bug in version 5.0 Alpha 03/27/98 of the Sun assembler,
3883 which causes a bootstrap failure when linking the 64-bit shared version of
3884 libgcc. A typical error message is:
3887 ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o:
3888 symbol <unknown>: offset 0xffffffff7ec133e7 is non-aligned.
3891 This bug has been fixed in the final 5.0 version of the assembler.
3893 A similar problem was reported for version Sun WorkShop 6 99/08/18 of the
3894 Sun assembler, which causes a bootstrap failure with GCC 4.0.0:
3897 ld: fatal: relocation error: R_SPARC_DISP32:
3898 file .libs/libstdc++.lax/libsupc++convenience.a/vterminate.o:
3899 symbol <unknown>: offset 0xfccd33ad is non-aligned
3902 This bug has been fixed in more recent revisions of the assembler.
3907 @heading @anchor{sparc-x-linux}sparc-*-linux*
3909 GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
3910 or newer on this platform. All earlier binutils and glibc
3911 releases mishandled unaligned relocations on @code{sparc-*-*} targets.
3917 @heading @anchor{sparc64-x-solaris2}sparc64-*-solaris2*
3919 When configuring the GNU Multiple Precision Library (GMP) or the
3920 MPFR library, the canonical target triplet must be specified as
3921 the @command{build} parameter on the configure line. For example
3922 on a Solaris 7 system:
3925 % ./configure --build=sparc64-sun-solaris2.7 --prefix=xxx
3928 The following compiler flags must be specified in the configure
3929 step in order to bootstrap this target with the Sun compiler:
3932 % CC="cc -xarch=v9 -xildoff" @var{srcdir}/configure [@var{options}] [@var{target}]
3935 @option{-xarch=v9} specifies the SPARC-V9 architecture to the Sun toolchain
3936 and @option{-xildoff} turns off the incremental linker.
3941 @heading @anchor{sparcv9-x-solaris2}sparcv9-*-solaris2*
3943 This is a synonym for sparc64-*-solaris2*.
3948 @heading @anchor{x-x-vxworks}*-*-vxworks*
3949 Support for VxWorks is in flux. At present GCC supports @emph{only} the
3950 very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC@.
3951 We welcome patches for other architectures supported by VxWorks 5.5.
3952 Support for VxWorks AE would also be welcome; we believe this is merely
3953 a matter of writing an appropriate ``configlette'' (see below). We are
3954 not interested in supporting older, a.out or COFF-based, versions of
3957 VxWorks comes with an older version of GCC installed in
3958 @file{@var{$WIND_BASE}/host}; we recommend you do not overwrite it.
3959 Choose an installation @var{prefix} entirely outside @var{$WIND_BASE}.
3960 Before running @command{configure}, create the directories @file{@var{prefix}}
3961 and @file{@var{prefix}/bin}. Link or copy the appropriate assembler,
3962 linker, etc.@: into @file{@var{prefix}/bin}, and set your @var{PATH} to
3963 include that directory while running both @command{configure} and
3966 You must give @command{configure} the
3967 @option{--with-headers=@var{$WIND_BASE}/target/h} switch so that it can
3968 find the VxWorks system headers. Since VxWorks is a cross compilation
3969 target only, you must also specify @option{--target=@var{target}}.
3970 @command{configure} will attempt to create the directory
3971 @file{@var{prefix}/@var{target}/sys-include} and copy files into it;
3972 make sure the user running @command{configure} has sufficient privilege
3975 GCC's exception handling runtime requires a special ``configlette''
3976 module, @file{contrib/gthr_supp_vxw_5x.c}. Follow the instructions in
3977 that file to add the module to your kernel build. (Future versions of
3978 VxWorks will incorporate this module.)
3983 @heading @anchor{x86-64-x-x}x86_64-*-*, amd64-*-*
3985 GCC supports the x86-64 architecture implemented by the AMD64 processor
3986 (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD@.
3987 On GNU/Linux the default is a bi-arch compiler which is able to generate
3988 both 64-bit x86-64 and 32-bit x86 code (via the @option{-m32} switch).
3993 @heading @anchor{xtensa-x-elf}xtensa-*-elf
3995 This target is intended for embedded Xtensa systems using the
3996 @samp{newlib} C library. It uses ELF but does not support shared
3997 objects. Designed-defined instructions specified via the
3998 Tensilica Instruction Extension (TIE) language are only supported
3999 through inline assembly.
4001 The Xtensa configuration information must be specified prior to
4002 building GCC@. The @file{include/xtensa-config.h} header
4003 file contains the configuration information. If you created your
4004 own Xtensa configuration with the Xtensa Processor Generator, the
4005 downloaded files include a customized copy of this header file,
4006 which you can use to replace the default header file.
4011 @heading @anchor{xtensa-x-linux}xtensa-*-linux*
4013 This target is for Xtensa systems running GNU/Linux. It supports ELF
4014 shared objects and the GNU C library (glibc). It also generates
4015 position-independent code (PIC) regardless of whether the
4016 @option{-fpic} or @option{-fPIC} options are used. In other
4017 respects, this target is the same as the
4018 @uref{#xtensa-*-elf,,@samp{xtensa-*-elf}} target.
4023 @heading @anchor{windows}Microsoft Windows (32-bit)
4025 Ports of GCC are included with the
4026 @uref{http://www.cygwin.com/,,Cygwin environment}.
4028 GCC will build under Cygwin without modification; it does not build
4029 with Microsoft's C++ compiler and there are no plans to make it do so.
4031 For MinGW, GCC will build with and support only MinGW runtime 3.12 and later.
4032 Earlier versions of headers are incompatible with the new default semantics
4033 of @code{extern inline} in @code{-std=c99} and @code{-std=gnu99} modes.
4038 @heading @anchor{os2}OS/2
4040 GCC does not currently support OS/2. However, Andrew Zabolotny has been
4041 working on a generic OS/2 port with pgcc. The current code can be found
4042 at @uref{http://www.goof.com/pcg/os2/,,http://www.goof.com/pcg/os2/}.
4047 @heading @anchor{older}Older systems
4049 GCC contains support files for many older (1980s and early
4050 1990s) Unix variants. For the most part, support for these systems
4051 has not been deliberately removed, but it has not been maintained for
4052 several years and may suffer from bitrot.
4054 Starting with GCC 3.1, each release has a list of ``obsoleted'' systems.
4055 Support for these systems is still present in that release, but
4056 @command{configure} will fail unless the @option{--enable-obsolete}
4057 option is given. Unless a maintainer steps forward, support for these
4058 systems will be removed from the next release of GCC@.
4060 Support for old systems as hosts for GCC can cause problems if the
4061 workarounds for compiler, library and operating system bugs affect the
4062 cleanliness or maintainability of the rest of GCC@. In some cases, to
4063 bring GCC up on such a system, if still possible with current GCC, may
4064 require first installing an old version of GCC which did work on that
4065 system, and using it to compile a more recent GCC, to avoid bugs in the
4066 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
4067 @file{old-releases} directory on the @uref{../mirrors.html,,GCC mirror
4068 sites}. Header bugs may generally be avoided using
4069 @command{fixincludes}, but bugs or deficiencies in libraries and the
4070 operating system may still cause problems.
4072 Support for older systems as targets for cross-compilation is less
4073 problematic than support for them as hosts for GCC; if an enthusiast
4074 wishes to make such a target work again (including resurrecting any of
4075 the targets that never worked with GCC 2, starting from the last
4076 version before they were removed), patches
4077 @uref{../contribute.html,,following the usual requirements} would be
4078 likely to be accepted, since they should not affect the support for more
4081 For some systems, old versions of GNU binutils may also be useful,
4082 and are available from @file{pub/binutils/old-releases} on
4083 @uref{http://sourceware.org/mirrors.html,,sourceware.org mirror sites}.
4085 Some of the information on specific systems above relates to
4086 such older systems, but much of the information
4087 about GCC on such systems (which may no longer be applicable to
4088 current GCC) is to be found in the GCC texinfo manual.
4093 @heading @anchor{elf}all ELF targets (SVR4, Solaris 2, etc.)
4095 C++ support is significantly better on ELF targets if you use the
4096 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
4097 inlines, vtables and template instantiations will be discarded
4106 @uref{./index.html,,Return to the GCC Installation page}
4110 @c ***Old documentation******************************************************
4112 @include install-old.texi
4118 @uref{./index.html,,Return to the GCC Installation page}
4122 @c ***GFDL********************************************************************
4130 @uref{./index.html,,Return to the GCC Installation page}
4134 @c ***************************************************************************
4135 @c Part 6 The End of the Document
4137 @comment node-name, next, previous, up
4138 @node Concept Index, , GNU Free Documentation License, Top
4142 @unnumbered Concept Index