[haiku-commits] buildtools: btrev43101 - in gcc: gcc/doc gcc/fortran INSTALL gcc .

From: jerome.duval@xxxxxxxxx
To: haiku-commits@xxxxxxxxxxxxx
Date: Sat, 11 Jul 2015 11:00:58 +0200 (CEST)

btrev43101 adds 2 changesets to branch 'master'
old head: 5ba2e2476452449349c88068283581e445472e19
new head: 3801b878c2c2bfea5a115bcbd75b56d3da05bc3d
overview:
http://cgit.haiku-os.org/buildtools/log/?qt=range&q=3801b878c2c2+%5E5ba2e2476452

----------------------------------------------------------------------------

a1af220a6fa1: import gcc 4.8.5

3801b878c2c2: Merge gcc 4.8.5

[ Jérôme Duval <jerome.duval@xxxxxxxxx> ]

----------------------------------------------------------------------------

433 files changed, 65001 insertions(+), 56673 deletions(-)
gcc/ChangeLog | 9 +
gcc/INSTALL/binaries.html | 199 +-
gcc/INSTALL/build.html | 510 +-
gcc/INSTALL/configure.html | 2184 +-
gcc/INSTALL/download.html | 163 +-
gcc/INSTALL/finalinstall.html | 277 +-
gcc/INSTALL/gfdl.html | 470 +-
gcc/INSTALL/index.html | 214 +-
gcc/INSTALL/old.html | 302 +-
gcc/INSTALL/prerequisites.html | 543 +-
gcc/INSTALL/specific.html | 1928 +-
gcc/INSTALL/test.html | 411 +-
gcc/LAST_UPDATED | 2 +-
gcc/MD5SUMS | 807 +-
gcc/NEWS | 203 +-
gcc/config/ChangeLog | 4 +
gcc/configure | 2 +-
gcc/configure.ac | 2 +-
gcc/contrib/ChangeLog | 4 +
gcc/contrib/reghunt/ChangeLog | 4 +
gcc/contrib/regression/ChangeLog | 4 +
gcc/fixincludes/ChangeLog | 4 +
gcc/gcc/BASE-VER | 2 +-
gcc/gcc/ChangeLog | 1127 +-
gcc/gcc/DATESTAMP | 2 +-
gcc/gcc/ada/ChangeLog | 9 +
gcc/gcc/ada/gcc-interface/utils2.c | 6 +
gcc/gcc/alias.c | 206 +-
gcc/gcc/builtins.c | 41 +
gcc/gcc/c-family/ChangeLog | 21 +
gcc/gcc/c-family/c-common.c | 3 +-
gcc/gcc/c-family/c-opts.c | 6 +
gcc/gcc/c/ChangeLog | 13 +
gcc/gcc/c/c-typeck.c | 3 +-
gcc/gcc/cfgexpand.c | 2 +-
gcc/gcc/combine.c | 4 +-
gcc/gcc/config.gcc | 30 +-
gcc/gcc/config/aarch64/aarch64.md | 12 +-
gcc/gcc/config/aarch64/atomics.md | 12 +-
gcc/gcc/config/aarch64/iterators.md | 3 +
gcc/gcc/config/alpha/alpha.c | 7 +-
gcc/gcc/config/alpha/alpha.md | 67 +-
gcc/gcc/config/arm/arm.c | 16 +-
gcc/gcc/config/arm/arm.h | 4 +-
gcc/gcc/config/arm/arm.md | 40 +-
gcc/gcc/config/avr/avr.c | 3 +-
gcc/gcc/config/avr/avr.md | 48 +-
gcc/gcc/config/i386/avx2intrin.h | 18 +
gcc/gcc/config/i386/emmintrin.h | 16 +
gcc/gcc/config/i386/i386.c | 78 +-
gcc/gcc/config/i386/i386.md | 50 +-
gcc/gcc/config/i386/predicates.md | 9 +-
gcc/gcc/config/i386/sse.md | 12 +-
gcc/gcc/config/microblaze/linux.h | 3 +
gcc/gcc/config/pa/pa-linux.h | 2 +-
gcc/gcc/config/pa/pa.c | 65 +-
gcc/gcc/config/rs6000/altivec.md | 4 +-
gcc/gcc/config/rs6000/crypto.md | 13 +-
gcc/gcc/config/rs6000/default64.h | 10 +-
gcc/gcc/config/rs6000/driver-rs6000.c | 8 +-
gcc/gcc/config/rs6000/htm.md | 287 +-
gcc/gcc/config/rs6000/htmxlintrin.h | 3 +-
gcc/gcc/config/rs6000/linux64.h | 8 +-
gcc/gcc/config/rs6000/rs6000-builtin.def | 107 +-
gcc/gcc/config/rs6000/rs6000-cpus.def | 4 +-
gcc/gcc/config/rs6000/rs6000-tables.opt | 5 +-
gcc/gcc/config/rs6000/rs6000.c | 1546 +-
gcc/gcc/config/rs6000/rs6000.h | 8 +-
gcc/gcc/config/rs6000/rs6000.md | 12 +-
gcc/gcc/config/rs6000/rs6000.opt | 28 +-
gcc/gcc/config/rs6000/t-fprules | 6 -
gcc/gcc/config/rs6000/t-linux | 14 +-
gcc/gcc/config/rs6000/vsx.md | 17 +-
gcc/gcc/config/s390/2827.md | 8 +-
gcc/gcc/config/s390/s390.c | 270 +-
gcc/gcc/config/s390/s390.md | 25 +
gcc/gcc/config/s390/s390.opt | 12 +-
gcc/gcc/config/sh/sh.md | 32 +-
gcc/gcc/config/sh/t-sh | 6 +-
gcc/gcc/cp/ChangeLog | 27 +
gcc/gcc/cp/decl2.c | 2 +-
gcc/gcc/cp/name-lookup.c | 2 +-
gcc/gcc/cp/parser.c | 7 +-
gcc/gcc/cp/semantics.c | 13 +-
gcc/gcc/cp/typeck.c | 6 +
gcc/gcc/df.h | 28 +-
gcc/gcc/doc/aot-compile.1 | 39 +-
gcc/gcc/doc/cpp.1 | 83 +-
gcc/gcc/doc/cpp.info | 3648 +-
gcc/gcc/doc/cpp.texi | 2 +-
gcc/gcc/doc/cppinternals.info | 700 +-
gcc/gcc/doc/cppinternals.texi | 4 +-
gcc/gcc/doc/extend.texi | 34 +-
gcc/gcc/doc/fsf-funding.7 | 41 +-
gcc/gcc/doc/g++.1 | 987 +-
gcc/gcc/doc/gc-analyze.1 | 39 +-
gcc/gcc/doc/gcc.1 | 987 +-
gcc/gcc/doc/gcc.info | 37654 ++++++++--------
gcc/gcc/doc/gcc.texi | 2 +-
[ *** stats truncated: 334 lines dropped *** ]

############################################################################

Commit: a1af220a6fa14bb85a5983b7e53741db7c5aa72f
URL: http://cgit.haiku-os.org/buildtools/commit/?id=a1af220a6fa1
Author: Jérôme Duval <jerome.duval@xxxxxxxxx>
Date: Sat Jul 11 07:14:42 2015 UTC

import gcc 4.8.5

----------------------------------------------------------------------------

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 21aed67..3dd1ce5 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,12 @@
+2015-06-23 Release Manager
+
+ * GCC 4.8.5 released.
+
+2015-05-03 Matthias Klose <doko@xxxxxxxxxx>
+
+ * configure.ac: Match $host configured with triplets.
+ * configure: Regenerate.
+
2014-12-19 Release Manager

* GCC 4.8.4 released.
diff --git a/gcc/INSTALL/binaries.html b/gcc/INSTALL/binaries.html
index de321c3..8955200 100644
--- a/gcc/INSTALL/binaries.html
+++ b/gcc/INSTALL/binaries.html
@@ -1,164 +1,111 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
-<html>
-
-
-<head>
-<title>Installing GCC</title>
-
-<meta name="description" content="Installing GCC">
-<meta name="keywords" content="Installing GCC">
-<meta name="resource-type" content="document">
-<meta name="distribution" content="global">
-<meta name="Generator" content="makeinfo">
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<style type="text/css">
-
-</style>
-
-
+ funds for GNU development.-->
+<meta http-equiv="Content-Style-Type" content="text/css">
+<style type="text/css"></style>
</head>
-
-<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
-<h1 class="settitle" align="center">Installing GCC</h1>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<a name="index-Binaries"></a>
-<a name="index-Installing-GCC_003a-Binaries"></a>
-
-We are often asked about pre-compiled versions of GCC. While we cannot
-provide these for all platforms, below you’ll find links to binaries for
+<body>
+<h1 class="settitle">Installing GCC: Binaries</h1>
+<a name="index-Binaries-1"></a><a
name="index-Installing-GCC_003a-Binaries-2"></a>
+We are often asked about pre-compiled versions of GCC. While we cannot
+provide these for all platforms, below you'll find links to binaries for
various platforms where creating them by yourself is not easy due to various
reasons.
-
-Please note that we did not create these binaries, nor do we
+
+ Please note that we did not create these binaries, nor do we
support them. If you have any problems installing them, please
contact their makers.
-
-<ul>
-<li> AIX:
-<ul>
-<li> <a href="http://www.bullfreeware.com";>Bull’s Freeware and Shareware
Archive for AIX</a>;

-</li><li> <a href="http://pware.hvcc.edu";>Hudson Valley Community College Open
Source Software for IBM System p</a>;
+ <ul>
+<li>AIX:
+ <ul>
+<li><a href="http://www.bullfreeware.com";>Bull's Freeware and Shareware
Archive for AIX</a>;

-</li><li> <a href="http://www.perzl.org/aix/";>AIX 5L and 6 Open Source
Packages</a>.
-</li></ul>
+ <li><a href="http://pware.hvcc.edu";>Hudson Valley Community College
Open Source Software for IBM System p</a>;

-</li><li> DOS—<a href="http://www.delorie.com/djgpp/";>DJGPP</a>.
+ <li><a href="http://www.perzl.org/aix/";>AIX 5L and 6 Open Source
Packages</a>.
+</ul>

-</li><li> Renesas H8/300[HS]—<a
href="http://h8300-hms.sourceforge.net/";>GNU
-Development Tools for the Renesas H8/300[HS] Series</a>.
+ <li>DOS—<a href="http://www.delorie.com/djgpp/";>DJGPP</a>.

-</li><li> HP-UX:
-<ul>
-<li> <a href="http://hpux.connect.org.uk/";>HP-UX Porting Center</a>;
+ <li>Renesas H8/300[HS]—<a
href="http://h8300-hms.sourceforge.net/";>GNU Development Tools for the Renesas
H8/300[HS] Series</a>.

-</li><li> <a
href="ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/";>Binaries
for HP-UX 11.00 at Aachen University of Technology</a>.
-</li></ul>
+ <li>HP-UX:
+ <ul>
+<li><a href="http://hpux.connect.org.uk/";>HP-UX Porting Center</a>;

-</li><li> <a href="http://www.sco.com/skunkware/devtools/index.html#gcc";>SCO
-OpenServer/Unixware</a>.
+ <li><a
href="ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/";>Binaries
for HP-UX 11.00 at Aachen University of Technology</a>.
+</ul>

-</li><li> Solaris 2 (SPARC, Intel):
-<ul>
-<li> <a href="http://www.opencsw.org/";>OpenCSW</a>
+ <li><a href="http://www.sco.com/skunkware/devtools/index.html#gcc";>SCO
OpenServer/Unixware</a>.

-</li><li> <a href="http://jupiterrise.com/tgcware/";>TGCware</a>
-</li></ul>
+ <li>Solaris 2 (SPARC, Intel):
+ <ul>
+<li><a href="http://www.opencsw.org/";>OpenCSW</a>

-</li><li> Microsoft Windows:
-<ul>
-<li> The <a href="http://sourceware.org/cygwin/";>Cygwin</a> project;
-</li><li> The <a href="http://www.mingw.org/";>MinGW</a> project.
-</li></ul>
+ <li><a href="http://jupiterrise.com/tgcware/";>TGCware</a>
+</ul>

-</li><li> <a href="ftp://ftp.thewrittenword.com/packages/by-name/";>The
-Written Word</a> offers binaries for
+ <li>Microsoft Windows:
+ <ul>
+<li>The <a href="http://sourceware.org/cygwin/";>Cygwin</a> project;
+<li>The <a href="http://www.mingw.org/";>MinGW</a> project.
+</ul>
+
+ <li><a href="ftp://ftp.thewrittenword.com/packages/by-name/";>The Written
Word</a> offers binaries for
AIX 4.3.3, 5.1 and 5.2,
GNU/Linux (i386),
HP-UX 10.20, 11.00, and 11.11, and
Solaris/SPARC 2.5.1, 2.6, 7, 8, 9 and 10.

-</li><li> <a href="http://www.openpkg.org/";>OpenPKG</a> offers binaries for
quite a
+ <li><a href="http://www.openpkg.org/";>OpenPKG</a> offers binaries for
quite a
number of platforms.

