1 \input texinfo.tex @c -*-texinfo-*-
4 @setfilename gccinstall.info
5 @settitle Installing GCC
10 @c Specify title for specific html page
12 @settitle Installing GCC
15 @settitle Host/Target specific installation notes for GCC
17 @ifset prerequisiteshtml
18 @settitle Prerequisites for GCC
21 @settitle Downloading GCC
24 @settitle Installing GCC: Configuration
27 @settitle Installing GCC: Building
30 @settitle Installing GCC: Testing
32 @ifset finalinstallhtml
33 @settitle Installing GCC: Final installation
36 @settitle Installing GCC: Binaries
39 @settitle Installing GCC: Old documentation
42 @settitle Installing GCC: GNU Free Documentation License
45 @c Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
46 @c 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc.
47 @c *** Converted to texinfo by Dean Wakerley, dean@wakerley.com
49 @c IMPORTANT: whenever you modify this file, run `install.texi2html' to
50 @c test the generation of HTML documents for the gcc.gnu.org web pages.
52 @c Do not use @footnote{} in this file as it breaks install.texi2html!
54 @c Include everything if we're not making html
58 @set prerequisiteshtml
69 @c Part 2 Summary Description and Copyright
71 Copyright @copyright{} 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
72 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc.
74 Permission is granted to copy, distribute and/or modify this document
75 under the terms of the GNU Free Documentation License, Version 1.2 or
76 any later version published by the Free Software Foundation; with no
77 Invariant Sections, the Front-Cover texts being (a) (see below), and
78 with the Back-Cover Texts being (b) (see below). A copy of the
79 license is included in the section entitled ``@uref{./gfdl.html,,GNU
80 Free Documentation License}''.
82 (a) The FSF's Front-Cover Text is:
86 (b) The FSF's Back-Cover Text is:
88 You have freedom to copy and modify this GNU Manual, like GNU
89 software. Copies published by the Free Software Foundation raise
90 funds for GNU development.
95 @dircategory Software development
97 * gccinstall: (gccinstall). Installing the GNU Compiler Collection.
100 @c Part 3 Titlepage and Copyright
103 @comment The title is printed in a large font.
104 @center @titlefont{Installing GCC}
106 @c The following two commands start the copyright page.
108 @vskip 0pt plus 1filll
112 @c Part 4 Top node and Master Menu
115 @comment node-name, next, Previous, up
118 * Installing GCC:: This document describes the generic installation
119 procedure for GCC as well as detailing some target
120 specific installation instructions.
122 * Specific:: Host/target specific installation notes for GCC.
123 * Binaries:: Where to get pre-compiled binaries.
125 * Old:: Old installation documentation.
127 * GNU Free Documentation License:: How you can copy and share this manual.
128 * Concept Index:: This index has two entries.
132 @c Part 5 The Body of the Document
133 @c ***Installing GCC**********************************************************
135 @comment node-name, next, previous, up
136 @node Installing GCC, Binaries, , Top
140 @chapter Installing GCC
143 The latest version of this document is always available at
144 @uref{http://gcc.gnu.org/install/,,http://gcc.gnu.org/install/}.
146 This document describes the generic installation procedure for GCC as well
147 as detailing some target specific installation instructions.
149 GCC includes several components that previously were separate distributions
150 with their own installation instructions. This document supersedes all
151 package specific installation instructions.
153 @emph{Before} starting the build/install procedure please check the
155 @ref{Specific, host/target specific installation notes}.
158 @uref{specific.html,,host/target specific installation notes}.
160 We recommend you browse the entire generic installation instructions before
163 Lists of successful builds for released versions of GCC are
164 available at @uref{http://gcc.gnu.org/buildstat.html}.
165 These lists are updated as new information becomes available.
167 The installation procedure itself is broken into five steps.
172 * Downloading the source::
175 * Testing:: (optional)
182 @uref{prerequisites.html,,Prerequisites}
184 @uref{download.html,,Downloading the source}
186 @uref{configure.html,,Configuration}
188 @uref{build.html,,Building}
190 @uref{test.html,,Testing} (optional)
192 @uref{finalinstall.html,,Final install}
196 Please note that GCC does not support @samp{make uninstall} and probably
197 won't do so in the near future as this would open a can of worms. Instead,
198 we suggest that you install GCC into a directory of its own and simply
199 remove that directory when you do not need that specific version of GCC
200 any longer, and, if shared libraries are installed there as well, no
201 more binaries exist that use them.
204 There are also some @uref{old.html,,old installation instructions},
205 which are mostly obsolete but still contain some information which has
206 not yet been merged into the main part of this manual.
214 @uref{./index.html,,Return to the GCC Installation page}
220 @c ***Prerequisites**************************************************
222 @comment node-name, next, previous, up
223 @node Prerequisites, Downloading the source, , Installing GCC
225 @ifset prerequisiteshtml
227 @chapter Prerequisites
229 @cindex Prerequisites
231 GCC requires that various tools and packages be available for use in the
232 build procedure. Modifying GCC sources requires additional tools
235 @heading Tools/packages necessary for building GCC
237 @item ISO C90 compiler
238 Necessary to bootstrap GCC, although versions of GCC prior
239 to 3.4 also allow bootstrapping with a traditional (K&R) C compiler.
241 To build all languages in a cross-compiler or other configuration where
242 3-stage bootstrap is not performed, you need to start with an existing
243 GCC binary (version 2.95 or later) because source code for language
244 frontends other than C might use GCC extensions.
248 In order to build the Ada compiler (GNAT) you must already have GNAT
249 installed because portions of the Ada frontend are written in Ada (with
250 GNAT extensions.) Refer to the Ada installation instructions for more
251 specific information.
253 @item A ``working'' POSIX compatible shell, or GNU bash
255 Necessary when running @command{configure} because some
256 @command{/bin/sh} shells have bugs and may crash when configuring the
257 target libraries. In other cases, @command{/bin/sh} or @command{ksh}
258 have disastrous corner-case performance problems. This
259 can cause target @command{configure} runs to literally take days to
260 complete in some cases.
262 So on some platforms @command{/bin/ksh} is sufficient, on others it
263 isn't. See the host/target specific instructions for your platform, or
264 use @command{bash} to be sure. Then set @env{CONFIG_SHELL} in your
265 environment to your ``good'' shell prior to running
266 @command{configure}/@command{make}.
268 @command{zsh} is not a fully compliant POSIX shell and will not
269 work when configuring GCC@.
273 Necessary in some circumstances, optional in others. See the
274 host/target specific instructions for your platform for the exact
277 @item gzip version 1.2.4 (or later) or
278 @itemx bzip2 version 1.0.2 (or later)
280 Necessary to uncompress GCC @command{tar} files when source code is
281 obtained via FTP mirror sites.
283 @item GNU make version 3.79.1 (or later)
285 You must have GNU make installed to build GCC@.
287 @item GNU tar version 1.14 (or later)
289 Necessary (only on some platforms) to untar the source code. Many
290 systems' @command{tar} programs will also work, only try GNU
291 @command{tar} if you have problems.
293 @item GNU Multiple Precision Library (GMP) version 4.1 (or later)
295 Necessary to build the Fortran frontend. If you do not have it
296 installed in your library search path, you will have to configure with
297 the @option{--with-gmp} or @option{--with-gmp-dir} configure option.
299 @item MPFR Library version 2.2 (or later)
301 Necessary to build the Fortran frontend. It can be downloaded from
302 @uref{http://www.mpfr.org/}. The version of MPFR that is bundled with
303 GMP 4.1.x contains numerous bugs. Although GNU Fortran will appear
304 to function with the buggy versions of MPFR, there are a few GNU Fortran
305 bugs that will not be fixed when using this version. It is strongly
306 recommended to upgrade to at least MPFR version 2.2.
308 The @option{--with-mpfr} or @option{--with-mpfr-dir} configure option should
309 be used if your MPFR Library is not installed in your library search path.
311 @item @command{jar}, or InfoZIP (@command{zip} and @command{unzip})
313 Necessary to build libgcj, the GCJ runtime.
318 @heading Tools/packages necessary for modifying GCC
320 @item autoconf versions 2.13 and 2.59
321 @itemx GNU m4 version 1.4 (or later)
323 Necessary when modifying @file{configure.ac}, @file{aclocal.m4}, etc.@:
324 to regenerate @file{configure} and @file{config.in} files. Most
325 directories require autoconf 2.59 (exactly), but the toplevel
326 still requires autoconf 2.13 (exactly).
328 @item automake versions 1.9.3
330 Necessary when modifying a @file{Makefile.am} file to regenerate its
331 associated @file{Makefile.in}.
333 Much of GCC does not use automake, so directly edit the @file{Makefile.in}
334 file. Specifically this applies to the @file{gcc}, @file{intl},
335 @file{libcpp}, @file{libiberty}, @file{libobjc} directories as well
336 as any of their subdirectories.
338 For directories that use automake, GCC requires the latest release in
339 the 1.9.x series, which is currently 1.9.3. When regenerating a directory
340 to a newer version, please update all the directories using an older 1.9.x
341 to the latest released version.
343 @item gettext version 0.14.5 (or later)
345 Needed to regenerate @file{gcc.pot}.
347 @item gperf version 2.7.2 (or later)
349 Necessary when modifying @command{gperf} input files, e.g.@:
350 @file{gcc/cp/cfns.gperf} to regenerate its associated header file, e.g.@:
351 @file{gcc/cp/cfns.h}.
357 Necessary to run the GCC testsuite; see the section on testing for details.
359 @item autogen version 5.5.4 (or later) and
360 @itemx guile version 1.4.1 (or later)
362 Necessary to regenerate @file{fixinc/fixincl.x} from
363 @file{fixinc/inclhack.def} and @file{fixinc/*.tpl}.
365 Necessary to run @samp{make check} for @file{fixinc}.
367 Necessary to regenerate the top level @file{Makefile.in} file from
368 @file{Makefile.tpl} and @file{Makefile.def}.
370 @item GNU Bison version 1.28 (or later)
371 Berkeley @command{yacc} (@command{byacc}) is also reported to work other
374 Necessary when modifying @file{*.y} files.
376 Necessary to build GCC during development because the generated output
377 files are not included in the SVN repository. They are included in
380 @item Flex version 2.5.4 (or later)
382 Necessary when modifying @file{*.l} files.
384 Necessary to build GCC during development because the generated output
385 files are not included in the SVN repository. They are included in
388 @item Texinfo version 4.4 (or later)
390 Necessary for running @command{makeinfo} when modifying @file{*.texi}
391 files to test your changes.
393 Necessary for running @command{make dvi} or @command{make pdf} to
394 create printable documentation in DVI or PDF format. Texinfo version
395 4.8 or later is required for @command{make pdf}.
397 Necessary to build GCC documentation during development because the
398 generated output files are not included in the SVN repository. They are
399 included in releases.
401 @item @TeX{} (any working version)
403 Necessary for running @command{texi2dvi} and @command{texi2pdf}, which
404 are used when running @command{make dvi} or @command{make pdf} to create
405 DVI or PDF files, respectively.
407 @item SVN (any version)
408 @itemx SSH (any version)
410 Necessary to access the SVN repository. Public releases and weekly
411 snapshots of the development sources are also available via FTP@.
413 @item Perl version 5.6.1 (or later)
415 Necessary when regenerating @file{Makefile} dependencies in libiberty.
416 Necessary when regenerating @file{libiberty/functions.texi}.
417 Necessary when generating manpages from Texinfo manuals.
418 Necessary when targetting Darwin, building libstdc++,
419 and not using @option{--disable-symvers}.
420 Used by various scripts to generate some files included in SVN (mainly
421 Unicode-related and rarely changing) from source tables.
423 @item GNU diffutils version 2.7 (or later)
425 Useful when submitting patches for the GCC source code.
427 @item patch version 2.5.4 (or later)
429 Necessary when applying patches, created with @command{diff}, to one's
439 @uref{./index.html,,Return to the GCC Installation page}
443 @c ***Downloading the source**************************************************
445 @comment node-name, next, previous, up
446 @node Downloading the source, Configuration, Prerequisites, Installing GCC
450 @chapter Downloading GCC
452 @cindex Downloading GCC
453 @cindex Downloading the Source
455 GCC is distributed via @uref{http://gcc.gnu.org/svn.html,,SVN} and FTP
456 tarballs compressed with @command{gzip} or
457 @command{bzip2}. It is possible to download a full distribution or specific
460 Please refer to the @uref{http://gcc.gnu.org/releases.html,,releases web page}
461 for information on how to obtain GCC@.
463 The full distribution includes the C, C++, Objective-C, Fortran 77, Fortran
464 (in case of GCC 4.0 and later), Java, and Ada (in case of GCC 3.1 and later)
465 compilers. The full distribution also includes runtime libraries for C++,
466 Objective-C, Fortran 77, Fortran, and Java. In GCC 3.0 and later versions,
467 GNU compiler testsuites are also included in the full distribution.
469 If you choose to download specific components, you must download the core
470 GCC distribution plus any language specific distributions you wish to
471 use. The core distribution includes the C language front end as well as the
472 shared components. Each language has a tarball which includes the language
473 front end as well as the language runtime (when appropriate).
475 Unpack the core distribution as well as any language specific
476 distributions in the same directory.
478 If you also intend to build binutils (either to upgrade an existing
479 installation or for use in place of the corresponding tools of your
480 OS), unpack the binutils distribution either in the same directory or
481 a separate one. In the latter case, add symbolic links to any
482 components of the binutils you intend to build alongside the compiler
483 (@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld},
484 @file{opcodes}, @dots{}) to the directory containing the GCC sources.
491 @uref{./index.html,,Return to the GCC Installation page}
495 @c ***Configuration***********************************************************
497 @comment node-name, next, previous, up
498 @node Configuration, Building, Downloading the source, Installing GCC
502 @chapter Installing GCC: Configuration
504 @cindex Configuration
505 @cindex Installing GCC: Configuration
507 Like most GNU software, GCC must be configured before it can be built.
508 This document describes the recommended configuration procedure
509 for both native and cross targets.
511 We use @var{srcdir} to refer to the toplevel source directory for
512 GCC; we use @var{objdir} to refer to the toplevel build/object directory.
514 If you obtained the sources via SVN, @var{srcdir} must refer to the top
515 @file{gcc} directory, the one where the @file{MAINTAINERS} can be found,
516 and not its @file{gcc} subdirectory, otherwise the build will fail.
518 If either @var{srcdir} or @var{objdir} is located on an automounted NFS
519 file system, the shell's built-in @command{pwd} command will return
520 temporary pathnames. Using these can lead to various sorts of build
521 problems. To avoid this issue, set the @env{PWDCMD} environment
522 variable to an automounter-aware @command{pwd} command, e.g.,
523 @command{pawd} or @samp{amq -w}, during the configuration and build
526 First, we @strong{highly} recommend that GCC be built into a
527 separate directory than the sources which does @strong{not} reside
528 within the source tree. This is how we generally build GCC; building
529 where @var{srcdir} == @var{objdir} should still work, but doesn't
530 get extensive testing; building where @var{objdir} is a subdirectory
531 of @var{srcdir} is unsupported.
533 If you have previously built GCC in the same directory for a
534 different target machine, do @samp{make distclean} to delete all files
535 that might be invalid. One of the files this deletes is @file{Makefile};
536 if @samp{make distclean} complains that @file{Makefile} does not exist
537 or issues a message like ``don't know how to make distclean'' it probably
538 means that the directory is already suitably clean. However, with the
539 recommended method of building in a separate @var{objdir}, you should
540 simply use a different @var{objdir} for each target.
542 Second, when configuring a native system, either @command{cc} or
543 @command{gcc} must be in your path or you must set @env{CC} in
544 your environment before running configure. Otherwise the configuration
548 Note that the bootstrap compiler and the resulting GCC must be link
549 compatible, else the bootstrap will fail with linker errors about
550 incompatible object file formats. Several multilibed targets are
551 affected by this requirement, see
553 @ref{Specific, host/target specific installation notes}.
556 @uref{specific.html,,host/target specific installation notes}.
565 % @var{srcdir}/configure [@var{options}] [@var{target}]
569 @heading Target specification
572 GCC has code to correctly determine the correct value for @var{target}
573 for nearly all native systems. Therefore, we highly recommend you not
574 provide a configure target when configuring a native compiler.
577 @var{target} must be specified as @option{--target=@var{target}}
578 when configuring a cross compiler; examples of valid targets would be
579 m68k-coff, sh-elf, etc.
582 Specifying just @var{target} instead of @option{--target=@var{target}}
583 implies that the host defaults to @var{target}.
587 @heading Options specification
589 Use @var{options} to override several configure time options for
590 GCC@. A list of supported @var{options} follows; @samp{configure
591 --help} may list other options, but those not listed below may not
592 work and should not normally be used.
594 Note that each @option{--enable} option has a corresponding
595 @option{--disable} option and that each @option{--with} option has a
596 corresponding @option{--without} option.
599 @item --prefix=@var{dirname}
600 Specify the toplevel installation
601 directory. This is the recommended way to install the tools into a directory
602 other than the default. The toplevel installation directory defaults to
605 We @strong{highly} recommend against @var{dirname} being the same or a
606 subdirectory of @var{objdir} or vice versa. If specifying a directory
607 beneath a user's home directory tree, some shells will not expand
608 @var{dirname} correctly if it contains the @samp{~} metacharacter; use
611 The following standard @command{autoconf} options are supported. Normally you
612 should not need to use these options.
614 @item --exec-prefix=@var{dirname}
615 Specify the toplevel installation directory for architecture-dependent
616 files. The default is @file{@var{prefix}}.
618 @item --bindir=@var{dirname}
619 Specify the installation directory for the executables called by users
620 (such as @command{gcc} and @command{g++}). The default is
621 @file{@var{exec-prefix}/bin}.
623 @item --libdir=@var{dirname}
624 Specify the installation directory for object code libraries and
625 internal data files of GCC@. The default is @file{@var{exec-prefix}/lib}.
627 @item --libexecdir=@var{dirname}
628 Specify the installation directory for internal executables of GCC@.
629 The default is @file{@var{exec-prefix}/libexec}.
631 @item --with-slibdir=@var{dirname}
632 Specify the installation directory for the shared libgcc library. The
633 default is @file{@var{libdir}}.
635 @item --infodir=@var{dirname}
636 Specify the installation directory for documentation in info format.
637 The default is @file{@var{prefix}/info}.
639 @item --datadir=@var{dirname}
640 Specify the installation directory for some architecture-independent
641 data files referenced by GCC@. The default is @file{@var{prefix}/share}.
643 @item --mandir=@var{dirname}
644 Specify the installation directory for manual pages. The default is
645 @file{@var{prefix}/man}. (Note that the manual pages are only extracts from
646 the full GCC manuals, which are provided in Texinfo format. The manpages
647 are derived by an automatic conversion process from parts of the full
650 @item --with-gxx-include-dir=@var{dirname}
652 the installation directory for G++ header files. The default is
653 @file{@var{prefix}/include/c++/@var{version}}.
657 @item --program-prefix=@var{prefix}
658 GCC supports some transformations of the names of its programs when
659 installing them. This option prepends @var{prefix} to the names of
660 programs to install in @var{bindir} (see above). For example, specifying
661 @option{--program-prefix=foo-} would result in @samp{gcc}
662 being installed as @file{/usr/local/bin/foo-gcc}.
664 @item --program-suffix=@var{suffix}
665 Appends @var{suffix} to the names of programs to install in @var{bindir}
666 (see above). For example, specifying @option{--program-suffix=-3.1}
667 would result in @samp{gcc} being installed as
668 @file{/usr/local/bin/gcc-3.1}.
670 @item --program-transform-name=@var{pattern}
671 Applies the @samp{sed} script @var{pattern} to be applied to the names
672 of programs to install in @var{bindir} (see above). @var{pattern} has to
673 consist of one or more basic @samp{sed} editing commands, separated by
674 semicolons. For example, if you want the @samp{gcc} program name to be
675 transformed to the installed program @file{/usr/local/bin/myowngcc} and
676 the @samp{g++} program name to be transformed to
677 @file{/usr/local/bin/gspecial++} without changing other program names,
678 you could use the pattern
679 @option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'}
680 to achieve this effect.
682 All three options can be combined and used together, resulting in more
683 complex conversion patterns. As a basic rule, @var{prefix} (and
684 @var{suffix}) are prepended (appended) before further transformations
685 can happen with a special transformation script @var{pattern}.
687 As currently implemented, this option only takes effect for native
688 builds; cross compiler binaries' names are not transformed even when a
689 transformation is explicitly asked for by one of these options.
691 For native builds, some of the installed programs are also installed
692 with the target alias in front of their name, as in
693 @samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen
694 before the target alias is prepended to the name---so, specifying
695 @option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the
696 resulting binary would be installed as
697 @file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}.
699 As a last shortcoming, none of the installed Ada programs are
700 transformed yet, which will be fixed in some time.
702 @item --with-local-prefix=@var{dirname}
704 installation directory for local include files. The default is
705 @file{/usr/local}. Specify this option if you want the compiler to
706 search directory @file{@var{dirname}/include} for locally installed
707 header files @emph{instead} of @file{/usr/local/include}.
709 You should specify @option{--with-local-prefix} @strong{only} if your
710 site has a different convention (not @file{/usr/local}) for where to put
713 The default value for @option{--with-local-prefix} is @file{/usr/local}
714 regardless of the value of @option{--prefix}. Specifying
715 @option{--prefix} has no effect on which directory GCC searches for
716 local header files. This may seem counterintuitive, but actually it is
719 The purpose of @option{--prefix} is to specify where to @emph{install
720 GCC}. The local header files in @file{/usr/local/include}---if you put
721 any in that directory---are not part of GCC@. They are part of other
722 programs---perhaps many others. (GCC installs its own header files in
723 another directory which is based on the @option{--prefix} value.)
725 Both the local-prefix include directory and the GCC-prefix include
726 directory are part of GCC's ``system include'' directories. Although these
727 two directories are not fixed, they need to be searched in the proper
728 order for the correct processing of the include_next directive. The
729 local-prefix include directory is searched before the GCC-prefix
730 include directory. Another characteristic of system include directories
731 is that pedantic warnings are turned off for headers in these directories.
733 Some autoconf macros add @option{-I @var{directory}} options to the
734 compiler command line, to ensure that directories containing installed
735 packages' headers are searched. When @var{directory} is one of GCC's
736 system include directories, GCC will ignore the option so that system
737 directories continue to be processed in the correct order. This
738 may result in a search order different from what was specified but the
739 directory will still be searched.
741 GCC automatically searches for ordinary libraries using
742 @env{GCC_EXEC_PREFIX}. Thus, when the same installation prefix is
743 used for both GCC and packages, GCC will automatically search for
744 both headers and libraries. This provides a configuration that is
745 easy to use. GCC behaves in a manner similar to that when it is
746 installed as a system compiler in @file{/usr}.
748 Sites that need to install multiple versions of GCC may not want to
749 use the above simple configuration. It is possible to use the
750 @option{--program-prefix}, @option{--program-suffix} and
751 @option{--program-transform-name} options to install multiple versions
752 into a single directory, but it may be simpler to use different prefixes
753 and the @option{--with-local-prefix} option to specify the location of the
754 site-specific files for each version. It will then be necessary for
755 users to specify explicitly the location of local site libraries
756 (e.g., with @env{LIBRARY_PATH}).
758 The same value can be used for both @option{--with-local-prefix} and
759 @option{--prefix} provided it is not @file{/usr}. This can be used
760 to avoid the default search of @file{/usr/local/include}.
762 @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
763 The directory you use for @option{--with-local-prefix} @strong{must not}
764 contain any of the system's standard header files. If it did contain
765 them, certain programs would be miscompiled (including GNU Emacs, on
766 certain targets), because this would override and nullify the header
767 file corrections made by the @command{fixincludes} script.
769 Indications are that people who use this option use it based on mistaken
770 ideas of what it is for. People use it as if it specified where to
771 install part of GCC@. Perhaps they make this assumption because
772 installing GCC creates the directory.
774 @item --enable-shared[=@var{package}[,@dots{}]]
775 Build shared versions of libraries, if shared libraries are supported on
776 the target platform. Unlike GCC 2.95.x and earlier, shared libraries
777 are enabled by default on all platforms that support shared libraries.
779 If a list of packages is given as an argument, build shared libraries
780 only for the listed packages. For other packages, only static libraries
781 will be built. Package names currently recognized in the GCC tree are
782 @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not
783 @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc},
784 @samp{ada}, @samp{libada}, @samp{libjava} and @samp{libobjc}.
785 Note @samp{libiberty} does not support shared libraries at all.
787 Use @option{--disable-shared} to build only static libraries. Note that
788 @option{--disable-shared} does not accept a list of package names as
789 argument, only @option{--enable-shared} does.
791 @item @anchor{with-gnu-as}--with-gnu-as
792 Specify that the compiler should assume that the
793 assembler it finds is the GNU assembler. However, this does not modify
794 the rules to find an assembler and will result in confusion if the
795 assembler found is not actually the GNU assembler. (Confusion may also
796 result if the compiler finds the GNU assembler but has not been
797 configured with @option{--with-gnu-as}.) If you have more than one
798 assembler installed on your system, you may want to use this option in
799 connection with @option{--with-as=@var{pathname}} or
800 @option{--with-build-time-tools=@var{pathname}}.
802 The following systems are the only ones where it makes a difference
803 whether you use the GNU assembler. On any other system,
804 @option{--with-gnu-as} has no effect.
807 @item @samp{hppa1.0-@var{any}-@var{any}}
808 @item @samp{hppa1.1-@var{any}-@var{any}}
809 @item @samp{i386-@var{any}-sysv}
810 @item @samp{m68k-bull-sysv}
811 @item @samp{m68k-hp-hpux}
812 @item @samp{m68000-hp-hpux}
813 @item @samp{m68000-att-sysv}
814 @item @samp{sparc-sun-solaris2.@var{any}}
815 @item @samp{sparc64-@var{any}-solaris2.@var{any}}
818 On the systems listed above (except for the HP-PA, the SPARC, for ISC on
819 the 386, if you use the GNU assembler, you should also use the GNU linker
820 (and specify @option{--with-gnu-ld}).
822 @item @anchor{with-as}--with-as=@var{pathname}
823 Specify that the compiler should use the assembler pointed to by
824 @var{pathname}, rather than the one found by the standard rules to find
825 an assembler, which are:
828 Unless GCC is being built with a cross compiler, check the
829 @file{@var{libexec}/gcc/@var{target}/@var{version}} directory.
830 @var{libexec} defaults to @file{@var{exec-prefix}/libexec};
831 @var{exec-prefix} defaults to @var{prefix}, which
832 defaults to @file{/usr/local} unless overridden by the
833 @option{--prefix=@var{pathname}} switch described above. @var{target}
834 is the target system triple, such as @samp{sparc-sun-solaris2.7}, and
835 @var{version} denotes the GCC version, such as 3.0.
838 If the target system is the same that you are building on, check
839 operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
843 Check in the @env{PATH} for a tool whose name is prefixed by the
844 target system triple.
847 Check in the @env{PATH} for a tool whose name is not prefixed by the
848 target system triple, if the host and target system triple are
849 the same (in other words, we use a host tool if it can be used for
853 You may want to use @option{--with-as} if no assembler
854 is installed in the directories listed above, or if you have multiple
855 assemblers installed and want to choose one that is not found by the
858 @item @anchor{with-gnu-ld}--with-gnu-ld
859 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
862 @item --with-ld=@var{pathname}
863 Same as @uref{#with-as,,@option{--with-as}}
867 Specify that stabs debugging
868 information should be used instead of whatever format the host normally
869 uses. Normally GCC uses the same debug format as the host system.
871 On MIPS based systems and on Alphas, you must specify whether you want
872 GCC to create the normal ECOFF debugging format, or to use BSD-style
873 stabs passed through the ECOFF symbol table. The normal ECOFF debug
874 format cannot fully handle languages other than C@. BSD stabs format can
875 handle other languages, but it only works with the GNU debugger GDB@.
877 Normally, GCC uses the ECOFF debugging format by default; if you
878 prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@.
880 No matter which default you choose when you configure GCC, the user
881 can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
882 the debug format for a particular compilation.
884 @option{--with-stabs} is meaningful on the ISC system on the 386, also, if
885 @option{--with-gas} is used. It selects use of stabs debugging
886 information embedded in COFF output. This kind of debugging information
887 supports C++ well; ordinary COFF debugging information does not.
889 @option{--with-stabs} is also meaningful on 386 systems running SVR4. It
890 selects use of stabs debugging information embedded in ELF output. The
891 C++ compiler currently (2.6.0) does not support the DWARF debugging
892 information normally used on 386 SVR4 platforms; stabs provide a
893 workable alternative. This requires gas and gdb, as the normal SVR4
894 tools can not generate or interpret stabs.
896 @item --disable-multilib
897 Specify that multiple target
898 libraries to support different target variants, calling
899 conventions, etc should not be built. The default is to build a
900 predefined set of them.
902 Some targets provide finer-grained control over which multilibs are built
903 (e.g., @option{--disable-softfloat}):
909 fpu, 26bit, underscore, interwork, biendian, nofmult.
912 softfloat, m68881, m68000, m68020.
915 single-float, biendian, softfloat.
917 @item powerpc*-*-*, rs6000*-*-*
918 aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
923 @item --enable-threads
924 Specify that the target
925 supports threads. This affects the Objective-C compiler and runtime
926 library, and exception handling for other languages like C++ and Java.
927 On some systems, this is the default.
929 In general, the best (and, in many cases, the only known) threading
930 model available will be configured for use. Beware that on some
931 systems, GCC has not been taught what threading models are generally
932 available for the system. In this case, @option{--enable-threads} is an
933 alias for @option{--enable-threads=single}.
935 @item --disable-threads
936 Specify that threading support should be disabled for the system.
937 This is an alias for @option{--enable-threads=single}.
939 @item --enable-threads=@var{lib}
941 @var{lib} is the thread support library. This affects the Objective-C
942 compiler and runtime library, and exception handling for other languages
943 like C++ and Java. The possibilities for @var{lib} are:
951 Ada tasking support. For non-Ada programs, this setting is equivalent
952 to @samp{single}. When used in conjunction with the Ada run time, it
953 causes GCC to use the same thread primitives as Ada uses. This option
954 is necessary when using both Ada and the back end exception handling,
955 which is the default for most Ada targets.
957 Generic MACH thread support, known to work on NeXTSTEP@. (Please note
958 that the file needed to support this configuration, @file{gthr-mach.h}, is
959 missing and thus this setting will cause a known bootstrap failure.)
961 This is an alias for @samp{single}.
963 Generic POSIX/Unix98 thread support.
965 Generic POSIX/Unix95 thread support.
967 RTEMS thread support.
969 Disable thread support, should work for all platforms.
971 Sun Solaris 2 thread support.
973 VxWorks thread support.
975 Microsoft Win32 API thread support.
977 Novell Kernel Services thread support.
981 Specify that the target supports TLS (Thread Local Storage). Usually
982 configure can correctly determine if TLS is supported. In cases where
983 it guesses incorrectly, TLS can be explicitly enabled or disabled with
984 @option{--enable-tls} or @option{--disable-tls}. This can happen if
985 the assembler supports TLS but the C library does not, or if the
986 assumptions made by the configure test are incorrect.
989 Specify that the target does not support TLS.
990 This is an alias for @option{--enable-tls=no}.
992 @item --with-cpu=@var{cpu}
993 Specify which cpu variant the compiler should generate code for by default.
994 @var{cpu} will be used as the default value of the @option{-mcpu=} switch.
995 This option is only supported on some targets, including ARM, i386, PowerPC,
998 @item --with-schedule=@var{cpu}
999 @itemx --with-arch=@var{cpu}
1000 @itemx --with-tune=@var{cpu}
1001 @itemx --with-abi=@var{abi}
1002 @itemx --with-fpu=@var{type}
1003 @itemx --with-float=@var{type}
1004 These configure options provide default values for the @option{-mschedule=},
1005 @option{-march=}, @option{-mtune=}, @option{-mabi=}, and @option{-mfpu=}
1006 options and for @option{-mhard-float} or @option{-msoft-float}. As with
1007 @option{--with-cpu}, which switches will be accepted and acceptable values
1008 of the arguments depend on the target.
1010 @item --with-mode=@var{mode}
1011 Specify if the compiler should default to @option{-marm} or @option{-mthumb}.
1012 This option is only supported on ARM targets.
1014 @item --with-divide=@var{type}
1015 Specify how the compiler should generate code for checking for
1016 division by zero. This option is only supported on the MIPS target.
1017 The possibilities for @var{type} are:
1020 Division by zero checks use conditional traps (this is the default on
1021 systems that support conditional traps).
1023 Division by zero checks use the break instruction.
1026 @item --enable-__cxa_atexit
1027 Define if you want to use __cxa_atexit, rather than atexit, to
1028 register C++ destructors for local statics and global objects.
1029 This is essential for fully standards-compliant handling of
1030 destructors, but requires __cxa_atexit in libc. This option is currently
1031 only available on systems with GNU libc. When enabled, this will cause
1032 @option{-fuse-cxa-exit} to be passed by default.
1034 @item --enable-target-optspace
1036 libraries should be optimized for code space instead of code speed.
1037 This is the default for the m32r platform.
1040 Specify that a user visible @command{cpp} program should not be installed.
1042 @item --with-cpp-install-dir=@var{dirname}
1043 Specify that the user visible @command{cpp} program should be installed
1044 in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
1046 @item --enable-initfini-array
1047 Force the use of sections @code{.init_array} and @code{.fini_array}
1048 (instead of @code{.init} and @code{.fini}) for constructors and
1049 destructors. Option @option{--disable-initfini-array} has the
1050 opposite effect. If neither option is specified, the configure script
1051 will try to guess whether the @code{.init_array} and
1052 @code{.fini_array} sections are supported and, if they are, use them.
1054 @item --enable-maintainer-mode
1055 The build rules that
1056 regenerate the GCC master message catalog @file{gcc.pot} are normally
1057 disabled. This is because it can only be rebuilt if the complete source
1058 tree is present. If you have changed the sources and want to rebuild the
1059 catalog, configuring with @option{--enable-maintainer-mode} will enable
1060 this. Note that you need a recent version of the @code{gettext} tools
1063 @item --disable-bootstrap
1064 For a native build, the default configuration is to perform
1065 a 3-stage bootstrap of the compiler when @samp{make} is invoked,
1066 testing that GCC can compile itself correctly. If you want to disable
1067 this process, you can configure with @option{--disable-bootstrap}.
1069 @item --enable-bootstrap
1070 In special cases, you may want to perform a 3-stage build
1071 even if the target and host triplets are different.
1072 This could happen when the host can run code compiled for
1073 the target (e.g.@: host is i686-linux, target is i486-linux).
1074 Starting from GCC 4.2, to do this you have to configure explicitly
1075 with @option{--enable-bootstrap}.
1077 @item --enable-generated-files-in-srcdir
1078 Neither the .c and .h files that are generated from Bison and flex nor the
1079 info manuals and man pages that are built from the .texi files are present
1080 in the SVN development tree. When building GCC from that development tree,
1081 or from one of our snapshots, those generated files are placed in your
1082 build directory, which allows for the source to be in a readonly
1085 If you configure with @option{--enable-generated-files-in-srcdir} then those
1086 generated files will go into the source directory. This is mainly intended
1087 for generating release or prerelease tarballs of the GCC sources, since it
1088 is not a requirement that the users of source releases to have flex, Bison,
1091 @item --enable-version-specific-runtime-libs
1093 that runtime libraries should be installed in the compiler specific
1094 subdirectory (@file{@var{libdir}/gcc}) rather than the usual places. In
1095 addition, @samp{libstdc++}'s include files will be installed into
1096 @file{@var{libdir}} unless you overruled it by using
1097 @option{--with-gxx-include-dir=@var{dirname}}. Using this option is
1098 particularly useful if you intend to use several versions of GCC in
1099 parallel. This is currently supported by @samp{libgfortran},
1100 @samp{libjava}, @samp{libmudflap}, @samp{libstdc++}, and @samp{libobjc}.
1102 @item --with-java-home=@var{dirname}
1103 This @samp{libjava} option overrides the default value of the
1104 @samp{java.home} system property. It is also used to set
1105 @samp{sun.boot.class.path} to @file{@var{dirname}/lib/rt.jar}. By
1106 default @samp{java.home} is set to @file{@var{prefix}} and
1107 @samp{sun.boot.class.path} to
1108 @file{@var{datadir}/java/libgcj-@var{version}.jar}.
1110 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
1111 Specify that only a particular subset of compilers and
1112 their runtime libraries should be built. For a list of valid values for
1113 @var{langN} you can issue the following command in the
1114 @file{gcc} directory of your GCC source tree:@*
1116 grep language= */config-lang.in
1118 Currently, you can use any of the following:
1119 @code{all}, @code{ada}, @code{c}, @code{c++}, @code{fortran}, @code{java},
1120 @code{objc}, @code{obj-c++}, @code{treelang}.
1121 Building the Ada compiler has special requirements, see below.
1122 If you do not pass this flag, or specify the option @code{all}, then all
1123 default languages available in the @file{gcc} sub-tree will be configured.
1124 Ada, Objective-C++, and treelang are not default languages; the rest are.
1125 Re-defining @code{LANGUAGES} when calling @samp{make} @strong{does not}
1126 work anymore, as those language sub-directories might not have been
1129 @item --disable-libada
1130 Specify that the run-time libraries and tools used by GNAT should not
1131 be built. This can be useful for debugging, or for compatibility with
1132 previous Ada build procedures, when it was required to explicitly
1133 do a @samp{make -C gcc gnatlib_and_tools}.
1135 @item --disable-libssp
1136 Specify that the run-time libraries for stack smashing protection
1137 should not be built.
1139 @item --disable-libgomp
1140 Specify that the run-time libraries used by GOMP should not be built.
1143 Specify that the compiler should
1144 use DWARF 2 debugging information as the default.
1146 @item --enable-targets=all
1147 @itemx --enable-targets=@var{target_list}
1148 Some GCC targets, e.g.@: powerpc64-linux, build bi-arch compilers.
1149 These are compilers that are able to generate either 64-bit or 32-bit
1150 code. Typically, the corresponding 32-bit target, e.g.@:
1151 powerpc-linux for powerpc64-linux, only generates 32-bit code. This
1152 option enables the 32-bit target to be a bi-arch compiler, which is
1153 useful when you want a bi-arch compiler that defaults to 32-bit, and
1154 you are building a bi-arch or multi-arch binutils in a combined tree.
1155 Currently, this option only affects powerpc-linux.
1157 @item --enable-secureplt
1158 This option enables @option{-msecure-plt} by default for powerpc-linux.
1160 @xref{RS/6000 and PowerPC Options,, RS/6000 and PowerPC Options, gcc,
1161 Using the GNU Compiler Collection (GCC)},
1164 See ``RS/6000 and PowerPC Options'' in the main manual
1167 @item --enable-win32-registry
1168 @itemx --enable-win32-registry=@var{key}
1169 @itemx --disable-win32-registry
1170 The @option{--enable-win32-registry} option enables Microsoft Windows-hosted GCC
1171 to look up installations paths in the registry using the following key:
1174 @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
1177 @var{key} defaults to GCC version number, and can be overridden by the
1178 @option{--enable-win32-registry=@var{key}} option. Vendors and distributors
1179 who use custom installers are encouraged to provide a different key,
1180 perhaps one comprised of vendor name and GCC version number, to
1181 avoid conflict with existing installations. This feature is enabled
1182 by default, and can be disabled by @option{--disable-win32-registry}
1183 option. This option has no effect on the other hosts.
1186 Specify that the machine does not have a floating point unit. This
1187 option only applies to @samp{m68k-sun-sunos@var{n}}. On any other
1188 system, @option{--nfp} has no effect.
1190 @item --enable-werror
1191 @itemx --disable-werror
1192 @itemx --enable-werror=yes
1193 @itemx --enable-werror=no
1194 When you specify this option, it controls whether certain files in the
1195 compiler are built with @option{-Werror} in bootstrap stage2 and later.
1196 If you don't specify it, @option{-Werror} is turned on for the main
1197 development trunk. However it defaults to off for release branches and
1198 final releases. The specific files which get @option{-Werror} are
1199 controlled by the Makefiles.
1201 @item --enable-checking
1202 @itemx --enable-checking=@var{list}
1203 When you specify this option, the compiler is built to perform internal
1204 consistency checks of the requested complexity. This does not change the
1205 generated code, but adds error checking within the compiler. This will
1206 slow down the compiler and may only work properly if you are building
1207 the compiler with GCC@. This is @samp{yes} by default when building
1208 from SVN or snapshots, but @samp{release} for releases. More control
1209 over the checks may be had by specifying @var{list}. The categories of
1210 checks available are @samp{yes} (most common checks
1211 @samp{assert,misc,tree,gc,rtlflag,runtime}), @samp{no} (no checks at
1212 all), @samp{all} (all but @samp{valgrind}), @samp{release} (cheapest
1213 checks @samp{assert,runtime}) or @samp{none} (same as @samp{no}).
1214 Individual checks can be enabled with these flags @samp{assert},
1215 @samp{fold}, @samp{gc}, @samp{gcac} @samp{misc}, @samp{rtl},
1216 @samp{rtlflag}, @samp{runtime}, @samp{tree}, and @samp{valgrind}.
1218 The @samp{valgrind} check requires the external @command{valgrind}
1219 simulator, available from @uref{http://valgrind.org/}. The
1220 @samp{rtl}, @samp{gcac} and @samp{valgrind} checks are very expensive.
1221 To disable all checking, @samp{--disable-checking} or
1222 @samp{--enable-checking=none} must be explicitly requested. Disabling
1223 assertions will make the compiler and runtime slightly faster but
1224 increase the risk of undetected internal errors causing wrong code to be
1227 @item --enable-coverage
1228 @itemx --enable-coverage=@var{level}
1229 With this option, the compiler is built to collect self coverage
1230 information, every time it is run. This is for internal development
1231 purposes, and only works when the compiler is being built with gcc. The
1232 @var{level} argument controls whether the compiler is built optimized or
1233 not, values are @samp{opt} and @samp{noopt}. For coverage analysis you
1234 want to disable optimization, for performance analysis you want to
1235 enable optimization. When coverage is enabled, the default level is
1236 without optimization.
1238 @item --enable-gather-detailed-mem-stats
1239 When this option is specified more detailed information on memory
1240 allocation is gathered. This information is printed when using
1241 @option{-fmem-report}.
1244 @itemx --with-gc=@var{choice}
1245 With this option you can specify the garbage collector implementation
1246 used during the compilation process. @var{choice} can be one of
1247 @samp{page} and @samp{zone}, where @samp{page} is the default.
1250 @itemx --disable-nls
1251 The @option{--enable-nls} option enables Native Language Support (NLS),
1252 which lets GCC output diagnostics in languages other than American
1253 English. Native Language Support is enabled by default if not doing a
1254 canadian cross build. The @option{--disable-nls} option disables NLS@.
1256 @item --with-included-gettext
1257 If NLS is enabled, the @option{--with-included-gettext} option causes the build
1258 procedure to prefer its copy of GNU @command{gettext}.
1260 @item --with-catgets
1261 If NLS is enabled, and if the host lacks @code{gettext} but has the
1262 inferior @code{catgets} interface, the GCC build procedure normally
1263 ignores @code{catgets} and instead uses GCC's copy of the GNU
1264 @code{gettext} library. The @option{--with-catgets} option causes the
1265 build procedure to use the host's @code{catgets} in this situation.
1267 @item --with-libiconv-prefix=@var{dir}
1268 Search for libiconv header files in @file{@var{dir}/include} and
1269 libiconv library files in @file{@var{dir}/lib}.
1271 @item --enable-obsolete
1272 Enable configuration for an obsoleted system. If you attempt to
1273 configure GCC for a system (build, host, or target) which has been
1274 obsoleted, and you do not specify this flag, configure will halt with an
1277 All support for systems which have been obsoleted in one release of GCC
1278 is removed entirely in the next major release, unless someone steps
1279 forward to maintain the port.
1281 @item --enable-decimal-float
1282 @itemx --disable-decimal-float
1283 Enable (or disable) support for the C decimal floating point
1284 extension. This is enabled by default only on PowerPC GNU/Linux
1285 systems. Other systems may also support it, but require the user to
1286 specifically enable it.
1288 @item --with-long-double-128
1289 Specify if @code{long double} type should be 128-bit by default on selected
1290 GNU/Linux architectures. If using @code{--without-long-double-128},
1291 @code{long double} will be by default 64-bit, the same as @code{double} type.
1292 When neither of these configure options are used, the default will be
1293 128-bit @code{long double} when built against GNU C Library 2.4 and later,
1294 64-bit @code{long double} otherwise.
1298 @subheading Cross-Compiler-Specific Options
1299 The following options only apply to building cross compilers.
1301 @item --with-sysroot
1302 @itemx --with-sysroot=@var{dir}
1303 Tells GCC to consider @var{dir} as the root of a tree that contains a
1304 (subset of) the root filesystem of the target operating system.
1305 Target system headers, libraries and run-time object files will be
1306 searched in there. The specified directory is not copied into the
1307 install tree, unlike the options @option{--with-headers} and
1308 @option{--with-libs} that this option obsoletes. The default value,
1309 in case @option{--with-sysroot} is not given an argument, is
1310 @option{$@{gcc_tooldir@}/sys-root}. If the specified directory is a
1311 subdirectory of @option{$@{exec_prefix@}}, then it will be found relative to
1312 the GCC binaries if the installation tree is moved.
1314 @item --with-build-sysroot
1315 @itemx --with-build-sysroot=@var{dir}
1316 Tells GCC to consider @var{dir} as the system root (see
1317 @option{--with-sysroot}) while building target libraries, instead of
1318 the directory specified with @option{--with-sysroot}. This option is
1319 only useful when you are already using @option{--with-sysroot}. You
1320 can use @option{--with-build-sysroot} when you are configuring with
1321 @option{--prefix} set to a directory that is different from the one in
1322 which you are installing GCC and your target libraries.
1324 This option affects the system root for the compiler used to build
1325 target libraries (which runs on the build system); it does not affect
1326 the compiler which is used to build GCC itself.
1328 @item --with-headers
1329 @itemx --with-headers=@var{dir}
1330 Deprecated in favor of @option{--with-sysroot}.
1331 Specifies that target headers are available when building a cross compiler.
1332 The @var{dir} argument specifies a directory which has the target include
1333 files. These include files will be copied into the @file{gcc} install
1334 directory. @emph{This option with the @var{dir} argument is required} when
1335 building a cross compiler, if @file{@var{prefix}/@var{target}/sys-include}
1336 doesn't pre-exist. If @file{@var{prefix}/@var{target}/sys-include} does
1337 pre-exist, the @var{dir} argument may be omitted. @command{fixincludes}
1338 will be run on these files to make them compatible with GCC@.
1340 @item --without-headers
1341 Tells GCC not use any target headers from a libc when building a cross
1342 compiler. When crossing to GNU/Linux, you need the headers so GCC
1343 can build the exception handling for libgcc.
1346 @itemx --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}''
1347 Deprecated in favor of @option{--with-sysroot}.
1348 Specifies a list of directories which contain the target runtime
1349 libraries. These libraries will be copied into the @file{gcc} install
1350 directory. If the directory list is omitted, this option has no
1354 Specifies that @samp{newlib} is
1355 being used as the target C library. This causes @code{__eprintf} to be
1356 omitted from @file{libgcc.a} on the assumption that it will be provided by
1359 @item --with-build-time-tools=@var{dir}
1360 Specifies where to find the set of target tools (assembler, linker, etc.)
1361 that will be used while building GCC itself. This option can be useful
1362 if the directory layouts are different between the system you are building
1363 GCC on, and the system where you will deploy it.
1365 For example, on a @option{ia64-hp-hpux} system, you may have the GNU
1366 assembler and linker in @file{/usr/bin}, and the native tools in a
1367 different path, and build a toolchain that expects to find the
1368 native tools in @file{/usr/bin}.
1370 When you use this option, you should ensure that @var{dir} includes
1371 @command{ar}, @command{as}, @command{ld}, @command{nm},
1372 @command{ranlib} and @command{strip} if necessary, and possibly
1373 @command{objdump}. Otherwise, GCC may use an inconsistent set of
1377 @subheading Fortran-Specific Options
1379 The following options apply to the build of the Fortran front end.
1383 @item --with-gmp=@var{pathname}
1384 @itemx --with-mpfr=@var{pathname}
1385 @itemx --with-gmp-dir=@var{pathname}
1386 @itemx --with-mpfr-dir=@var{pathname}
1387 If you don't have GMP (the GNU Multiple Precision library) and the MPFR
1388 Libraries installed in a standard location and you want to build the Fortran
1389 front-end, you can explicitly specify the directory where they are installed
1390 (@samp{--with-gmp=gmpinstalldir}, @samp{--with-mpfr=mpfrinstalldir}) or where
1391 you built them without installing (@samp{--with-gmp-dir=gmpbuilddir},
1392 @samp{--with-mpfr-dir=gmpbuilddir}).
1396 @subheading Java-Specific Options
1398 The following option applies to the build of the Java front end.
1401 @item --disable-libgcj
1402 Specify that the run-time libraries
1403 used by GCJ should not be built. This is useful in case you intend
1404 to use GCJ with some other run-time, or you're going to install it
1405 separately, or it just happens not to build on your particular
1406 machine. In general, if the Java front end is enabled, the GCJ
1407 libraries will be enabled too, unless they're known to not work on
1408 the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
1409 may need to port it; in this case, before modifying the top-level
1410 @file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
1411 you may use @option{--enable-libgcj} to override the default.
1415 The following options apply to building @samp{libgcj}.
1417 @subsubheading General Options
1420 @item --disable-getenv-properties
1421 Don't set system properties from @env{GCJ_PROPERTIES}.
1423 @item --enable-hash-synchronization
1424 Use a global hash table for monitor locks. Ordinarily,
1425 @samp{libgcj}'s @samp{configure} script automatically makes
1426 the correct choice for this option for your platform. Only use
1427 this if you know you need the library to be configured differently.
1429 @item --enable-interpreter
1430 Enable the Java interpreter. The interpreter is automatically
1431 enabled by default on all platforms that support it. This option
1432 is really only useful if you want to disable the interpreter
1433 (using @option{--disable-interpreter}).
1435 @item --disable-java-net
1436 Disable java.net. This disables the native part of java.net only,
1437 using non-functional stubs for native method implementations.
1439 @item --disable-jvmpi
1440 Disable JVMPI support.
1443 Enable runtime eCos target support.
1445 @item --without-libffi
1446 Don't use @samp{libffi}. This will disable the interpreter and JNI
1447 support as well, as these require @samp{libffi} to work.
1449 @item --enable-libgcj-debug
1450 Enable runtime debugging code.
1452 @item --enable-libgcj-multifile
1453 If specified, causes all @file{.java} source files to be
1454 compiled into @file{.class} files in one invocation of
1455 @samp{gcj}. This can speed up build time, but is more
1456 resource-intensive. If this option is unspecified or
1457 disabled, @samp{gcj} is invoked once for each @file{.java}
1458 file to compile into a @file{.class} file.
1460 @item --with-libiconv-prefix=DIR
1461 Search for libiconv in @file{DIR/include} and @file{DIR/lib}.
1463 @item --enable-sjlj-exceptions
1464 Force use of the @code{setjmp}/@code{longjmp}-based scheme for exceptions.
1465 @samp{configure} ordinarily picks the correct value based on the platform.
1466 Only use this option if you are sure you need a different setting.
1468 @item --with-system-zlib
1469 Use installed @samp{zlib} rather than that included with GCC@.
1471 @item --with-win32-nlsapi=ansi, unicows or unicode
1472 Indicates how MinGW @samp{libgcj} translates between UNICODE
1473 characters and the Win32 API@.
1476 Use the single-byte @code{char} and the Win32 A functions natively,
1477 translating to and from UNICODE when using these functions. If
1478 unspecified, this is the default.
1481 Use the @code{WCHAR} and Win32 W functions natively. Adds
1482 @code{-lunicows} to @file{libgcj.spec} to link with @samp{libunicows}.
1483 @file{unicows.dll} needs to be deployed on Microsoft Windows 9X machines
1484 running built executables. @file{libunicows.a}, an open-source
1485 import library around Microsoft's @code{unicows.dll}, is obtained from
1486 @uref{http://libunicows.sourceforge.net/}, which also gives details
1487 on getting @file{unicows.dll} from Microsoft.
1490 Use the @code{WCHAR} and Win32 W functions natively. Does @emph{not}
1491 add @code{-lunicows} to @file{libgcj.spec}. The built executables will
1492 only run on Microsoft Windows NT and above.
1496 @subsubheading AWT-Specific Options
1500 Use the X Window System.
1502 @item --enable-java-awt=PEER(S)
1503 Specifies the AWT peer library or libraries to build alongside
1504 @samp{libgcj}. If this option is unspecified or disabled, AWT
1505 will be non-functional. Current valid values are @option{gtk} and
1506 @option{xlib}. Multiple libraries should be separated by a
1507 comma (i.e.@: @option{--enable-java-awt=gtk,xlib}).
1509 @item --enable-gtk-cairo
1510 Build the cairo Graphics2D implementation on GTK@.
1512 @item --enable-java-gc=TYPE
1513 Choose garbage collector. Defaults to @option{boehm} if unspecified.
1515 @item --disable-gtktest
1516 Do not try to compile and run a test GTK+ program.
1518 @item --disable-glibtest
1519 Do not try to compile and run a test GLIB program.
1521 @item --with-libart-prefix=PFX
1522 Prefix where libart is installed (optional).
1524 @item --with-libart-exec-prefix=PFX
1525 Exec prefix where libart is installed (optional).
1527 @item --disable-libarttest
1528 Do not try to compile and run a test libart program.
1537 @uref{./index.html,,Return to the GCC Installation page}
1541 @c ***Building****************************************************************
1543 @comment node-name, next, previous, up
1544 @node Building, Testing, Configuration, Installing GCC
1550 @cindex Installing GCC: Building
1552 Now that GCC is configured, you are ready to build the compiler and
1555 Some commands executed when making the compiler may fail (return a
1556 nonzero status) and be ignored by @command{make}. These failures, which
1557 are often due to files that were not found, are expected, and can safely
1560 It is normal to have compiler warnings when compiling certain files.
1561 Unless you are a GCC developer, you can generally ignore these warnings
1562 unless they cause compilation to fail. Developers should attempt to fix
1563 any warnings encountered, however they can temporarily continue past
1564 warnings-as-errors by specifying the configure flag
1565 @option{--disable-werror}.
1567 On certain old systems, defining certain environment variables such as
1568 @env{CC} can interfere with the functioning of @command{make}.
1570 If you encounter seemingly strange errors when trying to build the
1571 compiler in a directory other than the source directory, it could be
1572 because you have previously configured the compiler in the source
1573 directory. Make sure you have done all the necessary preparations.
1575 If you build GCC on a BSD system using a directory stored in an old System
1576 V file system, problems may occur in running @command{fixincludes} if the
1577 System V file system doesn't support symbolic links. These problems
1578 result in a failure to fix the declaration of @code{size_t} in
1579 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
1580 that type mismatches occur, this could be the cause.
1582 The solution is not to use such a directory for building GCC@.
1584 When building from SVN or snapshots, or if you modify parser sources,
1585 you need the Bison parser generator installed. If you do not modify
1586 parser sources, releases contain the Bison-generated files and you do
1587 not need Bison installed to build them.
1589 When building from SVN or snapshots, or if you modify Texinfo
1590 documentation, you need version 4.4 or later of Texinfo installed if you
1591 want Info documentation to be regenerated. Releases contain Info
1592 documentation pre-built for the unmodified documentation in the release.
1594 @section Building a native compiler
1596 For a native build, the default configuration is to perform
1597 a 3-stage bootstrap of the compiler when @samp{make} is invoked.
1598 This will build the entire GCC system and ensure that it compiles
1599 itself correctly. It can be disabled with the @option{--disable-bootstrap}
1600 parameter to @samp{configure}, but bootstrapping is suggested because
1601 the compiler will be tested more completely and could also have
1604 The bootstrapping process will complete the following steps:
1608 Build tools necessary to build the compiler.
1611 Perform a 3-stage bootstrap of the compiler. This includes building
1612 three times the target tools for use by the compiler such as binutils
1613 (bfd, binutils, gas, gprof, ld, and opcodes) if they have been
1614 individually linked or moved into the top level GCC source tree before
1618 Perform a comparison test of the stage2 and stage3 compilers.
1621 Build runtime libraries using the stage3 compiler from the previous step.
1625 If you are short on disk space you might consider @samp{make
1626 bootstrap-lean} instead. The sequence of compilation is the
1627 same described above, but object files from the stage1 and
1628 stage2 of the 3-stage bootstrap of the compiler are deleted as
1629 soon as they are no longer needed.
1631 If you want to save additional space during the bootstrap and in
1632 the final installation as well, you can build the compiler binaries
1633 without debugging information as in the following example. This will save
1634 roughly 40% of disk space both for the bootstrap and the final installation.
1635 (Libraries will still contain debugging information.)
1638 make CFLAGS='-O' LIBCFLAGS='-g -O2' \
1639 LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap
1642 If you wish to use non-default GCC flags when compiling the stage2 and
1643 stage3 compilers, set @code{BOOT_CFLAGS} on the command line when doing
1644 @samp{make}. Non-default optimization flags are less well
1645 tested here than the default of @samp{-g -O2}, but should still work.
1646 In a few cases, you may find that you need to specify special flags such
1647 as @option{-msoft-float} here to complete the bootstrap; or, if the
1648 native compiler miscompiles the stage1 compiler, you may need to work
1649 around this, by choosing @code{BOOT_CFLAGS} to avoid the parts of the
1650 stage1 compiler that were miscompiled, or by using @samp{make
1651 bootstrap4} to increase the number of stages of bootstrap.
1653 Note that using non-standard @code{CFLAGS} can cause bootstrap to fail
1654 if these trigger a warning with the new compiler. For example using
1655 @samp{-O2 -g -mcpu=i686} on @code{i686-pc-linux-gnu} will cause bootstrap
1656 failure as @option{-mcpu=} is deprecated in 3.4.0 and above.
1659 If you used the flag @option{--enable-languages=@dots{}} to restrict
1660 the compilers to be built, only those you've actually enabled will be
1661 built. This will of course only build those runtime libraries, for
1662 which the particular compiler has been built. Please note,
1663 that re-defining @env{LANGUAGES} when calling @samp{make}
1664 @strong{does not} work anymore!
1666 If the comparison of stage2 and stage3 fails, this normally indicates
1667 that the stage2 compiler has compiled GCC incorrectly, and is therefore
1668 a potentially serious bug which you should investigate and report. (On
1669 a few systems, meaningful comparison of object files is impossible; they
1670 always appear ``different''. If you encounter this problem, you will
1671 need to disable comparison in the @file{Makefile}.)
1673 If you do not want to bootstrap your compiler, you can configure with
1674 @option{--disable-bootstrap}. In particular cases, you may want to
1675 bootstrap your compiler even if the target system is not the same as
1676 the one you are building on: for example, you could build a
1677 @code{powerpc-unknown-linux-gnu} toolchain on a
1678 @code{powerpc64-unknown-linux-gnu} host. In this case, pass
1679 @option{--enable-bootstrap} to the configure script.
1682 @section Building a cross compiler
1684 When building a cross compiler, it is not generally possible to do a
1685 3-stage bootstrap of the compiler. This makes for an interesting problem
1686 as parts of GCC can only be built with GCC@.
1688 To build a cross compiler, we first recommend building and installing a
1689 native compiler. You can then use the native GCC compiler to build the
1690 cross compiler. The installed native compiler needs to be GCC version
1693 Assuming you have already installed a native copy of GCC and configured
1694 your cross compiler, issue the command @command{make}, which performs the
1699 Build host tools necessary to build the compiler.
1702 Build target tools for use by the compiler such as binutils (bfd,
1703 binutils, gas, gprof, ld, and opcodes)
1704 if they have been individually linked or moved into the top level GCC source
1705 tree before configuring.
1708 Build the compiler (single stage only).
1711 Build runtime libraries using the compiler from the previous step.
1714 Note that if an error occurs in any step the make process will exit.
1716 If you are not building GNU binutils in the same source tree as GCC,
1717 you will need a cross-assembler and cross-linker installed before
1718 configuring GCC@. Put them in the directory
1719 @file{@var{prefix}/@var{target}/bin}. Here is a table of the tools
1720 you should put in this directory:
1724 This should be the cross-assembler.
1727 This should be the cross-linker.
1730 This should be the cross-archiver: a program which can manipulate
1731 archive files (linker libraries) in the target machine's format.
1734 This should be a program to construct a symbol table in an archive file.
1737 The installation of GCC will find these programs in that directory,
1738 and copy or link them to the proper place to for the cross-compiler to
1739 find them when run later.
1741 The easiest way to provide these files is to build the Binutils package.
1742 Configure it with the same @option{--host} and @option{--target}
1743 options that you use for configuring GCC, then build and install
1744 them. They install their executables automatically into the proper
1745 directory. Alas, they do not support all the targets that GCC
1748 If you are not building a C library in the same source tree as GCC,
1749 you should also provide the target libraries and headers before
1750 configuring GCC, specifying the directories with
1751 @option{--with-sysroot} or @option{--with-headers} and
1752 @option{--with-libs}. Many targets also require ``start files'' such
1753 as @file{crt0.o} and
1754 @file{crtn.o} which are linked into each executable. There may be several
1755 alternatives for @file{crt0.o}, for use with profiling or other
1756 compilation options. Check your target's definition of
1757 @code{STARTFILE_SPEC} to find out what start files it uses.
1759 @section Building in parallel
1761 GNU Make 3.79 and above, which is necessary to build GCC, support
1762 building in parallel. To activate this, you can use @samp{make -j 2}
1763 instead of @samp{make}. You can also specify a bigger number, and
1764 in most cases using a value greater than the number of processors in
1765 your machine will result in fewer and shorter I/O latency hits, thus
1766 improving overall throughput; this is especially true for slow drives
1767 and network filesystems.
1769 @section Building the Ada compiler
1771 In order to build GNAT, the Ada compiler, you need a working GNAT
1772 compiler (GNAT version 3.14 or later, or GCC version 3.1 or later).
1773 This includes GNAT tools such as @command{gnatmake} and
1774 @command{gnatlink}, since the Ada front end is written in Ada and
1775 uses some GNAT-specific extensions.
1777 In order to build a cross compiler, it is suggested to install
1778 the new compiler as native first, and then use it to build the cross
1781 @command{configure} does not test whether the GNAT installation works
1782 and has a sufficiently recent version; if too old a GNAT version is
1783 installed, the build will fail unless @option{--enable-languages} is
1784 used to disable building the Ada front end.
1786 @section Building with profile feedback
1788 It is possible to use profile feedback to optimize the compiler itself. This
1789 should result in a faster compiler binary. Experiments done on x86 using gcc
1790 3.3 showed approximately 7 percent speedup on compiling C programs. To
1791 bootstrap the compiler with profile feedback, use @code{make profiledbootstrap}.
1793 When @samp{make profiledbootstrap} is run, it will first build a @code{stage1}
1794 compiler. This compiler is used to build a @code{stageprofile} compiler
1795 instrumented to collect execution counts of instruction and branch
1796 probabilities. Then runtime libraries are compiled with profile collected.
1797 Finally a @code{stagefeedback} compiler is built using the information collected.
1799 Unlike standard bootstrap, several additional restrictions apply. The
1800 compiler used to build @code{stage1} needs to support a 64-bit integral type.
1801 It is recommended to only use GCC for this. Also parallel make is currently
1802 not supported since collisions in profile collecting may occur.
1809 @uref{./index.html,,Return to the GCC Installation page}
1813 @c ***Testing*****************************************************************
1815 @comment node-name, next, previous, up
1816 @node Testing, Final install, Building, Installing GCC
1820 @chapter Installing GCC: Testing
1823 @cindex Installing GCC: Testing
1826 Before you install GCC, we encourage you to run the testsuites and to
1827 compare your results with results from a similar configuration that have
1828 been submitted to the
1829 @uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
1830 Some of these archived results are linked from the build status lists
1831 at @uref{http://gcc.gnu.org/buildstat.html}, although not everyone who
1832 reports a successful build runs the testsuites and submits the results.
1833 This step is optional and may require you to download additional software,
1834 but it can give you confidence in your new GCC installation or point out
1835 problems before you install and start using your new GCC@.
1837 First, you must have @uref{download.html,,downloaded the testsuites}.
1838 These are part of the full distribution, but if you downloaded the
1839 ``core'' compiler plus any front ends, you must download the testsuites
1842 Second, you must have the testing tools installed. This includes
1843 @uref{http://www.gnu.org/software/dejagnu/,,DejaGnu}, Tcl, and Expect;
1844 the DejaGnu site has links to these.
1846 If the directories where @command{runtest} and @command{expect} were
1847 installed are not in the @env{PATH}, you may need to set the following
1848 environment variables appropriately, as in the following example (which
1849 assumes that DejaGnu has been installed under @file{/usr/local}):
1852 TCL_LIBRARY = /usr/local/share/tcl8.0
1853 DEJAGNULIBS = /usr/local/share/dejagnu
1856 (On systems such as Cygwin, these paths are required to be actual
1857 paths, not mounts or links; presumably this is due to some lack of
1858 portability in the DejaGnu code.)
1861 Finally, you can run the testsuite (which may take a long time):
1863 cd @var{objdir}; make -k check
1866 This will test various components of GCC, such as compiler
1867 front ends and runtime libraries. While running the testsuite, DejaGnu
1868 might emit some harmless messages resembling
1869 @samp{WARNING: Couldn't find the global config file.} or
1870 @samp{WARNING: Couldn't find tool init file} that can be ignored.
1872 @section How can you run the testsuite on selected tests?
1874 In order to run sets of tests selectively, there are targets
1875 @samp{make check-gcc} and @samp{make check-g++}
1876 in the @file{gcc} subdirectory of the object directory. You can also
1877 just run @samp{make check} in a subdirectory of the object directory.
1880 A more selective way to just run all @command{gcc} execute tests in the
1884 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
1887 Likewise, in order to run only the @command{g++} ``old-deja'' tests in
1888 the testsuite with filenames matching @samp{9805*}, you would use
1891 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
1894 The @file{*.exp} files are located in the testsuite directories of the GCC
1895 source, the most important ones being @file{compile.exp},
1896 @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
1897 To get a list of the possible @file{*.exp} files, pipe the
1898 output of @samp{make check} into a file and look at the
1899 @samp{Running @dots{} .exp} lines.
1901 @section Passing options and running multiple testsuites
1903 You can pass multiple options to the testsuite using the
1904 @samp{--target_board} option of DejaGNU, either passed as part of
1905 @samp{RUNTESTFLAGS}, or directly to @command{runtest} if you prefer to
1906 work outside the makefiles. For example,
1909 make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fno-strength-reduce"
1912 will run the standard @command{g++} testsuites (``unix'' is the target name
1913 for a standard native testsuite situation), passing
1914 @samp{-O3 -fno-strength-reduce} to the compiler on every test, i.e.,
1915 slashes separate options.
1917 You can run the testsuites multiple times using combinations of options
1918 with a syntax similar to the brace expansion of popular shells:
1921 @dots{}"--target_board=arm-sim/@{-mhard-float,-msoft-float@}@{-O1,-O2,-O3,@}"
1924 (Note the empty option caused by the trailing comma in the final group.)
1925 The following will run each testsuite eight times using the @samp{arm-sim}
1926 target, as if you had specified all possible combinations yourself:
1929 --target_board=arm-sim/-mhard-float/-O1
1930 --target_board=arm-sim/-mhard-float/-O2
1931 --target_board=arm-sim/-mhard-float/-O3
1932 --target_board=arm-sim/-mhard-float
1933 --target_board=arm-sim/-msoft-float/-O1
1934 --target_board=arm-sim/-msoft-float/-O2
1935 --target_board=arm-sim/-msoft-float/-O3
1936 --target_board=arm-sim/-msoft-float
1939 They can be combined as many times as you wish, in arbitrary ways. This
1943 @dots{}"--target_board=unix/-Wextra@{-O3,-fno-strength-reduce@}@{-fomit-frame-pointer,@}"
1946 will generate four combinations, all involving @samp{-Wextra}.
1948 The disadvantage to this method is that the testsuites are run in serial,
1949 which is a waste on multiprocessor systems. For users with GNU Make and
1950 a shell which performs brace expansion, you can run the testsuites in
1951 parallel by having the shell perform the combinations and @command{make}
1952 do the parallel runs. Instead of using @samp{--target_board}, use a
1953 special makefile target:
1956 make -j@var{N} check-@var{testsuite}//@var{test-target}/@var{option1}/@var{option2}/@dots{}
1962 make -j3 check-gcc//sh-hms-sim/@{-m1,-m2,-m3,-m3e,-m4@}/@{,-nofpu@}
1965 will run three concurrent ``make-gcc'' testsuites, eventually testing all
1966 ten combinations as described above. Note that this is currently only
1967 supported in the @file{gcc} subdirectory. (To see how this works, try
1968 typing @command{echo} before the example given here.)
1971 @section Additional testing for Java Class Libraries
1973 The Java runtime tests can be executed via @samp{make check}
1974 in the @file{@var{target}/libjava/testsuite} directory in
1977 The @uref{http://sources.redhat.com/mauve/,,Mauve Project} provides
1978 a suite of tests for the Java Class Libraries. This suite can be run
1979 as part of libgcj testing by placing the Mauve tree within the libjava
1980 testsuite at @file{libjava/testsuite/libjava.mauve/mauve}, or by
1981 specifying the location of that tree when invoking @samp{make}, as in
1982 @samp{make MAUVEDIR=~/mauve check}.
1984 @uref{http://sources.redhat.com/mauve/jacks.html,,Jacks}
1985 is a free testsuite that tests Java compiler front ends. This suite
1986 can be run as part of libgcj testing by placing the Jacks tree within
1987 the libjava testsuite at @file{libjava/testsuite/libjava.jacks/jacks}.
1989 @section How to interpret test results
1991 The result of running the testsuite are various @file{*.sum} and @file{*.log}
1992 files in the testsuite subdirectories. The @file{*.log} files contain a
1993 detailed log of the compiler invocations and the corresponding
1994 results, the @file{*.sum} files summarize the results. These summaries
1995 contain status codes for all tests:
1999 PASS: the test passed as expected
2001 XPASS: the test unexpectedly passed
2003 FAIL: the test unexpectedly failed
2005 XFAIL: the test failed as expected
2007 UNSUPPORTED: the test is not supported on this platform
2009 ERROR: the testsuite detected an error
2011 WARNING: the testsuite detected a possible problem
2014 It is normal for some tests to report unexpected failures. At the
2015 current time the testing harness does not allow fine grained control
2016 over whether or not a test is expected to fail. This problem should
2017 be fixed in future releases.
2020 @section Submitting test results
2022 If you want to report the results to the GCC project, use the
2023 @file{contrib/test_summary} shell script. Start it in the @var{objdir} with
2026 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
2027 -m gcc-testresults@@gcc.gnu.org |sh
2030 This script uses the @command{Mail} program to send the results, so
2031 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
2032 prepended to the testsuite summary and should contain any special
2033 remarks you have on your results or your build environment. Please
2034 do not edit the testsuite result block or the subject line, as these
2035 messages may be automatically processed.
2042 @uref{./index.html,,Return to the GCC Installation page}
2046 @c ***Final install***********************************************************
2048 @comment node-name, next, previous, up
2049 @node Final install, , Testing, Installing GCC
2051 @ifset finalinstallhtml
2053 @chapter Installing GCC: Final installation
2056 Now that GCC has been built (and optionally tested), you can install it with
2058 cd @var{objdir}; make install
2061 We strongly recommend to install into a target directory where there is
2062 no previous version of GCC present.
2064 That step completes the installation of GCC; user level binaries can
2065 be found in @file{@var{prefix}/bin} where @var{prefix} is the value
2066 you specified with the @option{--prefix} to configure (or
2067 @file{/usr/local} by default). (If you specified @option{--bindir},
2068 that directory will be used instead; otherwise, if you specified
2069 @option{--exec-prefix}, @file{@var{exec-prefix}/bin} will be used.)
2070 Headers for the C++ and Java libraries are installed in
2071 @file{@var{prefix}/include}; libraries in @file{@var{libdir}}
2072 (normally @file{@var{prefix}/lib}); internal parts of the compiler in
2073 @file{@var{libdir}/gcc} and @file{@var{libexecdir}/gcc}; documentation
2074 in info format in @file{@var{infodir}} (normally
2075 @file{@var{prefix}/info}).
2077 When installing cross-compilers, GCC's executables
2078 are not only installed into @file{@var{bindir}}, that
2079 is, @file{@var{exec-prefix}/bin}, but additionally into
2080 @file{@var{exec-prefix}/@var{target-alias}/bin}, if that directory
2081 exists. Typically, such @dfn{tooldirs} hold target-specific
2082 binutils, including assembler and linker.
2084 Installation into a temporary staging area or into a @command{chroot}
2085 jail can be achieved with the command
2088 make DESTDIR=@var{path-to-rootdir} install
2091 @noindent where @var{path-to-rootdir} is the absolute path of
2092 a directory relative to which all installation paths will be
2093 interpreted. Note that the directory specified by @code{DESTDIR}
2094 need not exist yet; it will be created if necessary.
2096 There is a subtle point with tooldirs and @code{DESTDIR}:
2097 If you relocate a cross-compiler installation with
2098 e.g.@: @samp{DESTDIR=@var{rootdir}}, then the directory
2099 @file{@var{rootdir}/@var{exec-prefix}/@var{target-alias}/bin} will
2100 be filled with duplicated GCC executables only if it already exists,
2101 it will not be created otherwise. This is regarded as a feature,
2102 not as a bug, because it gives slightly more control to the packagers
2103 using the @code{DESTDIR} feature.
2105 If you are bootstrapping a released version of GCC then please
2106 quickly review the build status page for your release, available from
2107 @uref{http://gcc.gnu.org/buildstat.html}.
2108 If your system is not listed for the version of GCC that you built,
2110 @email{gcc@@gcc.gnu.org} indicating
2111 that you successfully built and installed GCC@.
2112 Include the following information:
2116 Output from running @file{@var{srcdir}/config.guess}. Do not send
2117 that file itself, just the one-line output from running it.
2120 The output of @samp{gcc -v} for your newly installed @command{gcc}.
2121 This tells us which version of GCC you built and the options you passed to
2125 Whether you enabled all languages or a subset of them. If you used a
2126 full distribution then this information is part of the configure
2127 options in the output of @samp{gcc -v}, but if you downloaded the
2128 ``core'' compiler plus additional front ends then it isn't apparent
2129 which ones you built unless you tell us about it.
2132 If the build was for GNU/Linux, also include:
2135 The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
2136 this information should be available from @file{/etc/issue}.
2139 The version of the Linux kernel, available from @samp{uname --version}
2143 The version of glibc you used; for RPM-based systems like Red Hat,
2144 Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
2145 and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
2147 For other systems, you can include similar information if you think it is
2151 Any other information that you think would be useful to people building
2152 GCC on the same configuration. The new entry in the build status list
2153 will include a link to the archived copy of your message.
2156 We'd also like to know if the
2158 @ref{Specific, host/target specific installation notes}
2161 @uref{specific.html,,host/target specific installation notes}
2163 didn't include your host/target information or if that information is
2164 incomplete or out of date. Send a note to
2165 @email{gcc@@gcc.gnu.org} detailing how the information should be changed.
2167 If you find a bug, please report it following the
2168 @uref{../bugs.html,,bug reporting guidelines}.
2170 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
2171 dvi}. You will need to have @command{texi2dvi} (version at least 4.4)
2172 and @TeX{} installed. This creates a number of @file{.dvi} files in
2173 subdirectories of @file{@var{objdir}}; these may be converted for
2174 printing with programs such as @command{dvips}. Alternately, by using
2175 @samp{make pdf} in place of @samp{make dvi}, you can create documentation
2176 in the form of @file{.pdf} files; this requires @command{texi2pdf}, which
2177 is included with Texinfo version 4.8 and later. You can also
2178 @uref{http://www.gnu.org/order/order.html,,buy printed manuals from the
2179 Free Software Foundation}, though such manuals may not be for the most
2180 recent version of GCC@.
2182 If you would like to generate online HTML documentation, do @samp{cd
2183 @var{objdir}; make html} and HTML will be generated for the gcc manuals in
2184 @file{@var{objdir}/gcc/HTML}.
2191 @uref{./index.html,,Return to the GCC Installation page}
2195 @c ***Binaries****************************************************************
2197 @comment node-name, next, previous, up
2198 @node Binaries, Specific, Installing GCC, Top
2202 @chapter Installing GCC: Binaries
2205 @cindex Installing GCC: Binaries
2207 We are often asked about pre-compiled versions of GCC@. While we cannot
2208 provide these for all platforms, below you'll find links to binaries for
2209 various platforms where creating them by yourself is not easy due to various
2212 Please note that we did not create these binaries, nor do we
2213 support them. If you have any problems installing them, please
2214 contact their makers.
2221 @uref{http://www.bullfreeware.com,,Bull's Freeware and Shareware Archive for AIX};
2224 @uref{http://aixpdslib.seas.ucla.edu,,UCLA Software Library for AIX}.
2228 DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}.
2231 Renesas H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
2232 Development Tools for the Renesas H8/300[HS] Series}.
2238 @uref{http://hpux.cs.utah.edu/,,HP-UX Porting Center};
2241 @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}.
2245 Motorola 68HC11/68HC12---@uref{http://www.gnu-m68hc11.org,,GNU
2246 Development Tools for the Motorola 68HC11/68HC12}.
2249 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
2250 OpenServer/Unixware}.
2253 Solaris 2 (SPARC, Intel)---@uref{http://www.sunfreeware.com/,,Sunfreeware}.
2256 SGI---@uref{http://freeware.sgi.com/,,SGI Freeware}.
2262 The @uref{http://sources.redhat.com/cygwin/,,Cygwin} project;
2264 The @uref{http://www.mingw.org/,,MinGW} project.
2268 @uref{ftp://ftp.thewrittenword.com/packages/by-name/,,The
2269 Written Word} offers binaries for
2272 Digital UNIX 4.0D and 5.1,
2274 HP-UX 10.20, 11.00, and 11.11, and
2275 Solaris/SPARC 2.5.1, 2.6, 7, 8, and 9.
2278 @uref{http://www.openpkg.org/,,OpenPKG} offers binaries for quite a
2279 number of platforms.
2282 The @uref{http://gcc.gnu.org/wiki/GFortranBinaries,,GFortran Wiki} has
2283 links to GNU Fortran binaries for several platforms.
2286 In addition to those specific offerings, you can get a binary
2287 distribution CD-ROM from the
2288 @uref{http://www.gnu.org/order/order.html,,Free Software Foundation}.
2289 It contains binaries for a number of platforms, and
2290 includes not only GCC, but other stuff as well. The current CD does
2291 not contain the latest version of GCC, but it should allow
2292 bootstrapping the compiler. An updated version of that disk is in the
2300 @uref{./index.html,,Return to the GCC Installation page}
2304 @c ***Specific****************************************************************
2306 @comment node-name, next, previous, up
2307 @node Specific, Old, Binaries, Top
2311 @chapter Host/target specific installation notes for GCC
2314 @cindex Specific installation notes
2315 @cindex Target specific installation
2316 @cindex Host specific installation
2317 @cindex Target specific installation notes
2319 Please read this document carefully @emph{before} installing the
2320 GNU Compiler Collection on your machine.
2322 Note that this list of install notes is @emph{not} a list of supported
2323 hosts or targets. Not all supported hosts and targets are listed
2324 here, only the ones that require host-specific or target-specific
2330 @uref{#alpha-x-x,,alpha*-*-*}
2332 @uref{#alpha-dec-osf,,alpha*-dec-osf*}
2334 @uref{#alphaev5-cray-unicosmk,,alphaev5-cray-unicosmk*}
2336 @uref{#arc-x-elf,,arc-*-elf}
2338 @uref{#arm-x-elf,,arm-*-elf}
2339 @uref{#arm-x-coff,,arm-*-coff}
2340 @uref{#arm-x-aout,,arm-*-aout}
2342 @uref{#xscale-x-x,,xscale-*-*}
2346 @uref{#bfin,,Blackfin}
2352 @uref{#x-x-freebsd,,*-*-freebsd*}
2354 @uref{#h8300-hms,,h8300-hms}
2356 @uref{#hppa-hp-hpux,,hppa*-hp-hpux*}
2358 @uref{#hppa-hp-hpux10,,hppa*-hp-hpux10}
2360 @uref{#hppa-hp-hpux11,,hppa*-hp-hpux11}
2362 @uref{#x-x-linux-gnu,,*-*-linux-gnu}
2364 @uref{#ix86-x-linuxaout,,i?86-*-linux*aout}
2366 @uref{#ix86-x-linux,,i?86-*-linux*}
2368 @uref{#ix86-x-sco32v5,,i?86-*-sco3.2v5*}
2370 @uref{#ix86-x-solaris210,,i?86-*-solaris2.10}
2372 @uref{#ix86-x-udk,,i?86-*-udk}
2374 @uref{#ia64-x-linux,,ia64-*-linux}
2376 @uref{#ia64-x-hpux,,ia64-*-hpux*}
2378 @uref{#x-ibm-aix,,*-ibm-aix*}
2380 @uref{#iq2000-x-elf,,iq2000-*-elf}
2382 @uref{#m32c-x-elf,,m32c-*-elf}
2384 @uref{#m32r-x-elf,,m32r-*-elf}
2386 @uref{#m6811-elf,,m6811-elf}
2388 @uref{#m6812-elf,,m6812-elf}
2390 @uref{#m68k-hp-hpux,,m68k-hp-hpux}
2392 @uref{#mips-x-x,,mips-*-*}
2394 @uref{#mips-sgi-irix5,,mips-sgi-irix5}
2396 @uref{#mips-sgi-irix6,,mips-sgi-irix6}
2398 @uref{#powerpc-x-x,,powerpc*-*-*, powerpc-*-sysv4}
2400 @uref{#powerpc-x-darwin,,powerpc-*-darwin*}
2402 @uref{#powerpc-x-elf,,powerpc-*-elf, powerpc-*-sysv4}
2404 @uref{#powerpc-x-linux-gnu,,powerpc*-*-linux-gnu*}
2406 @uref{#powerpc-x-netbsd,,powerpc-*-netbsd*}
2408 @uref{#powerpc-x-eabisim,,powerpc-*-eabisim}
2410 @uref{#powerpc-x-eabi,,powerpc-*-eabi}
2412 @uref{#powerpcle-x-elf,,powerpcle-*-elf, powerpcle-*-sysv4}
2414 @uref{#powerpcle-x-eabisim,,powerpcle-*-eabisim}
2416 @uref{#powerpcle-x-eabi,,powerpcle-*-eabi}
2418 @uref{#s390-x-linux,,s390-*-linux*}
2420 @uref{#s390x-x-linux,,s390x-*-linux*}
2422 @uref{#s390x-ibm-tpf,,s390x-ibm-tpf*}
2424 @uref{#x-x-solaris2,,*-*-solaris2*}
2426 @uref{#sparc-sun-solaris2,,sparc-sun-solaris2*}
2428 @uref{#sparc-sun-solaris27,,sparc-sun-solaris2.7}
2430 @uref{#sparc-x-linux,,sparc-*-linux*}
2432 @uref{#sparc64-x-solaris2,,sparc64-*-solaris2*}
2434 @uref{#sparcv9-x-solaris2,,sparcv9-*-solaris2*}
2436 @uref{#x-x-sysv,,*-*-sysv*}
2438 @uref{#vax-dec-ultrix,,vax-dec-ultrix}
2440 @uref{#x-x-vxworks,,*-*-vxworks*}
2442 @uref{#x86-64-x-x,,x86_64-*-*, amd64-*-*}
2444 @uref{#xtensa-x-elf,,xtensa-*-elf}
2446 @uref{#xtensa-x-linux,,xtensa-*-linux*}
2448 @uref{#windows,,Microsoft Windows}
2452 @uref{#older,,Older systems}
2457 @uref{#elf,,all ELF targets} (SVR4, Solaris 2, etc.)
2463 <!-- -------- host/target specific issues start here ---------------- -->
2466 @heading @anchor{alpha-x-x}alpha*-*-*
2468 This section contains general configuration information for all
2469 alpha-based platforms using ELF (in particular, ignore this section for
2470 DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
2471 section, please read all other sections that match your target.
2473 We require binutils 2.11.2 or newer.
2474 Previous binutils releases had a number of problems with DWARF 2
2475 debugging information, not the least of which is incorrect linking of
2481 @heading @anchor{alpha-dec-osf}alpha*-dec-osf*
2482 Systems using processors that implement the DEC Alpha architecture and
2483 are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq
2484 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
2486 As of GCC 3.2, versions before @code{alpha*-dec-osf4} are no longer
2487 supported. (These are the versions which identify themselves as DEC
2490 In Digital Unix V4.0, virtual memory exhausted bootstrap failures
2491 may be fixed by configuring with @option{--with-gc=simple},
2492 reconfiguring Kernel Virtual Memory and Swap parameters
2493 per the @command{/usr/sbin/sys_check} Tuning Suggestions,
2494 or applying the patch in
2495 @uref{http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html}.
2497 In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
2498 currently (2001-06-13) work with @command{mips-tfile}. As a workaround,
2499 we need to use the old assembler, invoked via the barely documented
2500 @option{-oldas} option. To bootstrap GCC, you either need to use the
2504 % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}]
2507 or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
2510 % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}]
2513 As of GNU binutils 2.11.2, neither GNU @command{as} nor GNU @command{ld}
2514 are supported on Tru64 UNIX, so you must not configure GCC with
2515 @option{--with-gnu-as} or @option{--with-gnu-ld}.
2517 GCC writes a @samp{.verstamp} directive to the assembler output file
2518 unless it is built as a cross-compiler. It gets the version to use from
2519 the system header file @file{/usr/include/stamp.h}. If you install a
2520 new version of DEC Unix, you should rebuild GCC to pick up the new version
2523 Note that since the Alpha is a 64-bit architecture, cross-compilers from
2524 32-bit machines will not generate code as efficient as that generated
2525 when the compiler is running on a 64-bit machine because many
2526 optimizations that depend on being able to represent a word on the
2527 target in an integral value on the host cannot be performed. Building
2528 cross-compilers on the Alpha for 32-bit machines has only been tested in
2529 a few cases and may not work properly.
2531 @samp{make compare} may fail on old versions of DEC Unix unless you add
2532 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
2533 assembler input file is stored in the object file, and that makes
2534 comparison fail if it differs between the @code{stage1} and
2535 @code{stage2} compilations. The option @option{-save-temps} forces a
2536 fixed name to be used for the assembler input file, instead of a
2537 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
2538 unless the comparisons fail without that option. If you add
2539 @option{-save-temps}, you will have to manually delete the @samp{.i} and
2540 @samp{.s} files after each series of compilations.
2542 GCC now supports both the native (ECOFF) debugging format used by DBX
2543 and GDB and an encapsulated STABS format for use only with GDB@. See the
2544 discussion of the @option{--with-stabs} option of @file{configure} above
2545 for more information on these formats and how to select them.
2547 There is a bug in DEC's assembler that produces incorrect line numbers
2548 for ECOFF format when the @samp{.align} directive is used. To work
2549 around this problem, GCC will not emit such alignment directives
2550 while writing ECOFF format debugging information even if optimization is
2551 being performed. Unfortunately, this has the very undesirable
2552 side-effect that code addresses when @option{-O} is specified are
2553 different depending on whether or not @option{-g} is also specified.
2555 To avoid this behavior, specify @option{-gstabs+} and use GDB instead of
2556 DBX@. DEC is now aware of this problem with the assembler and hopes to
2557 provide a fix shortly.
2562 @heading @anchor{alphaev5-cray-unicosmk}alphaev5-cray-unicosmk*
2563 Cray T3E systems running Unicos/Mk.
2565 This port is incomplete and has many known bugs. We hope to improve the
2566 support for this target soon. Currently, only the C front end is supported,
2567 and it is not possible to build parallel applications. Cray modules are not
2568 supported; in particular, Craylibs are assumed to be in
2569 @file{/opt/ctl/craylibs/craylibs}.
2571 On this platform, you need to tell GCC where to find the assembler and
2572 the linker. The simplest way to do so is by providing @option{--with-as}
2573 and @option{--with-ld} to @file{configure}, e.g.@:
2576 configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld \
2577 --enable-languages=c
2580 The comparison test at the end of the bootstrapping process fails on Unicos/Mk
2581 because the assembler inserts timestamps into object files. You should
2582 be able to work around this by doing @samp{make all} after getting this
2588 @heading @anchor{arc-x-elf}arc-*-elf
2589 Argonaut ARC processor.
2590 This configuration is intended for embedded systems.
2595 @heading @anchor{arm-x-elf}arm-*-elf
2596 @heading @anchor{xscale-x-x}xscale-*-*
2597 ARM-family processors. Subtargets that use the ELF object format
2598 require GNU binutils 2.13 or newer. Such subtargets include:
2599 @code{arm-*-freebsd}, @code{arm-*-netbsdelf}, @code{arm-*-*linux},
2600 @code{arm-*-rtems} and @code{arm-*-kaos}.
2605 @heading @anchor{arm-x-coff}arm-*-coff
2606 ARM-family processors. Note that there are two different varieties
2607 of PE format subtarget supported: @code{arm-wince-pe} and
2608 @code{arm-pe} as well as a standard COFF target @code{arm-*-coff}.
2613 @heading @anchor{arm-x-aout}arm-*-aout
2614 ARM-family processors. These targets support the AOUT file format:
2615 @code{arm-*-aout}, @code{arm-*-netbsd}.
2620 @heading @anchor{avr}avr
2622 ATMEL AVR-family micro controllers. These are used in embedded
2623 applications. There are no standard Unix configurations.
2625 @xref{AVR Options,, AVR Options, gcc, Using the GNU Compiler
2629 See ``AVR Options'' in the main manual
2631 for the list of supported MCU types.
2633 Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
2635 Further installation notes and other useful information about AVR tools
2636 can also be obtained from:
2640 @uref{http://www.nongnu.org/avr/,,http://www.nongnu.org/avr/}
2642 @uref{http://home.overta.ru/users/denisc/,,http://home.overta.ru/users/denisc/}
2644 @uref{http://www.amelek.gda.pl/avr/,,http://www.amelek.gda.pl/avr/}
2647 We @emph{strongly} recommend using binutils 2.13 or newer.
2649 The following error:
2651 Error: register required
2654 indicates that you should upgrade to a newer version of the binutils.
2659 @heading @anchor{bfin}Blackfin
2661 The Blackfin processor, an Analog Devices DSP.
2663 @xref{Blackfin Options,, Blackfin Options, gcc, Using the GNU Compiler
2667 See ``Blackfin Options'' in the main manual
2670 More information, and a version of binutils with support for this processor,
2671 is available at @uref{http://blackfin.uclinux.org}
2676 @heading @anchor{c4x}c4x
2678 Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal
2679 Processors. These are used in embedded applications. There are no
2680 standard Unix configurations.
2682 @xref{TMS320C3x/C4x Options,, TMS320C3x/C4x Options, gcc, Using the
2683 GNU Compiler Collection (GCC)},
2686 See ``TMS320C3x/C4x Options'' in the main manual
2688 for the list of supported MCU types.
2690 GCC can be configured as a cross compiler for both the C3x and C4x
2691 architectures on the same system. Use @samp{configure --target=c4x
2692 --enable-languages="c,c++"} to configure.
2695 Further installation notes and other useful information about C4x tools
2696 can also be obtained from:
2700 @uref{http://www.elec.canterbury.ac.nz/c4x/,,http://www.elec.canterbury.ac.nz/c4x/}
2706 @heading @anchor{cris}CRIS
2708 CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
2709 series. These are used in embedded applications.
2712 @xref{CRIS Options,, CRIS Options, gcc, Using the GNU Compiler
2716 See ``CRIS Options'' in the main manual
2718 for a list of CRIS-specific options.
2720 There are a few different CRIS targets:
2722 @item cris-axis-aout
2723 Old target. Includes a multilib for the @samp{elinux} a.out-based
2724 target. No multilibs for newer architecture variants.
2726 Mainly for monolithic embedded systems. Includes a multilib for the
2727 @samp{v10} core used in @samp{ETRAX 100 LX}.
2728 @item cris-axis-linux-gnu
2729 A GNU/Linux port for the CRIS architecture, currently targeting
2730 @samp{ETRAX 100 LX} by default.
2733 For @code{cris-axis-aout} and @code{cris-axis-elf} you need binutils 2.11
2734 or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer.
2736 Pre-packaged tools can be obtained from
2737 @uref{ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/}. More
2738 information about this platform is available at
2739 @uref{http://developer.axis.com/}.
2744 @heading @anchor{crx}CRX
2746 The CRX CompactRISC architecture is a low-power 32-bit architecture with
2747 fast context switching and architectural extensibility features.
2750 @xref{CRX Options,, CRX Options, gcc, Using and Porting the GNU Compiler
2755 See ``CRX Options'' in the main manual for a list of CRX-specific options.
2758 Use @samp{configure --target=crx-elf --enable-languages=c,c++} to configure
2759 GCC@ for building a CRX cross-compiler. The option @samp{--target=crx-elf}
2760 is also used to build the @samp{newlib} C library for CRX.
2762 It is also possible to build libstdc++-v3 for the CRX architecture. This
2763 needs to be done in a separate step with the following configure settings:
2764 @samp{gcc/libstdc++-v3/configure --host=crx-elf --with-newlib
2765 --enable-sjlj-exceptions --enable-cxx-flags='-fexceptions -frtti'}
2770 @heading @anchor{dos}DOS
2772 Please have a look at the @uref{binaries.html,,binaries page}.
2774 You cannot install GCC by itself on MSDOS; it will not compile under
2775 any MSDOS compiler except itself. You need to get the complete
2776 compilation package DJGPP, which includes binaries as well as sources,
2777 and includes all the necessary compilation tools and libraries.
2782 @heading @anchor{x-x-freebsd}*-*-freebsd*
2784 The version of binutils installed in @file{/usr/bin} probably works with
2785 this release of GCC@. However, on FreeBSD 4, bootstrapping against the
2786 latest FSF binutils is known to improve overall testsuite results; and,
2787 on FreeBSD/alpha, using binutils 2.14 or later is required to build libjava.
2789 Support for FreeBSD 1 was discontinued in GCC 3.2.
2791 Support for FreeBSD 2 will be discontinued after GCC 3.4. The
2792 following was true for GCC 3.1 but the current status is unknown.
2793 For FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
2794 configuration support and files as shipped with GCC 2.95 are still in
2795 place. FreeBSD 2.2.7 has been known to bootstrap completely; however,
2796 it is unknown which version of binutils was used (it is assumed that it
2797 was the system copy in @file{/usr/bin}) and C++ EH failures were noted.
2799 For FreeBSD using the ELF file format: DWARF 2 debugging is now the
2800 default for all CPU architectures. It had been the default on
2801 FreeBSD/alpha since its inception. You may use @option{-gstabs} instead
2802 of @option{-g}, if you really want the old debugging format. There are
2803 no known issues with mixing object files and libraries with different
2804 debugging formats. Otherwise, this release of GCC should now match more
2805 of the configuration used in the stock FreeBSD configuration of GCC@. In
2806 particular, @option{--enable-threads} is now configured by default.
2807 However, as a general user, do not attempt to replace the system
2808 compiler with this release. Known to bootstrap and check with good
2809 results on FreeBSD 4.9-STABLE and 5-CURRENT@. In the past, known to
2810 bootstrap and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2,
2811 4.3, 4.4, 4.5, 4.8-STABLE@.
2813 In principle, @option{--enable-threads} is now compatible with
2814 @option{--enable-libgcj} on FreeBSD@. However, it has only been built
2815 and tested on @samp{i386-*-freebsd[45]} and @samp{alpha-*-freebsd[45]}.
2817 library may be incorrectly built (symbols are missing at link time).
2818 There is a rare timing-based startup hang (probably involves an
2819 assumption about the thread library). Multi-threaded boehm-gc (required for
2820 libjava) exposes severe threaded signal-handling bugs on FreeBSD before
2821 4.5-RELEASE@. Other CPU architectures
2822 supported by FreeBSD will require additional configuration tuning in, at
2823 the very least, both boehm-gc and libffi.
2825 Shared @file{libgcc_s.so} is now built and installed by default.
2830 @heading @anchor{h8300-hms}h8300-hms
2831 Renesas H8/300 series of processors.
2833 Please have a look at the @uref{binaries.html,,binaries page}.
2835 The calling convention and structure layout has changed in release 2.6.
2836 All code must be recompiled. The calling convention now passes the
2837 first three arguments in function calls in registers. Structures are no
2838 longer a multiple of 2 bytes.
2843 @heading @anchor{hppa-hp-hpux}hppa*-hp-hpux*
2844 Support for HP-UX version 9 and older was discontinued in GCC 3.4.
2846 We require using gas/binutils on all hppa platforms;
2847 you may encounter a variety of problems if you try to use the HP assembler.
2849 Specifically, @option{-g} does not work on HP-UX (since that system
2850 uses a peculiar debugging format which GCC does not know about), unless
2851 you use GAS and GDB@. It may be helpful to configure GCC with the
2852 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
2853 @option{--with-as=@dots{}} options to ensure that GCC can find GAS@.
2855 If you wish to use the pa-risc 2.0 architecture support with a 32-bit
2856 runtime, you must use gas/binutils 2.11 or newer.
2858 There are two default scheduling models for instructions. These are
2859 PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
2860 architecture specified for the target machine when configuring.
2861 PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
2862 the target is a @samp{hppa1*} machine.
2864 The PROCESSOR_8000 model is not well suited to older processors. Thus,
2865 it is important to completely specify the machine architecture when
2866 configuring if you want a model other than PROCESSOR_8000. The macro
2867 TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
2868 default scheduling model is desired.
2870 As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10
2871 through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later.
2872 This namespace change might cause problems when bootstrapping with
2873 an earlier version of GCC or the HP compiler as essentially the same
2874 namespace is required for an entire build. This problem can be avoided
2875 in a number of ways. With HP cc, @env{UNIX_STD} can be set to @samp{95}
2876 or @samp{98}. Another way is to add an appropriate set of predefines
2877 to @env{CC}. The description for the @option{munix=} option contains
2878 a list of the predefines used with each standard.
2880 As of GCC 4.1, @env{DWARF2} exception handling is available on HP-UX.
2881 It is now the default. This exposed a bug in the handling of data
2882 relocations in the GAS assembler. The handling of 64-bit data relocations
2883 was seriously broken, affecting debugging and exception support on all
2884 @samp{hppa64-*-*} targets. Under some circumstances, 32-bit data relocations
2885 could also be handled incorrectly. This problem is fixed in GAS version
2888 GCC versions prior to 4.1 incorrectly passed and returned complex
2889 values. They are now passed in the same manner as aggregates.
2891 More specific information to @samp{hppa*-hp-hpux*} targets follows.
2896 @heading @anchor{hppa-hp-hpux10}hppa*-hp-hpux10
2898 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
2899 @code{PHCO_19798} from HP@. HP has two sites which provide patches free of
2905 <a href="http://us.itrc.hp.com/service/home/home.do">US, Canada, Asia-Pacific, and
2909 @uref{http://us.itrc.hp.com/service/home/home.do,,} US, Canada, Asia-Pacific,
2913 @uref{http://europe.itrc.hp.com/service/home/home.do,,} Europe.
2916 The HP assembler on these systems has some problems. Most notably the
2917 assembler inserts timestamps into each object file it creates, causing
2918 the 3-stage comparison test to fail during a bootstrap.
2919 You should be able to continue by saying @samp{make all-host all-target}
2920 after getting the failure from @samp{make}.
2922 GCC 4.0 requires CVS binutils as of April 28, 2004 or later. Earlier
2923 versions require binutils 2.8 or later.
2925 The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces are
2926 used for one-only code and data. This resolves many of the previous
2927 problems in using C++ on this target. However, the ABI is not compatible
2928 with the one implemented under HP-UX 11 using secondary definitions.
2933 @heading @anchor{hppa-hp-hpux11}hppa*-hp-hpux11
2935 GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot
2936 be used to compile GCC 3.0 and up.
2938 Refer to @uref{binaries.html,,binaries} for information about obtaining
2939 precompiled GCC binaries for HP-UX@. Precompiled binaries must be obtained
2940 to build the Ada language as it can't be bootstrapped using C@. Ada is
2941 only available for the 32-bit PA-RISC runtime. The libffi and libjava
2942 haven't been ported to HP-UX and don't build.
2944 Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The
2945 bundled compiler supports only traditional C; you will need either HP's
2946 unbundled compiler, or a binary distribution of GCC@.
2948 It is possible to build GCC 3.3 starting with the bundled HP compiler,
2949 but the process requires several steps. GCC 3.3 can then be used to
2950 build later versions. The fastjar program contains ISO C code and
2951 can't be built with the HP bundled compiler. This problem can be
2952 avoided by not building the Java language. For example, use the
2953 @option{--enable-languages="c,c++,f77,objc"} option in your configure
2956 There are several possible approaches to building the distribution.
2957 Binutils can be built first using the HP tools. Then, the GCC
2958 distribution can be built. The second approach is to build GCC
2959 first using the HP tools, then build binutils, then rebuild GCC@.
2960 There have been problems with various binary distributions, so it
2961 is best not to start from a binary distribution.
2963 On 64-bit capable systems, there are two distinct targets. Different
2964 installation prefixes must be used if both are to be installed on
2965 the same system. The @samp{hppa[1-2]*-hp-hpux11*} target generates code
2966 for the 32-bit PA-RISC runtime architecture and uses the HP linker.
2967 The @samp{hppa64-hp-hpux11*} target generates 64-bit code for the
2968 PA-RISC 2.0 architecture. The HP and GNU linkers are both supported
2971 The script config.guess now selects the target type based on the compiler
2972 detected during configuration. You must define @env{PATH} or @env{CC} so
2973 that configure finds an appropriate compiler for the initial bootstrap.
2974 When @env{CC} is used, the definition should contain the options that are
2975 needed whenever @env{CC} is used.
2977 Specifically, options that determine the runtime architecture must be
2978 in @env{CC} to correctly select the target for the build. It is also
2979 convenient to place many other compiler options in @env{CC}. For example,
2980 @env{CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"}
2981 can be used to bootstrap the GCC 3.3 branch with the HP compiler in
2982 64-bit K&R/bundled mode. The @option{+DA2.0W} option will result in
2983 the automatic selection of the @samp{hppa64-hp-hpux11*} target. The
2984 macro definition table of cpp needs to be increased for a successful
2985 build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to
2986 be defined when building with the bundled compiler, or when using the
2987 @option{-Ac} option. These defines aren't necessary with @option{-Ae}.
2989 It is best to explicitly configure the @samp{hppa64-hp-hpux11*} target
2990 with the @option{--with-ld=@dots{}} option. This overrides the standard
2991 search for ld. The two linkers supported on this target require different
2992 commands. The default linker is determined during configuration. As a
2993 result, it's not possible to switch linkers in the middle of a GCC build.
2994 This has been been reported to sometimes occur in unified builds of
2997 GCC 3.0 through 3.2 require binutils 2.11 or above. GCC 3.3 through
2998 GCC 4.0 require binutils 2.14 or later.
3000 Although the HP assembler can be used for an initial build, it shouldn't
3001 be used with any languages other than C and perhaps Fortran due to its
3002 many limitations. For example, it does not support weak symbols or alias
3003 definitions. As a result, explicit template instantiations are required
3004 when using C++. This makes it difficult if not impossible to build many
3005 C++ applications. You can't generate debugging information when using
3006 the HP assembler. Finally, bootstrapping fails in the final
3007 comparison of object modules due to the time stamps that it inserts into
3008 the modules. The bootstrap can be continued from this point with
3009 @samp{make all-host all-target}.
3011 A recent linker patch must be installed for the correct operation of
3012 GCC 3.3 and later. @code{PHSS_26559} and @code{PHSS_24304} are the
3013 oldest linker patches that are known to work. They are for HP-UX
3014 11.00 and 11.11, respectively. @code{PHSS_24303}, the companion to
3015 @code{PHSS_24304}, might be usable but it hasn't been tested. These
3016 patches have been superseded. Consult the HP patch database to obtain
3017 the currently recommended linker patch for your system.
3019 The patches are necessary for the support of weak symbols on the
3020 32-bit port, and for the running of initializers and finalizers. Weak
3021 symbols are implemented using SOM secondary definition symbols. Prior
3022 to HP-UX 11, there are bugs in the linker support for secondary symbols.
3023 The patches correct a problem of linker core dumps creating shared
3024 libraries containing secondary symbols, as well as various other
3025 linking issues involving secondary symbols.
3027 GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
3028 run initializers and finalizers on the 64-bit port. The 32-bit port
3029 uses the linker @option{+init} and @option{+fini} options for the same
3030 purpose. The patches correct various problems with the +init/+fini
3031 options, including program core dumps. Binutils 2.14 corrects a
3032 problem on the 64-bit port resulting from HP's non-standard use of
3033 the .init and .fini sections for array initializers and finalizers.
3035 There are a number of issues to consider in selecting which linker to
3036 use with the 64-bit port. The GNU 64-bit linker can only create dynamic
3037 binaries. The @option{-static} option causes linking with archive
3038 libraries but doesn't produce a truly static binary. Dynamic binaries
3039 still require final binding by the dynamic loader to resolve a set of
3040 dynamic-loader-defined symbols. The default behavior of the HP linker
3041 is the same as the GNU linker. However, it can generate true 64-bit
3042 static binaries using the @option{+compat} option.
3044 The HP 64-bit linker doesn't support linkonce semantics. As a
3045 result, C++ programs have many more sections than they should.
3047 The GNU 64-bit linker has some issues with shared library support
3048 and exceptions. As a result, we only support libgcc in archive
3049 format. For similar reasons, dwarf2 unwind and exception support
3050 are disabled. The GNU linker also has problems creating binaries
3051 with @option{-static}. It doesn't provide stubs for internal
3052 calls to global functions in shared libraries, so these calls
3053 can't be overloaded.
3055 Thread support is not implemented in GCC 3.0 through 3.2, so the
3056 @option{--enable-threads} configure option does not work. In 3.3
3057 and later, POSIX threads are supported. The optional DCE thread
3058 library is not supported.
3060 This port still is undergoing significant development.
3065 @heading @anchor{x-x-linux-gnu}*-*-linux-gnu
3067 Versions of libstdc++-v3 starting with 3.2.1 require bugfixes present
3068 in glibc 2.2.5 and later. More information is available in the
3069 libstdc++-v3 documentation.
3074 @heading @anchor{ix86-x-linuxaout}i?86-*-linux*aout
3075 Use this configuration to generate @file{a.out} binaries on Linux-based
3076 GNU systems. This configuration is being superseded.
3081 @heading @anchor{ix86-x-linux}i?86-*-linux*
3083 As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
3084 See @uref{http://gcc.gnu.org/PR10877,,bug 10877} for more information.
3086 If you receive Signal 11 errors when building on GNU/Linux, then it is
3087 possible you have a hardware problem. Further information on this can be
3088 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
3093 @heading @anchor{ix86-x-sco32v5}i?86-*-sco3.2v5*
3094 Use this for the SCO OpenServer Release 5 family of operating systems.
3096 Unlike earlier versions of GCC, the ability to generate COFF with this
3097 target is no longer provided.
3099 Earlier versions of GCC emitted DWARF 1 when generating ELF to allow
3100 the system debugger to be used. That support was too burdensome to
3101 maintain. GCC now emits only DWARF 2 for this target. This means you
3102 may use either the UDK debugger or GDB to debug programs built by this
3105 GCC is now only supported on releases 5.0.4 and later, and requires that
3106 you install Support Level Supplement OSS646B or later, and Support Level
3107 Supplement OSS631C or later. If you are using release 5.0.7 of
3108 OpenServer, you must have at least the first maintenance pack installed
3109 (this includes the relevant portions of OSS646). OSS646, also known as
3110 the ``Execution Environment Update'', provides updated link editors and
3111 assemblers, as well as updated standard C and math libraries. The C
3112 startup modules are also updated to support the System V gABI draft, and
3113 GCC relies on that behavior. OSS631 provides a collection of commonly
3114 used open source libraries, some of which GCC depends on (such as GNU
3115 gettext and zlib). SCO OpenServer Release 5.0.7 has all of this built
3116 in by default, but OSS631C and later also apply to that release. Please
3118 @uref{ftp://ftp.sco.com/pub/openserver5,,ftp://ftp.sco.com/pub/openserver5}
3119 for the latest versions of these (and other potentially useful)
3122 Although there is support for using the native assembler, it is
3123 recommended that you configure GCC to use the GNU assembler. You do
3124 this by using the flags
3125 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}}. You should
3126 use a modern version of GNU binutils. Version 2.13.2.1 was used for all
3127 testing. In general, only the @option{--with-gnu-as} option is tested.
3128 A modern bintuils (as well as a plethora of other development related
3129 GNU utilities) can be found in Support Level Supplement OSS658A, the
3130 ``GNU Development Tools'' package. See the SCO web and ftp sites for details.
3131 That package also contains the currently ``officially supported'' version of
3132 GCC, version 2.95.3. It is useful for bootstrapping this version.
3137 @heading @anchor{ix86-x-solaris210}i?86-*-solaris2.10
3138 Use this for Solaris 10 or later on x86 and x86-64 systems. This
3139 configuration is supported by GCC 4.0 and later versions only.
3141 It is recommended that you configure GCC to use the GNU assembler in
3142 @file{/usr/sfw/bin/gas} but the Sun linker, using the options
3143 @option{--with-gnu-as --with-as=/usr/sfw/bin/gas --without-gnu-ld
3144 --with-ld=/usr/ccs/bin/ld}.
3149 @heading @anchor{ix86-x-udk}i?86-*-udk
3151 This target emulates the SCO Universal Development Kit and requires that
3152 package be installed. (If it is installed, you will have a
3153 @file{/udk/usr/ccs/bin/cc} file present.) It's very much like the
3154 @samp{i?86-*-unixware7*} target
3155 but is meant to be used when hosting on a system where UDK isn't the
3156 default compiler such as OpenServer 5 or Unixware 2. This target will
3157 generate binaries that will run on OpenServer, Unixware 2, or Unixware 7,
3158 with the same warnings and caveats as the SCO UDK@.
3160 This target is a little tricky to build because we have to distinguish
3161 it from the native tools (so it gets headers, startups, and libraries
3162 from the right place) while making the tools not think we're actually
3163 building a cross compiler. The easiest way to do this is with a configure
3167 CC=/udk/usr/ccs/bin/cc @var{/your/path/to}/gcc/configure \
3168 --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-
3171 @emph{You should substitute @samp{i686} in the above command with the appropriate
3172 processor for your host.}
3174 After the usual @samp{make} and
3175 @samp{make install}, you can then access the UDK-targeted GCC
3176 tools by adding @command{udk-} before the commonly known name. For
3177 example, to invoke the C compiler, you would use @command{udk-gcc}.
3178 They will coexist peacefully with any native-target GCC tools you may
3185 @heading @anchor{ia64-x-linux}ia64-*-linux
3186 IA-64 processor (also known as IPF, or Itanium Processor Family)
3189 If you are using the installed system libunwind library with
3190 @option{--with-system-libunwind}, then you must use libunwind 0.98 or
3193 None of the following versions of GCC has an ABI that is compatible
3194 with any of the other versions in this list, with the exception that
3195 Red Hat 2.96 and Trillian 000171 are compatible with each other:
3196 3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
3197 This primarily affects C++ programs and programs that create shared libraries.
3198 GCC 3.1 or later is recommended for compiling linux, the kernel.
3199 As of version 3.1 GCC is believed to be fully ABI compliant, and hence no
3200 more major ABI changes are expected.
3205 @heading @anchor{ia64-x-hpux}ia64-*-hpux*
3206 Building GCC on this target requires the GNU Assembler. The bundled HP
3207 assembler will not work. To prevent GCC from using the wrong assembler,
3208 the option @option{--with-gnu-as} may be necessary.
3210 The GCC libunwind library has not been ported to HPUX@. This means that for
3211 GCC versions 3.2.3 and earlier, @option{--enable-libunwind-exceptions}
3212 is required to build GCC@. For GCC 3.3 and later, this is the default.
3213 For gcc 3.4.3 and later, @option{--enable-libunwind-exceptions} is
3214 removed and the system libunwind library will always be used.
3218 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
3220 @heading @anchor{x-ibm-aix}*-ibm-aix*
3221 Support for AIX version 3 and older was discontinued in GCC 3.4.
3223 ``out of memory'' bootstrap failures may indicate a problem with
3224 process resource limits (ulimit). Hard limits are configured in the
3225 @file{/etc/security/limits} system configuration file.
3227 To speed up the configuration phases of bootstrapping and installing GCC,
3228 one may use GNU Bash instead of AIX @command{/bin/sh}, e.g.,
3231 % CONFIG_SHELL=/opt/freeware/bin/bash
3232 % export CONFIG_SHELL
3235 and then proceed as described in @uref{build.html,,the build
3236 instructions}, where we strongly recommend specifying an absolute path
3237 to invoke @var{srcdir}/configure.
3239 Because GCC on AIX is built as a 32-bit executable by default,
3240 (although it can generate 64-bit programs) the GMP and MPFR libraries
3241 required by gfortran must be 32-bit libraries. Building GMP and MPFR
3242 as static archive libraries works better than shared libraries.
3244 Errors involving @code{alloca} when building GCC generally are due
3245 to an incorrect definition of @code{CC} in the Makefile or mixing files
3246 compiled with the native C compiler and GCC@. During the stage1 phase of
3247 the build, the native AIX compiler @strong{must} be invoked as @command{cc}
3248 (not @command{xlc}). Once @command{configure} has been informed of
3249 @command{xlc}, one needs to use @samp{make distclean} to remove the
3250 configure cache files and ensure that @env{CC} environment variable
3251 does not provide a definition that will confuse @command{configure}.
3252 If this error occurs during stage2 or later, then the problem most likely
3253 is the version of Make (see above).
3255 The native @command{as} and @command{ld} are recommended for bootstrapping
3256 on AIX 4 and required for bootstrapping on AIX 5L@. The GNU Assembler
3257 reports that it supports WEAK symbols on AIX 4, which causes GCC to try to
3258 utilize weak symbol functionality although it is not supported. The GNU
3259 Assembler and Linker do not support AIX 5L sufficiently to bootstrap GCC@.
3260 The native AIX tools do interoperate with GCC@.
3262 Building @file{libstdc++.a} requires a fix for an AIX Assembler bug
3263 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a
3264 fix for another AIX Assembler bug and a co-dependent AIX Archiver fix
3265 referenced as APAR IY53606 (AIX 5.2) or a APAR IY54774 (AIX 5.1)
3267 @samp{libstdc++} in GCC 3.4 increments the major version number of the
3268 shared object and GCC installation places the @file{libstdc++.a}
3269 shared library in a common location which will overwrite the and GCC
3270 3.3 version of the shared library. Applications either need to be
3271 re-linked against the new shared library or the GCC 3.1 and GCC 3.3
3272 versions of the @samp{libstdc++} shared object needs to be available
3273 to the AIX runtime loader. The GCC 3.1 @samp{libstdc++.so.4}, if
3274 present, and GCC 3.3 @samp{libstdc++.so.5} shared objects can be
3275 installed for runtime dynamic loading using the following steps to set
3276 the @samp{F_LOADONLY} flag in the shared object for @emph{each}
3277 multilib @file{libstdc++.a} installed:
3279 Extract the shared objects from the currently installed
3280 @file{libstdc++.a} archive:
3282 % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
3285 Enable the @samp{F_LOADONLY} flag so that the shared object will be
3286 available for runtime dynamic loading, but not linking:
3288 % strip -e libstdc++.so.4 libstdc++.so.5
3291 Archive the runtime-only shared object in the GCC 3.4
3292 @file{libstdc++.a} archive:
3294 % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
3297 Linking executables and shared libraries may produce warnings of
3298 duplicate symbols. The assembly files generated by GCC for AIX always
3299 have included multiple symbol definitions for certain global variable
3300 and function declarations in the original program. The warnings should
3301 not prevent the linker from producing a correct library or runnable
3304 AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
3305 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
3306 to parse archive libraries did not handle the new format correctly.
3307 These routines are used by GCC and result in error messages during
3308 linking such as ``not a COFF file''. The version of the routines shipped
3309 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
3310 option of the archive command may be used to create archives of 32-bit
3311 objects using the original ``small format''. A correct version of the
3312 routines is shipped with AIX 4.3.2 and above.
3314 Some versions of the AIX binder (linker) can fail with a relocation
3315 overflow severe error when the @option{-bbigtoc} option is used to link
3316 GCC-produced object files into an executable that overflows the TOC@. A fix
3317 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
3318 available from IBM Customer Support and from its
3319 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3320 website as PTF U455193.
3322 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
3323 with a segmentation fault when invoked by any version of GCC@. A fix for
3324 APAR IX87327 is available from IBM Customer Support and from its
3325 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3326 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
3328 The initial assembler shipped with AIX 4.3.0 generates incorrect object
3329 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
3330 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
3331 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3332 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
3334 AIX provides National Language Support (NLS)@. Compilers and assemblers
3335 use NLS to support locale-specific representations of various data
3336 formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
3337 separating decimal fractions). There have been problems reported where
3338 GCC does not produce the same floating-point formats that the assembler
3339 expects. If one encounters this problem, set the @env{LANG}
3340 environment variable to @samp{C} or @samp{En_US}.
3342 By default, GCC for AIX 4.1 and above produces code that can be used on
3343 both Power or PowerPC processors.
3345 A default can be specified with the @option{-mcpu=@var{cpu_type}}
3346 switch and using the configure option @option{--with-cpu-@var{cpu_type}}.
3351 @heading @anchor{iq2000-x-elf}iq2000-*-elf
3352 Vitesse IQ2000 processors. These are used in embedded
3353 applications. There are no standard Unix configurations.
3358 @heading @anchor{m32c-x-elf}m32c-*-elf
3359 Renesas M32C processor.
3360 This configuration is intended for embedded systems.
3365 @heading @anchor{m32r-x-elf}m32r-*-elf
3366 Renesas M32R processor.
3367 This configuration is intended for embedded systems.
3372 @heading @anchor{m6811-elf}m6811-elf
3373 Motorola 68HC11 family micro controllers. These are used in embedded
3374 applications. There are no standard Unix configurations.
3379 @heading @anchor{m6812-elf}m6812-elf
3380 Motorola 68HC12 family micro controllers. These are used in embedded
3381 applications. There are no standard Unix configurations.
3386 @heading @anchor{m68k-hp-hpux}m68k-hp-hpux
3387 HP 9000 series 300 or 400 running HP-UX@. HP-UX version 8.0 has a bug in
3388 the assembler that prevents compilation of GCC@. This
3389 bug manifests itself during the first stage of compilation, while
3390 building @file{libgcc2.a}:
3394 cc1: warning: `-g' option not supported on this version of GCC
3395 cc1: warning: `-g1' option not supported on this version of GCC
3396 ./xgcc: Internal compiler error: program as got fatal signal 11
3399 A patched version of the assembler is available as the file
3400 @uref{ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler}. If you
3401 have HP software support, the patch can also be obtained directly from
3402 HP, as described in the following note:
3405 This is the patched assembler, to patch SR#1653-010439, where the
3406 assembler aborts on floating point constants.
3408 The bug is not really in the assembler, but in the shared library
3409 version of the function ``cvtnum(3c)''. The bug on ``cvtnum(3c)'' is
3410 SR#4701-078451. Anyway, the attached assembler uses the archive
3411 library version of ``cvtnum(3c)'' and thus does not exhibit the bug.
3414 This patch is also known as PHCO_4484.
3416 In addition gdb does not understand that native HP-UX format, so
3417 you must use gas if you wish to use gdb.
3419 On HP-UX version 8.05, but not on 8.07 or more recent versions, the
3420 @command{fixproto} shell script triggers a bug in the system shell. If you
3421 encounter this problem, upgrade your operating system or use BASH (the
3422 GNU shell) to run @command{fixproto}. This bug will cause the fixproto
3423 program to report an error of the form:
3426 ./fixproto: sh internal 1K buffer overflow
3429 To fix this, you can also change the first line of the fixproto script
3439 @heading @anchor{mips-x-x}mips-*-*
3440 If on a MIPS system you get an error message saying ``does not have gp
3441 sections for all it's [sic] sectons [sic]'', don't worry about it. This
3442 happens whenever you use GAS with the MIPS linker, but there is not
3443 really anything wrong, and it is okay to use the output file. You can
3444 stop such warnings by installing the GNU linker.
3446 It would be nice to extend GAS to produce the gp tables, but they are
3447 optional, and there should not be a warning about their absence.
3449 The libstdc++ atomic locking routines for MIPS targets requires MIPS II
3450 and later. A patch went in just after the GCC 3.3 release to
3451 make @samp{mips*-*-*} use the generic implementation instead. You can also
3452 configure for @samp{mipsel-elf} as a workaround. The
3453 @samp{mips*-*-linux*} target continues to use the MIPS II routines. More
3454 work on this is expected in future releases.
3456 MIPS systems check for division by zero (unless
3457 @option{-mno-check-zero-division} is passed to the compiler) by
3458 generating either a conditional trap or a break instruction. Using
3459 trap results in smaller code, but is only supported on MIPS II and
3460 later. Also, some versions of the Linux kernel have a bug that
3461 prevents trap from generating the proper signal (@code{SIGFPE}). To enable
3462 the use of break, use the @option{--with-divide=breaks}
3463 @command{configure} option when configuring GCC@. The default is to
3464 use traps on systems that support them.
3466 Cross-compilers for the MIPS as target using the MIPS assembler
3467 currently do not work, because the auxiliary programs
3468 @file{mips-tdump.c} and @file{mips-tfile.c} can't be compiled on
3469 anything but a MIPS. It does work to cross compile for a MIPS
3470 if you use the GNU assembler and linker.
3472 The linker from GNU binutils versions prior to 2.17 has a bug which
3473 causes the runtime linker stubs in @file{libgcj.so} to be incorrectly
3474 generated. If you want to use libgcj, either use binutils 2.17 or
3475 later to build it or export @samp{LD_BIND_NOW=1} in your runtime environment.
3480 @heading @anchor{mips-sgi-irix5}mips-sgi-irix5
3482 In order to compile GCC on an SGI running IRIX 5, the @samp{compiler_dev.hdr}
3483 subsystem must be installed from the IDO CD-ROM supplied by SGI@.
3484 It is also available for download from
3485 @uref{ftp://ftp.sgi.com/sgi/IRIX5.3/iris-development-option-5.3.tardist}.
3487 If you use the MIPS C compiler to bootstrap, it may be necessary
3488 to increase its table size for switch statements with the
3489 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
3490 optimization option, you also need to use @option{-Olimit 3000}.
3492 To enable debugging under IRIX 5, you must use GNU binutils 2.15 or
3493 later, and use the @option{--with-gnu-ld} @command{configure} option
3494 when configuring GCC@. You need to use GNU @command{ar} and @command{nm},
3495 also distributed with GNU binutils.
3497 Some users have reported that @command{/bin/sh} will hang during bootstrap.
3498 This problem can be avoided by running the commands:
3501 % CONFIG_SHELL=/bin/ksh
3502 % export CONFIG_SHELL
3505 before starting the build.
3510 @heading @anchor{mips-sgi-irix6}mips-sgi-irix6
3512 If you are using SGI's MIPSpro @command{cc} as your bootstrap compiler, you must
3513 ensure that the N32 ABI is in use. To test this, compile a simple C
3514 file with @command{cc} and then run @command{file} on the
3515 resulting object file. The output should look like:
3518 test.o: ELF N32 MSB @dots{}
3524 test.o: ELF 32-bit MSB @dots{}
3530 test.o: ELF 64-bit MSB @dots{}
3533 then your version of @command{cc} uses the O32 or N64 ABI by default. You
3534 should set the environment variable @env{CC} to @samp{cc -n32}
3535 before configuring GCC@.
3537 If you want the resulting @command{gcc} to run on old 32-bit systems
3538 with the MIPS R4400 CPU, you need to ensure that only code for the @samp{mips3}
3539 instruction set architecture (ISA) is generated. While GCC 3.x does
3540 this correctly, both GCC 2.95 and SGI's MIPSpro @command{cc} may change
3541 the ISA depending on the machine where GCC is built. Using one of them
3542 as the bootstrap compiler may result in @samp{mips4} code, which won't run at
3543 all on @samp{mips3}-only systems. For the test program above, you should see:
3546 test.o: ELF N32 MSB mips-3 @dots{}
3552 test.o: ELF N32 MSB mips-4 @dots{}
3555 instead, you should set the environment variable @env{CC} to @samp{cc
3556 -n32 -mips3} or @samp{gcc -mips3} respectively before configuring GCC@.
3558 MIPSpro C 7.4 may cause bootstrap failures, due to a bug when inlining
3559 @code{memcmp}. Either add @code{-U__INLINE_INTRINSICS} to the @env{CC}
3560 environment variable as a workaround or upgrade to MIPSpro C 7.4.1m.
3562 GCC on IRIX 6 is usually built to support the N32, O32 and N64 ABIs. If
3563 you build GCC on a system that doesn't have the N64 libraries installed
3564 or cannot run 64-bit binaries,
3565 you need to configure with @option{--disable-multilib} so GCC doesn't
3566 try to use them. This will disable building the O32 libraries, too.
3567 Look for @file{/usr/lib64/libc.so.1} to see if you
3568 have the 64-bit libraries installed.
3570 To enable debugging for the O32 ABI, you must use GNU @command{as} from
3571 GNU binutils 2.15 or later. You may also use GNU @command{ld}, but
3572 this is not required and currently causes some problems with Ada.
3574 The @option{--enable-threads} option doesn't currently work, a patch is
3575 in preparation for a future release. The @option{--enable-libgcj}
3576 option is disabled by default: IRIX 6 uses a very low default limit
3577 (20480) for the command line length. Although @command{libtool} contains a
3578 workaround for this problem, at least the N64 @samp{libgcj} is known not
3579 to build despite this, running into an internal error of the native
3580 @command{ld}. A sure fix is to increase this limit (@samp{ncargs}) to
3581 its maximum of 262144 bytes. If you have root access, you can use the
3582 @command{systune} command to do this.
3584 @code{wchar_t} support in @samp{libstdc++} is not available for old
3585 IRIX 6.5.x releases, @math{x < 19}. The problem cannot be autodetected
3586 and in order to build GCC for such targets you need to configure with
3587 @option{--disable-wchar_t}.
3589 See @uref{http://freeware.sgi.com/} for more
3590 information about using GCC on IRIX platforms.
3595 @heading @anchor{powerpc-x-x}powerpc-*-*
3597 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
3598 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
3603 @heading @anchor{powerpc-x-darwin}powerpc-*-darwin*
3604 PowerPC running Darwin (Mac OS X kernel).
3606 Pre-installed versions of Mac OS X may not include any developer tools,
3607 meaning that you will not be able to build GCC from source. Tool
3608 binaries are available at
3609 @uref{http://developer.apple.com/darwin/projects/compiler/} (free
3610 registration required).
3612 This version of GCC requires at least cctools-590.7.
3614 The version of GCC shipped by Apple typically includes a number of
3615 extensions not available in a standard GCC release. These extensions
3616 are generally for backwards compatibility and best avoided.
3621 @heading @anchor{powerpc-x-elf}powerpc-*-elf, powerpc-*-sysv4
3622 PowerPC system in big endian mode, running System V.4.
3627 @heading @anchor{powerpc-x-linux-gnu}powerpc*-*-linux-gnu*
3630 @uref{ftp://ftp.kernel.org/pub/linux/devel/binutils,,binutils 2.15}
3631 or newer for a working GCC@.
3636 @heading @anchor{powerpc-x-netbsd}powerpc-*-netbsd*
3637 PowerPC system in big endian mode running NetBSD@. To build the
3638 documentation you will need Texinfo version 4.4 (NetBSD 1.5.1 included
3639 Texinfo version 3.12).
3644 @heading @anchor{powerpc-x-eabisim}powerpc-*-eabisim
3645 Embedded PowerPC system in big endian mode for use in running under the
3651 @heading @anchor{powerpc-x-eabi}powerpc-*-eabi
3652 Embedded PowerPC system in big endian mode.
3657 @heading @anchor{powerpcle-x-elf}powerpcle-*-elf, powerpcle-*-sysv4
3658 PowerPC system in little endian mode, running System V.4.
3663 @heading @anchor{powerpcle-x-eabisim}powerpcle-*-eabisim
3664 Embedded PowerPC system in little endian mode for use in running under
3670 @heading @anchor{powerpcle-x-eabi}powerpcle-*-eabi
3671 Embedded PowerPC system in little endian mode.
3676 @heading @anchor{s390-x-linux}s390-*-linux*
3677 S/390 system running GNU/Linux for S/390@.
3682 @heading @anchor{s390x-x-linux}s390x-*-linux*
3683 zSeries system (64-bit) running GNU/Linux for zSeries@.
3688 @heading @anchor{s390x-ibm-tpf}s390x-ibm-tpf*
3689 zSeries system (64-bit) running TPF@. This platform is
3690 supported as cross-compilation target only.
3695 @c Please use Solaris 2 to refer to all release of Solaris, starting
3696 @c with 2.0 until 2.6, 7, 8, etc. Solaris 1 was a marketing name for
3697 @c SunOS 4 releases which we don't use to avoid confusion. Solaris
3698 @c alone is too unspecific and must be avoided.
3699 @heading @anchor{x-x-solaris2}*-*-solaris2*
3701 Sun does not ship a C compiler with Solaris 2. To bootstrap and install
3702 GCC you first have to install a pre-built compiler, see the
3703 @uref{binaries.html,,binaries page} for details.
3705 The Solaris 2 @command{/bin/sh} will often fail to configure
3706 @file{libstdc++-v3}, @file{boehm-gc} or @file{libjava}. We therefore
3707 recommend using the following initial sequence of commands
3710 % CONFIG_SHELL=/bin/ksh
3711 % export CONFIG_SHELL
3714 and proceed as described in @uref{configure.html,,the configure instructions}.
3715 In addition we strongly recommend specifying an absolute path to invoke
3716 @var{srcdir}/configure.
3718 Solaris 2 comes with a number of optional OS packages. Some of these
3719 are needed to use GCC fully, namely @code{SUNWarc},
3720 @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
3721 @code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all
3722 optional packages when installing Solaris 2, you will need to verify that
3723 the packages that GCC needs are installed.
3725 To check whether an optional package is installed, use
3726 the @command{pkginfo} command. To add an optional package, use the
3727 @command{pkgadd} command. For further details, see the Solaris 2
3730 Trying to use the linker and other tools in
3731 @file{/usr/ucb} to install GCC has been observed to cause trouble.
3732 For example, the linker may hang indefinitely. The fix is to remove
3733 @file{/usr/ucb} from your @env{PATH}.
3735 The build process works more smoothly with the legacy Sun tools so, if you
3736 have @file{/usr/xpg4/bin} in your @env{PATH}, we recommend that you place
3737 @file{/usr/bin} before @file{/usr/xpg4/bin} for the duration of the build.
3739 All releases of GNU binutils prior to 2.11.2 have known bugs on this
3740 platform. We recommend the use of GNU binutils 2.11.2 or later, or the
3741 vendor tools (Sun @command{as}, Sun @command{ld}). Note that your mileage
3742 may vary if you use a combination of the GNU tools and the Sun tools: while
3743 the combination GNU @command{as} + Sun @command{ld} should reasonably work,
3744 the reverse combination Sun @command{as} + GNU @command{ld} is known to
3745 cause memory corruption at runtime in some cases for C++ programs.
3747 The stock GNU binutils 2.15 release is broken on this platform because of a
3748 single bug. It has been fixed on the 2.15 branch in the CVS repository.
3749 You can obtain a working version by checking out the binutils-2_15-branch
3750 from the CVS repository or applying the patch
3751 @uref{http://sources.redhat.com/ml/binutils-cvs/2004-09/msg00036.html} to the
3754 We recommend using GNU binutils 2.16 or later in conjunction with GCC 4.x,
3755 or the vendor tools (Sun @command{as}, Sun @command{ld}). However, for
3756 Solaris 10 and above, an additional patch is required in order for the GNU
3757 linker to be able to cope with a new flavor of shared libraries. You
3758 can obtain a working version by checking out the binutils-2_16-branch from
3759 the CVS repository or applying the patch
3760 @uref{http://sourceware.org/ml/binutils-cvs/2005-07/msg00122.html} to the
3763 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
3764 newer: @command{g++} will complain that types are missing. These headers assume
3765 that omitting the type means @code{int}; this assumption worked for C89 but
3766 is wrong for C++, and is now wrong for C99 also.
3768 @command{g++} accepts such (invalid) constructs with the option
3769 @option{-fpermissive}; it
3770 will assume that any missing type is @code{int} (as defined by C89).
3772 There are patches for Solaris 2.6 (105633-56 or newer for SPARC,
3773 106248-42 or newer for Intel), Solaris 7 (108376-21 or newer for SPARC,
3774 108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC,
3775 108653-22 for Intel) that fix this bug.
3777 Sun bug 4927647 sometimes causes random spurious testsuite failures
3778 related to missing diagnostic output. This bug doesn't affect GCC
3779 itself, rather it is a kernel bug triggered by the @command{expect}
3780 program which is used only by the GCC testsuite driver. When the bug
3781 causes the @command{expect} program to miss anticipated output, extra
3782 testsuite failures appear.
3784 There are patches for Solaris 8 (117350-12 or newer for SPARC,
3785 117351-12 or newer for Intel) and Solaris 9 (117171-11 or newer for
3786 SPARC, 117172-11 or newer for Intel) that address this problem.
3791 @heading @anchor{sparc-sun-solaris2}sparc-sun-solaris2*
3793 When GCC is configured to use binutils 2.11.2 or later the binaries
3794 produced are smaller than the ones produced using Sun's native tools;
3795 this difference is quite significant for binaries containing debugging
3798 Sun @command{as} 4.x is broken in that it cannot cope with long symbol names.
3799 A typical error message might look similar to the following:
3802 /usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041: error:
3803 can't compute value of an expression involving an external symbol.
3806 This is Sun bug 4237974. This is fixed with patch 108908-02 for Solaris
3807 2.6 and has been fixed in later (5.x) versions of the assembler,
3808 starting with Solaris 7.
3810 Starting with Solaris 7, the operating system is capable of executing
3811 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
3812 this; the @option{-m64} option enables 64-bit code generation.
3813 However, if all you want is code tuned for the UltraSPARC CPU, you
3814 should try the @option{-mtune=ultrasparc} option instead, which produces
3815 code that, unlike full 64-bit code, can still run on non-UltraSPARC
3818 When configuring on a Solaris 7 or later system that is running a kernel
3819 that supports only 32-bit binaries, one must configure with
3820 @option{--disable-multilib}, since we will not be able to build the
3821 64-bit target libraries.
3823 GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of
3824 the GNU compiler (especially GCC 3.0.x versions), which lead to the
3825 miscompilation of the stage1 compiler and the subsequent failure of the
3826 bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary
3827 stage, i.e.@: to bootstrap that compiler with the base compiler and then
3828 use it to bootstrap the final compiler.
3830 GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE Studio 7)
3831 and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a bootstrap
3832 failure in form of a miscompilation of the stage1 compiler by the Sun
3833 compiler. This is Sun bug 4974440. This is fixed with patch 112760-07.
3835 GCC 3.4 changed the default debugging format from STABS to DWARF-2 for
3836 32-bit code on Solaris 7 and later. If you use the Sun assembler, this
3837 change apparently runs afoul of Sun bug 4910101 (which is referenced as
3838 a x86-only problem by Sun, probably because they do not use DWARF-2).
3839 A symptom of the problem is that you cannot compile C++ programs like
3840 @command{groff} 1.19.1 without getting messages similar to the following:
3843 ld: warning: relocation error: R_SPARC_UA32: @dots{}
3844 external symbolic relocation against non-allocatable section
3845 .debug_info cannot be processed at runtime: relocation ignored.
3848 To work around this problem, compile with @option{-gstabs+} instead of
3851 When configuring the GNU Multiple Precision Library (GMP) version 4.1.x
3852 on a Solaris 7 or later system, the canonical target triplet must be
3853 specified as the @command{build} parameter on the configure line:
3856 ./configure --build=sparc-sun-solaris2.7 --prefix=xxx --enable-mpfr
3862 @heading @anchor{sparc-sun-solaris27}sparc-sun-solaris2.7
3864 Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in
3865 the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8
3866 and later, including all EGCS releases. Sun formerly recommended
3867 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to
3868 recommend it only for people who use Sun's compilers.
3870 Here are some workarounds to this problem:
3873 Do not install Sun patch 107058-01 until after Sun releases a
3874 complete patch for bug 4210064. This is the simplest course to take,
3875 unless you must also use Sun's C compiler. Unfortunately 107058-01
3876 is preinstalled on some new Solaris 7-based hosts, so you may have to
3880 Copy the original, unpatched Solaris 7
3881 @command{/usr/ccs/bin/as} into
3882 @command{/usr/local/libexec/gcc/sparc-sun-solaris2.7/3.4/as},
3883 adjusting the latter name to fit your local conventions and software
3887 Install Sun patch 106950-03 (1999-05-25) or later. Nobody with
3888 both 107058-01 and 106950-03 installed has reported the bug with GCC
3889 and Sun's dynamic linker. This last course of action is riskiest,
3890 for two reasons. First, you must install 106950 on all hosts that
3891 run code generated by GCC; it doesn't suffice to install it only on
3892 the hosts that run GCC itself. Second, Sun says that 106950-03 is
3893 only a partial fix for bug 4210064, but Sun doesn't know whether the
3894 partial fix is adequate for GCC@. Revision -08 or later should fix
3895 the bug. The current (as of 2004-05-23) revision is -24, and is included in
3896 the Solaris 7 Recommended Patch Cluster.
3899 GCC 3.3 triggers a bug in version 5.0 Alpha 03/27/98 of the Sun assembler,
3900 which causes a bootstrap failure when linking the 64-bit shared version of
3901 libgcc. A typical error message is:
3904 ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o:
3905 symbol <unknown>: offset 0xffffffff7ec133e7 is non-aligned.
3908 This bug has been fixed in the final 5.0 version of the assembler.
3910 A similar problem was reported for version Sun WorkShop 6 99/08/18 of the
3911 Sun assembler, which causes a bootstrap failure with GCC 4.0.0:
3914 ld: fatal: relocation error: R_SPARC_DISP32:
3915 file .libs/libstdc++.lax/libsupc++convenience.a/vterminate.o:
3916 symbol <unknown>: offset 0xfccd33ad is non-aligned
3919 This bug has been fixed in more recent revisions of the assembler.
3924 @heading @anchor{sparc-x-linux}sparc-*-linux*
3926 GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
3927 or newer on this platform. All earlier binutils and glibc
3928 releases mishandled unaligned relocations on @code{sparc-*-*} targets.
3934 @heading @anchor{sparc64-x-solaris2}sparc64-*-solaris2*
3936 The following compiler flags must be specified in the configure
3937 step in order to bootstrap this target with the Sun compiler:
3940 % CC="cc -xildoff -xarch=v9" @var{srcdir}/configure [@var{options}] [@var{target}]
3943 @option{-xildoff} turns off the incremental linker, and @option{-xarch=v9}
3944 specifies the SPARC-V9 architecture to the Sun linker and assembler.
3949 @heading @anchor{sparcv9-x-solaris2}sparcv9-*-solaris2*
3951 This is a synonym for sparc64-*-solaris2*.
3956 @heading @anchor{x-x-sysv}*-*-sysv*
3957 On System V release 3, you may get this error message
3961 ld fatal: failed to write symbol name @var{something}
3962 in strings table for file @var{whatever}
3965 This probably indicates that the disk is full or your ulimit won't allow
3966 the file to be as large as it needs to be.
3968 This problem can also result because the kernel parameter @code{MAXUMEM}
3969 is too small. If so, you must regenerate the kernel and make the value
3970 much larger. The default value is reported to be 1024; a value of 32768
3971 is said to work. Smaller values may also work.
3973 On System V, if you get an error like this,
3976 /usr/local/lib/bison.simple: In function `yyparse':
3977 /usr/local/lib/bison.simple:625: virtual memory exhausted
3981 that too indicates a problem with disk space, ulimit, or @code{MAXUMEM}.
3983 On a System V release 4 system, make sure @file{/usr/bin} precedes
3984 @file{/usr/ucb} in @code{PATH}. The @command{cc} command in
3985 @file{/usr/ucb} uses libraries which have bugs.
3990 @heading @anchor{vax-dec-ultrix}vax-dec-ultrix
3991 Don't try compiling with VAX C (@command{vcc}). It produces incorrect code
3992 in some cases (for example, when @code{alloca} is used).
3997 @heading @anchor{x-x-vxworks}*-*-vxworks*
3998 Support for VxWorks is in flux. At present GCC supports @emph{only} the
3999 very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC@.
4000 We welcome patches for other architectures supported by VxWorks 5.5.
4001 Support for VxWorks AE would also be welcome; we believe this is merely
4002 a matter of writing an appropriate ``configlette'' (see below). We are
4003 not interested in supporting older, a.out or COFF-based, versions of
4006 VxWorks comes with an older version of GCC installed in
4007 @file{@var{$WIND_BASE}/host}; we recommend you do not overwrite it.
4008 Choose an installation @var{prefix} entirely outside @var{$WIND_BASE}.
4009 Before running @command{configure}, create the directories @file{@var{prefix}}
4010 and @file{@var{prefix}/bin}. Link or copy the appropriate assembler,
4011 linker, etc.@: into @file{@var{prefix}/bin}, and set your @var{PATH} to
4012 include that directory while running both @command{configure} and
4015 You must give @command{configure} the
4016 @option{--with-headers=@var{$WIND_BASE}/target/h} switch so that it can
4017 find the VxWorks system headers. Since VxWorks is a cross compilation
4018 target only, you must also specify @option{--target=@var{target}}.
4019 @command{configure} will attempt to create the directory
4020 @file{@var{prefix}/@var{target}/sys-include} and copy files into it;
4021 make sure the user running @command{configure} has sufficient privilege
4024 GCC's exception handling runtime requires a special ``configlette''
4025 module, @file{contrib/gthr_supp_vxw_5x.c}. Follow the instructions in
4026 that file to add the module to your kernel build. (Future versions of
4027 VxWorks will incorporate this module.)
4032 @heading @anchor{x86-64-x-x}x86_64-*-*, amd64-*-*
4034 GCC supports the x86-64 architecture implemented by the AMD64 processor
4035 (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD@.
4036 On GNU/Linux the default is a bi-arch compiler which is able to generate
4037 both 64-bit x86-64 and 32-bit x86 code (via the @option{-m32} switch).
4042 @heading @anchor{xtensa-x-elf}xtensa-*-elf
4044 This target is intended for embedded Xtensa systems using the
4045 @samp{newlib} C library. It uses ELF but does not support shared
4046 objects. Designed-defined instructions specified via the
4047 Tensilica Instruction Extension (TIE) language are only supported
4048 through inline assembly.
4050 The Xtensa configuration information must be specified prior to
4051 building GCC@. The @file{include/xtensa-config.h} header
4052 file contains the configuration information. If you created your
4053 own Xtensa configuration with the Xtensa Processor Generator, the
4054 downloaded files include a customized copy of this header file,
4055 which you can use to replace the default header file.
4060 @heading @anchor{xtensa-x-linux}xtensa-*-linux*
4062 This target is for Xtensa systems running GNU/Linux. It supports ELF
4063 shared objects and the GNU C library (glibc). It also generates
4064 position-independent code (PIC) regardless of whether the
4065 @option{-fpic} or @option{-fPIC} options are used. In other
4066 respects, this target is the same as the
4067 @uref{#xtensa-*-elf,,@samp{xtensa-*-elf}} target.
4072 @heading @anchor{windows}Microsoft Windows (32-bit)
4074 Ports of GCC are included with the
4075 @uref{http://www.cygwin.com/,,Cygwin environment}.
4077 GCC will build under Cygwin without modification; it does not build
4078 with Microsoft's C++ compiler and there are no plans to make it do so.
4083 @heading @anchor{os2}OS/2
4085 GCC does not currently support OS/2. However, Andrew Zabolotny has been
4086 working on a generic OS/2 port with pgcc. The current code can be found
4087 at @uref{http://www.goof.com/pcg/os2/,,http://www.goof.com/pcg/os2/}.
4092 @heading @anchor{older}Older systems
4094 GCC contains support files for many older (1980s and early
4095 1990s) Unix variants. For the most part, support for these systems
4096 has not been deliberately removed, but it has not been maintained for
4097 several years and may suffer from bitrot.
4099 Starting with GCC 3.1, each release has a list of ``obsoleted'' systems.
4100 Support for these systems is still present in that release, but
4101 @command{configure} will fail unless the @option{--enable-obsolete}
4102 option is given. Unless a maintainer steps forward, support for these
4103 systems will be removed from the next release of GCC@.
4105 Support for old systems as hosts for GCC can cause problems if the
4106 workarounds for compiler, library and operating system bugs affect the
4107 cleanliness or maintainability of the rest of GCC@. In some cases, to
4108 bring GCC up on such a system, if still possible with current GCC, may
4109 require first installing an old version of GCC which did work on that
4110 system, and using it to compile a more recent GCC, to avoid bugs in the
4111 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
4112 @file{old-releases} directory on the @uref{../mirrors.html,,GCC mirror
4113 sites}. Header bugs may generally be avoided using
4114 @command{fixincludes}, but bugs or deficiencies in libraries and the
4115 operating system may still cause problems.
4117 Support for older systems as targets for cross-compilation is less
4118 problematic than support for them as hosts for GCC; if an enthusiast
4119 wishes to make such a target work again (including resurrecting any of
4120 the targets that never worked with GCC 2, starting from the last
4121 version before they were removed), patches
4122 @uref{../contribute.html,,following the usual requirements} would be
4123 likely to be accepted, since they should not affect the support for more
4126 For some systems, old versions of GNU binutils may also be useful,
4127 and are available from @file{pub/binutils/old-releases} on
4128 @uref{http://sources.redhat.com/mirrors.html,,sources.redhat.com mirror sites}.
4130 Some of the information on specific systems above relates to
4131 such older systems, but much of the information
4132 about GCC on such systems (which may no longer be applicable to
4133 current GCC) is to be found in the GCC texinfo manual.
4138 @heading @anchor{elf}all ELF targets (SVR4, Solaris 2, etc.)
4140 C++ support is significantly better on ELF targets if you use the
4141 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
4142 inlines, vtables and template instantiations will be discarded
4151 @uref{./index.html,,Return to the GCC Installation page}
4155 @c ***Old documentation******************************************************
4157 @include install-old.texi
4163 @uref{./index.html,,Return to the GCC Installation page}
4167 @c ***GFDL********************************************************************
4175 @uref{./index.html,,Return to the GCC Installation page}
4179 @c ***************************************************************************
4180 @c Part 6 The End of the Document
4182 @comment node-name, next, previous, up
4183 @node Concept Index, , GNU Free Documentation License, Top
4187 @unnumbered Concept Index