[haiku-commits] buildtools: btrev43097 - in gcc: gcc/doc gcc/fortran . INSTALL gcc
- From: jerome.duval@xxxxxxxxx
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Sun, 21 Dec 2014 15:18:34 +0100 (CET)
btrev43097 adds 2 changesets to branch 'master'
old head: ff47abe8d7e552a3712bae0bc6bf17fd695e824f
new head: 1a00a76b58ae57d24bd4d774f6323c4ea62dd1e7
overview: http://cgit.haiku-os.org/buildtools/log/?qt=range&q=1a00a76+%5Eff47abe
----------------------------------------------------------------------------
514f593: import gcc 4.8.4
1a00a76: Merge gcc 4.8.4
[ Jérôme Duval <jerome.duval@xxxxxxxxx> ]
----------------------------------------------------------------------------
400 files changed, 66780 insertions(+), 58845 deletions(-)
gcc/ChangeLog | 20 +
gcc/INSTALL/binaries.html | 203 +-
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 | 1923 +-
gcc/INSTALL/test.html | 411 +-
gcc/LAST_UPDATED | 2 +-
gcc/MD5SUMS | 1424 +-
gcc/Makefile.def | 4 +
gcc/Makefile.in | 32 +
gcc/NEWS | 3925 +-
gcc/config/ChangeLog | 9 +
gcc/config/mh-alpha-linux | 3 +
gcc/configure | 52 +
gcc/configure.ac | 6 +
gcc/contrib/ChangeLog | 8 +
gcc/contrib/gennews | 2 +-
gcc/contrib/reghunt/ChangeLog | 4 +
gcc/contrib/regression/ChangeLog | 4 +
gcc/fixincludes/ChangeLog | 13 +
gcc/fixincludes/fixincl.x | 55 +-
gcc/fixincludes/inclhack.def | 13 +
gcc/fixincludes/tests/base/assert.h | 7 +
gcc/gcc/BASE-VER | 2 +-
gcc/gcc/ChangeLog | 1320 +
gcc/gcc/DATESTAMP | 2 +-
gcc/gcc/ada/ChangeLog | 30 +
gcc/gcc/ada/back_end.adb | 3 +-
gcc/gcc/ada/gsocket.h | 5 +
gcc/gcc/ada/s-osinte-rtems.adb | 2 +-
gcc/gcc/ada/socket.c | 2 +-
gcc/gcc/ada/uintp.adb | 16 -
gcc/gcc/ada/uintp.ads | 40 +-
gcc/gcc/c-family/ChangeLog | 4 +
gcc/gcc/c/ChangeLog | 4 +
gcc/gcc/cgraphunit.c | 2 +-
gcc/gcc/common.opt | 4 +
gcc/gcc/config.gcc | 7 +-
gcc/gcc/config.in | 6 +
gcc/gcc/config/aarch64/aarch64-elf-raw.h | 11 +-
gcc/gcc/config/aarch64/aarch64-linux.h | 13 +-
gcc/gcc/config/aarch64/aarch64-protos.h | 2 +
gcc/gcc/config/aarch64/aarch64.c | 155 +-
gcc/gcc/config/aarch64/aarch64.h | 12 +
gcc/gcc/config/aarch64/aarch64.md | 1 +
gcc/gcc/config/aarch64/aarch64.opt | 4 +
gcc/gcc/config/aarch64/arm_neon.h | 4 +-
gcc/gcc/config/alpha/alpha.c | 6 +
gcc/gcc/config/alpha/elf.h | 4 +
gcc/gcc/config/arm/arm-protos.h | 3 +
gcc/gcc/config/arm/arm.c | 18 +-
gcc/gcc/config/arm/arm.h | 7 +-
gcc/gcc/config/arm/arm.md | 62 +-
gcc/gcc/config/arm/constraints.md | 11 +-
gcc/gcc/config/arm/t-rtems-eabi | 124 +-
gcc/gcc/config/avr/avr-fixed.md | 4 +-
gcc/gcc/config/avr/avr.h | 14 +-
gcc/gcc/config/avr/avr.md | 9 +
gcc/gcc/config/darwin-c.c | 25 +-
gcc/gcc/config/darwin-driver.c | 35 +-
gcc/gcc/config/elfos.h | 2 +-
gcc/gcc/config/i386/driver-i386.c | 5 +
gcc/gcc/config/i386/i386.c | 24 +-
gcc/gcc/config/i386/i386.md | 79 +-
gcc/gcc/config/microblaze/microblaze.md | 12 -
gcc/gcc/config/microblaze/predicates.md | 4 -
gcc/gcc/config/pa/pa.c | 52 +-
gcc/gcc/config/pa/pa.md | 17 +-
gcc/gcc/config/rs6000/altivec.h | 6 +
gcc/gcc/config/rs6000/altivec.md | 56 +-
gcc/gcc/config/rs6000/constraints.md | 16 +-
gcc/gcc/config/rs6000/freebsd64.h | 2 +-
gcc/gcc/config/rs6000/htm.md | 2 +-
gcc/gcc/config/rs6000/linux64.h | 2 +-
gcc/gcc/config/rs6000/predicates.md | 75 +-
gcc/gcc/config/rs6000/rs6000-builtin.def | 31 +-
gcc/gcc/config/rs6000/rs6000-c.c | 147 +-
gcc/gcc/config/rs6000/rs6000-protos.h | 8 +-
gcc/gcc/config/rs6000/rs6000.c | 445 +-
gcc/gcc/config/rs6000/rs6000.h | 24 +-
gcc/gcc/config/rs6000/rs6000.md | 122 +-
gcc/gcc/config/rs6000/sysv4.h | 26 +-
gcc/gcc/config/rs6000/vsx.md | 565 +-
gcc/gcc/config/rs6000/xcoff.h | 9 +-
gcc/gcc/config/sh/sh.c | 8 +-
gcc/gcc/config/sh/sh.md | 7 +-
gcc/gcc/config/sh/sh.opt | 2 +-
gcc/gcc/config/sh/sync.md | 18 +-
gcc/gcc/config/sparc/leon.md | 14 +-
gcc/gcc/config/sparc/sparc-opts.h | 1 +
gcc/gcc/config/sparc/sparc.c | 3 +
gcc/gcc/config/sparc/sparc.h | 40 +-
gcc/gcc/config/sparc/sparc.md | 1 +
[ *** stats truncated: 301 lines dropped *** ]
############################################################################
Commit: 514f593381eb4eb904c81cedf836ca98a5222a55
URL: http://cgit.haiku-os.org/buildtools/commit/?id=514f593
Author: Jérôme Duval <jerome.duval@xxxxxxxxx>
Date: Sun Dec 21 11:07:28 2014 UTC
import gcc 4.8.4
----------------------------------------------------------------------------
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 0ed0083..21aed67 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,23 @@
+2014-12-19 Release Manager
+
+ * GCC 4.8.4 released.
+
+2014-12-08 Richard Biener <rguenther@xxxxxxx>
+
+ Backport from 4.9 branch
+ 2014-12-04 Tobias Burnus <burnus@xxxxxxxx>
+
+ * configure.ac: Permit also ISL 0.14 with CLooG.
+ * Makefile.def: Make more dependent on mpfr, mpc, isl, and cloog.
+ * Makefile.in: Regenerate.
+ * configure: Regenerate.
+
+2014-07-26 Uros Bizjak <ubizjak@xxxxxxxxx>
+
+ PR target/47230
+ * configure.ac (alpha*-*-linux*): Use mh-alpha-linux.
+ * configure: Regenerate.
+
2014-05-22 Release Manager
* GCC 4.8.3 released.
diff --git a/gcc/INSTALL/binaries.html b/gcc/INSTALL/binaries.html
index f89f17d..de321c3 100644
--- a/gcc/INSTALL/binaries.html
+++ b/gcc/INSTALL/binaries.html
@@ -1,115 +1,164 @@
-<html lang="en">
-<head>
-<title>Installing GCC: Binaries</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Installing GCC: Binaries">
-<meta name="generator" content="makeinfo 4.12">
-<link title="Top" rel="top" href="#Top">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
-<!--
-Copyright (C) 1988-2013 Free Software Foundation, Inc.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Copyright (C) 1988-2013 Free Software Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this document
+Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with no
Invariant Sections, the Front-Cover texts being (a) (see below), and
with the Back-Cover Texts being (b) (see below). A copy of the
-license is included in the section entitled "GNU Free Documentation License".
+license is included in the section entitled "GNU
+Free Documentation License".
(a) The FSF's Front-Cover Text is:
- A GNU Manual
+A GNU Manual
(b) The FSF's Back-Cover Text is:
- You have freedom to copy and modify this GNU Manual, like GNU
+You have freedom to copy and modify this GNU Manual, like GNU
software. Copies published by the Free Software Foundation raise
- funds for GNU development.-->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+ funds for GNU development. -->
+<!-- Created by GNU Texinfo 5.2, http://www.gnu.org/software/texinfo/ -->
+<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">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<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.
- <p>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.
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
+<h1 class="settitle" align="center">Installing GCC</h1>
+
+
+
+
+
+
+
+
+
+
- <ul>
-<li>AIX:
- <ul>
-<li><a href="http://www.bullfreeware.com";>Bull's Freeware and Shareware
Archive for AIX</a>;
- <li><a href="http://pware.hvcc.edu";>Hudson Valley Community College
Open Source Software for IBM System p</a>;
- <li><a href="http://www.perzl.org/aix/";>AIX 5L and 6 Open Source
Packages</a>.
-</ul>
- <li>DOS—<a href="http://www.delorie.com/djgpp/";>DJGPP</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>HP-UX:
- <ul>
-<li><a href="http://hpux.connect.org.uk/";>HP-UX Porting Center</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><a href="http://www.sco.com/skunkware/devtools/index.html#gcc";>SCO
OpenServer/Unixware</a>.
- <li>Solaris 2 (SPARC, Intel):
- <ul>
-<li><a href="http://www.sunfreeware.com/";>Sunfreeware</a>
- <li><a href="http://www.blastwave.org/";>Blastwave</a>
- <li><a href="http://www.opencsw.org/";>OpenCSW</a>
- <li><a href="http://jupiterrise.com/tgcware/";>TGCware</a>
-</ul>
- <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>
+<a name="index-Binaries"></a>
+<a name="index-Installing-GCC_003a-Binaries"></a>
- <li><a href="ftp://ftp.thewrittenword.com/packages/by-name/";>The Written
Word</a> offers binaries for
+<p>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.
+</p>
+<p>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.
+</p>
+<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>;
+
+</li><li> <a href="http://www.perzl.org/aix/";>AIX 5L and 6 Open Source
Packages</a>.
+</li></ul>
+
+</li><li> DOS—<a href="http://www.delorie.com/djgpp/";>DJGPP</a>.
+
+</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><li> HP-UX:
+<ul>
+<li> <a href="http://hpux.connect.org.uk/";>HP-UX Porting Center</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><li> <a href="http://www.sco.com/skunkware/devtools/index.html#gcc";>SCO
+OpenServer/Unixware</a>.
+
+</li><li> Solaris 2 (SPARC, Intel):
+<ul>
+<li> <a href="http://www.opencsw.org/";>OpenCSW</a>
+
+</li><li> <a href="http://jupiterrise.com/tgcware/";>TGCware</a>
+</li></ul>
+
+</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><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><a href="http://www.openpkg.org/";>OpenPKG</a> offers binaries for
quite a
+</li><li> <a href="http://www.openpkg.org/";>OpenPKG</a> offers binaries for
quite a
number of platforms.
- <li>The <a href="http://gcc.gnu.org/wiki/GFortranBinaries";>GFortran
Wiki</a> has
-links to GNU Fortran binaries for several platforms.
-</ul>
+</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 />
+<p><p><a href="./index.html">Return to the GCC Installation page</a>
+</p>
+
+
+
+
- <p><hr />
-<p><a href="./index.html">Return to the GCC Installation page</a>
-<!--
***Specific**************************************************************** -->
-<!-- ***Old
documentation****************************************************** -->
-<!--
***GFDL******************************************************************** -->
-<!--
*************************************************************************** -->
-<!-- Part 6 The End of the Document -->
-</body></html>
+</body>
+</html>
diff --git a/gcc/INSTALL/build.html b/gcc/INSTALL/build.html
index 4e47502..a44612a 100644
--- a/gcc/INSTALL/build.html
+++ b/gcc/INSTALL/build.html
@@ -1,378 +1,458 @@
-<html lang="en">
-<head>
-<title>Installing GCC: Building</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Installing GCC: Building">
-<meta name="generator" content="makeinfo 4.12">
-<link title="Top" rel="top" href="#Top">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
-<!--
-Copyright (C) 1988-2013 Free Software Foundation, Inc.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Copyright (C) 1988-2013 Free Software Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this document
+Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with no
Invariant Sections, the Front-Cover texts being (a) (see below), and
with the Back-Cover Texts being (b) (see below). A copy of the
-license is included in the section entitled "GNU Free Documentation License".
+license is included in the section entitled "GNU
+Free Documentation License".
(a) The FSF's Front-Cover Text is:
- A GNU Manual
+A GNU Manual
(b) The FSF's Back-Cover Text is:
- You have freedom to copy and modify this GNU Manual, like GNU
+You have freedom to copy and modify this GNU Manual, like GNU
software. Copies published by the Free Software Foundation raise
- funds for GNU development.-->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+ funds for GNU development. -->
+<!-- Created by GNU Texinfo 5.2, http://www.gnu.org/software/texinfo/ -->
+<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">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<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.
- <p>Some commands executed when making the compiler may fail (return a
-nonzero status) and be ignored by <samp><span
class="command">make</span></samp>. These failures, which
+<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>
+
+<p>Now that GCC is configured, you are ready to build the compiler and
+runtime libraries.
+</p>
+<p>Some commands executed when making the compiler may fail (return a
+nonzero status) and be ignored by <code>make</code>. These failures, which
are often due to files that were not found, are expected, and can safely
be ignored.
-
- <p>It is normal to have compiler warnings when compiling certain files.
+</p>
+<p>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><span class="option">--disable-werror</span></samp>.
-
- <p>On certain old systems, defining certain environment variables such as
-<samp><span class="env">CC</span></samp> can interfere with the functioning of
<samp><span class="command">make</span></samp>.
-
- <p>If you encounter seemingly strange errors when trying to build the
+<samp>--disable-werror</samp>.
+</p>
+<p>On certain old systems, defining certain environment variables such as
+<code>CC</code> can interfere with the functioning of <code>make</code>.
+</p>
+<p>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.
-
- <p>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><span
class="command">fixincludes</span></samp> if the
-System V file system doesn't support symbolic links. These problems
+</p>
+<p>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
result in a failure to fix the declaration of <code>size_t</code> in
-<samp><span class="file">sys/types.h</span></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.
-
- <p>The solution is not to use such a directory for building GCC.
-
- <p>Similarly, when building from SVN or snapshots, or if you modify
-<samp><span class="file">*.l</span></samp> files, you need the Flex lexical
analyzer generator
-installed. If you do not modify <samp><span class="file">*.l</span></samp>
files, releases contain
+</p>
+<p>The solution is not to use such a directory for building GCC.
+</p>
+<p>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.
-
- <p>When building from SVN or snapshots, or if you modify Texinfo
+</p>
+<p>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.
-
-<h3 class="section"><a name="TOC0"></a>Building a native compiler</h3>
+</p>
+<a name="Building-a-native-compiler"></a>
+<h3 class="section">Building a native compiler</h3>
<p>For a native build, the default configuration is to perform
-a 3-stage bootstrap of the compiler when ‘<samp><span
class="samp">make</span></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><span
class="option">--disable-bootstrap</span></samp>
-parameter to ‘<samp><span class="samp">configure</span></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.
+</p>
+<p>The bootstrapping process will complete the following steps:
+</p>
+<ul>
+<li> Build tools necessary to build the compiler.
- <p>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
+</li><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>Perform a comparison test of the stage2 and stage3 compilers.
+</li><li> Perform a comparison test of the stage2 and stage3 compilers.
- <li>Build runtime libraries using the stage3 compiler from the previous
step.
+</li><li> Build runtime libraries using the stage3 compiler from the previous
step.
- </ul>
+</li></ul>
- <p>If you are short on disk space you might consider ‘<samp><span
class="samp">make
-bootstrap-lean</span></samp>’ instead. The sequence of compilation is
the
+<p>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.
-
- <p>If you wish to use non-default GCC flags when compiling the stage2
+</p>
+<p>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><span class="samp">make</span></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.)
+</p>
+<div class="smallexample">
+<pre class="smallexample">make BOOT_CFLAGS='-O' bootstrap
+</pre></div>
-<pre class="smallexample"> make BOOT_CFLAGS='-O' bootstrap
-</pre>
- <p>You can place non-default optimization flags into
<code>BOOT_CFLAGS</code>; they
-are less well tested here than the default of ‘<samp><span
class="samp">-g -O2</span></samp>’, but should
+<p>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><span class="option">-msoft-float</span></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><span
class="samp">make
-bootstrap4</span></samp>’ to increase the number of stages of bootstrap.
-
- <p><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.
+</p>
+<p><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.
-
- <p>If you used the flag <samp><span
class="option">--enable-languages=...</span></samp> to restrict
-the compilers to be built, only those you've actually enabled will be
+</p>
+<p>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 <samp><span class="env">LANGUAGES</span></samp> when calling
‘<samp><span class="samp">make</span></samp>’
+that re-defining <code>LANGUAGES</code> when calling
‘<samp>make</samp>’
<strong>does not</strong> work anymore!
-
- <p>If the comparison of stage2 and stage3 fails, this normally indicates
+</p>
+<p>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><span
class="file">Makefile</span></samp>.)
-
- <p>If you do not want to bootstrap your compiler, you can configure with
-<samp><span class="option">--disable-bootstrap</span></samp>. In particular
cases, you may want to
+need to disable comparison in the <samp>Makefile</samp>.)
+</p>
+<p>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><span class="option">--enable-bootstrap</span></samp> to the configure
script.
-
- <p><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><span
class="file">config/</span><code>NAME</code><span
class="file">.mk</span></samp> will
-be included by the top-level <samp><span class="file">Makefile</span></samp>,
bringing in any settings
+<samp>--enable-bootstrap</samp> to the configure script.
+</p>
+<p><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><span
class="option">--with-build-config=</span><code>NAME</code><span
class="option">...</span></samp>. Some
+configure option <samp>--with-build-config=<code>NAME</code>...</samp>. Some
examples of supported build configurations are:
-
- <dl>
-<dt>‘<samp><span
class="samp">bootstrap-O1</span></samp>’<dd>Removes any <samp><span
class="option">-O</span></samp>-started option from <code>BOOT_CFLAGS</code>,
and adds
-<samp><span class="option">-O1</span></samp> to it. ‘<samp><span
class="samp">BUILD_CONFIG=bootstrap-O1</span></samp>’ is equivalent to
-‘<samp><span class="samp">BOOT_CFLAGS='-g -O1'</span></samp>’.
-
- <br><dt>‘<samp><span
class="samp">bootstrap-O3</span></samp>’<dd>Analogous to
<code>bootstrap-O1</code>.
-
- <br><dt>‘<samp><span
class="samp">bootstrap-lto</span></samp>’<dd>Enables Link-Time
Optimization for host tools during bootstrapping.
-‘<samp><span
class="samp">BUILD_CONFIG=bootstrap-lto</span></samp>’ is equivalent to
adding
-<samp><span class="option">-flto</span></samp> to ‘<samp><span
class="samp">BOOT_CFLAGS</span></samp>’.
-
- <br><dt>‘<samp><span
class="samp">bootstrap-debug</span></samp>’<dd>Verifies that the compiler
generates the same executable code, whether
+</p>
+<dl compact="compact">
+<dt>‘<samp>bootstrap-O1</samp>’</dt>
+<dd><p>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>’.
+</p>
+</dd>
+<dt>‘<samp>bootstrap-O3</samp>’</dt>
+<dd><p>Analogous to <code>bootstrap-O1</code>.
+</p>
+</dd>
+<dt>‘<samp>bootstrap-lto</samp>’</dt>
+<dd><p>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>’.
+</p>
+</dd>
+<dt>‘<samp>bootstrap-debug</samp>’</dt>
+<dd><p>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><span class="file">contrib/compare-debug</span></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.
-
- <br><dt>‘<samp><span
class="samp">bootstrap-debug-big</span></samp>’<dd>Rather than comparing
stripped object files, as in
+</p>
+</dd>
+<dt>‘<samp>bootstrap-debug-big</samp>’</dt>
+<dd><p>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><span
class="samp">bootstrap-debug</span></samp>’.
-
- <br><dt>‘<samp><span
class="samp">bootstrap-debug-lean</span></samp>’<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>’.
+</p>
+</dd>
+<dt>‘<samp>bootstrap-debug-lean</samp>’</dt>
+<dd><p>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><span class="option">-fcompare-debug</span></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.
-
- <br><dt>‘<samp><span
class="samp">bootstrap-debug-lib</span></samp>’<dd>This option tests
executable code invariance over debug information
+</p>
+</dd>
+<dt>‘<samp>bootstrap-debug-lib</samp>’</dt>
+<dd><p>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><span class="option">-fcompare-debug</span></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.
-
- <p>There aren't <code>-lean</code> or <code>-big</code> counterparts to
this option
+</p>
+<p>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.
-
- <br><dt>‘<samp><span
class="samp">bootstrap-debug-ckovw</span></samp>’<dd>Arranges for error
messages to be issued if the compiler built on any
-stage is run without the option <samp><span
class="option">-fcompare-debug</span></samp>. This is
-useful to verify the full <samp><span
class="option">-fcompare-debug</span></samp> testing coverage. It
+</p>
+</dd>
+<dt>‘<samp>bootstrap-debug-ckovw</samp>’</dt>
+<dd><p>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>.
-
- <br><dt>‘<samp><span
class="samp">bootstrap-time</span></samp>’<dd>Arranges for the run time
of each program started by the GCC driver,
-built in any stage, to be logged to <samp><span
class="file">time.log</span></samp>, in the top level of
+</p>
+</dd>
+<dt>‘<samp>bootstrap-time</samp>’</dt>
+<dd><p>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.
+</p>
+</dd>
+</dl>
- </dl>
-
-<h3 class="section"><a name="TOC1"></a>Building a cross compiler</h3>
+<a name="Building-a-cross-compiler"></a>
+<h3 class="section">Building a cross compiler</h3>
<p>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.
-
- <p>To build a cross compiler, we recommend first building and installing a
+</p>
+<p>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.
-
- <p>If the cross compiler is to be built with support for the Java
+</p>
+<p>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><span class="option">--with-ecj-jar=...</span></samp>.
-
- <p>Assuming you have already installed a native copy of GCC and configured
-your cross compiler, issue the command <samp><span
class="command">make</span></samp>, which performs the
+<samp>--with-ecj-jar=…</samp>.
+</p>
+<p>Assuming you have already installed a native copy of GCC and configured
+your cross compiler, issue the command <code>make</code>, which performs the
following steps:
+</p>
+<ul>
+<li> Build host tools necessary to build the compiler.
- <ul>
-<li>Build host tools necessary to build the compiler.
-
- <li>Build target tools for use by the compiler such as binutils (bfd,
+</li><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>Build the compiler (single stage only).
+</li><li> Build the compiler (single stage only).
- <li>Build runtime libraries using the compiler from the previous step.
-</ul>
+</li><li> Build runtime libraries using the compiler from the previous step.
+</li></ul>
- <p>Note that if an error occurs in any step the make process will exit.
-
- <p>If you are not building GNU binutils in the same source tree as GCC,
+<p>Note that if an error occurs in any step the make process will exit.
+</p>
+<p>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><span class="file">/</span><var>target</var><span
class="file">/bin</span></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>
-<dt><samp><span class="file">as</span></samp><dd>This should be the
cross-assembler.
-
- <br><dt><samp><span class="file">ld</span></samp><dd>This should be the
cross-linker.
-
- <br><dt><samp><span class="file">ar</span></samp><dd>This should be the
cross-archiver: a program which can manipulate
-archive files (linker libraries) in the target machine's format.
-
- <br><dt><samp><span class="file">ranlib</span></samp><dd>This should be a
program to construct a symbol table in an archive file.
+</p>
+<dl compact="compact">
+<dt><samp>as</samp></dt>
+<dd><p>This should be the cross-assembler.
+</p>
+</dd>
+<dt><samp>ld</samp></dt>
+<dd><p>This should be the cross-linker.
+</p>
+</dd>
+<dt><samp>ar</samp></dt>
+<dd><p>This should be the cross-archiver: a program which can manipulate
+archive files (linker libraries) in the target machine’s format.
+</p>
+</dd>
+<dt><samp>ranlib</samp></dt>
+<dd><p>This should be a program to construct a symbol table in an archive file.
+</p></dd>
</dl>
- <p>The installation of GCC will find these programs in that directory,
+<p>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.
-
- <p>The easiest way to provide these files is to build the Binutils package.
-Configure it with the same <samp><span class="option">--host</span></samp> and
<samp><span class="option">--target</span></samp>
+</p>
+<p>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.
-
- <p>If you are not building a C library in the same source tree as GCC,
+</p>
+<p>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><span class="option">--with-sysroot</span></samp> or <samp><span
class="option">--with-headers</span></samp> and
-<samp><span class="option">--with-libs</span></samp>. Many targets also
require “start files” such
-as <samp><span class="file">crt0.o</span></samp> and
-<samp><span class="file">crtn.o</span></samp> which are linked into each
executable. There may be several
-alternatives for <samp><span class="file">crt0.o</span></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.
-
-<h3 class="section"><a name="TOC2"></a>Building in parallel</h3>
+</p>
+<a name="Building-in-parallel"></a>
+<h3 class="section">Building in parallel</h3>
<p>GNU Make 3.80 and above, which is necessary to build GCC, support
-building in parallel. To activate this, you can use ‘<samp><span
class="samp">make -j 2</span></samp>’
-instead of ‘<samp><span class="samp">make</span></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.
-
-<h3 class="section"><a name="TOC3"></a>Building the Ada compiler</h3>
+</p>
+<a name="Building-the-Ada-compiler"></a>
+<h3 class="section">Building the Ada compiler</h3>
<p>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 <samp><span
class="command">gnatmake</span></samp> and
-<samp><span class="command">gnatlink</span></samp>, since the Ada front end is
written in Ada and
+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
uses some GNAT-specific extensions.
-
- <p>In order to build a cross compiler, it is suggested to install
+</p>
+<p>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.
-
- <p><samp><span class="command">configure</span></samp> does not test
whether the GNAT installation works
+</p>
+<p><code>configure</code> 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><span
class="option">--enable-languages</span></samp> is
+installed, the build will fail unless <samp>--enable-languages</samp> is
used to disable building the Ada front end.
-
- <p><samp><span class="env">ADA_INCLUDE_PATH</span></samp> and <samp><span
class="env">ADA_OBJECT_PATH</span></samp> environment variables
+</p>
+<p><code>ADA_INCLUDE_PATH</code> and <code>ADA_OBJECT_PATH</code> 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><span class="samp">gnatls
-v</span></samp>’ lists only one explicit path in each
+by verifying that ‘<samp>gnatls -v</samp>’ lists only one explicit
path in each
section.
-
-<h3 class="section"><a name="TOC4"></a>Building with profile feedback</h3>
+</p>
+<a name="Building-with-profile-feedback"></a>
+<h3 class="section">Building with profile feedback</h3>
<p>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>.
-
- <p>When ‘<samp><span class="samp">make
profiledbootstrap</span></samp>’ is run, it will first build a
<code>stage1</code>
+</p>
+<p>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.
-
- <p>Unlike standard bootstrap, several additional restrictions apply. The
-compiler used to build <code>stage1</code> needs to support a 64-bit integral
type.
+</p>
+<p>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.
+</p>
+<hr />
+<p><p><a href="./index.html">Return to the GCC Installation page</a>
+</p>
+
+
+
+
+
+
+
+<hr>
- <p><hr />
-<p><a href="./index.html">Return to the GCC Installation page</a>
-<!--
***Testing***************************************************************** -->
-<!-- ***Final
install*********************************************************** -->
-<!--
***Binaries**************************************************************** -->
-<!--
***Specific**************************************************************** -->
-<!-- ***Old
documentation****************************************************** -->
-<!--
***GFDL******************************************************************** -->
-<!--
*************************************************************************** -->
-<!-- Part 6 The End of the Document -->
-</body></html>
+</body>
+</html>
diff --git a/gcc/INSTALL/configure.html b/gcc/INSTALL/configure.html
index 722d95f..1abc3b9 100644
--- a/gcc/INSTALL/configure.html
+++ b/gcc/INSTALL/configure.html
@@ -1,1293 +1,1759 @@
-<html lang="en">
-<head>
-<title>Installing GCC: Configuration</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Installing GCC: Configuration">
-<meta name="generator" content="makeinfo 4.12">
-<link title="Top" rel="top" href="#Top">
-<link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
title="Texinfo Homepage">
-<!--
-Copyright (C) 1988-2013 Free Software Foundation, Inc.
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Copyright (C) 1988-2013 Free Software Foundation, Inc.
- Permission is granted to copy, distribute and/or modify this document
+Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with no
Invariant Sections, the Front-Cover texts being (a) (see below), and
with the Back-Cover Texts being (b) (see below). A copy of the
-license is included in the section entitled "GNU Free Documentation License".
+license is included in the section entitled "GNU
+Free Documentation License".
(a) The FSF's Front-Cover Text is:
- A GNU Manual
+A GNU Manual
(b) The FSF's Back-Cover Text is:
- You have freedom to copy and modify this GNU Manual, like GNU
+You have freedom to copy and modify this GNU Manual, like GNU
software. Copies published by the Free Software Foundation raise
- funds for GNU development.-->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
- pre.display { font-family:inherit }
- pre.format { font-family:inherit }
- pre.smalldisplay { font-family:inherit; font-size:smaller }
- pre.smallformat { font-family:inherit; font-size:smaller }
- pre.smallexample { font-size:smaller }
- pre.smalllisp { font-size:smaller }
- span.sc { font-variant:small-caps }
- span.roman { font-family:serif; font-weight:normal; }
- span.sansserif { font-family:sans-serif; font-weight:normal; }
---></style>
+ funds for GNU development. -->
+<!-- Created by GNU Texinfo 5.2, http://www.gnu.org/software/texinfo/ -->
+<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">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
</head>
-<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.
- <p>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.
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
+<h1 class="settitle" align="center">Installing GCC</h1>
+
+
+
+
+
+
+
- <p>If you obtained the sources via SVN, <var>srcdir</var> must refer to the
top
-<samp><span class="file">gcc</span></samp> directory, the one where the
<samp><span class="file">MAINTAINERS</span></samp> file can be
-found, and not its <samp><span class="file">gcc</span></samp> subdirectory,
otherwise the build will fail.
- <p>If either <var>srcdir</var> or <var>objdir</var> is located on an
automounted NFS
-file system, the shell's built-in <samp><span
class="command">pwd</span></samp> command will return
+
+
+
+
+
+
+
+
+
+
+<a name="index-Configuration"></a>
+<a name="index-Installing-GCC_003a-Configuration"></a>
+
+<p>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.
+</p>
+<p>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.
+</p>
+<p>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.
+</p>
+<p>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
temporary pathnames. Using these can lead to various sorts of build
-problems. To avoid this issue, set the <samp><span
class="env">PWDCMD</span></samp> environment
-variable to an automounter-aware <samp><span class="command">pwd</span></samp>
command, e.g.,
-<samp><span class="command">pawd</span></samp> or ‘<samp><span
class="samp">amq -w</span></samp>’, during the configuration and 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
phases.
-
- <p>First, we <strong>highly</strong> recommend that GCC be built into a
+</p>
+<p>First, we <strong>highly</strong> recommend that GCC be built into a
separate directory from the sources which does <strong>not</strong> 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.
-
- <p>If you have previously built GCC in the same directory for a
-different target machine, do ‘<samp><span class="samp">make
distclean</span></samp>’ to delete all files
-that might be invalid. One of the files this deletes is <samp><span
class="file">Makefile</span></samp>;
-if ‘<samp><span class="samp">make distclean</span></samp>’
complains that <samp><span class="file">Makefile</span></samp> does not exist
-or issues a message like “don't know how to make distclean” it
probably
+</p>
+<p>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.
-
- <p>Second, when configuring a native system, either <samp><span
class="command">cc</span></samp> or
-<samp><span class="command">gcc</span></samp> must be in your path or you must
set <samp><span class="env">CC</span></samp> in
+</p>
+<p>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
your environment before running configure. Otherwise the configuration
scripts may fail.
+</p>
- <p>To configure GCC:
+<p>To configure GCC:
+</p>
+<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>
-<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>
+<a name="Distributor-options"></a>
+<h3 class="heading">Distributor options</h3>
<p>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>
-<dt><code>--with-pkgversion=</code><var>version</var><dd>Specify a string that
identifies your package. You may wish
+</p>
+<dl compact="compact">
+<dt><code>--with-pkgversion=<var>version</var></code></dt>
+<dd><p>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 <samp><span class="command">gcc
--version</span></samp>. This suffix does
-not replace the default version string, only the ‘<samp><span
class="samp">GCC</span></samp>’ part.
-
- <p>The default value is ‘<samp><span
class="samp">GCC</span></samp>’.
-
- <br><dt><code>--with-bugurl=</code><var>url</var><dd>Specify the URL that
users should visit if they wish to report a bug.
+included in the output of <code>gcc --version</code>. This suffix does
+not replace the default version string, only the
‘<samp>GCC</samp>’ part.
+</p>
+<p>The default value is ‘<samp>GCC</samp>’.
+</p>
+</dd>
+<dt><code>--with-bugurl=<var>url</var></code></dt>
+<dd><p>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.
+</p>
+<p>The default value refers to the FSF’s GCC bug tracker.
+</p>
+</dd>
+</dl>
- <p>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>
+<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>
for nearly all native systems. Therefore, we highly recommend you do
not provide a configure target when configuring a native compiler.
- <li><var>target</var> must be specified as <samp><span
class="option">--target=</span><var>target</var></samp>
+</li><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>Specifying just <var>target</var> instead of <samp><span
class="option">--target=</span><var>target</var></samp>
-implies that the host defaults to <var>target</var>.
-</ul>
+</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>
-<h3 class="heading"><a name="TOC2"></a>Options specification</h3>
+
+<a name="Options-specification"></a>
+<h3 class="heading">Options specification</h3>
<p>Use <var>options</var> to override several configure time options for
-GCC. A list of supported <var>options</var> follows; ‘<samp><span
class="samp">configure
---help</span></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.
-
- <p>Note that each <samp><span class="option">--enable</span></samp> option
has a corresponding
-<samp><span class="option">--disable</span></samp> option and that each
<samp><span class="option">--with</span></samp> option has a
-corresponding <samp><span class="option">--without</span></samp> option.
-
- <dl>
-<dt><code>--prefix=</code><var>dirname</var><dd>Specify the toplevel
installation
+</p>
+<p>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.
+</p>
+<dl compact="compact">
+<dt><code>--prefix=<var>dirname</var></code></dt>
+<dd><p>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><span class="file">/usr/local</span></samp>.
-
- <p>We <strong>highly</strong> recommend against <var>dirname</var> being
the same or a
+<samp>/usr/local</samp>.
+</p>
+<p>We <strong>highly</strong> 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><span
class="samp">~</span></samp>’ metacharacter; use
-<samp><span class="env">$HOME</span></samp> instead.
-
- <p>The following standard <samp><span
class="command">autoconf</span></samp> 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
+<code>$HOME</code> instead.
+</p>
+<p>The following standard <code>autoconf</code> options are supported.
Normally you
should not need to use these options.
- <dl>
-<dt><code>--exec-prefix=</code><var>dirname</var><dd>Specify the toplevel
installation directory for architecture-dependent
+</p><dl compact="compact">
+<dt><code>--exec-prefix=<var>dirname</var></code></dt>
+<dd><p>Specify the toplevel installation directory for architecture-dependent
files. The default is <samp><var>prefix</var></samp>.
-
- <br><dt><code>--bindir=</code><var>dirname</var><dd>Specify the
installation directory for the executables called by users
-(such as <samp><span class="command">gcc</span></samp> and <samp><span
class="command">g++</span></samp>). The default is
-<samp><var>exec-prefix</var><span class="file">/bin</span></samp>.
-
- <br><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><span
class="file">/lib</span></samp>.
-
- <br><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><span
class="file">/libexec</span></samp>.
-
- <br><dt><code>--with-slibdir=</code><var>dirname</var><dd>Specify
the installation directory for the shared libgcc library. The
+</p>
+</dd>
+<dt><code>--bindir=<var>dirname</var></code></dt>
+<dd><p>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>.
+</p>
+</dd>
+<dt><code>--libdir=<var>dirname</var></code></dt>
+<dd><p>Specify the installation directory for object code libraries and
+internal data files of GCC. The default is
<samp><var>exec-prefix</var>/lib</samp>.
+</p>
+</dd>
+<dt><code>--libexecdir=<var>dirname</var></code></dt>
+<dd><p>Specify the installation directory for internal executables of GCC.
+The default is <samp><var>exec-prefix</var>/libexec</samp>.
+</p>
+</dd>
+<dt><code>--with-slibdir=<var>dirname</var></code></dt>
+<dd><p>Specify the installation directory for the shared libgcc library. The
default is <samp><var>libdir</var></samp>.
-
- <br><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><span
class="file">/share</span></samp>.
-
- <br><dt><code>--infodir=</code><var>dirname</var><dd>Specify the
installation directory for documentation in info format.
-The default is <samp><var>datarootdir</var><span
class="file">/info</span></samp>.
-
- <br><dt><code>--datadir=</code><var>dirname</var><dd>Specify the
installation directory for some architecture-independent
+</p>
+</dd>
+<dt><code>--datarootdir=<var>dirname</var></code></dt>
+<dd><p>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>.
+</p>
+</dd>
+<dt><code>--infodir=<var>dirname</var></code></dt>
+<dd><p>Specify the installation directory for documentation in info format.
+The default is <samp><var>datarootdir</var>/info</samp>.
+</p>
+</dd>
+<dt><code>--datadir=<var>dirname</var></code></dt>
+<dd><p>Specify the installation directory for some architecture-independent
data files referenced by GCC. The default is
<samp><var>datarootdir</var></samp>.
-
- <br><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><span
class="file">/doc</span></samp>.
-
- <br><dt><code>--htmldir=</code><var>dirname</var><dd>Specify the
installation directory for HTML documentation files.
+</p>
+</dd>
+<dt><code>--docdir=<var>dirname</var></code></dt>
+<dd><p>Specify the installation directory for documentation files (other
+than Info) for GCC. The default is <samp><var>datarootdir</var>/doc</samp>.
+</p>
+</dd>
+<dt><code>--htmldir=<var>dirname</var></code></dt>
+<dd><p>Specify the installation directory for HTML documentation files.
The default is <samp><var>docdir</var></samp>.
-
- <br><dt><code>--pdfdir=</code><var>dirname</var><dd>Specify the
installation directory for PDF documentation files.
+</p>
+</dd>
+<dt><code>--pdfdir=<var>dirname</var></code></dt>
+<dd><p>Specify the installation directory for PDF documentation files.
The default is <samp><var>docdir</var></samp>.
-
- <br><dt><code>--mandir=</code><var>dirname</var><dd>Specify the
installation directory for manual pages. The default is
-<samp><var>datarootdir</var><span class="file">/man</span></samp>. (Note that
the manual pages are only extracts
+</p>
+</dd>
+<dt><code>--mandir=<var>dirname</var></code></dt>
+<dd><p>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.)
-
-
<br><dt><code>--with-gxx-include-dir=</code><var>dirname</var><dd>Specify
+</p>
+</dd>
+<dt><code>--with-gxx-include-dir=<var>dirname</var></code></dt>
+<dd><p>Specify
the installation directory for G++ header files. The default depends
on other configuration options, and differs between cross and native
configurations.
-
- <br><dt><code>--with-specs=</code><var>specs</var><dd>Specify
additional command line driver SPECS.
+</p>
+</dd>
+<dt><code>--with-specs=<var>specs</var></code></dt>
+<dd><p>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><span
class="option">--with-specs=%{!fcommon:%{!fno-common:-fno-common}}</span></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
+</p>
+</dd>
+</dl>
- </dl>
-
- <br><dt><code>--program-prefix=</code><var>prefix</var><dd>GCC supports
some transformations of the names of its programs when
+</dd>
+<dt><code>--program-prefix=<var>prefix</var></code></dt>
+<dd><p>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><span class="option">--program-prefix=foo-</span></samp> would result in
‘<samp><span class="samp">gcc</span></samp>’
-being installed as <samp><span
class="file">/usr/local/bin/foo-gcc</span></samp>.
-
- <br><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><span
class="option">--program-suffix=-3.1</span></samp>
-would result in ‘<samp><span class="samp">gcc</span></samp>’ being
installed as
-<samp><span class="file">/usr/local/bin/gcc-3.1</span></samp>.
-
-
<br><dt><code>--program-transform-name=</code><var>pattern</var><dd>Applies the
‘<samp><span class="samp">sed</span></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>.
+</p>
+</dd>
+<dt><code>--program-suffix=<var>suffix</var></code></dt>
+<dd><p>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>.
+</p>
+</dd>
+<dt><code>--program-transform-name=<var>pattern</var></code></dt>
+<dd><p>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><span
class="samp">sed</span></samp>’ editing commands, separated by
-semicolons. For example, if you want the ‘<samp><span
class="samp">gcc</span></samp>’ program name to be
-transformed to the installed program <samp><span
class="file">/usr/local/bin/myowngcc</span></samp> and
-the ‘<samp><span class="samp">g++</span></samp>’ program name to
be transformed to
-<samp><span class="file">/usr/local/bin/gspecial++</span></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><span class="option">--program-transform-name='s/^gcc$/myowngcc/;
s/^g++$/gspecial++/'</span></samp>
+<samp>--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'</samp>
to achieve this effect.
-
- <p>All three options can be combined and used together, resulting in more
+</p>
+<p>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>.
-
- <p>As currently implemented, this option only takes effect for native
-builds; cross compiler binaries' names are not transformed even when a
+</p>
+<p>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.
-
- <p>For native builds, some of the installed programs are also installed
+</p>
+<p>For native builds, some of the installed programs are also installed
with the target alias in front of their name, as in
-‘<samp><span class="samp">i686-pc-linux-gnu-gcc</span></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><span class="option">--program-prefix=foo-</span></samp> and <samp><span
class="option">program-suffix=-3.1</span></samp>, the
+<samp>--program-prefix=foo-</samp> and <samp>program-suffix=-3.1</samp>, the
resulting binary would be installed as
-<samp><span
class="file">/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1</span></samp>.
-
- <p>As a last shortcoming, none of the installed Ada programs are
+<samp>/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1</samp>.
+</p>
+<p>As a last shortcoming, none of the installed Ada programs are
transformed yet, which will be fixed in some time.
-
- <br><dt><code>--with-local-prefix=</code><var>dirname</var><dd>Specify the
+</p>
+</dd>
+<dt><code>--with-local-prefix=<var>dirname</var></code></dt>
+<dd><p>Specify the
installation directory for local include files. The default is
-<samp><span class="file">/usr/local</span></samp>. Specify this option if you
want the compiler to
-search directory <samp><var>dirname</var><span
class="file">/include</span></samp> for locally installed
-header files <em>instead</em> of <samp><span
class="file">/usr/local/include</span></samp>.
-
- <p>You should specify <samp><span
class="option">--with-local-prefix</span></samp> <strong>only</strong> if your
-site has a different convention (not <samp><span
class="file">/usr/local</span></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 <em>instead</em> of <samp>/usr/local/include</samp>.
+</p>
+<p>You should specify <samp>--with-local-prefix</samp> <strong>only</strong>
if your
+site has a different convention (not <samp>/usr/local</samp>) for where to put
site-specific files.
-
- <p>The default value for <samp><span
class="option">--with-local-prefix</span></samp> is <samp><span
class="file">/usr/local</span></samp>
-regardless of the value of <samp><span class="option">--prefix</span></samp>.
Specifying
-<samp><span class="option">--prefix</span></samp> has no effect on which
directory GCC searches for
+</p>
+<p>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.
-
- <p>The purpose of <samp><span class="option">--prefix</span></samp> is to
specify where to <em>install
-GCC</em>. The local header files in <samp><span
class="file">/usr/local/include</span></samp>—if you put
+</p>
+<p>The purpose of <samp>--prefix</samp> is to specify where to <em>install
+GCC</em>. 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><span
class="option">--prefix</span></samp> value.)
-
- <p>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.)
+</p>
+<p>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.
-
- <p>Some autoconf macros add <samp><span class="option">-I
</span><var>directory</var></samp> options to the
+</p>
+<p>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.
-
- <p>GCC automatically searches for ordinary libraries using
-<samp><span class="env">GCC_EXEC_PREFIX</span></samp>. Thus, when the same
installation prefix is
+</p>
+<p>GCC automatically searches for ordinary libraries using
+<code>GCC_EXEC_PREFIX</code>. 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><span class="file">/usr</span></samp>.
-
- <p>Sites that need to install multiple versions of GCC may not want to
+installed as a system compiler in <samp>/usr</samp>.
+</p>
+<p>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><span class="option">--program-prefix</span></samp>, <samp><span
class="option">--program-suffix</span></samp> and
-<samp><span class="option">--program-transform-name</span></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><span class="option">--with-local-prefix</span></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 <samp><span class="env">LIBRARY_PATH</span></samp>).
-
- <p>The same value can be used for both <samp><span
class="option">--with-local-prefix</span></samp> and
-<samp><span class="option">--prefix</span></samp> provided it is not
<samp><span class="file">/usr</span></samp>. This can be used
-to avoid the default search of <samp><span
class="file">/usr/local/include</span></samp>.
-
- <p><strong>Do not</strong> specify <samp><span
class="file">/usr</span></samp> as the <samp><span
class="option">--with-local-prefix</span></samp>!
-The directory you use for <samp><span
class="option">--with-local-prefix</span></samp> <strong>must not</strong>
-contain any of the system's standard header files. If it did contain
+(e.g., with <code>LIBRARY_PATH</code>).
+</p>
+<p>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>.
+</p>
+<p><strong>Do not</strong> specify <samp>/usr</samp> as the
<samp>--with-local-prefix</samp>!
+The directory you use for <samp>--with-local-prefix</samp> <strong>must
not</strong>
+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 <samp><span
class="command">fixincludes</span></samp> script.
-
- <p>Indications are that people who use this option use it based on
mistaken
+file corrections made by the <code>fixincludes</code> script.
+</p>
+<p>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.
-
-
<br><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><span class="file">/usr/include</span></samp>.
This option is most useful
+</p>
+</dd>
+<dt><code>--with-native-system-header-dir=<var>dirname</var></code></dt>
+<dd><p>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><span class="option">--with-sysroot</span></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.
-
-
<br><dt><code>--enable-shared[=</code><var>package</var><code>[,...]]</code><dd>Build
shared versions of libraries, if shared libraries are supported on
+</p>
+</dd>
+<dt><code>--enable-shared[=<var>package</var>[,…]]</code></dt>
+<dd><p>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.
-
- <p>If a list of packages is given as an argument, build shared libraries
+</p>
+<p>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><span class="samp">libgcc</span></samp>’ (also known as
‘<samp><span class="samp">gcc</span></samp>’), ‘<samp><span
class="samp">libstdc++</span></samp>’ (not
-‘<samp><span class="samp">libstdc++-v3</span></samp>’),
‘<samp><span class="samp">libffi</span></samp>’, ‘<samp><span
class="samp">zlib</span></samp>’, ‘<samp><span
class="samp">boehm-gc</span></samp>’,
-‘<samp><span class="samp">ada</span></samp>’, ‘<samp><span
class="samp">libada</span></samp>’, ‘<samp><span
class="samp">libjava</span></samp>’, ‘<samp><span
class="samp">libgo</span></samp>’, and ‘<samp><span
class="samp">libobjc</span></samp>’.
-Note ‘<samp><span class="samp">libiberty</span></samp>’ does not
support shared libraries at all.
-
- <p>Use <samp><span class="option">--disable-shared</span></samp> to build
only static libraries. Note that
-<samp><span class="option">--disable-shared</span></samp> does not accept a
list of package names as
-argument, only <samp><span class="option">--enable-shared</span></samp> does.
-
- <br><dt><code><a
name="with_002dgnu_002das"></a>--with-gnu-as</code><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.
+</p>
+<p>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.
+</p>
+</dd>
+<dt><code><a name="with_002dgnu_002das"></a>--with-gnu-as</code></dt>
+<dd><p>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><span class="option">--with-gnu-as</span></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><span
class="option">--with-as=</span><var>pathname</var></samp> or
-<samp><span
class="option">--with-build-time-tools=</span><var>pathname</var></samp>.
-
- <p>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>.
+</p>
+<p>The following systems are the only ones where it makes a difference
whether you use the GNU assembler. On any other system,
-<samp><span class="option">--with-gnu-as</span></samp> has no effect.
-
- <ul>
-<li>‘<samp><span class="samp">hppa1.0-</span><var>any</var><span
class="samp">-</span><var>any</var></samp>’
-<li>‘<samp><span class="samp">hppa1.1-</span><var>any</var><span
class="samp">-</span><var>any</var></samp>’
-<li>‘<samp><span
class="samp">sparc-sun-solaris2.</span><var>any</var></samp>’
-<li>‘<samp><span class="samp">sparc64-</span><var>any</var><span
class="samp">-solaris2.</span><var>any</var></samp>’
-</ul>
-
- <br><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
+<samp>--with-gnu-as</samp> has no effect.
+</p>
+<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><p>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><span class="file">/gcc/</span><var>target</var><span
class="file">/</span><var>version</var></samp> directory.
-<var>libexec</var> defaults to <samp><var>exec-prefix</var><span
class="file">/libexec</span></samp>;
+</p><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><span class="file">/usr/local</span></samp> unless
overridden by the
-<samp><span class="option">--prefix=</span><var>pathname</var></samp> switch
described above. <var>target</var>
-is the target system triple, such as ‘<samp><span
class="samp">sparc-sun-solaris2.7</span></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>If the target system is the same that you are building on, check
-operating system specific directories (e.g. <samp><span
class="file">/usr/ccs/bin</span></samp> on
+</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
Sun Solaris 2).
- <li>Check in the <samp><span class="env">PATH</span></samp> for a
tool whose name is prefixed by the
+</li><li> Check in the <code>PATH</code> for a tool whose name is prefixed by
the
target system triple.
- <li>Check in the <samp><span class="env">PATH</span></samp> for a
tool whose name is not prefixed by the
+</li><li> Check in the <code>PATH</code> 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).
-</ul>
+the target as well).
+</li></ul>
- <p>You may want to use <samp><span class="option">--with-as</span></samp>
if no assembler
+<p>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.
-
- <br><dt><code><a
name="with_002dgnu_002dld"></a>--with-gnu-ld</code><dd>Same as <a
href="#with-gnu-as"><samp><span class="option">--with-gnu-as</span></samp></a>
+</p>
+</dd>
+<dt><code><a name="with_002dgnu_002dld"></a>--with-gnu-ld</code></dt>
+<dd><p>Same as <a href="#with-gnu-as"><samp>--with-gnu-as</samp></a>
but for the linker.
-
- <br><dt><code>--with-ld=</code><var>pathname</var><dd>Same as <a
href="#with-as"><samp><span class="option">--with-as</span></samp></a>
+</p>
+</dd>
+<dt><code>--with-ld=<var>pathname</var></code></dt>
+<dd><p>Same as <a href="#with-as"><samp>--with-as</samp></a>
but for the linker.
-
- <br><dt><code>--with-stabs</code><dd>Specify that stabs debugging
+</p>
+</dd>
+<dt><code>--with-stabs</code></dt>
+<dd><p>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.
-
- <p>On MIPS based systems and on Alphas, you must specify whether you want
+</p>
+<p>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.
-
- <p>Normally, GCC uses the ECOFF debugging format by default; if you
-prefer BSD stabs, specify <samp><span
class="option">--with-stabs</span></samp> when you configure GCC.
-
- <p>No matter which default you choose when you configure GCC, the user
-can use the <samp><span class="option">-gcoff</span></samp> and <samp><span
class="option">-gstabs+</span></samp> options to specify explicitly
+</p>
+<p>Normally, GCC uses the ECOFF debugging format by default; if you
+prefer BSD stabs, specify <samp>--with-stabs</samp> when you configure GCC.
+</p>
+<p>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.
-
- <p><samp><span class="option">--with-stabs</span></samp> is meaningful on
the ISC system on the 386, also, if
-<samp><span class="option">--with-gas</span></samp> is used. It selects use
of stabs debugging
+</p>
+<p><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.
-
- <p><samp><span class="option">--with-stabs</span></samp> is also
meaningful on 386 systems running SVR4. It
+</p>
+<p><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.
-
- <br><dt><code>--with-tls=</code><var>dialect</var><dd>Specify the default
TLS dialect, for systems were there is a choice.
+</p>
+</dd>
+<dt><code>--with-tls=<var>dialect</var></code></dt>
+<dd><p>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.
-
- <br><dt><code>--enable-multiarch</code><dd>Specify whether to enable or
disable multiarch support. The default is
+</p>
+</dd>
+<dt><code>--enable-multiarch</code></dt>
+<dd><p>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><span
class="option">--with-sysroot</span></samp>, and without
-<samp><span class="option">--with-native-system-header-dir</span></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>.
-
- <br><dt><code>--disable-multilib</code><dd>Specify that multiple target
+</p>
+</dd>
+<dt><code>--disable-multilib</code></dt>
+<dd><p>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.
-
- <p>Some targets provide finer-grained control over which multilibs are
built
-(e.g., <samp><span class="option">--disable-softfloat</span></samp>):
- <dl>
-<dt><code>arm-*-*</code><dd>fpu, 26bit, underscore, interwork, biendian,
nofmult.
-
- <br><dt><code>m68*-*-*</code><dd>softfloat, m68881, m68000, m68020.
-
- <br><dt><code>mips*-*-*</code><dd>single-float, biendian, softfloat.
-
- <br><dt><code>powerpc*-*-*, rs6000*-*-*</code><dd>aix64, pthread,
softfloat, powercpu, powerpccpu, powerpcos, biendian,
+</p>
+<p>Some targets provide finer-grained control over which multilibs are built
+(e.g., <samp>--disable-softfloat</samp>):
+</p><dl compact="compact">
+<dt><code>arm-*-*</code></dt>
+<dd><p>fpu, 26bit, underscore, interwork, biendian, nofmult.
+</p>
+</dd>
+<dt><code>m68*-*-*</code></dt>
+<dd><p>softfloat, m68881, m68000, m68020.
+</p>
+</dd>
+<dt><code>mips*-*-*</code></dt>
+<dd><p>single-float, biendian, softfloat.
+</p>
+</dd>
+<dt><code>powerpc*-*-*, rs6000*-*-*</code></dt>
+<dd><p>aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
sysv, aix.
+</p>
+</dd>
+</dl>
- </dl>
-
-
<br><dt><code>--with-multilib-list=</code><var>list</var><dt><code>--without-multilib-list</code><dd>Specify
what multilibs to build.
+</dd>
+<dt><code>--with-multilib-list=<var>list</var></code></dt>
+<dt><code>--without-multilib-list</code></dt>
+<dd><p>Specify what multilibs to build.
Currently only implemented for sh*-*-* and x86-64-*-linux*.
-
- <dl>
-<dt><code>sh*-*-*</code><dd><var>list</var> is a comma separated list of CPU
names. These must be of the
+</p>
+<dl compact="compact">
+<dt><code>sh*-*-*</code></dt>
+<dd><p><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><span class="option">--with-endian</span></samp>.
-
- <p>If <var>list</var> is empty, then there will be no multilibs for
extra
+these are handled by <samp>--with-endian</samp>.
+</p>
+<p>If <var>list</var> is empty, then there will be no multilibs for extra
processors. The multilib for the secondary endian remains enabled.
-
- <p>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><span
class="samp">MULTILIB_EXCLUDES</span></samp>’
+</p>
+<p>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).
-
- <p>If <samp><span class="option">--with-multilib-list</span></samp>
is not given, then a default set of
-multilibs is selected based on the value of <samp><span
class="option">--target</span></samp>. This is
+</p>
+<p>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.
-
- <p>Example 1: to configure a compiler for SH4A only, but supporting
both
+</p>
+<p>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>
- <p>Example 2: to configure a compiler for both SH4A and SH4AL-DSP,
but with
+</p><div class="smallexample">
+<pre class="smallexample">--with-cpu=sh4a --with-endian=little,big
--with-multilib-list=
+</pre></div>
+
+<p>Example 2: to configure a compiler for both SH4A and SH4AL-DSP, but with
only little endian SH4AL:
- <pre class="smallexample"> --with-cpu=sh4a
--with-endian=little,big \
- --with-multilib-list=sh4al,!mb/m4al
-</pre>
- <br><dt><code>x86-64-*-linux*</code><dd><var>list</var> is a comma
separated list of <code>m32</code>, <code>m64</code> and
+</p><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><p><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.
-
- <p>If <samp><span class="option">--with-multilib-list</span></samp>
is not given, then only 32-bit and
-64-bit run-time libraries will be enabled.
+</p>
+<p>If <samp>--with-multilib-list</samp> is not given, then only 32-bit and
+64-bit run-time libraries will be enabled.
+</p></dd>
</dl>
- <br><dt><code>--with-endian=</code><var>endians</var><dd>Specify what
endians to use.
+</dd>
+<dt><code>--with-endian=<var>endians</var></code></dt>
+<dd><p>Specify what endians to use.
Currently only implemented for sh*-*-*.
-
- <p><var>endians</var> may be one of the following:
- <dl>
-<dt><code>big</code><dd>Use big endian exclusively.
-<br><dt><code>little</code><dd>Use little endian exclusively.
-<br><dt><code>big,little</code><dd>Use big endian by default. Provide a
multilib for little endian.
-<br><dt><code>little,big</code><dd>Use little endian by default. Provide a
multilib for big endian.
+</p>
+<p><var>endians</var> may be one of the following:
+</p><dl compact="compact">
+<dt><code>big</code></dt>
+<dd><p>Use big endian exclusively.
+</p></dd>
+<dt><code>little</code></dt>
+<dd><p>Use little endian exclusively.
+</p></dd>
+<dt><code>big,little</code></dt>
+<dd><p>Use big endian by default. Provide a multilib for little endian.
+</p></dd>
+<dt><code>little,big</code></dt>
+<dd><p>Use little endian by default. Provide a multilib for big endian.
+</p></dd>
</dl>
- <br><dt><code>--enable-threads</code><dd>Specify that the target
+</dd>
+<dt><code>--enable-threads</code></dt>
+<dd><p>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.
-
- <p>In general, the best (and, in many cases, the only known) threading
+</p>
+<p>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><span
class="option">--enable-threads</span></samp> is an
-alias for <samp><span class="option">--enable-threads=single</span></samp>.
-
- <br><dt><code>--disable-threads</code><dd>Specify that threading support
should be disabled for the system.
-This is an alias for <samp><span
class="option">--enable-threads=single</span></samp>.
-
- <br><dt><code>--enable-threads=</code><var>lib</var><dd>Specify that
+available for the system. In this case, <samp>--enable-threads</samp> is an
+alias for <samp>--enable-threads=single</samp>.
+</p>
+</dd>
+<dt><code>--disable-threads</code></dt>
+<dd><p>Specify that threading support should be disabled for the system.
+This is an alias for <samp>--enable-threads=single</samp>.
+</p>
+</dd>
+<dt><code>--enable-threads=<var>lib</var></code></dt>
+<dd><p>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>
-<dt><code>aix</code><dd>AIX thread support.
-<br><dt><code>dce</code><dd>DCE thread support.
-<br><dt><code>lynx</code><dd>LynxOS thread support.
-<br><dt><code>mipssde</code><dd>MIPS SDE thread support.
-<br><dt><code>no</code><dd>This is an alias for ‘<samp><span
class="samp">single</span></samp>’.
-<br><dt><code>posix</code><dd>Generic POSIX/Unix98 thread support.
-<br><dt><code>rtems</code><dd>RTEMS thread support.
-<br><dt><code>single</code><dd>Disable thread support, should work for all
platforms.
-<br><dt><code>tpf</code><dd>TPF thread support.
-<br><dt><code>vxworks</code><dd>VxWorks thread support.
-<br><dt><code>win32</code><dd>Microsoft Win32 API thread support.
+</p>
+<dl compact="compact">
+<dt><code>aix</code></dt>
+<dd><p>AIX thread support.
+</p></dd>
+<dt><code>dce</code></dt>
+<dd><p>DCE thread support.
+</p></dd>
+<dt><code>lynx</code></dt>
+<dd><p>LynxOS thread support.
+</p></dd>
+<dt><code>mipssde</code></dt>
+<dd><p>MIPS SDE thread support.
+</p></dd>
+<dt><code>no</code></dt>
+<dd><p>This is an alias for ‘<samp>single</samp>’.
+</p></dd>
+<dt><code>posix</code></dt>
+<dd><p>Generic POSIX/Unix98 thread support.
+</p></dd>
+<dt><code>rtems</code></dt>
+<dd><p>RTEMS thread support.
+</p></dd>
+<dt><code>single</code></dt>
+<dd><p>Disable thread support, should work for all platforms.
+</p></dd>
+<dt><code>tpf</code></dt>
+<dd><p>TPF thread support.
+</p></dd>
+<dt><code>vxworks</code></dt>
+<dd><p>VxWorks thread support.
+</p></dd>
+<dt><code>win32</code></dt>
+<dd><p>Microsoft Win32 API thread support.
+</p></dd>
</dl>
- <br><dt><code>--enable-tls</code><dd>Specify that the target supports TLS
(Thread Local Storage). Usually
+</dd>
+<dt><code>--enable-tls</code></dt>
+<dd><p>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><span class="option">--enable-tls</span></samp> or <samp><span
class="option">--disable-tls</span></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.
-
- <br><dt><code>--disable-tls</code><dd>Specify that the target does not
support TLS.
-This is an alias for <samp><span class="option">--enable-tls=no</span></samp>.
-
-
<br><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><span
class="option">-mcpu=</span></samp> switch.
+</p>
+</dd>
+<dt><code>--disable-tls</code></dt>
+<dd><p>Specify that the target does not support TLS.
+This is an alias for <samp>--enable-tls=no</samp>.
+</p>
+</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><p>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><span
class="option">--with-cpu-32</span></samp> and
-<samp><span class="option">--with-cpu-64</span></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.
-
-
<br><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><span
class="option">-mschedule=</span></samp>,
-<samp><span class="option">-march=</span></samp>, <samp><span
class="option">-mtune=</span></samp>, <samp><span
class="option">-mabi=</span></samp>, and <samp><span
class="option">-mfpu=</span></samp>
-options and for <samp><span class="option">-mhard-float</span></samp> or
<samp><span class="option">-msoft-float</span></samp>. As with
-<samp><span class="option">--with-cpu</span></samp>, which switches will be
accepted and acceptable values
+</p>
+</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><p>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.
-
- <br><dt><code>--with-mode=</code><var>mode</var><dd>Specify if the
compiler should default to <samp><span class="option">-marm</span></samp> or
<samp><span class="option">-mthumb</span></samp>.
+</p>
+</dd>
+<dt><code>--with-mode=<var>mode</var></code></dt>
+<dd><p>Specify if the compiler should default to <samp>-marm</samp> or
<samp>-mthumb</samp>.
This option is only supported on ARM targets.
-
- <br><dt><code>--with-stack-offset=</code><var>num</var><dd>This option
sets the default for the -mstack-offset=<var>num</var> option,
+</p>
+</dd>
+<dt><code>--with-stack-offset=<var>num</var></code></dt>
+<dd><p>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.
-
- <br><dt><code>--with-fpmath=</code><var>isa</var><dd>This options sets
<samp><span class="option">-mfpmath=sse</span></samp> by default and specifies
the default
-ISA for floating-point arithmetics. You can select either ‘<samp><span
class="samp">sse</span></samp>’ which
-enables <samp><span class="option">-msse2</span></samp> or ‘<samp><span
class="samp">avx</span></samp>’ which enables <samp><span
class="option">-mavx</span></samp> by default.
+</p>
+</dd>
+<dt><code>--with-fpmath=<var>isa</var></code></dt>
+<dd><p>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.
-
- <br><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.
+</p>
+</dd>
+<dt><code>--with-divide=<var>type</var></code></dt>
+<dd><p>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>
-<dt><code>traps</code><dd>Division by zero checks use conditional traps (this
is the default on
-systems that support conditional traps).
-<br><dt><code>breaks</code><dd>Division by zero checks use the break
instruction.
+</p><dl compact="compact">
+<dt><code>traps</code></dt>
+<dd><p>Division by zero checks use conditional traps (this is the default on
+systems that support conditional traps).
+</p></dd>
+<dt><code>breaks</code></dt>
+<dd><p>Division by zero checks use the break instruction.
+</p></dd>
</dl>
- <!-- If you make -with-llsc the default for additional targets, -->
- <!-- update the -with-llsc description in the MIPS section below. -->
- <br><dt><code>--with-llsc</code><dd>On MIPS targets, make <samp><span
class="option">-mllsc</span></samp> the default when no
-<samp><span class="option">-mno-llsc</span></samp> option is passed. This is
the default for
+
+</dd>
+<dt><code>--with-llsc</code></dt>
+<dd><p>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.
-
- <br><dt><code>--without-llsc</code><dd>On MIPS targets, make <samp><span
class="option">-mno-llsc</span></samp> the default when no
-<samp><span class="option">-mllsc</span></samp> option is passed.
-
- <br><dt><code>--with-synci</code><dd>On MIPS targets, make <samp><span
class="option">-msynci</span></samp> the default when no
-<samp><span class="option">-mno-synci</span></samp> option is passed.
-
- <br><dt><code>--without-synci</code><dd>On MIPS targets, make <samp><span
class="option">-mno-synci</span></samp> the default when no
-<samp><span class="option">-msynci</span></samp> option is passed. This is
the default.
-
- <br><dt><code>--with-mips-plt</code><dd>On MIPS targets, make use of copy
relocations and PLTs.
+</p>
+</dd>
+<dt><code>--without-llsc</code></dt>
+<dd><p>On MIPS targets, make <samp>-mno-llsc</samp> the default when no
+<samp>-mllsc</samp> option is passed.
+</p>
+</dd>
+<dt><code>--with-synci</code></dt>
+<dd><p>On MIPS targets, make <samp>-msynci</samp> the default when no
+<samp>-mno-synci</samp> option is passed.
+</p>
+</dd>
+<dt><code>--without-synci</code></dt>
+<dd><p>On MIPS targets, make <samp>-mno-synci</samp> the default when no
+<samp>-msynci</samp> option is passed. This is the default.
+</p>
+</dd>
+<dt><code>--with-mips-plt</code></dt>
+<dd><p>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.
-
- <br><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.
+</p>
+</dd>
+<dt><code>--enable-__cxa_atexit</code></dt>
+<dd><p>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><span class="option">-fuse-cxa-atexit</span></samp> to be passed by
default.
-
- <br><dt><code>--enable-gnu-indirect-function</code><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.
+</p>
+</dd>
+<dt><code>--enable-gnu-indirect-function</code></dt>
+<dd><p>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.
-
- <br><dt><code>--enable-target-optspace</code><dd>Specify that target
-libraries should be optimized for code space instead of code speed.
+</p>
+</dd>
+<dt><code>--enable-target-optspace</code></dt>
+<dd><p>Specify that target
+libraries should be optimized for code space instead of code speed.
This is the default for the m32r platform.
-
- <br><dt><code>--with-cpp-install-dir=</code><var>dirname</var><dd>Specify
that the user visible <samp><span class="command">cpp</span></samp> program
should be installed
-in <samp><var>prefix</var><span class="file">/</span><var>dirname</var><span
class="file">/cpp</span></samp>, in addition to <var>bindir</var>.
-
- <br><dt><code>--enable-comdat</code><dd>Enable COMDAT group support.
This is primarily used to override the
+</p>
+</dd>
+<dt><code>--with-cpp-install-dir=<var>dirname</var></code></dt>
+<dd><p>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>.
+</p>
+</dd>
+<dt><code>--enable-comdat</code></dt>
+<dd><p>Enable COMDAT group support. This is primarily used to override the
automatically detected value.
-
- <br><dt><code>--enable-initfini-array</code><dd>Force the use of sections
<code>.init_array</code> and <code>.fini_array</code>
+</p>
+</dd>
+<dt><code>--enable-initfini-array</code></dt>
+<dd><p>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><span
class="option">--disable-initfini-array</span></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.
-
- <br><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><span
class="file">gcc.pot</span></samp> are normally
+</p>
+</dd>
+<dt><code>--enable-maintainer-mode</code></dt>
+<dd><p>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><span
class="option">--enable-maintainer-mode</span></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.
-
- <br><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><span
class="samp">make</span></samp>’ is invoked,
+</p>
+</dd>
+<dt><code>--disable-bootstrap</code></dt>
+<dd><p>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><span
class="option">--disable-bootstrap</span></samp>.
-
- <br><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 process, you can configure with <samp>--disable-bootstrap</samp>.
+</p>
+</dd>
+<dt><code>--enable-bootstrap</code></dt>
+<dd><p>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><span class="option">--enable-bootstrap</span></samp>.
-
- <br><dt><code>--enable-generated-files-in-srcdir</code><dd>Neither the .c
and .h files that are generated from Bison and flex nor the
+with <samp>--enable-bootstrap</samp>.
+</p>
+</dd>
+<dt><code>--enable-generated-files-in-srcdir</code></dt>
+<dd><p>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.
-
- <p>If you configure with <samp><span
class="option">--enable-generated-files-in-srcdir</span></samp> then those
+</p>
+<p>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.
-
- <br><dt><code>--enable-version-specific-runtime-libs</code><dd>Specify
+</p>
+</dd>
+<dt><code>--enable-version-specific-runtime-libs</code></dt>
+<dd><p>Specify
that runtime libraries should be installed in the compiler specific
-subdirectory (<samp><var>libdir</var><span class="file">/gcc</span></samp>)
rather than the usual places. In
-addition, ‘<samp><span class="samp">libstdc++</span></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><span
class="option">--with-gxx-include-dir=</span><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><span
class="samp">libgfortran</span></samp>’,
-‘<samp><span class="samp">libjava</span></samp>’,
‘<samp><span class="samp">libmudflap</span></samp>’,
‘<samp><span class="samp">libstdc++</span></samp>’, and
‘<samp><span class="samp">libobjc</span></samp>’.
-
-
<br><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
+parallel. This is currently supported by
‘<samp>libgfortran</samp>’,
+‘<samp>libjava</samp>’, ‘<samp>libmudflap</samp>’,
‘<samp>libstdc++</samp>’, and ‘<samp>libobjc</samp>’.
+</p>
+</dd>
+<dt><code>--enable-languages=<var>lang1</var>,<var>lang2</var>,…</code></dt>
+<dd><p>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><span class="file">gcc</span></samp> directory of your GCC source
tree:<br>
- <pre class="smallexample"> grep language= */config-lang.in
-</pre>
- <p>Currently, you can use any of the following:
+<samp>gcc</samp> directory of your GCC source tree:<br>
+</p><div class="smallexample">
+<pre class="smallexample">grep language= */config-lang.in
+</pre></div>
+<p>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><span class="file">gcc</span></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.
-
-
<br><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
+</p>
+</dd>
+<dt><code>--enable-stage1-languages=<var>lang1</var>,<var>lang2</var>,…</code></dt>
+<dd><p>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><span class="option">--enable-languages</span></samp>, and the option
<code>all</code> will select all
-of the languages enabled by <samp><span
class="option">--enable-languages</span></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 <samp><span
class="command">make
-stage1-bubble all-target</span></samp>, or run the testsuite on the stage-1
compiler
-for the specified languages using <samp><span class="command">make
stage1-start check-gcc</span></samp>.
-
- <br><dt><code>--disable-libada</code><dd>Specify that the run-time
libraries and tools used by GNAT should not
+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>.
+</p>
+</dd>
+<dt><code>--disable-libada</code></dt>
+<dd><p>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><span class="samp">make -C gcc
gnatlib_and_tools</span></samp>’.
-
- <br><dt><code>--disable-libssp</code><dd>Specify that the run-time
libraries for stack smashing protection
+do a ‘<samp>make -C gcc gnatlib_and_tools</samp>’.
+</p>
+</dd>
+<dt><code>--disable-libssp</code></dt>
+<dd><p>Specify that the run-time libraries for stack smashing protection
should not be built.
-
- <br><dt><code>--disable-libquadmath</code><dd>Specify that the GCC
quad-precision math library should not be built.
+</p>
+</dd>
+<dt><code>--disable-libquadmath</code></dt>
+<dd><p>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><span
class="option">--disable-libquadmath-support</span></samp>
+the Fortran front end, unless <samp>--disable-libquadmath-support</samp>
is used.
-
- <br><dt><code>--disable-libquadmath-support</code><dd>Specify that the
Fortran front end and <code>libgfortran</code> do not add
+</p>
+</dd>
+<dt><code>--disable-libquadmath-support</code></dt>
+<dd><p>Specify that the Fortran front end and <code>libgfortran</code> do not
add
support for <code>libquadmath</code> on systems supporting it.
-
- <br><dt><code>--disable-libgomp</code><dd>Specify that the run-time
libraries used by GOMP should not be built.
-
- <br><dt><code>--with-dwarf2</code><dd>Specify that the compiler should
+</p>
+</dd>
+<dt><code>--disable-libgomp</code></dt>
+<dd><p>Specify that the run-time libraries used by GOMP should not be built.
+</p>
+</dd>
+<dt><code>--with-dwarf2</code></dt>
+<dd><p>Specify that the compiler should
use DWARF 2 debugging information as the default.
-
-
<br><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.
+</p>
+</dd>
+<dt><code>--enable-targets=all</code></dt>
+<dt><code>--enable-targets=<var>target_list</var></code></dt>
+<dd><p>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.
-
- <br><dt><code>--enable-secureplt</code><dd>This option enables
<samp><span class="option">-msecure-plt</span></samp> by default for
powerpc-linux.
+</p>
+</dd>
+<dt><code>--enable-secureplt</code></dt>
+<dd><p>This option enables <samp>-msecure-plt</samp> by default for
powerpc-linux.
See “RS/6000 and PowerPC Options” in the main manual
-
- <br><dt><code>--enable-cld</code><dd>This option enables <samp><span
class="option">-mcld</span></samp> by default for 32-bit x86 targets.
+</p>
+</dd>
+<dt><code>--enable-cld</code></dt>
+<dd><p>This option enables <samp>-mcld</samp> by default for 32-bit x86
targets.
See “i386 and x86-64 Options” in the main manual
-
-
<br><dt><code>--enable-win32-registry</code><dt><code>--enable-win32-registry=</code><var>key</var><dt><code>--disable-win32-registry</code><dd>The
<samp><span class="option">--enable-win32-registry</span></samp> option
enables Microsoft Windows-hosted GCC
+</p>
+</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><p>The <samp>--enable-win32-registry</samp> option enables Microsoft
Windows-hosted GCC
to look up installations paths in the registry using the following key:
+</p>
+<div class="smallexample">
+<pre class="smallexample"><code>HKEY_LOCAL_MACHINE\SOFTWARE\Free Software
Foundation\<var>key</var></code>
+</pre></div>
- <pre class="smallexample">
<code>HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\</code><var>key</var>
-</pre>
- <p><var>key</var> defaults to GCC version number, and can be overridden
by the
-<samp><span
class="option">--enable-win32-registry=</span><var>key</var></samp> option.
Vendors and distributors
+<p><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><span
class="option">--disable-win32-registry</span></samp>
+by default, and can be disabled by <samp>--disable-win32-registry</samp>
option. This option has no effect on the other hosts.
-
- <br><dt><code>--nfp</code><dd>Specify that the machine does not have a
floating point unit. This
-option only applies to ‘<samp><span
class="samp">m68k-sun-sunos</span><var>n</var></samp>’. On any other
-system, <samp><span class="option">--nfp</span></samp> has no effect.
-
-
<br><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><span class="option">-Werror</span></samp> in
bootstrap stage2 and later.
-If you don't specify it, <samp><span class="option">-Werror</span></samp> is
turned on for the main
+</p>
+</dd>
+<dt><code>--nfp</code></dt>
+<dd><p>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.
+</p>
+</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><p>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><span
class="option">-Werror</span></samp> are
+final releases. The specific files which get <samp>-Werror</samp> are
controlled by the Makefiles.
-
-
<br><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
+</p>
+</dd>
+<dt><code>--enable-checking</code></dt>
+<dt><code>--enable-checking=<var>list</var></code></dt>
+<dd><p>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
[ *** diff truncated: 206387 lines dropped *** ]
############################################################################
Revision: btrev43097
Commit: 1a00a76b58ae57d24bd4d774f6323c4ea62dd1e7
URL: http://cgit.haiku-os.org/buildtools/commit/?id=1a00a76
Author: Jérôme Duval <jerome.duval@xxxxxxxxx>
Date: Sun Dec 21 11:11:47 2014 UTC
Merge gcc 4.8.4
----------------------------------------------------------------------------
Other related posts:
- » [haiku-commits] buildtools: btrev43097 - in gcc: gcc/doc gcc/fortran . INSTALL gcc - jerome . duval