-</li><li> The <a href="http://gcc.gnu.org/wiki/GFortranBinaries";>GFortran
Wiki</a> has
-links to GNU Fortran binaries for several platforms.
-</li></ul>
-
-<hr />
-<a href="./index.html">Return to the GCC Installation page</a>
-
-
-
-
-
+ <li>The <a href="http://gcc.gnu.org/wiki/GFortranBinaries";>GFortran
Wiki</a> has
+links to GNU Fortran binaries for several platforms.
+</ul>

+ <hr />
+<a href="./index.html">Return to the GCC Installation page</a>

+
+
+
+
+
+</body></html>

-</body>
-</html>
diff --git a/gcc/INSTALL/build.html b/gcc/INSTALL/build.html
index a44612a..0e5fa3c 100644
--- a/gcc/INSTALL/build.html
+++ b/gcc/INSTALL/build.html
@@ -1,458 +1,378 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
-<html>
-
-
-<head>
-<title>Installing GCC</title>
-
-<meta name="description" content="Installing GCC">
-<meta name="keywords" content="Installing GCC">
-<meta name="resource-type" content="document">
-<meta name="distribution" content="global">
-<meta name="Generator" content="makeinfo">
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<style type="text/css">
-
-</style>
-
-
+ funds for GNU development.-->
+<meta http-equiv="Content-Style-Type" content="text/css">
+<style type="text/css"></style>
</head>
-
-<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
-<h1 class="settitle" align="center">Installing GCC</h1>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<a name="index-Installing-GCC_003a-Building"></a>
-
-Now that GCC is configured, you are ready to build the compiler and
+<body>
+<h1 class="settitle">Installing GCC: Building</h1>
+<a name="index-Installing-GCC_003a-Building-1"></a>
+Now that GCC is configured, you are ready to build the compiler and
runtime libraries.
-
-Some commands executed when making the compiler may fail (return a
-nonzero status) and be ignored by <code>make</code>. These failures, which
+
+ Some commands executed when making the compiler may fail (return a
+nonzero status) and be ignored by <samp>make</samp>. These failures, which
are often due to files that were not found, are expected, and can safely
be ignored.
-
-It is normal to have compiler warnings when compiling certain files.
+
+ It is normal to have compiler warnings when compiling certain files.
Unless you are a GCC developer, you can generally ignore these warnings
unless they cause compilation to fail. Developers should attempt to fix
any warnings encountered, however they can temporarily continue past
warnings-as-errors by specifying the configure flag
-<samp>--disable-werror</samp>.
-
-On certain old systems, defining certain environment variables such as
-<code>CC</code> can interfere with the functioning of <code>make</code>.
-
-If you encounter seemingly strange errors when trying to build the
+<samp>--disable-werror</samp>.
+
+ On certain old systems, defining certain environment variables such as
+<samp>CC</samp> can interfere with the functioning of
<samp>make</samp>.
+
+ If you encounter seemingly strange errors when trying to build the
compiler in a directory other than the source directory, it could be
because you have previously configured the compiler in the source
directory. Make sure you have done all the necessary preparations.
-
-If you build GCC on a BSD system using a directory stored in an old System
-V file system, problems may occur in running <code>fixincludes</code> if the
-System V file system doesn’t support symbolic links. These problems
+
+ If you build GCC on a BSD system using a directory stored in an old
System
+V file system, problems may occur in running <samp>fixincludes</samp> if the
+System V file system doesn't support symbolic links. These problems
result in a failure to fix the declaration of <code>size_t</code> in
-<samp>sys/types.h</samp>. If you find that <code>size_t</code> is a signed
type and
+<samp>sys/types.h</samp>. If you find that
<code>size_t</code> is a signed type and
that type mismatches occur, this could be the cause.
-
-The solution is not to use such a directory for building GCC.
-
-Similarly, when building from SVN or snapshots, or if you modify
-<samp>*.l</samp> files, you need the Flex lexical analyzer generator
-installed. If you do not modify <samp>*.l</samp> files, releases contain
+
+ The solution is not to use such a directory for building GCC.
+
+ Similarly, when building from SVN or snapshots, or if you modify
+<samp>*.l</samp> files, you need the Flex lexical
analyzer generator
+installed. If you do not modify <samp>*.l</samp>
files, releases contain
the Flex-generated files and you do not need Flex installed to build
them. There is still one Flex-based lexical analyzer (part of the
build machinery, not of GCC itself) that is used even if you only
build the C front end.
-
-When building from SVN or snapshots, or if you modify Texinfo
+
+ When building from SVN or snapshots, or if you modify Texinfo
documentation, you need version 4.7 or later of Texinfo installed if you
want Info documentation to be regenerated. Releases contain Info
documentation pre-built for the unmodified documentation in the release.
-
-<a name="Building-a-native-compiler"></a>
-<h3 class="section">Building a native compiler</h3>
+
+<h3 class="section"><a name="TOC0"></a>Building a native compiler</h3>

For a native build, the default configuration is to perform
-a 3-stage bootstrap of the compiler when ‘<samp>make</samp>’ is
invoked.
+a 3-stage bootstrap of the compiler when ‘<samp>make</samp>’ is invoked.
This will build the entire GCC system and ensure that it compiles
-itself correctly. It can be disabled with the <samp>--disable-bootstrap</samp>
-parameter to ‘<samp>configure</samp>’, but bootstrapping is
suggested because
+itself correctly. It can be disabled with the <samp>--disable-bootstrap</samp>
+parameter to ‘<samp>configure</samp>’,
but bootstrapping is suggested because
the compiler will be tested more completely and could also have
better performance.
-
-The bootstrapping process will complete the following steps:
-
-<ul>
-<li> Build tools necessary to build the compiler.

-</li><li> Perform a 3-stage bootstrap of the compiler. This includes building
+ The bootstrapping process will complete the following steps:
+
+ <ul>
+<li>Build tools necessary to build the compiler.
+
+ <li>Perform a 3-stage bootstrap of the compiler. This includes building
three times the target tools for use by the compiler such as binutils
(bfd, binutils, gas, gprof, ld, and opcodes) if they have been
individually linked or moved into the top level GCC source tree before
configuring.

-</li><li> Perform a comparison test of the stage2 and stage3 compilers.
+ <li>Perform a comparison test of the stage2 and stage3 compilers.

-</li><li> Build runtime libraries using the stage3 compiler from the previous
step.
+ <li>Build runtime libraries using the stage3 compiler from the previous
step.

-</li></ul>
+ </ul>

-If you are short on disk space you might consider ‘<samp>make
-bootstrap-lean</samp>’ instead. The sequence of compilation is the
+ If you are short on disk space you might consider ‘<samp>make
+bootstrap-lean</samp>’ instead. The sequence of compilation is
the
same described above, but object files from the stage1 and
stage2 of the 3-stage bootstrap of the compiler are deleted as
soon as they are no longer needed.
-
-If you wish to use non-default GCC flags when compiling the stage2
+
+ If you wish to use non-default GCC flags when compiling the stage2
and stage3 compilers, set <code>BOOT_CFLAGS</code> on the command line when
-doing ‘<samp>make</samp>’. For example, if you want to save
additional space
+doing ‘<samp>make</samp>’. For example,
if you want to save additional space
during the bootstrap and in the final installation as well, you can
build the compiler binaries without debugging information as in the
following example. This will save roughly 40% of disk space both for
the bootstrap and the final installation. (Libraries will still contain
debugging information.)
-
-<div class="smallexample">
-<pre class="smallexample">make BOOT_CFLAGS='-O' bootstrap
-</pre></div>

-You can place non-default optimization flags into <code>BOOT_CFLAGS</code>;
they
-are less well tested here than the default of ‘<samp>-g
-O2</samp>’, but should
+<pre class="smallexample"> make BOOT_CFLAGS='-O' bootstrap
+</pre>
+ You can place non-default optimization flags into
<code>BOOT_CFLAGS</code>; they
+are less well tested here than the default of ‘<samp>-g -O2</samp>’, but should
still work. In a few cases, you may find that you need to specify special
-flags such as <samp>-msoft-float</samp> here to complete the bootstrap; or,
+flags such as <samp>-msoft-float</samp> here to
complete the bootstrap; or,
if the native compiler miscompiles the stage1 compiler, you may need
to work around this, by choosing <code>BOOT_CFLAGS</code> to avoid the parts
-of the stage1 compiler that were miscompiled, or by using ‘<samp>make
-bootstrap4</samp>’ to increase the number of stages of bootstrap.
-
-<code>BOOT_CFLAGS</code> does not apply to bootstrapped target libraries.
+of the stage1 compiler that were miscompiled, or by using ‘<samp>make
+bootstrap4</samp>’ to increase the number of stages of bootstrap.
+
+ <code>BOOT_CFLAGS</code> does not apply to bootstrapped target
libraries.
Since these are always compiled with the compiler currently being
bootstrapped, you can use <code>CFLAGS_FOR_TARGET</code> to modify their
-compilation flags, as for non-bootstrapped target libraries.
+compilation flags, as for non-bootstrapped target libraries.
Again, if the native compiler miscompiles the stage1 compiler, you may
need to work around this by avoiding non-working parts of the stage1
compiler. Use <code>STAGE1_TFLAGS</code> to this end.
-
-If you used the flag <samp>--enable-languages=…</samp> to restrict
-the compilers to be built, only those you’ve actually enabled will be
+
+ If you used the flag <samp>--enable-languages=...</samp> to restrict
+the compilers to be built, only those you've actually enabled will be
built. This will of course only build those runtime libraries, for
which the particular compiler has been built. Please note,
-that re-defining <code>LANGUAGES</code> when calling
‘<samp>make</samp>’
+that re-defining <samp>LANGUAGES</samp> when calling
‘<samp>make</samp>’
does not work anymore!
-
-If the comparison of stage2 and stage3 fails, this normally indicates
+
+ If the comparison of stage2 and stage3 fails, this normally indicates
that the stage2 compiler has compiled GCC incorrectly, and is therefore
a potentially serious bug which you should investigate and report. (On
a few systems, meaningful comparison of object files is impossible; they
always appear “different”. If you encounter this problem, you will
-need to disable comparison in the <samp>Makefile</samp>.)
-
-If you do not want to bootstrap your compiler, you can configure with
-<samp>--disable-bootstrap</samp>. In particular cases, you may want to
+need to disable comparison in the <samp>Makefile</samp>.)
+
+ If you do not want to bootstrap your compiler, you can configure with
+<samp>--disable-bootstrap</samp>. In particular
cases, you may want to
bootstrap your compiler even if the target system is not the same as
the one you are building on: for example, you could build a
<code>powerpc-unknown-linux-gnu</code> toolchain on a
<code>powerpc64-unknown-linux-gnu</code> host. In this case, pass
-<samp>--enable-bootstrap</samp> to the configure script.
-
-<code>BUILD_CONFIG</code> can be used to bring in additional customization
-to the build. It can be set to a whitespace-separated list of names.
-For each such <code>NAME</code>, top-level
<samp>config/<code>NAME</code>.mk</samp> will
-be included by the top-level <samp>Makefile</samp>, bringing in any settings
+<samp>--enable-bootstrap</samp> to the configure
script.
+
+ <code>BUILD_CONFIG</code> can be used to bring in additional
customization
+to the build. It can be set to a whitespace-separated list of names.
+For each such <code>NAME</code>, top-level <samp>config/<code>NAME</code>.mk</samp> will
+be included by the top-level <samp>Makefile</samp>,
bringing in any settings
it contains. The default <code>BUILD_CONFIG</code> can be set using the
-configure option <samp>--with-build-config=<code>NAME</code>...</samp>. Some
+configure option <samp>--with-build-config=<code>NAME</code>...</samp>. Some
examples of supported build configurations are:
-
-<dl compact="compact">
-<dt>‘<samp>bootstrap-O1</samp>’</dt>
-<dd>Removes any <samp>-O</samp>-started option from
<code>BOOT_CFLAGS</code>, and adds
-<samp>-O1</samp> to it. ‘<samp>BUILD_CONFIG=bootstrap-O1</samp>’
is equivalent to
-‘<samp>BOOT_CFLAGS='-g -O1'</samp>’.
-
-</dd>
-<dt>‘<samp>bootstrap-O3</samp>’</dt>
-<dd>Analogous to <code>bootstrap-O1</code>.
-
-</dd>
-<dt>‘<samp>bootstrap-lto</samp>’</dt>
-<dd>Enables Link-Time Optimization for host tools during bootstrapping.
-‘<samp>BUILD_CONFIG=bootstrap-lto</samp>’ is equivalent to adding
-<samp>-flto</samp> to ‘<samp>BOOT_CFLAGS</samp>’.
-
-</dd>
-<dt>‘<samp>bootstrap-debug</samp>’</dt>
-<dd>Verifies that the compiler generates the same executable code, whether
+
+ <dl>
+<dt>‘<samp>bootstrap-O1</samp>’<dd>Removes any <samp>-O</samp>-started option from <code>BOOT_CFLAGS</code>,
and adds
+<samp>-O1</samp> to it. ‘<samp>BUILD_CONFIG=bootstrap-O1</samp>’ is equivalent to
+‘<samp>BOOT_CFLAGS='-g -O1'</samp>’.
+
+ <dt>‘<samp>bootstrap-O3</samp>’<dd>Analogous to
<code>bootstrap-O1</code>.
+
+ <dt>‘<samp>bootstrap-lto</samp>’<dd>Enables Link-Time
Optimization for host tools during bootstrapping.
+‘<samp>BUILD_CONFIG=bootstrap-lto</samp>’ is equivalent to
adding
+<samp>-flto</samp> to ‘<samp>BOOT_CFLAGS</samp>’.
+
+ <dt>‘<samp>bootstrap-debug</samp>’<dd>Verifies that the compiler
generates the same executable code, whether
or not it is asked to emit debug information. To this end, this
option builds stage2 host programs without debug information, and uses
-<samp>contrib/compare-debug</samp> to compare them with the stripped stage3
+<samp>contrib/compare-debug</samp> to compare them
with the stripped stage3
object files. If <code>BOOT_CFLAGS</code> is overridden so as to not enable
-debug information, stage2 will have it, and stage3 won’t. This option
+debug information, stage2 will have it, and stage3 won't. This option
is enabled by default when GCC bootstrapping is enabled, if
<code>strip</code> can turn object files compiled with and without debug
info into identical object files. In addition to better test
coverage, this option makes default bootstraps faster and leaner.
-
-</dd>
-<dt>‘<samp>bootstrap-debug-big</samp>’</dt>
-<dd>Rather than comparing stripped object files, as in
+
+ <dt>‘<samp>bootstrap-debug-big</samp>’<dd>Rather than comparing
stripped object files, as in
<code>bootstrap-debug</code>, this option saves internal compiler dumps
during stage2 and stage3 and compares them as well, which helps catch
additional potential problems, but at a great cost in terms of disk
-space. It can be specified in addition to
‘<samp>bootstrap-debug</samp>’.
-
-</dd>
-<dt>‘<samp>bootstrap-debug-lean</samp>’</dt>
-<dd>This option saves disk space compared with
<code>bootstrap-debug-big</code>,
+space. It can be specified in addition to ‘<samp>bootstrap-debug</samp>’.
+
+ <dt>‘<samp>bootstrap-debug-lean</samp>’<dd>This option saves
disk space compared with <code>bootstrap-debug-big</code>,
but at the expense of some recompilation. Instead of saving the dumps
of stage2 and stage3 until the final compare, it uses
-<samp>-fcompare-debug</samp> to generate, compare and remove the dumps
+<samp>-fcompare-debug</samp> to generate, compare
and remove the dumps
during stage3, repeating the compilation that already took place in
stage2, whose dumps were not saved.
-
-</dd>
-<dt>‘<samp>bootstrap-debug-lib</samp>’</dt>
-<dd>This option tests executable code invariance over debug information
+
+ <dt>‘<samp>bootstrap-debug-lib</samp>’<dd>This option tests
executable code invariance over debug information
generation on target libraries, just like <code>bootstrap-debug-lean</code>
tests it on host programs. It builds stage3 libraries with
-<samp>-fcompare-debug</samp>, and it can be used along with any of the
+<samp>-fcompare-debug</samp>, and it can be used
along with any of the
<code>bootstrap-debug</code> options above.
-
-There aren’t <code>-lean</code> or <code>-big</code> counterparts to
this option
+
+ There aren't <code>-lean</code> or <code>-big</code> counterparts to
this option
because most libraries are only build in stage3, so bootstrap compares
would not get significant coverage. Moreover, the few libraries built
-in stage2 are used in stage3 host programs, so we wouldn’t want to
+in stage2 are used in stage3 host programs, so we wouldn't want to
compile stage2 libraries with different options for comparison purposes.
-
-</dd>
-<dt>‘<samp>bootstrap-debug-ckovw</samp>’</dt>
-<dd>Arranges for error messages to be issued if the compiler built on any
-stage is run without the option <samp>-fcompare-debug</samp>. This is
-useful to verify the full <samp>-fcompare-debug</samp> testing coverage. It
+
+ <dt>‘<samp>bootstrap-debug-ckovw</samp>’<dd>Arranges for error
messages to be issued if the compiler built on any
+stage is run without the option <samp>-fcompare-debug</samp>. This is
+useful to verify the full <samp>-fcompare-debug</samp> testing coverage. It
must be used along with <code>bootstrap-debug-lean</code> and
<code>bootstrap-debug-lib</code>.
-
-</dd>
-<dt>‘<samp>bootstrap-time</samp>’</dt>
-<dd>Arranges for the run time of each program started by the GCC driver,
-built in any stage, to be logged to <samp>time.log</samp>, in the top level of
+
+ <dt>‘<samp>bootstrap-time</samp>’<dd>Arranges for the run time
of each program started by the GCC driver,
+built in any stage, to be logged to <samp>time.log</samp>, in the top level of
the build tree.
-
-</dd>
-</dl>

