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 Programming
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.0 (or later)
295 Necessary to build the Fortran frontend. If you don't 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.
301 Necessary to build the Fortran frontend. It can be downloaded from
302 @uref{http://www.mpfr.org/}. It is also included in the current GMP
303 release (4.1.3) when configured with @option{--enable-mpfr}.
305 The @option{--with-mpfr} or @option{--with-mpfr-dir} configure option should
306 be used if your MPFR Library is not installed in your library search path.
310 Necessary to build libgcj, the GCJ runtime.
315 @heading Tools/packages necessary for modifying GCC
317 @item autoconf versions 2.13 and 2.59
318 @itemx GNU m4 version 1.4 (or later)
320 Necessary when modifying @file{configure.ac}, @file{aclocal.m4}, etc.@:
321 to regenerate @file{configure} and @file{config.in} files. Most
322 directories require autoconf 2.59 (exactly), but the toplevel
323 still requires autoconf 2.13 (exactly).
325 @item automake versions 1.9.3
327 Necessary when modifying a @file{Makefile.am} file to regenerate its
328 associated @file{Makefile.in}.
330 Much of GCC does not use automake, so directly edit the @file{Makefile.in}
331 file. Specifically this applies to the @file{gcc}, @file{intl},
332 @file{libcpp}, @file{libiberty}, @file{libobjc} directories as well
333 as any of their subdirectories.
335 For directories that use automake, GCC requires the latest release in
336 the 1.9.x series, which is currently 1.9.3. When regenerating a directory
337 to a newer version, please update all the directories using an older 1.9.x
338 to the latest released version.
340 @item gettext version 0.14.5 (or later)
342 Needed to regenerate @file{gcc.pot}.
344 @item gperf version 2.7.2 (or later)
346 Necessary when modifying @command{gperf} input files, e.g.@:
347 @file{gcc/cp/cfns.gperf} to regenerate its associated header file, e.g.@:
348 @file{gcc/cp/cfns.h}.
354 Necessary to run the GCC testsuite; see the section on testing for details.
356 @item autogen version 5.5.4 (or later) and
357 @itemx guile version 1.4.1 (or later)
359 Necessary to regenerate @file{fixinc/fixincl.x} from
360 @file{fixinc/inclhack.def} and @file{fixinc/*.tpl}.
362 Necessary to run @samp{make check} for @file{fixinc}.
364 Necessary to regenerate the top level @file{Makefile.in} file from
365 @file{Makefile.tpl} and @file{Makefile.def}.
367 @item GNU Bison version 1.28 (or later)
368 Berkeley @command{yacc} (@command{byacc}) is also reported to work other
371 Necessary when modifying @file{*.y} files.
373 Necessary to build GCC during development because the generated output
374 files are not included in the SVN repository. They are included in
377 @item Flex version 2.5.4 (or later)
379 Necessary when modifying @file{*.l} files.
381 Necessary to build GCC during development because the generated output
382 files are not included in the SVN repository. They are included in
385 @item Texinfo version 4.4 (or later)
387 Necessary for running @command{makeinfo} when modifying @file{*.texi}
388 files to test your changes.
390 Necessary to build GCC documentation during development because the
391 generated output files are not included in the SVN repository. They are
392 included in releases.
394 @item @TeX{} (any working version)
396 Necessary for running @command{texi2dvi}, used when running
397 @command{make dvi} to create DVI files.
399 @item SVN (any version)
400 @itemx SSH (any version)
402 Necessary to access the SVN repository. Public releases and weekly
403 snapshots of the development sources are also available via FTP@.
405 @item Perl version 5.6.1 (or later)
407 Necessary when regenerating @file{Makefile} dependencies in libiberty.
408 Necessary when regenerating @file{libiberty/functions.texi}.
409 Necessary when generating manpages from Texinfo manuals.
410 Necessary when targetting Darwin, building libstdc++,
411 and not using @option{--disable-symvers}.
412 Used by various scripts to generate some files included in SVN (mainly
413 Unicode-related and rarely changing) from source tables.
415 @item GNU diffutils version 2.7 (or later)
417 Useful when submitting patches for the GCC source code.
419 @item patch version 2.5.4 (or later)
421 Necessary when applying patches, created with @command{diff}, to one's
431 @uref{./index.html,,Return to the GCC Installation page}
435 @c ***Downloading the source**************************************************
437 @comment node-name, next, previous, up
438 @node Downloading the source, Configuration, Prerequisites, Installing GCC
442 @chapter Downloading GCC
444 @cindex Downloading GCC
445 @cindex Downloading the Source
447 GCC is distributed via @uref{http://gcc.gnu.org/svn.html,,SVN} and FTP
448 tarballs compressed with @command{gzip} or
449 @command{bzip2}. It is possible to download a full distribution or specific
452 Please refer to the @uref{http://gcc.gnu.org/releases.html,,releases web page}
453 for information on how to obtain GCC@.
455 The full distribution includes the C, C++, Objective-C, Fortran 77, Fortran
456 (in case of GCC 4.0 and later), Java, and Ada (in case of GCC 3.1 and later)
457 compilers. The full distribution also includes runtime libraries for C++,
458 Objective-C, Fortran 77, Fortran, and Java. In GCC 3.0 and later versions,
459 GNU compiler testsuites are also included in the full distribution.
461 If you choose to download specific components, you must download the core
462 GCC distribution plus any language specific distributions you wish to
463 use. The core distribution includes the C language front end as well as the
464 shared components. Each language has a tarball which includes the language
465 front end as well as the language runtime (when appropriate).
467 Unpack the core distribution as well as any language specific
468 distributions in the same directory.
470 If you also intend to build binutils (either to upgrade an existing
471 installation or for use in place of the corresponding tools of your
472 OS), unpack the binutils distribution either in the same directory or
473 a separate one. In the latter case, add symbolic links to any
474 components of the binutils you intend to build alongside the compiler
475 (@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld},
476 @file{opcodes}, @dots{}) to the directory containing the GCC sources.
483 @uref{./index.html,,Return to the GCC Installation page}
487 @c ***Configuration***********************************************************
489 @comment node-name, next, previous, up
490 @node Configuration, Building, Downloading the source, Installing GCC
494 @chapter Installing GCC: Configuration
496 @cindex Configuration
497 @cindex Installing GCC: Configuration
499 Like most GNU software, GCC must be configured before it can be built.
500 This document describes the recommended configuration procedure
501 for both native and cross targets.
503 We use @var{srcdir} to refer to the toplevel source directory for
504 GCC; we use @var{objdir} to refer to the toplevel build/object directory.
506 If you obtained the sources via SVN, @var{srcdir} must refer to the top
507 @file{gcc} directory, the one where the @file{MAINTAINERS} can be found,
508 and not its @file{gcc} subdirectory, otherwise the build will fail.
510 If either @var{srcdir} or @var{objdir} is located on an automounted NFS
511 file system, the shell's built-in @command{pwd} command will return
512 temporary pathnames. Using these can lead to various sorts of build
513 problems. To avoid this issue, set the @env{PWDCMD} environment
514 variable to an automounter-aware @command{pwd} command, e.g.,
515 @command{pawd} or @samp{amq -w}, during the configuration and build
518 First, we @strong{highly} recommend that GCC be built into a
519 separate directory than the sources which does @strong{not} reside
520 within the source tree. This is how we generally build GCC; building
521 where @var{srcdir} == @var{objdir} should still work, but doesn't
522 get extensive testing; building where @var{objdir} is a subdirectory
523 of @var{srcdir} is unsupported.
525 If you have previously built GCC in the same directory for a
526 different target machine, do @samp{make distclean} to delete all files
527 that might be invalid. One of the files this deletes is @file{Makefile};
528 if @samp{make distclean} complains that @file{Makefile} does not exist
529 or issues a message like ``don't know how to make distclean'' it probably
530 means that the directory is already suitably clean. However, with the
531 recommended method of building in a separate @var{objdir}, you should
532 simply use a different @var{objdir} for each target.
534 Second, when configuring a native system, either @command{cc} or
535 @command{gcc} must be in your path or you must set @env{CC} in
536 your environment before running configure. Otherwise the configuration
540 Note that the bootstrap compiler and the resulting GCC must be link
541 compatible, else the bootstrap will fail with linker errors about
542 incompatible object file formats. Several multilibed targets are
543 affected by this requirement, see
545 @ref{Specific, host/target specific installation notes}.
548 @uref{specific.html,,host/target specific installation notes}.
557 % @var{srcdir}/configure [@var{options}] [@var{target}]
561 @heading Target specification
564 GCC has code to correctly determine the correct value for @var{target}
565 for nearly all native systems. Therefore, we highly recommend you not
566 provide a configure target when configuring a native compiler.
569 @var{target} must be specified as @option{--target=@var{target}}
570 when configuring a cross compiler; examples of valid targets would be
571 m68k-coff, sh-elf, etc.
574 Specifying just @var{target} instead of @option{--target=@var{target}}
575 implies that the host defaults to @var{target}.
579 @heading Options specification
581 Use @var{options} to override several configure time options for
582 GCC@. A list of supported @var{options} follows; @samp{configure
583 --help} may list other options, but those not listed below may not
584 work and should not normally be used.
586 Note that each @option{--enable} option has a corresponding
587 @option{--disable} option and that each @option{--with} option has a
588 corresponding @option{--without} option.
591 @item --prefix=@var{dirname}
592 Specify the toplevel installation
593 directory. This is the recommended way to install the tools into a directory
594 other than the default. The toplevel installation directory defaults to
597 We @strong{highly} recommend against @var{dirname} being the same or a
598 subdirectory of @var{objdir} or vice versa. If specifying a directory
599 beneath a user's home directory tree, some shells will not expand
600 @var{dirname} correctly if it contains the @samp{~} metacharacter; use
603 The following standard @command{autoconf} options are supported. Normally you
604 should not need to use these options.
606 @item --exec-prefix=@var{dirname}
607 Specify the toplevel installation directory for architecture-dependent
608 files. The default is @file{@var{prefix}}.
610 @item --bindir=@var{dirname}
611 Specify the installation directory for the executables called by users
612 (such as @command{gcc} and @command{g++}). The default is
613 @file{@var{exec-prefix}/bin}.
615 @item --libdir=@var{dirname}
616 Specify the installation directory for object code libraries and
617 internal data files of GCC@. The default is @file{@var{exec-prefix}/lib}.
619 @item --libexecdir=@var{dirname}
620 Specify the installation directory for internal executables of GCC@.
621 The default is @file{@var{exec-prefix}/libexec}.
623 @item --with-slibdir=@var{dirname}
624 Specify the installation directory for the shared libgcc library. The
625 default is @file{@var{libdir}}.
627 @item --infodir=@var{dirname}
628 Specify the installation directory for documentation in info format.
629 The default is @file{@var{prefix}/info}.
631 @item --datadir=@var{dirname}
632 Specify the installation directory for some architecture-independent
633 data files referenced by GCC@. The default is @file{@var{prefix}/share}.
635 @item --mandir=@var{dirname}
636 Specify the installation directory for manual pages. The default is
637 @file{@var{prefix}/man}. (Note that the manual pages are only extracts from
638 the full GCC manuals, which are provided in Texinfo format. The manpages
639 are derived by an automatic conversion process from parts of the full
642 @item --with-gxx-include-dir=@var{dirname}
644 the installation directory for G++ header files. The default is
645 @file{@var{prefix}/include/c++/@var{version}}.
649 @item --program-prefix=@var{prefix}
650 GCC supports some transformations of the names of its programs when
651 installing them. This option prepends @var{prefix} to the names of
652 programs to install in @var{bindir} (see above). For example, specifying
653 @option{--program-prefix=foo-} would result in @samp{gcc}
654 being installed as @file{/usr/local/bin/foo-gcc}.
656 @item --program-suffix=@var{suffix}
657 Appends @var{suffix} to the names of programs to install in @var{bindir}
658 (see above). For example, specifying @option{--program-suffix=-3.1}
659 would result in @samp{gcc} being installed as
660 @file{/usr/local/bin/gcc-3.1}.
662 @item --program-transform-name=@var{pattern}
663 Applies the @samp{sed} script @var{pattern} to be applied to the names
664 of programs to install in @var{bindir} (see above). @var{pattern} has to
665 consist of one or more basic @samp{sed} editing commands, separated by
666 semicolons. For example, if you want the @samp{gcc} program name to be
667 transformed to the installed program @file{/usr/local/bin/myowngcc} and
668 the @samp{g++} program name to be transformed to
669 @file{/usr/local/bin/gspecial++} without changing other program names,
670 you could use the pattern
671 @option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'}
672 to achieve this effect.
674 All three options can be combined and used together, resulting in more
675 complex conversion patterns. As a basic rule, @var{prefix} (and
676 @var{suffix}) are prepended (appended) before further transformations
677 can happen with a special transformation script @var{pattern}.
679 As currently implemented, this option only takes effect for native
680 builds; cross compiler binaries' names are not transformed even when a
681 transformation is explicitly asked for by one of these options.
683 For native builds, some of the installed programs are also installed
684 with the target alias in front of their name, as in
685 @samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen
686 before the target alias is prepended to the name---so, specifying
687 @option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the
688 resulting binary would be installed as
689 @file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}.
691 As a last shortcoming, none of the installed Ada programs are
692 transformed yet, which will be fixed in some time.
694 @item --with-local-prefix=@var{dirname}
696 installation directory for local include files. The default is
697 @file{/usr/local}. Specify this option if you want the compiler to
698 search directory @file{@var{dirname}/include} for locally installed
699 header files @emph{instead} of @file{/usr/local/include}.
701 You should specify @option{--with-local-prefix} @strong{only} if your
702 site has a different convention (not @file{/usr/local}) for where to put
705 The default value for @option{--with-local-prefix} is @file{/usr/local}
706 regardless of the value of @option{--prefix}. Specifying
707 @option{--prefix} has no effect on which directory GCC searches for
708 local header files. This may seem counterintuitive, but actually it is
711 The purpose of @option{--prefix} is to specify where to @emph{install
712 GCC}. The local header files in @file{/usr/local/include}---if you put
713 any in that directory---are not part of GCC@. They are part of other
714 programs---perhaps many others. (GCC installs its own header files in
715 another directory which is based on the @option{--prefix} value.)
717 Both the local-prefix include directory and the GCC-prefix include
718 directory are part of GCC's ``system include'' directories. Although these
719 two directories are not fixed, they need to be searched in the proper
720 order for the correct processing of the include_next directive. The
721 local-prefix include directory is searched before the GCC-prefix
722 include directory. Another characteristic of system include directories
723 is that pedantic warnings are turned off for headers in these directories.
725 Some autoconf macros add @option{-I @var{directory}} options to the
726 compiler command line, to ensure that directories containing installed
727 packages' headers are searched. When @var{directory} is one of GCC's
728 system include directories, GCC will ignore the option so that system
729 directories continue to be processed in the correct order. This
730 may result in a search order different from what was specified but the
731 directory will still be searched.
733 GCC automatically searches for ordinary libraries using
734 @env{GCC_EXEC_PREFIX}. Thus, when the same installation prefix is
735 used for both GCC and packages, GCC will automatically search for
736 both headers and libraries. This provides a configuration that is
737 easy to use. GCC behaves in a manner similar to that when it is
738 installed as a system compiler in @file{/usr}.
740 Sites that need to install multiple versions of GCC may not want to
741 use the above simple configuration. It is possible to use the
742 @option{--program-prefix}, @option{--program-suffix} and
743 @option{--program-transform-name} options to install multiple versions
744 into a single directory, but it may be simpler to use different prefixes
745 and the @option{--with-local-prefix} option to specify the location of the
746 site-specific files for each version. It will then be necessary for
747 users to specify explicitly the location of local site libraries
748 (e.g., with @env{LIBRARY_PATH}).
750 The same value can be used for both @option{--with-local-prefix} and
751 @option{--prefix} provided it is not @file{/usr}. This can be used
752 to avoid the default search of @file{/usr/local/include}.
754 @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
755 The directory you use for @option{--with-local-prefix} @strong{must not}
756 contain any of the system's standard header files. If it did contain
757 them, certain programs would be miscompiled (including GNU Emacs, on
758 certain targets), because this would override and nullify the header
759 file corrections made by the @command{fixincludes} script.
761 Indications are that people who use this option use it based on mistaken
762 ideas of what it is for. People use it as if it specified where to
763 install part of GCC@. Perhaps they make this assumption because
764 installing GCC creates the directory.
766 @item --enable-shared[=@var{package}[,@dots{}]]
767 Build shared versions of libraries, if shared libraries are supported on
768 the target platform. Unlike GCC 2.95.x and earlier, shared libraries
769 are enabled by default on all platforms that support shared libraries.
771 If a list of packages is given as an argument, build shared libraries
772 only for the listed packages. For other packages, only static libraries
773 will be built. Package names currently recognized in the GCC tree are
774 @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not
775 @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc},
776 @samp{ada}, @samp{libada}, @samp{libjava} and @samp{libobjc}.
777 Note @samp{libiberty} does not support shared libraries at all.
779 Use @option{--disable-shared} to build only static libraries. Note that
780 @option{--disable-shared} does not accept a list of package names as
781 argument, only @option{--enable-shared} does.
783 @item @anchor{with-gnu-as}--with-gnu-as
784 Specify that the compiler should assume that the
785 assembler it finds is the GNU assembler. However, this does not modify
786 the rules to find an assembler and will result in confusion if the
787 assembler found is not actually the GNU assembler. (Confusion may also
788 result if the compiler finds the GNU assembler but has not been
789 configured with @option{--with-gnu-as}.) If you have more than one
790 assembler installed on your system, you may want to use this option in
791 connection with @option{--with-as=@var{pathname}} or
792 @option{--with-build-time-tools=@var{pathname}}.
794 The following systems are the only ones where it makes a difference
795 whether you use the GNU assembler. On any other system,
796 @option{--with-gnu-as} has no effect.
799 @item @samp{hppa1.0-@var{any}-@var{any}}
800 @item @samp{hppa1.1-@var{any}-@var{any}}
801 @item @samp{i386-@var{any}-sysv}
802 @item @samp{m68k-bull-sysv}
803 @item @samp{m68k-hp-hpux}
804 @item @samp{m68000-hp-hpux}
805 @item @samp{m68000-att-sysv}
806 @item @samp{sparc-sun-solaris2.@var{any}}
807 @item @samp{sparc64-@var{any}-solaris2.@var{any}}
810 On the systems listed above (except for the HP-PA, the SPARC, for ISC on
811 the 386, if you use the GNU assembler, you should also use the GNU linker
812 (and specify @option{--with-gnu-ld}).
814 @item @anchor{with-as}--with-as=@var{pathname}
815 Specify that the compiler should use the assembler pointed to by
816 @var{pathname}, rather than the one found by the standard rules to find
817 an assembler, which are:
820 Unless GCC is being built with a cross compiler, check the
821 @file{@var{libexec}/gcc/@var{target}/@var{version}} directory.
822 @var{libexec} defaults to @file{@var{exec-prefix}/libexec};
823 @var{exec-prefix} defaults to @var{prefix}, which
824 defaults to @file{/usr/local} unless overridden by the
825 @option{--prefix=@var{pathname}} switch described above. @var{target}
826 is the target system triple, such as @samp{sparc-sun-solaris2.7}, and
827 @var{version} denotes the GCC version, such as 3.0.
830 If the target system is the same that you are building on, check
831 operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
835 Check in the @env{PATH} for a tool whose name is prefixed by the
836 target system triple.
839 Check in the @env{PATH} for a tool whose name is not prefixed by the
840 target system triple, if the host and target system triple are
841 the same (in other words, we use a host tool if it can be used for
845 You may want to use @option{--with-as} if no assembler
846 is installed in the directories listed above, or if you have multiple
847 assemblers installed and want to choose one that is not found by the
850 @item @anchor{with-gnu-ld}--with-gnu-ld
851 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
854 @item --with-ld=@var{pathname}
855 Same as @uref{#with-as,,@option{--with-as}}
859 Specify that stabs debugging
860 information should be used instead of whatever format the host normally
861 uses. Normally GCC uses the same debug format as the host system.
863 On MIPS based systems and on Alphas, you must specify whether you want
864 GCC to create the normal ECOFF debugging format, or to use BSD-style
865 stabs passed through the ECOFF symbol table. The normal ECOFF debug
866 format cannot fully handle languages other than C@. BSD stabs format can
867 handle other languages, but it only works with the GNU debugger GDB@.
869 Normally, GCC uses the ECOFF debugging format by default; if you
870 prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@.
872 No matter which default you choose when you configure GCC, the user
873 can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
874 the debug format for a particular compilation.
876 @option{--with-stabs} is meaningful on the ISC system on the 386, also, if
877 @option{--with-gas} is used. It selects use of stabs debugging
878 information embedded in COFF output. This kind of debugging information
879 supports C++ well; ordinary COFF debugging information does not.
881 @option{--with-stabs} is also meaningful on 386 systems running SVR4. It
882 selects use of stabs debugging information embedded in ELF output. The
883 C++ compiler currently (2.6.0) does not support the DWARF debugging
884 information normally used on 386 SVR4 platforms; stabs provide a
885 workable alternative. This requires gas and gdb, as the normal SVR4
886 tools can not generate or interpret stabs.
888 @item --disable-multilib
889 Specify that multiple target
890 libraries to support different target variants, calling
891 conventions, etc should not be built. The default is to build a
892 predefined set of them.
894 Some targets provide finer-grained control over which multilibs are built
895 (e.g., @option{--disable-softfloat}):
901 fpu, 26bit, underscore, interwork, biendian, nofmult.
904 softfloat, m68881, m68000, m68020.
907 single-float, biendian, softfloat.
909 @item powerpc*-*-*, rs6000*-*-*
910 aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
915 @item --enable-threads
916 Specify that the target
917 supports threads. This affects the Objective-C compiler and runtime
918 library, and exception handling for other languages like C++ and Java.
919 On some systems, this is the default.
921 In general, the best (and, in many cases, the only known) threading
922 model available will be configured for use. Beware that on some
923 systems, GCC has not been taught what threading models are generally
924 available for the system. In this case, @option{--enable-threads} is an
925 alias for @option{--enable-threads=single}.
927 @item --disable-threads
928 Specify that threading support should be disabled for the system.
929 This is an alias for @option{--enable-threads=single}.
931 @item --enable-threads=@var{lib}
933 @var{lib} is the thread support library. This affects the Objective-C
934 compiler and runtime library, and exception handling for other languages
935 like C++ and Java. The possibilities for @var{lib} are:
943 Ada tasking support. For non-Ada programs, this setting is equivalent
944 to @samp{single}. When used in conjunction with the Ada run time, it
945 causes GCC to use the same thread primitives as Ada uses. This option
946 is necessary when using both Ada and the back end exception handling,
947 which is the default for most Ada targets.
949 Generic MACH thread support, known to work on NeXTSTEP@. (Please note
950 that the file needed to support this configuration, @file{gthr-mach.h}, is
951 missing and thus this setting will cause a known bootstrap failure.)
953 This is an alias for @samp{single}.
955 Generic POSIX/Unix98 thread support.
957 Generic POSIX/Unix95 thread support.
959 RTEMS thread support.
961 Disable thread support, should work for all platforms.
963 Sun Solaris 2 thread support.
965 VxWorks thread support.
967 Microsoft Win32 API thread support.
969 Novell Kernel Services thread support.
973 Specify that the target supports TLS (Thread Local Storage). Usually
974 configure can correctly determine if TLS is supported. In cases where
975 it guesses incorrectly, TLS can be explicitly enabled or disabled with
976 @option{--enable-tls} or @option{--disable-tls}. This can happen if
977 the assembler supports TLS but the C library does not, or if the
978 assumptions made by the configure test are incorrect.
981 Specify that the target does not support TLS.
982 This is an alias for @option{--enable-tls=no}.
984 @item --with-cpu=@var{cpu}
985 Specify which cpu variant the compiler should generate code for by default.
986 @var{cpu} will be used as the default value of the @option{-mcpu=} switch.
987 This option is only supported on some targets, including ARM, i386, PowerPC,
990 @item --with-schedule=@var{cpu}
991 @itemx --with-arch=@var{cpu}
992 @itemx --with-tune=@var{cpu}
993 @itemx --with-abi=@var{abi}
994 @itemx --with-fpu=@var{type}
995 @itemx --with-float=@var{type}
996 These configure options provide default values for the @option{-mschedule=},
997 @option{-march=}, @option{-mtune=}, @option{-mabi=}, and @option{-mfpu=}
998 options and for @option{-mhard-float} or @option{-msoft-float}. As with
999 @option{--with-cpu}, which switches will be accepted and acceptable values
1000 of the arguments depend on the target.
1002 @item --with-mode=@var{mode}
1003 Specify if the compiler should default to @option{-marm} or @option{-mthumb}.
1004 This option is only supported on ARM targets.
1006 @item --with-divide=@var{type}
1007 Specify how the compiler should generate code for checking for
1008 division by zero. This option is only supported on the MIPS target.
1009 The possibilities for @var{type} are:
1012 Division by zero checks use conditional traps (this is the default on
1013 systems that support conditional traps).
1015 Division by zero checks use the break instruction.
1018 @item --enable-__cxa_atexit
1019 Define if you want to use __cxa_atexit, rather than atexit, to
1020 register C++ destructors for local statics and global objects.
1021 This is essential for fully standards-compliant handling of
1022 destructors, but requires __cxa_atexit in libc. This option is currently
1023 only available on systems with GNU libc. When enabled, this will cause
1024 @option{-fuse-cxa-exit} to be passed by default.
1026 @item --enable-target-optspace
1028 libraries should be optimized for code space instead of code speed.
1029 This is the default for the m32r platform.
1032 Specify that a user visible @command{cpp} program should not be installed.
1034 @item --with-cpp-install-dir=@var{dirname}
1035 Specify that the user visible @command{cpp} program should be installed
1036 in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
1038 @item --enable-initfini-array
1039 Force the use of sections @code{.init_array} and @code{.fini_array}
1040 (instead of @code{.init} and @code{.fini}) for constructors and
1041 destructors. Option @option{--disable-initfini-array} has the
1042 opposite effect. If neither option is specified, the configure script
1043 will try to guess whether the @code{.init_array} and
1044 @code{.fini_array} sections are supported and, if they are, use them.
1046 @item --enable-maintainer-mode
1047 The build rules that
1048 regenerate the GCC master message catalog @file{gcc.pot} are normally
1049 disabled. This is because it can only be rebuilt if the complete source
1050 tree is present. If you have changed the sources and want to rebuild the
1051 catalog, configuring with @option{--enable-maintainer-mode} will enable
1052 this. Note that you need a recent version of the @code{gettext} tools
1055 @item --enable-generated-files-in-srcdir
1056 Neither the .c and .h files that are generated from Bison and flex nor the
1057 info manuals and man pages that are built from the .texi files are present
1058 in the SVN development tree. When building GCC from that development tree,
1059 or from one of our snapshots, those generated files are placed in your
1060 build directory, which allows for the source to be in a readonly
1063 If you configure with @option{--enable-generated-files-in-srcdir} then those
1064 generated files will go into the source directory. This is mainly intended
1065 for generating release or prerelease tarballs of the GCC sources, since it
1066 is not a requirement that the users of source releases to have flex, Bison,
1069 @item --enable-version-specific-runtime-libs
1071 that runtime libraries should be installed in the compiler specific
1072 subdirectory (@file{@var{libdir}/gcc}) rather than the usual places. In
1073 addition, @samp{libstdc++}'s include files will be installed into
1074 @file{@var{libdir}} unless you overruled it by using
1075 @option{--with-gxx-include-dir=@var{dirname}}. Using this option is
1076 particularly useful if you intend to use several versions of GCC in
1077 parallel. This is currently supported by @samp{libgfortran},
1078 @samp{libjava}, @samp{libmudflap}, @samp{libstdc++}, and @samp{libobjc}.
1080 @item --with-java-home=@var{dirname}
1081 This @samp{libjava} option overrides the default value of the
1082 @samp{java.home} system property. It is also used to set
1083 @samp{sun.boot.class.path} to @file{@var{dirname}/lib/rt.jar}. By
1084 default @samp{java.home} is set to @file{@var{prefix}} and
1085 @samp{sun.boot.class.path} to
1086 @file{@var{datadir}/java/libgcj-@var{version}.jar}.
1088 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
1089 Specify that only a particular subset of compilers and
1090 their runtime libraries should be built. For a list of valid values for
1091 @var{langN} you can issue the following command in the
1092 @file{gcc} directory of your GCC source tree:@*
1094 grep language= */config-lang.in
1096 Currently, you can use any of the following:
1097 @code{all}, @code{ada}, @code{c}, @code{c++}, @code{fortran}, @code{java},
1098 @code{objc}, @code{obj-c++}, @code{treelang}.
1099 Building the Ada compiler has special requirements, see below.
1100 If you do not pass this flag, or specify the option @code{all}, then all
1101 default languages available in the @file{gcc} sub-tree will be configured.
1102 Ada, Objective-C++, and treelang are not default languages; the rest are.
1103 Re-defining @code{LANGUAGES} when calling @samp{make} @strong{does not}
1104 work anymore, as those language sub-directories might not have been
1107 @item --disable-libada
1108 Specify that the run-time libraries and tools used by GNAT should not
1109 be built. This can be useful for debugging, or for compatibility with
1110 previous Ada build procedures, when it was required to explicitly
1111 do a @samp{make -C gcc gnatlib_and_tools}.
1113 @item --disable-libssp
1114 Specify that the run-time libraries for stack smashing protection
1115 should not be built.
1117 @item --disable-libgomp
1118 Specify that the run-time libraries used by GOMP should not be built.
1121 Specify that the compiler should
1122 use DWARF 2 debugging information as the default.
1124 @item --enable-targets=all
1125 @itemx --enable-targets=@var{target_list}
1126 Some GCC targets, e.g.@: powerpc64-linux, build bi-arch compilers.
1127 These are compilers that are able to generate either 64-bit or 32-bit
1128 code. Typically, the corresponding 32-bit target, e.g.@:
1129 powerpc-linux for powerpc64-linux, only generates 32-bit code. This
1130 option enables the 32-bit target to be a bi-arch compiler, which is
1131 useful when you want a bi-arch compiler that defaults to 32-bit, and
1132 you are building a bi-arch or multi-arch binutils in a combined tree.
1133 Currently, this option only affects powerpc-linux.
1135 @item --enable-secureplt
1136 This option enables @option{-msecure-plt} by default for powerpc-linux.
1138 @xref{RS/6000 and PowerPC Options,, RS/6000 and PowerPC Options, gcc,
1139 Using the GNU Compiler Collection (GCC)},
1142 See ``RS/6000 and PowerPC Options'' in the main manual
1145 @item --enable-win32-registry
1146 @itemx --enable-win32-registry=@var{key}
1147 @itemx --disable-win32-registry
1148 The @option{--enable-win32-registry} option enables Microsoft Windows-hosted GCC
1149 to look up installations paths in the registry using the following key:
1152 @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
1155 @var{key} defaults to GCC version number, and can be overridden by the
1156 @option{--enable-win32-registry=@var{key}} option. Vendors and distributors
1157 who use custom installers are encouraged to provide a different key,
1158 perhaps one comprised of vendor name and GCC version number, to
1159 avoid conflict with existing installations. This feature is enabled
1160 by default, and can be disabled by @option{--disable-win32-registry}
1161 option. This option has no effect on the other hosts.
1164 Specify that the machine does not have a floating point unit. This
1165 option only applies to @samp{m68k-sun-sunos@var{n}}. On any other
1166 system, @option{--nfp} has no effect.
1168 @item --enable-werror
1169 @itemx --disable-werror
1170 @itemx --enable-werror=yes
1171 @itemx --enable-werror=no
1172 When you specify this option, it controls whether certain files in the
1173 compiler are built with @option{-Werror} in bootstrap stage2 and later.
1174 If you don't specify it, @option{-Werror} is turned on for the main
1175 development trunk. However it defaults to off for release branches and
1176 final releases. The specific files which get @option{-Werror} are
1177 controlled by the Makefiles.
1179 @item --enable-checking
1180 @itemx --enable-checking=@var{list}
1181 When you specify this option, the compiler is built to perform internal
1182 consistency checks of the requested complexity. This does not change the
1183 generated code, but adds error checking within the compiler. This will
1184 slow down the compiler and may only work properly if you are building
1185 the compiler with GCC@. This is @samp{yes} by default when building
1186 from SVN or snapshots, but @samp{release} for releases. More control
1187 over the checks may be had by specifying @var{list}. The categories of
1188 checks available are @samp{yes} (most common checks
1189 @samp{assert,misc,tree,gc,rtlflag,runtime}), @samp{no} (no checks at
1190 all), @samp{all} (all but @samp{valgrind}), @samp{release} (cheapest
1191 checks @samp{assert,runtime}) or @samp{none} (same as @samp{no}).
1192 Individual checks can be enabled with these flags @samp{assert},
1193 @samp{fold}, @samp{gc}, @samp{gcac} @samp{misc}, @samp{rtl},
1194 @samp{rtlflag}, @samp{runtime}, @samp{tree}, and @samp{valgrind}.
1196 The @samp{valgrind} check requires the external @command{valgrind}
1197 simulator, available from @uref{http://valgrind.org/}. The
1198 @samp{rtl}, @samp{gcac} and @samp{valgrind} checks are very expensive.
1199 To disable all checking, @samp{--disable-checking} or
1200 @samp{--enable-checking=none} must be explicitly requested. Disabling
1201 assertions will make the compiler and runtime slightly faster but
1202 increase the risk of undetected internal errors causing wrong code to be
1205 @item --enable-coverage
1206 @itemx --enable-coverage=@var{level}
1207 With this option, the compiler is built to collect self coverage
1208 information, every time it is run. This is for internal development
1209 purposes, and only works when the compiler is being built with gcc. The
1210 @var{level} argument controls whether the compiler is built optimized or
1211 not, values are @samp{opt} and @samp{noopt}. For coverage analysis you
1212 want to disable optimization, for performance analysis you want to
1213 enable optimization. When coverage is enabled, the default level is
1214 without optimization.
1216 @item --enable-gather-detailed-mem-stats
1217 When this option is specified more detailed information on memory
1218 allocation is gathered. This information is printed when using
1219 @option{-fmem-report}.
1222 @itemx --with-gc=@var{choice}
1223 With this option you can specify the garbage collector implementation
1224 used during the compilation process. @var{choice} can be one of
1225 @samp{page} and @samp{zone}, where @samp{page} is the default.
1228 @itemx --disable-nls
1229 The @option{--enable-nls} option enables Native Language Support (NLS),
1230 which lets GCC output diagnostics in languages other than American
1231 English. Native Language Support is enabled by default if not doing a
1232 canadian cross build. The @option{--disable-nls} option disables NLS@.
1234 @item --with-included-gettext
1235 If NLS is enabled, the @option{--with-included-gettext} option causes the build
1236 procedure to prefer its copy of GNU @command{gettext}.
1238 @item --with-catgets
1239 If NLS is enabled, and if the host lacks @code{gettext} but has the
1240 inferior @code{catgets} interface, the GCC build procedure normally
1241 ignores @code{catgets} and instead uses GCC's copy of the GNU
1242 @code{gettext} library. The @option{--with-catgets} option causes the
1243 build procedure to use the host's @code{catgets} in this situation.
1245 @item --with-libiconv-prefix=@var{dir}
1246 Search for libiconv header files in @file{@var{dir}/include} and
1247 libiconv library files in @file{@var{dir}/lib}.
1249 @item --enable-obsolete
1250 Enable configuration for an obsoleted system. If you attempt to
1251 configure GCC for a system (build, host, or target) which has been
1252 obsoleted, and you do not specify this flag, configure will halt with an
1255 All support for systems which have been obsoleted in one release of GCC
1256 is removed entirely in the next major release, unless someone steps
1257 forward to maintain the port.
1259 @item --enable-decimal-float
1260 @itemx --disable-decimal-float
1261 Enable (or disable) support for the C decimal floating point
1262 extension. This is enabled by default only on PowerPC GNU/Linux
1263 systems. Other systems may also support it, but require the user to
1264 specifically enable it.
1266 @item --with-long-double-128
1267 Specify if @code{long double} type should be 128-bit by default on selected
1268 GNU/Linux architectures. If using @code{--without-long-double-128},
1269 @code{long double} will be by default 64-bit, the same as @code{double} type.
1270 When neither of these configure options are used, the default will be
1271 128-bit @code{long double} when built against GNU C Library 2.4 and later,
1272 64-bit @code{long double} otherwise.
1276 @subheading Cross-Compiler-Specific Options
1277 The following options only apply to building cross compilers.
1279 @item --with-sysroot
1280 @itemx --with-sysroot=@var{dir}
1281 Tells GCC to consider @var{dir} as the root of a tree that contains a
1282 (subset of) the root filesystem of the target operating system.
1283 Target system headers, libraries and run-time object files will be
1284 searched in there. The specified directory is not copied into the
1285 install tree, unlike the options @option{--with-headers} and
1286 @option{--with-libs} that this option obsoletes. The default value,
1287 in case @option{--with-sysroot} is not given an argument, is
1288 @option{$@{gcc_tooldir@}/sys-root}. If the specified directory is a
1289 subdirectory of @option{$@{exec_prefix@}}, then it will be found relative to
1290 the GCC binaries if the installation tree is moved.
1292 @item --with-build-sysroot
1293 @itemx --with-build-sysroot=@var{dir}
1294 Tells GCC to consider @var{dir} as the system root (see
1295 @option{--with-sysroot}) while building target libraries, instead of
1296 the directory specified with @option{--with-sysroot}. This option is
1297 only useful when you are already using @option{--with-sysroot}. You
1298 can use @option{--with-build-sysroot} when you are configuring with
1299 @option{--prefix} set to a directory that is different from the one in
1300 which you are installing GCC and your target libraries.
1302 This option affects the system root for the compiler used to build
1303 target libraries (which runs on the build system); it does not affect
1304 the compiler which is used to build GCC itself.
1306 @item --with-headers
1307 @itemx --with-headers=@var{dir}
1308 Deprecated in favor of @option{--with-sysroot}.
1309 Specifies that target headers are available when building a cross compiler.
1310 The @var{dir} argument specifies a directory which has the target include
1311 files. These include files will be copied into the @file{gcc} install
1312 directory. @emph{This option with the @var{dir} argument is required} when
1313 building a cross compiler, if @file{@var{prefix}/@var{target}/sys-include}
1314 doesn't pre-exist. If @file{@var{prefix}/@var{target}/sys-include} does
1315 pre-exist, the @var{dir} argument may be omitted. @command{fixincludes}
1316 will be run on these files to make them compatible with GCC@.
1318 @item --without-headers
1319 Tells GCC not use any target headers from a libc when building a cross
1320 compiler. When crossing to GNU/Linux, you need the headers so GCC
1321 can build the exception handling for libgcc.
1322 See @uref{http://www.objsw.com/CrossGCC/,,CrossGCC} for more information
1326 @itemx --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}''
1327 Deprecated in favor of @option{--with-sysroot}.
1328 Specifies a list of directories which contain the target runtime
1329 libraries. These libraries will be copied into the @file{gcc} install
1330 directory. If the directory list is omitted, this option has no
1334 Specifies that @samp{newlib} is
1335 being used as the target C library. This causes @code{__eprintf} to be
1336 omitted from @file{libgcc.a} on the assumption that it will be provided by
1339 @item --with-build-time-tools=@var{dir}
1340 Specifies where to find the set of target tools (assembler, linker, etc.)
1341 that will be used while building GCC itself. This option can be useful
1342 if the directory layouts are different between the system you are building
1343 GCC on, and the system where you will deploy it.
1345 For example, on a @option{ia64-hp-hpux} system, you may have the GNU
1346 assembler and linker in @file{/usr/bin}, and the native tools in a
1347 different path, and build a toolchain that expects to find the
1348 native tools in @file{/usr/bin}.
1350 When you use this option, you should ensure that @var{dir} includes
1351 @command{ar}, @command{as}, @command{ld}, @command{nm},
1352 @command{ranlib} and @command{strip} if necessary, and possibly
1353 @command{objdump}. Otherwise, GCC may use an inconsistent set of
1357 @subheading Fortran-Specific Options
1359 The following options apply to the build of the Fortran front end.
1363 @item --with-gmp=@var{pathname}
1364 @itemx --with-mpfr=@var{pathname}
1365 @itemx --with-gmp-dir=@var{pathname}
1366 @itemx --with-mpfr-dir=@var{pathname}
1367 If you don't have GMP (the GNU Multiple Precision library) and the MPFR
1368 Libraries installed in a standard location and you want to build the Fortran
1369 front-end, you can explicitly specify the directory where they are installed
1370 (@samp{--with-gmp=gmpinstalldir}, @samp{--with-mpfr=mpfrinstalldir}) or where
1371 you built them without installing (@samp{--with-gmp-dir=gmpbuilddir},
1372 @samp{--with-mpfr-dir=gmpbuilddir}).
1376 @subheading Java-Specific Options
1378 The following option applies to the build of the Java front end.
1381 @item --disable-libgcj
1382 Specify that the run-time libraries
1383 used by GCJ should not be built. This is useful in case you intend
1384 to use GCJ with some other run-time, or you're going to install it
1385 separately, or it just happens not to build on your particular
1386 machine. In general, if the Java front end is enabled, the GCJ
1387 libraries will be enabled too, unless they're known to not work on
1388 the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
1389 may need to port it; in this case, before modifying the top-level
1390 @file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
1391 you may use @option{--enable-libgcj} to override the default.
1395 The following options apply to building @samp{libgcj}.
1397 @subsubheading General Options
1400 @item --disable-getenv-properties
1401 Don't set system properties from @env{GCJ_PROPERTIES}.
1403 @item --enable-hash-synchronization
1404 Use a global hash table for monitor locks. Ordinarily,
1405 @samp{libgcj}'s @samp{configure} script automatically makes
1406 the correct choice for this option for your platform. Only use
1407 this if you know you need the library to be configured differently.
1409 @item --enable-interpreter
1410 Enable the Java interpreter. The interpreter is automatically
1411 enabled by default on all platforms that support it. This option
1412 is really only useful if you want to disable the interpreter
1413 (using @option{--disable-interpreter}).
1415 @item --disable-java-net
1416 Disable java.net. This disables the native part of java.net only,
1417 using non-functional stubs for native method implementations.
1419 @item --disable-jvmpi
1420 Disable JVMPI support.
1423 Enable runtime eCos target support.
1425 @item --without-libffi
1426 Don't use @samp{libffi}. This will disable the interpreter and JNI
1427 support as well, as these require @samp{libffi} to work.
1429 @item --enable-libgcj-debug
1430 Enable runtime debugging code.
1432 @item --enable-libgcj-multifile
1433 If specified, causes all @file{.java} source files to be
1434 compiled into @file{.class} files in one invocation of
1435 @samp{gcj}. This can speed up build time, but is more
1436 resource-intensive. If this option is unspecified or
1437 disabled, @samp{gcj} is invoked once for each @file{.java}
1438 file to compile into a @file{.class} file.
1440 @item --with-libiconv-prefix=DIR
1441 Search for libiconv in @file{DIR/include} and @file{DIR/lib}.
1443 @item --enable-sjlj-exceptions
1444 Force use of @code{builtin_setjmp} for exceptions. @samp{configure}
1445 ordinarily picks the correct value based on the platform. Only use
1446 this option if you are sure you need a different setting.
1448 @item --with-system-zlib
1449 Use installed @samp{zlib} rather than that included with GCC@.
1451 @item --with-win32-nlsapi=ansi, unicows or unicode
1452 Indicates how MinGW @samp{libgcj} translates between UNICODE
1453 characters and the Win32 API@.
1456 Use the single-byte @code{char} and the Win32 A functions natively,
1457 translating to and from UNICODE when using these functions. If
1458 unspecified, this is the default.
1461 Use the @code{WCHAR} and Win32 W functions natively. Adds
1462 @code{-lunicows} to @file{libgcj.spec} to link with @samp{libunicows}.
1463 @file{unicows.dll} needs to be deployed on Microsoft Windows 9X machines
1464 running built executables. @file{libunicows.a}, an open-source
1465 import library around Microsoft's @code{unicows.dll}, is obtained from
1466 @uref{http://libunicows.sourceforge.net/}, which also gives details
1467 on getting @file{unicows.dll} from Microsoft.
1470 Use the @code{WCHAR} and Win32 W functions natively. Does @emph{not}
1471 add @code{-lunicows} to @file{libgcj.spec}. The built executables will
1472 only run on Microsoft Windows NT and above.
1476 @subsubheading AWT-Specific Options
1480 Use the X Window System.
1482 @item --enable-java-awt=PEER(S)
1483 Specifies the AWT peer library or libraries to build alongside
1484 @samp{libgcj}. If this option is unspecified or disabled, AWT
1485 will be non-functional. Current valid values are @option{gtk} and
1486 @option{xlib}. Multiple libraries should be separated by a
1487 comma (i.e.@: @option{--enable-java-awt=gtk,xlib}).
1489 @item --enable-gtk-cairo
1490 Build the cairo Graphics2D implementation on GTK@.
1492 @item --enable-java-gc=TYPE
1493 Choose garbage collector. Defaults to @option{boehm} if unspecified.
1495 @item --disable-gtktest
1496 Do not try to compile and run a test GTK+ program.
1498 @item --disable-glibtest
1499 Do not try to compile and run a test GLIB program.
1501 @item --with-libart-prefix=PFX
1502 Prefix where libart is installed (optional).
1504 @item --with-libart-exec-prefix=PFX
1505 Exec prefix where libart is installed (optional).
1507 @item --disable-libarttest
1508 Do not try to compile and run a test libart program.
1517 @uref{./index.html,,Return to the GCC Installation page}
1521 @c ***Building****************************************************************
1523 @comment node-name, next, previous, up
1524 @node Building, Testing, Configuration, Installing GCC
1530 @cindex Installing GCC: Building
1532 Now that GCC is configured, you are ready to build the compiler and
1535 Some commands executed when making the compiler may fail (return a
1536 nonzero status) and be ignored by @command{make}. These failures, which
1537 are often due to files that were not found, are expected, and can safely
1540 It is normal to have compiler warnings when compiling certain files.
1541 Unless you are a GCC developer, you can generally ignore these warnings
1542 unless they cause compilation to fail. Developers should attempt to fix
1543 any warnings encountered, however they can temporarily continue past
1544 warnings-as-errors by specifying the configure flag
1545 @option{--disable-werror}.
1547 On certain old systems, defining certain environment variables such as
1548 @env{CC} can interfere with the functioning of @command{make}.
1550 If you encounter seemingly strange errors when trying to build the
1551 compiler in a directory other than the source directory, it could be
1552 because you have previously configured the compiler in the source
1553 directory. Make sure you have done all the necessary preparations.
1555 If you build GCC on a BSD system using a directory stored in an old System
1556 V file system, problems may occur in running @command{fixincludes} if the
1557 System V file system doesn't support symbolic links. These problems
1558 result in a failure to fix the declaration of @code{size_t} in
1559 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
1560 that type mismatches occur, this could be the cause.
1562 The solution is not to use such a directory for building GCC@.
1564 When building from SVN or snapshots, or if you modify parser sources,
1565 you need the Bison parser generator installed. If you do not modify
1566 parser sources, releases contain the Bison-generated files and you do
1567 not need Bison installed to build them.
1569 When building from SVN or snapshots, or if you modify Texinfo
1570 documentation, you need version 4.4 or later of Texinfo installed if you
1571 want Info documentation to be regenerated. Releases contain Info
1572 documentation pre-built for the unmodified documentation in the release.
1574 @section Building a native compiler
1576 For a native build, the command @samp{make} will trigger a 3-stage
1577 bootstrap of the compiler. This will build the entire GCC system
1578 and ensure that it compiles itself correctly, by doing the
1583 Build tools necessary to build the compiler.
1586 Perform a 3-stage bootstrap of the compiler. This includes building
1587 three times the target tools for use by the compiler such as binutils
1588 (bfd, binutils, gas, gprof, ld, and opcodes) if they have been
1589 individually linked or moved into the top level GCC source tree before
1593 Perform a comparison test of the stage2 and stage3 compilers.
1596 Build runtime libraries using the stage3 compiler from the previous step.
1600 If you are short on disk space you might consider @samp{make
1601 bootstrap-lean} instead. The sequence of compilation is the
1602 same described above, but object files from the stage1 and
1603 stage2 of the 3-stage bootstrap of the compiler are deleted as
1604 soon as they are no longer needed.
1606 If you want to save additional space during the bootstrap and in
1607 the final installation as well, you can build the compiler binaries
1608 without debugging information as in the following example. This will save
1609 roughly 40% of disk space both for the bootstrap and the final installation.
1610 (Libraries will still contain debugging information.)
1613 make CFLAGS='-O' LIBCFLAGS='-g -O2' \
1614 LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap
1617 If you wish to use non-default GCC flags when compiling the stage2 and
1618 stage3 compilers, set @code{BOOT_CFLAGS} on the command line when doing
1619 @samp{make}. Non-default optimization flags are less well
1620 tested here than the default of @samp{-g -O2}, but should still work.
1621 In a few cases, you may find that you need to specify special flags such
1622 as @option{-msoft-float} here to complete the bootstrap; or, if the
1623 native compiler miscompiles the stage1 compiler, you may need to work
1624 around this, by choosing @code{BOOT_CFLAGS} to avoid the parts of the
1625 stage1 compiler that were miscompiled, or by using @samp{make
1626 bootstrap4} to increase the number of stages of bootstrap.
1628 Note that using non-standard @code{CFLAGS} can cause bootstrap to fail
1629 if these trigger a warning with the new compiler. For example using
1630 @samp{-O2 -g -mcpu=i686} on @code{i686-pc-linux-gnu} will cause bootstrap
1631 failure as @option{-mcpu=} is deprecated in 3.4.0 and above.
1634 If you used the flag @option{--enable-languages=@dots{}} to restrict
1635 the compilers to be built, only those you've actually enabled will be
1636 built. This will of course only build those runtime libraries, for
1637 which the particular compiler has been built. Please note,
1638 that re-defining @env{LANGUAGES} when calling @samp{make}
1639 @strong{does not} work anymore!
1641 If the comparison of stage2 and stage3 fails, this normally indicates
1642 that the stage2 compiler has compiled GCC incorrectly, and is therefore
1643 a potentially serious bug which you should investigate and report. (On
1644 a few systems, meaningful comparison of object files is impossible; they
1645 always appear ``different''. If you encounter this problem, you will
1646 need to disable comparison in the @file{Makefile}.)
1648 If you do not want to bootstrap your compiler, you can configure with
1649 @option{--disable-bootstrap}. In particular cases, you may want to
1650 bootstrap your compiler even if the target system is not the same as
1651 the one you are building on: for example, you could build a
1652 @code{powerpc-unknown-linux-gnu} toolchain on a
1653 @code{powerpc64-unknown-linux-gnu} host. In this case, pass
1654 @option{--enable-bootstrap} to the configure script.
1657 @section Building a cross compiler
1659 We recommend reading the
1660 @uref{http://www.objsw.com/CrossGCC/,,crossgcc FAQ}
1661 for information about building cross compilers.
1663 When building a cross compiler, it is not generally possible to do a
1664 3-stage bootstrap of the compiler. This makes for an interesting problem
1665 as parts of GCC can only be built with GCC@.
1667 To build a cross compiler, we first recommend building and installing a
1668 native compiler. You can then use the native GCC compiler to build the
1669 cross compiler. The installed native compiler needs to be GCC version
1672 Assuming you have already installed a native copy of GCC and configured
1673 your cross compiler, issue the command @command{make}, which performs the
1678 Build host tools necessary to build the compiler.
1681 Build target tools for use by the compiler such as binutils (bfd,
1682 binutils, gas, gprof, ld, and opcodes)
1683 if they have been individually linked or moved into the top level GCC source
1684 tree before configuring.
1687 Build the compiler (single stage only).
1690 Build runtime libraries using the compiler from the previous step.
1693 Note that if an error occurs in any step the make process will exit.
1695 If you are not building GNU binutils in the same source tree as GCC,
1696 you will need a cross-assembler and cross-linker installed before
1697 configuring GCC@. Put them in the directory
1698 @file{@var{prefix}/@var{target}/bin}. Here is a table of the tools
1699 you should put in this directory:
1703 This should be the cross-assembler.
1706 This should be the cross-linker.
1709 This should be the cross-archiver: a program which can manipulate
1710 archive files (linker libraries) in the target machine's format.
1713 This should be a program to construct a symbol table in an archive file.
1716 The installation of GCC will find these programs in that directory,
1717 and copy or link them to the proper place to for the cross-compiler to
1718 find them when run later.
1720 The easiest way to provide these files is to build the Binutils package.
1721 Configure it with the same @option{--host} and @option{--target}
1722 options that you use for configuring GCC, then build and install
1723 them. They install their executables automatically into the proper
1724 directory. Alas, they do not support all the targets that GCC
1727 If you are not building a C library in the same source tree as GCC,
1728 you should also provide the target libraries and headers before
1729 configuring GCC, specifying the directories with
1730 @option{--with-sysroot} or @option{--with-headers} and
1731 @option{--with-libs}. Many targets also require ``start files'' such
1732 as @file{crt0.o} and
1733 @file{crtn.o} which are linked into each executable. There may be several
1734 alternatives for @file{crt0.o}, for use with profiling or other
1735 compilation options. Check your target's definition of
1736 @code{STARTFILE_SPEC} to find out what start files it uses.
1738 @section Building in parallel
1740 GNU Make 3.79 and above, which is necessary to build GCC, support
1741 building in parallel. To activate this, you can use @samp{make -j 2}
1742 instead of @samp{make}. You can also specify a bigger number, and
1743 in most cases using a value greater than the number of processors in
1744 your machine will result in fewer and shorter I/O latency hits, thus
1745 improving overall throughput; this is especially true for slow drives
1746 and network filesystems.
1748 @section Building the Ada compiler
1750 In order to build GNAT, the Ada compiler, you need a working GNAT
1751 compiler (GNAT version 3.14 or later, or GCC version 3.1 or later).
1752 This includes GNAT tools such as @command{gnatmake} and
1753 @command{gnatlink}, since the Ada front end is written in Ada and
1754 uses some GNAT-specific extensions.
1756 In order to build a cross compiler, it is suggested to install
1757 the new compiler as native first, and then use it to build the cross
1760 @command{configure} does not test whether the GNAT installation works
1761 and has a sufficiently recent version; if too old a GNAT version is
1762 installed, the build will fail unless @option{--enable-languages} is
1763 used to disable building the Ada front end.
1765 @section Building with profile feedback
1767 It is possible to use profile feedback to optimize the compiler itself. This
1768 should result in a faster compiler binary. Experiments done on x86 using gcc
1769 3.3 showed approximately 7 percent speedup on compiling C programs. To
1770 bootstrap the compiler with profile feedback, use @code{make profiledbootstrap}.
1772 When @samp{make profiledbootstrap} is run, it will first build a @code{stage1}
1773 compiler. This compiler is used to build a @code{stageprofile} compiler
1774 instrumented to collect execution counts of instruction and branch
1775 probabilities. Then runtime libraries are compiled with profile collected.
1776 Finally a @code{stagefeedback} compiler is built using the information collected.
1778 Unlike standard bootstrap, several additional restrictions apply. The
1779 compiler used to build @code{stage1} needs to support a 64-bit integral type.
1780 It is recommended to only use GCC for this. Also parallel make is currently
1781 not supported since collisions in profile collecting may occur.
1788 @uref{./index.html,,Return to the GCC Installation page}
1792 @c ***Testing*****************************************************************
1794 @comment node-name, next, previous, up
1795 @node Testing, Final install, Building, Installing GCC
1799 @chapter Installing GCC: Testing
1802 @cindex Installing GCC: Testing
1805 Before you install GCC, we encourage you to run the testsuites and to
1806 compare your results with results from a similar configuration that have
1807 been submitted to the
1808 @uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
1809 Some of these archived results are linked from the build status lists
1810 at @uref{http://gcc.gnu.org/buildstat.html}, although not everyone who
1811 reports a successful build runs the testsuites and submits the results.
1812 This step is optional and may require you to download additional software,
1813 but it can give you confidence in your new GCC installation or point out
1814 problems before you install and start using your new GCC@.
1816 First, you must have @uref{download.html,,downloaded the testsuites}.
1817 These are part of the full distribution, but if you downloaded the
1818 ``core'' compiler plus any front ends, you must download the testsuites
1821 Second, you must have the testing tools installed. This includes
1822 @uref{http://www.gnu.org/software/dejagnu/,,DejaGnu}, Tcl, and Expect;
1823 the DejaGnu site has links to these.
1825 If the directories where @command{runtest} and @command{expect} were
1826 installed are not in the @env{PATH}, you may need to set the following
1827 environment variables appropriately, as in the following example (which
1828 assumes that DejaGnu has been installed under @file{/usr/local}):
1831 TCL_LIBRARY = /usr/local/share/tcl8.0
1832 DEJAGNULIBS = /usr/local/share/dejagnu
1835 (On systems such as Cygwin, these paths are required to be actual
1836 paths, not mounts or links; presumably this is due to some lack of
1837 portability in the DejaGnu code.)
1840 Finally, you can run the testsuite (which may take a long time):
1842 cd @var{objdir}; make -k check
1845 This will test various components of GCC, such as compiler
1846 front ends and runtime libraries. While running the testsuite, DejaGnu
1847 might emit some harmless messages resembling
1848 @samp{WARNING: Couldn't find the global config file.} or
1849 @samp{WARNING: Couldn't find tool init file} that can be ignored.
1851 @section How can you run the testsuite on selected tests?
1853 In order to run sets of tests selectively, there are targets
1854 @samp{make check-gcc} and @samp{make check-g++}
1855 in the @file{gcc} subdirectory of the object directory. You can also
1856 just run @samp{make check} in a subdirectory of the object directory.
1859 A more selective way to just run all @command{gcc} execute tests in the
1863 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
1866 Likewise, in order to run only the @command{g++} ``old-deja'' tests in
1867 the testsuite with filenames matching @samp{9805*}, you would use
1870 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
1873 The @file{*.exp} files are located in the testsuite directories of the GCC
1874 source, the most important ones being @file{compile.exp},
1875 @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
1876 To get a list of the possible @file{*.exp} files, pipe the
1877 output of @samp{make check} into a file and look at the
1878 @samp{Running @dots{} .exp} lines.
1880 @section Passing options and running multiple testsuites
1882 You can pass multiple options to the testsuite using the
1883 @samp{--target_board} option of DejaGNU, either passed as part of
1884 @samp{RUNTESTFLAGS}, or directly to @command{runtest} if you prefer to
1885 work outside the makefiles. For example,
1888 make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fno-strength-reduce"
1891 will run the standard @command{g++} testsuites (``unix'' is the target name
1892 for a standard native testsuite situation), passing
1893 @samp{-O3 -fno-strength-reduce} to the compiler on every test, i.e.,
1894 slashes separate options.
1896 You can run the testsuites multiple times using combinations of options
1897 with a syntax similar to the brace expansion of popular shells:
1900 @dots{}"--target_board=arm-sim/@{-mhard-float,-msoft-float@}@{-O1,-O2,-O3,@}"
1903 (Note the empty option caused by the trailing comma in the final group.)
1904 The following will run each testsuite eight times using the @samp{arm-sim}
1905 target, as if you had specified all possible combinations yourself:
1908 --target_board=arm-sim/-mhard-float/-O1
1909 --target_board=arm-sim/-mhard-float/-O2
1910 --target_board=arm-sim/-mhard-float/-O3
1911 --target_board=arm-sim/-mhard-float
1912 --target_board=arm-sim/-msoft-float/-O1
1913 --target_board=arm-sim/-msoft-float/-O2
1914 --target_board=arm-sim/-msoft-float/-O3
1915 --target_board=arm-sim/-msoft-float
1918 They can be combined as many times as you wish, in arbitrary ways. This
1922 @dots{}"--target_board=unix/-Wextra@{-O3,-fno-strength-reduce@}@{-fomit-frame-pointer,@}"
1925 will generate four combinations, all involving @samp{-Wextra}.
1927 The disadvantage to this method is that the testsuites are run in serial,
1928 which is a waste on multiprocessor systems. For users with GNU Make and
1929 a shell which performs brace expansion, you can run the testsuites in
1930 parallel by having the shell perform the combinations and @command{make}
1931 do the parallel runs. Instead of using @samp{--target_board}, use a
1932 special makefile target:
1935 make -j@var{N} check-@var{testsuite}//@var{test-target}/@var{option1}/@var{option2}/@dots{}
1941 make -j3 check-gcc//sh-hms-sim/@{-m1,-m2,-m3,-m3e,-m4@}/@{,-nofpu@}
1944 will run three concurrent ``make-gcc'' testsuites, eventually testing all
1945 ten combinations as described above. Note that this is currently only
1946 supported in the @file{gcc} subdirectory. (To see how this works, try
1947 typing @command{echo} before the example given here.)
1950 @section Additional testing for Java Class Libraries
1952 The Java runtime tests can be executed via @samp{make check}
1953 in the @file{@var{target}/libjava/testsuite} directory in
1956 The @uref{http://sources.redhat.com/mauve/,,Mauve Project} provides
1957 a suite of tests for the Java Class Libraries. This suite can be run
1958 as part of libgcj testing by placing the Mauve tree within the libjava
1959 testsuite at @file{libjava/testsuite/libjava.mauve/mauve}, or by
1960 specifying the location of that tree when invoking @samp{make}, as in
1961 @samp{make MAUVEDIR=~/mauve check}.
1963 @uref{http://sources.redhat.com/mauve/jacks.html,,Jacks}
1964 is a free testsuite that tests Java compiler front ends. This suite
1965 can be run as part of libgcj testing by placing the Jacks tree within
1966 the libjava testsuite at @file{libjava/testsuite/libjava.jacks/jacks}.
1968 @section How to interpret test results
1970 The result of running the testsuite are various @file{*.sum} and @file{*.log}
1971 files in the testsuite subdirectories. The @file{*.log} files contain a
1972 detailed log of the compiler invocations and the corresponding
1973 results, the @file{*.sum} files summarize the results. These summaries
1974 contain status codes for all tests:
1978 PASS: the test passed as expected
1980 XPASS: the test unexpectedly passed
1982 FAIL: the test unexpectedly failed
1984 XFAIL: the test failed as expected
1986 UNSUPPORTED: the test is not supported on this platform
1988 ERROR: the testsuite detected an error
1990 WARNING: the testsuite detected a possible problem
1993 It is normal for some tests to report unexpected failures. At the
1994 current time the testing harness does not allow fine grained control
1995 over whether or not a test is expected to fail. This problem should
1996 be fixed in future releases.
1999 @section Submitting test results
2001 If you want to report the results to the GCC project, use the
2002 @file{contrib/test_summary} shell script. Start it in the @var{objdir} with
2005 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
2006 -m gcc-testresults@@gcc.gnu.org |sh
2009 This script uses the @command{Mail} program to send the results, so
2010 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
2011 prepended to the testsuite summary and should contain any special
2012 remarks you have on your results or your build environment. Please
2013 do not edit the testsuite result block or the subject line, as these
2014 messages may be automatically processed.
2021 @uref{./index.html,,Return to the GCC Installation page}
2025 @c ***Final install***********************************************************
2027 @comment node-name, next, previous, up
2028 @node Final install, , Testing, Installing GCC
2030 @ifset finalinstallhtml
2032 @chapter Installing GCC: Final installation
2035 Now that GCC has been built (and optionally tested), you can install it with
2037 cd @var{objdir}; make install
2040 We strongly recommend to install into a target directory where there is
2041 no previous version of GCC present.
2043 That step completes the installation of GCC; user level binaries can
2044 be found in @file{@var{prefix}/bin} where @var{prefix} is the value
2045 you specified with the @option{--prefix} to configure (or
2046 @file{/usr/local} by default). (If you specified @option{--bindir},
2047 that directory will be used instead; otherwise, if you specified
2048 @option{--exec-prefix}, @file{@var{exec-prefix}/bin} will be used.)
2049 Headers for the C++ and Java libraries are installed in
2050 @file{@var{prefix}/include}; libraries in @file{@var{libdir}}
2051 (normally @file{@var{prefix}/lib}); internal parts of the compiler in
2052 @file{@var{libdir}/gcc} and @file{@var{libexecdir}/gcc}; documentation
2053 in info format in @file{@var{infodir}} (normally
2054 @file{@var{prefix}/info}).
2056 When installing cross-compilers, GCC's executables
2057 are not only installed into @file{@var{bindir}}, that
2058 is, @file{@var{exec-prefix}/bin}, but additionally into
2059 @file{@var{exec-prefix}/@var{target-alias}/bin}, if that directory
2060 exists. Typically, such @dfn{tooldirs} hold target-specific
2061 binutils, including assembler and linker.
2063 Installation into a temporary staging area or into a @command{chroot}
2064 jail can be achieved with the command
2067 make DESTDIR=@var{path-to-rootdir} install
2070 @noindent where @var{path-to-rootdir} is the absolute path of
2071 a directory relative to which all installation paths will be
2072 interpreted. Note that the directory specified by @code{DESTDIR}
2073 need not exist yet; it will be created if necessary.
2075 There is a subtle point with tooldirs and @code{DESTDIR}:
2076 If you relocate a cross-compiler installation with
2077 e.g.@: @samp{DESTDIR=@var{rootdir}}, then the directory
2078 @file{@var{rootdir}/@var{exec-prefix}/@var{target-alias}/bin} will
2079 be filled with duplicated GCC executables only if it already exists,
2080 it will not be created otherwise. This is regarded as a feature,
2081 not as a bug, because it gives slightly more control to the packagers
2082 using the @code{DESTDIR} feature.
2084 If you are bootstrapping a released version of GCC then please
2085 quickly review the build status page for your release, available from
2086 @uref{http://gcc.gnu.org/buildstat.html}.
2087 If your system is not listed for the version of GCC that you built,
2089 @email{gcc@@gcc.gnu.org} indicating
2090 that you successfully built and installed GCC@.
2091 Include the following information:
2095 Output from running @file{@var{srcdir}/config.guess}. Do not send
2096 that file itself, just the one-line output from running it.
2099 The output of @samp{gcc -v} for your newly installed @command{gcc}.
2100 This tells us which version of GCC you built and the options you passed to
2104 Whether you enabled all languages or a subset of them. If you used a
2105 full distribution then this information is part of the configure
2106 options in the output of @samp{gcc -v}, but if you downloaded the
2107 ``core'' compiler plus additional front ends then it isn't apparent
2108 which ones you built unless you tell us about it.
2111 If the build was for GNU/Linux, also include:
2114 The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
2115 this information should be available from @file{/etc/issue}.
2118 The version of the Linux kernel, available from @samp{uname --version}
2122 The version of glibc you used; for RPM-based systems like Red Hat,
2123 Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
2124 and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
2126 For other systems, you can include similar information if you think it is
2130 Any other information that you think would be useful to people building
2131 GCC on the same configuration. The new entry in the build status list
2132 will include a link to the archived copy of your message.
2135 We'd also like to know if the
2137 @ref{Specific, host/target specific installation notes}
2140 @uref{specific.html,,host/target specific installation notes}
2142 didn't include your host/target information or if that information is
2143 incomplete or out of date. Send a note to
2144 @email{gcc@@gcc.gnu.org} detailing how the information should be changed.
2146 If you find a bug, please report it following the
2147 @uref{../bugs.html,,bug reporting guidelines}.
2149 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
2150 dvi}. You will need to have @command{texi2dvi} (version at least 4.4)
2151 and @TeX{} installed. This creates a number of @file{.dvi} files in
2152 subdirectories of @file{@var{objdir}}; these may be converted for
2153 printing with programs such as @command{dvips}. You can also
2154 @uref{http://www.gnu.org/order/order.html,,buy printed manuals from the
2155 Free Software Foundation}, though such manuals may not be for the most
2156 recent version of GCC@.
2158 If you would like to generate online HTML documentation, do @samp{cd
2159 @var{objdir}; make html} and HTML will be generated for the gcc manuals in
2160 @file{@var{objdir}/gcc/HTML}.
2167 @uref{./index.html,,Return to the GCC Installation page}
2171 @c ***Binaries****************************************************************
2173 @comment node-name, next, previous, up
2174 @node Binaries, Specific, Installing GCC, Top
2178 @chapter Installing GCC: Binaries
2181 @cindex Installing GCC: Binaries
2183 We are often asked about pre-compiled versions of GCC@. While we cannot
2184 provide these for all platforms, below you'll find links to binaries for
2185 various platforms where creating them by yourself is not easy due to various
2188 Please note that we did not create these binaries, nor do we
2189 support them. If you have any problems installing them, please
2190 contact their makers.
2197 @uref{http://www.bullfreeware.com,,Bull's Freeware and Shareware Archive for AIX};
2200 @uref{http://aixpdslib.seas.ucla.edu,,UCLA Software Library for AIX}.
2204 DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}.
2207 Renesas H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
2208 Development Tools for the Renesas H8/300[HS] Series}.
2214 @uref{http://hpux.cs.utah.edu/,,HP-UX Porting Center};
2217 @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}.
2221 Motorola 68HC11/68HC12---@uref{http://www.gnu-m68hc11.org,,GNU
2222 Development Tools for the Motorola 68HC11/68HC12}.
2225 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
2226 OpenServer/Unixware}.
2229 Solaris 2 (SPARC, Intel)---@uref{http://www.sunfreeware.com/,,Sunfreeware}.
2232 SGI---@uref{http://freeware.sgi.com/,,SGI Freeware}.
2238 The @uref{http://sources.redhat.com/cygwin/,,Cygwin} project;
2240 The @uref{http://www.mingw.org/,,MinGW} project.
2244 @uref{ftp://ftp.thewrittenword.com/packages/by-name/,,The
2245 Written Word} offers binaries for
2248 Digital UNIX 4.0D and 5.1,
2250 HP-UX 10.20, 11.00, and 11.11, and
2251 Solaris/SPARC 2.5.1, 2.6, 7, 8, and 9.
2254 @uref{http://www.openpkg.org/,,OpenPKG} offers binaries for quite a
2255 number of platforms.
2258 The @uref{http://gcc.gnu.org/wiki/GFortranBinaries,,GFortran Wiki} has
2259 links to gfortran binaries for several platforms.
2262 In addition to those specific offerings, you can get a binary
2263 distribution CD-ROM from the
2264 @uref{http://www.gnu.org/order/order.html,,Free Software Foundation}.
2265 It contains binaries for a number of platforms, and
2266 includes not only GCC, but other stuff as well. The current CD does
2267 not contain the latest version of GCC, but it should allow
2268 bootstrapping the compiler. An updated version of that disk is in the
2276 @uref{./index.html,,Return to the GCC Installation page}
2280 @c ***Specific****************************************************************
2282 @comment node-name, next, previous, up
2283 @node Specific, Old, Binaries, Top
2287 @chapter Host/target specific installation notes for GCC
2290 @cindex Specific installation notes
2291 @cindex Target specific installation
2292 @cindex Host specific installation
2293 @cindex Target specific installation notes
2295 Please read this document carefully @emph{before} installing the
2296 GNU Compiler Collection on your machine.
2298 Note that this list of install notes is @emph{not} a list of supported
2299 hosts or targets. Not all supported hosts and targets are listed
2300 here, only the ones that require host-specific or target-specific
2306 @uref{#alpha-x-x,,alpha*-*-*}
2308 @uref{#alpha-dec-osf,,alpha*-dec-osf*}
2310 @uref{#alphaev5-cray-unicosmk,,alphaev5-cray-unicosmk*}
2312 @uref{#arc-x-elf,,arc-*-elf}
2314 @uref{#arm-x-elf,,arm-*-elf}
2315 @uref{#arm-x-coff,,arm-*-coff}
2316 @uref{#arm-x-aout,,arm-*-aout}
2318 @uref{#xscale-x-x,,xscale-*-*}
2322 @uref{#bfin,,Blackfin}
2328 @uref{#x-x-freebsd,,*-*-freebsd*}
2330 @uref{#h8300-hms,,h8300-hms}
2332 @uref{#hppa-hp-hpux,,hppa*-hp-hpux*}
2334 @uref{#hppa-hp-hpux10,,hppa*-hp-hpux10}
2336 @uref{#hppa-hp-hpux11,,hppa*-hp-hpux11}
2338 @uref{#x-x-linux-gnu,,*-*-linux-gnu}
2340 @uref{#ix86-x-linuxaout,,i?86-*-linux*aout}
2342 @uref{#ix86-x-linux,,i?86-*-linux*}
2344 @uref{#ix86-x-sco32v5,,i?86-*-sco3.2v5*}
2346 @uref{#ix86-x-solaris210,,i?86-*-solaris2.10}
2348 @uref{#ix86-x-udk,,i?86-*-udk}
2350 @uref{#ia64-x-linux,,ia64-*-linux}
2352 @uref{#ia64-x-hpux,,ia64-*-hpux*}
2354 @uref{#x-ibm-aix,,*-ibm-aix*}
2356 @uref{#iq2000-x-elf,,iq2000-*-elf}
2358 @uref{#m32c-x-elf,,m32c-*-elf}
2360 @uref{#m32r-x-elf,,m32r-*-elf}
2362 @uref{#m6811-elf,,m6811-elf}
2364 @uref{#m6812-elf,,m6812-elf}
2366 @uref{#m68k-hp-hpux,,m68k-hp-hpux}
2368 @uref{#mips-x-x,,mips-*-*}
2370 @uref{#mips-sgi-irix5,,mips-sgi-irix5}
2372 @uref{#mips-sgi-irix6,,mips-sgi-irix6}
2374 @uref{#powerpc-x-x,,powerpc*-*-*, powerpc-*-sysv4}
2376 @uref{#powerpc-x-darwin,,powerpc-*-darwin*}
2378 @uref{#powerpc-x-elf,,powerpc-*-elf, powerpc-*-sysv4}
2380 @uref{#powerpc-x-linux-gnu,,powerpc*-*-linux-gnu*}
2382 @uref{#powerpc-x-netbsd,,powerpc-*-netbsd*}
2384 @uref{#powerpc-x-eabisim,,powerpc-*-eabisim}
2386 @uref{#powerpc-x-eabi,,powerpc-*-eabi}
2388 @uref{#powerpcle-x-elf,,powerpcle-*-elf, powerpcle-*-sysv4}
2390 @uref{#powerpcle-x-eabisim,,powerpcle-*-eabisim}
2392 @uref{#powerpcle-x-eabi,,powerpcle-*-eabi}
2394 @uref{#s390-x-linux,,s390-*-linux*}
2396 @uref{#s390x-x-linux,,s390x-*-linux*}
2398 @uref{#s390x-ibm-tpf,,s390x-ibm-tpf*}
2400 @uref{#x-x-solaris2,,*-*-solaris2*}
2402 @uref{#sparc-sun-solaris2,,sparc-sun-solaris2*}
2404 @uref{#sparc-sun-solaris27,,sparc-sun-solaris2.7}
2406 @uref{#sparc-x-linux,,sparc-*-linux*}
2408 @uref{#sparc64-x-solaris2,,sparc64-*-solaris2*}
2410 @uref{#sparcv9-x-solaris2,,sparcv9-*-solaris2*}
2412 @uref{#x-x-sysv,,*-*-sysv*}
2414 @uref{#vax-dec-ultrix,,vax-dec-ultrix}
2416 @uref{#x-x-vxworks,,*-*-vxworks*}
2418 @uref{#x86-64-x-x,,x86_64-*-*, amd64-*-*}
2420 @uref{#xtensa-x-elf,,xtensa-*-elf}
2422 @uref{#xtensa-x-linux,,xtensa-*-linux*}
2424 @uref{#windows,,Microsoft Windows}
2428 @uref{#older,,Older systems}
2433 @uref{#elf,,all ELF targets} (SVR4, Solaris 2, etc.)
2439 <!-- -------- host/target specific issues start here ---------------- -->
2442 @heading @anchor{alpha-x-x}alpha*-*-*
2444 This section contains general configuration information for all
2445 alpha-based platforms using ELF (in particular, ignore this section for
2446 DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
2447 section, please read all other sections that match your target.
2449 We require binutils 2.11.2 or newer.
2450 Previous binutils releases had a number of problems with DWARF 2
2451 debugging information, not the least of which is incorrect linking of
2457 @heading @anchor{alpha-dec-osf}alpha*-dec-osf*
2458 Systems using processors that implement the DEC Alpha architecture and
2459 are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq
2460 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
2462 As of GCC 3.2, versions before @code{alpha*-dec-osf4} are no longer
2463 supported. (These are the versions which identify themselves as DEC
2466 In Digital Unix V4.0, virtual memory exhausted bootstrap failures
2467 may be fixed by configuring with @option{--with-gc=simple},
2468 reconfiguring Kernel Virtual Memory and Swap parameters
2469 per the @command{/usr/sbin/sys_check} Tuning Suggestions,
2470 or applying the patch in
2471 @uref{http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html}.
2473 In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
2474 currently (2001-06-13) work with @command{mips-tfile}. As a workaround,
2475 we need to use the old assembler, invoked via the barely documented
2476 @option{-oldas} option. To bootstrap GCC, you either need to use the
2480 % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}]
2483 or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
2486 % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}]
2489 As of GNU binutils 2.11.2, neither GNU @command{as} nor GNU @command{ld}
2490 are supported on Tru64 UNIX, so you must not configure GCC with
2491 @option{--with-gnu-as} or @option{--with-gnu-ld}.
2493 GCC writes a @samp{.verstamp} directive to the assembler output file
2494 unless it is built as a cross-compiler. It gets the version to use from
2495 the system header file @file{/usr/include/stamp.h}. If you install a
2496 new version of DEC Unix, you should rebuild GCC to pick up the new version
2499 Note that since the Alpha is a 64-bit architecture, cross-compilers from
2500 32-bit machines will not generate code as efficient as that generated
2501 when the compiler is running on a 64-bit machine because many
2502 optimizations that depend on being able to represent a word on the
2503 target in an integral value on the host cannot be performed. Building
2504 cross-compilers on the Alpha for 32-bit machines has only been tested in
2505 a few cases and may not work properly.
2507 @samp{make compare} may fail on old versions of DEC Unix unless you add
2508 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
2509 assembler input file is stored in the object file, and that makes
2510 comparison fail if it differs between the @code{stage1} and
2511 @code{stage2} compilations. The option @option{-save-temps} forces a
2512 fixed name to be used for the assembler input file, instead of a
2513 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
2514 unless the comparisons fail without that option. If you add
2515 @option{-save-temps}, you will have to manually delete the @samp{.i} and
2516 @samp{.s} files after each series of compilations.
2518 GCC now supports both the native (ECOFF) debugging format used by DBX
2519 and GDB and an encapsulated STABS format for use only with GDB@. See the
2520 discussion of the @option{--with-stabs} option of @file{configure} above
2521 for more information on these formats and how to select them.
2523 There is a bug in DEC's assembler that produces incorrect line numbers
2524 for ECOFF format when the @samp{.align} directive is used. To work
2525 around this problem, GCC will not emit such alignment directives
2526 while writing ECOFF format debugging information even if optimization is
2527 being performed. Unfortunately, this has the very undesirable
2528 side-effect that code addresses when @option{-O} is specified are
2529 different depending on whether or not @option{-g} is also specified.
2531 To avoid this behavior, specify @option{-gstabs+} and use GDB instead of
2532 DBX@. DEC is now aware of this problem with the assembler and hopes to
2533 provide a fix shortly.
2538 @heading @anchor{alphaev5-cray-unicosmk}alphaev5-cray-unicosmk*
2539 Cray T3E systems running Unicos/Mk.
2541 This port is incomplete and has many known bugs. We hope to improve the
2542 support for this target soon. Currently, only the C front end is supported,
2543 and it is not possible to build parallel applications. Cray modules are not
2544 supported; in particular, Craylibs are assumed to be in
2545 @file{/opt/ctl/craylibs/craylibs}.
2547 On this platform, you need to tell GCC where to find the assembler and
2548 the linker. The simplest way to do so is by providing @option{--with-as}
2549 and @option{--with-ld} to @file{configure}, e.g.@:
2552 configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld \
2553 --enable-languages=c
2556 The comparison test at the end of the bootstrapping process fails on Unicos/Mk
2557 because the assembler inserts timestamps into object files. You should
2558 be able to work around this by doing @samp{make all} after getting this
2564 @heading @anchor{arc-x-elf}arc-*-elf
2565 Argonaut ARC processor.
2566 This configuration is intended for embedded systems.
2571 @heading @anchor{arm-x-elf}arm-*-elf
2572 @heading @anchor{xscale-x-x}xscale-*-*
2573 ARM-family processors. Subtargets that use the ELF object format
2574 require GNU binutils 2.13 or newer. Such subtargets include:
2575 @code{arm-*-freebsd}, @code{arm-*-netbsdelf}, @code{arm-*-*linux},
2576 @code{arm-*-rtems} and @code{arm-*-kaos}.
2581 @heading @anchor{arm-x-coff}arm-*-coff
2582 ARM-family processors. Note that there are two different varieties
2583 of PE format subtarget supported: @code{arm-wince-pe} and
2584 @code{arm-pe} as well as a standard COFF target @code{arm-*-coff}.
2589 @heading @anchor{arm-x-aout}arm-*-aout
2590 ARM-family processors. These targets support the AOUT file format:
2591 @code{arm-*-aout}, @code{arm-*-netbsd}.
2596 @heading @anchor{avr}avr
2598 ATMEL AVR-family micro controllers. These are used in embedded
2599 applications. There are no standard Unix configurations.
2601 @xref{AVR Options,, AVR Options, gcc, Using the GNU Compiler
2605 See ``AVR Options'' in the main manual
2607 for the list of supported MCU types.
2609 Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
2611 Further installation notes and other useful information about AVR tools
2612 can also be obtained from:
2616 @uref{http://www.nongnu.org/avr/,,http://www.nongnu.org/avr/}
2618 @uref{http://home.overta.ru/users/denisc/,,http://home.overta.ru/users/denisc/}
2620 @uref{http://www.amelek.gda.pl/avr/,,http://www.amelek.gda.pl/avr/}
2623 We @emph{strongly} recommend using binutils 2.13 or newer.
2625 The following error:
2627 Error: register required
2630 indicates that you should upgrade to a newer version of the binutils.
2635 @heading @anchor{bfin}Blackfin
2637 The Blackfin processor, an Analog Devices DSP.
2639 @xref{Blackfin Options,, Blackfin Options, gcc, Using the GNU Compiler
2643 See ``Blackfin Options'' in the main manual
2646 More information, and a version of binutils with support for this processor,
2647 is available at @uref{http://blackfin.uclinux.org}
2652 @heading @anchor{c4x}c4x
2654 Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal
2655 Processors. These are used in embedded applications. There are no
2656 standard Unix configurations.
2658 @xref{TMS320C3x/C4x Options,, TMS320C3x/C4x Options, gcc, Using the
2659 GNU Compiler Collection (GCC)},
2662 See ``TMS320C3x/C4x Options'' in the main manual
2664 for the list of supported MCU types.
2666 GCC can be configured as a cross compiler for both the C3x and C4x
2667 architectures on the same system. Use @samp{configure --target=c4x
2668 --enable-languages="c,c++"} to configure.
2671 Further installation notes and other useful information about C4x tools
2672 can also be obtained from:
2676 @uref{http://www.elec.canterbury.ac.nz/c4x/,,http://www.elec.canterbury.ac.nz/c4x/}
2682 @heading @anchor{cris}CRIS
2684 CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
2685 series. These are used in embedded applications.
2688 @xref{CRIS Options,, CRIS Options, gcc, Using the GNU Compiler
2692 See ``CRIS Options'' in the main manual
2694 for a list of CRIS-specific options.
2696 There are a few different CRIS targets:
2698 @item cris-axis-aout
2699 Old target. Includes a multilib for the @samp{elinux} a.out-based
2700 target. No multilibs for newer architecture variants.
2702 Mainly for monolithic embedded systems. Includes a multilib for the
2703 @samp{v10} core used in @samp{ETRAX 100 LX}.
2704 @item cris-axis-linux-gnu
2705 A GNU/Linux port for the CRIS architecture, currently targeting
2706 @samp{ETRAX 100 LX} by default.
2709 For @code{cris-axis-aout} and @code{cris-axis-elf} you need binutils 2.11
2710 or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer.
2712 Pre-packaged tools can be obtained from
2713 @uref{ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/}. More
2714 information about this platform is available at
2715 @uref{http://developer.axis.com/}.
2720 @heading @anchor{crx}CRX
2722 The CRX CompactRISC architecture is a low-power 32-bit architecture with
2723 fast context switching and architectural extensibility features.
2726 @xref{CRX Options,, CRX Options, gcc, Using and Porting the GNU Compiler
2731 See ``CRX Options'' in the main manual for a list of CRX-specific options.
2734 Use @samp{configure --target=crx-elf --enable-languages=c,c++} to configure
2735 GCC@ for building a CRX cross-compiler. The option @samp{--target=crx-elf}
2736 is also used to build the @samp{newlib} C library for CRX.
2738 It is also possible to build libstdc++-v3 for the CRX architecture. This
2739 needs to be done in a separate step with the following configure settings:
2740 @samp{gcc/libstdc++-v3/configure --host=crx-elf --with-newlib
2741 --enable-sjlj-exceptions --enable-cxx-flags='-fexceptions -frtti'}
2746 @heading @anchor{dos}DOS
2748 Please have a look at the @uref{binaries.html,,binaries page}.
2750 You cannot install GCC by itself on MSDOS; it will not compile under
2751 any MSDOS compiler except itself. You need to get the complete
2752 compilation package DJGPP, which includes binaries as well as sources,
2753 and includes all the necessary compilation tools and libraries.
2758 @heading @anchor{x-x-freebsd}*-*-freebsd*
2760 The version of binutils installed in @file{/usr/bin} probably works with
2761 this release of GCC@. However, on FreeBSD 4, bootstrapping against the
2762 latest FSF binutils is known to improve overall testsuite results; and,
2763 on FreeBSD/alpha, using binutils 2.14 or later is required to build libjava.
2765 Support for FreeBSD 1 was discontinued in GCC 3.2.
2767 Support for FreeBSD 2 will be discontinued after GCC 3.4. The
2768 following was true for GCC 3.1 but the current status is unknown.
2769 For FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
2770 configuration support and files as shipped with GCC 2.95 are still in
2771 place. FreeBSD 2.2.7 has been known to bootstrap completely; however,
2772 it is unknown which version of binutils was used (it is assumed that it
2773 was the system copy in @file{/usr/bin}) and C++ EH failures were noted.
2775 For FreeBSD using the ELF file format: DWARF 2 debugging is now the
2776 default for all CPU architectures. It had been the default on
2777 FreeBSD/alpha since its inception. You may use @option{-gstabs} instead
2778 of @option{-g}, if you really want the old debugging format. There are
2779 no known issues with mixing object files and libraries with different
2780 debugging formats. Otherwise, this release of GCC should now match more
2781 of the configuration used in the stock FreeBSD configuration of GCC@. In
2782 particular, @option{--enable-threads} is now configured by default.
2783 However, as a general user, do not attempt to replace the system
2784 compiler with this release. Known to bootstrap and check with good
2785 results on FreeBSD 4.9-STABLE and 5-CURRENT@. In the past, known to
2786 bootstrap and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2,
2787 4.3, 4.4, 4.5, 4.8-STABLE@.
2789 In principle, @option{--enable-threads} is now compatible with
2790 @option{--enable-libgcj} on FreeBSD@. However, it has only been built
2791 and tested on @samp{i386-*-freebsd[45]} and @samp{alpha-*-freebsd[45]}.
2793 library may be incorrectly built (symbols are missing at link time).
2794 There is a rare timing-based startup hang (probably involves an
2795 assumption about the thread library). Multi-threaded boehm-gc (required for
2796 libjava) exposes severe threaded signal-handling bugs on FreeBSD before
2797 4.5-RELEASE@. Other CPU architectures
2798 supported by FreeBSD will require additional configuration tuning in, at
2799 the very least, both boehm-gc and libffi.
2801 Shared @file{libgcc_s.so} is now built and installed by default.
2806 @heading @anchor{h8300-hms}h8300-hms
2807 Renesas H8/300 series of processors.
2809 Please have a look at the @uref{binaries.html,,binaries page}.
2811 The calling convention and structure layout has changed in release 2.6.
2812 All code must be recompiled. The calling convention now passes the
2813 first three arguments in function calls in registers. Structures are no
2814 longer a multiple of 2 bytes.
2819 @heading @anchor{hppa-hp-hpux}hppa*-hp-hpux*
2820 Support for HP-UX version 9 and older was discontinued in GCC 3.4.
2822 We require using gas/binutils on all hppa platforms;
2823 you may encounter a variety of problems if you try to use the HP assembler.
2825 Specifically, @option{-g} does not work on HP-UX (since that system
2826 uses a peculiar debugging format which GCC does not know about), unless
2827 you use GAS and GDB@. It may be helpful to configure GCC with the
2828 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
2829 @option{--with-as=@dots{}} options to ensure that GCC can find GAS@.
2831 If you wish to use the pa-risc 2.0 architecture support with a 32-bit
2832 runtime, you must use gas/binutils 2.11 or newer.
2834 There are two default scheduling models for instructions. These are
2835 PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
2836 architecture specified for the target machine when configuring.
2837 PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
2838 the target is a @samp{hppa1*} machine.
2840 The PROCESSOR_8000 model is not well suited to older processors. Thus,
2841 it is important to completely specify the machine architecture when
2842 configuring if you want a model other than PROCESSOR_8000. The macro
2843 TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
2844 default scheduling model is desired.
2846 As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10
2847 through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later.
2848 This namespace change might cause problems when bootstrapping with
2849 an earlier version of GCC or the HP compiler as essentially the same
2850 namespace is required for an entire build. This problem can be avoided
2851 in a number of ways. With HP cc, @env{UNIX_STD} can be set to @samp{95}
2852 or @samp{98}. Another way is to add an appropriate set of predefines
2853 to @env{CC}. The description for the @option{munix=} option contains
2854 a list of the predefines used with each standard.
2856 As of GCC 4.1, @env{DWARF2} exception handling is available on HP-UX.
2857 It is now the default. This exposed a bug in the handling of data
2858 relocations in the GAS assembler. The handling of 64-bit data relocations
2859 was seriously broken, affecting debugging and exception support on all
2860 @samp{hppa64-*-*} targets. Under some circumstances, 32-bit data relocations
2861 could also be handled incorrectly. This problem is fixed in GAS version
2864 GCC versions prior to 4.1 incorrectly passed and returned complex
2865 values. They are now passed in the same manner as aggregates.
2867 More specific information to @samp{hppa*-hp-hpux*} targets follows.
2872 @heading @anchor{hppa-hp-hpux10}hppa*-hp-hpux10
2874 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
2875 @code{PHCO_19798} from HP@. HP has two sites which provide patches free of
2881 <a href="http://us.itrc.hp.com/service/home/home.do">US, Canada, Asia-Pacific, and
2885 @uref{http://us.itrc.hp.com/service/home/home.do,,} US, Canada, Asia-Pacific,
2889 @uref{http://europe.itrc.hp.com/service/home/home.do,,} Europe.
2892 The HP assembler on these systems has some problems. Most notably the
2893 assembler inserts timestamps into each object file it creates, causing
2894 the 3-stage comparison test to fail during a bootstrap.
2895 You should be able to continue by saying @samp{make all-host all-target}
2896 after getting the failure from @samp{make}.
2898 GCC 4.0 requires CVS binutils as of April 28, 2004 or later. Earlier
2899 versions require binutils 2.8 or later.
2901 The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces are
2902 used for one-only code and data. This resolves many of the previous
2903 problems in using C++ on this target. However, the ABI is not compatible
2904 with the one implemented under HP-UX 11 using secondary definitions.
2909 @heading @anchor{hppa-hp-hpux11}hppa*-hp-hpux11
2911 GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot
2912 be used to compile GCC 3.0 and up.
2914 Refer to @uref{binaries.html,,binaries} for information about obtaining
2915 precompiled GCC binaries for HP-UX@. Precompiled binaries must be obtained
2916 to build the Ada language as it can't be bootstrapped using C@. Ada is
2917 only available for the 32-bit PA-RISC runtime. The libffi and libjava
2918 haven't been ported to HP-UX and don't build.
2920 It is possible to build GCC 3.3 starting with the bundled HP compiler,
2921 but the process requires several steps. GCC 3.3 can then be used to
2922 build later versions. The fastjar program contains ISO C code and
2923 can't be built with the HP bundled compiler. This problem can be
2924 avoided by not building the Java language. For example, use the
2925 @option{--enable-languages="c,c++,f77,objc"} option in your configure
2928 Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The
2929 bundled compiler supports only traditional C; you will need either HP's
2930 unbundled compiler, or a binary distribution of GCC@.
2932 There are several possible approaches to building the distribution.
2933 Binutils can be built first using the HP tools. Then, the GCC
2934 distribution can be built. The second approach is to build GCC
2935 first using the HP tools, then build binutils, then rebuild GCC@.
2936 There have been problems with various binary distributions, so it
2937 is best not to start from a binary distribution.
2939 On 64-bit capable systems, there are two distinct targets. Different
2940 installation prefixes must be used if both are to be installed on
2941 the same system. The @samp{hppa[1-2]*-hp-hpux11*} target generates code
2942 for the 32-bit PA-RISC runtime architecture and uses the HP linker.
2943 The @samp{hppa64-hp-hpux11*} target generates 64-bit code for the
2944 PA-RISC 2.0 architecture. The HP and GNU linkers are both supported
2947 The script config.guess now selects the target type based on the compiler
2948 detected during configuration. You must define @env{PATH} or @env{CC} so
2949 that configure finds an appropriate compiler for the initial bootstrap.
2950 When @env{CC} is used, the definition should contain the options that are
2951 needed whenever @env{CC} is used.
2953 Specifically, options that determine the runtime architecture must be
2954 in @env{CC} to correctly select the target for the build. It is also
2955 convenient to place many other compiler options in @env{CC}. For example,
2956 @env{CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"}
2957 can be used to bootstrap the GCC 3.3 branch with the HP compiler in
2958 64-bit K&R/bundled mode. The @option{+DA2.0W} option will result in
2959 the automatic selection of the @samp{hppa64-hp-hpux11*} target. The
2960 macro definition table of cpp needs to be increased for a successful
2961 build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to
2962 be defined when building with the bundled compiler, or when using the
2963 @option{-Ac} option. These defines aren't necessary with @option{-Ae}.
2965 It is best to explicitly configure the @samp{hppa64-hp-hpux11*} target
2966 with the @option{--with-ld=@dots{}} option. This overrides the standard
2967 search for ld. The two linkers supported on this target require different
2968 commands. The default linker is determined during configuration. As a
2969 result, it's not possible to switch linkers in the middle of a GCC build.
2970 This has been been reported to sometimes occur in unified builds of
2973 GCC 3.0 through 3.2 require binutils 2.11 or above. GCC 3.3 through
2974 GCC 4.0 require binutils 2.14 or later.
2976 Although the HP assembler can be used for an initial build, it shouldn't
2977 be used with any languages other than C and perhaps Fortran due to its
2978 many limitations. For example, it does not support weak symbols or alias
2979 definitions. As a result, explicit template instantiations are required
2980 when using C++. This makes it difficult if not impossible to build many
2981 C++ applications. You can't generate debugging information when using
2982 the HP assembler. Finally, bootstrapping fails in the final
2983 comparison of object modules due to the time stamps that it inserts into
2984 the modules. The bootstrap can be continued from this point with
2985 @samp{make all-host all-target}.
2987 A recent linker patch must be installed for the correct operation of
2988 GCC 3.3 and later. @code{PHSS_26559} and @code{PHSS_24304} are the
2989 oldest linker patches that are known to work. They are for HP-UX
2990 11.00 and 11.11, respectively. @code{PHSS_24303}, the companion to
2991 @code{PHSS_24304}, might be usable but it hasn't been tested. These
2992 patches have been superseded. Consult the HP patch database to obtain
2993 the currently recommended linker patch for your system.
2995 The patches are necessary for the support of weak symbols on the
2996 32-bit port, and for the running of initializers and finalizers. Weak
2997 symbols are implemented using SOM secondary definition symbols. Prior
2998 to HP-UX 11, there are bugs in the linker support for secondary symbols.
2999 The patches correct a problem of linker core dumps creating shared
3000 libraries containing secondary symbols, as well as various other
3001 linking issues involving secondary symbols.
3003 GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
3004 run initializers and finalizers on the 64-bit port. The 32-bit port
3005 uses the linker @option{+init} and @option{+fini} options for the same
3006 purpose. The patches correct various problems with the +init/+fini
3007 options, including program core dumps. Binutils 2.14 corrects a
3008 problem on the 64-bit port resulting from HP's non-standard use of
3009 the .init and .fini sections for array initializers and finalizers.
3011 There are a number of issues to consider in selecting which linker to
3012 use with the 64-bit port. The GNU 64-bit linker can only create dynamic
3013 binaries. The @option{-static} option causes linking with archive
3014 libraries but doesn't produce a truly static binary. Dynamic binaries
3015 still require final binding by the dynamic loader to resolve a set of
3016 dynamic-loader-defined symbols. The default behavior of the HP linker
3017 is the same as the GNU linker. However, it can generate true 64-bit
3018 static binaries using the @option{+compat} option.
3020 The HP 64-bit linker doesn't support linkonce semantics. As a
3021 result, C++ programs have many more sections than they should.
3023 The GNU 64-bit linker has some issues with shared library support
3024 and exceptions. As a result, we only support libgcc in archive
3025 format. For similar reasons, dwarf2 unwind and exception support
3026 are disabled. The GNU linker also has problems creating binaries
3027 with @option{-static}. It doesn't provide stubs for internal
3028 calls to global functions in shared libraries, so these calls
3029 can't be overloaded.
3031 Thread support is not implemented in GCC 3.0 through 3.2, so the
3032 @option{--enable-threads} configure option does not work. In 3.3
3033 and later, POSIX threads are supported. The optional DCE thread
3034 library is not supported.
3036 This port still is undergoing significant development.
3041 @heading @anchor{x-x-linux-gnu}*-*-linux-gnu
3043 Versions of libstdc++-v3 starting with 3.2.1 require bugfixes present
3044 in glibc 2.2.5 and later. More information is available in the
3045 libstdc++-v3 documentation.
3050 @heading @anchor{ix86-x-linuxaout}i?86-*-linux*aout
3051 Use this configuration to generate @file{a.out} binaries on Linux-based
3052 GNU systems. This configuration is being superseded.
3057 @heading @anchor{ix86-x-linux}i?86-*-linux*
3059 As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
3060 See @uref{http://gcc.gnu.org/PR10877,,bug 10877} for more information.
3062 If you receive Signal 11 errors when building on GNU/Linux, then it is
3063 possible you have a hardware problem. Further information on this can be
3064 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
3069 @heading @anchor{ix86-x-sco32v5}i?86-*-sco3.2v5*
3070 Use this for the SCO OpenServer Release 5 family of operating systems.
3072 Unlike earlier versions of GCC, the ability to generate COFF with this
3073 target is no longer provided.
3075 Earlier versions of GCC emitted DWARF 1 when generating ELF to allow
3076 the system debugger to be used. That support was too burdensome to
3077 maintain. GCC now emits only DWARF 2 for this target. This means you
3078 may use either the UDK debugger or GDB to debug programs built by this
3081 GCC is now only supported on releases 5.0.4 and later, and requires that
3082 you install Support Level Supplement OSS646B or later, and Support Level
3083 Supplement OSS631C or later. If you are using release 5.0.7 of
3084 OpenServer, you must have at least the first maintenance pack installed
3085 (this includes the relevant portions of OSS646). OSS646, also known as
3086 the ``Execution Environment Update'', provides updated link editors and
3087 assemblers, as well as updated standard C and math libraries. The C
3088 startup modules are also updated to support the System V gABI draft, and
3089 GCC relies on that behavior. OSS631 provides a collection of commonly
3090 used open source libraries, some of which GCC depends on (such as GNU
3091 gettext and zlib). SCO OpenServer Release 5.0.7 has all of this built
3092 in by default, but OSS631C and later also apply to that release. Please
3094 @uref{ftp://ftp.sco.com/pub/openserver5,,ftp://ftp.sco.com/pub/openserver5}
3095 for the latest versions of these (and other potentially useful)
3098 Although there is support for using the native assembler, it is
3099 recommended that you configure GCC to use the GNU assembler. You do
3100 this by using the flags
3101 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}}. You should
3102 use a modern version of GNU binutils. Version 2.13.2.1 was used for all
3103 testing. In general, only the @option{--with-gnu-as} option is tested.
3104 A modern bintuils (as well as a plethora of other development related
3105 GNU utilities) can be found in Support Level Supplement OSS658A, the
3106 ``GNU Development Tools'' package. See the SCO web and ftp sites for details.
3107 That package also contains the currently ``officially supported'' version of
3108 GCC, version 2.95.3. It is useful for bootstrapping this version.
3113 @heading @anchor{ix86-x-solaris210}i?86-*-solaris2.10
3114 Use this for Solaris 10 or later on x86 and x86-64 systems. This
3115 configuration is supported by GCC 4.0 and later versions only.
3117 It is recommended that you configure GCC to use the GNU assembler in
3118 @file{/usr/sfw/bin/gas} but the Sun linker, using the options
3119 @option{--with-gnu-as --with-as=/usr/sfw/bin/gas --without-gnu-ld
3120 --with-ld=/usr/ccs/bin/ld}.
3125 @heading @anchor{ix86-x-udk}i?86-*-udk
3127 This target emulates the SCO Universal Development Kit and requires that
3128 package be installed. (If it is installed, you will have a
3129 @file{/udk/usr/ccs/bin/cc} file present.) It's very much like the
3130 @samp{i?86-*-unixware7*} target
3131 but is meant to be used when hosting on a system where UDK isn't the
3132 default compiler such as OpenServer 5 or Unixware 2. This target will
3133 generate binaries that will run on OpenServer, Unixware 2, or Unixware 7,
3134 with the same warnings and caveats as the SCO UDK@.
3136 This target is a little tricky to build because we have to distinguish
3137 it from the native tools (so it gets headers, startups, and libraries
3138 from the right place) while making the tools not think we're actually
3139 building a cross compiler. The easiest way to do this is with a configure
3143 CC=/udk/usr/ccs/bin/cc @var{/your/path/to}/gcc/configure \
3144 --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-
3147 @emph{You should substitute @samp{i686} in the above command with the appropriate
3148 processor for your host.}
3150 After the usual @samp{make} and
3151 @samp{make install}, you can then access the UDK-targeted GCC
3152 tools by adding @command{udk-} before the commonly known name. For
3153 example, to invoke the C compiler, you would use @command{udk-gcc}.
3154 They will coexist peacefully with any native-target GCC tools you may
3161 @heading @anchor{ia64-x-linux}ia64-*-linux
3162 IA-64 processor (also known as IPF, or Itanium Processor Family)
3165 If you are using the installed system libunwind library with
3166 @option{--with-system-libunwind}, then you must use libunwind 0.98 or
3169 None of the following versions of GCC has an ABI that is compatible
3170 with any of the other versions in this list, with the exception that
3171 Red Hat 2.96 and Trillian 000171 are compatible with each other:
3172 3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
3173 This primarily affects C++ programs and programs that create shared libraries.
3174 GCC 3.1 or later is recommended for compiling linux, the kernel.
3175 As of version 3.1 GCC is believed to be fully ABI compliant, and hence no
3176 more major ABI changes are expected.
3181 @heading @anchor{ia64-x-hpux}ia64-*-hpux*
3182 Building GCC on this target requires the GNU Assembler. The bundled HP
3183 assembler will not work. To prevent GCC from using the wrong assembler,
3184 the option @option{--with-gnu-as} may be necessary.
3186 The GCC libunwind library has not been ported to HPUX@. This means that for
3187 GCC versions 3.2.3 and earlier, @option{--enable-libunwind-exceptions}
3188 is required to build GCC@. For GCC 3.3 and later, this is the default.
3189 For gcc 3.4.3 and later, @option{--enable-libunwind-exceptions} is
3190 removed and the system libunwind library will always be used.
3194 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
3196 @heading @anchor{x-ibm-aix}*-ibm-aix*
3197 Support for AIX version 3 and older was discontinued in GCC 3.4.
3199 ``out of memory'' bootstrap failures may indicate a problem with
3200 process resource limits (ulimit). Hard limits are configured in the
3201 @file{/etc/security/limits} system configuration file.
3203 To speed up the configuration phases of bootstrapping and installing GCC,
3204 one may use GNU Bash instead of AIX @command{/bin/sh}, e.g.,
3207 % CONFIG_SHELL=/opt/freeware/bin/bash
3208 % export CONFIG_SHELL
3211 and then proceed as described in @uref{build.html,,the build
3212 instructions}, where we strongly recommend specifying an absolute path
3213 to invoke @var{srcdir}/configure.
3215 Errors involving @code{alloca} when building GCC generally are due
3216 to an incorrect definition of @code{CC} in the Makefile or mixing files
3217 compiled with the native C compiler and GCC@. During the stage1 phase of
3218 the build, the native AIX compiler @strong{must} be invoked as @command{cc}
3219 (not @command{xlc}). Once @command{configure} has been informed of
3220 @command{xlc}, one needs to use @samp{make distclean} to remove the
3221 configure cache files and ensure that @env{CC} environment variable
3222 does not provide a definition that will confuse @command{configure}.
3223 If this error occurs during stage2 or later, then the problem most likely
3224 is the version of Make (see above).
3226 The native @command{as} and @command{ld} are recommended for bootstrapping
3227 on AIX 4 and required for bootstrapping on AIX 5L@. The GNU Assembler
3228 reports that it supports WEAK symbols on AIX 4, which causes GCC to try to
3229 utilize weak symbol functionality although it is not supported. The GNU
3230 Assembler and Linker do not support AIX 5L sufficiently to bootstrap GCC@.
3231 The native AIX tools do interoperate with GCC@.
3233 Building @file{libstdc++.a} requires a fix for an AIX Assembler bug
3234 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a
3235 fix for another AIX Assembler bug and a co-dependent AIX Archiver fix
3236 referenced as APAR IY53606 (AIX 5.2) or a APAR IY54774 (AIX 5.1)
3238 @samp{libstdc++} in GCC 3.4 increments the major version number of the
3239 shared object and GCC installation places the @file{libstdc++.a}
3240 shared library in a common location which will overwrite the and GCC
3241 3.3 version of the shared library. Applications either need to be
3242 re-linked against the new shared library or the GCC 3.1 and GCC 3.3
3243 versions of the @samp{libstdc++} shared object needs to be available
3244 to the AIX runtime loader. The GCC 3.1 @samp{libstdc++.so.4}, if
3245 present, and GCC 3.3 @samp{libstdc++.so.5} shared objects can be
3246 installed for runtime dynamic loading using the following steps to set
3247 the @samp{F_LOADONLY} flag in the shared object for @emph{each}
3248 multilib @file{libstdc++.a} installed:
3250 Extract the shared objects from the currently installed
3251 @file{libstdc++.a} archive:
3253 % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
3256 Enable the @samp{F_LOADONLY} flag so that the shared object will be
3257 available for runtime dynamic loading, but not linking:
3259 % strip -e libstdc++.so.4 libstdc++.so.5
3262 Archive the runtime-only shared object in the GCC 3.4
3263 @file{libstdc++.a} archive:
3265 % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
3268 Linking executables and shared libraries may produce warnings of
3269 duplicate symbols. The assembly files generated by GCC for AIX always
3270 have included multiple symbol definitions for certain global variable
3271 and function declarations in the original program. The warnings should
3272 not prevent the linker from producing a correct library or runnable
3275 AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
3276 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
3277 to parse archive libraries did not handle the new format correctly.
3278 These routines are used by GCC and result in error messages during
3279 linking such as ``not a COFF file''. The version of the routines shipped
3280 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
3281 option of the archive command may be used to create archives of 32-bit
3282 objects using the original ``small format''. A correct version of the
3283 routines is shipped with AIX 4.3.2 and above.
3285 Some versions of the AIX binder (linker) can fail with a relocation
3286 overflow severe error when the @option{-bbigtoc} option is used to link
3287 GCC-produced object files into an executable that overflows the TOC@. A fix
3288 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
3289 available from IBM Customer Support and from its
3290 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3291 website as PTF U455193.
3293 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
3294 with a segmentation fault when invoked by any version of GCC@. A fix for
3295 APAR IX87327 is available from IBM Customer Support and from its
3296 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3297 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
3299 The initial assembler shipped with AIX 4.3.0 generates incorrect object
3300 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
3301 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
3302 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3303 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
3305 AIX provides National Language Support (NLS)@. Compilers and assemblers
3306 use NLS to support locale-specific representations of various data
3307 formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
3308 separating decimal fractions). There have been problems reported where
3309 GCC does not produce the same floating-point formats that the assembler
3310 expects. If one encounters this problem, set the @env{LANG}
3311 environment variable to @samp{C} or @samp{En_US}.
3313 By default, GCC for AIX 4.1 and above produces code that can be used on
3314 both Power or PowerPC processors.
3316 A default can be specified with the @option{-mcpu=@var{cpu_type}}
3317 switch and using the configure option @option{--with-cpu-@var{cpu_type}}.
3322 @heading @anchor{iq2000-x-elf}iq2000-*-elf
3323 Vitesse IQ2000 processors. These are used in embedded
3324 applications. There are no standard Unix configurations.
3329 @heading @anchor{m32c-x-elf}m32c-*-elf
3330 Renesas M32C processor.
3331 This configuration is intended for embedded systems.
3336 @heading @anchor{m32r-x-elf}m32r-*-elf
3337 Renesas M32R processor.
3338 This configuration is intended for embedded systems.
3343 @heading @anchor{m6811-elf}m6811-elf
3344 Motorola 68HC11 family micro controllers. These are used in embedded
3345 applications. There are no standard Unix configurations.
3350 @heading @anchor{m6812-elf}m6812-elf
3351 Motorola 68HC12 family micro controllers. These are used in embedded
3352 applications. There are no standard Unix configurations.
3357 @heading @anchor{m68k-hp-hpux}m68k-hp-hpux
3358 HP 9000 series 300 or 400 running HP-UX@. HP-UX version 8.0 has a bug in
3359 the assembler that prevents compilation of GCC@. This
3360 bug manifests itself during the first stage of compilation, while
3361 building @file{libgcc2.a}:
3365 cc1: warning: `-g' option not supported on this version of GCC
3366 cc1: warning: `-g1' option not supported on this version of GCC
3367 ./xgcc: Internal compiler error: program as got fatal signal 11
3370 A patched version of the assembler is available as the file
3371 @uref{ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler}. If you
3372 have HP software support, the patch can also be obtained directly from
3373 HP, as described in the following note:
3376 This is the patched assembler, to patch SR#1653-010439, where the
3377 assembler aborts on floating point constants.
3379 The bug is not really in the assembler, but in the shared library
3380 version of the function ``cvtnum(3c)''. The bug on ``cvtnum(3c)'' is
3381 SR#4701-078451. Anyway, the attached assembler uses the archive
3382 library version of ``cvtnum(3c)'' and thus does not exhibit the bug.
3385 This patch is also known as PHCO_4484.
3387 In addition gdb does not understand that native HP-UX format, so
3388 you must use gas if you wish to use gdb.
3390 On HP-UX version 8.05, but not on 8.07 or more recent versions, the
3391 @command{fixproto} shell script triggers a bug in the system shell. If you
3392 encounter this problem, upgrade your operating system or use BASH (the
3393 GNU shell) to run @command{fixproto}. This bug will cause the fixproto
3394 program to report an error of the form:
3397 ./fixproto: sh internal 1K buffer overflow
3400 To fix this, you can also change the first line of the fixproto script
3410 @heading @anchor{mips-x-x}mips-*-*
3411 If on a MIPS system you get an error message saying ``does not have gp
3412 sections for all it's [sic] sectons [sic]'', don't worry about it. This
3413 happens whenever you use GAS with the MIPS linker, but there is not
3414 really anything wrong, and it is okay to use the output file. You can
3415 stop such warnings by installing the GNU linker.
3417 It would be nice to extend GAS to produce the gp tables, but they are
3418 optional, and there should not be a warning about their absence.
3420 The libstdc++ atomic locking routines for MIPS targets requires MIPS II
3421 and later. A patch went in just after the GCC 3.3 release to
3422 make @samp{mips*-*-*} use the generic implementation instead. You can also
3423 configure for @samp{mipsel-elf} as a workaround. The
3424 @samp{mips*-*-linux*} target continues to use the MIPS II routines. More
3425 work on this is expected in future releases.
3427 MIPS systems check for division by zero (unless
3428 @option{-mno-check-zero-division} is passed to the compiler) by
3429 generating either a conditional trap or a break instruction. Using
3430 trap results in smaller code, but is only supported on MIPS II and
3431 later. Also, some versions of the Linux kernel have a bug that
3432 prevents trap from generating the proper signal (@code{SIGFPE}). To enable
3433 the use of break, use the @option{--with-divide=breaks}
3434 @command{configure} option when configuring GCC@. The default is to
3435 use traps on systems that support them.
3437 Cross-compilers for the MIPS as target using the MIPS assembler
3438 currently do not work, because the auxiliary programs
3439 @file{mips-tdump.c} and @file{mips-tfile.c} can't be compiled on
3440 anything but a MIPS. It does work to cross compile for a MIPS
3441 if you use the GNU assembler and linker.
3446 @heading @anchor{mips-sgi-irix5}mips-sgi-irix5
3448 In order to compile GCC on an SGI running IRIX 5, the @samp{compiler_dev.hdr}
3449 subsystem must be installed from the IDO CD-ROM supplied by SGI@.
3450 It is also available for download from
3451 @uref{ftp://ftp.sgi.com/sgi/IRIX5.3/iris-development-option-5.3.tardist}.
3453 If you use the MIPS C compiler to bootstrap, it may be necessary
3454 to increase its table size for switch statements with the
3455 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
3456 optimization option, you also need to use @option{-Olimit 3000}.
3458 To enable debugging under IRIX 5, you must use GNU binutils 2.15 or
3459 later, and use the @option{--with-gnu-ld} @command{configure} option
3460 when configuring GCC@. You need to use GNU @command{ar} and @command{nm},
3461 also distributed with GNU binutils.
3463 Some users have reported that @command{/bin/sh} will hang during bootstrap.
3464 This problem can be avoided by running the commands:
3467 % CONFIG_SHELL=/bin/ksh
3468 % export CONFIG_SHELL
3471 before starting the build.
3476 @heading @anchor{mips-sgi-irix6}mips-sgi-irix6
3478 If you are using SGI's MIPSpro @command{cc} as your bootstrap compiler, you must
3479 ensure that the N32 ABI is in use. To test this, compile a simple C
3480 file with @command{cc} and then run @command{file} on the
3481 resulting object file. The output should look like:
3484 test.o: ELF N32 MSB @dots{}
3490 test.o: ELF 32-bit MSB @dots{}
3496 test.o: ELF 64-bit MSB @dots{}
3499 then your version of @command{cc} uses the O32 or N64 ABI by default. You
3500 should set the environment variable @env{CC} to @samp{cc -n32}
3501 before configuring GCC@.
3503 If you want the resulting @command{gcc} to run on old 32-bit systems
3504 with the MIPS R4400 CPU, you need to ensure that only code for the @samp{mips3}
3505 instruction set architecture (ISA) is generated. While GCC 3.x does
3506 this correctly, both GCC 2.95 and SGI's MIPSpro @command{cc} may change
3507 the ISA depending on the machine where GCC is built. Using one of them
3508 as the bootstrap compiler may result in @samp{mips4} code, which won't run at
3509 all on @samp{mips3}-only systems. For the test program above, you should see:
3512 test.o: ELF N32 MSB mips-3 @dots{}
3518 test.o: ELF N32 MSB mips-4 @dots{}
3521 instead, you should set the environment variable @env{CC} to @samp{cc
3522 -n32 -mips3} or @samp{gcc -mips3} respectively before configuring GCC@.
3524 MIPSpro C 7.4 may cause bootstrap failures, due to a bug when inlining
3525 @code{memcmp}. Either add @code{-U__INLINE_INTRINSICS} to the @env{CC}
3526 environment variable as a workaround or upgrade to MIPSpro C 7.4.1m.
3528 GCC on IRIX 6 is usually built to support the N32, O32 and N64 ABIs. If
3529 you build GCC on a system that doesn't have the N64 libraries installed
3530 or cannot run 64-bit binaries,
3531 you need to configure with @option{--disable-multilib} so GCC doesn't
3532 try to use them. This will disable building the O32 libraries, too.
3533 Look for @file{/usr/lib64/libc.so.1} to see if you
3534 have the 64-bit libraries installed.
3536 To enable debugging for the O32 ABI, you must use GNU @command{as} from
3537 GNU binutils 2.15 or later. You may also use GNU @command{ld}, but
3538 this is not required and currently causes some problems with Ada.
3540 The @option{--enable-threads} option doesn't currently work, a patch is
3541 in preparation for a future release. The @option{--enable-libgcj}
3542 option is disabled by default: IRIX 6 uses a very low default limit
3543 (20480) for the command line length. Although @command{libtool} contains a
3544 workaround for this problem, at least the N64 @samp{libgcj} is known not
3545 to build despite this, running into an internal error of the native
3546 @command{ld}. A sure fix is to increase this limit (@samp{ncargs}) to
3547 its maximum of 262144 bytes. If you have root access, you can use the
3548 @command{systune} command to do this.
3550 See @uref{http://freeware.sgi.com/} for more
3551 information about using GCC on IRIX platforms.
3556 @heading @anchor{powerpc-x-x}powerpc-*-*
3558 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
3559 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
3564 @heading @anchor{powerpc-x-darwin}powerpc-*-darwin*
3565 PowerPC running Darwin (Mac OS X kernel).
3567 Pre-installed versions of Mac OS X may not include any developer tools,
3568 meaning that you will not be able to build GCC from source. Tool
3569 binaries are available at
3570 @uref{http://developer.apple.com/darwin/projects/compiler/} (free
3571 registration required).
3573 This version of GCC requires at least cctools-590.7.
3575 The version of GCC shipped by Apple typically includes a number of
3576 extensions not available in a standard GCC release. These extensions
3577 are generally for backwards compatibility and best avoided.
3582 @heading @anchor{powerpc-x-elf}powerpc-*-elf, powerpc-*-sysv4
3583 PowerPC system in big endian mode, running System V.4.
3588 @heading @anchor{powerpc-x-linux-gnu}powerpc*-*-linux-gnu*
3591 @uref{ftp://ftp.kernel.org/pub/linux/devel/binutils,,binutils 2.15}
3592 or newer for a working GCC@.
3597 @heading @anchor{powerpc-x-netbsd}powerpc-*-netbsd*
3598 PowerPC system in big endian mode running NetBSD@. To build the
3599 documentation you will need Texinfo version 4.4 (NetBSD 1.5.1 included
3600 Texinfo version 3.12).
3605 @heading @anchor{powerpc-x-eabisim}powerpc-*-eabisim
3606 Embedded PowerPC system in big endian mode for use in running under the
3612 @heading @anchor{powerpc-x-eabi}powerpc-*-eabi
3613 Embedded PowerPC system in big endian mode.
3618 @heading @anchor{powerpcle-x-elf}powerpcle-*-elf, powerpcle-*-sysv4
3619 PowerPC system in little endian mode, running System V.4.
3624 @heading @anchor{powerpcle-x-eabisim}powerpcle-*-eabisim
3625 Embedded PowerPC system in little endian mode for use in running under
3631 @heading @anchor{powerpcle-x-eabi}powerpcle-*-eabi
3632 Embedded PowerPC system in little endian mode.
3637 @heading @anchor{s390-x-linux}s390-*-linux*
3638 S/390 system running GNU/Linux for S/390@.
3643 @heading @anchor{s390x-x-linux}s390x-*-linux*
3644 zSeries system (64-bit) running GNU/Linux for zSeries@.
3649 @heading @anchor{s390x-ibm-tpf}s390x-ibm-tpf*
3650 zSeries system (64-bit) running TPF@. This platform is
3651 supported as cross-compilation target only.
3656 @c Please use Solaris 2 to refer to all release of Solaris, starting
3657 @c with 2.0 until 2.6, 7, 8, etc. Solaris 1 was a marketing name for
3658 @c SunOS 4 releases which we don't use to avoid confusion. Solaris
3659 @c alone is too unspecific and must be avoided.
3660 @heading @anchor{x-x-solaris2}*-*-solaris2*
3662 Sun does not ship a C compiler with Solaris 2. To bootstrap and install
3663 GCC you first have to install a pre-built compiler, see the
3664 @uref{binaries.html,,binaries page} for details.
3666 The Solaris 2 @command{/bin/sh} will often fail to configure
3667 @file{libstdc++-v3}, @file{boehm-gc} or @file{libjava}. We therefore
3668 recommend using the following initial sequence of commands
3671 % CONFIG_SHELL=/bin/ksh
3672 % export CONFIG_SHELL
3675 and proceed as described in @uref{configure.html,,the configure instructions}.
3676 In addition we strongly recommend specifying an absolute path to invoke
3677 @var{srcdir}/configure.
3679 Solaris 2 comes with a number of optional OS packages. Some of these
3680 are needed to use GCC fully, namely @code{SUNWarc},
3681 @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
3682 @code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all
3683 optional packages when installing Solaris 2, you will need to verify that
3684 the packages that GCC needs are installed.
3686 To check whether an optional package is installed, use
3687 the @command{pkginfo} command. To add an optional package, use the
3688 @command{pkgadd} command. For further details, see the Solaris 2
3691 Trying to use the linker and other tools in
3692 @file{/usr/ucb} to install GCC has been observed to cause trouble.
3693 For example, the linker may hang indefinitely. The fix is to remove
3694 @file{/usr/ucb} from your @env{PATH}.
3696 The build process works more smoothly with the legacy Sun tools so, if you
3697 have @file{/usr/xpg4/bin} in your @env{PATH}, we recommend that you place
3698 @file{/usr/bin} before @file{/usr/xpg4/bin} for the duration of the build.
3700 All releases of GNU binutils prior to 2.11.2 have known bugs on this
3701 platform. We recommend the use of GNU binutils 2.11.2 or later, or the
3702 vendor tools (Sun @command{as}, Sun @command{ld}). Note that your mileage
3703 may vary if you use a combination of the GNU tools and the Sun tools: while
3704 the combination GNU @command{as} + Sun @command{ld} should reasonably work,
3705 the reverse combination Sun @command{as} + GNU @command{ld} is known to
3706 cause memory corruption at runtime in some cases for C++ programs.
3708 The stock GNU binutils 2.15 release is broken on this platform because of a
3709 single bug. It has been fixed on the 2.15 branch in the CVS repository.
3710 You can obtain a working version by checking out the binutils-2_15-branch
3711 from the CVS repository or applying the patch
3712 @uref{http://sources.redhat.com/ml/binutils-cvs/2004-09/msg00036.html} to the
3715 We recommend using GNU binutils 2.16 or later in conjunction with GCC 4.x,
3716 or the vendor tools (Sun @command{as}, Sun @command{ld}). However, for
3717 Solaris 10 and above, an additional patch is required in order for the GNU
3718 linker to be able to cope with a new flavor of shared libraries. You
3719 can obtain a working version by checking out the binutils-2_16-branch from
3720 the CVS repository or applying the patch
3721 @uref{http://sourceware.org/ml/binutils-cvs/2005-07/msg00122.html} to the
3724 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
3725 newer: @command{g++} will complain that types are missing. These headers assume
3726 that omitting the type means @code{int}; this assumption worked for C89 but
3727 is wrong for C++, and is now wrong for C99 also.
3729 @command{g++} accepts such (invalid) constructs with the option
3730 @option{-fpermissive}; it
3731 will assume that any missing type is @code{int} (as defined by C89).
3733 There are patches for Solaris 2.6 (105633-56 or newer for SPARC,
3734 106248-42 or newer for Intel), Solaris 7 (108376-21 or newer for SPARC,
3735 108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC,
3736 108653-22 for Intel) that fix this bug.
3738 Sun bug 4927647 sometimes causes random spurious testsuite failures
3739 related to missing diagnostic output. This bug doesn't affect GCC
3740 itself, rather it is a kernel bug triggered by the @command{expect}
3741 program which is used only by the GCC testsuite driver. When the bug
3742 causes the @command{expect} program to miss anticipated output, extra
3743 testsuite failures appear.
3745 There are patches for Solaris 8 (117350-12 or newer for SPARC,
3746 117351-12 or newer for Intel) and Solaris 9 (117171-11 or newer for
3747 SPARC, 117172-11 or newer for Intel) that address this problem.
3752 @heading @anchor{sparc-sun-solaris2}sparc-sun-solaris2*
3754 When GCC is configured to use binutils 2.11.2 or later the binaries
3755 produced are smaller than the ones produced using Sun's native tools;
3756 this difference is quite significant for binaries containing debugging
3759 Sun @command{as} 4.x is broken in that it cannot cope with long symbol names.
3760 A typical error message might look similar to the following:
3763 /usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041: error:
3764 can't compute value of an expression involving an external symbol.
3767 This is Sun bug 4237974. This is fixed with patch 108908-02 for Solaris
3768 2.6 and has been fixed in later (5.x) versions of the assembler,
3769 starting with Solaris 7.
3771 Starting with Solaris 7, the operating system is capable of executing
3772 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
3773 this; the @option{-m64} option enables 64-bit code generation.
3774 However, if all you want is code tuned for the UltraSPARC CPU, you
3775 should try the @option{-mtune=ultrasparc} option instead, which produces
3776 code that, unlike full 64-bit code, can still run on non-UltraSPARC
3779 When configuring on a Solaris 7 or later system that is running a kernel
3780 that supports only 32-bit binaries, one must configure with
3781 @option{--disable-multilib}, since we will not be able to build the
3782 64-bit target libraries.
3784 GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of
3785 the GNU compiler (especially GCC 3.0.x versions), which lead to the
3786 miscompilation of the stage1 compiler and the subsequent failure of the
3787 bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary
3788 stage, i.e.@: to bootstrap that compiler with the base compiler and then
3789 use it to bootstrap the final compiler.
3791 GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE Studio 7)
3792 and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a bootstrap
3793 failure in form of a miscompilation of the stage1 compiler by the Sun
3794 compiler. This is Sun bug 4974440. This is fixed with patch 112760-07.
3796 GCC 3.4 changed the default debugging format from STABS to DWARF-2 for
3797 32-bit code on Solaris 7 and later. If you use the Sun assembler, this
3798 change apparently runs afoul of Sun bug 4910101 (which is referenced as
3799 a x86-only problem by Sun, probably because they do not use DWARF-2).
3800 A symptom of the problem is that you cannot compile C++ programs like
3801 @command{groff} 1.19.1 without getting messages similar to the following:
3804 ld: warning: relocation error: R_SPARC_UA32: @dots{}
3805 external symbolic relocation against non-allocatable section
3806 .debug_info cannot be processed at runtime: relocation ignored.
3809 To work around this problem, compile with @option{-gstabs+} instead of
3812 When configuring the GNU Multiple Precision Library (GMP) on a Solaris 7
3813 or later system, the canonical target triplet must be specified as the
3814 @command{build} parameter on the configure line:
3817 ./configure --build=sparc-sun-solaris2.7 --prefix=xxx --enable-mpfr
3823 @heading @anchor{sparc-sun-solaris27}sparc-sun-solaris2.7
3825 Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in
3826 the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8
3827 and later, including all EGCS releases. Sun formerly recommended
3828 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to
3829 recommend it only for people who use Sun's compilers.
3831 Here are some workarounds to this problem:
3834 Do not install Sun patch 107058-01 until after Sun releases a
3835 complete patch for bug 4210064. This is the simplest course to take,
3836 unless you must also use Sun's C compiler. Unfortunately 107058-01
3837 is preinstalled on some new Solaris 7-based hosts, so you may have to
3841 Copy the original, unpatched Solaris 7
3842 @command{/usr/ccs/bin/as} into
3843 @command{/usr/local/libexec/gcc/sparc-sun-solaris2.7/3.4/as},
3844 adjusting the latter name to fit your local conventions and software
3848 Install Sun patch 106950-03 (1999-05-25) or later. Nobody with
3849 both 107058-01 and 106950-03 installed has reported the bug with GCC
3850 and Sun's dynamic linker. This last course of action is riskiest,
3851 for two reasons. First, you must install 106950 on all hosts that
3852 run code generated by GCC; it doesn't suffice to install it only on
3853 the hosts that run GCC itself. Second, Sun says that 106950-03 is
3854 only a partial fix for bug 4210064, but Sun doesn't know whether the
3855 partial fix is adequate for GCC@. Revision -08 or later should fix
3856 the bug. The current (as of 2004-05-23) revision is -24, and is included in
3857 the Solaris 7 Recommended Patch Cluster.
3860 GCC 3.3 triggers a bug in version 5.0 Alpha 03/27/98 of the Sun assembler,
3861 which causes a bootstrap failure when linking the 64-bit shared version of
3862 libgcc. A typical error message is:
3865 ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o:
3866 symbol <unknown>: offset 0xffffffff7ec133e7 is non-aligned.
3869 This bug has been fixed in the final 5.0 version of the assembler.
3871 A similar problem was reported for version Sun WorkShop 6 99/08/18 of the
3872 Sun assembler, which causes a bootstrap failure with GCC 4.0.0:
3875 ld: fatal: relocation error: R_SPARC_DISP32:
3876 file .libs/libstdc++.lax/libsupc++convenience.a/vterminate.o:
3877 symbol <unknown>: offset 0xfccd33ad is non-aligned
3880 This bug has been fixed in more recent revisions of the assembler.
3885 @heading @anchor{sparc-x-linux}sparc-*-linux*
3887 GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
3888 or newer on this platform. All earlier binutils and glibc
3889 releases mishandled unaligned relocations on @code{sparc-*-*} targets.
3895 @heading @anchor{sparc64-x-solaris2}sparc64-*-solaris2*
3897 The following compiler flags must be specified in the configure
3898 step in order to bootstrap this target with the Sun compiler:
3901 % CC="cc -xildoff -xarch=v9" @var{srcdir}/configure [@var{options}] [@var{target}]
3904 @option{-xildoff} turns off the incremental linker, and @option{-xarch=v9}
3905 specifies the SPARC-V9 architecture to the Sun linker and assembler.
3910 @heading @anchor{sparcv9-x-solaris2}sparcv9-*-solaris2*
3912 This is a synonym for sparc64-*-solaris2*.
3917 @heading @anchor{x-x-sysv}*-*-sysv*
3918 On System V release 3, you may get this error message
3922 ld fatal: failed to write symbol name @var{something}
3923 in strings table for file @var{whatever}
3926 This probably indicates that the disk is full or your ulimit won't allow
3927 the file to be as large as it needs to be.
3929 This problem can also result because the kernel parameter @code{MAXUMEM}
3930 is too small. If so, you must regenerate the kernel and make the value
3931 much larger. The default value is reported to be 1024; a value of 32768
3932 is said to work. Smaller values may also work.
3934 On System V, if you get an error like this,
3937 /usr/local/lib/bison.simple: In function `yyparse':
3938 /usr/local/lib/bison.simple:625: virtual memory exhausted
3942 that too indicates a problem with disk space, ulimit, or @code{MAXUMEM}.
3944 On a System V release 4 system, make sure @file{/usr/bin} precedes
3945 @file{/usr/ucb} in @code{PATH}. The @command{cc} command in
3946 @file{/usr/ucb} uses libraries which have bugs.
3951 @heading @anchor{vax-dec-ultrix}vax-dec-ultrix
3952 Don't try compiling with VAX C (@command{vcc}). It produces incorrect code
3953 in some cases (for example, when @code{alloca} is used).
3958 @heading @anchor{x-x-vxworks}*-*-vxworks*
3959 Support for VxWorks is in flux. At present GCC supports @emph{only} the
3960 very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC@.
3961 We welcome patches for other architectures supported by VxWorks 5.5.
3962 Support for VxWorks AE would also be welcome; we believe this is merely
3963 a matter of writing an appropriate ``configlette'' (see below). We are
3964 not interested in supporting older, a.out or COFF-based, versions of
3967 VxWorks comes with an older version of GCC installed in
3968 @file{@var{$WIND_BASE}/host}; we recommend you do not overwrite it.
3969 Choose an installation @var{prefix} entirely outside @var{$WIND_BASE}.
3970 Before running @command{configure}, create the directories @file{@var{prefix}}
3971 and @file{@var{prefix}/bin}. Link or copy the appropriate assembler,
3972 linker, etc.@: into @file{@var{prefix}/bin}, and set your @var{PATH} to
3973 include that directory while running both @command{configure} and
3976 You must give @command{configure} the
3977 @option{--with-headers=@var{$WIND_BASE}/target/h} switch so that it can
3978 find the VxWorks system headers. Since VxWorks is a cross compilation
3979 target only, you must also specify @option{--target=@var{target}}.
3980 @command{configure} will attempt to create the directory
3981 @file{@var{prefix}/@var{target}/sys-include} and copy files into it;
3982 make sure the user running @command{configure} has sufficient privilege
3985 GCC's exception handling runtime requires a special ``configlette''
3986 module, @file{contrib/gthr_supp_vxw_5x.c}. Follow the instructions in
3987 that file to add the module to your kernel build. (Future versions of
3988 VxWorks will incorporate this module.)
3993 @heading @anchor{x86-64-x-x}x86_64-*-*, amd64-*-*
3995 GCC supports the x86-64 architecture implemented by the AMD64 processor
3996 (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD@.
3997 On GNU/Linux the default is a bi-arch compiler which is able to generate
3998 both 64-bit x86-64 and 32-bit x86 code (via the @option{-m32} switch).
4003 @heading @anchor{xtensa-x-elf}xtensa-*-elf
4005 This target is intended for embedded Xtensa systems using the
4006 @samp{newlib} C library. It uses ELF but does not support shared
4007 objects. Designed-defined instructions specified via the
4008 Tensilica Instruction Extension (TIE) language are only supported
4009 through inline assembly.
4011 The Xtensa configuration information must be specified prior to
4012 building GCC@. The @file{include/xtensa-config.h} header
4013 file contains the configuration information. If you created your
4014 own Xtensa configuration with the Xtensa Processor Generator, the
4015 downloaded files include a customized copy of this header file,
4016 which you can use to replace the default header file.
4021 @heading @anchor{xtensa-x-linux}xtensa-*-linux*
4023 This target is for Xtensa systems running GNU/Linux. It supports ELF
4024 shared objects and the GNU C library (glibc). It also generates
4025 position-independent code (PIC) regardless of whether the
4026 @option{-fpic} or @option{-fPIC} options are used. In other
4027 respects, this target is the same as the
4028 @uref{#xtensa-*-elf,,@samp{xtensa-*-elf}} target.
4033 @heading @anchor{windows}Microsoft Windows (32-bit)
4035 Ports of GCC are included with the
4036 @uref{http://www.cygwin.com/,,Cygwin environment}.
4038 GCC will build under Cygwin without modification; it does not build
4039 with Microsoft's C++ compiler and there are no plans to make it do so.
4044 @heading @anchor{os2}OS/2
4046 GCC does not currently support OS/2. However, Andrew Zabolotny has been
4047 working on a generic OS/2 port with pgcc. The current code can be found
4048 at @uref{http://www.goof.com/pcg/os2/,,http://www.goof.com/pcg/os2/}.
4053 @heading @anchor{older}Older systems
4055 GCC contains support files for many older (1980s and early
4056 1990s) Unix variants. For the most part, support for these systems
4057 has not been deliberately removed, but it has not been maintained for
4058 several years and may suffer from bitrot.
4060 Starting with GCC 3.1, each release has a list of ``obsoleted'' systems.
4061 Support for these systems is still present in that release, but
4062 @command{configure} will fail unless the @option{--enable-obsolete}
4063 option is given. Unless a maintainer steps forward, support for these
4064 systems will be removed from the next release of GCC@.
4066 Support for old systems as hosts for GCC can cause problems if the
4067 workarounds for compiler, library and operating system bugs affect the
4068 cleanliness or maintainability of the rest of GCC@. In some cases, to
4069 bring GCC up on such a system, if still possible with current GCC, may
4070 require first installing an old version of GCC which did work on that
4071 system, and using it to compile a more recent GCC, to avoid bugs in the
4072 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
4073 @file{old-releases} directory on the @uref{../mirrors.html,,GCC mirror
4074 sites}. Header bugs may generally be avoided using
4075 @command{fixincludes}, but bugs or deficiencies in libraries and the
4076 operating system may still cause problems.
4078 Support for older systems as targets for cross-compilation is less
4079 problematic than support for them as hosts for GCC; if an enthusiast
4080 wishes to make such a target work again (including resurrecting any of
4081 the targets that never worked with GCC 2, starting from the last
4082 version before they were removed), patches
4083 @uref{../contribute.html,,following the usual requirements} would be
4084 likely to be accepted, since they should not affect the support for more
4087 For some systems, old versions of GNU binutils may also be useful,
4088 and are available from @file{pub/binutils/old-releases} on
4089 @uref{http://sources.redhat.com/mirrors.html,,sources.redhat.com mirror sites}.
4091 Some of the information on specific systems above relates to
4092 such older systems, but much of the information
4093 about GCC on such systems (which may no longer be applicable to
4094 current GCC) is to be found in the GCC texinfo manual.
4099 @heading @anchor{elf}all ELF targets (SVR4, Solaris 2, etc.)
4101 C++ support is significantly better on ELF targets if you use the
4102 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
4103 inlines, vtables and template instantiations will be discarded
4112 @uref{./index.html,,Return to the GCC Installation page}
4116 @c ***Old documentation******************************************************
4118 @include install-old.texi
4124 @uref{./index.html,,Return to the GCC Installation page}
4128 @c ***GFDL********************************************************************
4136 @uref{./index.html,,Return to the GCC Installation page}
4140 @c ***************************************************************************
4141 @c Part 6 The End of the Document
4143 @comment node-name, next, previous, up
4144 @node Concept Index, , GNU Free Documentation License, Top
4148 @unnumbered Concept Index