gcc/INSTALL/configure.html - Issue 3050029: [gcc] GCC 4.5.0=>4.5.1

Unified Diff: gcc/INSTALL/configure.html

Issue 3050029: [gcc] GCC 4.5.0=>4.5.1 (Closed) Base URL: ssh://git@gitrw.chromium.org:9222/nacl-toolchain.git

Patch Set: Created 10 years, 5 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View side-by-side diff with in-line comments

Index: gcc/INSTALL/configure.html

diff --git a/gcc/INSTALL/configure.html b/gcc/INSTALL/configure.html

index 40d681517e2bd0595e6dbfc71a553f0ddafc68bc..15a3fdd83c45b63d5dc2a75d8abf4e01c11a2a58 100644

--- a/gcc/INSTALL/configure.html

+++ b/gcc/INSTALL/configure.html

@@ -3,7 +3,7 @@

<title>Installing GCC: Configuration</title>

-<meta name="generator" content="makeinfo 4.13">

+<meta name="generator" content="makeinfo 4.12">

<!--

@@ -51,8 +51,8 @@ for both native and cross targets.

GCC; we use <var>objdir</var> to refer to the toplevel build/object directory.

If you obtained the sources via SVN, <var>srcdir</var> must refer to the top

-<samp>gcc</samp> directory, the one where the <samp>MAINTAINERS</samp> can be found,

-and not its <samp>gcc</samp> subdirectory, otherwise the build will fail.

+<samp>gcc</samp> directory, the one where the <samp>MAINTAINERS</samp> file can be

+found, and not its <samp>gcc</samp> subdirectory, otherwise the build will fail.

If either <var>srcdir</var> or <var>objdir</var> is located on an automounted NFS

file system, the shell's built-in <samp>pwd</samp> command will return

@@ -63,7 +63,7 @@ variable to an automounter-aware <samp>pwd</samp> c

phases.

First, we highly recommend that GCC be built into a

-separate directory than the sources which does not reside

+separate directory from the sources which does not reside

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

where <var>srcdir</var> == <var>objdir</var> should still work, but doesn't

get extensive testing; building where <var>objdir</var> is a subdirectory

@@ -115,12 +115,12 @@ if you determine that they are not bugs in your modifications.

<ul>

<li>GCC has code to correctly determine the correct value for <var>target</var>

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

-provide a configure target when configuring a native compiler.

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

+not provide a configure target when configuring a native compiler.

<li><var>target</var> must be specified as <samp>--target=<var>target</var></samp>

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

-m68k-coff, sh-elf, etc.

+m68k-elf, sh-elf, etc.

<li>Specifying just <var>target</var> instead of <samp>--target=<var>target</var></samp>

implies that the host defaults to <var>target</var>.

@@ -168,21 +168,34 @@ The default is <samp><var>exec-prefix</var>/libexec</s

<dt><code>--with-slibdir=</code><var>dirname</var><dd>Specify the installation directory for the shared libgcc library. The

default is <samp><var>libdir</var></samp>.

+ <dt><code>--datarootdir=</code><var>dirname</var><dd>Specify the root of the directory tree for read-only architecture-independent

+data files referenced by GCC. The default is <samp><var>prefix</var>/share</samp>.

<dt><code>--infodir=</code><var>dirname</var><dd>Specify the installation directory for documentation in info format.

-The default is <samp><var>prefix</var>/info</samp>.

+The default is <samp><var>datarootdir</var>/info</samp>.

<dt><code>--datadir=</code><var>dirname</var><dd>Specify the installation directory for some architecture-independent

-data files referenced by GCC. The default is <samp><var>prefix</var>/share</samp>.

+data files referenced by GCC. The default is <samp><var>datarootdir</var></samp>.

+ <dt><code>--docdir=</code><var>dirname</var><dd>Specify the installation directory for documentation files (other

+than Info) for GCC. The default is <samp><var>datarootdir</var>/doc</samp>.

+ <dt><code>--htmldir=</code><var>dirname</var><dd>Specify the installation directory for HTML documentation files.

+The default is <samp><var>docdir</var></samp>.