-<a name="Building-a-cross-compiler"></a>
-<h3 class="section">Building a cross compiler</h3>
+ </dl>
+
+<h3 class="section"><a name="TOC1"></a>Building a cross compiler</h3>

When building a cross compiler, it is not generally possible to do a
3-stage bootstrap of the compiler. This makes for an interesting problem
as parts of GCC can only be built with GCC.
-
-To build a cross compiler, we recommend first building and installing a
+
+ To build a cross compiler, we recommend first building and installing a
native compiler. You can then use the native GCC compiler to build the
cross compiler. The installed native compiler needs to be GCC version
2.95 or later.
-
-If the cross compiler is to be built with support for the Java
+
+ If the cross compiler is to be built with support for the Java
programming language and the ability to compile .java source files is
desired, the installed native compiler used to build the cross
compiler needs to be the same GCC version as the cross compiler. In
addition the cross compiler needs to be configured with
-<samp>--with-ecj-jar=…</samp>.
-
-Assuming you have already installed a native copy of GCC and configured
-your cross compiler, issue the command <code>make</code>, which performs the
+<samp>--with-ecj-jar=...</samp>.
+
+ Assuming you have already installed a native copy of GCC and configured
+your cross compiler, issue the command <samp>make</samp>, which performs the
following steps:
-
-<ul>
-<li> Build host tools necessary to build the compiler.

-</li><li> Build target tools for use by the compiler such as binutils (bfd,
+ <ul>
+<li>Build host tools necessary to build the compiler.
+
+ <li>Build target tools for use by the compiler such as binutils (bfd,
binutils, gas, gprof, ld, and opcodes)
if they have been individually linked or moved into the top level GCC source
tree before configuring.

-</li><li> Build the compiler (single stage only).
+ <li>Build the compiler (single stage only).

-</li><li> Build runtime libraries using the compiler from the previous step.
-</li></ul>
+ <li>Build runtime libraries using the compiler from the previous step.
+</ul>

-Note that if an error occurs in any step the make process will exit.
-
-If you are not building GNU binutils in the same source tree as GCC,
+ Note that if an error occurs in any step the make process will exit.
+
+ If you are not building GNU binutils in the same source tree as GCC,
you will need a cross-assembler and cross-linker installed before
configuring GCC. Put them in the directory
-<samp><var>prefix</var>/<var>target</var>/bin</samp>. Here is a table of the
tools
+<samp><var>prefix</var>/<var>target</var>/bin</samp>. Here is a table of the tools
you should put in this directory:
-
-<dl compact="compact">
-<dt><samp>as</samp></dt>
-<dd>This should be the cross-assembler.
-
-</dd>
-<dt><samp>ld</samp></dt>
-<dd>This should be the cross-linker.
-
-</dd>
-<dt><samp>ar</samp></dt>
-<dd>This should be the cross-archiver: a program which can manipulate
-archive files (linker libraries) in the target machine’s format.
-
-</dd>
-<dt><samp>ranlib</samp></dt>
-<dd>This should be a program to construct a symbol table in an archive file.
-</dd>
+
+ <dl>
+<dt><samp>as</samp><dd>This should be the
cross-assembler.
+
+ <dt><samp>ld</samp><dd>This should be the
cross-linker.
+
+ <dt><samp>ar</samp><dd>This should be the
cross-archiver: a program which can manipulate
+archive files (linker libraries) in the target machine's format.
+
+ <dt><samp>ranlib</samp><dd>This should be a
program to construct a symbol table in an archive file.
</dl>

-The installation of GCC will find these programs in that directory,
+ The installation of GCC will find these programs in that directory,
and copy or link them to the proper place to for the cross-compiler to
find them when run later.
-
-The easiest way to provide these files is to build the Binutils package.
-Configure it with the same <samp>--host</samp> and <samp>--target</samp>
+
+ The easiest way to provide these files is to build the Binutils package.
+Configure it with the same <samp>--host</samp> and
<samp>--target</samp>
options that you use for configuring GCC, then build and install
them. They install their executables automatically into the proper
directory. Alas, they do not support all the targets that GCC
supports.
-
-If you are not building a C library in the same source tree as GCC,
+
+ If you are not building a C library in the same source tree as GCC,
you should also provide the target libraries and headers before
configuring GCC, specifying the directories with
-<samp>--with-sysroot</samp> or <samp>--with-headers</samp> and
-<samp>--with-libs</samp>. Many targets also require “start files”
such
-as <samp>crt0.o</samp> and
-<samp>crtn.o</samp> which are linked into each executable. There may be
several
-alternatives for <samp>crt0.o</samp>, for use with profiling or other
-compilation options. Check your target’s definition of
+<samp>--with-sysroot</samp> or <samp>--with-headers</samp> and
+<samp>--with-libs</samp>. Many targets also
require “start files” such
+as <samp>crt0.o</samp> and
+<samp>crtn.o</samp> which are linked into each
executable. There may be several
+alternatives for <samp>crt0.o</samp>, for use with
profiling or other
+compilation options. Check your target's definition of
<code>STARTFILE_SPEC</code> to find out what start files it uses.
-
-<a name="Building-in-parallel"></a>
-<h3 class="section">Building in parallel</h3>
+
+<h3 class="section"><a name="TOC2"></a>Building in parallel</h3>

GNU Make 3.80 and above, which is necessary to build GCC, support
-building in parallel. To activate this, you can use ‘<samp>make -j
2</samp>’
-instead of ‘<samp>make</samp>’. You can also specify a bigger
number, and
+building in parallel. To activate this, you can use ‘<samp>make -j 2</samp>’
+instead of ‘<samp>make</samp>’. You can
also specify a bigger number, and
in most cases using a value greater than the number of processors in
your machine will result in fewer and shorter I/O latency hits, thus
improving overall throughput; this is especially true for slow drives
and network filesystems.
-
-<a name="Building-the-Ada-compiler"></a>
-<h3 class="section">Building the Ada compiler</h3>
+
+<h3 class="section"><a name="TOC3"></a>Building the Ada compiler</h3>

In order to build GNAT, the Ada compiler, you need a working GNAT
-compiler (GCC version 4.0 or later).
-This includes GNAT tools such as <code>gnatmake</code> and
-<code>gnatlink</code>, since the Ada front end is written in Ada and
+compiler (GCC version 4.0 or later).
+This includes GNAT tools such as <samp>gnatmake</samp> and
+<samp>gnatlink</samp>, since the Ada front end is
written in Ada and
uses some GNAT-specific extensions.
-
-In order to build a cross compiler, it is suggested to install
+
+ In order to build a cross compiler, it is suggested to install
the new compiler as native first, and then use it to build the cross
compiler.
-
-<code>configure</code> does not test whether the GNAT installation works
+
+ <samp>configure</samp> does not test
whether the GNAT installation works
and has a sufficiently recent version; if too old a GNAT version is
-installed, the build will fail unless <samp>--enable-languages</samp> is
+installed, the build will fail unless <samp>--enable-languages</samp> is
used to disable building the Ada front end.
-
-<code>ADA_INCLUDE_PATH</code> and <code>ADA_OBJECT_PATH</code> environment
variables
+
+ <samp>ADA_INCLUDE_PATH</samp> and <samp>ADA_OBJECT_PATH</samp> environment variables
must not be set when building the Ada compiler, the Ada tools, or the
Ada runtime libraries. You can check that your build environment is clean
-by verifying that ‘<samp>gnatls -v</samp>’ lists only one explicit
path in each
+by verifying that ‘<samp>gnatls
-v</samp>’ lists only one explicit path in each
section.
-
-<a name="Building-with-profile-feedback"></a>
-<h3 class="section">Building with profile feedback</h3>
+
+<h3 class="section"><a name="TOC4"></a>Building with profile feedback</h3>

It is possible to use profile feedback to optimize the compiler itself.
This
should result in a faster compiler binary. Experiments done on x86 using gcc
3.3 showed approximately 7 percent speedup on compiling C programs. To
bootstrap the compiler with profile feedback, use <code>make
profiledbootstrap</code>.
-
-When ‘<samp>make profiledbootstrap</samp>’ is run, it will
first build a <code>stage1</code>
+
+ When ‘<samp>make
profiledbootstrap</samp>’ is run, it will first build a
<code>stage1</code>
compiler. This compiler is used to build a <code>stageprofile</code> compiler
instrumented to collect execution counts of instruction and branch
-probabilities. Then runtime libraries are compiled with profile collected.
+probabilities. Then runtime libraries are compiled with profile collected.
Finally a <code>stagefeedback</code> compiler is built using the information
collected.
-
-Unlike standard bootstrap, several additional restrictions apply. The
-compiler used to build <code>stage1</code> needs to support a 64-bit integral
type.
+
+ Unlike standard bootstrap, several additional restrictions apply. The
+compiler used to build <code>stage1</code> needs to support a 64-bit integral
type.
It is recommended to only use GCC for this. Also parallel make is currently
not supported since collisions in profile collecting may occur.
-
-<hr />
-<a href="./index.html">Return to the GCC Installation page</a>
-
-
-
-
-
-
-
-
-<hr>

+ <hr />
+<a href="./index.html">Return to the GCC Installation page</a>

+
+
+
+
+
+
+
+
+</body></html>

-</body>
-</html>
diff --git a/gcc/INSTALL/configure.html b/gcc/INSTALL/configure.html
index 1abc3b9..41ace36 100644
--- a/gcc/INSTALL/configure.html
+++ b/gcc/INSTALL/configure.html
@@ -1,1759 +1,1293 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
-<html>
-
-
-<head>
-<title>Installing GCC</title>
-
-<meta name="description" content="Installing GCC">
-<meta name="keywords" content="Installing GCC">
-<meta name="resource-type" content="document">
-<meta name="distribution" content="global">
-<meta name="Generator" content="makeinfo">
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<style type="text/css">
-
-</style>
-
-
+ funds for GNU development.-->
+<meta http-equiv="Content-Style-Type" content="text/css">
+<style type="text/css"></style>
</head>
-
-<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
-<h1 class="settitle" align="center">Installing GCC</h1>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<a name="index-Configuration"></a>
-<a name="index-Installing-GCC_003a-Configuration"></a>
-
-Like most GNU software, GCC must be configured before it can be built.
+<body>
+<h1 class="settitle">Installing GCC: Configuration</h1>
+<a name="index-Configuration-1"></a><a
name="index-Installing-GCC_003a-Configuration-2"></a>
+Like most GNU software, GCC must be configured before it can be built.
This document describes the recommended configuration procedure
for both native and cross targets.
-
-We use <var>srcdir</var> to refer to the toplevel source directory for
+
+ We use <var>srcdir</var> to refer to the toplevel source directory for
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> 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 <code>pwd</code> command will return
+
+ 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> 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
temporary pathnames. Using these can lead to various sorts of build
-problems. To avoid this issue, set the <code>PWDCMD</code> environment
-variable to an automounter-aware <code>pwd</code> command, e.g.,
-<code>pawd</code> or ‘<samp>amq -w</samp>’, during the
configuration and build
+problems. To avoid this issue, set the <samp>PWDCMD</samp> environment
+variable to an automounter-aware <samp>pwd</samp>
command, e.g.,
+<samp>pawd</samp> or ‘<samp>amq -w</samp>’, during the configuration and build
phases.
-
-First, we highly recommend that GCC be built into a
+
+ First, we highly recommend that GCC be built into a
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
+where <var>srcdir</var> == <var>objdir</var> should still work, but doesn't
get extensive testing; building where <var>objdir</var> is a subdirectory
of <var>srcdir</var> is unsupported.
-
-If you have previously built GCC in the same directory for a
-different target machine, do ‘<samp>make distclean</samp>’ to
delete all files
-that might be invalid. One of the files this deletes is <samp>Makefile</samp>;
-if ‘<samp>make distclean</samp>’ complains that
<samp>Makefile</samp> does not exist
-or issues a message like “don’t know how to make distclean”
it probably
+
+ If you have previously built GCC in the same directory for a
+different target machine, do ‘<samp>make
distclean</samp>’ to delete all files
+that might be invalid. One of the files this deletes is <samp>Makefile</samp>;
+if ‘<samp>make distclean</samp>’
complains that <samp>Makefile</samp> does not exist
+or issues a message like “don't know how to make distclean” it
probably
means that the directory is already suitably clean. However, with the
recommended method of building in a separate <var>objdir</var>, you should
simply use a different <var>objdir</var> for each target.
-
-Second, when configuring a native system, either <code>cc</code> or
-<code>gcc</code> must be in your path or you must set <code>CC</code> in
+
+ Second, when configuring a native system, either <samp>cc</samp> or
+<samp>gcc</samp> must be in your path or you must
set <samp>CC</samp> in
your environment before running configure. Otherwise the configuration
scripts may fail.
-

-To configure GCC:
-
-<div class="smallexample">
-<pre class="smallexample">% mkdir <var>objdir</var>
-% cd <var>objdir</var>
-% <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>]
-</pre></div>
+ To configure GCC:

-<a name="Distributor-options"></a>
-<h3 class="heading">Distributor options</h3>
+<pre class="smallexample"> % mkdir <var>objdir</var>
+ % cd <var>objdir</var>
+ % <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>]
+</pre>
+ <h3 class="heading"><a name="TOC0"></a>Distributor options</h3>

If you will be distributing binary versions of GCC, with modifications
to the source code, you should use the options described in this
section to make clear that your version contains modifications.
-
-<dl compact="compact">
-<dt><code>--with-pkgversion=<var>version</var></code></dt>
-<dd>Specify a string that identifies your package. You may wish
+
+ <dl>
+<dt><code>--with-pkgversion=</code><var>version</var><dd>Specify a string that
identifies your package. You may wish
to include a build number or build date. This version string will be
-included in the output of <code>gcc --version</code>. This suffix does
-not replace the default version string, only the
‘<samp>GCC</samp>’ part.
-
-The default value is ‘<samp>GCC</samp>’.
-
-</dd>
-<dt><code>--with-bugurl=<var>url</var></code></dt>
-<dd>Specify the URL that users should visit if they wish to report a bug.
+included in the output of <samp>gcc
--version</samp>. This suffix does
+not replace the default version string, only the ‘<samp>GCC</samp>’ part.
+
+ The default value is ‘<samp>GCC</samp>’.
+
+ <dt><code>--with-bugurl=</code><var>url</var><dd>Specify the URL that
users should visit if they wish to report a bug.
You are of course welcome to forward bugs reported to you to the FSF,
if you determine that they are not bugs in your modifications.
-
-The default value refers to the FSF’s GCC bug tracker.
-
-</dd>
-</dl>

-<a name="Target-specification"></a>
-<h3 class="heading">Target specification</h3>
-<ul>
-<li> GCC has code to correctly determine the correct value for
<var>target</var>
+ The default value refers to the FSF's GCC bug tracker.
+
+ </dl>
+
+<h3 class="heading"><a name="TOC1"></a>Target specification</h3>
+
+ <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 do
not provide a configure target when configuring a native compiler.

-</li><li> <var>target</var> must be specified as
<samp>--target=<var>target</var></samp>
+ <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-elf, sh-elf, etc.

-</li><li> Specifying just <var>target</var> instead of
<samp>--target=<var>target</var></samp>
-implies that the host defaults to <var>target</var>.
-</li></ul>
+ <li>Specifying just <var>target</var> instead of <samp>--target=<var>target</var></samp>
+implies that the host defaults to <var>target</var>.
+</ul>

-
-<a name="Options-specification"></a>
-<h3 class="heading">Options specification</h3>
+<h3 class="heading"><a name="TOC2"></a>Options specification</h3>

Use <var>options</var> to override several configure time options for
-GCC. A list of supported <var>options</var> follows; ‘<samp>configure
---help</samp>’ may list other options, but those not listed below may not
+GCC. A list of supported <var>options</var> follows; ‘<samp>configure
+--help</samp>’ may list other options, but those not listed below
may not
work and should not normally be used.
-
-Note that each <samp>--enable</samp> option has a corresponding
-<samp>--disable</samp> option and that each <samp>--with</samp> option has a
-corresponding <samp>--without</samp> option.
-
-<dl compact="compact">
-<dt><code>--prefix=<var>dirname</var></code></dt>
-<dd>Specify the toplevel installation
+
+ Note that each <samp>--enable</samp> option
has a corresponding
+<samp>--disable</samp> option and that each
<samp>--with</samp> option has a
+corresponding <samp>--without</samp> option.
+
+ <dl>
+<dt><code>--prefix=</code><var>dirname</var><dd>Specify the toplevel
installation
directory. This is the recommended way to install the tools into a directory
other than the default. The toplevel installation directory defaults to
-<samp>/usr/local</samp>.
-
-We highly recommend against <var>dirname</var> being the
same or a
+<samp>/usr/local</samp>.
+
+ We highly recommend against <var>dirname</var> being
the same or a
subdirectory of <var>objdir</var> or vice versa. If specifying a directory
-beneath a user’s home directory tree, some shells will not expand
-<var>dirname</var> correctly if it contains the ‘<samp>~</samp>’
metacharacter; use
-<code>$HOME</code> instead.
-
-The following standard <code>autoconf</code> options are supported.
Normally you
+beneath a user's home directory tree, some shells will not expand
+<var>dirname</var> correctly if it contains the ‘<samp>~</samp>’ metacharacter; use
+<samp>$HOME</samp> instead.
+
+ The following standard <samp>autoconf</samp> options are supported. Normally you
should not need to use these options.
-<dl compact="compact">
-<dt><code>--exec-prefix=<var>dirname</var></code></dt>
-<dd>Specify the toplevel installation directory for architecture-dependent
+ <dl>
+<dt><code>--exec-prefix=</code><var>dirname</var><dd>Specify the toplevel
installation directory for architecture-dependent
files. The default is <samp><var>prefix</var></samp>.
-
-</dd>
-<dt><code>--bindir=<var>dirname</var></code></dt>
-<dd>Specify the installation directory for the executables called by users
-(such as <code>gcc</code> and <code>g++</code>). The default is
-<samp><var>exec-prefix</var>/bin</samp>.
-
-</dd>
-<dt><code>--libdir=<var>dirname</var></code></dt>
-<dd>Specify the installation directory for object code libraries and
-internal data files of GCC. The default is
<samp><var>exec-prefix</var>/lib</samp>.
-
-</dd>
-<dt><code>--libexecdir=<var>dirname</var></code></dt>
-<dd>Specify the installation directory for internal executables of GCC.
-The default is <samp><var>exec-prefix</var>/libexec</samp>.
-
-</dd>
-<dt><code>--with-slibdir=<var>dirname</var></code></dt>
-<dd>Specify the installation directory for the shared libgcc library. The
+
+ <dt><code>--bindir=</code><var>dirname</var><dd>Specify the
installation directory for the executables called by users
+(such as <samp>gcc</samp> and <samp>g++</samp>). The default is
+<samp><var>exec-prefix</var>/bin</samp>.
+
+ <dt><code>--libdir=</code><var>dirname</var><dd>Specify the
installation directory for object code libraries and
+internal data files of GCC. The default is <samp><var>exec-prefix</var>/lib</samp>.
+
+ <dt><code>--libexecdir=</code><var>dirname</var><dd>Specify the
installation directory for internal executables of GCC.
+The default is <samp><var>exec-prefix</var>/libexec</samp>.
+
+ <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>.
-
-</dd>
-<dt><code>--datarootdir=<var>dirname</var></code></dt>
-<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>.
-
-</dd>
-<dt><code>--infodir=<var>dirname</var></code></dt>
-<dd>Specify the installation directory for documentation in info format.
-The default is <samp><var>datarootdir</var>/info</samp>.
-
-</dd>
-<dt><code>--datadir=<var>dirname</var></code></dt>
-<dd>Specify the installation directory for some architecture-independent
+
+ <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>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>datarootdir</var></samp>.
-
-</dd>
-<dt><code>--docdir=<var>dirname</var></code></dt>
-<dd>Specify the installation directory for documentation files (other
-than Info) for GCC. The default is <samp><var>datarootdir</var>/doc</samp>.
-
-</dd>
-<dt><code>--htmldir=<var>dirname</var></code></dt>
-<dd>Specify the installation directory for HTML documentation files.
+
+ <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>.
-
-</dd>
-<dt><code>--pdfdir=<var>dirname</var></code></dt>
-<dd>Specify the installation directory for PDF documentation files.
+
+ <dt><code>--pdfdir=</code><var>dirname</var><dd>Specify the
installation directory for PDF documentation files.
The default is <samp><var>docdir</var></samp>.
-
-</dd>
-<dt><code>--mandir=<var>dirname</var></code></dt>
-<dd>Specify the installation directory for manual pages. The default is
-<samp><var>datarootdir</var>/man</samp>. (Note that the manual pages are only
extracts
+
+ <dt><code>--mandir=</code><var>dirname</var><dd>Specify the
installation directory for manual pages. The default is
+<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.)
-
-</dd>
-<dt><code>--with-gxx-include-dir=<var>dirname</var></code></dt>
-<dd>Specify
+
+
 <dt><code>--with-gxx-include-dir=</code><var>dirname</var><dd>Specify
the installation directory for G++ header files. The default depends
on other configuration options, and differs between cross and native
configurations.
-
-</dd>
-<dt><code>--with-specs=<var>specs</var></code></dt>
-<dd>Specify additional command line driver SPECS.
+
+ <dt><code>--with-specs=</code><var>specs</var><dd>Specify
additional command line driver SPECS.
This can be useful if you need to turn on a non-standard feature by
-default without modifying the compiler’s source code, for instance
-<samp>--with-specs=%{!fcommon:%{!fno-common:-fno-common}}</samp>.
+default without modifying the compiler's source code, for instance
+<samp>--with-specs=%{!fcommon:%{!fno-common:-fno-common}}</samp>.

See “Spec Files” in the main manual
-
-</dd>
-</dl>

