Subversion Repositories openrisc_2011-10-31

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

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

@c @ifnothtml

@c @ifnothtml

@c %**start of header

@c %**start of header

@setfilename gccinstall.info

@setfilename gccinstall.info

@settitle Installing GCC

@settitle Installing GCC

@setchapternewpage odd

@setchapternewpage odd

@c %**end of header

@c %**end of header

@c @end ifnothtml

@c @end ifnothtml

@include gcc-common.texi

@include gcc-common.texi

@c Specify title for specific html page

@c Specify title for specific html page

@ifset indexhtml

@ifset indexhtml

@settitle Installing GCC

@settitle Installing GCC

@end ifset

@end ifset

@ifset specifichtml

@ifset specifichtml

@settitle Host/Target specific installation notes for GCC

@settitle Host/Target specific installation notes for GCC

@end ifset

@end ifset

@ifset prerequisiteshtml

@ifset prerequisiteshtml

@settitle Prerequisites for GCC

@settitle Prerequisites for GCC

@end ifset

@end ifset

@ifset downloadhtml

@ifset downloadhtml

@settitle Downloading GCC

@settitle Downloading GCC

@end ifset

@end ifset

@ifset configurehtml

@ifset configurehtml

@settitle Installing GCC: Configuration

@settitle Installing GCC: Configuration

@end ifset

@end ifset

@ifset buildhtml

@ifset buildhtml

@settitle Installing GCC: Building

@settitle Installing GCC: Building

@end ifset

@end ifset

@ifset testhtml

@ifset testhtml

@settitle Installing GCC: Testing

@settitle Installing GCC: Testing

@end ifset

@end ifset

@ifset finalinstallhtml

@ifset finalinstallhtml

@settitle Installing GCC: Final installation

@settitle Installing GCC: Final installation

@end ifset

@end ifset

@ifset binarieshtml

@ifset binarieshtml

@settitle Installing GCC: Binaries

@settitle Installing GCC: Binaries

@end ifset

@end ifset

@ifset oldhtml

@ifset oldhtml

@settitle Installing GCC: Old documentation

@settitle Installing GCC: Old documentation

@end ifset

@end ifset

@ifset gfdlhtml

@ifset gfdlhtml

@settitle Installing GCC: GNU Free Documentation License

@settitle Installing GCC: GNU Free Documentation License

@end ifset

@end ifset

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

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

@c 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,

@c 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,

@c 2010 Free Software Foundation, Inc.

@c 2010 Free Software Foundation, Inc.

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

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

@c IMPORTANT: whenever you modify this file, run `install.texi2html' to

@c IMPORTANT: whenever you modify this file, run `install.texi2html' to

@c test the generation of HTML documents for the gcc.gnu.org web pages.

@c test the generation of HTML documents for the gcc.gnu.org web pages.

@c

@c

@c Do not use @footnote{} in this file as it breaks install.texi2html!

@c Do not use @footnote{} in this file as it breaks install.texi2html!

@c Include everything if we're not making html

@c Include everything if we're not making html

@ifnothtml

@ifnothtml

@set indexhtml

@set indexhtml

@set specifichtml

@set specifichtml

@set prerequisiteshtml

@set prerequisiteshtml

@set downloadhtml

@set downloadhtml

@set configurehtml

@set configurehtml

@set buildhtml

@set buildhtml

@set testhtml

@set testhtml

@set finalinstallhtml

@set finalinstallhtml

@set binarieshtml

@set binarieshtml

@set oldhtml

@set oldhtml

@set gfdlhtml

@set gfdlhtml

@end ifnothtml

@end ifnothtml

@c Part 2 Summary Description and Copyright

@c Part 2 Summary Description and Copyright

@copying

@copying

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

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

1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007,

1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007,

2008 Free Software Foundation, Inc.

2008 Free Software Foundation, Inc.

@sp 1

@sp 1

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

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

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

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

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

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

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

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

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

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

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

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

Free Documentation License}''.

Free Documentation License}''.

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

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

     A GNU Manual

     A GNU Manual

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

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

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

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

     software.  Copies published by the Free Software Foundation raise

     software.  Copies published by the Free Software Foundation raise

     funds for GNU development.

     funds for GNU development.

@end copying

@end copying

@ifinfo

@ifinfo

@insertcopying

@insertcopying

@end ifinfo

@end ifinfo

@dircategory Software development

@dircategory Software development

@direntry

@direntry

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

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

@end direntry

@end direntry

@c Part 3 Titlepage and Copyright

@c Part 3 Titlepage and Copyright

@titlepage

@titlepage

@title Installing GCC

@title Installing GCC

@versionsubtitle

@versionsubtitle

@c The following two commands start the copyright page.

@c The following two commands start the copyright page.

@page

@page

@vskip 0pt plus 1filll

@vskip 0pt plus 1filll

@insertcopying

@insertcopying

@end titlepage

@end titlepage

@c Part 4 Top node, Master Menu, and/or Table of Contents

@c Part 4 Top node, Master Menu, and/or Table of Contents

@ifinfo

@ifinfo

@node    Top, , , (dir)

@node    Top, , , (dir)

@comment node-name, next,          Previous, up

@comment node-name, next,          Previous, up

@menu

@menu

* Installing GCC::  This document describes the generic installation

* Installing GCC::  This document describes the generic installation

                    procedure for GCC as well as detailing some target

                    procedure for GCC as well as detailing some target

                    specific installation instructions.

                    specific installation instructions.

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

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

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

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

* Old::             Old installation documentation.

* Old::             Old installation documentation.

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

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

* Concept Index::   This index has two entries.

* Concept Index::   This index has two entries.

@end menu

@end menu

@end ifinfo

@end ifinfo

@iftex

@iftex

@contents

@contents

@end iftex

@end iftex

@c Part 5 The Body of the Document

@c Part 5 The Body of the Document

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

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

@ifnothtml

@ifnothtml

@comment node-name,     next,          previous, up

@comment node-name,     next,          previous, up

@node    Installing GCC, Binaries, , Top

@node    Installing GCC, Binaries, , Top

@end ifnothtml

@end ifnothtml

@ifset indexhtml

@ifset indexhtml

@ifnothtml

@ifnothtml

@chapter Installing GCC

@chapter Installing GCC

@end ifnothtml

@end ifnothtml

The latest version of this document is always available at

The latest version of this document is always available at

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

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

This document describes the generic installation procedure for GCC as well

This document describes the generic installation procedure for GCC as well

as detailing some target specific installation instructions.

as detailing some target specific installation instructions.

GCC includes several components that previously were separate distributions

GCC includes several components that previously were separate distributions

with their own installation instructions.  This document supersedes all

with their own installation instructions.  This document supersedes all

package specific installation instructions.

package specific installation instructions.

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

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

@ifnothtml