+ <dt><code>--pdfdir=</code><var>dirname</var><dd>Specify the installation directory for PDF documentation files.

+The default is <samp><var>docdir</var></samp>.

<dt><code>--mandir=</code><var>dirname</var><dd>Specify the installation directory for manual pages. The default is

-<samp><var>prefix</var>/man</samp>. (Note that the manual pages are only extracts from

-the full GCC manuals, which are provided in Texinfo format. The manpages

+<samp><var>datarootdir</var>/man</samp>. (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.)

<dt><code>--with-gxx-include-dir=</code><var>dirname</var><dd>Specify

-the installation directory for G++ header files. The default is

-<samp><var>prefix</var>/include/c++/<var>version</var></samp>.

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

+on other configuration options, and differs between cross and native

+configurations.

</dl>

@@ -423,6 +436,46 @@ sysv, aix.

</dl>

+ <dt><code>--with-multilib-list=</code><var>list</var><dt><code>--without-multilib-list</code><dd>Specify what multilibs to build.

+Currently only implemented for sh*-*-*.

+ <var>list</var> is a comma separated list of CPU names. These must be of the

+form <code>sh*</code> or <code>m*</code> (in which case they match the compiler option

+for that processor). The list should not contain any endian options -

+these are handled by <samp>--with-endian</samp>.

+ If <var>list</var> is empty, then there will be no multilibs for extra

+processors. The multilib for the secondary endian remains enabled.

+ As a special case, if an entry in the list starts with a <code>!</code>

+(exclamation point), then it is added to the list of excluded multilibs.

+Entries of this sort should be compatible with ‘<samp>MULTILIB_EXCLUDES</samp>’

+(once the leading <code>!</code> has been stripped).

+ If <samp>--with-multilib-list</samp> is not given, then a default set of

+multilibs is selected based on the value of <samp>--target</samp>. This is

+usually the complete set of libraries, but some targets imply a more

+specialized subset.

+ Example 1: to configure a compiler for SH4A only, but supporting both

+endians, with little endian being the default:

+ <pre class="smallexample"> --with-cpu=sh4a --with-endian=little,big --with-multilib-list=

+</pre>

+ Example 2: to configure a compiler for both SH4A and SH4AL-DSP, but with

+only little endian SH4AL:

+ <pre class="smallexample"> --with-cpu=sh4a --with-endian=little,big --with-multilib-list=sh4al,!mb/m4al

+</pre>

+ <dt><code>--with-endian=</code><var>endians</var><dd>Specify what endians to use.

+Currently only implemented for sh*-*-*.

+ <var>endians</var> may be one of the following:

+ <dl>

+<dt><code>big</code><dd>Use big endian exclusively.

+ <dt><code>little</code><dd>Use little endian exclusively.

+ <dt><code>big,little</code><dd>Use big endian by default. Provide a multilib for little endian.

+ <dt><code>little,big</code><dd>Use little endian by default. Provide a multilib for big endian.

+</dl>

<dt><code>--enable-threads</code><dd>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.

@@ -458,7 +511,8 @@ missing and thus this setting will cause a known bootstrap failure.)

<dt><code>posix95</code><dd>Generic POSIX/Unix95 thread support.

<dt><code>rtems</code><dd>RTEMS thread support.

<dt><code>single</code><dd>Disable thread support, should work for all platforms.

- <dt><code>solaris</code><dd>Sun Solaris 2 thread support.

+ <dt><code>solaris</code><dd>Sun Solaris 2/Unix International thread support. Only use this if you

+really need to use this legacy API instead of the default, ‘<samp>posix</samp>’.

<dt><code>vxworks</code><dd>VxWorks thread support.

<dt><code>win32</code><dd>Microsoft Win32 API thread support.

<dt><code>nks</code><dd>Novell Kernel Services thread support.

@@ -479,8 +533,8 @@ This is an alias for <samp>--enable-tls=no</samp>.

This option is only supported on some targets, including ARM, i386, M68k,

PowerPC, and SPARC. The <samp>--with-cpu-32</samp> and

<samp>--with-cpu-64</samp> options specify separate default CPUs for

-32-bit and 64-bit modes; these options are only supported for i386 and

-x86-64.