-</dd>
-<dt><code>--program-prefix=<var>prefix</var></code></dt>
-<dd>GCC supports some transformations of the names of its programs when
+ </dl>
+
+ <dt><code>--program-prefix=</code><var>prefix</var><dd>GCC supports
some transformations of the names of its programs when
installing them. This option prepends <var>prefix</var> to the names of
programs to install in <var>bindir</var> (see above). For example, specifying
-<samp>--program-prefix=foo-</samp> would result in
‘<samp>gcc</samp>’
-being installed as <samp>/usr/local/bin/foo-gcc</samp>.
-
-</dd>
-<dt><code>--program-suffix=<var>suffix</var></code></dt>
-<dd>Appends <var>suffix</var> to the names of programs to install in
<var>bindir</var>
-(see above). For example, specifying <samp>--program-suffix=-3.1</samp>
-would result in ‘<samp>gcc</samp>’ being installed as
-<samp>/usr/local/bin/gcc-3.1</samp>.
-
-</dd>
-<dt><code>--program-transform-name=<var>pattern</var></code></dt>
-<dd>Applies the ‘<samp>sed</samp>’ script <var>pattern</var> to
be applied to the names
+<samp>--program-prefix=foo-</samp> would result in
‘<samp>gcc</samp>’
+being installed as <samp>/usr/local/bin/foo-gcc</samp>.
+
+ <dt><code>--program-suffix=</code><var>suffix</var><dd>Appends
<var>suffix</var> to the names of programs to install in <var>bindir</var>
+(see above). For example, specifying <samp>--program-suffix=-3.1</samp>
+would result in ‘<samp>gcc</samp>’ being
installed as
+<samp>/usr/local/bin/gcc-3.1</samp>.
+
+
 <dt><code>--program-transform-name=</code><var>pattern</var><dd>Applies the
‘<samp>sed</samp>’ script
<var>pattern</var> to be applied to the names
of programs to install in <var>bindir</var> (see above). <var>pattern</var>
has to
-consist of one or more basic ‘<samp>sed</samp>’ editing commands,
separated by
-semicolons. For example, if you want the ‘<samp>gcc</samp>’
program name to be
-transformed to the installed program <samp>/usr/local/bin/myowngcc</samp> and
-the ‘<samp>g++</samp>’ program name to be transformed to
-<samp>/usr/local/bin/gspecial++</samp> without changing other program names,
+consist of one or more basic ‘<samp>sed</samp>’ editing commands, separated by
+semicolons. For example, if you want the ‘<samp>gcc</samp>’ program name to be
+transformed to the installed program <samp>/usr/local/bin/myowngcc</samp> and
+the ‘<samp>g++</samp>’ program name to
be transformed to
+<samp>/usr/local/bin/gspecial++</samp> without
changing other program names,
you could use the pattern
-<samp>--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'</samp>
+<samp>--program-transform-name='s/^gcc$/myowngcc/;
s/^g++$/gspecial++/'</samp>
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</var> (and
<var>suffix</var>) are prepended (appended) before further transformations
can happen with a special transformation script <var>pattern</var>.
-
-As currently implemented, this option only takes effect for native
-builds; cross compiler binaries’ names are not transformed even when a
+
+ As currently implemented, this option only takes effect for native
+builds; cross compiler binaries' names are not transformed even when a
transformation is explicitly asked for by one of these options.
-
-For native builds, some of the installed programs are also installed
+
+ For native builds, some of the installed programs are also installed
with the target alias in front of their name, as in
-‘<samp>i686-pc-linux-gnu-gcc</samp>’. All of the above
transformations happen
+‘<samp>i686-pc-linux-gnu-gcc</samp>’.
All of the above transformations happen
before the target alias is prepended to the name—so, specifying
-<samp>--program-prefix=foo-</samp> and <samp>program-suffix=-3.1</samp>, the
+<samp>--program-prefix=foo-</samp> and <samp>program-suffix=-3.1</samp>, the
resulting binary would be installed as
-<samp>/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1</samp>.
-
-As a last shortcoming, none of the installed Ada programs are
+<samp>/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1</samp>.
+
+ As a last shortcoming, none of the installed Ada programs are
transformed yet, which will be fixed in some time.
-
-</dd>
-<dt><code>--with-local-prefix=<var>dirname</var></code></dt>
-<dd>Specify the
+
+ <dt><code>--with-local-prefix=</code><var>dirname</var><dd>Specify the
installation directory for local include files. The default is
-<samp>/usr/local</samp>. Specify this option if you want the compiler to
-search directory <samp><var>dirname</var>/include</samp> for locally installed
-header files instead of <samp>/usr/local/include</samp>.
-
-You should specify <samp>--with-local-prefix</samp> only
if your
-site has a different convention (not <samp>/usr/local</samp>) for where to put
+<samp>/usr/local</samp>. Specify this option if you
want the compiler to
+search directory <samp><var>dirname</var>/include</samp> for locally installed
+header files instead of <samp>/usr/local/include</samp>.
+
+ You should specify <samp>--with-local-prefix</samp> only if your
+site has a different convention (not <samp>/usr/local</samp>) for where to put
site-specific files.
-
-The default value for <samp>--with-local-prefix</samp> is
<samp>/usr/local</samp>
-regardless of the value of <samp>--prefix</samp>. Specifying
-<samp>--prefix</samp> has no effect on which directory GCC searches for
+
+ The default value for <samp>--with-local-prefix</samp> is <samp>/usr/local</samp>
+regardless of the value of <samp>--prefix</samp>.
Specifying
+<samp>--prefix</samp> has no effect on which
directory GCC searches for
local header files. This may seem counterintuitive, but actually it is
logical.
-
-The purpose of <samp>--prefix</samp> is to specify where to install
-GCC. The local header files in <samp>/usr/local/include</samp>—if
you put
+
+ The purpose of <samp>--prefix</samp> is to
specify where to install
+GCC. The local header files in <samp>/usr/local/include</samp>—if you put
any in that directory—are not part of GCC. They are part of other
programs—perhaps many others. (GCC installs its own header files in
-another directory which is based on the <samp>--prefix</samp> value.)
-
-Both the local-prefix include directory and the GCC-prefix include
-directory are part of GCC’s “system include” directories.
Although these
+another directory which is based on the <samp>--prefix</samp> value.)
+
+ Both the local-prefix include directory and the GCC-prefix include
+directory are part of GCC's “system include” directories.
Although these
two directories are not fixed, they need to be searched in the proper
order for the correct processing of the include_next directive. The
local-prefix include directory is searched before the GCC-prefix
include directory. Another characteristic of system include directories
is that pedantic warnings are turned off for headers in these directories.
-
-Some autoconf macros add <samp>-I <var>directory</var></samp> options to the
+
+ Some autoconf macros add <samp>-I
<var>directory</var></samp> options to the
compiler command line, to ensure that directories containing installed
-packages’ headers are searched. When <var>directory</var> is one of
GCC’s
+packages' headers are searched. When <var>directory</var> is one of GCC's
system include directories, GCC will ignore the option so that system
directories continue to be processed in the correct order. This
may result in a search order different from what was specified but the
directory will still be searched.
-
-GCC automatically searches for ordinary libraries using
-<code>GCC_EXEC_PREFIX</code>. Thus, when the same installation prefix is
+
+ GCC automatically searches for ordinary libraries using
+<samp>GCC_EXEC_PREFIX</samp>. Thus, when the same
installation prefix is
used for both GCC and packages, GCC will automatically search for
both headers and libraries. This provides a configuration that is
easy to use. GCC behaves in a manner similar to that when it is
-installed as a system compiler in <samp>/usr</samp>.
-
-Sites that need to install multiple versions of GCC may not want to
+installed as a system compiler in <samp>/usr</samp>.
+
+ Sites that need to install multiple versions of GCC may not want to
use the above simple configuration. It is possible to use the
-<samp>--program-prefix</samp>, <samp>--program-suffix</samp> and
-<samp>--program-transform-name</samp> options to install multiple versions
+<samp>--program-prefix</samp>, <samp>--program-suffix</samp> and
+<samp>--program-transform-name</samp> options to
install multiple versions
into a single directory, but it may be simpler to use different prefixes
-and the <samp>--with-local-prefix</samp> option to specify the location of the
+and the <samp>--with-local-prefix</samp> option to
specify the location of the
site-specific files for each version. It will then be necessary for
users to specify explicitly the location of local site libraries
-(e.g., with <code>LIBRARY_PATH</code>).
-
-The same value can be used for both <samp>--with-local-prefix</samp> and
-<samp>--prefix</samp> provided it is not <samp>/usr</samp>. This can be used
-to avoid the default search of <samp>/usr/local/include</samp>.
-
-Do not specify <samp>/usr</samp> as the
<samp>--with-local-prefix</samp>!
-The directory you use for <samp>--with-local-prefix</samp> must
not
-contain any of the system’s standard header files. If it did contain
+(e.g., with <samp>LIBRARY_PATH</samp>).
+
+ The same value can be used for both <samp>--with-local-prefix</samp> and
+<samp>--prefix</samp> provided it is not
<samp>/usr</samp>. This can be used
+to avoid the default search of <samp>/usr/local/include</samp>.
+
+ Do not specify <samp>/usr</samp> as the <samp>--with-local-prefix</samp>!
+The directory you use for <samp>--with-local-prefix</samp> must not
+contain any of the system's standard header files. If it did contain
them, certain programs would be miscompiled (including GNU Emacs, on
certain targets), because this would override and nullify the header
-file corrections made by the <code>fixincludes</code> script.
-
-Indications are that people who use this option use it based on mistaken
+file corrections made by the <samp>fixincludes</samp> script.
+
+ Indications are that people who use this option use it based on
mistaken
ideas of what it is for. People use it as if it specified where to
install part of GCC. Perhaps they make this assumption because
installing GCC creates the directory.
-
-</dd>
-<dt><code>--with-native-system-header-dir=<var>dirname</var></code></dt>
-<dd>Specifies that <var>dirname</var> is the directory that contains native
system
-header files, rather than <samp>/usr/include</samp>. This option is most
useful
+
+
 <dt><code>--with-native-system-header-dir=</code><var>dirname</var><dd>Specifies
that <var>dirname</var> is the directory that contains native system
+header files, rather than <samp>/usr/include</samp>.
This option is most useful
if you are creating a compiler that should be isolated from the system
as much as possible. It is most commonly used with the
-<samp>--with-sysroot</samp> option and will cause GCC to search
+<samp>--with-sysroot</samp> option and will cause
GCC to search
<var>dirname</var> inside the system root specified by that option.
-
-</dd>
-<dt><code>--enable-shared[=<var>package</var>[,…]]</code></dt>
-<dd>Build shared versions of libraries, if shared libraries are supported on
+
+
 <dt><code>--enable-shared[=</code><var>package</var><code>[,...]]</code><dd>Build
