Subversion Repositories scarts

\input texinfo.tex    @c -*-texinfo-*-

@c @ifnothtml

@c %**start of header

@setfilename gccinstall.info

@settitle Installing GCC

@setchapternewpage odd

@c %**end of header

@c @end ifnothtml

@c Specify title for specific html page

@ifset indexhtml

@settitle Installing GCC

@end ifset

@ifset specifichtml

@settitle Host/Target specific installation notes for GCC

@end ifset

@ifset prerequisiteshtml

@settitle Prerequisites for GCC

@end ifset

@ifset downloadhtml

@settitle Downloading GCC

@end ifset

@ifset configurehtml

@settitle Installing GCC: Configuration

@end ifset

@ifset buildhtml

@settitle Installing GCC: Building

@end ifset

@ifset testhtml

@settitle Installing GCC: Testing

@end ifset

@ifset finalinstallhtml

@settitle Installing GCC: Final installation

@end ifset

@ifset binarieshtml

@settitle Installing GCC: Binaries

@end ifset

@ifset oldhtml

@settitle Installing GCC: Old documentation

@end ifset

@ifset gfdlhtml

@settitle Installing GCC: GNU Free Documentation License

@end ifset

@c Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,

@c 1999, 2000, 2001, 2002, 2003, 2004, 2005 Free Software Foundation, Inc.

@c *** Converted to texinfo by Dean Wakerley, dean@wakerley.com

@c Include everything if we're not making html

@ifnothtml

@set indexhtml

@set specifichtml

@set prerequisiteshtml

@set downloadhtml

@set configurehtml

@set buildhtml

@set testhtml

@set finalinstallhtml

@set binarieshtml

@set oldhtml

@set gfdlhtml

@end ifnothtml

@c Part 2 Summary Description and Copyright

@copying

Copyright @copyright{} 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,

1999, 2000, 2001, 2002, 2003, 2004, 2005 Free Software Foundation, Inc.

@sp 1

Permission is granted to copy, distribute and/or modify this document

under the terms of the GNU Free Documentation License, Version 1.2 or

any later version published by the Free Software Foundation; with no

Invariant Sections, the Front-Cover texts being (a) (see below), and

with the Back-Cover Texts being (b) (see below).  A copy of the

license is included in the section entitled ``@uref{./gfdl.html,,GNU

Free Documentation License}''.

(a) The FSF's Front-Cover Text is:

     A GNU Manual

(b) The FSF's Back-Cover Text is:

     You have freedom to copy and modify this GNU Manual, like GNU

     software.  Copies published by the Free Software Foundation raise

     funds for GNU development.

@end copying

@ifinfo

@insertcopying

@end ifinfo

@dircategory Programming

@direntry

* gccinstall: (gccinstall).    Installing the GNU Compiler Collection.

@end direntry

@c Part 3 Titlepage and Copyright

@titlepage

@sp 10

@comment The title is printed in a large font.

@center @titlefont{Installing GCC}

@c The following two commands start the copyright page.

@page

@vskip 0pt plus 1filll

@insertcopying

@end titlepage

@c Part 4 Top node and Master Menu

@ifinfo

@node    Top, , , (dir)

@comment node-name, next,          Previous, up

@menu

* Installing GCC::  This document describes the generic installation

                    procedure for GCC as well as detailing some target

                    specific installation instructions.

* Specific::        Host/target specific installation notes for GCC.

* Binaries::        Where to get pre-compiled binaries.

* Old::             Old installation documentation.

* GNU Free Documentation License:: How you can copy and share this manual.

* Concept Index::   This index has two entries.

@end menu

@end ifinfo

@c Part 5 The Body of the Document

@c ***Installing GCC**********************************************************

@ifnothtml

@comment node-name,     next,          previous, up

@node    Installing GCC, Binaries, , Top

@end ifnothtml

@ifset indexhtml

@ifnothtml

@chapter Installing GCC

@end ifnothtml

The latest version of this document is always available at

@uref{http://gcc.gnu.org/install/,,http://gcc.gnu.org/install/}.

This document describes the generic installation procedure for GCC as well

as detailing some target specific installation instructions.

GCC includes several components that previously were separate distributions

with their own installation instructions.  This document supersedes all

package specific installation instructions.

@emph{Before} starting the build/install procedure please check the

@ifnothtml

@ref{Specific, host/target specific installation notes}.

@end ifnothtml

@ifhtml

@uref{specific.html,,host/target specific installation notes}.

@end ifhtml

We recommend you browse the entire generic installation instructions before

you proceed.

Lists of successful builds for released versions of GCC are

available at @uref{http://gcc.gnu.org/buildstat.html}.

These lists are updated as new information becomes available.

The installation procedure itself is broken into five steps.

@ifinfo

@menu

* Prerequisites::

* Downloading the source::

* Configuration::

* Building::

* Testing:: (optional)

* Final install::

@end menu

@end ifinfo

@ifhtml

@enumerate

@item

@uref{prerequisites.html,,Prerequisites}

@item

@uref{download.html,,Downloading the source}

@item

@uref{configure.html,,Configuration}

@item

@uref{build.html,,Building}

@item

@uref{test.html,,Testing} (optional)

@item

@uref{finalinstall.html,,Final install}

@end enumerate

@end ifhtml

Please note that GCC does not support @samp{make uninstall} and probably

won't do so in the near future as this would open a can of worms.  Instead,

we suggest that you install GCC into a directory of its own and simply

remove that directory when you do not need that specific version of GCC

any longer, and, if shared libraries are installed there as well, no

more binaries exist that use them.

@ifhtml

There are also some @uref{old.html,,old installation instructions},

which are mostly obsolete but still contain some information which has

not yet been merged into the main part of this manual.

@end ifhtml

@html

<hr />

<p>

@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 C90 compiler

Necessary to bootstrap GCC, although 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 2.95 or later) because source code for language

frontends other than C might use GCC extensions.

@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 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.79.1 (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 GNU Multiple Precision Library (GMP) version 4.0 (or later)

Necessary to build the Fortran frontend.  If you don't have it

installed in your library search path, you will have to configure with

the @option{--with-gmp} or @option{--with-gmp-dir} configure option.

@item MPFR Library

Necessary to build the Fortran frontend.  It can be downloaded from

@uref{http://www.mpfr.org/}.  It is also included in the current GMP

release (4.1.3) when configured with @option{--enable-mpfr}.

The @option{--with-mpfr} or @option{--with-mpfr-dir} configure option should

be used if your MPFR Library is not installed in your library search path.

@end table

@heading Tools/packages necessary for modifying GCC

@table @asis

@item autoconf versions 2.13 and 2.59

@itemx GNU m4 version 1.4 (or later)

Necessary when modifying @file{configure.ac}, @file{aclocal.m4}, etc.@:

to regenerate @file{configure} and @file{config.in} files.  Most

directories require autoconf 2.59 (exactly), but the toplevel

still requires autoconf 2.13 (exactly).

@item automake versions 1.9.3

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.9.x series, which is currently 1.9.3.  When regenerating a directory

to a newer version, please update all the directories using an older 1.9.x

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 GNU Bison version 1.28 (or later)

Berkeley @command{yacc} (@command{byacc}) is also reported to work other

than for GCJ.

Necessary when modifying @file{*.y} 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 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.2 (or later)

Necessary for running @command{makeinfo} when modifying @file{*.texi}

files to test your changes.

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}, used when running

@command{make dvi} to create DVI files.

@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 Perl version 5.6.1 (or later)

Necessary when regenerating @file{Makefile} dependencies in libiberty.

Necessary when regenerating @file{libiberty/functions.texi}.

Necessary when generating manpages from Texinfo manuals.

Necessary when targetting Darwin, building libstdc++,

and not using @option{--disable-symvers}.

Used by various scripts to generate some files included in SVN (mainly

Unicode-related and rarely changing) from source tables.

@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.

@end table

@html

<hr />

<p>

@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}.  It is possible to download a full distribution or specific

components.

Please refer to the @uref{http://gcc.gnu.org/releases.html,,releases web page}

for information on how to obtain GCC@.

The full distribution includes the C, C++, Objective-C, Fortran 77, Fortran

(in case of GCC 4.0 and later), Java, and Ada (in case of GCC 3.1 and later)

compilers.  The full distribution also includes runtime libraries for C++,

Objective-C, Fortran 77, Fortran, and Java.  In GCC 3.0 and later versions,

GNU compiler testsuites are also included in the full distribution.

If you choose to download specific components, you must download the core

GCC distribution plus any language specific distributions you wish to

use.  The core distribution includes the C language front end as well as the

shared components.  Each language has a tarball which includes the language

front end as well as the language runtime (when appropriate).

Unpack the core distribution as well as any language specific

distributions in the same directory.

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.

@html

<hr />

<p>

@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} 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 than 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.

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

To configure GCC:

@smallexample

   % mkdir @var{objdir}

   % cd @var{objdir}

   % @var{srcdir}/configure [@var{options}] [@var{target}]

@end smallexample

@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 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-coff, 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 --infodir=@var{dirname}

Specify the installation directory for documentation in info format.

The default is @file{@var{prefix}/info}.

@item --datadir=@var{dirname}

Specify the installation directory for some architecture-independent

data files referenced by GCC@.  The default is @file{@var{prefix}/share}.

@item --mandir=@var{dirname}

Specify the installation directory for manual pages.  The default is

@file{@var{prefix}/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 is

@file{@var{prefix}/include/c++/@var{version}}.

@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 --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} 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}}.

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{i386-@var{any}-sysv}

@item @samp{m68k-bull-sysv}

@item @samp{m68k-hp-hpux}

@item @samp{m68000-hp-hpux}

@item @samp{m68000-att-sysv}

@item @samp{sparc-sun-solaris2.@var{any}}

@item @samp{sparc64-@var{any}-solaris2.@var{any}}

@end itemize

On the systems listed above (except for the HP-PA, the SPARC, for ISC on

the 386, if you use the GNU assembler, you should also use the GNU linker

(and specify @option{--with-gnu-ld}).

@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

Check the @file{@var{libexec}/gcc/@var{target}/@var{version}}

directory, where @var{libexec} defaults to

@file{@var{exec-prefix}/libexec} and @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

Check operating system specific directories (e.g.@: @file{/usr/ccs/bin} on

Sun Solaris 2).

@end itemize

Note that these rules do not check for the value of @env{PATH}.  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 --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 arc-*-elf*

biendian.

@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 --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 gnat

Ada tasking support.  For non-Ada programs, this setting is equivalent

to @samp{single}.  When used in conjunction with the Ada run time, it

causes GCC to use the same thread primitives as Ada uses.  This option

is necessary when using both Ada and the back end exception handling,

which is the default for most Ada targets.

@item mach

Generic MACH thread support, known to work on NeXTSTEP@.  (Please note

that the file needed to support this configuration, @file{gthr-mach.h}, is

missing and thus this setting will cause a known bootstrap failure.)

@item no

This is an alias for @samp{single}.

@item posix

Generic POSIX/Unix98 thread support.

@item posix95

Generic POSIX/Unix95 thread support.

@item rtems

RTEMS thread support.

@item single

Disable thread support, should work for all platforms.

@item solaris

Sun Solaris 2 thread support.