+32-bit and 64-bit modes; these options are only supported for i386,

+x86-64 and PowerPC.

<dt><code>--with-schedule=</code><var>cpu</var><dt><code>--with-arch=</code><var>cpu</var><dt><code>--with-arch-32=</code><var>cpu</var><dt><code>--with-arch-64=</code><var>cpu</var><dt><code>--with-tune=</code><var>cpu</var><dt><code>--with-tune-32=</code><var>cpu</var><dt><code>--with-tune-64=</code><var>cpu</var><dt><code>--with-abi=</code><var>abi</var><dt><code>--with-fpu=</code><var>type</var><dt><code>--with-float=</code><var>type</var><dd>These configure options provide default values for the <samp>-mschedule=</samp>,

<samp>-march=</samp>, <samp>-mtune=</samp>, <samp>-mabi=</samp>, and <samp>-mfpu=</samp>

@@ -491,6 +545,10 @@ of the arguments depend on the target.

<dt><code>--with-mode=</code><var>mode</var><dd>Specify if the compiler should default to <samp>-marm</samp> or <samp>-mthumb</samp>.

This option is only supported on ARM targets.

+ <dt><code>--with-fpmath=sse</code><dd>Specify if the compiler should default to <samp>-msse2</samp> and

+<samp>-mfpmath=sse</samp>. This option is only supported on i386 and

+x86-64 targets.

<dt><code>--with-divide=</code><var>type</var><dd>Specify how the compiler should generate code for checking for

division by zero. This option is only supported on the MIPS target.

The possibilities for <var>type</var> are:

@@ -510,6 +568,12 @@ not provide them.

<dt><code>--without-llsc</code><dd>On MIPS targets, make <samp>-mno-llsc</samp> the default when no

<samp>-mllsc</samp> option is passed.

+ <dt><code>--with-synci</code><dd>On MIPS targets, make <samp>-msynci</samp> the default when no

+<samp>-mno-synci</samp> option is passed.

+ <dt><code>--without-synci</code><dd>On MIPS targets, make <samp>-mno-synci</samp> the default when no

+<samp>-msynci</samp> option is passed. This is the default.

<dt><code>--with-mips-plt</code><dd>On MIPS targets, make use of copy relocations and PLTs.

These features are extensions to the traditional

SVR4-based MIPS ABIs and require support from GNU binutils

@@ -526,11 +590,12 @@ only available on systems with GNU libc. When enabled, this will cause

libraries should be optimized for code space instead of code speed.

This is the default for the m32r platform.

- <dt><code>--disable-cpp</code><dd>Specify that a user visible <samp>cpp</samp> program should not be installed.

<dt><code>--with-cpp-install-dir=</code><var>dirname</var><dd>Specify that the user visible <samp>cpp</samp> program should be installed

in <samp><var>prefix</var>/<var>dirname</var>/cpp</samp>, in addition to <var>bindir</var>.

+ <dt><code>--enable-comdat</code><dd>Enable COMDAT group support. This is primarily used to override the

+automatically detected value.

<dt><code>--enable-initfini-array</code><dd>Force the use of sections <code>.init_array</code> and <code>.fini_array</code>

(instead of <code>.init</code> and <code>.fini</code>) for constructors and

destructors. Option <samp>--disable-initfini-array</samp> has the

@@ -538,8 +603,11 @@ opposite effect. If neither option is specified, the configure script

will try to guess whether the <code>.init_array</code> and

<code>.fini_array</code> sections are supported and, if they are, use them.

- <dt><code>--enable-maintainer-mode</code><dd>The build rules that

-regenerate the GCC master message catalog <samp>gcc.pot</samp> are normally

+ <dt><code>--enable-build-with-cxx</code><dd>Build GCC using a C++ compiler rather than a C compiler. This is an

+experimental option which may become the default in a later release.

+ <dt><code>--enable-maintainer-mode</code><dd>The build rules that regenerate the Autoconf and Automake output files as

+well as the GCC master message catalog <samp>gcc.pot</samp> are normally

disabled. This is because it can only be rebuilt if the complete source

tree is present. If you have changed the sources and want to rebuild the