shared versions of libraries, if shared libraries are supported on
the target platform. Unlike GCC 2.95.x and earlier, shared libraries
are enabled by default on all platforms that support shared libraries.
-
-If a list of packages is given as an argument, build shared libraries
+
+ If a list of packages is given as an argument, build shared libraries
only for the listed packages. For other packages, only static libraries
will be built. Package names currently recognized in the GCC tree are
-‘<samp>libgcc</samp>’ (also known as
‘<samp>gcc</samp>’), ‘<samp>libstdc++</samp>’ (not
-‘<samp>libstdc++-v3</samp>’), ‘<samp>libffi</samp>’,
‘<samp>zlib</samp>’, ‘<samp>boehm-gc</samp>’,
-‘<samp>ada</samp>’, ‘<samp>libada</samp>’,
‘<samp>libjava</samp>’, ‘<samp>libgo</samp>’, and
‘<samp>libobjc</samp>’.
-Note ‘<samp>libiberty</samp>’ does not support shared libraries at
all.
-
-Use <samp>--disable-shared</samp> to build only static libraries. Note that
-<samp>--disable-shared</samp> does not accept a list of package names as
-argument, only <samp>--enable-shared</samp> does.
-
-</dd>
-<dt><code><a name="with_002dgnu_002das"></a>--with-gnu-as</code></dt>
-<dd>Specify that the compiler should assume that the
+‘<samp>libgcc</samp>’ (also known as
‘<samp>gcc</samp>’), ‘<samp>libstdc++</samp>’ (not
+‘<samp>libstdc++-v3</samp>’),
‘<samp>libffi</samp>’, ‘<samp>zlib</samp>’, ‘<samp>boehm-gc</samp>’,
+‘<samp>ada</samp>’, ‘<samp>libada</samp>’, ‘<samp>libjava</samp>’, ‘<samp>libgo</samp>’, and ‘<samp>libobjc</samp>’.
+Note ‘<samp>libiberty</samp>’ does not
support shared libraries at all.
+
+ Use <samp>--disable-shared</samp> to build
only static libraries. Note that
+<samp>--disable-shared</samp> does not accept a
list of package names as
+argument, only <samp>--enable-shared</samp> does.
+
+ <dt><code><a
name="with_002dgnu_002das"></a>--with-gnu-as</code><dd>Specify that the
compiler should assume that the
assembler it finds is the GNU assembler. However, this does not modify
the rules to find an assembler and will result in confusion if the
assembler found is not actually the GNU assembler. (Confusion may also
result if the compiler finds the GNU assembler but has not been
-configured with <samp>--with-gnu-as</samp>.) If you have more than one
+configured with <samp>--with-gnu-as</samp>.) If
you have more than one
assembler installed on your system, you may want to use this option in
-connection with <samp>--with-as=<var>pathname</var></samp> or
-<samp>--with-build-time-tools=<var>pathname</var></samp>.
-
-The following systems are the only ones where it makes a difference
+connection with <samp>--with-as=<var>pathname</var></samp> or
+<samp>--with-build-time-tools=<var>pathname</var></samp>.
+
+ The following systems are the only ones where it makes a difference
whether you use the GNU assembler. On any other system,
-<samp>--with-gnu-as</samp> has no effect.
-
-<ul>
-<li> ‘<samp>hppa1.0-<var>any</var>-<var>any</var></samp>’
-</li><li> ‘<samp>hppa1.1-<var>any</var>-<var>any</var></samp>’
-</li><li> ‘<samp>sparc-sun-solaris2.<var>any</var></samp>’
-</li><li>
‘<samp>sparc64-<var>any</var>-solaris2.<var>any</var></samp>’
-</li></ul>
-
-</dd>
-<dt><code><a name="with_002das"></a>--with-as=<var>pathname</var></code></dt>
-<dd>Specify that the compiler should use the assembler pointed to by
+<samp>--with-gnu-as</samp> has no effect.
+
+ <ul>
+<li>‘<samp>hppa1.0-<var>any</var>-<var>any</var></samp>’
+<li>‘<samp>hppa1.1-<var>any</var>-<var>any</var></samp>’
+<li>‘<samp>sparc-sun-solaris2.<var>any</var></samp>’
+<li>‘<samp>sparc64-<var>any</var>-solaris2.<var>any</var></samp>’
+</ul>
+
+ <dt><code><a
name="with_002das"></a>--with-as=</code><var>pathname</var><dd>Specify that the
compiler should use the assembler pointed to by
<var>pathname</var>, rather than the one found by the standard rules to find
an assembler, which are:
-<ul>
-<li> Unless GCC is being built with a cross compiler, check the
-<samp><var>libexec</var>/gcc/<var>target</var>/<var>version</var></samp>
directory.
-<var>libexec</var> defaults to <samp><var>exec-prefix</var>/libexec</samp>;
+ <ul>
+<li>Unless GCC is being built with a cross compiler, check the
+<samp><var>libexec</var>/gcc/<var>target</var>/<var>version</var></samp> directory.
+<var>libexec</var> defaults to <samp><var>exec-prefix</var>/libexec</samp>;
<var>exec-prefix</var> defaults to <var>prefix</var>, which
-defaults to <samp>/usr/local</samp> unless overridden by the
-<samp>--prefix=<var>pathname</var></samp> switch described above.
<var>target</var>
-is the target system triple, such as
‘<samp>sparc-sun-solaris2.7</samp>’, and
+defaults to <samp>/usr/local</samp> unless
overridden by the
+<samp>--prefix=<var>pathname</var></samp> switch
described above. <var>target</var>
+is the target system triple, such as ‘<samp>sparc-sun-solaris2.7</samp>’, and
<var>version</var> denotes the GCC version, such as 3.0.

-</li><li> If the target system is the same that you are building on, check
-operating system specific directories (e.g. <samp>/usr/ccs/bin</samp> on
+ <li>If the target system is the same that you are building on, check
+operating system specific directories (e.g. <samp>/usr/ccs/bin</samp> on
Sun Solaris 2).

-</li><li> Check in the <code>PATH</code> for a tool whose name is prefixed by
the
+ <li>Check in the <samp>PATH</samp> for a
tool whose name is prefixed by the
target system triple.

-</li><li> Check in the <code>PATH</code> for a tool whose name is not prefixed
by the
+ <li>Check in the <samp>PATH</samp> for a
tool whose name is not prefixed by the
target system triple, if the host and target system triple are
the same (in other words, we use a host tool if it can be used for
-the target as well).
-</li></ul>
+the target as well).
+</ul>

-You may want to use <samp>--with-as</samp> if no assembler
+ You may want to use <samp>--with-as</samp>
if no assembler
is installed in the directories listed above, or if you have multiple
assemblers installed and want to choose one that is not found by the
above rules.
-
-</dd>
-<dt><code><a name="with_002dgnu_002dld"></a>--with-gnu-ld</code></dt>
-<dd>Same as <a href="#with-gnu-as"><samp>--with-gnu-as</samp></a>
+
+ <dt><code><a
name="with_002dgnu_002dld"></a>--with-gnu-ld</code><dd>Same as <a
href="#with-gnu-as"><samp>--with-gnu-as</samp></a>
but for the linker.
-
-</dd>
-<dt><code>--with-ld=<var>pathname</var></code></dt>
-<dd>Same as <a href="#with-as"><samp>--with-as</samp></a>
+
+ <dt><code>--with-ld=</code><var>pathname</var><dd>Same as <a
href="#with-as"><samp>--with-as</samp></a>
but for the linker.
-
-</dd>
-<dt><code>--with-stabs</code></dt>
-<dd>Specify that stabs debugging
+
+ <dt><code>--with-stabs</code><dd>Specify that stabs debugging
information should be used instead of whatever format the host normally
uses. Normally GCC uses the same debug format as the host system.
-
-On MIPS based systems and on Alphas, you must specify whether you want
+
+ On MIPS based systems and on Alphas, you must specify whether you want
GCC to create the normal ECOFF debugging format, or to use BSD-style
stabs passed through the ECOFF symbol table. The normal ECOFF debug
format cannot fully handle languages other than C. BSD stabs format can
handle other languages, but it only works with the GNU debugger GDB.
-
-Normally, GCC uses the ECOFF debugging format by default; if you
-prefer BSD stabs, specify <samp>--with-stabs</samp> when you configure GCC.
-
-No matter which default you choose when you configure GCC, the user
-can use the <samp>-gcoff</samp> and <samp>-gstabs+</samp> options to specify
explicitly
+
+ Normally, GCC uses the ECOFF debugging format by default; if you
+prefer BSD stabs, specify <samp>--with-stabs</samp> when you configure GCC.
+
+ No matter which default you choose when you configure GCC, the user
+can use the <samp>-gcoff</samp> and <samp>-gstabs+</samp> options to specify explicitly
the debug format for a particular compilation.
-
-<samp>--with-stabs</samp> is meaningful on the ISC system on the 386, also,
if
-<samp>--with-gas</samp> is used. It selects use of stabs debugging
+
+ <samp>--with-stabs</samp> is meaningful on
the ISC system on the 386, also, if
+<samp>--with-gas</samp> is used. It selects use
of stabs debugging
information embedded in COFF output. This kind of debugging information
supports C++ well; ordinary COFF debugging information does not.
-
-<samp>--with-stabs</samp> is also meaningful on 386 systems running SVR4.
It
+
+ <samp>--with-stabs</samp> is also
meaningful on 386 systems running SVR4. It
selects use of stabs debugging information embedded in ELF output. The
C++ compiler currently (2.6.0) does not support the DWARF debugging
information normally used on 386 SVR4 platforms; stabs provide a
workable alternative. This requires gas and gdb, as the normal SVR4
tools can not generate or interpret stabs.
-
-</dd>
-<dt><code>--with-tls=<var>dialect</var></code></dt>
-<dd>Specify the default TLS dialect, for systems were there is a choice.
+
+ <dt><code>--with-tls=</code><var>dialect</var><dd>Specify the default
TLS dialect, for systems were there is a choice.
For ARM targets, possible values for <var>dialect</var> are <code>gnu</code> or
<code>gnu2</code>, which select between the original GNU dialect and the GNU
TLS
descriptor-based dialect.
-
-</dd>
-<dt><code>--enable-multiarch</code></dt>
-<dd>Specify whether to enable or disable multiarch support. The default is
+
+ <dt><code>--enable-multiarch</code><dd>Specify whether to enable or
disable multiarch support. The default is
to check for glibc start files in a multiarch location, and enable it
if the files are found. The auto detection is enabled for native builds,
-and for cross builds configured with <samp>--with-sysroot</samp>, and without
-<samp>--with-native-system-header-dir</samp>.
+and for cross builds configured with <samp>--with-sysroot</samp>, and without
+<samp>--with-native-system-header-dir</samp>.
More documentation about multiarch can be found at
<a
href="http://wiki.debian.org/Multiarch";>http://wiki.debian.org/Multiarch</a>.
-
-</dd>
-<dt><code>--disable-multilib</code></dt>
-<dd>Specify that multiple target
+
+ <dt><code>--disable-multilib</code><dd>Specify that multiple target
libraries to support different target variants, calling
conventions, etc. should not be built. The default is to build a
predefined set of them.
-
-Some targets provide finer-grained control over which multilibs are built
-(e.g., <samp>--disable-softfloat</samp>):
-<dl compact="compact">
-<dt><code>arm-*-*</code></dt>
-<dd>fpu, 26bit, underscore, interwork, biendian, nofmult.
-
-</dd>
-<dt><code>m68*-*-*</code></dt>
-<dd>softfloat, m68881, m68000, m68020.
-
-</dd>
-<dt><code>mips*-*-*</code></dt>
-<dd>single-float, biendian, softfloat.
-
-</dd>
-<dt><code>powerpc*-*-*, rs6000*-*-*</code></dt>
-<dd>aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
+
+ Some targets provide finer-grained control over which multilibs are
built
+(e.g., <samp>--disable-softfloat</samp>):
+ <dl>
+<dt><code>arm-*-*</code><dd>fpu, 26bit, underscore, interwork, biendian,
nofmult.
+
+ <dt><code>m68*-*-*</code><dd>softfloat, m68881, m68000, m68020.
+
+ <dt><code>mips*-*-*</code><dd>single-float, biendian, softfloat.
+
+ <dt><code>powerpc*-*-*, rs6000*-*-*</code><dd>aix64, pthread,
softfloat, powercpu, powerpccpu, powerpcos, biendian,
sysv, aix.
-
-</dd>
-</dl>

-</dd>
-<dt><code>--with-multilib-list=<var>list</var></code></dt>
-<dt><code>--without-multilib-list</code></dt>
-<dd>Specify what multilibs to build.
+ </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*-*-* and x86-64-*-linux*.
-
-<dl compact="compact">
-<dt><code>sh*-*-*</code></dt>
-<dd><var>list</var> is a comma separated list of CPU names. These must be
of the
+
+ <dl>
+<dt><code>sh*-*-*</code><dd><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
+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>’
+
+ 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
+
+ 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:
-<div class="smallexample">
-<pre class="smallexample">--with-cpu=sh4a --with-endian=little,big
--with-multilib-list=
-</pre></div>

-Example 2: to configure a compiler for both SH4A and SH4AL-DSP, but with
+ 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:
-<div class="smallexample">
-<pre class="smallexample">--with-cpu=sh4a --with-endian=little,big \
---with-multilib-list=sh4al,!mb/m4al
-</pre></div>
-
-</dd>
-<dt><code>x86-64-*-linux*</code></dt>
-<dd><var>list</var> is a comma separated list of <code>m32</code>,
<code>m64</code> and
+ <pre class="smallexample"> --with-cpu=sh4a
--with-endian=little,big \
+ --with-multilib-list=sh4al,!mb/m4al
+</pre>
+ <dt><code>x86-64-*-linux*</code><dd><var>list</var> is a comma
separated list of <code>m32</code>, <code>m64</code> and
<code>mx32</code> to enable 32-bit, 64-bit and x32 run-time libraries,
respectively. If <var>list</var> is empty, then there will be no multilibs
and only the default run-time library will be enabled.
-
-If <samp>--with-multilib-list</samp> is not given, then only 32-bit and
-64-bit run-time libraries will be enabled.
-</dd>
+
+ If <samp>--with-multilib-list</samp>
is not given, then only 32-bit and
+64-bit run-time libraries will be enabled.
</dl>

-</dd>
-<dt><code>--with-endian=<var>endians</var></code></dt>
-<dd>Specify what endians to use.
+ <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 compact="compact">
-<dt><code>big</code></dt>
-<dd>Use big endian exclusively.
-</dd>
-<dt><code>little</code></dt>
-<dd>Use little endian exclusively.
-</dd>
-<dt><code>big,little</code></dt>
-<dd>Use big endian by default. Provide a multilib for little endian.
-</dd>
-<dt><code>little,big</code></dt>
-<dd>Use little endian by default. Provide a multilib for big endian.
-</dd>
+
+ <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>

