@end html @ifhtml @uref{./index.html,,Return to the GCC Installation page} @insertcopying @end ifhtml @end ifset @c ***Prerequisites************************************************** @ifnothtml @comment node-name, next, previous, up @node Prerequisites, Downloading the source, , Installing GCC @end ifnothtml @ifset prerequisiteshtml @ifnothtml @chapter Prerequisites @end ifnothtml @cindex Prerequisites GCC requires that various tools and packages be available for use in the build procedure. Modifying GCC sources requires additional tools described below. @heading Tools/packages necessary for building GCC @table @asis @item ISO C++98 compiler Necessary to bootstrap GCC, although versions of GCC prior to 4.8 also allow bootstrapping with a ISO C89 compiler and versions of GCC prior to 3.4 also allow bootstrapping with a traditional (K&R) C compiler. To build all languages in a cross-compiler or other configuration where 3-stage bootstrap is not performed, you need to start with an existing GCC binary (version 3.4 or later) because source code for language frontends other than C might use GCC extensions. Note that to bootstrap GCC with versions of GCC earlier than 3.4, you may need to use @option{--disable-stage1-checking}, though bootstrapping the compiler with such earlier compilers is strongly discouraged. @item GNAT In order to build the Ada compiler (GNAT) you must already have GNAT installed because portions of the Ada frontend are written in Ada (with GNAT extensions.) Refer to the Ada installation instructions for more specific information. @item A ``working'' POSIX compatible shell, or GNU bash Necessary when running @command{configure} because some @command{/bin/sh} shells have bugs and may crash when configuring the target libraries. In other cases, @command{/bin/sh} or @command{ksh} have disastrous corner-case performance problems. This can cause target @command{configure} runs to literally take days to complete in some cases. So on some platforms @command{/bin/ksh} is sufficient, on others it isn't. See the host/target specific instructions for your platform, or use @command{bash} to be sure. Then set @env{CONFIG_SHELL} in your environment to your ``good'' shell prior to running @command{configure}/@command{make}. @command{zsh} is not a fully compliant POSIX shell and will not work when configuring GCC@. @item A POSIX or SVR4 awk Necessary for creating some of the generated source files for GCC@. If in doubt, use a recent GNU awk version, as some of the older ones are broken. GNU awk version 3.1.5 is known to work. @item GNU binutils Necessary in some circumstances, optional in others. See the host/target specific instructions for your platform for the exact requirements. @item gzip version 1.2.4 (or later) or @itemx bzip2 version 1.0.2 (or later) Necessary to uncompress GCC @command{tar} files when source code is obtained via FTP mirror sites. @item GNU make version 3.80 (or later) You must have GNU make installed to build GCC@. @item GNU tar version 1.14 (or later) Necessary (only on some platforms) to untar the source code. Many systems' @command{tar} programs will also work, only try GNU @command{tar} if you have problems. @item Perl version 5.6.1 (or later) Necessary when targeting Darwin, building @samp{libstdc++}, and not using @option{--disable-symvers}. Necessary when targeting Solaris 2 with Sun @command{ld} and not using @option{--disable-symvers}. The bundled @command{perl} in Solaris@tie{}8 and up works. Necessary when regenerating @file{Makefile} dependencies in libiberty. Necessary when regenerating @file{libiberty/functions.texi}. Necessary when generating manpages from Texinfo manuals. Used by various scripts to generate some files included in SVN (mainly Unicode-related and rarely changing) from source tables. @item @command{jar}, or InfoZIP (@command{zip} and @command{unzip}) Necessary to build libgcj, the GCJ runtime. @end table Several support libraries are necessary to build GCC, some are required, others optional. While any sufficiently new version of required tools usually work, library requirements are generally stricter. Newer versions may work in some cases, but it's safer to use the exact versions documented. We appreciate bug reports about problems with newer versions, though. If your OS vendor provides packages for the support libraries then using those packages may be the simplest way to install the libraries. @table @asis @item GNU Multiple Precision Library (GMP) version 4.3.2 (or later) Necessary to build GCC@. If a GMP source distribution is found in a subdirectory of your GCC sources named @file{gmp}, it will be built together with GCC. Alternatively, if GMP is already installed but it is not in your library search path, you will have to configure with the @option{--with-gmp} configure option. See also @option{--with-gmp-lib} and @option{--with-gmp-include}. @item MPFR Library version 2.4.2 (or later) Necessary to build GCC@. It can be downloaded from @uref{http://www.mpfr.org/}. If an MPFR source distribution is found in a subdirectory of your GCC sources named @file{mpfr}, it will be built together with GCC. Alternatively, if MPFR is already installed but it is not in your default library search path, the @option{--with-mpfr} configure option should be used. See also @option{--with-mpfr-lib} and @option{--with-mpfr-include}. @item MPC Library version 0.8.1 (or later) Necessary to build GCC@. It can be downloaded from @uref{http://www.multiprecision.org/}. If an MPC source distribution is found in a subdirectory of your GCC sources named @file{mpc}, it will be built together with GCC. Alternatively, if MPC is already installed but it is not in your default library search path, the @option{--with-mpc} configure option should be used. See also @option{--with-mpc-lib} and @option{--with-mpc-include}. @item ISL Library version 0.11.1 Necessary to build GCC with the Graphite loop optimizations. It can be downloaded from @uref{ftp://gcc.gnu.org/pub/gcc/infrastructure/} as @file{isl-0.11.1.tar.bz2}. The @option{--with-isl} configure option should be used if ISL is not installed in your default library search path. @item CLooG 0.18.0 Necessary to build GCC with the Graphite loop optimizations. It can be downloaded from @uref{ftp://gcc.gnu.org/pub/gcc/infrastructure/} as @file{cloog-0.18.0.tar.gz}. The @option{--with-cloog} configure option should be used if CLooG is not installed in your default library search path. CLooG needs to be built against ISL 0.11.1. Use @option{--with-isl=system} to direct CLooG to pick up an already installed ISL, otherwise it will use ISL 0.11.1 as bundled with CLooG. CLooG needs to be configured to use GMP internally, use @option{--with-bits=gmp} to direct it to do that. @end table @heading Tools/packages necessary for modifying GCC @table @asis @item autoconf version 2.64 @itemx GNU m4 version 1.4.6 (or later) Necessary when modifying @file{configure.ac}, @file{aclocal.m4}, etc.@: to regenerate @file{configure} and @file{config.in} files. @item automake version 1.11.1 Necessary when modifying a @file{Makefile.am} file to regenerate its associated @file{Makefile.in}. Much of GCC does not use automake, so directly edit the @file{Makefile.in} file. Specifically this applies to the @file{gcc}, @file{intl}, @file{libcpp}, @file{libiberty}, @file{libobjc} directories as well as any of their subdirectories. For directories that use automake, GCC requires the latest release in the 1.11 series, which is currently 1.11.1. When regenerating a directory to a newer version, please update all the directories using an older 1.11 to the latest released version. @item gettext version 0.14.5 (or later) Needed to regenerate @file{gcc.pot}. @item gperf version 2.7.2 (or later) Necessary when modifying @command{gperf} input files, e.g.@: @file{gcc/cp/cfns.gperf} to regenerate its associated header file, e.g.@: @file{gcc/cp/cfns.h}. @item DejaGnu 1.4.4 @itemx Expect @itemx Tcl Necessary to run the GCC testsuite; see the section on testing for details. @item autogen version 5.5.4 (or later) and @itemx guile version 1.4.1 (or later) Necessary to regenerate @file{fixinc/fixincl.x} from @file{fixinc/inclhack.def} and @file{fixinc/*.tpl}. Necessary to run @samp{make check} for @file{fixinc}. Necessary to regenerate the top level @file{Makefile.in} file from @file{Makefile.tpl} and @file{Makefile.def}. @item Flex version 2.5.4 (or later) Necessary when modifying @file{*.l} files. Necessary to build GCC during development because the generated output files are not included in the SVN repository. They are included in releases. @item Texinfo version 4.7 (or later) Necessary for running @command{makeinfo} when modifying @file{*.texi} files to test your changes. Necessary for running @command{make dvi} or @command{make pdf} to create printable documentation in DVI or PDF format. Texinfo version 4.8 or later is required for @command{make pdf}. Necessary to build GCC documentation during development because the generated output files are not included in the SVN repository. They are included in releases. @item @TeX{} (any working version) Necessary for running @command{texi2dvi} and @command{texi2pdf}, which are used when running @command{make dvi} or @command{make pdf} to create DVI or PDF files, respectively. @item SVN (any version) @itemx SSH (any version) Necessary to access the SVN repository. Public releases and weekly snapshots of the development sources are also available via FTP@. @item GNU diffutils version 2.7 (or later) Useful when submitting patches for the GCC source code. @item patch version 2.5.4 (or later) Necessary when applying patches, created with @command{diff}, to one's own sources. @item ecj1 @itemx gjavah If you wish to modify @file{.java} files in libjava, you will need to configure with @option{--enable-java-maintainer-mode}, and you will need to have executables named @command{ecj1} and @command{gjavah} in your path. The @command{ecj1} executable should run the Eclipse Java compiler via the GCC-specific entry point. You can download a suitable jar from @uref{ftp://sourceware.org/pub/java/}, or by running the script @command{contrib/download_ecj}. @item antlr.jar version 2.7.1 (or later) @itemx antlr binary If you wish to build the @command{gjdoc} binary in libjava, you will need to have an @file{antlr.jar} library available. The library is searched for in system locations but can be specified with @option{--with-antlr-jar=} instead. When configuring with @option{--enable-java-maintainer-mode}, you will need to have one of the executables named @command{cantlr}, @command{runantlr} or @command{antlr} in your path. @end table @html
@end html @ifhtml @uref{./index.html,,Return to the GCC Installation page} @end ifhtml @end ifset @c ***Downloading the source************************************************** @ifnothtml @comment node-name, next, previous, up @node Downloading the source, Configuration, Prerequisites, Installing GCC @end ifnothtml @ifset downloadhtml @ifnothtml @chapter Downloading GCC @end ifnothtml @cindex Downloading GCC @cindex Downloading the Source GCC is distributed via @uref{http://gcc.gnu.org/svn.html,,SVN} and FTP tarballs compressed with @command{gzip} or @command{bzip2}. Please refer to the @uref{http://gcc.gnu.org/releases.html,,releases web page} for information on how to obtain GCC@. The source distribution includes the C, C++, Objective-C, Fortran, Java, and Ada (in the case of GCC 3.1 and later) compilers, as well as runtime libraries for C++, Objective-C, Fortran, and Java. For previous versions these were downloadable as separate components such as the core GCC distribution, which included the C language front end and shared components, and language-specific distributions including the language front end and the language runtime (where appropriate). If you also intend to build binutils (either to upgrade an existing installation or for use in place of the corresponding tools of your OS), unpack the binutils distribution either in the same directory or a separate one. In the latter case, add symbolic links to any components of the binutils you intend to build alongside the compiler (@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld}, @file{opcodes}, @dots{}) to the directory containing the GCC sources. Likewise the GMP, MPFR and MPC libraries can be automatically built together with GCC. Unpack the GMP, MPFR and/or MPC source distributions in the directory containing the GCC sources and rename their directories to @file{gmp}, @file{mpfr} and @file{mpc}, respectively (or use symbolic links with the same name). @html
@end html @ifhtml @uref{./index.html,,Return to the GCC Installation page} @end ifhtml @end ifset @c ***Configuration*********************************************************** @ifnothtml @comment node-name, next, previous, up @node Configuration, Building, Downloading the source, Installing GCC @end ifnothtml @ifset configurehtml @ifnothtml @chapter Installing GCC: Configuration @end ifnothtml @cindex Configuration @cindex Installing GCC: Configuration Like most GNU software, GCC must be configured before it can be built. This document describes the recommended configuration procedure for both native and cross targets. We use @var{srcdir} to refer to the toplevel source directory for GCC; we use @var{objdir} to refer to the toplevel build/object directory. If you obtained the sources via SVN, @var{srcdir} must refer to the top @file{gcc} directory, the one where the @file{MAINTAINERS} file can be found, and not its @file{gcc} subdirectory, otherwise the build will fail. If either @var{srcdir} or @var{objdir} is located on an automounted NFS file system, the shell's built-in @command{pwd} command will return temporary pathnames. Using these can lead to various sorts of build problems. To avoid this issue, set the @env{PWDCMD} environment variable to an automounter-aware @command{pwd} command, e.g., @command{pawd} or @samp{amq -w}, during the configuration and build phases. First, we @strong{highly} recommend that GCC be built into a separate directory from the sources which does @strong{not} reside within the source tree. This is how we generally build GCC; building where @var{srcdir} == @var{objdir} should still work, but doesn't get extensive testing; building where @var{objdir} is a subdirectory of @var{srcdir} is unsupported. If you have previously built GCC in the same directory for a different target machine, do @samp{make distclean} to delete all files that might be invalid. One of the files this deletes is @file{Makefile}; if @samp{make distclean} complains that @file{Makefile} does not exist or issues a message like ``don't know how to make distclean'' it probably means that the directory is already suitably clean. However, with the recommended method of building in a separate @var{objdir}, you should simply use a different @var{objdir} for each target. Second, when configuring a native system, either @command{cc} or @command{gcc} must be in your path or you must set @env{CC} in your environment before running configure. Otherwise the configuration scripts may fail. @ignore Note that the bootstrap compiler and the resulting GCC must be link compatible, else the bootstrap will fail with linker errors about incompatible object file formats. Several multilibed targets are affected by this requirement, see @ifnothtml @ref{Specific, host/target specific installation notes}. @end ifnothtml @ifhtml @uref{specific.html,,host/target specific installation notes}. @end ifhtml @end ignore To configure GCC: @smallexample % mkdir @var{objdir} % cd @var{objdir} % @var{srcdir}/configure [@var{options}] [@var{target}] @end smallexample @heading Distributor options If you will be distributing binary versions of GCC, with modifications to the source code, you should use the options described in this section to make clear that your version contains modifications. @table @code @item --with-pkgversion=@var{version} Specify a string that identifies your package. You may wish to include a build number or build date. This version string will be included in the output of @command{gcc --version}. This suffix does not replace the default version string, only the @samp{GCC} part. The default value is @samp{GCC}. @item --with-bugurl=@var{url} Specify the URL that users should visit if they wish to report a bug. You are of course welcome to forward bugs reported to you to the FSF, if you determine that they are not bugs in your modifications. The default value refers to the FSF's GCC bug tracker. @end table @heading Target specification @itemize @bullet @item GCC has code to correctly determine the correct value for @var{target} for nearly all native systems. Therefore, we highly recommend you do not provide a configure target when configuring a native compiler. @item @var{target} must be specified as @option{--target=@var{target}} when configuring a cross compiler; examples of valid targets would be m68k-elf, sh-elf, etc. @item Specifying just @var{target} instead of @option{--target=@var{target}} implies that the host defaults to @var{target}. @end itemize @heading Options specification Use @var{options} to override several configure time options for GCC@. A list of supported @var{options} follows; @samp{configure --help} may list other options, but those not listed below may not work and should not normally be used. Note that each @option{--enable} option has a corresponding @option{--disable} option and that each @option{--with} option has a corresponding @option{--without} option. @table @code @item --prefix=@var{dirname} Specify the toplevel installation directory. This is the recommended way to install the tools into a directory other than the default. The toplevel installation directory defaults to @file{/usr/local}. We @strong{highly} recommend against @var{dirname} being the same or a subdirectory of @var{objdir} or vice versa. If specifying a directory beneath a user's home directory tree, some shells will not expand @var{dirname} correctly if it contains the @samp{~} metacharacter; use @env{$HOME} instead. The following standard @command{autoconf} options are supported. Normally you should not need to use these options. @table @code @item --exec-prefix=@var{dirname} Specify the toplevel installation directory for architecture-dependent files. The default is @file{@var{prefix}}. @item --bindir=@var{dirname} Specify the installation directory for the executables called by users (such as @command{gcc} and @command{g++}). The default is @file{@var{exec-prefix}/bin}. @item --libdir=@var{dirname} Specify the installation directory for object code libraries and internal data files of GCC@. The default is @file{@var{exec-prefix}/lib}. @item --libexecdir=@var{dirname} Specify the installation directory for internal executables of GCC@. The default is @file{@var{exec-prefix}/libexec}. @item --with-slibdir=@var{dirname} Specify the installation directory for the shared libgcc library. The default is @file{@var{libdir}}. @item --datarootdir=@var{dirname} Specify the root of the directory tree for read-only architecture-independent data files referenced by GCC@. The default is @file{@var{prefix}/share}. @item --infodir=@var{dirname} Specify the installation directory for documentation in info format. The default is @file{@var{datarootdir}/info}. @item --datadir=@var{dirname} Specify the installation directory for some architecture-independent data files referenced by GCC@. The default is @file{@var{datarootdir}}. @item --docdir=@var{dirname} Specify the installation directory for documentation files (other than Info) for GCC@. The default is @file{@var{datarootdir}/doc}. @item --htmldir=@var{dirname} Specify the installation directory for HTML documentation files. The default is @file{@var{docdir}}. @item --pdfdir=@var{dirname} Specify the installation directory for PDF documentation files. The default is @file{@var{docdir}}. @item --mandir=@var{dirname} Specify the installation directory for manual pages. The default is @file{@var{datarootdir}/man}. (Note that the manual pages are only extracts from the full GCC manuals, which are provided in Texinfo format. The manpages are derived by an automatic conversion process from parts of the full manual.) @item --with-gxx-include-dir=@var{dirname} Specify the installation directory for G++ header files. The default depends on other configuration options, and differs between cross and native configurations. @item --with-specs=@var{specs} Specify additional command line driver SPECS. This can be useful if you need to turn on a non-standard feature by default without modifying the compiler's source code, for instance @option{--with-specs=%@{!fcommon:%@{!fno-common:-fno-common@}@}}. @ifnothtml @xref{Spec Files,, Specifying subprocesses and the switches to pass to them, gcc, Using the GNU Compiler Collection (GCC)}, @end ifnothtml @ifhtml See ``Spec Files'' in the main manual @end ifhtml @end table @item --program-prefix=@var{prefix} GCC supports some transformations of the names of its programs when installing them. This option prepends @var{prefix} to the names of programs to install in @var{bindir} (see above). For example, specifying @option{--program-prefix=foo-} would result in @samp{gcc} being installed as @file{/usr/local/bin/foo-gcc}. @item --program-suffix=@var{suffix} Appends @var{suffix} to the names of programs to install in @var{bindir} (see above). For example, specifying @option{--program-suffix=-3.1} would result in @samp{gcc} being installed as @file{/usr/local/bin/gcc-3.1}. @item --program-transform-name=@var{pattern} Applies the @samp{sed} script @var{pattern} to be applied to the names of programs to install in @var{bindir} (see above). @var{pattern} has to consist of one or more basic @samp{sed} editing commands, separated by semicolons. For example, if you want the @samp{gcc} program name to be transformed to the installed program @file{/usr/local/bin/myowngcc} and the @samp{g++} program name to be transformed to @file{/usr/local/bin/gspecial++} without changing other program names, you could use the pattern @option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'} to achieve this effect. All three options can be combined and used together, resulting in more complex conversion patterns. As a basic rule, @var{prefix} (and @var{suffix}) are prepended (appended) before further transformations can happen with a special transformation script @var{pattern}. As currently implemented, this option only takes effect for native builds; cross compiler binaries' names are not transformed even when a transformation is explicitly asked for by one of these options. For native builds, some of the installed programs are also installed with the target alias in front of their name, as in @samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen before the target alias is prepended to the name---so, specifying @option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the resulting binary would be installed as @file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}. As a last shortcoming, none of the installed Ada programs are transformed yet, which will be fixed in some time. @item --with-local-prefix=@var{dirname} Specify the installation directory for local include files. The default is @file{/usr/local}. Specify this option if you want the compiler to search directory @file{@var{dirname}/include} for locally installed header files @emph{instead} of @file{/usr/local/include}. You should specify @option{--with-local-prefix} @strong{only} if your site has a different convention (not @file{/usr/local}) for where to put site-specific files. The default value for @option{--with-local-prefix} is @file{/usr/local} regardless of the value of @option{--prefix}. Specifying @option{--prefix} has no effect on which directory GCC searches for local header files. This may seem counterintuitive, but actually it is logical. The purpose of @option{--prefix} is to specify where to @emph{install GCC}. The local header files in @file{/usr/local/include}---if you put any in that directory---are not part of GCC@. They are part of other programs---perhaps many others. (GCC installs its own header files in another directory which is based on the @option{--prefix} value.) Both the local-prefix include directory and the GCC-prefix include directory are part of GCC's ``system include'' directories. Although these two directories are not fixed, they need to be searched in the proper order for the correct processing of the include_next directive. The local-prefix include directory is searched before the GCC-prefix include directory. Another characteristic of system include directories is that pedantic warnings are turned off for headers in these directories. Some autoconf macros add @option{-I @var{directory}} options to the compiler command line, to ensure that directories containing installed packages' headers are searched. When @var{directory} is one of GCC's system include directories, GCC will ignore the option so that system directories continue to be processed in the correct order. This may result in a search order different from what was specified but the directory will still be searched. GCC automatically searches for ordinary libraries using @env{GCC_EXEC_PREFIX}. Thus, when the same installation prefix is used for both GCC and packages, GCC will automatically search for both headers and libraries. This provides a configuration that is easy to use. GCC behaves in a manner similar to that when it is installed as a system compiler in @file{/usr}. Sites that need to install multiple versions of GCC may not want to use the above simple configuration. It is possible to use the @option{--program-prefix}, @option{--program-suffix} and @option{--program-transform-name} options to install multiple versions into a single directory, but it may be simpler to use different prefixes and the @option{--with-local-prefix} option to specify the location of the site-specific files for each version. It will then be necessary for users to specify explicitly the location of local site libraries (e.g., with @env{LIBRARY_PATH}). The same value can be used for both @option{--with-local-prefix} and @option{--prefix} provided it is not @file{/usr}. This can be used to avoid the default search of @file{/usr/local/include}. @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}! The directory you use for @option{--with-local-prefix} @strong{must not} contain any of the system's standard header files. If it did contain them, certain programs would be miscompiled (including GNU Emacs, on certain targets), because this would override and nullify the header file corrections made by the @command{fixincludes} script. Indications are that people who use this option use it based on mistaken ideas of what it is for. People use it as if it specified where to install part of GCC@. Perhaps they make this assumption because installing GCC creates the directory. @item --with-native-system-header-dir=@var{dirname} Specifies that @var{dirname} is the directory that contains native system header files, rather than @file{/usr/include}. This option is most useful if you are creating a compiler that should be isolated from the system as much as possible. It is most commonly used with the @option{--with-sysroot} option and will cause GCC to search @var{dirname} inside the system root specified by that option. @item --enable-shared[=@var{package}[,@dots{}]] Build shared versions of libraries, if shared libraries are supported on the target platform. Unlike GCC 2.95.x and earlier, shared libraries are enabled by default on all platforms that support shared libraries. If a list of packages is given as an argument, build shared libraries only for the listed packages. For other packages, only static libraries will be built. Package names currently recognized in the GCC tree are @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc}, @samp{ada}, @samp{libada}, @samp{libjava}, @samp{libgo}, and @samp{libobjc}. Note @samp{libiberty} does not support shared libraries at all. Use @option{--disable-shared} to build only static libraries. Note that @option{--disable-shared} does not accept a list of package names as argument, only @option{--enable-shared} does. @item @anchor{with-gnu-as}--with-gnu-as Specify that the compiler should assume that the assembler it finds is the GNU assembler. However, this does not modify the rules to find an assembler and will result in confusion if the assembler found is not actually the GNU assembler. (Confusion may also result if the compiler finds the GNU assembler but has not been configured with @option{--with-gnu-as}.) If you have more than one assembler installed on your system, you may want to use this option in connection with @option{--with-as=@var{pathname}} or @option{--with-build-time-tools=@var{pathname}}. The following systems are the only ones where it makes a difference whether you use the GNU assembler. On any other system, @option{--with-gnu-as} has no effect. @itemize @bullet @item @samp{hppa1.0-@var{any}-@var{any}} @item @samp{hppa1.1-@var{any}-@var{any}} @item @samp{sparc-sun-solaris2.@var{any}} @item @samp{sparc64-@var{any}-solaris2.@var{any}} @end itemize @item @anchor{with-as}--with-as=@var{pathname} Specify that the compiler should use the assembler pointed to by @var{pathname}, rather than the one found by the standard rules to find an assembler, which are: @itemize @bullet @item Unless GCC is being built with a cross compiler, check the @file{@var{libexec}/gcc/@var{target}/@var{version}} directory. @var{libexec} defaults to @file{@var{exec-prefix}/libexec}; @var{exec-prefix} defaults to @var{prefix}, which defaults to @file{/usr/local} unless overridden by the @option{--prefix=@var{pathname}} switch described above. @var{target} is the target system triple, such as @samp{sparc-sun-solaris2.7}, and @var{version} denotes the GCC version, such as 3.0. @item If the target system is the same that you are building on, check operating system specific directories (e.g.@: @file{/usr/ccs/bin} on Sun Solaris 2). @item Check in the @env{PATH} for a tool whose name is prefixed by the target system triple. @item Check in the @env{PATH} for a tool whose name is not prefixed by the target system triple, if the host and target system triple are the same (in other words, we use a host tool if it can be used for the target as well). @end itemize You may want to use @option{--with-as} if no assembler is installed in the directories listed above, or if you have multiple assemblers installed and want to choose one that is not found by the above rules. @item @anchor{with-gnu-ld}--with-gnu-ld Same as @uref{#with-gnu-as,,@option{--with-gnu-as}} but for the linker. @item --with-ld=@var{pathname} Same as @uref{#with-as,,@option{--with-as}} but for the linker. @item --with-stabs Specify that stabs debugging information should be used instead of whatever format the host normally uses. Normally GCC uses the same debug format as the host system. On MIPS based systems and on Alphas, you must specify whether you want GCC to create the normal ECOFF debugging format, or to use BSD-style stabs passed through the ECOFF symbol table. The normal ECOFF debug format cannot fully handle languages other than C@. BSD stabs format can handle other languages, but it only works with the GNU debugger GDB@. Normally, GCC uses the ECOFF debugging format by default; if you prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@. No matter which default you choose when you configure GCC, the user can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly the debug format for a particular compilation. @option{--with-stabs} is meaningful on the ISC system on the 386, also, if @option{--with-gas} is used. It selects use of stabs debugging information embedded in COFF output. This kind of debugging information supports C++ well; ordinary COFF debugging information does not. @option{--with-stabs} is also meaningful on 386 systems running SVR4. It selects use of stabs debugging information embedded in ELF output. The C++ compiler currently (2.6.0) does not support the DWARF debugging information normally used on 386 SVR4 platforms; stabs provide a workable alternative. This requires gas and gdb, as the normal SVR4 tools can not generate or interpret stabs. @item --with-tls=@var{dialect} Specify the default TLS dialect, for systems were there is a choice. For ARM targets, possible values for @var{dialect} are @code{gnu} or @code{gnu2}, which select between the original GNU dialect and the GNU TLS descriptor-based dialect. @item --enable-multiarch Specify whether to enable or disable multiarch support. The default is to check for glibc start files in a multiarch location, and enable it if the files are found. The auto detection is enabled for native builds, and for cross builds configured with @option{--with-sysroot}, and without @option{--with-native-system-header-dir}. More documentation about multiarch can be found at @uref{http://wiki.debian.org/Multiarch}. @item --disable-multilib Specify that multiple target libraries to support different target variants, calling conventions, etc.@: should not be built. The default is to build a predefined set of them. Some targets provide finer-grained control over which multilibs are built (e.g., @option{--disable-softfloat}): @table @code @item arm-*-* fpu, 26bit, underscore, interwork, biendian, nofmult. @item m68*-*-* softfloat, m68881, m68000, m68020. @item mips*-*-* single-float, biendian, softfloat. @item powerpc*-*-*, rs6000*-*-* aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian, sysv, aix. @end table @item --with-multilib-list=@var{list} @itemx --without-multilib-list Specify what multilibs to build. Currently only implemented for sh*-*-* and x86-64-*-linux*. @table @code @item sh*-*-* @var{list} is a comma separated list of CPU names. These must be of the form @code{sh*} or @code{m*} (in which case they match the compiler option for that processor). The list should not contain any endian options - these are handled by @option{--with-endian}. If @var{list} is empty, then there will be no multilibs for extra processors. The multilib for the secondary endian remains enabled. As a special case, if an entry in the list starts with a @code{!} (exclamation point), then it is added to the list of excluded multilibs. Entries of this sort should be compatible with @samp{MULTILIB_EXCLUDES} (once the leading @code{!} has been stripped). If @option{--with-multilib-list} is not given, then a default set of multilibs is selected based on the value of @option{--target}. This is usually the complete set of libraries, but some targets imply a more specialized subset. Example 1: to configure a compiler for SH4A only, but supporting both endians, with little endian being the default: @smallexample --with-cpu=sh4a --with-endian=little,big --with-multilib-list= @end smallexample Example 2: to configure a compiler for both SH4A and SH4AL-DSP, but with only little endian SH4AL: @smallexample --with-cpu=sh4a --with-endian=little,big \ --with-multilib-list=sh4al,!mb/m4al @end smallexample @item x86-64-*-linux* @var{list} is a comma separated list of @code{m32}, @code{m64} and @code{mx32} to enable 32-bit, 64-bit and x32 run-time libraries, respectively. If @var{list} is empty, then there will be no multilibs and only the default run-time library will be enabled. If @option{--with-multilib-list} is not given, then only 32-bit and 64-bit run-time libraries will be enabled. @end table @item --with-endian=@var{endians} Specify what endians to use. Currently only implemented for sh*-*-*. @var{endians} may be one of the following: @table @code @item big Use big endian exclusively. @item little Use little endian exclusively. @item big,little Use big endian by default. Provide a multilib for little endian. @item little,big Use little endian by default. Provide a multilib for big endian. @end table @item --enable-threads Specify that the target supports threads. This affects the Objective-C compiler and runtime library, and exception handling for other languages like C++ and Java. On some systems, this is the default. In general, the best (and, in many cases, the only known) threading model available will be configured for use. Beware that on some systems, GCC has not been taught what threading models are generally available for the system. In this case, @option{--enable-threads} is an alias for @option{--enable-threads=single}. @item --disable-threads Specify that threading support should be disabled for the system. This is an alias for @option{--enable-threads=single}. @item --enable-threads=@var{lib} Specify that @var{lib} is the thread support library. This affects the Objective-C compiler and runtime library, and exception handling for other languages like C++ and Java. The possibilities for @var{lib} are: @table @code @item aix AIX thread support. @item dce DCE thread support. @item lynx LynxOS thread support. @item mipssde MIPS SDE thread support. @item no This is an alias for @samp{single}. @item posix Generic POSIX/Unix98 thread support. @item rtems RTEMS thread support. @item single Disable thread support, should work for all platforms. @item tpf TPF thread support. @item vxworks VxWorks thread support. @item win32 Microsoft Win32 API thread support. @end table @item --enable-tls Specify that the target supports TLS (Thread Local Storage). Usually configure can correctly determine if TLS is supported. In cases where it guesses incorrectly, TLS can be explicitly enabled or disabled with @option{--enable-tls} or @option{--disable-tls}. This can happen if the assembler supports TLS but the C library does not, or if the assumptions made by the configure test are incorrect. @item --disable-tls Specify that the target does not support TLS. This is an alias for @option{--enable-tls=no}. @item --with-cpu=@var{cpu} @itemx --with-cpu-32=@var{cpu} @itemx --with-cpu-64=@var{cpu} Specify which cpu variant the compiler should generate code for by default. @var{cpu} will be used as the default value of the @option{-mcpu=} switch. This option is only supported on some targets, including ARM, i386, M68k, PowerPC, and SPARC@. The @option{--with-cpu-32} and @option{--with-cpu-64} options specify separate default CPUs for 32-bit and 64-bit modes; these options are only supported for i386, x86-64 and PowerPC. @item --with-schedule=@var{cpu} @itemx --with-arch=@var{cpu} @itemx --with-arch-32=@var{cpu} @itemx --with-arch-64=@var{cpu} @itemx --with-tune=@var{cpu} @itemx --with-tune-32=@var{cpu} @itemx --with-tune-64=@var{cpu} @itemx --with-abi=@var{abi} @itemx --with-fpu=@var{type} @itemx --with-float=@var{type} These configure options provide default values for the @option{-mschedule=}, @option{-march=}, @option{-mtune=}, @option{-mabi=}, and @option{-mfpu=} options and for @option{-mhard-float} or @option{-msoft-float}. As with @option{--with-cpu}, which switches will be accepted and acceptable values of the arguments depend on the target. @item --with-mode=@var{mode} Specify if the compiler should default to @option{-marm} or @option{-mthumb}. This option is only supported on ARM targets. @item --with-stack-offset=@var{num} This option sets the default for the -mstack-offset=@var{num} option, and will thus generally also control the setting of this option for libraries. This option is only supported on Epiphany targets. @item --with-fpmath=@var{isa} This options sets @option{-mfpmath=sse} by default and specifies the default ISA for floating-point arithmetics. You can select either @samp{sse} which enables @option{-msse2} or @samp{avx} which enables @option{-mavx} by default. This option is only supported on i386 and x86-64 targets. @item --with-divide=@var{type} Specify how the compiler should generate code for checking for division by zero. This option is only supported on the MIPS target. The possibilities for @var{type} are: @table @code @item traps Division by zero checks use conditional traps (this is the default on systems that support conditional traps). @item breaks Division by zero checks use the break instruction. @end table @c If you make --with-llsc the default for additional targets, @c update the --with-llsc description in the MIPS section below. @item --with-llsc On MIPS targets, make @option{-mllsc} the default when no @option{-mno-llsc} option is passed. This is the default for Linux-based targets, as the kernel will emulate them if the ISA does not provide them. @item --without-llsc On MIPS targets, make @option{-mno-llsc} the default when no @option{-mllsc} option is passed. @item --with-synci On MIPS targets, make @option{-msynci} the default when no @option{-mno-synci} option is passed. @item --without-synci On MIPS targets, make @option{-mno-synci} the default when no @option{-msynci} option is passed. This is the default. @item --with-mips-plt On MIPS targets, make use of copy relocations and PLTs. These features are extensions to the traditional SVR4-based MIPS ABIs and require support from GNU binutils and the runtime C library. @item --enable-__cxa_atexit Define if you want to use __cxa_atexit, rather than atexit, to register C++ destructors for local statics and global objects. This is essential for fully standards-compliant handling of destructors, but requires __cxa_atexit in libc. This option is currently only available on systems with GNU libc. When enabled, this will cause @option{-fuse-cxa-atexit} to be passed by default. @item --enable-gnu-indirect-function Define if you want to enable the @code{ifunc} attribute. This option is currently only available on systems with GNU libc on certain targets. @item --enable-target-optspace Specify that target libraries should be optimized for code space instead of code speed. This is the default for the m32r platform. @item --with-cpp-install-dir=@var{dirname} Specify that the user visible @command{cpp} program should be installed in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}. @item --enable-comdat Enable COMDAT group support. This is primarily used to override the automatically detected value. @item --enable-initfini-array Force the use of sections @code{.init_array} and @code{.fini_array} (instead of @code{.init} and @code{.fini}) for constructors and destructors. Option @option{--disable-initfini-array} has the opposite effect. If neither option is specified, the configure script will try to guess whether the @code{.init_array} and @code{.fini_array} sections are supported and, if they are, use them. @item --enable-maintainer-mode The build rules that regenerate the Autoconf and Automake output files as well as the GCC master message catalog @file{gcc.pot} are normally disabled. This is because it can only be rebuilt if the complete source tree is present. If you have changed the sources and want to rebuild the catalog, configuring with @option{--enable-maintainer-mode} will enable this. Note that you need a recent version of the @code{gettext} tools to do so. @item --disable-bootstrap For a native build, the default configuration is to perform a 3-stage bootstrap of the compiler when @samp{make} is invoked, testing that GCC can compile itself correctly. If you want to disable this process, you can configure with @option{--disable-bootstrap}. @item --enable-bootstrap In special cases, you may want to perform a 3-stage build even if the target and host triplets are different. This is possible when the host can run code compiled for the target (e.g.@: host is i686-linux, target is i486-linux). Starting from GCC 4.2, to do this you have to configure explicitly with @option{--enable-bootstrap}. @item --enable-generated-files-in-srcdir Neither the .c and .h files that are generated from Bison and flex nor the info manuals and man pages that are built from the .texi files are present in the SVN development tree. When building GCC from that development tree, or from one of our snapshots, those generated files are placed in your build directory, which allows for the source to be in a readonly directory. If you configure with @option{--enable-generated-files-in-srcdir} then those generated files will go into the source directory. This is mainly intended for generating release or prerelease tarballs of the GCC sources, since it is not a requirement that the users of source releases to have flex, Bison, or makeinfo. @item --enable-version-specific-runtime-libs Specify that runtime libraries should be installed in the compiler specific subdirectory (@file{@var{libdir}/gcc}) rather than the usual places. In addition, @samp{libstdc++}'s include files will be installed into @file{@var{libdir}} unless you overruled it by using @option{--with-gxx-include-dir=@var{dirname}}. Using this option is particularly useful if you intend to use several versions of GCC in parallel. This is currently supported by @samp{libgfortran}, @samp{libjava}, @samp{libmudflap}, @samp{libstdc++}, and @samp{libobjc}. @item --enable-languages=@var{lang1},@var{lang2},@dots{} Specify that only a particular subset of compilers and their runtime libraries should be built. For a list of valid values for @var{langN} you can issue the following command in the @file{gcc} directory of your GCC source tree:@* @smallexample grep language= */config-lang.in @end smallexample Currently, you can use any of the following: @code{all}, @code{ada}, @code{c}, @code{c++}, @code{fortran}, @code{go}, @code{java}, @code{objc}, @code{obj-c++}. Building the Ada compiler has special requirements, see below. If you do not pass this flag, or specify the option @code{all}, then all default languages available in the @file{gcc} sub-tree will be configured. Ada, Go and Objective-C++ are not default languages; the rest are. @item --enable-stage1-languages=@var{lang1},@var{lang2},@dots{} Specify that a particular subset of compilers and their runtime libraries should be built with the system C compiler during stage 1 of the bootstrap process, rather than only in later stages with the bootstrapped C compiler. The list of valid values is the same as for @option{--enable-languages}, and the option @code{all} will select all of the languages enabled by @option{--enable-languages}. This option is primarily useful for GCC development; for instance, when a development version of the compiler cannot bootstrap due to compiler bugs, or when one is debugging front ends other than the C front end. When this option is used, one can then build the target libraries for the specified languages with the stage-1 compiler by using @command{make stage1-bubble all-target}, or run the testsuite on the stage-1 compiler for the specified languages using @command{make stage1-start check-gcc}. @item --disable-libada Specify that the run-time libraries and tools used by GNAT should not be built. This can be useful for debugging, or for compatibility with previous Ada build procedures, when it was required to explicitly do a @samp{make -C gcc gnatlib_and_tools}. @item --disable-libssp Specify that the run-time libraries for stack smashing protection should not be built. @item --disable-libquadmath Specify that the GCC quad-precision math library should not be built. On some systems, the library is required to be linkable when building the Fortran front end, unless @option{--disable-libquadmath-support} is used. @item --disable-libquadmath-support Specify that the Fortran front end and @code{libgfortran} do not add support for @code{libquadmath} on systems supporting it. @item --disable-libgomp Specify that the run-time libraries used by GOMP should not be built. @item --with-dwarf2 Specify that the compiler should use DWARF 2 debugging information as the default. @item --enable-targets=all @itemx --enable-targets=@var{target_list} Some GCC targets, e.g.@: powerpc64-linux, build bi-arch compilers. These are compilers that are able to generate either 64-bit or 32-bit code. Typically, the corresponding 32-bit target, e.g.@: powerpc-linux for powerpc64-linux, only generates 32-bit code. This option enables the 32-bit target to be a bi-arch compiler, which is useful when you want a bi-arch compiler that defaults to 32-bit, and you are building a bi-arch or multi-arch binutils in a combined tree. On mips-linux, this will build a tri-arch compiler (ABI o32/n32/64), defaulted to o32. Currently, this option only affects sparc-linux, powerpc-linux, x86-linux, mips-linux and s390-linux. @item --enable-secureplt This option enables @option{-msecure-plt} by default for powerpc-linux. @ifnothtml @xref{RS/6000 and PowerPC Options,, RS/6000 and PowerPC Options, gcc, Using the GNU Compiler Collection (GCC)}, @end ifnothtml @ifhtml See ``RS/6000 and PowerPC Options'' in the main manual @end ifhtml @item --enable-cld This option enables @option{-mcld} by default for 32-bit x86 targets. @ifnothtml @xref{i386 and x86-64 Options,, i386 and x86-64 Options, gcc, Using the GNU Compiler Collection (GCC)}, @end ifnothtml @ifhtml See ``i386 and x86-64 Options'' in the main manual @end ifhtml @item --enable-win32-registry @itemx --enable-win32-registry=@var{key} @itemx --disable-win32-registry The @option{--enable-win32-registry} option enables Microsoft Windows-hosted GCC to look up installations paths in the registry using the following key: @smallexample @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}} @end smallexample @var{key} defaults to GCC version number, and can be overridden by the @option{--enable-win32-registry=@var{key}} option. Vendors and distributors who use custom installers are encouraged to provide a different key, perhaps one comprised of vendor name and GCC version number, to avoid conflict with existing installations. This feature is enabled by default, and can be disabled by @option{--disable-win32-registry} option. This option has no effect on the other hosts. @item --nfp Specify that the machine does not have a floating point unit. This option only applies to @samp{m68k-sun-sunos@var{n}}. On any other system, @option{--nfp} has no effect. @item --enable-werror @itemx --disable-werror @itemx --enable-werror=yes @itemx --enable-werror=no When you specify this option, it controls whether certain files in the compiler are built with @option{-Werror} in bootstrap stage2 and later. If you don't specify it, @option{-Werror} is turned on for the main development trunk. However it defaults to off for release branches and final releases. The specific files which get @option{-Werror} are controlled by the Makefiles. @item --enable-checking @itemx --enable-checking=@var{list} When you specify this option, the compiler is built to perform internal consistency checks of the requested complexity. This does not change the generated code, but adds error checking within the compiler. This will slow down the compiler and may only work properly if you are building the compiler with GCC@. This is @samp{yes} by default when building from SVN or snapshots, but @samp{release} for releases. The default for building the stage1 compiler is @samp{yes}. More control over the checks may be had by specifying @var{list}. The categories of checks available are @samp{yes} (most common checks @samp{assert,misc,tree,gc,rtlflag,runtime}), @samp{no} (no checks at all), @samp{all} (all but @samp{valgrind}), @samp{release} (cheapest checks @samp{assert,runtime}) or @samp{none} (same as @samp{no}). Individual checks can be enabled with these flags @samp{assert}, @samp{df}, @samp{fold}, @samp{gc}, @samp{gcac} @samp{misc}, @samp{rtl}, @samp{rtlflag}, @samp{runtime}, @samp{tree}, and @samp{valgrind}. The @samp{valgrind} check requires the external @command{valgrind} simulator, available from @uref{http://valgrind.org/}. The @samp{df}, @samp{rtl}, @samp{gcac} and @samp{valgrind} checks are very expensive. To disable all checking, @samp{--disable-checking} or @samp{--enable-checking=none} must be explicitly requested. Disabling assertions will make the compiler and runtime slightly faster but increase the risk of undetected internal errors causing wrong code to be generated. @item --disable-stage1-checking @itemx --enable-stage1-checking @itemx --enable-stage1-checking=@var{list} If no @option{--enable-checking} option is specified the stage1 compiler will be built with @samp{yes} checking enabled, otherwise the stage1 checking flags are the same as specified by @option{--enable-checking}. To build the stage1 compiler with different checking options use @option{--enable-stage1-checking}. The list of checking options is the same as for @option{--enable-checking}. If your system is too slow or too small to bootstrap a released compiler with checking for stage1 enabled, you can use @samp{--disable-stage1-checking} to disable checking for the stage1 compiler. @item --enable-coverage @itemx --enable-coverage=@var{level} With this option, the compiler is built to collect self coverage information, every time it is run. This is for internal development purposes, and only works when the compiler is being built with gcc. The @var{level} argument controls whether the compiler is built optimized or not, values are @samp{opt} and @samp{noopt}. For coverage analysis you want to disable optimization, for performance analysis you want to enable optimization. When coverage is enabled, the default level is without optimization. @item --enable-gather-detailed-mem-stats When this option is specified more detailed information on memory allocation is gathered. This information is printed when using @option{-fmem-report}. @item --enable-nls @itemx --disable-nls The @option{--enable-nls} option enables Native Language Support (NLS), which lets GCC output diagnostics in languages other than American English. Native Language Support is enabled by default if not doing a canadian cross build. The @option{--disable-nls} option disables NLS@. @item --with-included-gettext If NLS is enabled, the @option{--with-included-gettext} option causes the build procedure to prefer its copy of GNU @command{gettext}. @item --with-catgets If NLS is enabled, and if the host lacks @code{gettext} but has the inferior @code{catgets} interface, the GCC build procedure normally ignores @code{catgets} and instead uses GCC's copy of the GNU @code{gettext} library. The @option{--with-catgets} option causes the build procedure to use the host's @code{catgets} in this situation. @item --with-libiconv-prefix=@var{dir} Search for libiconv header files in @file{@var{dir}/include} and libiconv library files in @file{@var{dir}/lib}. @item --enable-obsolete Enable configuration for an obsoleted system. If you attempt to configure GCC for a system (build, host, or target) which has been obsoleted, and you do not specify this flag, configure will halt with an error message. All support for systems which have been obsoleted in one release of GCC is removed entirely in the next major release, unless someone steps forward to maintain the port. @item --enable-decimal-float @itemx --enable-decimal-float=yes @itemx --enable-decimal-float=no @itemx --enable-decimal-float=bid @itemx --enable-decimal-float=dpd @itemx --disable-decimal-float Enable (or disable) support for the C decimal floating point extension that is in the IEEE 754-2008 standard. This is enabled by default only on PowerPC, i386, and x86_64 GNU/Linux systems. Other systems may also support it, but require the user to specifically enable it. You can optionally control which decimal floating point format is used (either @samp{bid} or @samp{dpd}). The @samp{bid} (binary integer decimal) format is default on i386 and x86_64 systems, and the @samp{dpd} (densely packed decimal) format is default on PowerPC systems. @item --enable-fixed-point @itemx --disable-fixed-point Enable (or disable) support for C fixed-point arithmetic. This option is enabled by default for some targets (such as MIPS) which have hardware-support for fixed-point operations. On other targets, you may enable this option manually. @item --with-long-double-128 Specify if @code{long double} type should be 128-bit by default on selected GNU/Linux architectures. If using @code{--without-long-double-128}, @code{long double} will be by default 64-bit, the same as @code{double} type. When neither of these configure options are used, the default will be 128-bit @code{long double} when built against GNU C Library 2.4 and later, 64-bit @code{long double} otherwise. @item --with-gmp=@var{pathname} @itemx --with-gmp-include=@var{pathname} @itemx --with-gmp-lib=@var{pathname} @itemx --with-mpfr=@var{pathname} @itemx --with-mpfr-include=@var{pathname} @itemx --with-mpfr-lib=@var{pathname} @itemx --with-mpc=@var{pathname} @itemx --with-mpc-include=@var{pathname} @itemx --with-mpc-lib=@var{pathname} If you want to build GCC but do not have the GMP library, the MPFR library and/or the MPC library installed in a standard location and do not have their sources present in the GCC source tree then you can explicitly specify the directory where they are installed (@samp{--with-gmp=@var{gmpinstalldir}}, @samp{--with-mpfr=@/@var{mpfrinstalldir}}, @samp{--with-mpc=@/@var{mpcinstalldir}}). The @option{--with-gmp=@/@var{gmpinstalldir}} option is shorthand for @option{--with-gmp-lib=@/@var{gmpinstalldir}/lib} and @option{--with-gmp-include=@/@var{gmpinstalldir}/include}. Likewise the @option{--with-mpfr=@/@var{mpfrinstalldir}} option is shorthand for @option{--with-mpfr-lib=@/@var{mpfrinstalldir}/lib} and @option{--with-mpfr-include=@/@var{mpfrinstalldir}/include}, also the @option{--with-mpc=@/@var{mpcinstalldir}} option is shorthand for @option{--with-mpc-lib=@/@var{mpcinstalldir}/lib} and @option{--with-mpc-include=@/@var{mpcinstalldir}/include}. If these shorthand assumptions are not correct, you can use the explicit include and lib options directly. You might also need to ensure the shared libraries can be found by the dynamic linker when building and using GCC, for example by setting the runtime shared library path variable (@env{LD_LIBRARY_PATH} on GNU/Linux and Solaris systems). These flags are applicable to the host platform only. When building a cross compiler, they will not be used to configure target libraries. @item --with-isl=@var{pathname} @itemx --with-isl-include=@var{pathname} @itemx --with-isl-lib=@var{pathname} @itemx --with-cloog=@var{pathname} @itemx --with-cloog-include=@var{pathname} @itemx --with-cloog-lib=@var{pathname} If you do not have ISL and the CLooG libraries installed in a standard location and you want to build GCC, you can explicitly specify the directory where they are installed (@samp{--with-isl=@/@var{islinstalldir}}, @samp{--with-cloog=@/@var{clooginstalldir}}). The @option{--with-isl=@/@var{islinstalldir}} option is shorthand for @option{--with-isl-lib=@/@var{islinstalldir}/lib} and @option{--with-isl-include=@/@var{islinstalldir}/include}. Likewise the @option{--with-cloog=@/@var{clooginstalldir}} option is shorthand for @option{--with-cloog-lib=@/@var{clooginstalldir}/lib} and @option{--with-cloog-include=@/@var{clooginstalldir}/include}. If these shorthand assumptions are not correct, you can use the explicit include and lib options directly. These flags are applicable to the host platform only. When building a cross compiler, they will not be used to configure target libraries. @item --with-host-libstdcxx=@var{linker-args} If you are linking with a static copy of PPL, you can use this option to specify how the linker should find the standard C++ library used internally by PPL. Typical values of @var{linker-args} might be @samp{-lstdc++} or @samp{-Wl,-Bstatic,-lstdc++,-Bdynamic -lm}. If you are linking with a shared copy of PPL, you probably do not need this option; shared library dependencies will cause the linker to search for the standard C++ library automatically. @item --with-stage1-ldflags=@var{flags} This option may be used to set linker flags to be used when linking stage 1 of GCC. These are also used when linking GCC if configured with @option{--disable-bootstrap}. By default no special flags are used. @item --with-stage1-libs=@var{libs} This option may be used to set libraries to be used when linking stage 1 of GCC. These are also used when linking GCC if configured with @option{--disable-bootstrap}. The default is the argument to @option{--with-host-libstdcxx}, if specified. @item --with-boot-ldflags=@var{flags} This option may be used to set linker flags to be used when linking stage 2 and later when bootstrapping GCC. If neither --with-boot-libs nor --with-host-libstdcxx is set to a value, then the default is @samp{-static-libstdc++ -static-libgcc}. @item --with-boot-libs=@var{libs} This option may be used to set libraries to be used when linking stage 2 and later when bootstrapping GCC. The default is the argument to @option{--with-host-libstdcxx}, if specified. @item --with-debug-prefix-map=@var{map} Convert source directory names using @option{-fdebug-prefix-map} when building runtime libraries. @samp{@var{map}} is a space-separated list of maps of the form @samp{@var{old}=@var{new}}. @item --enable-linker-build-id Tells GCC to pass @option{--build-id} option to the linker for all final links (links performed without the @option{-r} or @option{--relocatable} option), if the linker supports it. If you specify @option{--enable-linker-build-id}, but your linker does not support @option{--build-id} option, a warning is issued and the @option{--enable-linker-build-id} option is ignored. The default is off. @item --with-linker-hash-style=@var{choice} Tells GCC to pass @option{--hash-style=@var{choice}} option to the linker for all final links. @var{choice} can be one of @samp{sysv}, @samp{gnu}, and @samp{both} where @samp{sysv} is the default. @item --enable-gnu-unique-object @itemx --disable-gnu-unique-object Tells GCC to use the gnu_unique_object relocation for C++ template static data members and inline function local statics. Enabled by default for a native toolchain with an assembler that accepts it and GLIBC 2.11 or above, otherwise disabled. @item --enable-lto @itemx --disable-lto Enable support for link-time optimization (LTO). This is enabled by default, and may be disabled using @option{--disable-lto}. @item --with-plugin-ld=@var{pathname} Enable an alternate linker to be used at link-time optimization (LTO) link time when @option{-fuse-linker-plugin} is enabled. This linker should have plugin support such as gold starting with version 2.20 or GNU ld starting with version 2.21. See @option{-fuse-linker-plugin} for details. @item --enable-canonical-system-headers @itemx --disable-canonical-system-headers Enable system header path canonicalization for @file{libcpp}. This can produce shorter header file paths in diagnostics and dependency output files, but these changed header paths may conflict with some compilation environments. Enabled by default, and may be disabled using @option{--disable-canonical-system-headers}. @end table @subheading Cross-Compiler-Specific Options The following options only apply to building cross compilers. @table @code @item --with-sysroot @itemx --with-sysroot=@var{dir} Tells GCC to consider @var{dir} as the root of a tree that contains (a subset of) the root filesystem of the target operating system. Target system headers, libraries and run-time object files will be searched for in there. More specifically, this acts as if @option{--sysroot=@var{dir}} was added to the default options of the built compiler. The specified directory is not copied into the install tree, unlike the options @option{--with-headers} and @option{--with-libs} that this option obsoletes. The default value, in case @option{--with-sysroot} is not given an argument, is @option{$@{gcc_tooldir@}/sys-root}. If the specified directory is a subdirectory of @option{$@{exec_prefix@}}, then it will be found relative to the GCC binaries if the installation tree is moved. This option affects the system root for the compiler used to build target libraries (which runs on the build system) and the compiler newly installed with @code{make install}; it does not affect the compiler which is used to build GCC itself. If you specify the @option{--with-native-system-header-dir=@var{dirname}} option then the compiler will search that directory within @var{dirname} for native system headers rather than the default @file{/usr/include}. @item --with-build-sysroot @itemx --with-build-sysroot=@var{dir} Tells GCC to consider @var{dir} as the system root (see @option{--with-sysroot}) while building target libraries, instead of the directory specified with @option{--with-sysroot}. This option is only useful when you are already using @option{--with-sysroot}. You can use @option{--with-build-sysroot} when you are configuring with @option{--prefix} set to a directory that is different from the one in which you are installing GCC and your target libraries. This option affects the system root for the compiler used to build target libraries (which runs on the build system); it does not affect the compiler which is used to build GCC itself. If you specify the @option{--with-native-system-header-dir=@var{dirname}} option then the compiler will search that directory within @var{dirname} for native system headers rather than the default @file{/usr/include}. @item --with-headers @itemx --with-headers=@var{dir} Deprecated in favor of @option{--with-sysroot}. Specifies that target headers are available when building a cross compiler. The @var{dir} argument specifies a directory which has the target include files. These include files will be copied into the @file{gcc} install directory. @emph{This option with the @var{dir} argument is required} when building a cross compiler, if @file{@var{prefix}/@var{target}/sys-include} doesn't pre-exist. If @file{@var{prefix}/@var{target}/sys-include} does pre-exist, the @var{dir} argument may be omitted. @command{fixincludes} will be run on these files to make them compatible with GCC@. @item --without-headers Tells GCC not use any target headers from a libc when building a cross compiler. When crossing to GNU/Linux, you need the headers so GCC can build the exception handling for libgcc. @item --with-libs @itemx --with-libs="@var{dir1} @var{dir2} @dots{} @var{dirN}" Deprecated in favor of @option{--with-sysroot}. Specifies a list of directories which contain the target runtime libraries. These libraries will be copied into the @file{gcc} install directory. If the directory list is omitted, this option has no effect. @item --with-newlib Specifies that @samp{newlib} is being used as the target C library. This causes @code{__eprintf} to be omitted from @file{libgcc.a} on the assumption that it will be provided by @samp{newlib}. @item --with-avrlibc Specifies that @samp{AVR-Libc} is being used as the target C library. This causes float support functions like @code{__addsf3} to be omitted from @file{libgcc.a} on the assumption that it will be provided by @file{libm.a}. For more technical details, cf. @uref{http://gcc.gnu.org/PR54461,,PR54461}. This option is only supported for the AVR target. It is not supported for RTEMS configurations, which currently use newlib. The option is supported since version 4.7.2 and is the default in 4.8.0 and newer. @item --with-build-time-tools=@var{dir} Specifies where to find the set of target tools (assembler, linker, etc.) that will be used while building GCC itself. This option can be useful if the directory layouts are different between the system you are building GCC on, and the system where you will deploy it. For example, on an @samp{ia64-hp-hpux} system, you may have the GNU assembler and linker in @file{/usr/bin}, and the native tools in a different path, and build a toolchain that expects to find the native tools in @file{/usr/bin}. When you use this option, you should ensure that @var{dir} includes @command{ar}, @command{as}, @command{ld}, @command{nm}, @command{ranlib} and @command{strip} if necessary, and possibly @command{objdump}. Otherwise, GCC may use an inconsistent set of tools. @end table @subheading Java-Specific Options The following option applies to the build of the Java front end. @table @code @item --disable-libgcj Specify that the run-time libraries used by GCJ should not be built. This is useful in case you intend to use GCJ with some other run-time, or you're going to install it separately, or it just happens not to build on your particular machine. In general, if the Java front end is enabled, the GCJ libraries will be enabled too, unless they're known to not work on the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you may need to port it; in this case, before modifying the top-level @file{configure.in} so that @samp{libgcj} is enabled by default on this platform, you may use @option{--enable-libgcj} to override the default. @end table The following options apply to building @samp{libgcj}. @subsubheading General Options @table @code @item --enable-java-maintainer-mode By default the @samp{libjava} build will not attempt to compile the @file{.java} source files to @file{.class}. Instead, it will use the @file{.class} files from the source tree. If you use this option you must have executables named @command{ecj1} and @command{gjavah} in your path for use by the build. You must use this option if you intend to modify any @file{.java} files in @file{libjava}. @item --with-java-home=@var{dirname} This @samp{libjava} option overrides the default value of the @samp{java.home} system property. It is also used to set @samp{sun.boot.class.path} to @file{@var{dirname}/lib/rt.jar}. By default @samp{java.home} is set to @file{@var{prefix}} and @samp{sun.boot.class.path} to @file{@var{datadir}/java/libgcj-@var{version}.jar}. @item --with-ecj-jar=@var{filename} This option can be used to specify the location of an external jar file containing the Eclipse Java compiler. A specially modified version of this compiler is used by @command{gcj} to parse @file{.java} source files. If this option is given, the @samp{libjava} build will create and install an @file{ecj1} executable which uses this jar file at runtime. If this option is not given, but an @file{ecj.jar} file is found in the topmost source tree at configure time, then the @samp{libgcj} build will create and install @file{ecj1}, and will also install the discovered @file{ecj.jar} into a suitable place in the install tree. If @file{ecj1} is not installed, then the user will have to supply one on his path in order for @command{gcj} to properly parse @file{.java} source files. A suitable jar is available from @uref{ftp://sourceware.org/pub/java/}. @item --disable-getenv-properties Don't set system properties from @env{GCJ_PROPERTIES}. @item --enable-hash-synchronization Use a global hash table for monitor locks. Ordinarily, @samp{libgcj}'s @samp{configure} script automatically makes the correct choice for this option for your platform. Only use this if you know you need the library to be configured differently. @item --enable-interpreter Enable the Java interpreter. The interpreter is automatically enabled by default on all platforms that support it. This option is really only useful if you want to disable the interpreter (using @option{--disable-interpreter}). @item --disable-java-net Disable java.net. This disables the native part of java.net only, using non-functional stubs for native method implementations. @item --disable-jvmpi Disable JVMPI support. @item --disable-libgcj-bc Disable BC ABI compilation of certain parts of libgcj. By default, some portions of libgcj are compiled with @option{-findirect-dispatch} and @option{-fno-indirect-classes}, allowing them to be overridden at run-time. If @option{--disable-libgcj-bc} is specified, libgcj is built without these options. This allows the compile-time linker to resolve dependencies when statically linking to libgcj. However it makes it impossible to override the affected portions of libgcj at run-time. @item --enable-reduced-reflection Build most of libgcj with @option{-freduced-reflection}. This reduces the size of libgcj at the expense of not being able to do accurate reflection on the classes it contains. This option is safe if you know that code using libgcj will never use reflection on the standard runtime classes in libgcj (including using serialization, RMI or CORBA). @item --with-ecos Enable runtime eCos target support. @item --without-libffi Don't use @samp{libffi}. This will disable the interpreter and JNI support as well, as these require @samp{libffi} to work. @item --enable-libgcj-debug Enable runtime debugging code. @item --enable-libgcj-multifile If specified, causes all @file{.java} source files to be compiled into @file{.class} files in one invocation of @samp{gcj}. This can speed up build time, but is more resource-intensive. If this option is unspecified or disabled, @samp{gcj} is invoked once for each @file{.java} file to compile into a @file{.class} file. @item --with-libiconv-prefix=DIR Search for libiconv in @file{DIR/include} and @file{DIR/lib}. @item --enable-sjlj-exceptions Force use of the @code{setjmp}/@code{longjmp}-based scheme for exceptions. @samp{configure} ordinarily picks the correct value based on the platform. Only use this option if you are sure you need a different setting. @item --with-system-zlib Use installed @samp{zlib} rather than that included with GCC@. @item --with-win32-nlsapi=ansi, unicows or unicode Indicates how MinGW @samp{libgcj} translates between UNICODE characters and the Win32 API@. @item --enable-java-home If enabled, this creates a JPackage compatible SDK environment during install. Note that if --enable-java-home is used, --with-arch-directory=ARCH must also be specified. @item --with-arch-directory=ARCH Specifies the name to use for the @file{jre/lib/ARCH} directory in the SDK environment created when --enable-java-home is passed. Typical names for this directory include i386, amd64, ia64, etc. @item --with-os-directory=DIR Specifies the OS directory for the SDK include directory. This is set to auto detect, and is typically 'linux'. @item --with-origin-name=NAME Specifies the JPackage origin name. This defaults to the 'gcj' in java-1.5.0-gcj. @item --with-arch-suffix=SUFFIX Specifies the suffix for the sdk directory. Defaults to the empty string. Examples include '.x86_64' in 'java-1.5.0-gcj-1.5.0.0.x86_64'. @item --with-jvm-root-dir=DIR Specifies where to install the SDK. Default is $(prefix)/lib/jvm. @item --with-jvm-jar-dir=DIR Specifies where to install jars. Default is $(prefix)/lib/jvm-exports. @item --with-python-dir=DIR Specifies where to install the Python modules used for aot-compile. DIR should not include the prefix used in installation. For example, if the Python modules are to be installed in /usr/lib/python2.5/site-packages, then --with-python-dir=/lib/python2.5/site-packages should be passed. If this is not specified, then the Python modules are installed in $(prefix)/share/python. @item --enable-aot-compile-rpm Adds aot-compile-rpm to the list of installed scripts. @item --enable-browser-plugin Build the gcjwebplugin web browser plugin. @item --enable-static-libjava Build static libraries in libjava. The default is to only build shared libraries. @table @code @item ansi Use the single-byte @code{char} and the Win32 A functions natively, translating to and from UNICODE when using these functions. If unspecified, this is the default. @item unicows Use the @code{WCHAR} and Win32 W functions natively. Adds @code{-lunicows} to @file{libgcj.spec} to link with @samp{libunicows}. @file{unicows.dll} needs to be deployed on Microsoft Windows 9X machines running built executables. @file{libunicows.a}, an open-source import library around Microsoft's @code{unicows.dll}, is obtained from @uref{http://libunicows.sourceforge.net/}, which also gives details on getting @file{unicows.dll} from Microsoft. @item unicode Use the @code{WCHAR} and Win32 W functions natively. Does @emph{not} add @code{-lunicows} to @file{libgcj.spec}. The built executables will only run on Microsoft Windows NT and above. @end table @end table @subsubheading AWT-Specific Options @table @code @item --with-x Use the X Window System. @item --enable-java-awt=PEER(S) Specifies the AWT peer library or libraries to build alongside @samp{libgcj}. If this option is unspecified or disabled, AWT will be non-functional. Current valid values are @option{gtk} and @option{xlib}. Multiple libraries should be separated by a comma (i.e.@: @option{--enable-java-awt=gtk,xlib}). @item --enable-gtk-cairo Build the cairo Graphics2D implementation on GTK@. @item --enable-java-gc=TYPE Choose garbage collector. Defaults to @option{boehm} if unspecified. @item --disable-gtktest Do not try to compile and run a test GTK+ program. @item --disable-glibtest Do not try to compile and run a test GLIB program. @item --with-libart-prefix=PFX Prefix where libart is installed (optional). @item --with-libart-exec-prefix=PFX Exec prefix where libart is installed (optional). @item --disable-libarttest Do not try to compile and run a test libart program. @end table @subsubheading Overriding @command{configure} test results Sometimes, it might be necessary to override the result of some @command{configure} test, for example in order to ease porting to a new system or work around a bug in a test. The toplevel @command{configure} script provides three variables for this: @table @code @item build_configargs @cindex @code{build_configargs} The contents of this variable is passed to all build @command{configure} scripts. @item host_configargs @cindex @code{host_configargs} The contents of this variable is passed to all host @command{configure} scripts. @item target_configargs @cindex @code{target_configargs} The contents of this variable is passed to all target @command{configure} scripts. @end table In order to avoid shell and @command{make} quoting issues for complex overrides, you can pass a setting for @env{CONFIG_SITE} and set variables in the site file. @html
@end html @ifhtml @uref{./index.html,,Return to the GCC Installation page} @end ifhtml @end ifset @c ***Building**************************************************************** @ifnothtml @comment node-name, next, previous, up @node Building, Testing, Configuration, Installing GCC @end ifnothtml @ifset buildhtml @ifnothtml @chapter Building @end ifnothtml @cindex Installing GCC: Building Now that GCC is configured, you are ready to build the compiler and runtime libraries. Some commands executed when making the compiler may fail (return a nonzero status) and be ignored by @command{make}. These failures, which are often due to files that were not found, are expected, and can safely be ignored. It is normal to have compiler warnings when compiling certain files. Unless you are a GCC developer, you can generally ignore these warnings unless they cause compilation to fail. Developers should attempt to fix any warnings encountered, however they can temporarily continue past warnings-as-errors by specifying the configure flag @option{--disable-werror}. On certain old systems, defining certain environment variables such as @env{CC} can interfere with the functioning of @command{make}. If you encounter seemingly strange errors when trying to build the compiler in a directory other than the source directory, it could be because you have previously configured the compiler in the source directory. Make sure you have done all the necessary preparations. If you build GCC on a BSD system using a directory stored in an old System V file system, problems may occur in running @command{fixincludes} if the System V file system doesn't support symbolic links. These problems result in a failure to fix the declaration of @code{size_t} in @file{sys/types.h}. If you find that @code{size_t} is a signed type and that type mismatches occur, this could be the cause. The solution is not to use such a directory for building GCC@. Similarly, when building from SVN or snapshots, or if you modify @file{*.l} files, you need the Flex lexical analyzer generator installed. If you do not modify @file{*.l} files, releases contain the Flex-generated files and you do not need Flex installed to build them. There is still one Flex-based lexical analyzer (part of the build machinery, not of GCC itself) that is used even if you only build the C front end. When building from SVN or snapshots, or if you modify Texinfo documentation, you need version 4.7 or later of Texinfo installed if you want Info documentation to be regenerated. Releases contain Info documentation pre-built for the unmodified documentation in the release. @section Building a native compiler For a native build, the default configuration is to perform a 3-stage bootstrap of the compiler when @samp{make} is invoked. This will build the entire GCC system and ensure that it compiles itself correctly. It can be disabled with the @option{--disable-bootstrap} parameter to @samp{configure}, but bootstrapping is suggested because the compiler will be tested more completely and could also have better performance. The bootstrapping process will complete the following steps: @itemize @bullet @item Build tools necessary to build the compiler. @item Perform a 3-stage bootstrap of the compiler. This includes building three times the target tools for use by the compiler such as binutils (bfd, binutils, gas, gprof, ld, and opcodes) if they have been individually linked or moved into the top level GCC source tree before configuring. @item Perform a comparison test of the stage2 and stage3 compilers. @item Build runtime libraries using the stage3 compiler from the previous step. @end itemize If you are short on disk space you might consider @samp{make bootstrap-lean} instead. The sequence of compilation is the same described above, but object files from the stage1 and stage2 of the 3-stage bootstrap of the compiler are deleted as soon as they are no longer needed. If you wish to use non-default GCC flags when compiling the stage2 and stage3 compilers, set @code{BOOT_CFLAGS} on the command line when doing @samp{make}. For example, if you want to save additional space during the bootstrap and in the final installation as well, you can build the compiler binaries without debugging information as in the following example. This will save roughly 40% of disk space both for the bootstrap and the final installation. (Libraries will still contain debugging information.) @smallexample make BOOT_CFLAGS='-O' bootstrap @end smallexample You can place non-default optimization flags into @code{BOOT_CFLAGS}; they are less well tested here than the default of @samp{-g -O2}, but should still work. In a few cases, you may find that you need to specify special flags such as @option{-msoft-float} here to complete the bootstrap; or, if the native compiler miscompiles the stage1 compiler, you may need to work around this, by choosing @code{BOOT_CFLAGS} to avoid the parts of the stage1 compiler that were miscompiled, or by using @samp{make bootstrap4} to increase the number of stages of bootstrap. @code{BOOT_CFLAGS} does not apply to bootstrapped target libraries. Since these are always compiled with the compiler currently being bootstrapped, you can use @code{CFLAGS_FOR_TARGET} to modify their compilation flags, as for non-bootstrapped target libraries. Again, if the native compiler miscompiles the stage1 compiler, you may need to work around this by avoiding non-working parts of the stage1 compiler. Use @code{STAGE1_TFLAGS} to this end. If you used the flag @option{--enable-languages=@dots{}} to restrict the compilers to be built, only those you've actually enabled will be built. This will of course only build those runtime libraries, for which the particular compiler has been built. Please note, that re-defining @env{LANGUAGES} when calling @samp{make} @strong{does not} work anymore! If the comparison of stage2 and stage3 fails, this normally indicates that the stage2 compiler has compiled GCC incorrectly, and is therefore a potentially serious bug which you should investigate and report. (On a few systems, meaningful comparison of object files is impossible; they always appear ``different''. If you encounter this problem, you will need to disable comparison in the @file{Makefile}.) If you do not want to bootstrap your compiler, you can configure with @option{--disable-bootstrap}. In particular cases, you may want to bootstrap your compiler even if the target system is not the same as the one you are building on: for example, you could build a @code{powerpc-unknown-linux-gnu} toolchain on a @code{powerpc64-unknown-linux-gnu} host. In this case, pass @option{--enable-bootstrap} to the configure script. @code{BUILD_CONFIG} can be used to bring in additional customization to the build. It can be set to a whitespace-separated list of names. For each such @code{NAME}, top-level @file{config/@code{NAME}.mk} will be included by the top-level @file{Makefile}, bringing in any settings it contains. The default @code{BUILD_CONFIG} can be set using the configure option @option{--with-build-config=@code{NAME}...}. Some examples of supported build configurations are: @table @asis @item @samp{bootstrap-O1} Removes any @option{-O}-started option from @code{BOOT_CFLAGS}, and adds @option{-O1} to it. @samp{BUILD_CONFIG=bootstrap-O1} is equivalent to @samp{BOOT_CFLAGS='-g -O1'}. @item @samp{bootstrap-O3} Analogous to @code{bootstrap-O1}. @item @samp{bootstrap-lto} Enables Link-Time Optimization for host tools during bootstrapping. @samp{BUILD_CONFIG=bootstrap-lto} is equivalent to adding @option{-flto} to @samp{BOOT_CFLAGS}. @item @samp{bootstrap-debug} Verifies that the compiler generates the same executable code, whether or not it is asked to emit debug information. To this end, this option builds stage2 host programs without debug information, and uses @file{contrib/compare-debug} to compare them with the stripped stage3 object files. If @code{BOOT_CFLAGS} is overridden so as to not enable debug information, stage2 will have it, and stage3 won't. This option is enabled by default when GCC bootstrapping is enabled, if @code{strip} can turn object files compiled with and without debug info into identical object files. In addition to better test coverage, this option makes default bootstraps faster and leaner. @item @samp{bootstrap-debug-big} Rather than comparing stripped object files, as in @code{bootstrap-debug}, this option saves internal compiler dumps during stage2 and stage3 and compares them as well, which helps catch additional potential problems, but at a great cost in terms of disk space. It can be specified in addition to @samp{bootstrap-debug}. @item @samp{bootstrap-debug-lean} This option saves disk space compared with @code{bootstrap-debug-big}, but at the expense of some recompilation. Instead of saving the dumps of stage2 and stage3 until the final compare, it uses @option{-fcompare-debug} to generate, compare and remove the dumps during stage3, repeating the compilation that already took place in stage2, whose dumps were not saved. @item @samp{bootstrap-debug-lib} This option tests executable code invariance over debug information generation on target libraries, just like @code{bootstrap-debug-lean} tests it on host programs. It builds stage3 libraries with @option{-fcompare-debug}, and it can be used along with any of the @code{bootstrap-debug} options above. There aren't @code{-lean} or @code{-big} counterparts to this option because most libraries are only build in stage3, so bootstrap compares would not get significant coverage. Moreover, the few libraries built in stage2 are used in stage3 host programs, so we wouldn't want to compile stage2 libraries with different options for comparison purposes. @item @samp{bootstrap-debug-ckovw} Arranges for error messages to be issued if the compiler built on any stage is run without the option @option{-fcompare-debug}. This is useful to verify the full @option{-fcompare-debug} testing coverage. It must be used along with @code{bootstrap-debug-lean} and @code{bootstrap-debug-lib}. @item @samp{bootstrap-time} Arranges for the run time of each program started by the GCC driver, built in any stage, to be logged to @file{time.log}, in the top level of the build tree. @end table @section Building a cross compiler When building a cross compiler, it is not generally possible to do a 3-stage bootstrap of the compiler. This makes for an interesting problem as parts of GCC can only be built with GCC@. To build a cross compiler, we recommend first building and installing a native compiler. You can then use the native GCC compiler to build the cross compiler. The installed native compiler needs to be GCC version 2.95 or later. If the cross compiler is to be built with support for the Java programming language and the ability to compile .java source files is desired, the installed native compiler used to build the cross compiler needs to be the same GCC version as the cross compiler. In addition the cross compiler needs to be configured with @option{--with-ecj-jar=@dots{}}. Assuming you have already installed a native copy of GCC and configured your cross compiler, issue the command @command{make}, which performs the following steps: @itemize @bullet @item Build host tools necessary to build the compiler. @item Build target tools for use by the compiler such as binutils (bfd, binutils, gas, gprof, ld, and opcodes) if they have been individually linked or moved into the top level GCC source tree before configuring. @item Build the compiler (single stage only). @item Build runtime libraries using the compiler from the previous step. @end itemize Note that if an error occurs in any step the make process will exit. If you are not building GNU binutils in the same source tree as GCC, you will need a cross-assembler and cross-linker installed before configuring GCC@. Put them in the directory @file{@var{prefix}/@var{target}/bin}. Here is a table of the tools you should put in this directory: @table @file @item as This should be the cross-assembler. @item ld This should be the cross-linker. @item ar This should be the cross-archiver: a program which can manipulate archive files (linker libraries) in the target machine's format. @item ranlib This should be a program to construct a symbol table in an archive file. @end table The installation of GCC will find these programs in that directory, and copy or link them to the proper place to for the cross-compiler to find them when run later. The easiest way to provide these files is to build the Binutils package. Configure it with the same @option{--host} and @option{--target} options that you use for configuring GCC, then build and install them. They install their executables automatically into the proper directory. Alas, they do not support all the targets that GCC supports. If you are not building a C library in the same source tree as GCC, you should also provide the target libraries and headers before configuring GCC, specifying the directories with @option{--with-sysroot} or @option{--with-headers} and @option{--with-libs}. Many targets also require ``start files'' such as @file{crt0.o} and @file{crtn.o} which are linked into each executable. There may be several alternatives for @file{crt0.o}, for use with profiling or other compilation options. Check your target's definition of @code{STARTFILE_SPEC} to find out what start files it uses. @section Building in parallel GNU Make 3.80 and above, which is necessary to build GCC, support building in parallel. To activate this, you can use @samp{make -j 2} instead of @samp{make}. You can also specify a bigger number, and in most cases using a value greater than the number of processors in your machine will result in fewer and shorter I/O latency hits, thus improving overall throughput; this is especially true for slow drives and network filesystems. @section Building the Ada compiler In order to build GNAT, the Ada compiler, you need a working GNAT compiler (GCC version 4.0 or later). This includes GNAT tools such as @command{gnatmake} and @command{gnatlink}, since the Ada front end is written in Ada and uses some GNAT-specific extensions. In order to build a cross compiler, it is suggested to install the new compiler as native first, and then use it to build the cross compiler. @command{configure} does not test whether the GNAT installation works and has a sufficiently recent version; if too old a GNAT version is installed, the build will fail unless @option{--enable-languages} is used to disable building the Ada front end. @env{ADA_INCLUDE_PATH} and @env{ADA_OBJECT_PATH} environment variables must not be set when building the Ada compiler, the Ada tools, or the Ada runtime libraries. You can check that your build environment is clean by verifying that @samp{gnatls -v} lists only one explicit path in each section. @section Building with profile feedback It is possible to use profile feedback to optimize the compiler itself. This should result in a faster compiler binary. Experiments done on x86 using gcc 3.3 showed approximately 7 percent speedup on compiling C programs. To bootstrap the compiler with profile feedback, use @code{make profiledbootstrap}. When @samp{make profiledbootstrap} is run, it will first build a @code{stage1} compiler. This compiler is used to build a @code{stageprofile} compiler instrumented to collect execution counts of instruction and branch probabilities. Then runtime libraries are compiled with profile collected. Finally a @code{stagefeedback} compiler is built using the information collected. Unlike standard bootstrap, several additional restrictions apply. The compiler used to build @code{stage1} needs to support a 64-bit integral type. It is recommended to only use GCC for this. Also parallel make is currently not supported since collisions in profile collecting may occur. @html
@end html @ifhtml @uref{./index.html,,Return to the GCC Installation page} @end ifhtml @end ifset @c ***Testing***************************************************************** @ifnothtml @comment node-name, next, previous, up @node Testing, Final install, Building, Installing GCC @end ifnothtml @ifset testhtml @ifnothtml @chapter Installing GCC: Testing @end ifnothtml @cindex Testing @cindex Installing GCC: Testing @cindex Testsuite Before you install GCC, we encourage you to run the testsuites and to compare your results with results from a similar configuration that have been submitted to the @uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}. Some of these archived results are linked from the build status lists at @uref{http://gcc.gnu.org/buildstat.html}, although not everyone who reports a successful build runs the testsuites and submits the results. This step is optional and may require you to download additional software, but it can give you confidence in your new GCC installation or point out problems before you install and start using your new GCC@. First, you must have @uref{download.html,,downloaded the testsuites}. These are part of the full distribution, but if you downloaded the ``core'' compiler plus any front ends, you must download the testsuites separately. Second, you must have the testing tools installed. This includes @uref{http://www.gnu.org/software/dejagnu/,,DejaGnu}, Tcl, and Expect; the DejaGnu site has links to these. If the directories where @command{runtest} and @command{expect} were installed are not in the @env{PATH}, you may need to set the following environment variables appropriately, as in the following example (which assumes that DejaGnu has been installed under @file{/usr/local}): @smallexample TCL_LIBRARY = /usr/local/share/tcl8.0 DEJAGNULIBS = /usr/local/share/dejagnu @end smallexample (On systems such as Cygwin, these paths are required to be actual paths, not mounts or links; presumably this is due to some lack of portability in the DejaGnu code.) Finally, you can run the testsuite (which may take a long time): @smallexample cd @var{objdir}; make -k check @end smallexample This will test various components of GCC, such as compiler front ends and runtime libraries. While running the testsuite, DejaGnu might emit some harmless messages resembling @samp{WARNING: Couldn't find the global config file.} or @samp{WARNING: Couldn't find tool init file} that can be ignored. If you are testing a cross-compiler, you may want to run the testsuite on a simulator as described at @uref{http://gcc.gnu.org/simtest-howto.html}. @section How can you run the testsuite on selected tests? In order to run sets of tests selectively, there are targets @samp{make check-gcc} and language specific @samp{make check-c}, @samp{make check-c++}, @samp{make check-fortran}, @samp{make check-java}, @samp{make check-ada}, @samp{make check-objc}, @samp{make check-obj-c++}, @samp{make check-lto} in the @file{gcc} subdirectory of the object directory. You can also just run @samp{make check} in a subdirectory of the object directory. A more selective way to just run all @command{gcc} execute tests in the testsuite is to use @smallexample make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}" @end smallexample Likewise, in order to run only the @command{g++} ``old-deja'' tests in the testsuite with filenames matching @samp{9805*}, you would use @smallexample make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}" @end smallexample The @file{*.exp} files are located in the testsuite directories of the GCC source, the most important ones being @file{compile.exp}, @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}. To get a list of the possible @file{*.exp} files, pipe the output of @samp{make check} into a file and look at the @samp{Running @dots{} .exp} lines. @section Passing options and running multiple testsuites You can pass multiple options to the testsuite using the @samp{--target_board} option of DejaGNU, either passed as part of @samp{RUNTESTFLAGS}, or directly to @command{runtest} if you prefer to work outside the makefiles. For example, @smallexample make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fmerge-constants" @end smallexample will run the standard @command{g++} testsuites (``unix'' is the target name for a standard native testsuite situation), passing @samp{-O3 -fmerge-constants} to the compiler on every test, i.e., slashes separate options. You can run the testsuites multiple times using combinations of options with a syntax similar to the brace expansion of popular shells: @smallexample @dots{}"--target_board=arm-sim\@{-mhard-float,-msoft-float\@}\@{-O1,-O2,-O3,\@}" @end smallexample (Note the empty option caused by the trailing comma in the final group.) The following will run each testsuite eight times using the @samp{arm-sim} target, as if you had specified all possible combinations yourself: @smallexample --target_board='arm-sim/-mhard-float/-O1 \ arm-sim/-mhard-float/-O2 \ arm-sim/-mhard-float/-O3 \ arm-sim/-mhard-float \ arm-sim/-msoft-float/-O1 \ arm-sim/-msoft-float/-O2 \ arm-sim/-msoft-float/-O3 \ arm-sim/-msoft-float' @end smallexample They can be combined as many times as you wish, in arbitrary ways. This list: @smallexample @dots{}"--target_board=unix/-Wextra\@{-O3,-fno-strength\@}\@{-fomit-frame,\@}" @end smallexample will generate four combinations, all involving @samp{-Wextra}. The disadvantage to this method is that the testsuites are run in serial, which is a waste on multiprocessor systems. For users with GNU Make and a shell which performs brace expansion, you can run the testsuites in parallel by having the shell perform the combinations and @command{make} do the parallel runs. Instead of using @samp{--target_board}, use a special makefile target: @smallexample make -j@var{N} check-@var{testsuite}//@var{test-target}/@var{option1}/@var{option2}/@dots{} @end smallexample For example, @smallexample make -j3 check-gcc//sh-hms-sim/@{-m1,-m2,-m3,-m3e,-m4@}/@{,-nofpu@} @end smallexample will run three concurrent ``make-gcc'' testsuites, eventually testing all ten combinations as described above. Note that this is currently only supported in the @file{gcc} subdirectory. (To see how this works, try typing @command{echo} before the example given here.) @section Additional testing for Java Class Libraries The Java runtime tests can be executed via @samp{make check} in the @file{@var{target}/libjava/testsuite} directory in the build tree. The @uref{http://sourceware.org/mauve/,,Mauve Project} provides a suite of tests for the Java Class Libraries. This suite can be run as part of libgcj testing by placing the Mauve tree within the libjava testsuite at @file{libjava/testsuite/libjava.mauve/mauve}, or by specifying the location of that tree when invoking @samp{make}, as in @samp{make MAUVEDIR=~/mauve check}. @section How to interpret test results The result of running the testsuite are various @file{*.sum} and @file{*.log} files in the testsuite subdirectories. The @file{*.log} files contain a detailed log of the compiler invocations and the corresponding results, the @file{*.sum} files summarize the results. These summaries contain status codes for all tests: @itemize @bullet @item PASS: the test passed as expected @item XPASS: the test unexpectedly passed @item FAIL: the test unexpectedly failed @item XFAIL: the test failed as expected @item UNSUPPORTED: the test is not supported on this platform @item ERROR: the testsuite detected an error @item WARNING: the testsuite detected a possible problem @end itemize It is normal for some tests to report unexpected failures. At the current time the testing harness does not allow fine grained control over whether or not a test is expected to fail. This problem should be fixed in future releases. @section Submitting test results If you want to report the results to the GCC project, use the @file{contrib/test_summary} shell script. Start it in the @var{objdir} with @smallexample @var{srcdir}/contrib/test_summary -p your_commentary.txt \ -m gcc-testresults@@gcc.gnu.org |sh @end smallexample This script uses the @command{Mail} program to send the results, so make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is prepended to the testsuite summary and should contain any special remarks you have on your results or your build environment. Please do not edit the testsuite result block or the subject line, as these messages may be automatically processed. @html
@end html @ifhtml @uref{./index.html,,Return to the GCC Installation page} @end ifhtml @end ifset @c ***Final install*********************************************************** @ifnothtml @comment node-name, next, previous, up @node Final install, , Testing, Installing GCC @end ifnothtml @ifset finalinstallhtml @ifnothtml @chapter Installing GCC: Final installation @end ifnothtml Now that GCC has been built (and optionally tested), you can install it with @smallexample cd @var{objdir} && make install @end smallexample We strongly recommend to install into a target directory where there is no previous version of GCC present. Also, the GNAT runtime should not be stripped, as this would break certain features of the debugger that depend on this debugging information (catching Ada exceptions for instance). That step completes the installation of GCC; user level binaries can be found in @file{@var{prefix}/bin} where @var{prefix} is the value you specified with the @option{--prefix} to configure (or @file{/usr/local} by default). (If you specified @option{--bindir}, that directory will be used instead; otherwise, if you specified @option{--exec-prefix}, @file{@var{exec-prefix}/bin} will be used.) Headers for the C++ and Java libraries are installed in @file{@var{prefix}/include}; libraries in @file{@var{libdir}} (normally @file{@var{prefix}/lib}); internal parts of the compiler in @file{@var{libdir}/gcc} and @file{@var{libexecdir}/gcc}; documentation in info format in @file{@var{infodir}} (normally @file{@var{prefix}/info}). When installing cross-compilers, GCC's executables are not only installed into @file{@var{bindir}}, that is, @file{@var{exec-prefix}/bin}, but additionally into @file{@var{exec-prefix}/@var{target-alias}/bin}, if that directory exists. Typically, such @dfn{tooldirs} hold target-specific binutils, including assembler and linker. Installation into a temporary staging area or into a @command{chroot} jail can be achieved with the command @smallexample make DESTDIR=@var{path-to-rootdir} install @end smallexample @noindent where @var{path-to-rootdir} is the absolute path of a directory relative to which all installation paths will be interpreted. Note that the directory specified by @code{DESTDIR} need not exist yet; it will be created if necessary. There is a subtle point with tooldirs and @code{DESTDIR}: If you relocate a cross-compiler installation with e.g.@: @samp{DESTDIR=@var{rootdir}}, then the directory @file{@var{rootdir}/@var{exec-prefix}/@var{target-alias}/bin} will be filled with duplicated GCC executables only if it already exists, it will not be created otherwise. This is regarded as a feature, not as a bug, because it gives slightly more control to the packagers using the @code{DESTDIR} feature. You can install stripped programs and libraries with @smallexample make install-strip @end smallexample If you are bootstrapping a released version of GCC then please quickly review the build status page for your release, available from @uref{http://gcc.gnu.org/buildstat.html}. If your system is not listed for the version of GCC that you built, send a note to @email{gcc@@gcc.gnu.org} indicating that you successfully built and installed GCC@. Include the following information: @itemize @bullet @item Output from running @file{@var{srcdir}/config.guess}. Do not send that file itself, just the one-line output from running it. @item The output of @samp{gcc -v} for your newly installed @command{gcc}. This tells us which version of GCC you built and the options you passed to configure. @item Whether you enabled all languages or a subset of them. If you used a full distribution then this information is part of the configure options in the output of @samp{gcc -v}, but if you downloaded the ``core'' compiler plus additional front ends then it isn't apparent which ones you built unless you tell us about it. @item If the build was for GNU/Linux, also include: @itemize @bullet @item The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3); this information should be available from @file{/etc/issue}. @item The version of the Linux kernel, available from @samp{uname --version} or @samp{uname -a}. @item The version of glibc you used; for RPM-based systems like Red Hat, Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version, and on systems like Debian and Progeny use @samp{dpkg -l libc6}. @end itemize For other systems, you can include similar information if you think it is relevant. @item Any other information that you think would be useful to people building GCC on the same configuration. The new entry in the build status list will include a link to the archived copy of your message. @end itemize We'd also like to know if the @ifnothtml @ref{Specific, host/target specific installation notes} @end ifnothtml @ifhtml @uref{specific.html,,host/target specific installation notes} @end ifhtml didn't include your host/target information or if that information is incomplete or out of date. Send a note to @email{gcc@@gcc.gnu.org} detailing how the information should be changed. If you find a bug, please report it following the @uref{../bugs/,,bug reporting guidelines}. If you want to print the GCC manuals, do @samp{cd @var{objdir}; make dvi}. You will need to have @command{texi2dvi} (version at least 4.7) and @TeX{} installed. This creates a number of @file{.dvi} files in subdirectories of @file{@var{objdir}}; these may be converted for printing with programs such as @command{dvips}. Alternately, by using @samp{make pdf} in place of @samp{make dvi}, you can create documentation in the form of @file{.pdf} files; this requires @command{texi2pdf}, which is included with Texinfo version 4.8 and later. You can also @uref{http://shop.fsf.org/,,buy printed manuals from the Free Software Foundation}, though such manuals may not be for the most recent version of GCC@. If you would like to generate online HTML documentation, do @samp{cd @var{objdir}; make html} and HTML will be generated for the gcc manuals in @file{@var{objdir}/gcc/HTML}. @html
@end html @ifhtml @uref{./index.html,,Return to the GCC Installation page} @end ifhtml @end ifset @c ***Binaries**************************************************************** @ifnothtml @comment node-name, next, previous, up @node Binaries, Specific, Installing GCC, Top @end ifnothtml @ifset binarieshtml @ifnothtml @chapter Installing GCC: Binaries @end ifnothtml @cindex Binaries @cindex Installing GCC: Binaries We are often asked about pre-compiled versions of GCC@. While we cannot provide these for all platforms, below you'll find links to binaries for various platforms where creating them by yourself is not easy due to various reasons. Please note that we did not create these binaries, nor do we support them. If you have any problems installing them, please contact their makers. @itemize @item AIX: @itemize @item @uref{http://www.bullfreeware.com,,Bull's Freeware and Shareware Archive for AIX}; @item @uref{http://pware.hvcc.edu,,Hudson Valley Community College Open Source Software for IBM System p}; @item @uref{http://www.perzl.org/aix/,,AIX 5L and 6 Open Source Packages}. @end itemize @item DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}. @item Renesas H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU Development Tools for the Renesas H8/300[HS] Series}. @item HP-UX: @itemize @item @uref{http://hpux.connect.org.uk/,,HP-UX Porting Center}; @item @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}. @end itemize @item @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO OpenServer/Unixware}. @item Solaris 2 (SPARC, Intel): @itemize @item @uref{http://www.sunfreeware.com/,,Sunfreeware} @item @uref{http://www.blastwave.org/,,Blastwave} @item @uref{http://www.opencsw.org/,,OpenCSW} @item @uref{http://jupiterrise.com/tgcware/,,TGCware} @end itemize @item Microsoft Windows: @itemize @item The @uref{http://sourceware.org/cygwin/,,Cygwin} project; @item The @uref{http://www.mingw.org/,,MinGW} project. @end itemize @item @uref{ftp://ftp.thewrittenword.com/packages/by-name/,,The Written Word} offers binaries for AIX 4.3.3, 5.1 and 5.2, GNU/Linux (i386), HP-UX 10.20, 11.00, and 11.11, and Solaris/SPARC 2.5.1, 2.6, 7, 8, 9 and 10. @item @uref{http://www.openpkg.org/,,OpenPKG} offers binaries for quite a number of platforms. @item The @uref{http://gcc.gnu.org/wiki/GFortranBinaries,,GFortran Wiki} has links to GNU Fortran binaries for several platforms. @end itemize @html
@end html @ifhtml @uref{./index.html,,Return to the GCC Installation page} @end ifhtml @end ifset @c ***Specific**************************************************************** @ifnothtml @comment node-name, next, previous, up @node Specific, Old, Binaries, Top @end ifnothtml @ifset specifichtml @ifnothtml @chapter Host/target specific installation notes for GCC @end ifnothtml @cindex Specific @cindex Specific installation notes @cindex Target specific installation @cindex Host specific installation @cindex Target specific installation notes Please read this document carefully @emph{before} installing the GNU Compiler Collection on your machine. Note that this list of install notes is @emph{not} a list of supported hosts or targets. Not all supported hosts and targets are listed here, only the ones that require host-specific or target-specific information have to. @ifhtml @itemize @item @uref{#alpha-x-x,,alpha*-*-*} @item @uref{#alpha-dec-osf51,,alpha*-dec-osf5.1} @item @uref{#amd64-x-solaris210,,amd64-*-solaris2.10} @item @uref{#arm-x-eabi,,arm-*-eabi} @item @uref{#avr,,avr} @item @uref{#bfin,,Blackfin} @item @uref{#dos,,DOS} @item @uref{#x-x-freebsd,,*-*-freebsd*} @item @uref{#h8300-hms,,h8300-hms} @item @uref{#hppa-hp-hpux,,hppa*-hp-hpux*} @item @uref{#hppa-hp-hpux10,,hppa*-hp-hpux10} @item @uref{#hppa-hp-hpux11,,hppa*-hp-hpux11} @item @uref{#x-x-linux-gnu,,*-*-linux-gnu} @item @uref{#ix86-x-linux,,i?86-*-linux*} @item @uref{#ix86-x-solaris289,,i?86-*-solaris2.9} @item @uref{#ix86-x-solaris210,,i?86-*-solaris2.10} @item @uref{#ia64-x-linux,,ia64-*-linux} @item @uref{#ia64-x-hpux,,ia64-*-hpux*} @item @uref{#x-ibm-aix,,*-ibm-aix*} @item @uref{#iq2000-x-elf,,iq2000-*-elf} @item @uref{#lm32-x-elf,,lm32-*-elf} @item @uref{#lm32-x-uclinux,,lm32-*-uclinux} @item @uref{#m32c-x-elf,,m32c-*-elf} @item @uref{#m32r-x-elf,,m32r-*-elf} @item @uref{#m68k-x-x,,m68k-*-*} @item @uref{#m68k-uclinux,,m68k-uclinux} @item @uref{#mep-x-elf,,mep-*-elf} @item @uref{#microblaze-x-elf,,microblaze-*-elf} @item @uref{#mips-x-x,,mips-*-*} @item @uref{#mips-sgi-irix5,,mips-sgi-irix5} @item @uref{#mips-sgi-irix6,,mips-sgi-irix6} @item @uref{#powerpc-x-x,,powerpc*-*-*} @item @uref{#powerpc-x-darwin,,powerpc-*-darwin*} @item @uref{#powerpc-x-elf,,powerpc-*-elf} @item @uref{#powerpc-x-linux-gnu,,powerpc*-*-linux-gnu*} @item @uref{#powerpc-x-netbsd,,powerpc-*-netbsd*} @item @uref{#powerpc-x-eabisim,,powerpc-*-eabisim} @item @uref{#powerpc-x-eabi,,powerpc-*-eabi} @item @uref{#powerpcle-x-elf,,powerpcle-*-elf} @item @uref{#powerpcle-x-eabisim,,powerpcle-*-eabisim} @item @uref{#powerpcle-x-eabi,,powerpcle-*-eabi} @item @uref{#s390-x-linux,,s390-*-linux*} @item @uref{#s390x-x-linux,,s390x-*-linux*} @item @uref{#s390x-ibm-tpf,,s390x-ibm-tpf*} @item @uref{#x-x-solaris2,,*-*-solaris2*} @item @uref{#sparc-x-x,,sparc*-*-*} @item @uref{#sparc-sun-solaris2,,sparc-sun-solaris2*} @item @uref{#sparc-sun-solaris210,,sparc-sun-solaris2.10} @item @uref{#sparc-x-linux,,sparc-*-linux*} @item @uref{#sparc64-x-solaris2,,sparc64-*-solaris2*} @item @uref{#sparcv9-x-solaris2,,sparcv9-*-solaris2*} @item @uref{#c6x-x-x,,c6x-*-*} @item @uref{#tilegx-x-linux,,tilegx-*-linux*} @item @uref{#tilepro-x-linux,,tilepro-*-linux*} @item @uref{#x-x-vxworks,,*-*-vxworks*} @item @uref{#x86-64-x-x,,x86_64-*-*, amd64-*-*} @item @uref{#x86-64-x-solaris210,,x86_64-*-solaris2.1[0-9]*} @item @uref{#xtensa-x-elf,,xtensa*-*-elf} @item @uref{#xtensa-x-linux,,xtensa*-*-linux*} @item @uref{#windows,,Microsoft Windows} @item @uref{#x-x-cygwin,,*-*-cygwin} @item @uref{#x-x-interix,,*-*-interix} @item @uref{#x-x-mingw32,,*-*-mingw32} @item @uref{#os2,,OS/2} @item @uref{#older,,Older systems} @end itemize @itemize @item @uref{#elf,,all ELF targets} (SVR4, Solaris 2, etc.) @end itemize @end ifhtml @html
@end html @ifhtml @uref{./index.html,,Return to the GCC Installation page} @end ifhtml @end ifset @c ***Old documentation****************************************************** @ifset oldhtml @include install-old.texi @html
@end html @ifhtml @uref{./index.html,,Return to the GCC Installation page} @end ifhtml @end ifset @c ***GFDL******************************************************************** @ifset gfdlhtml @include fdl.texi @html
@end html @ifhtml @uref{./index.html,,Return to the GCC Installation page} @end ifhtml @end ifset @c *************************************************************************** @c Part 6 The End of the Document @ifinfo @comment node-name, next, previous, up @node Concept Index, , GNU Free Documentation License, Top @end ifinfo @ifinfo @unnumbered Concept Index @printindex cp @contents @end ifinfo @bye