catalog, configuring with <samp>--enable-maintainer-mode</samp> will enable

@@ -553,7 +621,7 @@ this process, you can configure with <samp>--disable-bootst

<dt><code>--enable-bootstrap</code><dd>In special cases, you may want to perform a 3-stage build

even if the target and host triplets are different.

-This could happen when the host can run code compiled for

+This is possible when the host can run code compiled for

the target (e.g. host is i686-linux, target is i486-linux).

Starting from GCC 4.2, to do this you have to configure explicitly

with <samp>--enable-bootstrap</samp>.

@@ -632,8 +700,10 @@ powerpc-linux for powerpc64-linux, only generates 32-bit code. This

option enables the 32-bit target to be a bi-arch compiler, which is

useful when you want a bi-arch compiler that defaults to 32-bit, and

you are building a bi-arch or multi-arch binutils in a combined tree.

-Currently, this option only affects sparc-linux, powerpc-linux and

-x86-linux.

+On mips-linux, this will build a tri-arch compiler (ABI o32/n32/64),

+defaulted to o32.

+Currently, this option only affects sparc-linux, powerpc-linux, x86-linux

+and mips-linux.

<dt><code>--enable-secureplt</code><dd>This option enables <samp>-msecure-plt</samp> by default for powerpc-linux.

See “RS/6000 and PowerPC Options” in the main manual

@@ -690,7 +760,7 @@ assertions will make the compiler and runtime slightly faster but

increase the risk of undetected internal errors causing wrong code to be

generated.

- <dt><code>--disable-stage1-checking</code> <dt><code>--enable-stage1-checking</code><dt><code>--enable-stage1-checking=</code><var>list</var><dd>If no <samp>--enable-checking</samp> option is specified the stage1

+ <dt><code>--disable-stage1-checking</code><dt><code>--enable-stage1-checking</code><dt><code>--enable-stage1-checking=</code><var>list</var><dd>If no <samp>--enable-checking</samp> option is specified the stage1

compiler will be built with ‘<samp>yes</samp>’ checking enabled, otherwise

the stage1 checking flags are the same as specified by

<samp>--enable-checking</samp>. To build the stage1 compiler with

@@ -764,17 +834,21 @@ When neither of these configure options are used, the default will be

128-bit <code>long double</code> when built against GNU C Library 2.4 and later,

64-bit <code>long double</code> otherwise.

- <dt><code>--with-gmp=</code><var>pathname</var><dt><code>--with-gmp-include=</code><var>pathname</var><dt><code>--with-gmp-lib=</code><var>pathname</var><dt><code>--with-mpfr=</code><var>pathname</var><dt><code>--with-mpfr-include=</code><var>pathname</var><dt><code>--with-mpfr-lib=</code><var>pathname</var><dd>If you do not have GMP (the GNU Multiple Precision library) and the

-MPFR Libraries installed in a standard location and you want to build

-GCC, you can explicitly specify the directory where they are installed

-(‘<samp>--with-gmp=<var>gmpinstalldir</var></samp>’,

-‘<samp>--with-mpfr=<var>mpfrinstalldir</var></samp>’). The

+ <dt><code>--with-gmp=</code><var>pathname</var><dt><code>--with-gmp-include=</code><var>pathname</var><dt><code>--with-gmp-lib=</code><var>pathname</var><dt><code>--with-mpfr=</code><var>pathname</var><dt><code>--with-mpfr-include=</code><var>pathname</var><dt><code>--with-mpfr-lib=</code><var>pathname</var><dt><code>--with-mpc=</code><var>pathname</var><dt><code>--with-mpc-include=</code><var>pathname</var><dt><code>--with-mpc-lib=</code><var>pathname</var><dd>If you do not have GMP (the GNU Multiple Precision library), the MPFR

+library and/or the MPC library installed in a standard location and

+you want to build GCC, you can explicitly specify the directory where

+they are installed (‘<samp>--with-gmp=<var>gmpinstalldir</var></samp>’,

+‘<samp>--with-mpfr=<var>mpfrinstalldir</var></samp>’,

+‘<samp>--with-mpc=<var>mpcinstalldir</var></samp>’). The

<samp>--with-gmp=<var>gmpinstalldir</var></samp> option is shorthand for

<samp>--with-gmp-lib=<var>gmpinstalldir</var>/lib</samp> and

<samp>--with-gmp-include=<var>gmpinstalldir</var>/include</samp>. Likewise the

<samp>--with-mpfr=<var>mpfrinstalldir</var></samp> option is shorthand for

<samp>--with-mpfr-lib=<var>mpfrinstalldir</var>/lib</samp> and

-<samp>--with-mpfr-include=<var>mpfrinstalldir</var>/include</samp>. If these

+<samp>--with-mpfr-include=<var>mpfrinstalldir</var>/include</samp>, also the

+<samp>--with-mpc=<var>mpcinstalldir</var></samp> option is shorthand for

+<samp>--with-mpc-lib=<var>mpcinstalldir</var>/lib</samp> and

+<samp>--with-mpc-include=<var>mpcinstalldir</var>/include</samp>. If these

shorthand assumptions are not correct, you can use the explicit

include and lib options directly.

@@ -800,20 +874,70 @@ linking with a shared copy of PPL, you probably do not need this

option; shared library dependencies will cause the linker to search

for the standard C++ library automatically.

+ <dt><code>--with-stage1-ldflags=</code><var>flags</var><dd>This option may be used to set linker flags to be used when linking

+stage 1 of GCC. These are also used when linking GCC if configured with

+<samp>--disable-bootstrap</samp>. By default no special flags are used.

+ <dt><code>--with-stage1-libs=</code><var>libs</var><dd>This option may be used to set libraries to be used when linking stage 1

+of GCC. These are also used when linking GCC if configured with

+<samp>--disable-bootstrap</samp>. The default is the argument to

+<samp>--with-host-libstdcxx</samp>, if specified.

+ <dt><code>--with-boot-ldflags=</code><var>flags</var><dd>This option may be used to set linker flags to be used when linking

+stage 2 and later when bootstrapping GCC. By default no special flags

+are used.

+ <dt><code>--with-boot-libs=</code><var>libs</var><dd>This option may be used to set libraries to be used when linking stage 2

+and later when bootstrapping GCC. The default is the argument to

+<samp>--with-host-libstdcxx</samp>, if specified.

<dt><code>--with-debug-prefix-map=</code><var>map</var><dd>Convert source directory names using <samp>-fdebug-prefix-map</samp> when

building runtime libraries. ‘<samp><var>map</var></samp>’ is a space-separated

list of maps of the form ‘<samp><var>old</var>=<var>new</var></samp>’.

- </dl>

+ <dt><code>--enable-linker-build-id</code><dd>Tells GCC to pass <samp>--build-id</samp> option to the linker for all final

+links (links performed without the <samp>-r</samp> or <samp>--relocatable</samp>

+option), if the linker supports it. If you specify

+<samp>--enable-linker-build-id</samp>, but your linker does not

+support <samp>--build-id</samp> option, a warning is issued and the

+<samp>--enable-linker-build-id</samp> option is ignored. The default is off.

+ <dt><code>--enable-gnu-unique-object</code><dt><code>--disable-gnu-unique-object</code><dd>Tells GCC to use the gnu_unique_object relocation for C++ template

+static data members and inline function local statics. Enabled by

+default for a native toolchain with an assembler that accepts it and

+GLIBC 2.11 or above, otherwise disabled.

+ <dt><code>--enable-lto</code><dd>Enable support for link-time optimization (LTO). This is enabled by

+default if a working libelf implementation is found (see

+<samp>--with-libelf</samp>).

+ <dt><code>--with-libelf=</code><var>pathname</var><dt><code>--with-libelf-include=</code><var>pathname</var><dt><code>--with-libelf-lib=</code><var>pathname</var><dd>If you do not have libelf installed in a standard location and you

+want to enable support for link-time optimization (LTO), you can

+explicitly specify the directory where libelf is installed

+(‘<samp>--with-libelf=<var>libelfinstalldir</var></samp>’). The

+<samp>--with-libelf=<var>libelfinstalldir</var></samp> option is shorthand for

+<samp>--with-libelf-include=<var>libelfinstalldir</var>/include</samp>