@ifnothtml

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

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

@end ifnothtml

@end ifnothtml

@ifhtml

@ifhtml

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

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

@end ifhtml

@end ifhtml

We recommend you browse the entire generic installation instructions before

We recommend you browse the entire generic installation instructions before

you proceed.

you proceed.

Lists of successful builds for released versions of GCC are

Lists of successful builds for released versions of GCC are

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

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

These lists are updated as new information becomes available.

These lists are updated as new information becomes available.

The installation procedure itself is broken into five steps.

The installation procedure itself is broken into five steps.

@ifinfo

@ifinfo

@menu

@menu

* Prerequisites::

* Prerequisites::

* Downloading the source::

* Downloading the source::

* Configuration::

* Configuration::

* Building::

* Building::

* Testing:: (optional)

* Testing:: (optional)

* Final install::

* Final install::

@end menu

@end menu

@end ifinfo

@end ifinfo

@ifhtml

@ifhtml

@enumerate

@enumerate

@item

@item

@uref{prerequisites.html,,Prerequisites}

@uref{prerequisites.html,,Prerequisites}

@item

@item

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

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

@item

@item

@uref{configure.html,,Configuration}

@uref{configure.html,,Configuration}

@item

@item

@uref{build.html,,Building}

@uref{build.html,,Building}

@item

@item

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

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

@item

@item

@uref{finalinstall.html,,Final install}

@uref{finalinstall.html,,Final install}

@end enumerate

@end enumerate

@end ifhtml

@end ifhtml

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

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,

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

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

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

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

more binaries exist that use them.

more binaries exist that use them.

@ifhtml

@ifhtml

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

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

which are mostly obsolete but still contain some information which has

which are mostly obsolete but still contain some information which has

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

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

@end ifhtml

@end ifhtml

@html

@html

<hr />

<hr />

<p>

<p>

@end html

@end html

@ifhtml

@ifhtml

@uref{./index.html,,Return to the GCC Installation page}

@uref{./index.html,,Return to the GCC Installation page}

@insertcopying

@insertcopying

@end ifhtml

@end ifhtml

@end ifset

@end ifset

@c ***Prerequisites**************************************************

@c ***Prerequisites**************************************************

@ifnothtml

@ifnothtml

@comment node-name,     next,          previous, up

@comment node-name,     next,          previous, up

@node    Prerequisites, Downloading the source, , Installing GCC

@node    Prerequisites, Downloading the source, , Installing GCC

@end ifnothtml

@end ifnothtml

@ifset prerequisiteshtml

@ifset prerequisiteshtml

@ifnothtml

@ifnothtml

@chapter Prerequisites

@chapter Prerequisites

@end ifnothtml

@end ifnothtml

@cindex Prerequisites

@cindex Prerequisites

GCC requires that various tools and packages be available for use in the

GCC requires that various tools and packages be available for use in the

build procedure.  Modifying GCC sources requires additional tools

build procedure.  Modifying GCC sources requires additional tools

described below.

described below.

@heading Tools/packages necessary for building GCC

@heading Tools/packages necessary for building GCC

@table @asis

@table @asis

@item ISO C90 compiler

@item ISO C90 compiler

Necessary to bootstrap GCC, although versions of GCC prior

Necessary to bootstrap GCC, although versions of GCC prior

to 3.4 also allow bootstrapping with a traditional (K&R) C compiler.

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

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

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

GCC binary (version 2.95 or later) because source code for language

frontends other than C might use GCC extensions.

frontends other than C might use GCC extensions.

@item GNAT

@item GNAT

In order to build the Ada compiler (GNAT) you must already have 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

installed because portions of the Ada frontend are written in Ada (with

GNAT extensions.)  Refer to the Ada installation instructions for more

GNAT extensions.)  Refer to the Ada installation instructions for more

specific information.

specific information.

@item A ``working'' POSIX compatible shell, or GNU bash

@item A ``working'' POSIX compatible shell, or GNU bash

Necessary when running @command{configure} because some

Necessary when running @command{configure} because some

@command{/bin/sh} shells have bugs and may crash when configuring the

@command{/bin/sh} shells have bugs and may crash when configuring the

target libraries.  In other cases, @command{/bin/sh} or @command{ksh}

target libraries.  In other cases, @command{/bin/sh} or @command{ksh}

have disastrous corner-case performance problems.  This

have disastrous corner-case performance problems.  This

can cause target @command{configure} runs to literally take days to

can cause target @command{configure} runs to literally take days to

complete in some cases.

complete in some cases.

So on some platforms @command{/bin/ksh} is sufficient, on others it

So on some platforms @command{/bin/ksh} is sufficient, on others it

isn't.  See the host/target specific instructions for your platform, or

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

use @command{bash} to be sure.  Then set @env{CONFIG_SHELL} in your

environment to your ``good'' shell prior to running

environment to your ``good'' shell prior to running

@command{configure}/@command{make}.

@command{configure}/@command{make}.

@command{zsh} is not a fully compliant POSIX shell and will not

@command{zsh} is not a fully compliant POSIX shell and will not

work when configuring GCC@.

work when configuring GCC@.

@item A POSIX or SVR4 awk

@item A POSIX or SVR4 awk

Necessary for creating some of the generated source files for GCC@.

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

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.

are broken.  GNU awk version 3.1.5 is known to work.

@item GNU binutils

@item GNU binutils

Necessary in some circumstances, optional in others.  See the

Necessary in some circumstances, optional in others.  See the

host/target specific instructions for your platform for the exact

host/target specific instructions for your platform for the exact

requirements.

requirements.

@item gzip version 1.2.4 (or later) or

@item gzip version 1.2.4 (or later) or

@itemx bzip2 version 1.0.2 (or later)

@itemx bzip2 version 1.0.2 (or later)

Necessary to uncompress GCC @command{tar} files when source code is

Necessary to uncompress GCC @command{tar} files when source code is

obtained via FTP mirror sites.

obtained via FTP mirror sites.

@item GNU make version 3.80 (or later)

@item GNU make version 3.80 (or later)

You must have GNU make installed to build GCC@.

You must have GNU make installed to build GCC@.

@item GNU tar version 1.14 (or later)

@item GNU tar version 1.14 (or later)

Necessary (only on some platforms) to untar the source code.  Many

Necessary (only on some platforms) to untar the source code.  Many

systems' @command{tar} programs will also work, only try GNU

systems' @command{tar} programs will also work, only try GNU

@command{tar} if you have problems.

@command{tar} if you have problems.

@item GNU Multiple Precision Library (GMP) version 4.3.2 (or later)

@item GNU Multiple Precision Library (GMP) version 4.3.2 (or later)

Necessary to build GCC@.  If you do not have it installed in your

Necessary to build GCC@.  If you do not have it installed in your

library search path, you will have to configure with the