-</dd>
-<dt><code>--enable-threads</code></dt>
-<dd>Specify that the target
+ <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.
+library, and exception handling for other languages like C++ and Java.
On some systems, this is the default.
-
-In general, the best (and, in many cases, the only known) threading
+
+ In general, the best (and, in many cases, the only known) threading
model available will be configured for use. Beware that on some
systems, GCC has not been taught what threading models are generally
-available for the system. In this case, <samp>--enable-threads</samp> is an
-alias for <samp>--enable-threads=single</samp>.
-
-</dd>
-<dt><code>--disable-threads</code></dt>
-<dd>Specify that threading support should be disabled for the system.
-This is an alias for <samp>--enable-threads=single</samp>.
-
-</dd>
-<dt><code>--enable-threads=<var>lib</var></code></dt>
-<dd>Specify that
+available for the system. In this case, <samp>--enable-threads</samp> is an
+alias for <samp>--enable-threads=single</samp>.
+
+ <dt><code>--disable-threads</code><dd>Specify that threading support
should be disabled for the system.
+This is an alias for <samp>--enable-threads=single</samp>.
+
+ <dt><code>--enable-threads=</code><var>lib</var><dd>Specify that
<var>lib</var> is the thread support library. This affects the Objective-C
compiler and runtime library, and exception handling for other languages
like C++ and Java. The possibilities for <var>lib</var> are:
-
-<dl compact="compact">
-<dt><code>aix</code></dt>
-<dd>AIX thread support.
-</dd>
-<dt><code>dce</code></dt>
-<dd>DCE thread support.
-</dd>
-<dt><code>lynx</code></dt>
-<dd>LynxOS thread support.
-</dd>
-<dt><code>mipssde</code></dt>
-<dd>MIPS SDE thread support.
-</dd>
-<dt><code>no</code></dt>
-<dd>This is an alias for ‘<samp>single</samp>’.
-</dd>
-<dt><code>posix</code></dt>
-<dd>Generic POSIX/Unix98 thread support.
-</dd>
-<dt><code>rtems</code></dt>
-<dd>RTEMS thread support.
-</dd>
-<dt><code>single</code></dt>
-<dd>Disable thread support, should work for all platforms.
-</dd>
-<dt><code>tpf</code></dt>
-<dd>TPF thread support.
-</dd>
-<dt><code>vxworks</code></dt>
-<dd>VxWorks thread support.
-</dd>
-<dt><code>win32</code></dt>
-<dd>Microsoft Win32 API thread support.
-</dd>
+
+ <dl>
+<dt><code>aix</code><dd>AIX thread support.
+ <dt><code>dce</code><dd>DCE thread support.
+ <dt><code>lynx</code><dd>LynxOS thread support.
+ <dt><code>mipssde</code><dd>MIPS SDE thread support.
+ <dt><code>no</code><dd>This is an alias for ‘<samp>single</samp>’.
+ <dt><code>posix</code><dd>Generic POSIX/Unix98 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>tpf</code><dd>TPF thread support.
+ <dt><code>vxworks</code><dd>VxWorks thread support.
+ <dt><code>win32</code><dd>Microsoft Win32 API thread support.
</dl>

-</dd>
-<dt><code>--enable-tls</code></dt>
-<dd>Specify that the target supports TLS (Thread Local Storage). Usually
+ <dt><code>--enable-tls</code><dd>Specify that the target supports TLS
(Thread Local Storage). Usually
configure can correctly determine if TLS is supported. In cases where
it guesses incorrectly, TLS can be explicitly enabled or disabled with
-<samp>--enable-tls</samp> or <samp>--disable-tls</samp>. This can happen if
+<samp>--enable-tls</samp> or <samp>--disable-tls</samp>. This can happen if
the assembler supports TLS but the C library does not, or if the
assumptions made by the configure test are incorrect.
-
-</dd>
-<dt><code>--disable-tls</code></dt>
-<dd>Specify that the target does not support TLS.
-This is an alias for <samp>--enable-tls=no</samp>.
-
-</dd>
-<dt><code>--with-cpu=<var>cpu</var></code></dt>
-<dt><code>--with-cpu-32=<var>cpu</var></code></dt>
-<dt><code>--with-cpu-64=<var>cpu</var></code></dt>
-<dd>Specify which cpu variant the compiler should generate code for by
default.
-<var>cpu</var> will be used as the default value of the <samp>-mcpu=</samp>
switch.
+
+ <dt><code>--disable-tls</code><dd>Specify that the target does not
support TLS.
+This is an alias for <samp>--enable-tls=no</samp>.
+
+
 <dt><code>--with-cpu=</code><var>cpu</var><dt><code>--with-cpu-32=</code><var>cpu</var><dt><code>--with-cpu-64=</code><var>cpu</var><dd>Specify
which cpu variant the compiler should generate code for by default.
+<var>cpu</var> will be used as the default value of the <samp>-mcpu=</samp> switch.
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
+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,
x86-64 and PowerPC.
-
-</dd>
-<dt><code>--with-schedule=<var>cpu</var></code></dt>
-<dt><code>--with-arch=<var>cpu</var></code></dt>
-<dt><code>--with-arch-32=<var>cpu</var></code></dt>
-<dt><code>--with-arch-64=<var>cpu</var></code></dt>
-<dt><code>--with-tune=<var>cpu</var></code></dt>
-<dt><code>--with-tune-32=<var>cpu</var></code></dt>
-<dt><code>--with-tune-64=<var>cpu</var></code></dt>
-<dt><code>--with-abi=<var>abi</var></code></dt>
-<dt><code>--with-fpu=<var>type</var></code></dt>
-<dt><code>--with-float=<var>type</var></code></dt>
-<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>
-options and for <samp>-mhard-float</samp> or <samp>-msoft-float</samp>. As
with
-<samp>--with-cpu</samp>, which switches will be accepted and acceptable values
+
+
 <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>
+options and for <samp>-mhard-float</samp> or
<samp>-msoft-float</samp>. As with
+<samp>--with-cpu</samp>, which switches will be
accepted and acceptable values
of the arguments depend on the target.
-
-</dd>
-<dt><code>--with-mode=<var>mode</var></code></dt>
-<dd>Specify if the compiler should default to <samp>-marm</samp> or
<samp>-mthumb</samp>.
+
+ <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.
-
-</dd>
-<dt><code>--with-stack-offset=<var>num</var></code></dt>
-<dd>This option sets the default for the -mstack-offset=<var>num</var>
option,
+
+ <dt><code>--with-stack-offset=</code><var>num</var><dd>This option
sets the default for the -mstack-offset=<var>num</var> option,
and will thus generally also control the setting of this option for
libraries. This option is only supported on Epiphany targets.
-
-</dd>
-<dt><code>--with-fpmath=<var>isa</var></code></dt>
-<dd>This options sets <samp>-mfpmath=sse</samp> by default and specifies
the default
-ISA for floating-point arithmetics. You can select either
‘<samp>sse</samp>’ which
-enables <samp>-msse2</samp> or ‘<samp>avx</samp>’ which enables
<samp>-mavx</samp> by default.
+
+ <dt><code>--with-fpmath=</code><var>isa</var><dd>This options sets
<samp>-mfpmath=sse</samp> by default and specifies
the default
+ISA for floating-point arithmetics. You can select either ‘<samp>sse</samp>’ which
+enables <samp>-msse2</samp> or ‘<samp>avx</samp>’ which enables <samp>-mavx</samp> by default.
This option is only supported on i386 and x86-64 targets.
-
-</dd>
-<dt><code>--with-divide=<var>type</var></code></dt>
-<dd>Specify how the compiler should generate code for checking for
-division by zero. This option is only supported on the MIPS target.
+
+ <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:
-<dl compact="compact">
-<dt><code>traps</code></dt>
-<dd>Division by zero checks use conditional traps (this is the default on
-systems that support conditional traps).
-</dd>
-<dt><code>breaks</code></dt>
-<dd>Division by zero checks use the break instruction.
-</dd>
+ <dl>
+<dt><code>traps</code><dd>Division by zero checks use conditional traps (this
is the default on
+systems that support conditional traps).
+ <dt><code>breaks</code><dd>Division by zero checks use the break
instruction.
</dl>

-
-</dd>
-<dt><code>--with-llsc</code></dt>
-<dd>On MIPS targets, make <samp>-mllsc</samp> the default when no
-<samp>-mno-llsc</samp> option is passed. This is the default for
+ 
+ 
+ <dt><code>--with-llsc</code><dd>On MIPS targets, make <samp>-mllsc</samp> the default when no
+<samp>-mno-llsc</samp> option is passed. This is
the default for
Linux-based targets, as the kernel will emulate them if the ISA does
not provide them.
-
-</dd>
-<dt><code>--without-llsc</code></dt>
-<dd>On MIPS targets, make <samp>-mno-llsc</samp> the default when no
-<samp>-mllsc</samp> option is passed.
-
-</dd>
-<dt><code>--with-synci</code></dt>
-<dd>On MIPS targets, make <samp>-msynci</samp> the default when no
-<samp>-mno-synci</samp> option is passed.
-
-</dd>
-<dt><code>--without-synci</code></dt>
-<dd>On MIPS targets, make <samp>-mno-synci</samp> the default when no
-<samp>-msynci</samp> option is passed. This is the default.
-
-</dd>
-<dt><code>--with-mips-plt</code></dt>
-<dd>On MIPS targets, make use of copy relocations and PLTs.
+
+ <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
and the runtime C library.
-
-</dd>
-<dt><code>--enable-__cxa_atexit</code></dt>
-<dd>Define if you want to use __cxa_atexit, rather than atexit, to
-register C++ destructors for local statics and global objects.
+
+ <dt><code>--enable-__cxa_atexit</code><dd>Define if you want to use
__cxa_atexit, rather than atexit, to
+register C++ destructors for local statics and global objects.
This is essential for fully standards-compliant handling of
destructors, but requires __cxa_atexit in libc. This option is currently
only available on systems with GNU libc. When enabled, this will cause
-<samp>-fuse-cxa-atexit</samp> to be passed by default.
-
-</dd>
-<dt><code>--enable-gnu-indirect-function</code></dt>
-<dd>Define if you want to enable the <code>ifunc</code> attribute. This
option is
+<samp>-fuse-cxa-atexit</samp> to be passed by
default.
+
+ <dt><code>--enable-gnu-indirect-function</code><dd>Define if you want
to enable the <code>ifunc</code> attribute. This option is
currently only available on systems with GNU libc on certain targets.
-
-</dd>
-<dt><code>--enable-target-optspace</code></dt>
-<dd>Specify that target
-libraries should be optimized for code space instead of code speed.
+
+ <dt><code>--enable-target-optspace</code><dd>Specify that target
+libraries should be optimized for code space instead of code speed.
This is the default for the m32r platform.
-
-</dd>
-<dt><code>--with-cpp-install-dir=<var>dirname</var></code></dt>
-<dd>Specify that the user visible <code>cpp</code> program should be
installed
-in <samp><var>prefix</var>/<var>dirname</var>/cpp</samp>, in addition to
<var>bindir</var>.
-
-</dd>
-<dt><code>--enable-comdat</code></dt>
-<dd>Enable COMDAT group support. This is primarily used to override the
+
+ <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.
-
-</dd>
-<dt><code>--enable-initfini-array</code></dt>
-<dd>Force the use of sections <code>.init_array</code> and
<code>.fini_array</code>
+
+ <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
+destructors. Option <samp>--disable-initfini-array</samp> has the
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.
-
-</dd>
-<dt><code>--enable-maintainer-mode</code></dt>
-<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
+
+ <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
+catalog, configuring with <samp>--enable-maintainer-mode</samp> will enable
this. Note that you need a recent version of the <code>gettext</code> tools
to do so.
-
-</dd>
-<dt><code>--disable-bootstrap</code></dt>
-<dd>For a native build, the default configuration is to perform
-a 3-stage bootstrap of the compiler when ‘<samp>make</samp>’ is
invoked,
+
+ <dt><code>--disable-bootstrap</code><dd>For a native build, the
default configuration is to perform
+a 3-stage bootstrap of the compiler when ‘<samp>make</samp>’ is invoked,
testing that GCC can compile itself correctly. If you want to disable
-this process, you can configure with <samp>--disable-bootstrap</samp>.
-
-</dd>
-<dt><code>--enable-bootstrap</code></dt>
-<dd>In special cases, you may want to perform a 3-stage build
-even if the target and host triplets are different.
+this process, you can configure with <samp>--disable-bootstrap</samp>.
+
+ <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 is possible when the host can run code compiled for
-the target (e.g. host is i686-linux, target is i486-linux).
+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>.
-
-</dd>
-<dt><code>--enable-generated-files-in-srcdir</code></dt>
-<dd>Neither the .c and .h files that are generated from Bison and flex nor
the
+with <samp>--enable-bootstrap</samp>.
+
+ <dt><code>--enable-generated-files-in-srcdir</code><dd>Neither the .c
and .h files that are generated from Bison and flex nor the
info manuals and man pages that are built from the .texi files are present
in the SVN development tree. When building GCC from that development tree,
or from one of our snapshots, those generated files are placed in your
build directory, which allows for the source to be in a readonly
directory.
-
-If you configure with <samp>--enable-generated-files-in-srcdir</samp> then
those
+
+ If you configure with <samp>--enable-generated-files-in-srcdir</samp> then those
generated files will go into the source directory. This is mainly intended
for generating release or prerelease tarballs of the GCC sources, since it
is not a requirement that the users of source releases to have flex, Bison,
or makeinfo.
-
-</dd>
-<dt><code>--enable-version-specific-runtime-libs</code></dt>
-<dd>Specify
+
+ <dt><code>--enable-version-specific-runtime-libs</code><dd>Specify
that runtime libraries should be installed in the compiler specific
-subdirectory (<samp><var>libdir</var>/gcc</samp>) rather than the usual
places. In
-addition, ‘<samp>libstdc++</samp>’’s include files will be
installed into
+subdirectory (<samp><var>libdir</var>/gcc</samp>)
rather than the usual places. In
+addition, ‘<samp>libstdc++</samp>’'s
include files will be installed into
<samp><var>libdir</var></samp> unless you overruled it by using
-<samp>--with-gxx-include-dir=<var>dirname</var></samp>. Using this option is
+<samp>--with-gxx-include-dir=<var>dirname</var></samp>. Using
this option is
particularly useful if you intend to use several versions of GCC in
-parallel. This is currently supported by
‘<samp>libgfortran</samp>’,
-‘<samp>libjava</samp>’, ‘<samp>libmudflap</samp>’,
‘<samp>libstdc++</samp>’, and ‘<samp>libobjc</samp>’.
-
-</dd>
-<dt><code>--enable-languages=<var>lang1</var>,<var>lang2</var>,…</code></dt>
-<dd>Specify that only a particular subset of compilers and
+parallel. This is currently supported by ‘<samp>libgfortran</samp>’,
+‘<samp>libjava</samp>’,
‘<samp>libmudflap</samp>’,
‘<samp>libstdc++</samp>’, and
‘<samp>libobjc</samp>’.
+
+
 <dt><code>--enable-languages=</code><var>lang1</var><code>,</code><var>lang2</var><code>,...</code><dd>Specify