+<samp>--with-libelf-lib=<var>libelfinstalldir</var>/lib</samp>.

+ <dt><code>--enable-gold</code><dd>Enable support for using <samp>gold</samp> as the linker. If gold support is

+enabled together with <samp>--enable-lto</samp>, an additional directory

+<samp>lto-plugin</samp> will be built. The code in this directory is a

+plugin for gold that allows the link-time optimizer to extract object

+files with LTO information out of library archives. See

+<samp>-flto</samp> and <samp>-fwhopr</samp> for details.

+</dl>

<h4 class="subheading"><a name="TOC3"></a>Cross-Compiler-Specific Options</h4>

The following options only apply to building cross compilers.

<dl>

<dt><code>--with-sysroot</code><dt><code>--with-sysroot=</code><var>dir</var><dd>Tells GCC to consider <var>dir</var> as the root of a tree that contains a

(subset of) the root filesystem of the target operating system.

Target system headers, libraries and run-time object files will be

-searched in there. The specified directory is not copied into the

+searched in there. More specifically, this acts as if

+<samp>--sysroot=<var>dir</var></samp> was added to the default options of the built

+compiler. The specified directory is not copied into the

install tree, unlike the options <samp>--with-headers</samp> and

<samp>--with-libs</samp> that this option obsoletes. The default value,

in case <samp>--with-sysroot</samp> is not given an argument, is

@@ -821,6 +945,11 @@ in case <samp>--with-sysroot</samp> is not given an

subdirectory of <samp>${exec_prefix}</samp>, then it will be found relative to

the GCC binaries if the installation tree is moved.

+ This option affects the system root for the compiler used to build

+target libraries (which runs on the build system) and the compiler newly

+installed with <code>make install</code>; it does not affect the compiler which is

+used to build GCC itself.

<dt><code>--with-build-sysroot</code><dt><code>--with-build-sysroot=</code><var>dir</var><dd>Tells GCC to consider <var>dir</var> as the system root (see

<samp>--with-sysroot</samp>) while building target libraries, instead of

the directory specified with <samp>--with-sysroot</samp>. This option is

@@ -847,7 +976,7 @@ will be run on these files to make them compatible with GCC.

compiler. When crossing to GNU/Linux, you need the headers so GCC

can build the exception handling for libgcc.

- <dt><code>--with-libs</code><dt><code>--with-libs=``</code><var>dir1</var> <var>dir2</var><code> ... </code><var>dirN</var><code>''</code><dd>Deprecated in favor of <samp>--with-sysroot</samp>.

+ <dt><code>--with-libs</code><dt><code>--with-libs="</code><var>dir1</var> <var>dir2</var><code> ... </code><var>dirN</var><code>"</code><dd>Deprecated in favor of <samp>--with-sysroot</samp>.

Specifies a list of directories which contain the target runtime

libraries. These libraries will be copied into the <samp>gcc</samp> install

directory. If the directory list is omitted, this option has no

@@ -863,7 +992,7 @@ that will be used while building GCC itself. This option can be useful

if the directory layouts are different between the system you are building

GCC on, and the system where you will deploy it.

- For example, on a <samp>ia64-hp-hpux</samp> system, you may have the GNU

+ For example, on an ‘<samp>ia64-hp-hpux</samp>’ system, you may have the GNU

assembler and linker in <samp>/usr/bin</samp>, and the native tools in a

different path, and build a toolchain that expects to find the

native tools in <samp>/usr/bin</samp>.

@@ -1016,6 +1145,8 @@ not specified, then the Python modules are installed in $(prefix)/share/python.

<dt><code>--enable-aot-compile-rpm</code><dd>Adds aot-compile-rpm to the list of installed scripts.

+ <dt><code>--enable-browser-plugin</code><dd>Build the gcjwebplugin web browser plugin.

<dl>

<dt><code>ansi</code><dd>Use the single-byte <code>char</code> and the Win32 A functions natively,

translating to and from UNICODE when using these functions. If

« no previous file with comments | « gcc/INSTALL/build.html ('k') | gcc/INSTALL/download.html » ('j') | no next file with comments »