library search path, you will have to configure with the

@option{--with-gmp} configure option.  See also @option{--with-gmp-lib}

@option{--with-gmp} configure option.  See also @option{--with-gmp-lib}

and @option{--with-gmp-include}.  Alternatively, if a GMP source

and @option{--with-gmp-include}.  Alternatively, if a GMP source

distribution is found in a subdirectory of your GCC sources named

distribution is found in a subdirectory of your GCC sources named

@file{gmp}, it will be built together with GCC@.

@file{gmp}, it will be built together with GCC@.

@item MPFR Library version 2.4.2 (or later)

@item MPFR Library version 2.4.2 (or later)

Necessary to build GCC@.  It can be downloaded from

Necessary to build GCC@.  It can be downloaded from

@uref{http://www.mpfr.org/}.  The @option{--with-mpfr} configure

@uref{http://www.mpfr.org/}.  The @option{--with-mpfr} configure

option should be used if your MPFR Library is not installed in your

option should be used if your MPFR Library is not installed in your

default library search path.  See also @option{--with-mpfr-lib} and

default library search path.  See also @option{--with-mpfr-lib} and

@option{--with-mpfr-include}.  Alternatively, if a MPFR source

@option{--with-mpfr-include}.  Alternatively, if a MPFR source

distribution is found in a subdirectory of your GCC sources named

distribution is found in a subdirectory of your GCC sources named

@file{mpfr}, it will be built together with GCC@.

@file{mpfr}, it will be built together with GCC@.

@item MPC Library version 0.8.1 (or later)

@item MPC Library version 0.8.1 (or later)

Necessary to build GCC@.  It can be downloaded from

Necessary to build GCC@.  It can be downloaded from

@uref{http://www.multiprecision.org/}.  The @option{--with-mpc}

@uref{http://www.multiprecision.org/}.  The @option{--with-mpc}

configure option should be used if your MPC Library is not installed

configure option should be used if your MPC Library is not installed

in your default library search path.  See also @option{--with-mpc-lib}

in your default library search path.  See also @option{--with-mpc-lib}

and @option{--with-mpc-include}.  Alternatively, if an MPC source

and @option{--with-mpc-include}.  Alternatively, if an MPC source

distribution is found in a subdirectory of your GCC sources named

distribution is found in a subdirectory of your GCC sources named

@file{mpc}, it will be built together with GCC@.

@file{mpc}, it will be built together with GCC@.

@item Parma Polyhedra Library (PPL) version 0.10

@item Parma Polyhedra Library (PPL) version 0.10

Necessary to build GCC with the Graphite loop optimizations.

Necessary to build GCC with the Graphite loop optimizations.

It can be downloaded from @uref{http://www.cs.unipr.it/ppl/Download/}.

It can be downloaded from @uref{http://www.cs.unipr.it/ppl/Download/}.

The @option{--with-ppl} configure option should be used if PPL is not

The @option{--with-ppl} configure option should be used if PPL is not

installed in your default library search path.

installed in your default library search path.

@item CLooG-PPL version 0.15

@item CLooG-PPL version 0.15

Necessary to build GCC with the Graphite loop optimizations.  It can

Necessary to build GCC with the Graphite loop optimizations.  It can

be downloaded from @uref{ftp://gcc.gnu.org/pub/gcc/infrastructure/}.

be downloaded from @uref{ftp://gcc.gnu.org/pub/gcc/infrastructure/}.

The code in @file{cloog-ppl-0.15.tar.gz} comes from a branch of CLooG

The code in @file{cloog-ppl-0.15.tar.gz} comes from a branch of CLooG

available from @uref{http://repo.or.cz/w/cloog-ppl.git}.  CLooG-PPL

available from @uref{http://repo.or.cz/w/cloog-ppl.git}.  CLooG-PPL

should be configured with @option{--with-ppl}.

should be configured with @option{--with-ppl}.

The @option{--with-cloog} configure option should be used if CLooG is

The @option{--with-cloog} configure option should be used if CLooG is

not installed in your default library search path.

not installed in your default library search path.

@item @command{jar}, or InfoZIP (@command{zip} and @command{unzip})

@item @command{jar}, or InfoZIP (@command{zip} and @command{unzip})

Necessary to build libgcj, the GCJ runtime.

Necessary to build libgcj, the GCJ runtime.

@item libelf version 0.8.12 (or later)

@item libelf version 0.8.12 (or later)

Necessary to build link-time optimization (LTO) support.  It can be

Necessary to build link-time optimization (LTO) support.  It can be

downloaded from @uref{http://www.mr511.de/software/libelf-0.8.12.tar.gz},

downloaded from @uref{http://www.mr511.de/software/libelf-0.8.12.tar.gz},

though it is commonly available in several systems.  The versions in

though it is commonly available in several systems.  The versions in

IRIX 5 and 6 don't work since they lack @file{gelf.h}.  The version in

IRIX 5 and 6 don't work since they lack @file{gelf.h}.  The version in

Solaris 2 does work.

Solaris 2 does work.

The @option{--with-libelf} configure option should be used if libelf is

The @option{--with-libelf} configure option should be used if libelf is

not installed in your default library search patch.

not installed in your default library search patch.

@end table

@end table

@heading Tools/packages necessary for modifying GCC

@heading Tools/packages necessary for modifying GCC

@table @asis

@table @asis

@item autoconf version 2.64

@item autoconf version 2.64

@itemx GNU m4 version 1.4.6 (or later)

@itemx GNU m4 version 1.4.6 (or later)

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

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

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

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

@item automake version 1.11.1

@item automake version 1.11.1

Necessary when modifying a @file{Makefile.am} file to regenerate its

Necessary when modifying a @file{Makefile.am} file to regenerate its

associated @file{Makefile.in}.

associated @file{Makefile.in}.

Much of GCC does not use automake, so directly edit the @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.  Specifically this applies to the @file{gcc}, @file{intl},

@file{libcpp}, @file{libiberty}, @file{libobjc} directories as well

@file{libcpp}, @file{libiberty}, @file{libobjc} directories as well

as any of their subdirectories.

as any of their subdirectories.

For directories that use automake, GCC requires the latest release in

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

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 a newer version, please update all the directories using an older 1.11

to the latest released version.

to the latest released version.

@item gettext version 0.14.5 (or later)

@item gettext version 0.14.5 (or later)

Needed to regenerate @file{gcc.pot}.

Needed to regenerate @file{gcc.pot}.

@item gperf version 2.7.2 (or later)

@item gperf version 2.7.2 (or later)

Necessary when modifying @command{gperf} input files, e.g.@:

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.gperf} to regenerate its associated header file, e.g.@:

@file{gcc/cp/cfns.h}.

@file{gcc/cp/cfns.h}.

@item DejaGnu 1.4.4

@item DejaGnu 1.4.4

@itemx Expect

@itemx Expect

@itemx Tcl

@itemx Tcl

Necessary to run the GCC testsuite; see the section on testing for details.

Necessary to run the GCC testsuite; see the section on testing for details.

@item autogen version 5.5.4 (or later) and

@item autogen version 5.5.4 (or later) and

@itemx guile version 1.4.1 (or later)

@itemx guile version 1.4.1 (or later)

Necessary to regenerate @file{fixinc/fixincl.x} from

Necessary to regenerate @file{fixinc/fixincl.x} from

@file{fixinc/inclhack.def} and @file{fixinc/*.tpl}.

@file{fixinc/inclhack.def} and @file{fixinc/*.tpl}.

Necessary to run @samp{make check} for @file{fixinc}.

Necessary to run @samp{make check} for @file{fixinc}.

Necessary to regenerate the top level @file{Makefile.in} file from

Necessary to regenerate the top level @file{Makefile.in} file from

@file{Makefile.tpl} and @file{Makefile.def}.

@file{Makefile.tpl} and @file{Makefile.def}.

@item Flex version 2.5.4 (or later)

@item Flex version 2.5.4 (or later)

Necessary when modifying @file{*.l} files.

Necessary when modifying @file{*.l} files.

Necessary to build GCC during development because the generated output

Necessary to build GCC during development because the generated output

files are not included in the SVN repository.  They are included in

files are not included in the SVN repository.  They are included in

releases.

releases.

@item Texinfo version 4.7 (or later)

@item Texinfo version 4.7 (or later)

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

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

files to test your changes.

files to test your changes.

Necessary for running @command{make dvi} or @command{make pdf} to

Necessary for running @command{make dvi} or @command{make pdf} to

create printable documentation in DVI or PDF format.  Texinfo version

create printable documentation in DVI or PDF format.  Texinfo version

4.8 or later is required for @command{make pdf}.

4.8 or later is required for @command{make pdf}.

Necessary to build GCC documentation during development because the

Necessary to build GCC documentation during development because the

generated output files are not included in the SVN repository.  They are

generated output files are not included in the SVN repository.  They are

included in releases.

included in releases.

@item @TeX{} (any working version)

@item @TeX{} (any working version)

Necessary for running @command{texi2dvi} and @command{texi2pdf}, which

Necessary for running @command{texi2dvi} and @command{texi2pdf}, which

are used when running @command{make dvi} or @command{make pdf} to create

are used when running @command{make dvi} or @command{make pdf} to create

DVI or PDF files, respectively.

DVI or PDF files, respectively.

@item SVN (any version)

@item SVN (any version)

@itemx SSH (any version)

@itemx SSH (any version)

Necessary to access the SVN repository.  Public releases and weekly

Necessary to access the SVN repository.  Public releases and weekly

snapshots of the development sources are also available via FTP@.

snapshots of the development sources are also available via FTP@.

@item Perl version 5.6.1 (or later)

@item Perl version 5.6.1 (or later)

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

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

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

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

Necessary when generating manpages from Texinfo manuals.

Necessary when generating manpages from Texinfo manuals.

Necessary when targetting Darwin, building libstdc++,

Necessary when targetting Darwin, building libstdc++,

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

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

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

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

Unicode-related and rarely changing) from source tables.

Unicode-related and rarely changing) from source tables.

@item GNU diffutils version 2.7 (or later)

@item GNU diffutils version 2.7 (or later)

Useful when submitting patches for the GCC source code.

Useful when submitting patches for the GCC source code.

@item patch version 2.5.4 (or later)

@item patch version 2.5.4 (or later)

Necessary when applying patches, created with @command{diff}, to one's

Necessary when applying patches, created with @command{diff}, to one's

own sources.

own sources.

@item ecj1

@item ecj1

@itemx gjavah

@itemx gjavah

If you wish to modify @file{.java} files in libjava, you will need to

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

configure with @option{--enable-java-maintainer-mode}, and you will need

to have executables named @command{ecj1} and @command{gjavah} in your path.

to have executables named @command{ecj1} and @command{gjavah} in your path.

The @command{ecj1} executable should run the Eclipse Java compiler via

The @command{ecj1} executable should run the Eclipse Java compiler via

the GCC-specific entry point.  You can download a suitable jar from

the GCC-specific entry point.  You can download a suitable jar from

@uref{ftp://sourceware.org/pub/java/}, or by running the script

@uref{ftp://sourceware.org/pub/java/}, or by running the script

@command{contrib/download_ecj}.

@command{contrib/download_ecj}.

@item antlr.jar version 2.7.1 (or later)

@item antlr.jar version 2.7.1 (or later)

@itemx antlr binary

@itemx antlr binary

If you wish to build the @command{gjdoc} binary in libjava, you will

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

need to have an @file{antlr.jar} library available. The library is

searched in system locations but can be configured with

searched in system locations but can be configured with

@option{--with-antlr-jar=} instead.  When configuring with

@option{--with-antlr-jar=} instead.  When configuring with

@option{--enable-java-maintainer-mode}, you will need to have one of

@option{--enable-java-maintainer-mode}, you will need to have one of

the executables named @command{cantlr}, @command{runantlr} or

the executables named @command{cantlr}, @command{runantlr} or

@command{antlr} in your path.

@command{antlr} in your path.

@end table

@end table

@html

@html

<hr />

<hr />

<p>

<p>

@end html

@end html

@ifhtml

@ifhtml

@uref{./index.html,,Return to the GCC Installation page}

@uref{./index.html,,Return to the GCC Installation page}

@end ifhtml

@end ifhtml

@end ifset

@end ifset

@c ***Downloading the source**************************************************

@c ***Downloading the source**************************************************

@ifnothtml

@ifnothtml

@comment node-name,     next,          previous, up

@comment node-name,     next,          previous, up

@node    Downloading the source, Configuration, Prerequisites, Installing GCC

@node    Downloading the source, Configuration, Prerequisites, Installing GCC

@end ifnothtml

@end ifnothtml

@ifset downloadhtml

@ifset downloadhtml

@ifnothtml

@ifnothtml

@chapter Downloading GCC

@chapter Downloading GCC

@end ifnothtml

@end ifnothtml

@cindex Downloading GCC

@cindex Downloading GCC

@cindex Downloading the Source

@cindex Downloading the Source

GCC is distributed via @uref{http://gcc.gnu.org/svn.html,,SVN} and FTP

GCC is distributed via @uref{http://gcc.gnu.org/svn.html,,SVN} and FTP

tarballs compressed with @command{gzip} or

tarballs compressed with @command{gzip} or

@command{bzip2}.  It is possible to download a full distribution or specific

@command{bzip2}.  It is possible to download a full distribution or specific

components.

components.

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

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

for information on how to obtain GCC@.

for information on how to obtain GCC@.

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

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

and Ada (in the case of GCC 3.1 and later) compilers.  The full

and Ada (in the case of GCC 3.1 and later) compilers.  The full

distribution also includes runtime libraries for C++, Objective-C,

distribution also includes runtime libraries for C++, Objective-C,

Fortran, and Java.  In GCC 3.0 and later versions, the GNU compiler

Fortran, and Java.  In GCC 3.0 and later versions, the GNU compiler

testsuites are also included in the full distribution.

testsuites are also included in the full distribution.

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

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

GCC distribution plus any language specific distributions you wish to

GCC distribution plus any language specific distributions you wish to

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

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

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

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

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

Unpack the core distribution as well as any language specific

Unpack the core distribution as well as any language specific

distributions in the same directory.

distributions in the same directory.

If you also intend to build binutils (either to upgrade an existing

If you also intend to build binutils (either to upgrade an existing

installation or for use in place of the corresponding tools of your

installation or for use in place of the corresponding tools of your

OS), unpack the binutils distribution either in the same directory or

OS), unpack the binutils distribution either in the same directory or

a separate one.  In the latter case, add symbolic links to any

a separate one.  In the latter case, add symbolic links to any

components of the binutils you intend to build alongside the compiler

components of the binutils you intend to build alongside the compiler

(@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld},

(@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld},

@file{opcodes}, @dots{}) to the directory containing the GCC sources.

@file{opcodes}, @dots{}) to the directory containing the GCC sources.

Likewise the GMP, MPFR and MPC libraries can be automatically built

Likewise the GMP, MPFR and MPC libraries can be automatically built

together with GCC.  Unpack the GMP, MPFR and/or MPC source

together with GCC.  Unpack the GMP, MPFR and/or MPC source

distributions in the directory containing the GCC sources and rename

distributions in the directory containing the GCC sources and rename

their directories to @file{gmp}, @file{mpfr} and @file{mpc},

their directories to @file{gmp}, @file{mpfr} and @file{mpc},

respectively (or use symbolic links with the same name).

respectively (or use symbolic links with the same name).

@html

@html

<hr />

<hr />

<p>

<p>

@end html

@end html

@ifhtml

@ifhtml

@uref{./index.html,,Return to the GCC Installation page}

@uref{./index.html,,Return to the GCC Installation page}

@end ifhtml

@end ifhtml

@end ifset

@end ifset

@c ***Configuration***********************************************************

@c ***Configuration***********************************************************

@ifnothtml

@ifnothtml

@comment node-name,     next,          previous, up

@comment node-name,     next,          previous, up

@node    Configuration, Building, Downloading the source, Installing GCC

@node    Configuration, Building, Downloading the source, Installing GCC

@end ifnothtml

@end ifnothtml

@ifset configurehtml

@ifset configurehtml

@ifnothtml

@ifnothtml

@chapter Installing GCC: Configuration

@chapter Installing GCC: Configuration

@end ifnothtml

@end ifnothtml

@cindex Configuration

@cindex Configuration

@cindex Installing GCC: Configuration

@cindex Installing GCC: Configuration

Like most GNU software, GCC must be configured before it can be built.

Like most GNU software, GCC must be configured before it can be built.

This document describes the recommended configuration procedure

This document describes the recommended configuration procedure

for both native and cross targets.

for both native and cross targets.

We use @var{srcdir} to refer to the toplevel source directory for

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.

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

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

@file{gcc} directory, the one where the @file{MAINTAINERS} file can be

found, and not its @file{gcc} subdirectory, otherwise the build will fail.

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

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

file system, the shell's built-in @command{pwd} command will return

temporary pathnames.  Using these can lead to various sorts of build

temporary pathnames.  Using these can lead to various sorts of build

problems.  To avoid this issue, set the @env{PWDCMD} environment

problems.  To avoid this issue, set the @env{PWDCMD} environment

variable to an automounter-aware @command{pwd} command, e.g.,

variable to an automounter-aware @command{pwd} command, e.g.,

@command{pawd} or @samp{amq -w}, during the configuration and build

@command{pawd} or @samp{amq -w}, during the configuration and build

phases.

phases.

First, we @strong{highly} recommend that GCC be built into a

First, we @strong{highly} recommend that GCC be built into a

separate directory from the sources which does @strong{not} reside

separate directory from the sources which does @strong{not} reside

within the source tree.  This is how we generally build GCC; building

within the source tree.  This is how we generally build GCC; building

where @var{srcdir} == @var{objdir} should still work, but doesn't

where @var{srcdir} == @var{objdir} should still work, but doesn't

get extensive testing; building where @var{objdir} is a subdirectory

get extensive testing; building where @var{objdir} is a subdirectory

of @var{srcdir} is unsupported.

of @var{srcdir} is unsupported.

If you have previously built GCC in the same directory for a

If you have previously built GCC in the same directory for a

different target machine, do @samp{make distclean} to delete all files

different target machine, do @samp{make distclean} to delete all files

that might be invalid.  One of the files this deletes is @file{Makefile};

that might be invalid.  One of the files this deletes is @file{Makefile};

if @samp{make distclean} complains that @file{Makefile} does not exist

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

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

means that the directory is already suitably clean.  However, with the

recommended method of building in a separate @var{objdir}, you should

recommended method of building in a separate @var{objdir}, you should

simply use a different @var{objdir} for each target.

simply use a different @var{objdir} for each target.

Second, when configuring a native system, either @command{cc} or

Second, when configuring a native system, either @command{cc} or

@command{gcc} must be in your path or you must set @env{CC} in

@command{gcc} must be in your path or you must set @env{CC} in

your environment before running configure.  Otherwise the configuration

your environment before running configure.  Otherwise the configuration

scripts may fail.

scripts may fail.

@ignore

@ignore

Note that the bootstrap compiler and the resulting GCC must be link

Note that the bootstrap compiler and the resulting GCC must be link

compatible, else the bootstrap will fail with linker errors about

compatible, else the bootstrap will fail with linker errors about

incompatible object file formats.  Several multilibed targets are

incompatible object file formats.  Several multilibed targets are

affected by this requirement, see

affected by this requirement, see

@ifnothtml

@ifnothtml

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

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

@end ifnothtml

@end ifnothtml

@ifhtml

@ifhtml

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

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

@end ifhtml

@end ifhtml

@end ignore

@end ignore

To configure GCC:

To configure GCC:

@smallexample

@smallexample

   % mkdir @var{objdir}

   % mkdir @var{objdir}

   % cd @var{objdir}

   % cd @var{objdir}

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

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

@end smallexample

@end smallexample

@heading Distributor options

@heading Distributor options

If you will be distributing binary versions of GCC, with modifications

If you will be distributing binary versions of GCC, with modifications

to the source code, you should use the options described in this

to the source code, you should use the options described in this

section to make clear that your version contains modifications.

section to make clear that your version contains modifications.

@table @code

@table @code

@item --with-pkgversion=@var{version}

@item --with-pkgversion=@var{version}

Specify a string that identifies your package.  You may wish

Specify a string that identifies your package.  You may wish

to include a build number or build date.  This version string will be

to include a build number or build date.  This version string will be

included in the output of @command{gcc --version}.  This suffix does

included in the output of @command{gcc --version}.  This suffix does

not replace the default version string, only the @samp{GCC} part.

not replace the default version string, only the @samp{GCC} part.

The default value is @samp{GCC}.

The default value is @samp{GCC}.

@item --with-bugurl=@var{url}

@item --with-bugurl=@var{url}

Specify the URL that users should visit if they wish to report a bug.

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,

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.

if you determine that they are not bugs in your modifications.

The default value refers to the FSF's GCC bug tracker.

The default value refers to the FSF's GCC bug tracker.

@end table

@end table

@heading Target specification

@heading Target specification

@itemize @bullet

@itemize @bullet

@item

@item

GCC has code to correctly determine the correct value for @var{target}

GCC has code to correctly determine the correct value for @var{target}

for nearly all native systems.  Therefore, we highly recommend you do

for nearly all native systems.  Therefore, we highly recommend you do

not provide a configure target when configuring a native compiler.

not provide a configure target when configuring a native compiler.

@item

@item

@var{target} must be specified as @option{--target=@var{target}}

@var{target} must be specified as @option{--target=@var{target}}

when configuring a cross compiler; examples of valid targets would be

when configuring a cross compiler; examples of valid targets would be

m68k-elf, sh-elf, etc.

m68k-elf, sh-elf, etc.

@item

@item

Specifying just @var{target} instead of @option{--target=@var{target}}

Specifying just @var{target} instead of @option{--target=@var{target}}

implies that the host defaults to @var{target}.

implies that the host defaults to @var{target}.

@end itemize

@end itemize

@heading Options specification

@heading Options specification

Use @var{options} to override several configure time options for

Use @var{options} to override several configure time options for

GCC@.  A list of supported @var{options} follows; @samp{configure

GCC@.  A list of supported @var{options} follows; @samp{configure

--help} may list other options, but those not listed below may not

--help} may list other options, but those not listed below may not

work and should not normally be used.

work and should not normally be used.

Note that each @option{--enable} option has a corresponding

Note that each @option{--enable} option has a corresponding

@option{--disable} option and that each @option{--with} option has a

@option{--disable} option and that each @option{--with} option has a

corresponding @option{--without} option.

corresponding @option{--without} option.

@table @code

@table @code

@item --prefix=@var{dirname}

@item --prefix=@var{dirname}

Specify the toplevel installation

Specify the toplevel installation

directory.  This is the recommended way to install the tools into a directory

directory.  This is the recommended way to install the tools into a directory

other than the default.  The toplevel installation directory defaults to

other than the default.  The toplevel installation directory defaults to

@file{/usr/local}.

@file{/usr/local}.

We @strong{highly} recommend against @var{dirname} being the same or a

We @strong{highly} recommend against @var{dirname} being the same or a

subdirectory of @var{objdir} or vice versa.  If specifying a directory

subdirectory of @var{objdir} or vice versa.  If specifying a directory

beneath a user's home directory tree, some shells will not expand

beneath a user's home directory tree, some shells will not expand

@var{dirname} correctly if it contains the @samp{~} metacharacter; use

@var{dirname} correctly if it contains the @samp{~} metacharacter; use

@env{$HOME} instead.

@env{$HOME} instead.

The following standard @command{autoconf} options are supported.  Normally you

The following standard @command{autoconf} options are supported.  Normally you

should not need to use these options.

should not need to use these options.

@table @code

@table @code

@item --exec-prefix=@var{dirname}

@item --exec-prefix=@var{dirname}

Specify the toplevel installation directory for architecture-dependent

Specify the toplevel installation directory for architecture-dependent

files.  The default is @file{@var{prefix}}.

files.  The default is @file{@var{prefix}}.

@item --bindir=@var{dirname}

@item --bindir=@var{dirname}

Specify the installation directory for the executables called by users

Specify the installation directory for the executables called by users

(such as @command{gcc} and @command{g++}).  The default is

(such as @command{gcc} and @command{g++}).  The default is

@file{@var{exec-prefix}/bin}.

@file{@var{exec-prefix}/bin}.

@item --libdir=@var{dirname}

@item --libdir=@var{dirname}

Specify the installation directory for object code libraries and

Specify the installation directory for object code libraries and

internal data files of GCC@.  The default is @file{@var{exec-prefix}/lib}.

internal data files of GCC@.  The default is @file{@var{exec-prefix}/lib}.

@item --libexecdir=@var{dirname}

@item --libexecdir=@var{dirname}

Specify the installation directory for internal executables of GCC@.

Specify the installation directory for internal executables of GCC@.

The default is @file{@var{exec-prefix}/libexec}.

The default is @file{@var{exec-prefix}/libexec}.

@item --with-slibdir=@var{dirname}

@item --with-slibdir=@var{dirname}

Specify the installation directory for the shared libgcc library.  The

Specify the installation directory for the shared libgcc library.  The

default is @file{@var{libdir}}.

default is @file{@var{libdir}}.

@item --datarootdir=@var{dirname}

@item --datarootdir=@var{dirname}

Specify the root of the directory tree for read-only architecture-independent

Specify the root of the directory tree for read-only architecture-independent

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

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

@item --infodir=@var{dirname}

@item --infodir=@var{dirname}

Specify the installation directory for documentation in info format.

Specify the installation directory for documentation in info format.

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

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

@item --datadir=@var{dirname}

@item --datadir=@var{dirname}

Specify the installation directory for some architecture-independent

Specify the installation directory for some architecture-independent

data files referenced by GCC@.  The default is @file{@var{datarootdir}}.

data files referenced by GCC@.  The default is @file{@var{datarootdir}}.

@item --docdir=@var{dirname}

@item --docdir=@var{dirname}

Specify the installation directory for documentation files (other

Specify the installation directory for documentation files (other

than Info) for GCC@.  The default is @file{@var{datarootdir}/doc}.

than Info) for GCC@.  The default is @file{@var{datarootdir}/doc}.

@item --htmldir=@var{dirname}

@item --htmldir=@var{dirname}

Specify the installation directory for HTML documentation files.

Specify the installation directory for HTML documentation files.

The default is @file{@var{docdir}}.

The default is @file{@var{docdir}}.

@item --pdfdir=@var{dirname}

@item --pdfdir=@var{dirname}

Specify the installation directory for PDF documentation files.

Specify the installation directory for PDF documentation files.

The default is @file{@var{docdir}}.

The default is @file{@var{docdir}}.

@item --mandir=@var{dirname}

@item --mandir=@var{dirname}

Specify the installation directory for manual pages.  The default is

Specify the installation directory for manual pages.  The default is

@file{@var{datarootdir}/man}.  (Note that the manual pages are only extracts

@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

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

are derived by an automatic conversion process from parts of the full

manual.)

manual.)

@item --with-gxx-include-dir=@var{dirname}

@item --with-gxx-include-dir=@var{dirname}

Specify

Specify

the installation directory for G++ header files.  The default depends

the installation directory for G++ header files.  The default depends

on other configuration options, and differs between cross and native

on other configuration options, and differs between cross and native

configurations.

configurations.

@end table

@end table

@item --program-prefix=@var{prefix}

@item --program-prefix=@var{prefix}

GCC supports some transformations of the names of its programs when

GCC supports some transformations of the names of its programs when

installing them.  This option prepends @var{prefix} to the names of

installing them.  This option prepends @var{prefix} to the names of

programs to install in @var{bindir} (see above).  For example, specifying

programs to install in @var{bindir} (see above).  For example, specifying

@option{--program-prefix=foo-} would result in @samp{gcc}

@option{--program-prefix=foo-} would result in @samp{gcc}

being installed as @file{/usr/local/bin/foo-gcc}.

being installed as @file{/usr/local/bin/foo-gcc}.

@item --program-suffix=@var{suffix}

@item --program-suffix=@var{suffix}

Appends @var{suffix} to the names of programs to install in @var{bindir}

Appends @var{suffix} to the names of programs to install in @var{bindir}

(see above).  For example, specifying @option{--program-suffix=-3.1}

(see above).  For example, specifying @option{--program-suffix=-3.1}

would result in @samp{gcc} being installed as

would result in @samp{gcc} being installed as

@file{/usr/local/bin/gcc-3.1}.

@file{/usr/local/bin/gcc-3.1}.

@item --program-transform-name=@var{pattern}

@item --program-transform-name=@var{pattern}

Applies the @samp{sed} script @var{pattern} to be applied to the names

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

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

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

semicolons.  For example, if you want the @samp{gcc} program name to be

transformed to the installed program @file{/usr/local/bin/myowngcc} and

transformed to the installed program @file{/usr/local/bin/myowngcc} and

the @samp{g++} program name to be transformed to

the @samp{g++} program name to be transformed to

@file{/usr/local/bin/gspecial++} without changing other program names,

@file{/usr/local/bin/gspecial++} without changing other program names,

you could use the pattern

you could use the pattern

@option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'}

@option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'}

to achieve this effect.

to achieve this effect.

All three options can be combined and used together, resulting in more

All three options can be combined and used together, resulting in more

complex conversion patterns.  As a basic rule, @var{prefix} (and

complex conversion patterns.  As a basic rule, @var{prefix} (and

@var{suffix}) are prepended (appended) before further transformations

@var{suffix}) are prepended (appended) before further transformations

can happen with a special transformation script @var{pattern}.

can happen with a special transformation script @var{pattern}.

As currently implemented, this option only takes effect for native

As currently implemented, this option only takes effect for native

builds; cross compiler binaries' names are not transformed even when a

builds; cross compiler binaries' names are not transformed even when a

transformation is explicitly asked for by one of these options.

transformation is explicitly asked for by one of these options.

For native builds, some of the installed programs are also installed

For native builds, some of the installed programs are also installed

with the target alias in front of their name, as in

with the target alias in front of their name, as in

@samp{i686-pc-linux-gnu-gcc}.  All of the above transformations happen

@samp{i686-pc-linux-gnu-gcc}.  All of the above transformations happen

before the target alias is prepended to the name---so, specifying

before the target alias is prepended to the name---so, specifying

@option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the

@option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the

resulting binary would be installed as

resulting binary would be installed as

@file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}.

@file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}.

As a last shortcoming, none of the installed Ada programs are

As a last shortcoming, none of the installed Ada programs are

transformed yet, which will be fixed in some time.

transformed yet, which will be fixed in some time.

@item --with-local-prefix=@var{dirname}

@item --with-local-prefix=@var{dirname}

Specify the

Specify the

installation directory for local include files.  The default is

installation directory for local include files.  The default is

@file{/usr/local}.  Specify this option if you want the compiler to

@file{/usr/local}.  Specify this option if you want the compiler to

search directory @file{@var{dirname}/include} for locally installed

search directory @file{@var{dirname}/include} for locally installed

header files @emph{instead} of @file{/usr/local/include}.

header files @emph{instead} of @file{/usr/local/include}.

You should specify @option{--with-local-prefix} @strong{only} if your

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 has a different convention (not @file{/usr/local}) for where to put

site-specific files.

site-specific files.

The default value for @option{--with-local-prefix} is @file{/usr/local}

The default value for @option{--with-local-prefix} is @file{/usr/local}

regardless of the value of @option{--prefix}.  Specifying

regardless of the value of @option{--prefix}.  Specifying

@option{--prefix} has no effect on which directory GCC searches for

@option{--prefix} has no effect on which directory GCC searches for

local header files.  This may seem counterintuitive, but actually it is

local header files.  This may seem counterintuitive, but actually it is

logical.

logical.

The purpose of @option{--prefix} is to specify where to @emph{install

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

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

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

programs---perhaps many others.  (GCC installs its own header files in

another directory which is based on the @option{--prefix} value.)

another directory which is based on the @option{--prefix} value.)

Both the local-prefix include directory and the GCC-prefix include

Both the local-prefix include directory and the GCC-prefix include

directory are part of GCC's ``system include'' directories.  Although these

directory are part of GCC's ``system include'' directories.  Although these

two directories are not fixed, they need to be searched in the proper

two directories are not fixed, they need to be searched in the proper

order for the correct processing of the include_next directive.  The

order for the correct processing of the include_next directive.  The

local-prefix include directory is searched before the GCC-prefix

local-prefix include directory is searched before the GCC-prefix

include directory.  Another characteristic of system include directories

include directory.  Another characteristic of system include directories

is that pedantic warnings are turned off for headers in these directories.

is that pedantic warnings are turned off for headers in these directories.

Some autoconf macros add @option{-I @var{directory}} options to the

Some autoconf macros add @option{-I @var{directory}} options to the

compiler command line, to ensure that directories containing installed

compiler command line, to ensure that directories containing installed

packages' headers are searched.  When @var{directory} is one of GCC's

packages' headers are searched.  When @var{directory} is one of GCC's

system include directories, GCC will ignore the option so that system

system include directories, GCC will ignore the option so that system

directories continue to be processed in the correct order.  This

directories continue to be processed in the correct order.  This

may result in a search order different from what was specified but the

may result in a search order different from what was specified but the

directory will still be searched.

directory will still be searched.

GCC automatically searches for ordinary libraries using

GCC automatically searches for ordinary libraries using

@env{GCC_EXEC_PREFIX}.  Thus, when the same installation prefix is

@env{GCC_EXEC_PREFIX}.  Thus, when the same installation prefix is

used for both GCC and packages, GCC will automatically search for

used for both GCC and packages, GCC will automatically search for

both headers and libraries.  This provides a configuration that is

both headers and libraries.  This provides a configuration that is

easy to use.  GCC behaves in a manner similar to that when it is

easy to use.  GCC behaves in a manner similar to that when it is

installed as a system compiler in @file{/usr}.

installed as a system compiler in @file{/usr}.

Sites that need to install multiple versions of GCC may not want to

Sites that need to install multiple versions of GCC may not want to

use the above simple configuration.  It is possible to use the

use the above simple configuration.  It is possible to use the

@option{--program-prefix}, @option{--program-suffix} and

@option{--program-prefix}, @option{--program-suffix} and

@option{--program-transform-name} options to install multiple versions

@option{--program-transform-name} options to install multiple versions

into a single directory, but it may be simpler to use different prefixes

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

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

site-specific files for each version.  It will then be necessary for

users to specify explicitly the location of local site libraries

users to specify explicitly the location of local site libraries

(e.g., with @env{LIBRARY_PATH}).

(e.g., with @env{LIBRARY_PATH}).

The same value can be used for both @option{--with-local-prefix} and

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

@option{--prefix} provided it is not @file{/usr}.  This can be used

to avoid the default search of @file{/usr/local/include}.

to avoid the default search of @file{/usr/local/include}.

@strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!

@strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!

The directory you use for @option{--with-local-prefix} @strong{must not}

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

contain any of the system's standard header files.  If it did contain

them, certain programs would be miscompiled (including GNU Emacs, on

them, certain programs would be miscompiled (including GNU Emacs, on

certain targets), because this would override and nullify the header

certain targets), because this would override and nullify the header

file corrections made by the @command{fixincludes} script.

file corrections made by the @command{fixincludes} script.

Indications are that people who use this option use it based on mistaken

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

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

install part of GCC@.  Perhaps they make this assumption because

installing GCC creates the directory.

installing GCC creates the directory.

@item --enable-shared[=@var{package}[,@dots{}]]

@item --enable-shared[=@var{package}[,@dots{}]]

Build shared versions of libraries, if shared libraries are supported on

Build shared versions of libraries, if shared libraries are supported on

the target platform.  Unlike GCC 2.95.x and earlier, shared libraries

the target platform.  Unlike GCC 2.95.x and earlier, shared libraries

are enabled by default on all platforms that support 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

If a list of packages is given as an argument, build shared libraries

only for the listed packages.  For other packages, only static libraries

only for the listed packages.  For other packages, only static libraries

will be built.  Package names currently recognized in the GCC tree are

will be built.  Package names currently recognized in the GCC tree are

@samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not

@samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not

@samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc},

@samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc},

@samp{ada}, @samp{libada}, @samp{libjava} and @samp{libobjc}.

@samp{ada}, @samp{libada}, @samp{libjava} and @samp{libobjc}.

Note @samp{libiberty} does not support shared libraries at all.

Note @samp{libiberty} does not support shared libraries at all.

Use @option{--disable-shared} to build only static libraries.  Note that

Use @option{--disable-shared} to build only static libraries.  Note that

@option{--disable-shared} does not accept a list of package names as

@option{--disable-shared} does not accept a list of package names as

argument, only @option{--enable-shared} does.

argument, only @option{--enable-shared} does.

@item @anchor{with-gnu-as}--with-gnu-as

@item @anchor{with-gnu-as}--with-gnu-as

Specify that the compiler should assume that the

Specify that the compiler should assume that the

assembler it finds is the GNU assembler.  However, this does not modify

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

the rules to find an assembler and will result in confusion if the

assembler found is not actually the GNU assembler.  (Confusion may also

assembler found is not actually the GNU assembler.  (Confusion may also

result if the compiler finds the GNU assembler but has not been

result if the compiler finds the GNU assembler but has not been

configured with @option{--with-gnu-as}.)  If you have more than one

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

assembler installed on your system, you may want to use this option in

connection with @option{--with-as=@var{pathname}} or

connection with @option{--with-as=@var{pathname}} or

@option{--with-build-time-tools=@var{pathname}}.

@option{--with-build-time-tools=@var{pathname}}.

The following systems are the only ones where it makes a difference

The following systems are the only ones where it makes a difference

whether you use the GNU assembler.  On any other system,

whether you use the GNU assembler.  On any other system,

@option{--with-gnu-as} has no effect.

@option{--with-gnu-as} has no effect.

@itemize @bullet

@itemize @bullet

@item @samp{hppa1.0-@var{any}-@var{any}}

@item @samp{hppa1.0-@var{any}-@var{any}}

@item @samp{hppa1.1-@var{any}-@var{any}}

@item @samp{hppa1.1-@var{any}-@var{any}}

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

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

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

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

@end itemize

@end itemize

@item @anchor{with-as}--with-as=@var{pathname}

@item @anchor{with-as}--with-as=@var{pathname}

Specify that the compiler should use the assembler pointed to by

Specify that the compiler should use the assembler pointed to by

@var{pathname}, rather than the one found by the standard rules to find

@var{pathname}, rather than the one found by the standard rules to find

an assembler, which are:

an assembler, which are:

@itemize @bullet

@itemize @bullet

@item

@item

Unless GCC is being built with a cross compiler, check the

Unless GCC is being built with a cross compiler, check the

@file{@var{libexec}/gcc/@var{target}/@var{version}} directory.

@file{@var{libexec}/gcc/@var{target}/@var{version}} directory.

@var{libexec} defaults to @file{@var{exec-prefix}/libexec};

@var{libexec} defaults to @file{@var{exec-prefix}/libexec};

@var{exec-prefix} defaults to @var{prefix}, which

@var{exec-prefix} defaults to @var{prefix}, which

defaults to @file{/usr/local} unless overridden by the

defaults to @file{/usr/local} unless overridden by the

@option{--prefix=@var{pathname}} switch described above.  @var{target}

@option{--prefix=@var{pathname}} switch described above.  @var{target}

is the target system triple, such as @samp{sparc-sun-solaris2.7}, and

is the target system triple, such as @samp{sparc-sun-solaris2.7}, and

@var{version} denotes the GCC version, such as 3.0.

@var{version} denotes the GCC version, such as 3.0.

@item

@item

If the target system is the same that you are building on, check

If the target system is the same that you are building on, check

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

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

Sun Solaris 2).

Sun Solaris 2).