that only a particular subset of compilers and
their runtime libraries should be built. For a list of valid values for
<var>langN</var> you can issue the following command in the
-<samp>gcc</samp> directory of your GCC source tree: 
-<div class="smallexample">
-<pre class="smallexample">grep language= */config-lang.in
-</pre></div>
-Currently, you can use any of the following:
+<samp>gcc</samp> directory of your GCC source
tree: 
+ <pre class="smallexample"> grep language= */config-lang.in
+</pre>
+ Currently, you can use any of the following:
<code>all</code>, <code>ada</code>, <code>c</code>, <code>c++</code>,
<code>fortran</code>,
-<code>go</code>, <code>java</code>, <code>objc</code>, <code>obj-c++</code>.
-Building the Ada compiler has special requirements, see below.
+<code>go</code>, <code>java</code>, <code>objc</code>, <code>obj-c++</code>.
+Building the Ada compiler has special requirements, see below.
If you do not pass this flag, or specify the option <code>all</code>, then all
-default languages available in the <samp>gcc</samp> sub-tree will be
configured.
+default languages available in the <samp>gcc</samp>
sub-tree will be configured.
Ada, Go and Objective-C++ are not default languages; the rest are.
-
-</dd>
-<dt><code>--enable-stage1-languages=<var>lang1</var>,<var>lang2</var>,…</code></dt>
-<dd>Specify that a particular subset of compilers and their runtime
+
+
 <dt><code>--enable-stage1-languages=</code><var>lang1</var><code>,</code><var>lang2</var><code>,...</code><dd>Specify
that a particular subset of compilers and their runtime
libraries should be built with the system C compiler during stage 1 of
the bootstrap process, rather than only in later stages with the
bootstrapped C compiler. The list of valid values is the same as for
-<samp>--enable-languages</samp>, and the option <code>all</code> will select
all
-of the languages enabled by <samp>--enable-languages</samp>. This option is
+<samp>--enable-languages</samp>, and the option
<code>all</code> will select all
+of the languages enabled by <samp>--enable-languages</samp>. This option is
primarily useful for GCC development; for instance, when a development
version of the compiler cannot bootstrap due to compiler bugs, or when
one is debugging front ends other than the C front end. When this
option is used, one can then build the target libraries for the
-specified languages with the stage-1 compiler by using <code>make
-stage1-bubble all-target</code>, or run the testsuite on the stage-1 compiler
-for the specified languages using <code>make stage1-start check-gcc</code>.
-
-</dd>
-<dt><code>--disable-libada</code></dt>
-<dd>Specify that the run-time libraries and tools used by GNAT should not
+specified languages with the stage-1 compiler by using <samp>make
+stage1-bubble all-target</samp>, or run the testsuite on the stage-1
compiler
+for the specified languages using <samp>make
stage1-start check-gcc</samp>.
+
+ <dt><code>--disable-libada</code><dd>Specify that the run-time
libraries and tools used by GNAT should not
be built. This can be useful for debugging, or for compatibility with
previous Ada build procedures, when it was required to explicitly
-do a ‘<samp>make -C gcc gnatlib_and_tools</samp>’.
-
-</dd>
-<dt><code>--disable-libssp</code></dt>
-<dd>Specify that the run-time libraries for stack smashing protection
+do a ‘<samp>make -C gcc
gnatlib_and_tools</samp>’.
+
+ <dt><code>--disable-libssp</code><dd>Specify that the run-time
libraries for stack smashing protection
should not be built.
-
-</dd>
-<dt><code>--disable-libquadmath</code></dt>
-<dd>Specify that the GCC quad-precision math library should not be built.
+
+ <dt><code>--disable-libquadmath</code><dd>Specify that the GCC
quad-precision math library should not be built.
On some systems, the library is required to be linkable when building
-the Fortran front end, unless <samp>--disable-libquadmath-support</samp>
+the Fortran front end, unless <samp>--disable-libquadmath-support</samp>
is used.
-
-</dd>
-<dt><code>--disable-libquadmath-support</code></dt>
-<dd>Specify that the Fortran front end and <code>libgfortran</code> do not
add
+
+ <dt><code>--disable-libquadmath-support</code><dd>Specify that the
Fortran front end and <code>libgfortran</code> do not add
support for <code>libquadmath</code> on systems supporting it.
-
-</dd>
-<dt><code>--disable-libgomp</code></dt>
-<dd>Specify that the run-time libraries used by GOMP should not be built.
-
-</dd>
-<dt><code>--with-dwarf2</code></dt>
-<dd>Specify that the compiler should
+
+ <dt><code>--disable-libgomp</code><dd>Specify that the run-time
libraries used by GOMP should not be built.
+
+ <dt><code>--with-dwarf2</code><dd>Specify that the compiler should
use DWARF 2 debugging information as the default.
-
-</dd>
-<dt><code>--enable-targets=all</code></dt>
-<dt><code>--enable-targets=<var>target_list</var></code></dt>
-<dd>Some GCC targets, e.g. powerpc64-linux, build bi-arch compilers.
+
+
 <dt><code>--enable-targets=all</code><dt><code>--enable-targets=</code><var>target_list</var><dd>Some
GCC targets, e.g. powerpc64-linux, build bi-arch compilers.
These are compilers that are able to generate either 64-bit or 32-bit
-code. Typically, the corresponding 32-bit target, e.g.
+code. Typically, the corresponding 32-bit target, e.g.
powerpc-linux for powerpc64-linux, only generates 32-bit code. This
option enables the 32-bit target to be a bi-arch compiler, which is
useful when you want a bi-arch compiler that defaults to 32-bit, and
-you are building a bi-arch or multi-arch binutils in a combined tree.
+you are building a bi-arch or multi-arch binutils in a combined tree.
On mips-linux, this will build a tri-arch compiler (ABI o32/n32/64),
-defaulted to o32.
+defaulted to o32.
Currently, this option only affects sparc-linux, powerpc-linux, x86-linux,
mips-linux and s390-linux.
-
-</dd>
-<dt><code>--enable-secureplt</code></dt>
-<dd>This option enables <samp>-msecure-plt</samp> by default for
powerpc-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
-
-</dd>
-<dt><code>--enable-cld</code></dt>
-<dd>This option enables <samp>-mcld</samp> by default for 32-bit x86
targets.
+
+ <dt><code>--enable-cld</code><dd>This option enables <samp>-mcld</samp> by default for 32-bit x86 targets.
See “i386 and x86-64 Options” in the main manual
-
-</dd>
-<dt><code>--enable-win32-registry</code></dt>
-<dt><code>--enable-win32-registry=<var>key</var></code></dt>
-<dt><code>--disable-win32-registry</code></dt>
-<dd>The <samp>--enable-win32-registry</samp> option enables Microsoft
Windows-hosted GCC
+
+
 <dt><code>--enable-win32-registry</code><dt><code>--enable-win32-registry=</code><var>key</var><dt><code>--disable-win32-registry</code><dd>The
<samp>--enable-win32-registry</samp> option
enables Microsoft Windows-hosted GCC
to look up installations paths in the registry using the following key:
-
-<div class="smallexample">
-<pre class="smallexample"><code>HKEY_LOCAL_MACHINE\SOFTWARE\Free Software
Foundation\<var>key</var></code>
-</pre></div>

-<var>key</var> defaults to GCC version number, and can be overridden by the
-<samp>--enable-win32-registry=<var>key</var></samp> option. Vendors and
distributors
+ <pre class="smallexample">
<code>HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\</code><var>key</var>
+</pre>
+ <var>key</var> defaults to GCC version number, and can be overridden
by the
+<samp>--enable-win32-registry=<var>key</var></samp> option.
Vendors and distributors
who use custom installers are encouraged to provide a different key,
perhaps one comprised of vendor name and GCC version number, to
avoid conflict with existing installations. This feature is enabled
-by default, and can be disabled by <samp>--disable-win32-registry</samp>
+by default, and can be disabled by <samp>--disable-win32-registry</samp>
option. This option has no effect on the other hosts.
-
-</dd>
-<dt><code>--nfp</code></dt>
-<dd>Specify that the machine does not have a floating point unit. This
-option only applies to ‘<samp>m68k-sun-sunos<var>n</var></samp>’.
On any other
-system, <samp>--nfp</samp> has no effect.
-
-</dd>
-<dt><code>--enable-werror</code></dt>
-<dt><code>--disable-werror</code></dt>
-<dt><code>--enable-werror=yes</code></dt>
-<dt><code>--enable-werror=no</code></dt>
-<dd>When you specify this option, it controls whether certain files in the
-compiler are built with <samp>-Werror</samp> in bootstrap stage2 and later.
-If you don’t specify it, <samp>-Werror</samp> is turned on for the main
+
+ <dt><code>--nfp</code><dd>Specify that the machine does not have a
floating point unit. This
+option only applies to ‘<samp>m68k-sun-sunos<var>n</var></samp>’. On any other
+system, <samp>--nfp</samp> has no effect.
+
+
 <dt><code>--enable-werror</code><dt><code>--disable-werror</code><dt><code>--enable-werror=yes</code><dt><code>--enable-werror=no</code><dd>When
you specify this option, it controls whether certain files in the
+compiler are built with <samp>-Werror</samp> in
bootstrap stage2 and later.
+If you don't specify it, <samp>-Werror</samp> is
turned on for the main
development trunk. However it defaults to off for release branches and
-final releases. The specific files which get <samp>-Werror</samp> are
+final releases. The specific files which get <samp>-Werror</samp> are
controlled by the Makefiles.
-
-</dd>
-<dt><code>--enable-checking</code></dt>
-<dt><code>--enable-checking=<var>list</var></code></dt>
-<dd>When you specify this option, the compiler is built to perform internal
+
+
 <dt><code>--enable-checking</code><dt><code>--enable-checking=</code><var>list</var><dd>When
you specify this option, the compiler is built to perform internal
consistency checks of the requested complexity. This does not change the
generated code, but adds error checking within the compiler. This will
slow down the compiler and may only work properly if you are building
-the compiler with GCC. This is ‘<samp>yes</samp>’ by default when
building
-from SVN or snapshots, but ‘<samp>release</samp>’ for releases.
The default
-for building the stage1 compiler is ‘<samp>yes</samp>’. More
control
+the compiler with GCC. This is ‘<samp>yes</samp>’ by default when building
+from SVN or snapshots, but ‘<samp>release</samp>’ for releases. The default
+for building the stage1 compiler is ‘<samp>yes</samp>’. More control
over the checks may be had by specifying <var>list</var>. The categories of
-checks available are ‘<samp>yes</samp>’ (most common checks
-‘<samp>assert,misc,tree,gc,rtlflag,runtime</samp>’),
‘<samp>no</samp>’ (no checks at
-all), ‘<samp>all</samp>’ (all but
‘<samp>valgrind</samp>’), ‘<samp>release</samp>’
(cheapest
-checks ‘<samp>assert,runtime</samp>’) or
‘<samp>none</samp>’ (same as ‘<samp>no</samp>’).
-Individual checks can be enabled with these flags
‘<samp>assert</samp>’,
-‘<samp>df</samp>’, ‘<samp>fold</samp>’,
‘<samp>gc</samp>’, ‘<samp>gcac</samp>’
‘<samp>misc</samp>’, ‘<samp>rtl</samp>’,
-‘<samp>rtlflag</samp>’, ‘<samp>runtime</samp>’,
‘<samp>tree</samp>’, and ‘<samp>valgrind</samp>’.

[ *** diff truncated: 199529 lines dropped *** ]

############################################################################

Revision: btrev43101
Commit: 3801b878c2c2bfea5a115bcbd75b56d3da05bc3d
URL: http://cgit.haiku-os.org/buildtools/commit/?id=3801b878c2c2
Author: Jérôme Duval <jerome.duval@xxxxxxxxx>
Date: Sat Jul 11 07:17:00 2015 UTC

Merge gcc 4.8.5

----------------------------------------------------------------------------

[haiku-commits] buildtools: btrev43101 - in gcc: gcc/doc gcc/fortran INSTALL gcc .

Other related posts: