diff options
| author | Lorry Tar Creator <lorry-tar-importer@baserock.org> | 2014-10-30 09:35:42 +0000 |
|---|---|---|
| committer | <> | 2015-01-09 11:51:27 +0000 |
| commit | c27a97d04853380f1e80525391b3f0d156ed4c84 (patch) | |
| tree | 68ffaade7c605bc80cffa18360799c98a810976f /INSTALL | |
| parent | 6af3fdec2262dd94954acc5e426ef71cbd4521d3 (diff) | |
| download | gcc-tarball-c27a97d04853380f1e80525391b3f0d156ed4c84.tar.gz | |
Imported from /home/lorry/working-area/delta_gcc-tarball/gcc-4.9.2.tar.bz2.gcc-4.9.2
Diffstat (limited to 'INSTALL')
| -rw-r--r-- | INSTALL/README | 1 | ||||
| -rw-r--r-- | INSTALL/binaries.html | 210 | ||||
| -rw-r--r-- | INSTALL/build.html | 513 | ||||
| -rw-r--r-- | INSTALL/configure.html | 2285 | ||||
| -rw-r--r-- | INSTALL/download.html | 177 | ||||
| -rw-r--r-- | INSTALL/finalinstall.html | 279 | ||||
| -rw-r--r-- | INSTALL/gfdl.html | 472 | ||||
| -rw-r--r-- | INSTALL/index.html | 218 | ||||
| -rw-r--r-- | INSTALL/old.html | 304 | ||||
| -rw-r--r-- | INSTALL/prerequisites.html | 590 | ||||
| -rw-r--r-- | INSTALL/specific.html | 2161 | ||||
| -rw-r--r-- | INSTALL/test.html | 413 |
12 files changed, 4290 insertions, 3333 deletions
diff --git a/INSTALL/README b/INSTALL/README index 27bd1738bc..6d19791057 100644 --- a/INSTALL/README +++ b/INSTALL/README @@ -4,3 +4,4 @@ For releases the installation documentation is generated from gcc/doc/install.texi and copied into this directory. To read this documentation, please point your HTML browser to "index.html". +The latest version is always available at http://gcc.gnu.org/install/ . diff --git a/INSTALL/binaries.html b/INSTALL/binaries.html index 40eb488064..fb6c15abca 100644 --- a/INSTALL/binaries.html +++ b/INSTALL/binaries.html @@ -1,126 +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, 1989, 1992, 1993, 1994, 1995, 1996, 1997, -1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, -2010 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-2014 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>SGI IRIX: - <ul> -<li><a href="http://nekochan.net/">Nekoware</a> - <li><a href="http://jupiterrise.com/tgcware/">TGCware</a> -</ul> +<a name="index-Binaries"></a> +<a name="index-Installing-GCC_003a-Binaries"></a> - <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> +<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><a href="ftp://ftp.thewrittenword.com/packages/by-name/">The Written Word</a> offers binaries for +</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, -IRIX 6.5, -Tru64 UNIX 4.0D and 5.1, 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/INSTALL/build.html b/INSTALL/build.html index d70e10a5a6..1f7f22f046 100644 --- a/INSTALL/build.html +++ b/INSTALL/build.html @@ -1,380 +1,457 @@ -<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, 1989, 1992, 1993, 1994, 1995, 1996, 1997, -1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, -2010 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-2014 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> +<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. +</p> +<hr /> +<p><p><a href="./index.html">Return to the GCC Installation page</a> +</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. +<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/INSTALL/configure.html b/INSTALL/configure.html index 1a83c50f98..e1c858775d 100644 --- a/INSTALL/configure.html +++ b/INSTALL/configure.html @@ -1,1301 +1,1842 @@ -<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, 1989, 1992, 1993, 1994, 1995, 1996, 1997, -1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, -2010 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-2014 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> +<p>Contrast with <samp>--enable-host-shared</samp>, which affects <em>host</em> +code. +</p> +</dd> +<dt><code>--enable-host-shared</code></dt> +<dd><p>Specify that the <em>host</em> code should be built into position-independent +machine code (with -fPIC), allowing it to be used within shared libraries, +but yielding a slightly slower compiler. +</p> +<p>Currently this option is only of use to people developing GCC itself. +</p> +<p>Contrast with <samp>--enable-shared</samp>, which affects <em>target</em> +libraries. +</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>--enable-vtable-verify</code></dt> +<dd><p>Specify whether to enable or disable the vtable verification feature. +Enabling this feature causes libstdc++ to be built with its virtual calls +in verifiable mode. This means that, when linked with libvtv, every +virtual call in libstdc++ will verify the vtable pointer through which the +call will be made before actually making the call. If not linked with libvtv, +the verifier will call stub functions (in libstdc++ itself) and do nothing. +If vtable verification is disabled, then libstdc++ is not built with its +virtual calls in verifiable mode at all. However the libvtv library will +still be built (see <samp>--disable-libvtv</samp> to turn off building libvtv). +<samp>--disable-vtable-verify</samp> is the default. +</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. -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 +</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 ARC, ARM, i386, M68k, +PowerPC, and SPARC. It is mandatory for ARC. 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-nan=<var>encoding</var></code></dt> +<dd><p>On MIPS targets, set the default encoding convention to use for the +special not-a-number (NaN) IEEE 754 floating-point data. The +possibilities for <var>encoding</var> are: +</p><dl compact="compact"> +<dt><code>legacy</code></dt> +<dd><p>Use the legacy encoding, as with the <samp>-mnan=legacy</samp> command-line +option. +</p></dd> +<dt><code>2008</code></dt> +<dd><p>Use the 754-2008 encoding, as with the <samp>-mnan=2008</samp> command-line +option. +</p></dd> +</dl> +<p>To use this configuration option you must have an assembler version +installed that supports the <samp>-mnan=</samp> command-line option too. +In the absence of this configuration option the default convention is +the legacy encoding, as when neither of the <samp>-mnan=2008</samp> and +<samp>-mnan=legacy</samp> command-line options has been used. +</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-build-with-cxx</code><dd>Build GCC using a C++ compiler rather than a C compiler. This is an -experimental option which may become the default in a later release. - - <br><dt><code>--enable-build-poststage1-with-cxx</code><dd>When bootstrapping, build stages 2 and 3 of GCC using a C++ compiler -rather than a C compiler. Stage 1 is still built with a C compiler. -This is enabled by default and may be disabled using -<samp><span class="option">--disable-build-poststage1-with-cxx</span></samp>. - - <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-link-mutex</code></dt> +<dd><p>When building GCC, use a mutex to avoid linking the compilers for +multiple languages at the same time, to avoid thrashing on build +systems with limited free memory. The default is not to use such a mutex. +</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>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-libsanitizer</code></dt> +<dd><p>Specify that the run-time libraries for the various sanitizers should +not be built. +</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>--disable-libvtv</code></dt> +<dd><p>Specify that the run-time libraries used by vtable verification +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 slow down the compiler and may only work properly if you are building -the compiler with GCC. This is ‘<samp><span class="samp">yes</span></samp>’ by default when building -from SVN or snapshots, but ‘<samp><span class="samp">release</span></samp>’ for releases. The default -for building the stage1 compiler is ‘<samp><span class="samp">yes</span></samp>’. More control +the compiler with GCC. This is ‘<samp>yes</samp>’ by default when building +from SVN or snapshots, but ‘<samp>release</samp>’ for releases. The default +for building the stage1 compiler is ‘<samp>yes</samp>’. More control over the checks may be had by specifying <var>list</var>. The categories of -checks available are ‘<samp><span class="samp">yes</span></samp>’ (most common checks -‘<samp><span class="samp">assert,misc,tree,gc,rtlflag,runtime</span></samp>’), ‘<samp><span class="samp">no</span></samp>’ (no checks at -all), ‘<samp><span class="samp">all</span></samp>’ (all but ‘<samp><span class="samp">valgrind</span></samp>’), ‘<samp><span class="samp">release</span></samp>’ (cheapest -checks ‘<samp><span class="samp">assert,runtime</span></samp>’) or ‘<samp><span class="samp">none</span></samp>’ (same as ‘<samp><span class="samp">no</span></samp>’). -Individual checks can be enabled with these flags ‘<samp><span class="samp">assert</span></samp>’, -‘<samp><span class="samp">df</span></samp>’, ‘<samp><span class="samp">fold</span></samp>’, ‘<samp><span class="samp">gc</span></samp>’, ‘<samp><span class="samp">gcac</span></samp>’ ‘<samp><span class="samp">misc</span></samp>’, ‘<samp><span class="samp">rtl</span></samp>’, -‘<samp><span class="samp">rtlflag</span></samp>’, ‘<samp><span class="samp">runtime</span></samp>’, ‘<samp><span class="samp">tree</span></samp>’, and ‘<samp><span class="samp">valgrind</span></samp>’. - - <p>The ‘<samp><span class="samp">valgrind</span></samp>’ check requires the external <samp><span class="command">valgrind</span></samp> +checks available are ‘<samp>yes</samp>’ (most common checks +‘<samp>assert,misc,tree,gc,rtlflag,runtime</samp>’), ‘<samp>no</samp>’ (no checks at +all), ‘<samp>all</samp>’ (all but ‘<samp>valgrind</samp>’), ‘<samp>release</samp>’ (cheapest +checks ‘<samp>assert,runtime</samp>’) or ‘<samp>none</samp>’ (same as ‘<samp>no</samp>’). +Individual checks can be enabled with these flags ‘<samp>assert</samp>’, +‘<samp>df</samp>’, ‘<samp>fold</samp>’, ‘<samp>gc</samp>’, ‘<samp>gcac</samp>’ ‘<samp>misc</samp>’, ‘<samp>rtl</samp>’, +‘<samp>rtlflag</samp>’, ‘<samp>runtime</samp>’, ‘<samp>tree</samp>’, and ‘<samp>valgrind</samp>’. +</p> +<p>The ‘<samp>valgrind</samp>’ check requires the external <code>valgrind</code> simulator, available from <a href="http://valgrind.org/">http://valgrind.org/</a>. The -‘<samp><span class="samp">df</span></samp>’, ‘<samp><span class="samp">rtl</span></samp>’, ‘<samp><span class="samp">gcac</span></samp>’ and ‘<samp><span class="samp">valgrind</span></samp>’ checks are very expensive. -To disable all checking, ‘<samp><span class="samp">--disable-checking</span></samp>’ or -‘<samp><span class="samp">--enable-checking=none</span></samp>’ must be explicitly requested. Disabling +‘<samp>df</samp>’, ‘<samp>rtl</samp>’, ‘<samp>gcac</samp>’ and ‘<samp>valgrind</samp>’ checks are very expensive. +To disable all checking, ‘<samp>--disable-checking</samp>’ or +‘<samp>--enable-checking=none</samp>’ must be explicitly requested. Disabling assertions will make the compiler and runtime slightly faster but increase the risk of undetected internal errors causing wrong code to be generated. - - <br><dt><code>--disable-stage1-checking</code><dt><code>--enable-stage1-checking</code><dt><code>--enable-stage1-checking=</code><var>list</var><dd>If no <samp><span class="option">--enable-checking</span></samp> option is specified the stage1 -compiler will be built with ‘<samp><span class="samp">yes</span></samp>’ checking enabled, otherwise +</p> +</dd> +<dt><code>--disable-stage1-checking</code></dt> +<dt><code>--enable-stage1-checking</code></dt> +<dt><code>--enable-stage1-checking=<var>list</var></code></dt> +<dd><p>If no <samp>--enable-checking</samp> option is specified the stage1 +compiler will be built with ‘<samp>yes</samp>’ checking enabled, otherwise the stage1 checking flags are the same as specified by -<samp><span class="option">--enable-checking</span></samp>. To build the stage1 compiler with -different checking options use <samp><span class="option">--enable-stage1-checking</span></samp>. -The list of checking options is the same as for <samp><span class="option">--enable-checking</span></samp>. +<samp>--enable-checking</samp>. To build the stage1 compiler with +different checking options use <samp>--enable-stage1-checking</samp>. +The list of checking options is the same as for <samp>--enable-checking</samp>. If your system is too slow or too small to bootstrap a released compiler -with checking for stage1 enabled, you can use ‘<samp><span class="samp">--disable-stage1-checking</span></samp>’ +with checking for stage1 enabled, you can use ‘<samp>--disable-stage1-checking</samp>’ to disable checking for the stage1 compiler. - - <br><dt><code>--enable-coverage</code><dt><code>--enable-coverage=</code><var>level</var><dd>With this option, the compiler is built to collect self coverage +</p> +</dd> +<dt><code>--enable-coverage</code></dt> +<dt><code>--enable-coverage=<var>level</var></code></dt> +<dd><p>With this option, the compiler is built to collect self coverage information, every time it is run. This is for internal development purposes, and only works when the compiler is being built with gcc. The <var>level</var> argument controls whether the compiler is built optimized or -not, values are ‘<samp><span class="samp">opt</span></samp>’ and ‘<samp><span class="samp">noopt</span></samp>’. For coverage analysis you +not, values are ‘<samp>opt</samp>’ and ‘<samp>noopt</samp>’. For coverage analysis you want to disable optimization, for performance analysis you want to enable optimization. When coverage is enabled, the default level is without optimization. - - <br><dt><code>--enable-gather-detailed-mem-stats</code><dd>When this option is specified more detailed information on memory +</p> +</dd> +<dt><code>--enable-gather-detailed-mem-stats</code></dt> +<dd><p>When this option is specified more detailed information on memory allocation is gathered. This information is printed when using -<samp><span class="option">-fmem-report</span></samp>. - - <br><dt><code>--with-gc</code><dt><code>--with-gc=</code><var>choice</var><dd>With this option you can specify the garbage collector implementation -used during the compilation process. <var>choice</var> can be one of -‘<samp><span class="samp">page</span></samp>’ and ‘<samp><span class="samp">zone</span></samp>’, where ‘<samp><span class="samp">page</span></samp>’ is the default. - - <br><dt><code>--enable-nls</code><dt><code>--disable-nls</code><dd>The <samp><span class="option">--enable-nls</span></samp> option enables Native Language Support (NLS), +<samp>-fmem-report</samp>. +</p> +</dd> +<dt><code>--enable-nls</code></dt> +<dt><code>--disable-nls</code></dt> +<dd><p>The <samp>--enable-nls</samp> option enables Native Language Support (NLS), which lets GCC output diagnostics in languages other than American English. Native Language Support is enabled by default if not doing a -canadian cross build. The <samp><span class="option">--disable-nls</span></samp> option disables NLS. - - <br><dt><code>--with-included-gettext</code><dd>If NLS is enabled, the <samp><span class="option">--with-included-gettext</span></samp> option causes the build -procedure to prefer its copy of GNU <samp><span class="command">gettext</span></samp>. - - <br><dt><code>--with-catgets</code><dd>If NLS is enabled, and if the host lacks <code>gettext</code> but has the +canadian cross build. The <samp>--disable-nls</samp> option disables NLS. +</p> +</dd> +<dt><code>--with-included-gettext</code></dt> +<dd><p>If NLS is enabled, the <samp>--with-included-gettext</samp> option causes the build +procedure to prefer its copy of GNU <code>gettext</code>. +</p> +</dd> +<dt><code>--with-catgets</code></dt> +<dd><p>If NLS is enabled, and if the host lacks <code>gettext</code> but has the inferior <code>catgets</code> interface, the GCC build procedure normally -ignores <code>catgets</code> and instead uses GCC's copy of the GNU -<code>gettext</code> library. The <samp><span class="option">--with-catgets</span></samp> option causes the -build procedure to use the host's <code>catgets</code> in this situation. - - <br><dt><code>--with-libiconv-prefix=</code><var>dir</var><dd>Search for libiconv header files in <samp><var>dir</var><span class="file">/include</span></samp> and -libiconv library files in <samp><var>dir</var><span class="file">/lib</span></samp>. - - <br><dt><code>--enable-obsolete</code><dd>Enable configuration for an obsoleted system. If you attempt to +ignores <code>catgets</code> and instead uses GCC’s copy of the GNU +<code>gettext</code> library. The <samp>--with-catgets</samp> option causes the +build procedure to use the host’s <code>catgets</code> in this situation. +</p> +</dd> +<dt><code>--with-libiconv-prefix=<var>dir</var></code></dt> +<dd><p>Search for libiconv header files in <samp><var>dir</var>/include</samp> and +libiconv library files in <samp><var>dir</var>/lib</samp>. +</p> +</dd> +<dt><code>--enable-obsolete</code></dt> +<dd><p>Enable configuration for an obsoleted system. If you attempt to configure GCC for a system (build, host, or target) which has been obsoleted, and you do not specify this flag, configure will halt with an error message. - - <p>All support for systems which have been obsoleted in one release of GCC +</p> +<p>All support for systems which have been obsoleted in one release of GCC is removed entirely in the next major release, unless someone steps forward to maintain the port. - - <br><dt><code>--enable-decimal-float</code><dt><code>--enable-decimal-float=yes</code><dt><code>--enable-decimal-float=no</code><dt><code>--enable-decimal-float=bid</code><dt><code>--enable-decimal-float=dpd</code><dt><code>--disable-decimal-float</code><dd>Enable (or disable) support for the C decimal floating point extension +</p> +</dd> +<dt><code>--enable-decimal-float</code></dt> +<dt><code>--enable-decimal-float=yes</code></dt> +<dt><code>--enable-decimal-float=no</code></dt> +<dt><code>--enable-decimal-float=bid</code></dt> +<dt><code>--enable-decimal-float=dpd</code></dt> +<dt><code>--disable-decimal-float</code></dt> +<dd><p>Enable (or disable) support for the C decimal floating point extension that is in the IEEE 754-2008 standard. This is enabled by default only on PowerPC, i386, and x86_64 GNU/Linux systems. Other systems may also support it, but require the user to specifically enable it. You can optionally control which decimal floating point format is used (either -‘<samp><span class="samp">bid</span></samp>’ or ‘<samp><span class="samp">dpd</span></samp>’). The ‘<samp><span class="samp">bid</span></samp>’ (binary integer decimal) -format is default on i386 and x86_64 systems, and the ‘<samp><span class="samp">dpd</span></samp>’ +‘<samp>bid</samp>’ or ‘<samp>dpd</samp>’). The ‘<samp>bid</samp>’ (binary integer decimal) +format is default on i386 and x86_64 systems, and the ‘<samp>dpd</samp>’ (densely packed decimal) format is default on PowerPC systems. - - <br><dt><code>--enable-fixed-point</code><dt><code>--disable-fixed-point</code><dd>Enable (or disable) support for C fixed-point arithmetic. +</p> +</dd> +<dt><code>--enable-fixed-point</code></dt> +<dt><code>--disable-fixed-point</code></dt> +<dd><p>Enable (or disable) support for C fixed-point arithmetic. This option is enabled by default for some targets (such as MIPS) which have hardware-support for fixed-point operations. On other targets, you may enable this option manually. - - <br><dt><code>--with-long-double-128</code><dd>Specify if <code>long double</code> type should be 128-bit by default on selected +</p> +</dd> +<dt><code>--with-long-double-128</code></dt> +<dd><p>Specify if <code>long double</code> type should be 128-bit by default on selected GNU/Linux architectures. If using <code>--without-long-double-128</code>, -<code>long double</code> will be by default 64-bit, the same as <code>double</code> type. +<code>long double</code> will be by default 64-bit, the same as <code>double</code> type. When neither of these configure options are used, the default will be 128-bit <code>long double</code> when built against GNU C Library 2.4 and later, 64-bit <code>long double</code> otherwise. - - <br><dt><code>--with-gmp=</code><var>pathname</var><dt><code>--with-gmp-include=</code><var>pathname</var><dt><code>--with-gmp-lib=</code><var>pathname</var><dt><code>--with-mpfr=</code><var>pathname</var><dt><code>--with-mpfr-include=</code><var>pathname</var><dt><code>--with-mpfr-lib=</code><var>pathname</var><dt><code>--with-mpc=</code><var>pathname</var><dt><code>--with-mpc-include=</code><var>pathname</var><dt><code>--with-mpc-lib=</code><var>pathname</var><dd>If you want to build GCC but do not have the GMP library, the MPFR +</p> +</dd> +<dt><code>--with-gmp=<var>pathname</var></code></dt> +<dt><code>--with-gmp-include=<var>pathname</var></code></dt> +<dt><code>--with-gmp-lib=<var>pathname</var></code></dt> +<dt><code>--with-mpfr=<var>pathname</var></code></dt> +<dt><code>--with-mpfr-include=<var>pathname</var></code></dt> +<dt><code>--with-mpfr-lib=<var>pathname</var></code></dt> +<dt><code>--with-mpc=<var>pathname</var></code></dt> +<dt><code>--with-mpc-include=<var>pathname</var></code></dt> +<dt><code>--with-mpc-lib=<var>pathname</var></code></dt> +<dd><p>If you want to build GCC but do not have the GMP library, the MPFR library and/or the MPC library installed in a standard location and do not have their sources present in the GCC source tree then you can explicitly specify the directory where they are installed -(‘<samp><span class="samp">--with-gmp=</span><var>gmpinstalldir</var></samp>’, -‘<samp><span class="samp">--with-mpfr=</span><var>mpfrinstalldir</var></samp>’, -‘<samp><span class="samp">--with-mpc=</span><var>mpcinstalldir</var></samp>’). The -<samp><span class="option">--with-gmp=</span><var>gmpinstalldir</var></samp> option is shorthand for -<samp><span class="option">--with-gmp-lib=</span><var>gmpinstalldir</var><span class="option">/lib</span></samp> and -<samp><span class="option">--with-gmp-include=</span><var>gmpinstalldir</var><span class="option">/include</span></samp>. Likewise the -<samp><span class="option">--with-mpfr=</span><var>mpfrinstalldir</var></samp> option is shorthand for -<samp><span class="option">--with-mpfr-lib=</span><var>mpfrinstalldir</var><span class="option">/lib</span></samp> and -<samp><span class="option">--with-mpfr-include=</span><var>mpfrinstalldir</var><span class="option">/include</span></samp>, also the -<samp><span class="option">--with-mpc=</span><var>mpcinstalldir</var></samp> option is shorthand for -<samp><span class="option">--with-mpc-lib=</span><var>mpcinstalldir</var><span class="option">/lib</span></samp> and -<samp><span class="option">--with-mpc-include=</span><var>mpcinstalldir</var><span class="option">/include</span></samp>. If these +(‘<samp>--with-gmp=<var>gmpinstalldir</var></samp>’, +‘<samp>--with-mpfr=<var>mpfrinstalldir</var></samp>’, +‘<samp>--with-mpc=<var>mpcinstalldir</var></samp>’). The +<samp>--with-gmp=<var>gmpinstalldir</var></samp> option is shorthand for +<samp>--with-gmp-lib=<var>gmpinstalldir</var>/lib</samp> and +<samp>--with-gmp-include=<var>gmpinstalldir</var>/include</samp>. Likewise the +<samp>--with-mpfr=<var>mpfrinstalldir</var></samp> option is shorthand for +<samp>--with-mpfr-lib=<var>mpfrinstalldir</var>/lib</samp> and +<samp>--with-mpfr-include=<var>mpfrinstalldir</var>/include</samp>, also the +<samp>--with-mpc=<var>mpcinstalldir</var></samp> option is shorthand for +<samp>--with-mpc-lib=<var>mpcinstalldir</var>/lib</samp> and +<samp>--with-mpc-include=<var>mpcinstalldir</var>/include</samp>. If these shorthand assumptions are not correct, you can use the explicit include and lib options directly. You might also need to ensure the shared libraries can be found by the dynamic linker when building and using GCC, for example by setting the runtime shared library path -variable (<samp><span class="env">LD_LIBRARY_PATH</span></samp> on GNU/Linux and Solaris systems). - - <p>These flags are applicable to the host platform only. When building +variable (<code>LD_LIBRARY_PATH</code> on GNU/Linux and Solaris systems). +</p> +<p>These flags are applicable to the host platform only. When building a cross compiler, they will not be used to configure target libraries. - - <br><dt><code>--with-ppl=</code><var>pathname</var><dt><code>--with-ppl-include=</code><var>pathname</var><dt><code>--with-ppl-lib=</code><var>pathname</var><dt><code>--with-cloog=</code><var>pathname</var><dt><code>--with-cloog-include=</code><var>pathname</var><dt><code>--with-cloog-lib=</code><var>pathname</var><dd>If you do not have PPL (the Parma Polyhedra Library) and the CLooG +</p> +</dd> +<dt><code>--with-isl=<var>pathname</var></code></dt> +<dt><code>--with-isl-include=<var>pathname</var></code></dt> +<dt><code>--with-isl-lib=<var>pathname</var></code></dt> +<dt><code>--with-cloog=<var>pathname</var></code></dt> +<dt><code>--with-cloog-include=<var>pathname</var></code></dt> +<dt><code>--with-cloog-lib=<var>pathname</var></code></dt> +<dd><p>If you do not have ISL and the CLooG libraries installed in a standard location and you want to build GCC, you can explicitly specify the directory where they are installed -(‘<samp><span class="samp">--with-ppl=</span><var>pplinstalldir</var></samp>’, -‘<samp><span class="samp">--with-cloog=</span><var>clooginstalldir</var></samp>’). The -<samp><span class="option">--with-ppl=</span><var>pplinstalldir</var></samp> option is shorthand for -<samp><span class="option">--with-ppl-lib=</span><var>pplinstalldir</var><span class="option">/lib</span></samp> and -<samp><span class="option">--with-ppl-include=</span><var>pplinstalldir</var><span class="option">/include</span></samp>. Likewise the -<samp><span class="option">--with-cloog=</span><var>clooginstalldir</var></samp> option is shorthand for -<samp><span class="option">--with-cloog-lib=</span><var>clooginstalldir</var><span class="option">/lib</span></samp> and -<samp><span class="option">--with-cloog-include=</span><var>clooginstalldir</var><span class="option">/include</span></samp>. If these +(‘<samp>--with-isl=<var>islinstalldir</var></samp>’, +‘<samp>--with-cloog=<var>clooginstalldir</var></samp>’). The +<samp>--with-isl=<var>islinstalldir</var></samp> option is shorthand for +<samp>--with-isl-lib=<var>islinstalldir</var>/lib</samp> and +<samp>--with-isl-include=<var>islinstalldir</var>/include</samp>. Likewise the +<samp>--with-cloog=<var>clooginstalldir</var></samp> option is shorthand for +<samp>--with-cloog-lib=<var>clooginstalldir</var>/lib</samp> and +<samp>--with-cloog-include=<var>clooginstalldir</var>/include</samp>. If these shorthand assumptions are not correct, you can use the explicit include and lib options directly. - - <p>These flags are applicable to the host platform only. When building +</p> +<p>These flags are applicable to the host platform only. When building a cross compiler, they will not be used to configure target libraries. - - <br><dt><code>--with-host-libstdcxx=</code><var>linker-args</var><dd>If you are linking with a static copy of PPL, you can use this option +</p> +</dd> +<dt><code>--with-host-libstdcxx=<var>linker-args</var></code></dt> +<dd><p>If you are linking with a static copy of PPL, you can use this option to specify how the linker should find the standard C++ library used internally by PPL. Typical values of <var>linker-args</var> might be -‘<samp><span class="samp">-lstdc++</span></samp>’ or ‘<samp><span class="samp">-Wl,-Bstatic,-lstdc++,-Bdynamic -lm</span></samp>’. If you are +‘<samp>-lstdc++</samp>’ or ‘<samp>-Wl,-Bstatic,-lstdc++,-Bdynamic -lm</samp>’. If you are linking with a shared copy of PPL, you probably do not need this option; shared library dependencies will cause the linker to search for the standard C++ library automatically. - - <br><dt><code>--with-stage1-ldflags=</code><var>flags</var><dd>This option may be used to set linker flags to be used when linking +</p> +</dd> +<dt><code>--with-stage1-ldflags=<var>flags</var></code></dt> +<dd><p>This option may be used to set linker flags to be used when linking stage 1 of GCC. These are also used when linking GCC if configured with -<samp><span class="option">--disable-bootstrap</span></samp>. By default no special flags are used. - - <br><dt><code>--with-stage1-libs=</code><var>libs</var><dd>This option may be used to set libraries to be used when linking stage 1 +<samp>--disable-bootstrap</samp>. By default no special flags are used. +</p> +</dd> +<dt><code>--with-stage1-libs=<var>libs</var></code></dt> +<dd><p>This option may be used to set libraries to be used when linking stage 1 of GCC. These are also used when linking GCC if configured with -<samp><span class="option">--disable-bootstrap</span></samp>. The default is the argument to -<samp><span class="option">--with-host-libstdcxx</span></samp>, if specified. - - <br><dt><code>--with-boot-ldflags=</code><var>flags</var><dd>This option may be used to set linker flags to be used when linking +<samp>--disable-bootstrap</samp>. The default is the argument to +<samp>--with-host-libstdcxx</samp>, if specified. +</p> +</dd> +<dt><code>--with-boot-ldflags=<var>flags</var></code></dt> +<dd><p>This option may be used to set linker flags to be used when linking stage 2 and later when bootstrapping GCC. If neither –with-boot-libs nor –with-host-libstdcxx is set to a value, then the default is -‘<samp><span class="samp">-static-libstdc++ -static-libgcc</span></samp>’. - - <br><dt><code>--with-boot-libs=</code><var>libs</var><dd>This option may be used to set libraries to be used when linking stage 2 +‘<samp>-static-libstdc++ -static-libgcc</samp>’. +</p> +</dd> +<dt><code>--with-boot-libs=<var>libs</var></code></dt> +<dd><p>This option may be used to set libraries to be used when linking stage 2 and later when bootstrapping GCC. The default is the argument to -<samp><span class="option">--with-host-libstdcxx</span></samp>, if specified. - - <br><dt><code>--with-debug-prefix-map=</code><var>map</var><dd>Convert source directory names using <samp><span class="option">-fdebug-prefix-map</span></samp> when +<samp>--with-host-libstdcxx</samp>, if specified. +</p> +</dd> +<dt><code>--with-debug-prefix-map=<var>map</var></code></dt> +<dd><p>Convert source directory names using <samp>-fdebug-prefix-map</samp> when building runtime libraries. ‘<samp><var>map</var></samp>’ is a space-separated -list of maps of the form ‘<samp><var>old</var><span class="samp">=</span><var>new</var></samp>’. - - <br><dt><code>--enable-linker-build-id</code><dd>Tells GCC to pass <samp><span class="option">--build-id</span></samp> option to the linker for all final -links (links performed without the <samp><span class="option">-r</span></samp> or <samp><span class="option">--relocatable</span></samp> +list of maps of the form ‘<samp><var>old</var>=<var>new</var></samp>’. +</p> +</dd> +<dt><code>--enable-linker-build-id</code></dt> +<dd><p>Tells GCC to pass <samp>--build-id</samp> option to the linker for all final +links (links performed without the <samp>-r</samp> or <samp>--relocatable</samp> option), if the linker supports it. If you specify -<samp><span class="option">--enable-linker-build-id</span></samp>, but your linker does not -support <samp><span class="option">--build-id</span></samp> option, a warning is issued and the -<samp><span class="option">--enable-linker-build-id</span></samp> option is ignored. The default is off. - - <br><dt><code>--with-linker-hash-style=</code><var>choice</var><dd>Tells GCC to pass <samp><span class="option">--hash-style=</span><var>choice</var></samp> option to the +<samp>--enable-linker-build-id</samp>, but your linker does not +support <samp>--build-id</samp> option, a warning is issued and the +<samp>--enable-linker-build-id</samp> option is ignored. The default is off. +</p> +</dd> +<dt><code>--with-linker-hash-style=<var>choice</var></code></dt> +<dd><p>Tells GCC to pass <samp>--hash-style=<var>choice</var></samp> option to the linker for all final links. <var>choice</var> can be one of -‘<samp><span class="samp">sysv</span></samp>’, ‘<samp><span class="samp">gnu</span></samp>’, and ‘<samp><span class="samp">both</span></samp>’ where ‘<samp><span class="samp">sysv</span></samp>’ is the default. - - <br><dt><code>--enable-gnu-unique-object</code><dt><code>--disable-gnu-unique-object</code><dd>Tells GCC to use the gnu_unique_object relocation for C++ template +‘<samp>sysv</samp>’, ‘<samp>gnu</samp>’, and ‘<samp>both</samp>’ where ‘<samp>sysv</samp>’ is the default. +</p> +</dd> +<dt><code>--enable-gnu-unique-object</code></dt> +<dt><code>--disable-gnu-unique-object</code></dt> +<dd><p>Tells GCC to use the gnu_unique_object relocation for C++ template static data members and inline function local statics. Enabled by -default for a native toolchain with an assembler that accepts it and +default for a toolchain with an assembler that accepts it and GLIBC 2.11 or above, otherwise disabled. - - <br><dt><code>--enable-lto</code><dt><code>--disable-lto</code><dd>Enable support for link-time optimization (LTO). This is enabled by -default, and may be disabled using <samp><span class="option">--disable-lto</span></samp>. - - <br><dt><code>--with-plugin-ld=</code><var>pathname</var><dd>Enable an alternate linker to be used at link-time optimization (LTO) -link time when <samp><span class="option">-fuse-linker-plugin</span></samp> is enabled. +</p> +</dd> +<dt><code>--enable-lto</code></dt> +<dt><code>--disable-lto</code></dt> +<dd><p>Enable support for link-time optimization (LTO). This is enabled by +default, and may be disabled using <samp>--disable-lto</samp>. +</p> +</dd> +<dt><code>--with-plugin-ld=<var>pathname</var></code></dt> +<dd><p>Enable an alternate linker to be used at link-time optimization (LTO) +link time when <samp>-fuse-linker-plugin</samp> is enabled. This linker should have plugin support such as gold starting with -version 2.20 or GNU ld starting with version 2.21. -See <samp><span class="option">-fuse-linker-plugin</span></samp> for details. +version 2.20 or GNU ld starting with version 2.21. +See <samp>-fuse-linker-plugin</samp> for details. +</p> +</dd> +<dt><code>--enable-canonical-system-headers</code></dt> +<dt><code>--disable-canonical-system-headers</code></dt> +<dd><p>Enable system header path canonicalization for <samp>libcpp</samp>. This can +produce shorter header file paths in diagnostics and dependency output +files, but these changed header paths may conflict with some compilation +environments. Enabled by default, and may be disabled using +<samp>--disable-canonical-system-headers</samp>. +</p> +</dd> +<dt><code>--with-glibc-version=<var>major</var>.<var>minor</var></code></dt> +<dd><p>Tell GCC that when the GNU C Library (glibc) is used on the target it +will be version <var>major</var>.<var>minor</var> or later. Normally this can +be detected from the C library’s header files, but this option may be +needed when bootstrapping a cross toolchain without the header files +available for building the initial bootstrap compiler. +</p> +<p>If GCC is configured with some multilibs that use glibc and some that +do not, this option applies only to the multilibs that use glibc. +However, such configurations may not work well as not all the relevant +configuration in GCC is on a per-multilib basis. +</p></dd> </dl> -<h4 class="subheading"><a name="TOC3"></a>Cross-Compiler-Specific Options</h4> - +<a name="Cross_002dCompiler_002dSpecific-Options"></a> +<h4 class="subheading">Cross-Compiler-Specific Options</h4> <p>The following options only apply to building cross compilers. - - <dl> -<dt><code>--with-sysroot</code><dt><code>--with-sysroot=</code><var>dir</var><dd>Tells GCC to consider <var>dir</var> as the root of a tree that contains -(a subset of) the root filesystem of the target operating system. +</p> +<dl compact="compact"> +<dt><code>--with-sysroot</code></dt> +<dt><code>--with-sysroot=<var>dir</var></code></dt> +<dd><p>Tells GCC to consider <var>dir</var> as the root of a tree that contains +(a subset of) the root filesystem of the target operating system. Target system headers, libraries and run-time object files will be searched for in there. More specifically, this acts as if -<samp><span class="option">--sysroot=</span><var>dir</var></samp> was added to the default options of the built +<samp>--sysroot=<var>dir</var></samp> was added to the default options of the built compiler. The specified directory is not copied into the -install tree, unlike the options <samp><span class="option">--with-headers</span></samp> and -<samp><span class="option">--with-libs</span></samp> that this option obsoletes. The default value, -in case <samp><span class="option">--with-sysroot</span></samp> is not given an argument, is -<samp><span class="option">${gcc_tooldir}/sys-root</span></samp>. If the specified directory is a -subdirectory of <samp><span class="option">${exec_prefix}</span></samp>, then it will be found relative to +install tree, unlike the options <samp>--with-headers</samp> and +<samp>--with-libs</samp> that this option obsoletes. The default value, +in case <samp>--with-sysroot</samp> is not given an argument, is +<samp>${gcc_tooldir}/sys-root</samp>. If the specified directory is a +subdirectory of <samp>${exec_prefix}</samp>, then it will be found relative to the GCC binaries if the installation tree is moved. - - <p>This option affects the system root for the compiler used to build +</p> +<p>This option affects the system root for the compiler used to build target libraries (which runs on the build system) and the compiler newly installed with <code>make install</code>; it does not affect the compiler which is used to build GCC itself. - - <p>If you specify the <samp><span class="option">--with-native-system-header-dir=</span><var>dirname</var></samp> +</p> +<p>If you specify the <samp>--with-native-system-header-dir=<var>dirname</var></samp> option then the compiler will search that directory within <var>dirname</var> for -native system headers rather than the default <samp><span class="file">/usr/include</span></samp>. - - <br><dt><code>--with-build-sysroot</code><dt><code>--with-build-sysroot=</code><var>dir</var><dd>Tells GCC to consider <var>dir</var> as the system root (see -<samp><span class="option">--with-sysroot</span></samp>) while building target libraries, instead of -the directory specified with <samp><span class="option">--with-sysroot</span></samp>. This option is -only useful when you are already using <samp><span class="option">--with-sysroot</span></samp>. You -can use <samp><span class="option">--with-build-sysroot</span></samp> when you are configuring with -<samp><span class="option">--prefix</span></samp> set to a directory that is different from the one in +native system headers rather than the default <samp>/usr/include</samp>. +</p> +</dd> +<dt><code>--with-build-sysroot</code></dt> +<dt><code>--with-build-sysroot=<var>dir</var></code></dt> +<dd><p>Tells GCC to consider <var>dir</var> as the system root (see +<samp>--with-sysroot</samp>) while building target libraries, instead of +the directory specified with <samp>--with-sysroot</samp>. This option is +only useful when you are already using <samp>--with-sysroot</samp>. You +can use <samp>--with-build-sysroot</samp> when you are configuring with +<samp>--prefix</samp> set to a directory that is different from the one in which you are installing GCC and your target libraries. - - <p>This option affects the system root for the compiler used to build +</p> +<p>This option affects the system root for the compiler used to build target libraries (which runs on the build system); it does not affect the compiler which is used to build GCC itself. - - <p>If you specify the <samp><span class="option">--with-native-system-header-dir=</span><var>dirname</var></samp> +</p> +<p>If you specify the <samp>--with-native-system-header-dir=<var>dirname</var></samp> option then the compiler will search that directory within <var>dirname</var> for -native system headers rather than the default <samp><span class="file">/usr/include</span></samp>. - - <br><dt><code>--with-headers</code><dt><code>--with-headers=</code><var>dir</var><dd>Deprecated in favor of <samp><span class="option">--with-sysroot</span></samp>. -Specifies that target headers are available when building a cross compiler. +native system headers rather than the default <samp>/usr/include</samp>. +</p> +</dd> +<dt><code>--with-headers</code></dt> +<dt><code>--with-headers=<var>dir</var></code></dt> +<dd><p>Deprecated in favor of <samp>--with-sysroot</samp>. +Specifies that target headers are available when building a cross compiler. The <var>dir</var> argument specifies a directory which has the target include -files. These include files will be copied into the <samp><span class="file">gcc</span></samp> install -directory. <em>This option with the </em><var>dir</var><em> argument is required</em> when -building a cross compiler, if <samp><var>prefix</var><span class="file">/</span><var>target</var><span class="file">/sys-include</span></samp> -doesn't pre-exist. If <samp><var>prefix</var><span class="file">/</span><var>target</var><span class="file">/sys-include</span></samp> does -pre-exist, the <var>dir</var> argument may be omitted. <samp><span class="command">fixincludes</span></samp> +files. These include files will be copied into the <samp>gcc</samp> install +directory. <em>This option with the <var>dir</var> argument is required</em> when +building a cross compiler, if <samp><var>prefix</var>/<var>target</var>/sys-include</samp> +doesn’t pre-exist. If <samp><var>prefix</var>/<var>target</var>/sys-include</samp> does +pre-exist, the <var>dir</var> argument may be omitted. <code>fixincludes</code> will be run on these files to make them compatible with GCC. - - <br><dt><code>--without-headers</code><dd>Tells GCC not use any target headers from a libc when building a cross +</p> +</dd> +<dt><code>--without-headers</code></dt> +<dd><p>Tells GCC not use any target headers from a libc when building a cross compiler. When crossing to GNU/Linux, you need the headers so GCC can build the exception handling for libgcc. - - <br><dt><code>--with-libs</code><dt><code>--with-libs="</code><var>dir1</var> <var>dir2</var><code> ... </code><var>dirN</var><code>"</code><dd>Deprecated in favor of <samp><span class="option">--with-sysroot</span></samp>. +</p> +</dd> +<dt><code>--with-libs</code></dt> +<dt><code>--with-libs="<var>dir1</var> <var>dir2</var> … <var>dirN</var>"</code></dt> +<dd><p>Deprecated in favor of <samp>--with-sysroot</samp>. Specifies a list of directories which contain the target runtime -libraries. These libraries will be copied into the <samp><span class="file">gcc</span></samp> install +libraries. These libraries will be copied into the <samp>gcc</samp> install directory. If the directory list is omitted, this option has no effect. - - <br><dt><code>--with-newlib</code><dd>Specifies that ‘<samp><span class="samp">newlib</span></samp>’ is +</p> +</dd> +<dt><code>--with-newlib</code></dt> +<dd><p>Specifies that ‘<samp>newlib</samp>’ is being used as the target C library. This causes <code>__eprintf</code> to be -omitted from <samp><span class="file">libgcc.a</span></samp> on the assumption that it will be provided by -‘<samp><span class="samp">newlib</span></samp>’. - - <br><dt><code>--with-avrlibc</code><dd>Specifies that ‘<samp><span class="samp">AVR-Libc</span></samp>’ is +omitted from <samp>libgcc.a</samp> on the assumption that it will be provided by +‘<samp>newlib</samp>’. +</p> +</dd> +<dt><code>--with-avrlibc</code></dt> +<dd><p>Specifies that ‘<samp>AVR-Libc</samp>’ is being used as the target C library. This causes float support -functions like <code>__addsf3</code> to be omitted from <samp><span class="file">libgcc.a</span></samp> on -the assumption that it will be provided by <samp><span class="file">libm.a</span></samp>. For more -technical details, cf. <a href="http://gcc.gnu.org/PR54461">PR54461</a>. +functions like <code>__addsf3</code> to be omitted from <samp>libgcc.a</samp> on +the assumption that it will be provided by <samp>libm.a</samp>. For more +technical details, cf. <a href="http://gcc.gnu.org/PR54461">PR54461</a>. This option is only supported for the AVR target. It is not supported for RTEMS configurations, which currently use newlib. The option is supported since version 4.7.2 and is the default in 4.8.0 and newer. - - <br><dt><code>--with-build-time-tools=</code><var>dir</var><dd>Specifies where to find the set of target tools (assembler, linker, etc.) +</p> +</dd> +<dt><code>--with-nds32-lib=<var>library</var></code></dt> +<dd><p>Specifies that <var>library</var> setting is used for building <samp>libgcc.a</samp>. +Currently, the valid <var>library</var> is ‘<samp>newlib</samp>’ or ‘<samp>mculib</samp>’. +This option is only supported for the NDS32 target. +</p> +</dd> +<dt><code>--with-build-time-tools=<var>dir</var></code></dt> +<dd><p>Specifies where to find the set of target tools (assembler, linker, etc.) that will be used while building GCC itself. This option can be useful if the directory layouts are different between the system you are building GCC on, and the system where you will deploy it. - - <p>For example, on an ‘<samp><span class="samp">ia64-hp-hpux</span></samp>’ system, you may have the GNU -assembler and linker in <samp><span class="file">/usr/bin</span></samp>, and the native tools in a +</p> +<p>For example, on an ‘<samp>ia64-hp-hpux</samp>’ system, you may have the GNU +assembler and linker in <samp>/usr/bin</samp>, and the native tools in a different path, and build a toolchain that expects to find the -native tools in <samp><span class="file">/usr/bin</span></samp>. - - <p>When you use this option, you should ensure that <var>dir</var> includes -<samp><span class="command">ar</span></samp>, <samp><span class="command">as</span></samp>, <samp><span class="command">ld</span></samp>, <samp><span class="command">nm</span></samp>, -<samp><span class="command">ranlib</span></samp> and <samp><span class="command">strip</span></samp> if necessary, and possibly -<samp><span class="command">objdump</span></samp>. Otherwise, GCC may use an inconsistent set of -tools. +native tools in <samp>/usr/bin</samp>. +</p> +<p>When you use this option, you should ensure that <var>dir</var> includes +<code>ar</code>, <code>as</code>, <code>ld</code>, <code>nm</code>, +<code>ranlib</code> and <code>strip</code> if necessary, and possibly +<code>objdump</code>. Otherwise, GCC may use an inconsistent set of +tools. +</p></dd> </dl> -<h4 class="subheading"><a name="TOC4"></a>Java-Specific Options</h4> +<a name="Java_002dSpecific-Options"></a> +<h4 class="subheading">Java-Specific Options</h4> <p>The following option applies to the build of the Java front end. - - <dl> -<dt><code>--disable-libgcj</code><dd>Specify that the run-time libraries +</p> +<dl compact="compact"> +<dt><code>--disable-libgcj</code></dt> +<dd><p>Specify that the run-time libraries used by GCJ should not be built. This is useful in case you intend -to use GCJ with some other run-time, or you're going to install it +to use GCJ with some other run-time, or you’re going to install it separately, or it just happens not to build on your particular machine. In general, if the Java front end is enabled, the GCJ -libraries will be enabled too, unless they're known to not work on -the target platform. If GCJ is enabled but ‘<samp><span class="samp">libgcj</span></samp>’ isn't built, you +libraries will be enabled too, unless they’re known to not work on +the target platform. If GCJ is enabled but ‘<samp>libgcj</samp>’ isn’t built, you may need to port it; in this case, before modifying the top-level -<samp><span class="file">configure.in</span></samp> so that ‘<samp><span class="samp">libgcj</span></samp>’ is enabled by default on this platform, -you may use <samp><span class="option">--enable-libgcj</span></samp> to override the default. - - </dl> - - <p>The following options apply to building ‘<samp><span class="samp">libgcj</span></samp>’. - -<h5 class="subsubheading"><a name="TOC5"></a>General Options</h5> +<samp>configure.in</samp> so that ‘<samp>libgcj</samp>’ is enabled by default on this platform, +you may use <samp>--enable-libgcj</samp> to override the default. +</p> +</dd> +</dl> - <dl> -<dt><code>--enable-java-maintainer-mode</code><dd>By default the ‘<samp><span class="samp">libjava</span></samp>’ build will not attempt to compile the -<samp><span class="file">.java</span></samp> source files to <samp><span class="file">.class</span></samp>. Instead, it will use the -<samp><span class="file">.class</span></samp> files from the source tree. If you use this option you -must have executables named <samp><span class="command">ecj1</span></samp> and <samp><span class="command">gjavah</span></samp> in your path +<p>The following options apply to building ‘<samp>libgcj</samp>’. +</p> +<a name="General-Options"></a> +<h4 class="subsubheading">General Options</h4> + +<dl compact="compact"> +<dt><code>--enable-java-maintainer-mode</code></dt> +<dd><p>By default the ‘<samp>libjava</samp>’ build will not attempt to compile the +<samp>.java</samp> source files to <samp>.class</samp>. Instead, it will use the +<samp>.class</samp> files from the source tree. If you use this option you +must have executables named <code>ecj1</code> and <code>gjavah</code> in your path for use by the build. You must use this option if you intend to -modify any <samp><span class="file">.java</span></samp> files in <samp><span class="file">libjava</span></samp>. - - <br><dt><code>--with-java-home=</code><var>dirname</var><dd>This ‘<samp><span class="samp">libjava</span></samp>’ option overrides the default value of the -‘<samp><span class="samp">java.home</span></samp>’ system property. It is also used to set -‘<samp><span class="samp">sun.boot.class.path</span></samp>’ to <samp><var>dirname</var><span class="file">/lib/rt.jar</span></samp>. By -default ‘<samp><span class="samp">java.home</span></samp>’ is set to <samp><var>prefix</var></samp> and -‘<samp><span class="samp">sun.boot.class.path</span></samp>’ to -<samp><var>datadir</var><span class="file">/java/libgcj-</span><var>version</var><span class="file">.jar</span></samp>. - - <br><dt><code>--with-ecj-jar=</code><var>filename</var><dd>This option can be used to specify the location of an external jar +modify any <samp>.java</samp> files in <samp>libjava</samp>. +</p> +</dd> +<dt><code>--with-java-home=<var>dirname</var></code></dt> +<dd><p>This ‘<samp>libjava</samp>’ option overrides the default value of the +‘<samp>java.home</samp>’ system property. It is also used to set +‘<samp>sun.boot.class.path</samp>’ to <samp><var>dirname</var>/lib/rt.jar</samp>. By +default ‘<samp>java.home</samp>’ is set to <samp><var>prefix</var></samp> and +‘<samp>sun.boot.class.path</samp>’ to +<samp><var>datadir</var>/java/libgcj-<var>version</var>.jar</samp>. +</p> +</dd> +<dt><code>--with-ecj-jar=<var>filename</var></code></dt> +<dd><p>This option can be used to specify the location of an external jar file containing the Eclipse Java compiler. A specially modified -version of this compiler is used by <samp><span class="command">gcj</span></samp> to parse -<samp><span class="file">.java</span></samp> source files. If this option is given, the -‘<samp><span class="samp">libjava</span></samp>’ build will create and install an <samp><span class="file">ecj1</span></samp> executable +version of this compiler is used by <code>gcj</code> to parse +<samp>.java</samp> source files. If this option is given, the +‘<samp>libjava</samp>’ build will create and install an <samp>ecj1</samp> executable which uses this jar file at runtime. - - <p>If this option is not given, but an <samp><span class="file">ecj.jar</span></samp> file is found in -the topmost source tree at configure time, then the ‘<samp><span class="samp">libgcj</span></samp>’ -build will create and install <samp><span class="file">ecj1</span></samp>, and will also install the -discovered <samp><span class="file">ecj.jar</span></samp> into a suitable place in the install tree. - - <p>If <samp><span class="file">ecj1</span></samp> is not installed, then the user will have to supply one -on his path in order for <samp><span class="command">gcj</span></samp> to properly parse <samp><span class="file">.java</span></samp> +</p> +<p>If this option is not given, but an <samp>ecj.jar</samp> file is found in +the topmost source tree at configure time, then the ‘<samp>libgcj</samp>’ +build will create and install <samp>ecj1</samp>, and will also install the +discovered <samp>ecj.jar</samp> into a suitable place in the install tree. +</p> +<p>If <samp>ecj1</samp> is not installed, then the user will have to supply one +on his path in order for <code>gcj</code> to properly parse <samp>.java</samp> source files. A suitable jar is available from <a href="ftp://sourceware.org/pub/java/">ftp://sourceware.org/pub/java/</a>. - - <br><dt><code>--disable-getenv-properties</code><dd>Don't set system properties from <samp><span class="env">GCJ_PROPERTIES</span></samp>. - - <br><dt><code>--enable-hash-synchronization</code><dd>Use a global hash table for monitor locks. Ordinarily, -‘<samp><span class="samp">libgcj</span></samp>’'s ‘<samp><span class="samp">configure</span></samp>’ script automatically makes +</p> +</dd> +<dt><code>--disable-getenv-properties</code></dt> +<dd><p>Don’t set system properties from <code>GCJ_PROPERTIES</code>. +</p> +</dd> +<dt><code>--enable-hash-synchronization</code></dt> +<dd><p>Use a global hash table for monitor locks. Ordinarily, +‘<samp>libgcj</samp>’’s ‘<samp>configure</samp>’ script automatically makes the correct choice for this option for your platform. Only use this if you know you need the library to be configured differently. - - <br><dt><code>--enable-interpreter</code><dd>Enable the Java interpreter. The interpreter is automatically +</p> +</dd> +<dt><code>--enable-interpreter</code></dt> +<dd><p>Enable the Java interpreter. The interpreter is automatically enabled by default on all platforms that support it. This option is really only useful if you want to disable the interpreter -(using <samp><span class="option">--disable-interpreter</span></samp>). - - <br><dt><code>--disable-java-net</code><dd>Disable java.net. This disables the native part of java.net only, +(using <samp>--disable-interpreter</samp>). +</p> +</dd> +<dt><code>--disable-java-net</code></dt> +<dd><p>Disable java.net. This disables the native part of java.net only, using non-functional stubs for native method implementations. - - <br><dt><code>--disable-jvmpi</code><dd>Disable JVMPI support. - - <br><dt><code>--disable-libgcj-bc</code><dd>Disable BC ABI compilation of certain parts of libgcj. By default, -some portions of libgcj are compiled with <samp><span class="option">-findirect-dispatch</span></samp> -and <samp><span class="option">-fno-indirect-classes</span></samp>, allowing them to be overridden at +</p> +</dd> +<dt><code>--disable-jvmpi</code></dt> +<dd><p>Disable JVMPI support. +</p> +</dd> +<dt><code>--disable-libgcj-bc</code></dt> +<dd><p>Disable BC ABI compilation of certain parts of libgcj. By default, +some portions of libgcj are compiled with <samp>-findirect-dispatch</samp> +and <samp>-fno-indirect-classes</samp>, allowing them to be overridden at run-time. - - <p>If <samp><span class="option">--disable-libgcj-bc</span></samp> is specified, libgcj is built without +</p> +<p>If <samp>--disable-libgcj-bc</samp> is specified, libgcj is built without these options. This allows the compile-time linker to resolve dependencies when statically linking to libgcj. However it makes it impossible to override the affected portions of libgcj at run-time. - - <br><dt><code>--enable-reduced-reflection</code><dd>Build most of libgcj with <samp><span class="option">-freduced-reflection</span></samp>. This reduces +</p> +</dd> +<dt><code>--enable-reduced-reflection</code></dt> +<dd><p>Build most of libgcj with <samp>-freduced-reflection</samp>. This reduces the size of libgcj at the expense of not being able to do accurate reflection on the classes it contains. This option is safe if you know that code using libgcj will never use reflection on the standard runtime classes in libgcj (including using serialization, RMI or CORBA). - - <br><dt><code>--with-ecos</code><dd>Enable runtime eCos target support. - - <br><dt><code>--without-libffi</code><dd>Don't use ‘<samp><span class="samp">libffi</span></samp>’. This will disable the interpreter and JNI -support as well, as these require ‘<samp><span class="samp">libffi</span></samp>’ to work. - - <br><dt><code>--enable-libgcj-debug</code><dd>Enable runtime debugging code. - - <br><dt><code>--enable-libgcj-multifile</code><dd>If specified, causes all <samp><span class="file">.java</span></samp> source files to be -compiled into <samp><span class="file">.class</span></samp> files in one invocation of -‘<samp><span class="samp">gcj</span></samp>’. This can speed up build time, but is more +</p> +</dd> +<dt><code>--with-ecos</code></dt> +<dd><p>Enable runtime eCos target support. +</p> +</dd> +<dt><code>--without-libffi</code></dt> +<dd><p>Don’t use ‘<samp>libffi</samp>’. This will disable the interpreter and JNI +support as well, as these require ‘<samp>libffi</samp>’ to work. +</p> +</dd> +<dt><code>--enable-libgcj-debug</code></dt> +<dd><p>Enable runtime debugging code. +</p> +</dd> +<dt><code>--enable-libgcj-multifile</code></dt> +<dd><p>If specified, causes all <samp>.java</samp> source files to be +compiled into <samp>.class</samp> files in one invocation of +‘<samp>gcj</samp>’. This can speed up build time, but is more resource-intensive. If this option is unspecified or -disabled, ‘<samp><span class="samp">gcj</span></samp>’ is invoked once for each <samp><span class="file">.java</span></samp> -file to compile into a <samp><span class="file">.class</span></samp> file. - - <br><dt><code>--with-libiconv-prefix=DIR</code><dd>Search for libiconv in <samp><span class="file">DIR/include</span></samp> and <samp><span class="file">DIR/lib</span></samp>. - - <br><dt><code>--enable-sjlj-exceptions</code><dd>Force use of the <code>setjmp</code>/<code>longjmp</code>-based scheme for exceptions. -‘<samp><span class="samp">configure</span></samp>’ ordinarily picks the correct value based on the platform. +disabled, ‘<samp>gcj</samp>’ is invoked once for each <samp>.java</samp> +file to compile into a <samp>.class</samp> file. +</p> +</dd> +<dt><code>--with-libiconv-prefix=DIR</code></dt> +<dd><p>Search for libiconv in <samp>DIR/include</samp> and <samp>DIR/lib</samp>. +</p> +</dd> +<dt><code>--enable-sjlj-exceptions</code></dt> +<dd><p>Force use of the <code>setjmp</code>/<code>longjmp</code>-based scheme for exceptions. +‘<samp>configure</samp>’ ordinarily picks the correct value based on the platform. Only use this option if you are sure you need a different setting. - - <br><dt><code>--with-system-zlib</code><dd>Use installed ‘<samp><span class="samp">zlib</span></samp>’ rather than that included with GCC. - - <br><dt><code>--with-win32-nlsapi=ansi, unicows or unicode</code><dd>Indicates how MinGW ‘<samp><span class="samp">libgcj</span></samp>’ translates between UNICODE +</p> +</dd> +<dt><code>--with-system-zlib</code></dt> +<dd><p>Use installed ‘<samp>zlib</samp>’ rather than that included with GCC. +</p> +</dd> +<dt><code>--with-win32-nlsapi=ansi, unicows or unicode</code></dt> +<dd><p>Indicates how MinGW ‘<samp>libgcj</samp>’ translates between UNICODE characters and the Win32 API. - - <br><dt><code>--enable-java-home</code><dd>If enabled, this creates a JPackage compatible SDK environment during install. +</p> +</dd> +<dt><code>--enable-java-home</code></dt> +<dd><p>If enabled, this creates a JPackage compatible SDK environment during install. Note that if –enable-java-home is used, –with-arch-directory=ARCH must also be specified. - - <br><dt><code>--with-arch-directory=ARCH</code><dd>Specifies the name to use for the <samp><span class="file">jre/lib/ARCH</span></samp> directory in the SDK +</p> +</dd> +<dt><code>--with-arch-directory=ARCH</code></dt> +<dd><p>Specifies the name to use for the <samp>jre/lib/ARCH</samp> directory in the SDK environment created when –enable-java-home is passed. Typical names for this directory include i386, amd64, ia64, etc. - - <br><dt><code>--with-os-directory=DIR</code><dd>Specifies the OS directory for the SDK include directory. This is set to auto -detect, and is typically 'linux'. - - <br><dt><code>--with-origin-name=NAME</code><dd>Specifies the JPackage origin name. This defaults to the 'gcj' in +</p> +</dd> +<dt><code>--with-os-directory=DIR</code></dt> +<dd><p>Specifies the OS directory for the SDK include directory. This is set to auto +detect, and is typically ’linux’. +</p> +</dd> +<dt><code>--with-origin-name=NAME</code></dt> +<dd><p>Specifies the JPackage origin name. This defaults to the ’gcj’ in java-1.5.0-gcj. - - <br><dt><code>--with-arch-suffix=SUFFIX</code><dd>Specifies the suffix for the sdk directory. Defaults to the empty string. -Examples include '.x86_64' in 'java-1.5.0-gcj-1.5.0.0.x86_64'. - - <br><dt><code>--with-jvm-root-dir=DIR</code><dd>Specifies where to install the SDK. Default is $(prefix)/lib/jvm. - - <br><dt><code>--with-jvm-jar-dir=DIR</code><dd>Specifies where to install jars. Default is $(prefix)/lib/jvm-exports. - - <br><dt><code>--with-python-dir=DIR</code><dd>Specifies where to install the Python modules used for aot-compile. DIR should +</p> +</dd> +<dt><code>--with-arch-suffix=SUFFIX</code></dt> +<dd><p>Specifies the suffix for the sdk directory. Defaults to the empty string. +Examples include ’.x86_64’ in ’java-1.5.0-gcj-1.5.0.0.x86_64’. +</p> +</dd> +<dt><code>--with-jvm-root-dir=DIR</code></dt> +<dd><p>Specifies where to install the SDK. Default is $(prefix)/lib/jvm. +</p> +</dd> +<dt><code>--with-jvm-jar-dir=DIR</code></dt> +<dd><p>Specifies where to install jars. Default is $(prefix)/lib/jvm-exports. +</p> +</dd> +<dt><code>--with-python-dir=DIR</code></dt> +<dd><p>Specifies where to install the Python modules used for aot-compile. DIR should not include the prefix used in installation. For example, if the Python modules are to be installed in /usr/lib/python2.5/site-packages, then –with-python-dir=/lib/python2.5/site-packages should be passed. If this is not specified, then the Python modules are installed in $(prefix)/share/python. - - <br><dt><code>--enable-aot-compile-rpm</code><dd>Adds aot-compile-rpm to the list of installed scripts. - - <br><dt><code>--enable-browser-plugin</code><dd>Build the gcjwebplugin web browser plugin. - - <br><dt><code>--enable-static-libjava</code><dd>Build static libraries in libjava. The default is to only build shared +</p> +</dd> +<dt><code>--enable-aot-compile-rpm</code></dt> +<dd><p>Adds aot-compile-rpm to the list of installed scripts. +</p> +</dd> +<dt><code>--enable-browser-plugin</code></dt> +<dd><p>Build the gcjwebplugin web browser plugin. +</p> +</dd> +<dt><code>--enable-static-libjava</code></dt> +<dd><p>Build static libraries in libjava. The default is to only build shared libraries. - - <dl> -<dt><code>ansi</code><dd>Use the single-byte <code>char</code> and the Win32 A functions natively, +</p> +<dl compact="compact"> +<dt><code>ansi</code></dt> +<dd><p>Use the single-byte <code>char</code> and the Win32 A functions natively, translating to and from UNICODE when using these functions. If unspecified, this is the default. - - <br><dt><code>unicows</code><dd>Use the <code>WCHAR</code> and Win32 W functions natively. Adds -<code>-lunicows</code> to <samp><span class="file">libgcj.spec</span></samp> to link with ‘<samp><span class="samp">libunicows</span></samp>’. -<samp><span class="file">unicows.dll</span></samp> needs to be deployed on Microsoft Windows 9X machines -running built executables. <samp><span class="file">libunicows.a</span></samp>, an open-source -import library around Microsoft's <code>unicows.dll</code>, is obtained from +</p> +</dd> +<dt><code>unicows</code></dt> +<dd><p>Use the <code>WCHAR</code> and Win32 W functions natively. Adds +<code>-lunicows</code> to <samp>libgcj.spec</samp> to link with ‘<samp>libunicows</samp>’. +<samp>unicows.dll</samp> needs to be deployed on Microsoft Windows 9X machines +running built executables. <samp>libunicows.a</samp>, an open-source +import library around Microsoft’s <code>unicows.dll</code>, is obtained from <a href="http://libunicows.sourceforge.net/">http://libunicows.sourceforge.net/</a>, which also gives details -on getting <samp><span class="file">unicows.dll</span></samp> from Microsoft. - - <br><dt><code>unicode</code><dd>Use the <code>WCHAR</code> and Win32 W functions natively. Does <em>not</em> -add <code>-lunicows</code> to <samp><span class="file">libgcj.spec</span></samp>. The built executables will -only run on Microsoft Windows NT and above. +on getting <samp>unicows.dll</samp> from Microsoft. +</p> +</dd> +<dt><code>unicode</code></dt> +<dd><p>Use the <code>WCHAR</code> and Win32 W functions natively. Does <em>not</em> +add <code>-lunicows</code> to <samp>libgcj.spec</samp>. The built executables will +only run on Microsoft Windows NT and above. +</p></dd> +</dl> +</dd> </dl> - </dl> - -<h5 class="subsubheading"><a name="TOC6"></a>AWT-Specific Options</h5> - - <dl> -<dt><code>--with-x</code><dd>Use the X Window System. - - <br><dt><code>--enable-java-awt=PEER(S)</code><dd>Specifies the AWT peer library or libraries to build alongside -‘<samp><span class="samp">libgcj</span></samp>’. If this option is unspecified or disabled, AWT -will be non-functional. Current valid values are <samp><span class="option">gtk</span></samp> and -<samp><span class="option">xlib</span></samp>. Multiple libraries should be separated by a -comma (i.e. <samp><span class="option">--enable-java-awt=gtk,xlib</span></samp>). - - <br><dt><code>--enable-gtk-cairo</code><dd>Build the cairo Graphics2D implementation on GTK. - - <br><dt><code>--enable-java-gc=TYPE</code><dd>Choose garbage collector. Defaults to <samp><span class="option">boehm</span></samp> if unspecified. - - <br><dt><code>--disable-gtktest</code><dd>Do not try to compile and run a test GTK+ program. - <br><dt><code>--disable-glibtest</code><dd>Do not try to compile and run a test GLIB program. +<a name="AWT_002dSpecific-Options"></a> +<h4 class="subsubheading">AWT-Specific Options</h4> + +<dl compact="compact"> +<dt><code>--with-x</code></dt> +<dd><p>Use the X Window System. +</p> +</dd> +<dt><code>--enable-java-awt=PEER(S)</code></dt> +<dd><p>Specifies the AWT peer library or libraries to build alongside +‘<samp>libgcj</samp>’. If this option is unspecified or disabled, AWT +will be non-functional. Current valid values are <samp>gtk</samp> and +<samp>xlib</samp>. Multiple libraries should be separated by a +comma (i.e. <samp>--enable-java-awt=gtk,xlib</samp>). +</p> +</dd> +<dt><code>--enable-gtk-cairo</code></dt> +<dd><p>Build the cairo Graphics2D implementation on GTK. +</p> +</dd> +<dt><code>--enable-java-gc=TYPE</code></dt> +<dd><p>Choose garbage collector. Defaults to <samp>boehm</samp> if unspecified. +</p> +</dd> +<dt><code>--disable-gtktest</code></dt> +<dd><p>Do not try to compile and run a test GTK+ program. +</p> +</dd> +<dt><code>--disable-glibtest</code></dt> +<dd><p>Do not try to compile and run a test GLIB program. +</p> +</dd> +<dt><code>--with-libart-prefix=PFX</code></dt> +<dd><p>Prefix where libart is installed (optional). +</p> +</dd> +<dt><code>--with-libart-exec-prefix=PFX</code></dt> +<dd><p>Exec prefix where libart is installed (optional). +</p> +</dd> +<dt><code>--disable-libarttest</code></dt> +<dd><p>Do not try to compile and run a test libart program. +</p> +</dd> +</dl> - <br><dt><code>--with-libart-prefix=PFX</code><dd>Prefix where libart is installed (optional). +<a name="Overriding-configure-test-results"></a> +<h4 class="subsubheading">Overriding <code>configure</code> test results</h4> - <br><dt><code>--with-libart-exec-prefix=PFX</code><dd>Exec prefix where libart is installed (optional). +<p>Sometimes, it might be necessary to override the result of some +<code>configure</code> test, for example in order to ease porting to a new +system or work around a bug in a test. The toplevel <code>configure</code> +script provides three variables for this: +</p> +<dl compact="compact"> +<dt><code>build_configargs</code></dt> +<dd><a name="index-build_005fconfigargs"></a> +<p>The contents of this variable is passed to all build <code>configure</code> +scripts. +</p> +</dd> +<dt><code>host_configargs</code></dt> +<dd><a name="index-host_005fconfigargs"></a> +<p>The contents of this variable is passed to all host <code>configure</code> +scripts. +</p> +</dd> +<dt><code>target_configargs</code></dt> +<dd><a name="index-target_005fconfigargs"></a> +<p>The contents of this variable is passed to all target <code>configure</code> +scripts. +</p> +</dd> +</dl> - <br><dt><code>--disable-libarttest</code><dd>Do not try to compile and run a test libart program. +<p>In order to avoid shell and <code>make</code> quoting issues for complex +overrides, you can pass a setting for <code>CONFIG_SITE</code> and set +variables in the site file. +</p> +<hr /> +<p><p><a href="./index.html">Return to the GCC Installation page</a> +</p> -</dl> -<h5 class="subsubheading"><a name="TOC7"></a>Overriding <samp><span class="command">configure</span></samp> test results</h5> -<p>Sometimes, it might be necessary to override the result of some -<samp><span class="command">configure</span></samp> test, for example in order to ease porting to a new -system or work around a bug in a test. The toplevel <samp><span class="command">configure</span></samp> -script provides three variables for this: - <dl> -<dt><code>build_configargs</code><dd><a name="index-g_t_0040code_007bbuild_005fconfigargs_007d-3"></a>The contents of this variable is passed to all build <samp><span class="command">configure</span></samp> -scripts. - <br><dt><code>host_configargs</code><dd><a name="index-g_t_0040code_007bhost_005fconfigargs_007d-4"></a>The contents of this variable is passed to all host <samp><span class="command">configure</span></samp> -scripts. - <br><dt><code>target_configargs</code><dd><a name="index-g_t_0040code_007btarget_005fconfigargs_007d-5"></a>The contents of this variable is passed to all target <samp><span class="command">configure</span></samp> -scripts. - </dl> - <p>In order to avoid shell and <samp><span class="command">make</span></samp> quoting issues for complex -overrides, you can pass a setting for <samp><span class="env">CONFIG_SITE</span></samp> and set -variables in the site file. - <p><hr /> -<p><a href="./index.html">Return to the GCC Installation page</a> -<!-- ***Building**************************************************************** --> -<!-- ***Testing***************************************************************** --> -<!-- ***Final install*********************************************************** --> -<!-- ***Binaries**************************************************************** --> -<!-- ***Specific**************************************************************** --> -<!-- ***Old documentation****************************************************** --> -<!-- ***GFDL******************************************************************** --> -<!-- *************************************************************************** --> -<!-- Part 6 The End of the Document --> -</body></html> +</body> +</html> diff --git a/INSTALL/download.html b/INSTALL/download.html index cbd0cffbca..40847edff1 100644 --- a/INSTALL/download.html +++ b/INSTALL/download.html @@ -1,97 +1,132 @@ -<html lang="en"> -<head> -<title>Downloading GCC</title> -<meta http-equiv="Content-Type" content="text/html"> -<meta name="description" content="Downloading GCC"> -<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, 1989, 1992, 1993, 1994, 1995, 1996, 1997, -1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, -2010 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-2014 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">Downloading GCC</h1> -<a name="index-Downloading-GCC-1"></a><a name="index-Downloading-the-Source-2"></a> -GCC is distributed via <a href="http://gcc.gnu.org/svn.html">SVN</a> and FTP -tarballs compressed with <samp><span class="command">gzip</span></samp> or -<samp><span class="command">bzip2</span></samp>. It is possible to download a full distribution or specific -components. - - <p>Please refer to the <a href="http://gcc.gnu.org/releases.html">releases web page</a> -for information on how to obtain GCC. - <p>The full distribution includes the C, C++, Objective-C, Fortran, Java, -and Ada (in the case of GCC 3.1 and later) compilers. The full -distribution also includes runtime libraries for C++, Objective-C, -Fortran, and Java. In GCC 3.0 and later versions, the GNU compiler -testsuites are also included in the full distribution. +<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000"> +<h1 class="settitle" align="center">Installing GCC</h1> + + + + + + + + + + - <p>If you choose to download specific components, you must download the core -GCC distribution plus any language specific distributions you wish to -use. The core distribution includes the C language front end as well as the -shared components. Each language has a tarball which includes the language -front end as well as the language runtime (when appropriate). - <p>Unpack the core distribution as well as any language specific -distributions in the same directory. - <p>If you also intend to build binutils (either to upgrade an existing + + + + + +<a name="index-Downloading-GCC"></a> +<a name="index-Downloading-the-Source"></a> + +<p>GCC is distributed via <a href="http://gcc.gnu.org/svn.html">SVN</a> and FTP +tarballs compressed with <code>gzip</code> or +<code>bzip2</code>. +</p> +<p>Please refer to the <a href="http://gcc.gnu.org/releases.html">releases web page</a> +for information on how to obtain GCC. +</p> +<p>The source distribution includes the C, C++, Objective-C, Fortran, Java, +and Ada (in the case of GCC 3.1 and later) compilers, as well as +runtime libraries for C++, Objective-C, Fortran, and Java. +For previous versions these were downloadable as separate components such +as the core GCC distribution, which included the C language front end and +shared components, and language-specific distributions including the +language front end and the language runtime (where appropriate). +</p> +<p>If you also intend to build binutils (either to upgrade an existing installation or for use in place of the corresponding tools of your OS), unpack the binutils distribution either in the same directory or a separate one. In the latter case, add symbolic links to any components of the binutils you intend to build alongside the compiler -(<samp><span class="file">bfd</span></samp>, <samp><span class="file">binutils</span></samp>, <samp><span class="file">gas</span></samp>, <samp><span class="file">gprof</span></samp>, <samp><span class="file">ld</span></samp>, -<samp><span class="file">opcodes</span></samp>, <small class="dots">...</small>) to the directory containing the GCC sources. - - <p>Likewise the GMP, MPFR and MPC libraries can be automatically built +(<samp>bfd</samp>, <samp>binutils</samp>, <samp>gas</samp>, <samp>gprof</samp>, <samp>ld</samp>, +<samp>opcodes</samp>, …) to the directory containing the GCC sources. +</p> +<p>Likewise the GMP, MPFR and MPC libraries can be automatically built together with GCC. Unpack the GMP, MPFR and/or MPC source distributions in the directory containing the GCC sources and rename -their directories to <samp><span class="file">gmp</span></samp>, <samp><span class="file">mpfr</span></samp> and <samp><span class="file">mpc</span></samp>, +their directories to <samp>gmp</samp>, <samp>mpfr</samp> and <samp>mpc</samp>, respectively (or use symbolic links with the same name). +</p> +<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> - -<!-- ***Configuration*********************************************************** --> -<!-- ***Building**************************************************************** --> -<!-- ***Testing***************************************************************** --> -<!-- ***Final install*********************************************************** --> -<!-- ***Binaries**************************************************************** --> -<!-- ***Specific**************************************************************** --> -<!-- ***Old documentation****************************************************** --> -<!-- ***GFDL******************************************************************** --> -<!-- *************************************************************************** --> -<!-- Part 6 The End of the Document --> -</body></html> +</body> +</html> diff --git a/INSTALL/finalinstall.html b/INSTALL/finalinstall.html index 04c4e43bd4..9f592e4d5d 100644 --- a/INSTALL/finalinstall.html +++ b/INSTALL/finalinstall.html @@ -1,174 +1,227 @@ -<html lang="en"> -<head> -<title>Installing GCC: Final installation</title> -<meta http-equiv="Content-Type" content="text/html"> -<meta name="description" content="Installing GCC: Final installation"> -<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, 1989, 1992, 1993, 1994, 1995, 1996, 1997, -1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, -2010 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-2014 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: Final installation</h1> -Now that GCC has been built (and optionally tested), you can install it with -<pre class="smallexample"> cd <var>objdir</var> && make install -</pre> - <p>We strongly recommend to install into a target directory where there is + +<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000"> +<h1 class="settitle" align="center">Installing GCC</h1> + + + + + + + + + + + + + + + + + + + + + + + +<p>Now that GCC has been built (and optionally tested), you can install it with +</p><div class="smallexample"> +<pre class="smallexample">cd <var>objdir</var> && make install +</pre></div> + +<p>We strongly recommend to install into a target directory where there is no previous version of GCC present. Also, the GNAT runtime should not be stripped, as this would break certain features of the debugger that depend on this debugging information (catching Ada exceptions for instance). - - <p>That step completes the installation of GCC; user level binaries can -be found in <samp><var>prefix</var><span class="file">/bin</span></samp> where <var>prefix</var> is the value -you specified with the <samp><span class="option">--prefix</span></samp> to configure (or -<samp><span class="file">/usr/local</span></samp> by default). (If you specified <samp><span class="option">--bindir</span></samp>, +</p> +<p>That step completes the installation of GCC; user level binaries can +be found in <samp><var>prefix</var>/bin</samp> where <var>prefix</var> is the value +you specified with the <samp>--prefix</samp> to configure (or +<samp>/usr/local</samp> by default). (If you specified <samp>--bindir</samp>, that directory will be used instead; otherwise, if you specified -<samp><span class="option">--exec-prefix</span></samp>, <samp><var>exec-prefix</var><span class="file">/bin</span></samp> will be used.) +<samp>--exec-prefix</samp>, <samp><var>exec-prefix</var>/bin</samp> will be used.) Headers for the C++ and Java libraries are installed in -<samp><var>prefix</var><span class="file">/include</span></samp>; libraries in <samp><var>libdir</var></samp> -(normally <samp><var>prefix</var><span class="file">/lib</span></samp>); internal parts of the compiler in -<samp><var>libdir</var><span class="file">/gcc</span></samp> and <samp><var>libexecdir</var><span class="file">/gcc</span></samp>; documentation +<samp><var>prefix</var>/include</samp>; libraries in <samp><var>libdir</var></samp> +(normally <samp><var>prefix</var>/lib</samp>); internal parts of the compiler in +<samp><var>libdir</var>/gcc</samp> and <samp><var>libexecdir</var>/gcc</samp>; documentation in info format in <samp><var>infodir</var></samp> (normally -<samp><var>prefix</var><span class="file">/info</span></samp>). - - <p>When installing cross-compilers, GCC's executables +<samp><var>prefix</var>/info</samp>). +</p> +<p>When installing cross-compilers, GCC’s executables are not only installed into <samp><var>bindir</var></samp>, that -is, <samp><var>exec-prefix</var><span class="file">/bin</span></samp>, but additionally into -<samp><var>exec-prefix</var><span class="file">/</span><var>target-alias</var><span class="file">/bin</span></samp>, if that directory -exists. Typically, such <dfn>tooldirs</dfn> hold target-specific +is, <samp><var>exec-prefix</var>/bin</samp>, but additionally into +<samp><var>exec-prefix</var>/<var>target-alias</var>/bin</samp>, if that directory +exists. Typically, such <em>tooldirs</em> hold target-specific binutils, including assembler and linker. - - <p>Installation into a temporary staging area or into a <samp><span class="command">chroot</span></samp> +</p> +<p>Installation into a temporary staging area or into a <code>chroot</code> jail can be achieved with the command +</p> +<div class="smallexample"> +<pre class="smallexample">make DESTDIR=<var>path-to-rootdir</var> install +</pre></div> -<pre class="smallexample"> make DESTDIR=<var>path-to-rootdir</var> install -</pre> - <p class="noindent">where <var>path-to-rootdir</var> is the absolute path of +<p>where <var>path-to-rootdir</var> is the absolute path of a directory relative to which all installation paths will be interpreted. Note that the directory specified by <code>DESTDIR</code> need not exist yet; it will be created if necessary. - - <p>There is a subtle point with tooldirs and <code>DESTDIR</code>: +</p> +<p>There is a subtle point with tooldirs and <code>DESTDIR</code>: If you relocate a cross-compiler installation with -e.g. ‘<samp><span class="samp">DESTDIR=</span><var>rootdir</var></samp>’, then the directory -<samp><var>rootdir</var><span class="file">/</span><var>exec-prefix</var><span class="file">/</span><var>target-alias</var><span class="file">/bin</span></samp> will +e.g. ‘<samp>DESTDIR=<var>rootdir</var></samp>’, then the directory +<samp><var>rootdir</var>/<var>exec-prefix</var>/<var>target-alias</var>/bin</samp> will be filled with duplicated GCC executables only if it already exists, it will not be created otherwise. This is regarded as a feature, not as a bug, because it gives slightly more control to the packagers using the <code>DESTDIR</code> feature. - - <p>You can install stripped programs and libraries with - -<pre class="smallexample"> make install-strip -</pre> - <p>If you are bootstrapping a released version of GCC then please +</p> +<p>You can install stripped programs and libraries with +</p> +<div class="smallexample"> +<pre class="smallexample">make install-strip +</pre></div> + +<p>If you are bootstrapping a released version of GCC then please quickly review the build status page for your release, available from -<a href="http://gcc.gnu.org/buildstat.html">http://gcc.gnu.org/buildstat.html</a>. +<a href="http://gcc.gnu.org/buildstat.html">http://gcc.gnu.org/buildstat.html</a>. If your system is not listed for the version of GCC that you built, send a note to <a href="mailto:gcc@gcc.gnu.org">gcc@gcc.gnu.org</a> indicating -that you successfully built and installed GCC. +that you successfully built and installed GCC. Include the following information: - - <ul> -<li>Output from running <samp><var>srcdir</var><span class="file">/config.guess</span></samp>. Do not send +</p> +<ul> +<li> Output from running <samp><var>srcdir</var>/config.guess</samp>. Do not send that file itself, just the one-line output from running it. - <li>The output of ‘<samp><span class="samp">gcc -v</span></samp>’ for your newly installed <samp><span class="command">gcc</span></samp>. +</li><li> The output of ‘<samp>gcc -v</samp>’ for your newly installed <code>gcc</code>. This tells us which version of GCC you built and the options you passed to configure. - <li>Whether you enabled all languages or a subset of them. If you used a +</li><li> Whether you enabled all languages or a subset of them. If you used a full distribution then this information is part of the configure -options in the output of ‘<samp><span class="samp">gcc -v</span></samp>’, but if you downloaded the -“core” compiler plus additional front ends then it isn't apparent +options in the output of ‘<samp>gcc -v</samp>’, but if you downloaded the +“core” compiler plus additional front ends then it isn’t apparent which ones you built unless you tell us about it. - <li>If the build was for GNU/Linux, also include: - <ul> -<li>The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3); -this information should be available from <samp><span class="file">/etc/issue</span></samp>. +</li><li> If the build was for GNU/Linux, also include: +<ul> +<li> The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3); +this information should be available from <samp>/etc/issue</samp>. - <li>The version of the Linux kernel, available from ‘<samp><span class="samp">uname --version</span></samp>’ -or ‘<samp><span class="samp">uname -a</span></samp>’. +</li><li> The version of the Linux kernel, available from ‘<samp>uname --version</samp>’ +or ‘<samp>uname -a</samp>’. - <li>The version of glibc you used; for RPM-based systems like Red Hat, -Mandrake, and SuSE type ‘<samp><span class="samp">rpm -q glibc</span></samp>’ to get the glibc version, -and on systems like Debian and Progeny use ‘<samp><span class="samp">dpkg -l libc6</span></samp>’. -</ul> - For other systems, you can include similar information if you think it is +</li><li> The version of glibc you used; for RPM-based systems like Red Hat, +Mandrake, and SuSE type ‘<samp>rpm -q glibc</samp>’ to get the glibc version, +and on systems like Debian and Progeny use ‘<samp>dpkg -l libc6</samp>’. +</li></ul> +<p>For other systems, you can include similar information if you think it is relevant. - - <li>Any other information that you think would be useful to people building +</p> +</li><li> Any other information that you think would be useful to people building GCC on the same configuration. The new entry in the build status list -will include a link to the archived copy of your message. -</ul> +will include a link to the archived copy of your message. +</li></ul> - <p>We'd also like to know if the +<p>We’d also like to know if the <a href="specific.html">host/target specific installation notes</a> -didn't include your host/target information or if that information is +didn’t include your host/target information or if that information is incomplete or out of date. Send a note to <a href="mailto:gcc@gcc.gnu.org">gcc@gcc.gnu.org</a> detailing how the information should be changed. - - <p>If you find a bug, please report it following the +</p> +<p>If you find a bug, please report it following the <a href="../bugs/">bug reporting guidelines</a>. - - <p>If you want to print the GCC manuals, do ‘<samp><span class="samp">cd </span><var>objdir</var><span class="samp">; make -dvi</span></samp>’. You will need to have <samp><span class="command">texi2dvi</span></samp> (version at least 4.7) -and TeX installed. This creates a number of <samp><span class="file">.dvi</span></samp> files in +</p> +<p>If you want to print the GCC manuals, do ‘<samp>cd <var>objdir</var>; make +dvi</samp>’. You will need to have <code>texi2dvi</code> (version at least 4.7) +and TeX installed. This creates a number of <samp>.dvi</samp> files in subdirectories of <samp><var>objdir</var></samp>; these may be converted for -printing with programs such as <samp><span class="command">dvips</span></samp>. Alternately, by using -‘<samp><span class="samp">make pdf</span></samp>’ in place of ‘<samp><span class="samp">make dvi</span></samp>’, you can create documentation -in the form of <samp><span class="file">.pdf</span></samp> files; this requires <samp><span class="command">texi2pdf</span></samp>, which +printing with programs such as <code>dvips</code>. Alternately, by using +‘<samp>make pdf</samp>’ in place of ‘<samp>make dvi</samp>’, you can create documentation +in the form of <samp>.pdf</samp> files; this requires <code>texi2pdf</code>, which is included with Texinfo version 4.8 and later. You can also -<a href="http://shop.fsf.org/">buy printed manuals from the Free Software Foundation</a>, though such manuals may not be for the most +<a href="http://shop.fsf.org/">buy printed manuals from the +Free Software Foundation</a>, though such manuals may not be for the most recent version of GCC. +</p> +<p>If you would like to generate online HTML documentation, do ‘<samp>cd +<var>objdir</var>; make html</samp>’ and HTML will be generated for the gcc manuals in +<samp><var>objdir</var>/gcc/HTML</samp>. +</p> +<hr /> +<p><p><a href="./index.html">Return to the GCC Installation page</a> +</p> + + + + - <p>If you would like to generate online HTML documentation, do ‘<samp><span class="samp">cd -</span><var>objdir</var><span class="samp">; make html</span></samp>’ and HTML will be generated for the gcc manuals in -<samp><var>objdir</var><span class="file">/gcc/HTML</span></samp>. - <p><hr /> -<p><a href="./index.html">Return to the GCC Installation page</a> -<!-- ***Binaries**************************************************************** --> -<!-- ***Specific**************************************************************** --> -<!-- ***Old documentation****************************************************** --> -<!-- ***GFDL******************************************************************** --> -<!-- *************************************************************************** --> -<!-- Part 6 The End of the Document --> -</body></html> +</body> +</html> diff --git a/INSTALL/gfdl.html b/INSTALL/gfdl.html index 0e8c13d826..d87a789112 100644 --- a/INSTALL/gfdl.html +++ b/INSTALL/gfdl.html @@ -1,84 +1,133 @@ -<html lang="en"> -<head> -<title>Installing GCC: GNU Free Documentation License</title> -<meta http-equiv="Content-Type" content="text/html"> -<meta name="description" content="Installing GCC: GNU Free Documentation License"> -<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, 1989, 1992, 1993, 1994, 1995, 1996, 1997, -1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, -2010 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-2014 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: GNU Free Documentation License</h1> -<h1 align="center">Installing GCC: GNU Free Documentation License</h1><!-- man begin DESCRIPTION --> - - <p><a name="index-FDL_002c-GNU-Free-Documentation-License-1"></a><div align="center">Version 1.3, 3 November 2008</div> - -<pre class="display"> Copyright © 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. - <a href="http://fsf.org/">http://fsf.org/</a> - - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not allowed. -</pre> - <ol type=1 start=0> -<li>PREAMBLE - - <p>The purpose of this License is to make a manual, textbook, or other -functional and useful document <dfn>free</dfn> in the sense of freedom: to + +<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000"> +<h1 class="settitle" align="center">Installing GCC</h1> + + + + + + + + + + + + + + + + + + + + + + + + + + +<h1 align="center">Installing GCC: GNU Free Documentation License</h1> +<a name="index-FDL_002c-GNU-Free-Documentation-License"></a> +<div align="center">Version 1.3, 3 November 2008 +</div> +<div class="display"> +<pre class="display">Copyright © 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. +<a href="http://fsf.org/">http://fsf.org/</a> + +Everyone is permitted to copy and distribute verbatim copies +of this license document, but changing it is not allowed. +</pre></div> + +<ol> +<li> PREAMBLE + +<p>The purpose of this License is to make a manual, textbook, or other +functional and useful document <em>free</em> in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, -with or without modifying it, either commercially or noncommercially. +with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others. - - <p>This License is a kind of “copyleft”, which means that derivative +</p> +<p>This License is a kind of “copyleft”, which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software. - - <p>We have designed this License in order to use it for manuals for free +</p> +<p>We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference. +</p> +</li><li> APPLICABILITY AND DEFINITIONS - <li>APPLICABILITY AND DEFINITIONS - - <p>This License applies to any manual or other work, in any medium, that +<p>This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that @@ -87,14 +136,14 @@ refers to any such manual or work. Any member of the public is a licensee, and is addressed as “you”. You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law. - - <p>A “Modified Version” of the Document means any work containing the +</p> +<p>A “Modified Version” of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language. - - <p>A “Secondary Section” is a named appendix or a front-matter section +</p> +<p>A “Secondary Section” is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the -publishers or authors of the Document to the Document's overall +publishers or authors of the Document to the Document’s overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain @@ -102,21 +151,21 @@ any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them. - - <p>The “Invariant Sections” are certain Secondary Sections whose titles +</p> +<p>The “Invariant Sections” are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none. - - <p>The “Cover Texts” are certain short passages of text that are listed, +</p> +<p>The “Cover Texts” are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words. - - <p>A “Transparent” copy of the Document means a machine-readable copy, +</p> +<p>A “Transparent” copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of @@ -125,12 +174,12 @@ drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart -or discourage subsequent modification by readers is not Transparent. +or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not “Transparent” is called “Opaque”. - - <p>Examples of suitable formats for Transparent copies include plain -<span class="sc">ascii</span> without markup, Texinfo input format, LaTeX input +</p> +<p>Examples of suitable formats for Transparent copies include plain +<small>ASCII</small> without markup, Texinfo input format, LaTeX input format, <acronym>SGML</acronym> or <acronym>XML</acronym> using a publicly available <acronym>DTD</acronym>, and standard-conforming simple <acronym>HTML</acronym>, PostScript or <acronym>PDF</acronym> designed for human modification. Examples @@ -141,35 +190,35 @@ read and edited only by proprietary word processors, <acronym>SGML</acronym> or not generally available, and the machine-generated <acronym>HTML</acronym>, PostScript or <acronym>PDF</acronym> produced by some word processors for output purposes only. - - <p>The “Title Page” means, for a printed book, the title page itself, +</p> +<p>The “Title Page” means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, “Title Page” means -the text near the most prominent appearance of the work's title, +the text near the most prominent appearance of the work’s title, preceding the beginning of the body of the text. - - <p>The “publisher” means any person or entity that distributes copies +</p> +<p>The “publisher” means any person or entity that distributes copies of the Document to the public. - - <p>A section “Entitled XYZ” means a named subunit of the Document whose +</p> +<p>A section “Entitled XYZ” means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as “Acknowledgements”, “Dedications”, “Endorsements”, or “History”.) To “Preserve the Title” of such a section when you modify the Document means that it remains a section “Entitled XYZ” according to this definition. - - <p>The Document may include Warranty Disclaimers next to the notice which +</p> +<p>The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License. +</p> +</li><li> VERBATIM COPYING - <li>VERBATIM COPYING - - <p>You may copy and distribute the Document in any medium, either +<p>You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other @@ -178,87 +227,87 @@ technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3. - - <p>You may also lend copies, under the same conditions stated above, and +</p> +<p>You may also lend copies, under the same conditions stated above, and you may publicly display copies. +</p> +</li><li> COPYING IN QUANTITY - <li>COPYING IN QUANTITY - - <p>If you publish printed copies (or copies in media that commonly have +<p>If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the -Document's license notice requires Cover Texts, you must enclose the +Document’s license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and -visible. You may add other material on the covers in addition. +visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects. - - <p>If the required texts for either cover are too voluminous to fit +</p> +<p>If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages. - - <p>If you publish or distribute Opaque copies of the Document numbering +</p> +<p>If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols -a complete Transparent copy of the Document, free of added material. +a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public. - - <p>It is requested, but not required, that you contact the authors of the +</p> +<p>It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document. +</p> +</li><li> MODIFICATIONS - <li>MODIFICATIONS - - <p>You may copy and distribute a Modified Version of the Document under +<p>You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version: - - <ol type=A start=1> -<li>Use in the Title Page (and on the covers, if any) a title distinct +</p> +<ol> +<li> Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission. - <li>List on the Title Page, as authors, one or more persons or entities +</li><li> List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement. - <li>State on the Title page the name of the publisher of the +</li><li> State on the Title page the name of the publisher of the Modified Version, as the publisher. - <li>Preserve all the copyright notices of the Document. +</li><li> Preserve all the copyright notices of the Document. - <li>Add an appropriate copyright notice for your modifications +</li><li> Add an appropriate copyright notice for your modifications adjacent to the other copyright notices. - <li>Include, immediately after the copyright notices, a license notice +</li><li> Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below. - <li>Preserve in that license notice the full lists of Invariant Sections -and required Cover Texts given in the Document's license notice. +</li><li> Preserve in that license notice the full lists of Invariant Sections +and required Cover Texts given in the Document’s license notice. - <li>Include an unaltered copy of this License. +</li><li> Include an unaltered copy of this License. - <li>Preserve the section Entitled “History”, Preserve its Title, and add +</li><li> Preserve the section Entitled “History”, Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled “History” in the Document, create one @@ -266,46 +315,46 @@ stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence. - <li>Preserve the network location, if any, given in the Document for +</li><li> Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions -it was based on. These may be placed in the “History” section. +it was based on. These may be placed in the “History” section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission. - <li>For any section Entitled “Acknowledgements” or “Dedications”, Preserve +</li><li> For any section Entitled “Acknowledgements” or “Dedications”, Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein. - <li>Preserve all the Invariant Sections of the Document, +</li><li> Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles. - <li>Delete any section Entitled “Endorsements”. Such a section +</li><li> Delete any section Entitled “Endorsements”. Such a section may not be included in the Modified Version. - <li>Do not retitle any existing section to be Entitled “Endorsements” or +</li><li> Do not retitle any existing section to be Entitled “Endorsements” or to conflict in title with any Invariant Section. - <li>Preserve any Warranty Disclaimers. - </ol> +</li><li> Preserve any Warranty Disclaimers. +</li></ol> - <p>If the Modified Version includes new front-matter sections or +<p>If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the -list of Invariant Sections in the Modified Version's license notice. +list of Invariant Sections in the Modified Version’s license notice. These titles must be distinct from any other section titles. - - <p>You may add a section Entitled “Endorsements”, provided it contains +</p> +<p>You may add a section Entitled “Endorsements”, provided it contains nothing but endorsements of your Modified Version by various parties—for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard. - - <p>You may add a passage of up to five words as a Front-Cover Text, and a +</p> +<p>You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or @@ -314,71 +363,71 @@ includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one. - - <p>The author(s) and publisher(s) of the Document do not by this License +</p> +<p>The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version. +</p> +</li><li> COMBINING DOCUMENTS - <li>COMBINING DOCUMENTS - - <p>You may combine the Document with other documents released under this +<p>You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers. - - <p>The combined work need only contain one copy of this License, and +</p> +<p>The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original -author or publisher of that section if known, or else a unique number. +author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work. - - <p>In the combination, you must combine any sections Entitled “History” +</p> +<p>In the combination, you must combine any sections Entitled “History” in the various original documents, forming one section Entitled “History”; likewise combine any sections Entitled “Acknowledgements”, and any sections Entitled “Dedications”. You must delete all sections Entitled “Endorsements.” +</p> +</li><li> COLLECTIONS OF DOCUMENTS - <li>COLLECTIONS OF DOCUMENTS - - <p>You may make a collection consisting of the Document and other documents +<p>You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects. - - <p>You may extract a single document from such a collection, and distribute +</p> +<p>You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document. +</p> +</li><li> AGGREGATION WITH INDEPENDENT WORKS - <li>AGGREGATION WITH INDEPENDENT WORKS - - <p>A compilation of the Document or its derivatives with other separate +<p>A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an “aggregate” if the copyright resulting from the compilation is not used to limit the legal rights -of the compilation's users beyond what the individual works permit. +of the compilation’s users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document. - - <p>If the Cover Text requirement of section 3 is applicable to these +</p> +<p>If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of -the entire aggregate, the Document's Cover Texts may be placed on +the entire aggregate, the Document’s Cover Texts may be placed on covers that bracket the Document within the aggregate, or the -electronic equivalent of covers if the Document is in electronic form. +electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate. +</p> +</li><li> TRANSLATION - <li>TRANSLATION - - <p>Translation is considered a kind of modification, so you may -distribute translations of the Document under the terms of section 4. +<p>Translation is considered a kind of modification, so you may +distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the @@ -389,48 +438,48 @@ the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail. - - <p>If a section in the Document is Entitled “Acknowledgements”, +</p> +<p>If a section in the Document is Entitled “Acknowledgements”, “Dedications”, or “History”, the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title. +</p> +</li><li> TERMINATION - <li>TERMINATION - - <p>You may not copy, modify, sublicense, or distribute the Document +<p>You may not copy, modify, sublicense, or distribute the Document except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, or distribute it is void, and will automatically terminate your rights under this License. - - <p>However, if you cease all violation of this License, then your license +</p> +<p>However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. - - <p>Moreover, your license from a particular copyright holder is +</p> +<p>Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice. - - <p>Termination of your rights under this section does not terminate the +</p> +<p>Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, receipt of a copy of some or all of the same material does not give you any rights to use it. +</p> +</li><li> FUTURE REVISIONS OF THIS LICENSE - <li>FUTURE REVISIONS OF THIS LICENSE - - <p>The Free Software Foundation may publish new, revised versions +<p>The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See <a href="http://www.gnu.org/copyleft/">http://www.gnu.org/copyleft/</a>. - - <p>Each version of the License is given a distinguishing version number. +</p> +<p>Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License “or any later version” applies to it, you have the option of following the terms and conditions either of that specified version or @@ -439,79 +488,84 @@ Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation. If the Document specifies that a proxy can decide which future versions of this -License can be used, that proxy's public statement of acceptance of a +License can be used, that proxy’s public statement of acceptance of a version permanently authorizes you to choose that version for the Document. +</p> +</li><li> RELICENSING - <li>RELICENSING - - <p>“Massive Multiauthor Collaboration Site” (or “MMC Site”) means any +<p>“Massive Multiauthor Collaboration Site” (or “MMC Site”) means any World Wide Web server that publishes copyrightable works and also provides prominent facilities for anybody to edit those works. A public wiki that anybody can edit is an example of such a server. A “Massive Multiauthor Collaboration” (or “MMC”) contained in the site means any set of copyrightable works thus published on the MMC site. - - <p>“CC-BY-SA” means the Creative Commons Attribution-Share Alike 3.0 +</p> +<p>“CC-BY-SA” means the Creative Commons Attribution-Share Alike 3.0 license published by Creative Commons Corporation, a not-for-profit corporation with a principal place of business in San Francisco, California, as well as future copyleft versions of that license published by that same organization. - - <p>“Incorporate” means to publish or republish a Document, in whole or +</p> +<p>“Incorporate” means to publish or republish a Document, in whole or in part, as part of another Document. - - <p>An MMC is “eligible for relicensing” if it is licensed under this +</p> +<p>An MMC is “eligible for relicensing” if it is licensed under this License, and if all works that were first published under this License somewhere other than this MMC, and subsequently incorporated in whole or in part into the MMC, (1) had no cover texts or invariant sections, and (2) were thus incorporated prior to November 1, 2008. - - <p>The operator of an MMC Site may republish an MMC contained in the site +</p> +<p>The operator of an MMC Site may republish an MMC contained in the site under CC-BY-SA on the same site at any time before August 1, 2009, provided the MMC is eligible for relicensing. +</p> +</li></ol> - </ol> - -<h3 class="unnumberedsec"><a name="TOC0"></a>ADDENDUM: How to use this License for your documents</h3> +<a name="ADDENDUM_003a-How-to-use-this-License-for-your-documents"></a> +<h3 class="unnumberedsec">ADDENDUM: How to use this License for your documents</h3> <p>To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page: - -<pre class="smallexample"> Copyright (C) <var>year</var> <var>your name</var>. - 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, no Front-Cover Texts, and no Back-Cover - Texts. A copy of the license is included in the section entitled ``GNU - Free Documentation License''. -</pre> - <p>If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, +</p> +<div class="smallexample"> +<pre class="smallexample"> Copyright (C) <var>year</var> <var>your name</var>. + 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, no Front-Cover Texts, and no Back-Cover + Texts. A copy of the license is included in the section entitled ``GNU + Free Documentation License''. +</pre></div> + +<p>If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the “with...Texts.” line with this: - -<pre class="smallexample"> with the Invariant Sections being <var>list their titles</var>, with - the Front-Cover Texts being <var>list</var>, and with the Back-Cover Texts - being <var>list</var>. -</pre> - <p>If you have Invariant Sections without Cover Texts, or some other +</p> +<div class="smallexample"> +<pre class="smallexample"> with the Invariant Sections being <var>list their titles</var>, with + the Front-Cover Texts being <var>list</var>, and with the Back-Cover Texts + being <var>list</var>. +</pre></div> + +<p>If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation. - - <p>If your document contains nontrivial examples of program code, we +</p> +<p>If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software. +</p> + +<hr /> +<p><p><a href="./index.html">Return to the GCC Installation page</a> +</p> + +<hr> -<!-- Local Variables: --> -<!-- ispell-local-pdict: "ispell-dict" --> -<!-- End: --> -<!-- man end --> - <p><hr /> -<p><a href="./index.html">Return to the GCC Installation page</a> -<!-- *************************************************************************** --> -<!-- Part 6 The End of the Document --> -</body></html> +</body> +</html> diff --git a/INSTALL/index.html b/INSTALL/index.html index 6dbc332332..2812c77e18 100644 --- a/INSTALL/index.html +++ b/INSTALL/index.html @@ -1,125 +1,165 @@ -<html lang="en"> -<head> -<title>Installing GCC</title> -<meta http-equiv="Content-Type" content="text/html"> -<meta name="description" content="Installing GCC"> -<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, 1989, 1992, 1993, 1994, 1995, 1996, 1997, -1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, -2010 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-2014 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</h1> -The latest version of this document is always available at -<a href="http://gcc.gnu.org/install/">http://gcc.gnu.org/install/</a>. - <p>This document describes the generic installation procedure for GCC as well -as detailing some target specific installation instructions. +<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000"> +<h1 class="settitle" align="center">Installing GCC</h1> + + + + + + + + + - <p>GCC includes several components that previously were separate distributions -with their own installation instructions. This document supersedes all -package specific installation instructions. - <p><em>Before</em> starting the build/install procedure please check the -<a href="specific.html">host/target specific installation notes</a>. -We recommend you browse the entire generic installation instructions before -you proceed. - <p>Lists of successful builds for released versions of GCC are -available at <a href="http://gcc.gnu.org/buildstat.html">http://gcc.gnu.org/buildstat.html</a>. -These lists are updated as new information becomes available. - <p>The installation procedure itself is broken into five steps. - <ol type=1 start=1> -<li><a href="prerequisites.html">Prerequisites</a> -<li><a href="download.html">Downloading the source</a> -<li><a href="configure.html">Configuration</a> -<li><a href="build.html">Building</a> -<li><a href="test.html">Testing</a> (optional) -<li><a href="finalinstall.html">Final install</a> - </ol> - <p>Please note that GCC does not support ‘<samp><span class="samp">make uninstall</span></samp>’ and probably -won't do so in the near future as this would open a can of worms. Instead, + + +<p>The latest version of this document is always available at +<a href="http://gcc.gnu.org/install/">http://gcc.gnu.org/install/</a>. +It refers to the current development sources, instructions for +specific released versions are included with the sources. +</p> +<p>This document describes the generic installation procedure for GCC as well +as detailing some target specific installation instructions. +</p> +<p>GCC includes several components that previously were separate distributions +with their own installation instructions. This document supersedes all +package-specific installation instructions. +</p> +<p><em>Before</em> starting the build/install procedure please check the +<a href="specific.html">host/target specific installation notes</a>. +We recommend you browse the entire generic installation instructions before +you proceed. +</p> +<p>Lists of successful builds for released versions of GCC are +available at <a href="http://gcc.gnu.org/buildstat.html">http://gcc.gnu.org/buildstat.html</a>. +These lists are updated as new information becomes available. +</p> +<p>The installation procedure itself is broken into five steps. +</p> +<ol> +<li> <a href="prerequisites.html">Prerequisites</a> +</li><li> <a href="download.html">Downloading the source</a> +</li><li> <a href="configure.html">Configuration</a> +</li><li> <a href="build.html">Building</a> +</li><li> <a href="test.html">Testing</a> (optional) +</li><li> <a href="finalinstall.html">Final install</a> +</li></ol> + +<p>Please note that GCC does not support ‘<samp>make uninstall</samp>’ and probably +won’t do so in the near future as this would open a can of worms. Instead, we suggest that you install GCC into a directory of its own and simply remove that directory when you do not need that specific version of GCC any longer, and, if shared libraries are installed there as well, no more binaries exist that use them. - - <p>There are also some <a href="old.html">old installation instructions</a>, +</p> +<p>There are also some <a href="old.html">old installation instructions</a>, which are mostly obsolete but still contain some information which has not yet been merged into the main part of this manual. - - <p><hr /> -<p><a href="./index.html">Return to the GCC Installation page</a> - - <p>Copyright © 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, -1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, -2010 Free Software Foundation, Inc. - <pre class="sp"> - -</pre> -Permission is granted to copy, distribute and/or modify this document +</p> +<hr /> +<p><p><a href="./index.html">Return to the GCC Installation page</a> +</p> +<p>Copyright © 1988-2014 Free Software Foundation, Inc. +</p><br> +<p>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 “<a href="./gfdl.html">GNU Free Documentation License</a>”. +license is included in the section entitled “<a href="./gfdl.html">GNU +Free Documentation License</a>”. +</p> +<p>(a) The FSF’s Front-Cover Text is: +</p> +<p>A GNU Manual +</p> +<p>(b) The FSF’s Back-Cover Text is: +</p> +<p>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. +</p> + + + + + + + + + - <p>(a) The FSF's Front-Cover Text is: - <p>A GNU Manual - <p>(b) The FSF's Back-Cover Text is: - <p>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. -<!-- ***Prerequisites************************************************** --> -<!-- ***Downloading the source************************************************** --> -<!-- ***Configuration*********************************************************** --> -<!-- ***Building**************************************************************** --> -<!-- ***Testing***************************************************************** --> -<!-- ***Final install*********************************************************** --> -<!-- ***Binaries**************************************************************** --> -<!-- ***Specific**************************************************************** --> -<!-- ***Old documentation****************************************************** --> -<!-- ***GFDL******************************************************************** --> -<!-- *************************************************************************** --> -<!-- Part 6 The End of the Document --> -</body></html> +</body> +</html> diff --git a/INSTALL/old.html b/INSTALL/old.html index 370568e1ff..9891930ada 100644 --- a/INSTALL/old.html +++ b/INSTALL/old.html @@ -1,183 +1,231 @@ -<html lang="en"> -<head> -<title>Installing GCC: Old documentation</title> -<meta http-equiv="Content-Type" content="text/html"> -<meta name="description" content="Installing GCC: Old documentation"> -<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, 1989, 1992, 1993, 1994, 1995, 1996, 1997, -1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, -2010 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-2014 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: Old documentation</h1> -<h1 align="center">Old installation documentation</h1> - <p>Note most of this information is out of date and superseded by the +<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000"> +<h1 class="settitle" align="center">Installing GCC</h1> + + + + + + + + + + + + + + + + + + + + + + + + + + +<h1 align="center">Old installation documentation</h1> +<p>Note most of this information is out of date and superseded by the previous chapters of this manual. It is provided for historical reference only, because of a lack of volunteers to merge it into the main manual. +</p> - <p>Here is the procedure for installing GCC on a GNU or Unix system. - - <ol type=1 start=1> -<li>If you have chosen a configuration for GCC which requires other GNU +<p>Here is the procedure for installing GCC on a GNU or Unix system. +</p> +<ol> +<li> If you have chosen a configuration for GCC which requires other GNU tools (such as GAS or the GNU linker) instead of the standard system tools, install the required tools in the build directory under the names -<samp><span class="file">as</span></samp>, <samp><span class="file">ld</span></samp> or whatever is appropriate. +<samp>as</samp>, <samp>ld</samp> or whatever is appropriate. - <p>Alternatively, you can do subsequent compilation using a value of the +<p>Alternatively, you can do subsequent compilation using a value of the <code>PATH</code> environment variable such that the necessary GNU tools come before the standard system tools. +</p> +</li><li> Specify the host, build and target machine configurations. You do this +when you run the <samp>configure</samp> script. - <li>Specify the host, build and target machine configurations. You do this -when you run the <samp><span class="file">configure</span></samp> script. - - <p>The <dfn>build</dfn> machine is the system which you are using, the -<dfn>host</dfn> machine is the system where you want to run the resulting -compiler (normally the build machine), and the <dfn>target</dfn> machine is +<p>The <em>build</em> machine is the system which you are using, the +<em>host</em> machine is the system where you want to run the resulting +compiler (normally the build machine), and the <em>target</em> machine is the system for which you want the compiler to generate code. - - <p>If you are building a compiler to produce code for the machine it runs +</p> +<p>If you are building a compiler to produce code for the machine it runs on (a native compiler), you normally do not need to specify any operands -to <samp><span class="file">configure</span></samp>; it will try to guess the type of machine you are on -and use that as the build, host and target machines. So you don't need +to <samp>configure</samp>; it will try to guess the type of machine you are on +and use that as the build, host and target machines. So you don’t need to specify a configuration when building a native compiler unless -<samp><span class="file">configure</span></samp> cannot figure out what your configuration is or guesses +<samp>configure</samp> cannot figure out what your configuration is or guesses wrong. - - <p>In those cases, specify the build machine's <dfn>configuration name</dfn> -with the <samp><span class="option">--host</span></samp> option; the host and target will default to be +</p> +<p>In those cases, specify the build machine’s <em>configuration name</em> +with the <samp>--host</samp> option; the host and target will default to be the same as the host machine. - - <p>Here is an example: - - <pre class="smallexample"> ./configure --host=sparc-sun-sunos4.1 -</pre> - <p>A configuration name may be canonical or it may be more or less +</p> +<p>Here is an example: +</p> +<div class="smallexample"> +<pre class="smallexample">./configure --host=sparc-sun-sunos4.1 +</pre></div> + +<p>A configuration name may be canonical or it may be more or less abbreviated. - - <p>A canonical configuration name has three parts, separated by dashes. -It looks like this: ‘<samp><var>cpu</var><span class="samp">-</span><var>company</var><span class="samp">-</span><var>system</var></samp>’. -(The three parts may themselves contain dashes; <samp><span class="file">configure</span></samp> +</p> +<p>A canonical configuration name has three parts, separated by dashes. +It looks like this: ‘<samp><var>cpu</var>-<var>company</var>-<var>system</var></samp>’. +(The three parts may themselves contain dashes; <samp>configure</samp> can figure out which dashes serve which purpose.) For example, -‘<samp><span class="samp">m68k-sun-sunos4.1</span></samp>’ specifies a Sun 3. - - <p>You can also replace parts of the configuration by nicknames or aliases. -For example, ‘<samp><span class="samp">sun3</span></samp>’ stands for ‘<samp><span class="samp">m68k-sun</span></samp>’, so -‘<samp><span class="samp">sun3-sunos4.1</span></samp>’ is another way to specify a Sun 3. - - <p>You can specify a version number after any of the system types, and some +‘<samp>m68k-sun-sunos4.1</samp>’ specifies a Sun 3. +</p> +<p>You can also replace parts of the configuration by nicknames or aliases. +For example, ‘<samp>sun3</samp>’ stands for ‘<samp>m68k-sun</samp>’, so +‘<samp>sun3-sunos4.1</samp>’ is another way to specify a Sun 3. +</p> +<p>You can specify a version number after any of the system types, and some of the CPU types. In most cases, the version is irrelevant, and will be ignored. So you might as well specify the version if you know it. - - <p>See <a href="#Configurations">Configurations</a>, for a list of supported configuration names and +</p> +<p>See <a href="#Configurations">Configurations</a>, for a list of supported configuration names and notes on many of the configurations. You should check the notes in that section before proceeding any further with the installation of GCC. +</p> +</li></ol> - </ol> +<h2><a name="Configurations"></a>Configurations Supported by GCC</h2><a name="index-configurations-supported-by-GCC"></a> - <p><h2><a name="Configurations"></a>Configurations Supported by GCC</h2><a name="index-configurations-supported-by-GCC-1"></a> -Here are the possible CPU types: - - <blockquote> -<!-- gmicro, fx80, spur and tahoe omitted since they don't work. --> -1750a, a29k, alpha, arm, avr, c<var>n</var>, clipper, dsp16xx, elxsi, fr30, h8300, +<p>Here are the possible CPU types: +</p> +<blockquote> +<p>1750a, a29k, alpha, arm, avr, c<var>n</var>, clipper, dsp16xx, elxsi, fr30, h8300, hppa1.0, hppa1.1, i370, i386, i486, i586, i686, i786, i860, i960, ip2k, m32r, m68000, m68k, m88k, mcore, mips, mipsel, mips64, mips64el, mn10200, mn10300, ns32k, pdp11, powerpc, powerpcle, romp, rs6000, sh, sparc, -sparclite, sparc64, v850, vax, we32k. -</blockquote> +sparclite, sparc64, v850, vax, we32k. +</p></blockquote> - <p>Here are the recognized company names. As you can see, customary +<p>Here are the recognized company names. As you can see, customary abbreviations are used rather than the longer official names. - -<!-- What should be done about merlin, tek*, dolphin? --> - <blockquote> -acorn, alliant, altos, apollo, apple, att, bull, +</p> +<blockquote> +<p>acorn, alliant, altos, apollo, apple, att, bull, cbm, convergent, convex, crds, dec, dg, dolphin, elxsi, encore, harris, hitachi, hp, ibm, intergraph, isi, mips, motorola, ncr, next, ns, omron, plexus, -sequent, sgi, sony, sun, tti, unicom, wrs. -</blockquote> +sequent, sgi, sony, sun, tti, unicom, wrs. +</p></blockquote> - <p>The company name is meaningful only to disambiguate when the rest of +<p>The company name is meaningful only to disambiguate when the rest of the information supplied is insufficient. You can omit it, writing -just ‘<samp><var>cpu</var><span class="samp">-</span><var>system</var></samp>’, if it is not needed. For example, -‘<samp><span class="samp">vax-ultrix4.2</span></samp>’ is equivalent to ‘<samp><span class="samp">vax-dec-ultrix4.2</span></samp>’. - - <p>Here is a list of system types: - - <blockquote> -386bsd, aix, acis, amigaos, aos, aout, aux, bosx, bsd, clix, coff, ctix, cxux, +just ‘<samp><var>cpu</var>-<var>system</var></samp>’, if it is not needed. For example, +‘<samp>vax-ultrix4.2</samp>’ is equivalent to ‘<samp>vax-dec-ultrix4.2</samp>’. +</p> +<p>Here is a list of system types: +</p> +<blockquote> +<p>386bsd, aix, acis, amigaos, aos, aout, aux, bosx, bsd, clix, coff, ctix, cxux, dgux, dynix, ebmon, ecoff, elf, esix, freebsd, hms, genix, gnu, linux, linux-gnu, hiux, hpux, iris, irix, isc, luna, lynxos, mach, minix, msdos, mvs, netbsd, newsos, nindy, ns, osf, osfrose, ptx, riscix, riscos, rtu, sco, sim, solaris, sunos, sym, sysv, udi, ultrix, unicos, uniplus, unos, vms, vsta, -vxworks, winnt, xenix. -</blockquote> +vxworks, winnt, xenix. +</p></blockquote> -<p class="noindent">You can omit the system type; then <samp><span class="file">configure</span></samp> guesses the +<p>You can omit the system type; then <samp>configure</samp> guesses the operating system from the CPU and company. - - <p>You can add a version number to the system type; this may or may not -make a difference. For example, you can write ‘<samp><span class="samp">bsd4.3</span></samp>’ or -‘<samp><span class="samp">bsd4.4</span></samp>’ to distinguish versions of BSD. In practice, the version -number is most needed for ‘<samp><span class="samp">sysv3</span></samp>’ and ‘<samp><span class="samp">sysv4</span></samp>’, which are often +</p> +<p>You can add a version number to the system type; this may or may not +make a difference. For example, you can write ‘<samp>bsd4.3</samp>’ or +‘<samp>bsd4.4</samp>’ to distinguish versions of BSD. In practice, the version +number is most needed for ‘<samp>sysv3</samp>’ and ‘<samp>sysv4</samp>’, which are often treated differently. - - <p>‘<samp><span class="samp">linux-gnu</span></samp>’ is the canonical name for the GNU/Linux target; however -GCC will also accept ‘<samp><span class="samp">linux</span></samp>’. The version of the kernel in use is -not relevant on these systems. A suffix such as ‘<samp><span class="samp">libc1</span></samp>’ or ‘<samp><span class="samp">aout</span></samp>’ +</p> +<p>‘<samp>linux-gnu</samp>’ is the canonical name for the GNU/Linux target; however +GCC will also accept ‘<samp>linux</samp>’. The version of the kernel in use is +not relevant on these systems. A suffix such as ‘<samp>libc1</samp>’ or ‘<samp>aout</samp>’ distinguishes major versions of the C library; all of the suffixed versions are obsolete. - - <p>If you specify an impossible combination such as ‘<samp><span class="samp">i860-dg-vms</span></samp>’, -then you may get an error message from <samp><span class="file">configure</span></samp>, or it may -ignore part of the information and do the best it can with the rest. -<samp><span class="file">configure</span></samp> always prints the canonical name for the alternative +</p> +<p>If you specify an impossible combination such as ‘<samp>i860-dg-vms</samp>’, +then you may get an error message from <samp>configure</samp>, or it may +ignore part of the information and do the best it can with the rest. +<samp>configure</samp> always prints the canonical name for the alternative that it used. GCC does not support all possible alternatives. - - <p>Often a particular model of machine has a name. Many machine names are +</p> +<p>Often a particular model of machine has a name. Many machine names are recognized as aliases for CPU/company combinations. Thus, the machine -name ‘<samp><span class="samp">sun3</span></samp>’, mentioned above, is an alias for ‘<samp><span class="samp">m68k-sun</span></samp>’. +name ‘<samp>sun3</samp>’, mentioned above, is an alias for ‘<samp>m68k-sun</samp>’. Sometimes we accept a company name as a machine name, when the name is popularly used for a particular machine. Here is a table of the known machine names: - - <blockquote> -3300, 3b1, 3b<var>n</var>, 7300, altos3068, altos, +</p> +<blockquote> +<p>3300, 3b1, 3b<var>n</var>, 7300, altos3068, altos, apollo68, att-7300, balance, convex-c<var>n</var>, crds, decstation-3100, decstation, delta, encore, @@ -188,16 +236,18 @@ m3230, magnum, merlin, miniframe, mmax, news-3600, news800, news, next, pbd, pc532, pmax, powerpc, powerpcle, ps2, risc-news, rtpc, sun2, sun386i, sun386, sun3, -sun4, symmetry, tower-32, tower. -</blockquote> +sun4, symmetry, tower-32, tower. +</p></blockquote> -<p class="noindent">Remember that a machine name specifies both the cpu type and the company -name. +<p>Remember that a machine name specifies both the cpu type and the company +name. <hr /> <p><a href="./index.html">Return to the GCC Installation page</a> +</p> + + + -<!-- ***GFDL******************************************************************** --> -<!-- *************************************************************************** --> -<!-- Part 6 The End of the Document --> -</body></html> +</body> +</html> diff --git a/INSTALL/prerequisites.html b/INSTALL/prerequisites.html index 2d3d972e9c..3b9cf58c94 100644 --- a/INSTALL/prerequisites.html +++ b/INSTALL/prerequisites.html @@ -1,297 +1,431 @@ -<html lang="en"> -<head> -<title>Prerequisites for GCC</title> -<meta http-equiv="Content-Type" content="text/html"> -<meta name="description" content="Prerequisites for GCC"> -<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, 1989, 1992, 1993, 1994, 1995, 1996, 1997, -1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, -2010 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-2014 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">Prerequisites for GCC</h1> -<a name="index-Prerequisites-1"></a> -GCC requires that various tools and packages be available for use in the -build procedure. Modifying GCC sources requires additional tools -described below. -<h3 class="heading"><a name="TOC0"></a>Tools/packages necessary for building GCC</h3> +<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000"> +<h1 class="settitle" align="center">Installing GCC</h1> + + + + + + + + + + + + + - <dl> -<dt>ISO C90 compiler<dd>Necessary to bootstrap GCC, although versions of GCC prior -to 3.4 also allow bootstrapping with a traditional (K&R) C compiler. - <p>To build all languages in a cross-compiler or other configuration where + + +<a name="index-Prerequisites"></a> + +<p>GCC requires that various tools and packages be available for use in the +build procedure. Modifying GCC sources requires additional tools +described below. +</p> +<a name="Tools_002fpackages-necessary-for-building-GCC"></a> +<h3 class="heading">Tools/packages necessary for building GCC</h3> +<dl compact="compact"> +<dt>ISO C++98 compiler</dt> +<dd><p>Necessary to bootstrap GCC, although versions of GCC prior +to 4.8 also allow bootstrapping with a ISO C89 compiler and versions +of GCC prior to 3.4 also allow bootstrapping with a traditional +(K&R) C compiler. +</p> +<p>To build all languages in a cross-compiler or other configuration where 3-stage bootstrap is not performed, you need to start with an existing -GCC binary (version 2.95 or later) because source code for language +GCC binary (version 3.4 or later) because source code for language frontends other than C might use GCC extensions. - - <br><dt>GNAT<dd> -In order to build the Ada compiler (GNAT) you must already have GNAT +</p> +<p>Note that to bootstrap GCC with versions of GCC earlier than 3.4, you +may need to use <samp>--disable-stage1-checking</samp>, though +bootstrapping the compiler with such earlier compilers is strongly +discouraged. +</p> +</dd> +<dt>C standard library and headers</dt> +<dd> +<p>In order to build GCC, the C standard library and headers must be present +for all target variants for which target libraries will be built (and not +only the variant of the host C++ compiler). +</p> +<p>This affects the popular ‘<samp>x86_64-unknown-linux-gnu</samp>’ platform (among +other multilib targets), for which 64-bit (‘<samp>x86_64</samp>’) and 32-bit +(‘<samp>i386</samp>’) libc headers are usually packaged separately. If you do a +build of a native compiler on ‘<samp>x86_64-unknown-linux-gnu</samp>’, make sure you +either have the 32-bit libc developer package properly installed (the exact +name of the package depends on your distro) or you must build GCC as a +64-bit only compiler by configuring with the option +<samp>--disable-multilib</samp>. Otherwise, you may encounter an error such as +‘<samp>fatal error: gnu/stubs-32.h: No such file</samp>’ +</p> +</dd> +<dt>GNAT</dt> +<dd> +<p>In order to build the Ada compiler (GNAT) you must already have GNAT installed because portions of the Ada frontend are written in Ada (with GNAT extensions.) Refer to the Ada installation instructions for more specific information. - - <br><dt>A “working” POSIX compatible shell, or GNU bash<dd> -Necessary when running <samp><span class="command">configure</span></samp> because some -<samp><span class="command">/bin/sh</span></samp> shells have bugs and may crash when configuring the -target libraries. In other cases, <samp><span class="command">/bin/sh</span></samp> or <samp><span class="command">ksh</span></samp> +</p> +</dd> +<dt>A “working” POSIX compatible shell, or GNU bash</dt> +<dd> +<p>Necessary when running <code>configure</code> because some +<code>/bin/sh</code> shells have bugs and may crash when configuring the +target libraries. In other cases, <code>/bin/sh</code> or <code>ksh</code> have disastrous corner-case performance problems. This -can cause target <samp><span class="command">configure</span></samp> runs to literally take days to +can cause target <code>configure</code> runs to literally take days to complete in some cases. - - <p>So on some platforms <samp><span class="command">/bin/ksh</span></samp> is sufficient, on others it -isn't. See the host/target specific instructions for your platform, or -use <samp><span class="command">bash</span></samp> to be sure. Then set <samp><span class="env">CONFIG_SHELL</span></samp> in your +</p> +<p>So on some platforms <code>/bin/ksh</code> is sufficient, on others it +isn’t. See the host/target specific instructions for your platform, or +use <code>bash</code> to be sure. Then set <code>CONFIG_SHELL</code> in your environment to your “good” shell prior to running -<samp><span class="command">configure</span></samp>/<samp><span class="command">make</span></samp>. - - <p><samp><span class="command">zsh</span></samp> is not a fully compliant POSIX shell and will not +<code>configure</code>/<code>make</code>. +</p> +<p><code>zsh</code> is not a fully compliant POSIX shell and will not work when configuring GCC. - - <br><dt>A POSIX or SVR4 awk<dd> -Necessary for creating some of the generated source files for GCC. +</p> +</dd> +<dt>A POSIX or SVR4 awk</dt> +<dd> +<p>Necessary for creating some of the generated source files for GCC. If in doubt, use a recent GNU awk version, as some of the older ones are broken. GNU awk version 3.1.5 is known to work. - - <br><dt>GNU binutils<dd> -Necessary in some circumstances, optional in others. See the +</p> +</dd> +<dt>GNU binutils</dt> +<dd> +<p>Necessary in some circumstances, optional in others. See the host/target specific instructions for your platform for the exact requirements. - - <br><dt>gzip version 1.2.4 (or later) or<dt>bzip2 version 1.0.2 (or later)<dd> -Necessary to uncompress GCC <samp><span class="command">tar</span></samp> files when source code is +</p> +</dd> +<dt>gzip version 1.2.4 (or later) or</dt> +<dt>bzip2 version 1.0.2 (or later)</dt> +<dd> +<p>Necessary to uncompress GCC <code>tar</code> files when source code is obtained via FTP mirror sites. - - <br><dt>GNU make version 3.80 (or later)<dd> -You must have GNU make installed to build GCC. - - <br><dt>GNU tar version 1.14 (or later)<dd> -Necessary (only on some platforms) to untar the source code. Many -systems' <samp><span class="command">tar</span></samp> programs will also work, only try GNU -<samp><span class="command">tar</span></samp> if you have problems. - - <br><dt>Perl version 5.6.1 (or later)<dd> -Necessary when targetting Darwin, building ‘<samp><span class="samp">libstdc++</span></samp>’, -and not using <samp><span class="option">--disable-symvers</span></samp>. -Necessary when targetting Solaris 2 with Sun <samp><span class="command">ld</span></samp> and not using -<samp><span class="option">--disable-symvers</span></samp>. The bundled <samp><span class="command">perl</span></samp> in Solaris 8 +</p> +</dd> +<dt>GNU make version 3.80 (or later)</dt> +<dd> +<p>You must have GNU make installed to build GCC. +</p> +</dd> +<dt>GNU tar version 1.14 (or later)</dt> +<dd> +<p>Necessary (only on some platforms) to untar the source code. Many +systems’ <code>tar</code> programs will also work, only try GNU +<code>tar</code> if you have problems. +</p> +</dd> +<dt>Perl version 5.6.1 (or later)</dt> +<dd> +<p>Necessary when targeting Darwin, building ‘<samp>libstdc++</samp>’, +and not using <samp>--disable-symvers</samp>. +Necessary when targeting Solaris 2 with Sun <code>ld</code> and not using +<samp>--disable-symvers</samp>. The bundled <code>perl</code> in Solaris 8 and up works. - - <p>Necessary when regenerating <samp><span class="file">Makefile</span></samp> dependencies in libiberty. -Necessary when regenerating <samp><span class="file">libiberty/functions.texi</span></samp>. -Necessary when generating manpages from Texinfo manuals. +</p> +<p>Necessary when regenerating <samp>Makefile</samp> dependencies in libiberty. +Necessary when regenerating <samp>libiberty/functions.texi</samp>. +Necessary when generating manpages from Texinfo manuals. Used by various scripts to generate some files included in SVN (mainly Unicode-related and rarely changing) from source tables. - - <br><dt><samp><span class="command">jar</span></samp>, or InfoZIP (<samp><span class="command">zip</span></samp> and <samp><span class="command">unzip</span></samp>)<dd> -Necessary to build libgcj, the GCJ runtime. - +</p> +</dd> +<dt><code>jar</code>, or InfoZIP (<code>zip</code> and <code>unzip</code>)</dt> +<dd> +<p>Necessary to build libgcj, the GCJ runtime. +</p> +</dd> </dl> - <p>Several support libraries are necessary to build GCC, some are required, +<p>Several support libraries are necessary to build GCC, some are required, others optional. While any sufficiently new version of required tools usually work, library requirements are generally stricter. Newer -versions may work in some cases, but it's safer to use the exact +versions may work in some cases, but it’s safer to use the exact versions documented. We appreciate bug reports about problems with newer versions, though. If your OS vendor provides packages for the support libraries then using those packages may be the simplest way to install the libraries. - - <dl> -<dt>GNU Multiple Precision Library (GMP) version 4.3.2 (or later)<dd> -Necessary to build GCC. If a GMP source distribution is found in a -subdirectory of your GCC sources named <samp><span class="file">gmp</span></samp>, it will be built +</p> +<dl compact="compact"> +<dt>GNU Multiple Precision Library (GMP) version 4.3.2 (or later)</dt> +<dd> +<p>Necessary to build GCC. If a GMP source distribution is found in a +subdirectory of your GCC sources named <samp>gmp</samp>, it will be built together with GCC. Alternatively, if GMP is already installed but it is not in your library search path, you will have to configure with the -<samp><span class="option">--with-gmp</span></samp> configure option. See also <samp><span class="option">--with-gmp-lib</span></samp> -and <samp><span class="option">--with-gmp-include</span></samp>. - - <br><dt>MPFR Library version 2.4.2 (or later)<dd> -Necessary to build GCC. It can be downloaded from +<samp>--with-gmp</samp> configure option. See also <samp>--with-gmp-lib</samp> +and <samp>--with-gmp-include</samp>. +</p> +</dd> +<dt>MPFR Library version 2.4.2 (or later)</dt> +<dd> +<p>Necessary to build GCC. It can be downloaded from <a href="http://www.mpfr.org/">http://www.mpfr.org/</a>. If an MPFR source distribution is found -in a subdirectory of your GCC sources named <samp><span class="file">mpfr</span></samp>, it will be +in a subdirectory of your GCC sources named <samp>mpfr</samp>, it will be built together with GCC. Alternatively, if MPFR is already installed but it is not in your default library search path, the -<samp><span class="option">--with-mpfr</span></samp> configure option should be used. See also -<samp><span class="option">--with-mpfr-lib</span></samp> and <samp><span class="option">--with-mpfr-include</span></samp>. - - <br><dt>MPC Library version 0.8.1 (or later)<dd> -Necessary to build GCC. It can be downloaded from +<samp>--with-mpfr</samp> configure option should be used. See also +<samp>--with-mpfr-lib</samp> and <samp>--with-mpfr-include</samp>. +</p> +</dd> +<dt>MPC Library version 0.8.1 (or later)</dt> +<dd> +<p>Necessary to build GCC. It can be downloaded from <a href="http://www.multiprecision.org/">http://www.multiprecision.org/</a>. If an MPC source distribution -is found in a subdirectory of your GCC sources named <samp><span class="file">mpc</span></samp>, it +is found in a subdirectory of your GCC sources named <samp>mpc</samp>, it will be built together with GCC. Alternatively, if MPC is already installed but it is not in your default library search path, the -<samp><span class="option">--with-mpc</span></samp> configure option should be used. See also -<samp><span class="option">--with-mpc-lib</span></samp> and <samp><span class="option">--with-mpc-include</span></samp>. - - <br><dt>Parma Polyhedra Library (PPL) version 0.11<dd> -Necessary to build GCC with the Graphite loop optimizations. -It can be downloaded from <a href="http://www.cs.unipr.it/ppl/Download/">http://www.cs.unipr.it/ppl/Download/</a>. - - <p>The <samp><span class="option">--with-ppl</span></samp> configure option should be used if PPL is not -installed in your default library search path. - - <br><dt>CLooG-PPL version 0.15 or CLooG 0.16<dd> -Necessary to build GCC with the Graphite loop optimizations. There -are two versions available. CLooG-PPL 0.15 as well as CLooG 0.16. -The former is the default right now. It can be downloaded from -<a href="ftp://gcc.gnu.org/pub/gcc/infrastructure/">ftp://gcc.gnu.org/pub/gcc/infrastructure/</a> as -<samp><span class="file">cloog-ppl-0.15.tar.gz</span></samp>. - - <p>CLooG 0.16 support is still in testing stage, but will be the -default in future GCC releases. It is also available at -<a href="ftp://gcc.gnu.org/pub/gcc/infrastructure/">ftp://gcc.gnu.org/pub/gcc/infrastructure/</a> as -<samp><span class="file">cloog-0.16.1.tar.gz</span></samp>. To use it add the additional configure -option <samp><span class="option">--enable-cloog-backend=isl</span></samp>. Even if CLooG 0.16 -does not use PPL, PPL is still required for Graphite. - - <p>In both cases <samp><span class="option">--with-cloog</span></samp> configure option should be used -if CLooG is not installed in your default library search path. - - </dl> - -<h3 class="heading"><a name="TOC1"></a>Tools/packages necessary for modifying GCC</h3> - - <dl> -<dt>autoconf version 2.64<dt>GNU m4 version 1.4.6 (or later)<dd> -Necessary when modifying <samp><span class="file">configure.ac</span></samp>, <samp><span class="file">aclocal.m4</span></samp>, etc. -to regenerate <samp><span class="file">configure</span></samp> and <samp><span class="file">config.in</span></samp> files. - - <br><dt>automake version 1.11.1<dd> -Necessary when modifying a <samp><span class="file">Makefile.am</span></samp> file to regenerate its -associated <samp><span class="file">Makefile.in</span></samp>. +<samp>--with-mpc</samp> configure option should be used. See also +<samp>--with-mpc-lib</samp> and <samp>--with-mpc-include</samp>. +</p> +</dd> +<dt>ISL Library version 0.12.2</dt> +<dd> +<p>Necessary to build GCC with the Graphite loop optimizations. +It can be downloaded from <a href="ftp://gcc.gnu.org/pub/gcc/infrastructure/">ftp://gcc.gnu.org/pub/gcc/infrastructure/</a> +as <samp>isl-0.12.2.tar.bz2</samp>. If an ISL source distribution is found +in a subdirectory of your GCC sources named <samp>isl</samp>, it will be +built together with GCC. Alternatively, the <samp>--with-isl</samp> configure +option should be used if ISL is not installed in your default library +search path. +</p> +</dd> +<dt>CLooG 0.18.1</dt> +<dd> +<p>Necessary to build GCC with the Graphite loop optimizations. It can be +downloaded from <a href="ftp://gcc.gnu.org/pub/gcc/infrastructure/">ftp://gcc.gnu.org/pub/gcc/infrastructure/</a> as +<samp>cloog-0.18.1.tar.gz</samp>. If a CLooG source distribution is found +in a subdirectory of your GCC sources named <samp>cloog</samp>, it will be +built together with GCC. Alternatively, the <samp>--with-cloog</samp> configure +option should be used if CLooG is not installed in your default library search +path. +</p> +<p>If you want to install CLooG separately it needs to be built against +ISL 0.12.2 by using the <samp>--with-isl=system</samp> to direct CLooG to pick +up an already installed ISL. Using the ISL library as bundled with CLooG +is not supported. +</p> +</dd> +</dl> - <p>Much of GCC does not use automake, so directly edit the <samp><span class="file">Makefile.in</span></samp> -file. Specifically this applies to the <samp><span class="file">gcc</span></samp>, <samp><span class="file">intl</span></samp>, -<samp><span class="file">libcpp</span></samp>, <samp><span class="file">libiberty</span></samp>, <samp><span class="file">libobjc</span></samp> directories as well +<a name="Tools_002fpackages-necessary-for-modifying-GCC"></a> +<h3 class="heading">Tools/packages necessary for modifying GCC</h3> +<dl compact="compact"> +<dt>autoconf version 2.64</dt> +<dt>GNU m4 version 1.4.6 (or later)</dt> +<dd> +<p>Necessary when modifying <samp>configure.ac</samp>, <samp>aclocal.m4</samp>, etc. +to regenerate <samp>configure</samp> and <samp>config.in</samp> files. +</p> +</dd> +<dt>automake version 1.11.1</dt> +<dd> +<p>Necessary when modifying a <samp>Makefile.am</samp> file to regenerate its +associated <samp>Makefile.in</samp>. +</p> +<p>Much of GCC does not use automake, so directly edit the <samp>Makefile.in</samp> +file. Specifically this applies to the <samp>gcc</samp>, <samp>intl</samp>, +<samp>libcpp</samp>, <samp>libiberty</samp>, <samp>libobjc</samp> directories as well as any of their subdirectories. - - <p>For directories that use automake, GCC requires the latest release in +</p> +<p>For directories that use automake, GCC requires the latest release in the 1.11 series, which is currently 1.11.1. When regenerating a directory to a newer version, please update all the directories using an older 1.11 to the latest released version. - - <br><dt>gettext version 0.14.5 (or later)<dd> -Needed to regenerate <samp><span class="file">gcc.pot</span></samp>. - - <br><dt>gperf version 2.7.2 (or later)<dd> -Necessary when modifying <samp><span class="command">gperf</span></samp> input files, e.g. -<samp><span class="file">gcc/cp/cfns.gperf</span></samp> to regenerate its associated header file, e.g. -<samp><span class="file">gcc/cp/cfns.h</span></samp>. - - <br><dt>DejaGnu 1.4.4<dt>Expect<dt>Tcl<dd> -Necessary to run the GCC testsuite; see the section on testing for details. - - <br><dt>autogen version 5.5.4 (or later) and<dt>guile version 1.4.1 (or later)<dd> -Necessary to regenerate <samp><span class="file">fixinc/fixincl.x</span></samp> from -<samp><span class="file">fixinc/inclhack.def</span></samp> and <samp><span class="file">fixinc/*.tpl</span></samp>. - - <p>Necessary to run ‘<samp><span class="samp">make check</span></samp>’ for <samp><span class="file">fixinc</span></samp>. - - <p>Necessary to regenerate the top level <samp><span class="file">Makefile.in</span></samp> file from -<samp><span class="file">Makefile.tpl</span></samp> and <samp><span class="file">Makefile.def</span></samp>. - - <br><dt>Flex version 2.5.4 (or later)<dd> -Necessary when modifying <samp><span class="file">*.l</span></samp> files. - - <p>Necessary to build GCC during development because the generated output +</p> +</dd> +<dt>gettext version 0.14.5 (or later)</dt> +<dd> +<p>Needed to regenerate <samp>gcc.pot</samp>. +</p> +</dd> +<dt>gperf version 2.7.2 (or later)</dt> +<dd> +<p>Necessary when modifying <code>gperf</code> input files, e.g. +<samp>gcc/cp/cfns.gperf</samp> to regenerate its associated header file, e.g. +<samp>gcc/cp/cfns.h</samp>. +</p> +</dd> +<dt>DejaGnu 1.4.4</dt> +<dt>Expect</dt> +<dt>Tcl</dt> +<dd> +<p>Necessary to run the GCC testsuite; see the section on testing for +details. Tcl 8.6 has a known regression in RE pattern handling that +make parts of the testsuite fail. See +<a href="http://core.tcl.tk/tcl/tktview/267b7e2334ee2e9de34c4b00d6e72e2f1997085f">http://core.tcl.tk/tcl/tktview/267b7e2334ee2e9de34c4b00d6e72e2f1997085f</a> +for more information. +</p> +</dd> +<dt>autogen version 5.5.4 (or later) and</dt> +<dt>guile version 1.4.1 (or later)</dt> +<dd> +<p>Necessary to regenerate <samp>fixinc/fixincl.x</samp> from +<samp>fixinc/inclhack.def</samp> and <samp>fixinc/*.tpl</samp>. +</p> +<p>Necessary to run ‘<samp>make check</samp>’ for <samp>fixinc</samp>. +</p> +<p>Necessary to regenerate the top level <samp>Makefile.in</samp> file from +<samp>Makefile.tpl</samp> and <samp>Makefile.def</samp>. +</p> +</dd> +<dt>Flex version 2.5.4 (or later)</dt> +<dd> +<p>Necessary when modifying <samp>*.l</samp> files. +</p> +<p>Necessary to build GCC during development because the generated output files are not included in the SVN repository. They are included in releases. - - <br><dt>Texinfo version 4.7 (or later)<dd> -Necessary for running <samp><span class="command">makeinfo</span></samp> when modifying <samp><span class="file">*.texi</span></samp> +</p> +</dd> +<dt>Texinfo version 4.7 (or later)</dt> +<dd> +<p>Necessary for running <code>makeinfo</code> when modifying <samp>*.texi</samp> files to test your changes. - - <p>Necessary for running <samp><span class="command">make dvi</span></samp> or <samp><span class="command">make pdf</span></samp> to +</p> +<p>Necessary for running <code>make dvi</code> or <code>make pdf</code> to create printable documentation in DVI or PDF format. Texinfo version -4.8 or later is required for <samp><span class="command">make pdf</span></samp>. - - <p>Necessary to build GCC documentation during development because the +4.8 or later is required for <code>make pdf</code>. +</p> +<p>Necessary to build GCC documentation during development because the generated output files are not included in the SVN repository. They are included in releases. - - <br><dt>TeX (any working version)<dd> -Necessary for running <samp><span class="command">texi2dvi</span></samp> and <samp><span class="command">texi2pdf</span></samp>, which -are used when running <samp><span class="command">make dvi</span></samp> or <samp><span class="command">make pdf</span></samp> to create +</p> +</dd> +<dt>TeX (any working version)</dt> +<dd> +<p>Necessary for running <code>texi2dvi</code> and <code>texi2pdf</code>, which +are used when running <code>make dvi</code> or <code>make pdf</code> to create DVI or PDF files, respectively. - - <br><dt>SVN (any version)<dt>SSH (any version)<dd> -Necessary to access the SVN repository. Public releases and weekly +</p> +</dd> +<dt>SVN (any version)</dt> +<dt>SSH (any version)</dt> +<dd> +<p>Necessary to access the SVN repository. Public releases and weekly snapshots of the development sources are also available via FTP. - - <br><dt>GNU diffutils version 2.7 (or later)<dd> -Useful when submitting patches for the GCC source code. - - <br><dt>patch version 2.5.4 (or later)<dd> -Necessary when applying patches, created with <samp><span class="command">diff</span></samp>, to one's +</p> +</dd> +<dt>GNU diffutils version 2.7 (or later)</dt> +<dd> +<p>Useful when submitting patches for the GCC source code. +</p> +</dd> +<dt>patch version 2.5.4 (or later)</dt> +<dd> +<p>Necessary when applying patches, created with <code>diff</code>, to one’s own sources. - - <br><dt>ecj1<dt>gjavah<dd> -If you wish to modify <samp><span class="file">.java</span></samp> files in libjava, you will need to -configure with <samp><span class="option">--enable-java-maintainer-mode</span></samp>, and you will need -to have executables named <samp><span class="command">ecj1</span></samp> and <samp><span class="command">gjavah</span></samp> in your path. -The <samp><span class="command">ecj1</span></samp> executable should run the Eclipse Java compiler via +</p> +</dd> +<dt>ecj1</dt> +<dt>gjavah</dt> +<dd> +<p>If you wish to modify <samp>.java</samp> files in libjava, you will need to +configure with <samp>--enable-java-maintainer-mode</samp>, and you will need +to have executables named <code>ecj1</code> and <code>gjavah</code> in your path. +The <code>ecj1</code> executable should run the Eclipse Java compiler via the GCC-specific entry point. You can download a suitable jar from <a href="ftp://sourceware.org/pub/java/">ftp://sourceware.org/pub/java/</a>, or by running the script -<samp><span class="command">contrib/download_ecj</span></samp>. - - <br><dt>antlr.jar version 2.7.1 (or later)<dt>antlr binary<dd> -If you wish to build the <samp><span class="command">gjdoc</span></samp> binary in libjava, you will -need to have an <samp><span class="file">antlr.jar</span></samp> library available. The library is +<code>contrib/download_ecj</code>. +</p> +</dd> +<dt>antlr.jar version 2.7.1 (or later)</dt> +<dt>antlr binary</dt> +<dd> +<p>If you wish to build the <code>gjdoc</code> binary in libjava, you will +need to have an <samp>antlr.jar</samp> library available. The library is searched for in system locations but can be specified with -<samp><span class="option">--with-antlr-jar=</span></samp> instead. When configuring with -<samp><span class="option">--enable-java-maintainer-mode</span></samp>, you will need to have one of -the executables named <samp><span class="command">cantlr</span></samp>, <samp><span class="command">runantlr</span></samp> or -<samp><span class="command">antlr</span></samp> in your path. - +<samp>--with-antlr-jar=</samp> instead. When configuring with +<samp>--enable-java-maintainer-mode</samp>, you will need to have one of +the executables named <code>cantlr</code>, <code>runantlr</code> or +<code>antlr</code> in your path. +</p> +</dd> </dl> - <p><hr /> -<p><a href="./index.html">Return to the GCC Installation page</a> - -<!-- ***Downloading the source************************************************** --> -<!-- ***Configuration*********************************************************** --> -<!-- ***Building**************************************************************** --> -<!-- ***Testing***************************************************************** --> -<!-- ***Final install*********************************************************** --> -<!-- ***Binaries**************************************************************** --> -<!-- ***Specific**************************************************************** --> -<!-- ***Old documentation****************************************************** --> -<!-- ***GFDL******************************************************************** --> -<!-- *************************************************************************** --> -<!-- Part 6 The End of the Document --> -</body></html> +<hr /> +<p><p><a href="./index.html">Return to the GCC Installation page</a> +</p> + + + + + + + + + + + + +</body> +</html> diff --git a/INSTALL/specific.html b/INSTALL/specific.html index 3de182f62d..f85373a52a 100644 --- a/INSTALL/specific.html +++ b/INSTALL/specific.html @@ -1,1577 +1,1431 @@ -<html lang="en"> -<head> -<title>Host/Target specific installation notes for GCC</title> -<meta http-equiv="Content-Type" content="text/html"> -<meta name="description" content="Host/Target specific installation notes for GCC"> -<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, 1989, 1992, 1993, 1994, 1995, 1996, 1997, -1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, -2010 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-2014 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">Host/Target specific installation notes for GCC</h1> -<a name="index-Specific-1"></a><a name="index-Specific-installation-notes-2"></a><a name="index-Target-specific-installation-3"></a><a name="index-Host-specific-installation-4"></a><a name="index-Target-specific-installation-notes-5"></a> -Please read this document carefully <em>before</em> installing the -GNU Compiler Collection on your machine. - <p>Note that this list of install notes is <em>not</em> a list of supported -hosts or targets. Not all supported hosts and targets are listed -here, only the ones that require host-specific or target-specific -information are. - - <ul> -<li><a href="#alpha-x-x">alpha*-*-*</a> -<li><a href="#alpha-dec-osf51">alpha*-dec-osf5.1</a> -<li><a href="#amd64-x-solaris210">amd64-*-solaris2.10</a> -<li><a href="#arm-x-eabi">arm-*-eabi</a> -<li><a href="#avr">avr</a> -<li><a href="#bfin">Blackfin</a> -<li><a href="#dos">DOS</a> -<li><a href="#x-x-freebsd">*-*-freebsd*</a> -<li><a href="#h8300-hms">h8300-hms</a> -<li><a href="#hppa-hp-hpux">hppa*-hp-hpux*</a> -<li><a href="#hppa-hp-hpux10">hppa*-hp-hpux10</a> -<li><a href="#hppa-hp-hpux11">hppa*-hp-hpux11</a> -<li><a href="#x-x-linux-gnu">*-*-linux-gnu</a> -<li><a href="#ix86-x-linux">i?86-*-linux*</a> -<li><a href="#ix86-x-solaris289">i?86-*-solaris2.[89]</a> -<li><a href="#ix86-x-solaris210">i?86-*-solaris2.10</a> -<li><a href="#ia64-x-linux">ia64-*-linux</a> -<li><a href="#ia64-x-hpux">ia64-*-hpux*</a> -<li><a href="#x-ibm-aix">*-ibm-aix*</a> -<li><a href="#iq2000-x-elf">iq2000-*-elf</a> -<li><a href="#lm32-x-elf">lm32-*-elf</a> -<li><a href="#lm32-x-uclinux">lm32-*-uclinux</a> -<li><a href="#m32c-x-elf">m32c-*-elf</a> -<li><a href="#m32r-x-elf">m32r-*-elf</a> -<li><a href="#m68k-x-x">m68k-*-*</a> -<li><a href="#m68k-uclinux">m68k-uclinux</a> -<li><a href="#mep-x-elf">mep-*-elf</a> -<li><a href="#microblaze-x-elf">microblaze-*-elf</a> -<li><a href="#mips-x-x">mips-*-*</a> -<li><a href="#mips-sgi-irix5">mips-sgi-irix5</a> -<li><a href="#mips-sgi-irix6">mips-sgi-irix6</a> -<li><a href="#powerpc-x-x">powerpc*-*-*</a> -<li><a href="#powerpc-x-darwin">powerpc-*-darwin*</a> -<li><a href="#powerpc-x-elf">powerpc-*-elf</a> -<li><a href="#powerpc-x-linux-gnu">powerpc*-*-linux-gnu*</a> -<li><a href="#powerpc-x-netbsd">powerpc-*-netbsd*</a> -<li><a href="#powerpc-x-eabisim">powerpc-*-eabisim</a> -<li><a href="#powerpc-x-eabi">powerpc-*-eabi</a> -<li><a href="#powerpcle-x-elf">powerpcle-*-elf</a> -<li><a href="#powerpcle-x-eabisim">powerpcle-*-eabisim</a> -<li><a href="#powerpcle-x-eabi">powerpcle-*-eabi</a> -<li><a href="#s390-x-linux">s390-*-linux*</a> -<li><a href="#s390x-x-linux">s390x-*-linux*</a> -<li><a href="#s390x-ibm-tpf">s390x-ibm-tpf*</a> -<li><a href="#x-x-solaris2">*-*-solaris2*</a> -<li><a href="#sparc-x-x">sparc*-*-*</a> -<li><a href="#sparc-sun-solaris2">sparc-sun-solaris2*</a> -<li><a href="#sparc-sun-solaris210">sparc-sun-solaris2.10</a> -<li><a href="#sparc-x-linux">sparc-*-linux*</a> -<li><a href="#sparc64-x-solaris2">sparc64-*-solaris2*</a> -<li><a href="#sparcv9-x-solaris2">sparcv9-*-solaris2*</a> -<li><a href="#c6x-x-x">c6x-*-*</a> -<li><a href="#tilegx-x-linux">tilegx-*-linux*</a> -<li><a href="#tilepro-x-linux">tilepro-*-linux*</a> -<li><a href="#x-x-vxworks">*-*-vxworks*</a> -<li><a href="#x86-64-x-x">x86_64-*-*</a> amd64-*-* -<li><a href="#x86-64-x-solaris210">x86_64-*-solaris2.1[0-9]*</a> -<li><a href="#xtensa-x-elf">xtensa*-*-elf</a> -<li><a href="#xtensa-x-linux">xtensa*-*-linux*</a> -<li><a href="#windows">Microsoft Windows</a> -<li><a href="#x-x-cygwin">*-*-cygwin</a> -<li><a href="#x-x-interix">*-*-interix</a> -<li><a href="#x-x-mingw32">*-*-mingw32</a> -<li><a href="#os2">OS/2</a> -<li><a href="#older">Older systems</a> -</ul> - - <ul> -<li><a href="#elf">all ELF targets</a> (SVR4, Solaris 2, etc.) -</ul> - - <p><!-- -------- host/target specific issues start here ---------------- --> -<hr /> +<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000"> +<h1 class="settitle" align="center">Installing GCC</h1> -<h3 class="heading"><a name="TOC0"></a><a name="alpha_002dx_002dx"></a>alpha*-*-*</h3> -<p>This section contains general configuration information for all -alpha-based platforms using ELF (in particular, ignore this section for -DEC OSF/1, Digital UNIX and Tru64 UNIX). In addition to reading this -section, please read all other sections that match your target. - <p>We require binutils 2.11.2 or newer. -Previous binutils releases had a number of problems with DWARF 2 -debugging information, not the least of which is incorrect linking of -shared libraries. - <p><hr /> -<h3 class="heading"><a name="TOC1"></a><a name="alpha_002ddec_002dosf51"></a>alpha*-dec-osf5.1</h3> -<p>Systems using processors that implement the DEC Alpha architecture and -are running the DEC/Compaq/HP Unix (DEC OSF/1, Digital UNIX, or Compaq/HP -Tru64 UNIX) operating system, for example the DEC Alpha AXP systems. - <p>Support for Tru64 UNIX V5.1 has been obsoleted in GCC 4.7, but can still -be enabled by configuring with <samp><span class="option">--enable-obsolete</span></samp>. Support will -be removed in GCC 4.8. As of GCC 4.6, support for Tru64 UNIX V4.0 and -V5.0 has been removed. As of GCC 3.2, versions before -<code>alpha*-dec-osf4</code> are no longer supported. (These are the versions -which identify themselves as DEC OSF/1.) - <p>On Tru64 UNIX, virtual memory exhausted bootstrap failures -may be fixed by reconfiguring Kernel Virtual Memory and Swap parameters -per the <samp><span class="command">/usr/sbin/sys_check</span></samp> Tuning Suggestions, -or applying the patch in -<a href="http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html">http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html</a>. Depending on -the OS version used, you need a data segment size between 512 MB and -1 GB, so simply use <samp><span class="command">ulimit -Sd unlimited</span></samp>. - <p>As of GNU binutils 2.22, neither GNU <samp><span class="command">as</span></samp> nor GNU <samp><span class="command">ld</span></samp> -are supported on Tru64 UNIX, so you must not configure GCC with -<samp><span class="option">--with-gnu-as</span></samp> or <samp><span class="option">--with-gnu-ld</span></samp>. - <p>Cross-compilers for the Tru64 UNIX target currently do not work because -the auxiliary programs <samp><span class="command">mips-tdump</span></samp> and <samp><span class="command">mips-tfile</span></samp> can't -be compiled on anything but Tru64 UNIX. - <p>GCC writes a ‘<samp><span class="samp">.verstamp</span></samp>’ directive to the assembler output file -unless it is built as a cross-compiler. It gets the version to use from -the system header file <samp><span class="file">/usr/include/stamp.h</span></samp>. If you install a -new version of Tru64 UNIX, you should rebuild GCC to pick up the new version -stamp. - <p>GCC now supports both the native (ECOFF) debugging format used by DBX -and GDB and an encapsulated STABS format for use only with GDB. See the -discussion of the <samp><span class="option">--with-stabs</span></samp> option of <samp><span class="file">configure</span></samp> above -for more information on these formats and how to select them. -<!-- FIXME: does this work at all? If so, perhaps make default. --> - <p>There is a bug in DEC's assembler that produces incorrect line numbers -for ECOFF format when the ‘<samp><span class="samp">.align</span></samp>’ directive is used. To work -around this problem, GCC will not emit such alignment directives -while writing ECOFF format debugging information even if optimization is -being performed. Unfortunately, this has the very undesirable -side-effect that code addresses when <samp><span class="option">-O</span></samp> is specified are -different depending on whether or not <samp><span class="option">-g</span></samp> is also specified. - <p>To avoid this behavior, specify <samp><span class="option">-gstabs+</span></samp> and use GDB instead of -DBX. DEC is now aware of this problem with the assembler and hopes to -provide a fix shortly. -<!-- FIXME: still applicable? --> - <p><hr /> -<h3 class="heading"><a name="TOC2"></a><a name="amd64_002dx_002dsolaris210"></a>amd64-*-solaris2.1[0-9]*</h3> -<p>This is a synonym for ‘<samp><span class="samp">x86_64-*-solaris2.1[0-9]*</span></samp>’. - <p><hr /> -<h3 class="heading"><a name="TOC3"></a><a name="arm_002dx_002deabi"></a>arm-*-eabi</h3> -<p>ARM-family processors. Subtargets that use the ELF object format -require GNU binutils 2.13 or newer. Such subtargets include: -<code>arm-*-netbsdelf</code>, <code>arm-*-*linux-gnueabi*</code> -and <code>arm-*-rtemseabi</code>. - <p><hr /> -<h3 class="heading"><a name="TOC4"></a><a name="avr"></a>avr</h3> + +<a name="index-Specific"></a> +<a name="index-Specific-installation-notes"></a> +<a name="index-Target-specific-installation"></a> +<a name="index-Host-specific-installation"></a> +<a name="index-Target-specific-installation-notes"></a> + +<p>Please read this document carefully <em>before</em> installing the +GNU Compiler Collection on your machine. +</p> +<p>Note that this list of install notes is <em>not</em> a list of supported +hosts or targets. Not all supported hosts and targets are listed +here, only the ones that require host-specific or target-specific +information have to. +</p> +<ul> +<li> <a href="#alpha-x-x">alpha*-*-*</a> +</li><li> <a href="#alpha-dec-osf51">alpha*-dec-osf5.1</a> +</li><li> <a href="#amd64-x-solaris210">amd64-*-solaris2.10</a> +</li><li> <a href="#arm-x-eabi">arm-*-eabi</a> +</li><li> <a href="#avr">avr</a> +</li><li> <a href="#bfin">Blackfin</a> +</li><li> <a href="#dos">DOS</a> +</li><li> <a href="#x-x-freebsd">*-*-freebsd*</a> +</li><li> <a href="#h8300-hms">h8300-hms</a> +</li><li> <a href="#hppa-hp-hpux">hppa*-hp-hpux*</a> +</li><li> <a href="#hppa-hp-hpux10">hppa*-hp-hpux10</a> +</li><li> <a href="#hppa-hp-hpux11">hppa*-hp-hpux11</a> +</li><li> <a href="#x-x-linux-gnu">*-*-linux-gnu</a> +</li><li> <a href="#ix86-x-linux">i?86-*-linux*</a> +</li><li> <a href="#ix86-x-solaris289">i?86-*-solaris2.9</a> +</li><li> <a href="#ix86-x-solaris210">i?86-*-solaris2.10</a> +</li><li> <a href="#ia64-x-linux">ia64-*-linux</a> +</li><li> <a href="#ia64-x-hpux">ia64-*-hpux*</a> +</li><li> <a href="#x-ibm-aix">*-ibm-aix*</a> +</li><li> <a href="#iq2000-x-elf">iq2000-*-elf</a> +</li><li> <a href="#lm32-x-elf">lm32-*-elf</a> +</li><li> <a href="#lm32-x-uclinux">lm32-*-uclinux</a> +</li><li> <a href="#m32c-x-elf">m32c-*-elf</a> +</li><li> <a href="#m32r-x-elf">m32r-*-elf</a> +</li><li> <a href="#m68k-x-x">m68k-*-*</a> +</li><li> <a href="#m68k-uclinux">m68k-uclinux</a> +</li><li> <a href="#mep-x-elf">mep-*-elf</a> +</li><li> <a href="#microblaze-x-elf">microblaze-*-elf</a> +</li><li> <a href="#mips-x-x">mips-*-*</a> +</li><li> <a href="#mips-sgi-irix5">mips-sgi-irix5</a> +</li><li> <a href="#mips-sgi-irix6">mips-sgi-irix6</a> +</li><li> <a href="#nds32le-x-elf">nds32le-*-elf</a> +</li><li> <a href="#nds32be-x-elf">nds32be-*-elf</a> +</li><li> <a href="#powerpc-x-x">powerpc*-*-*</a> +</li><li> <a href="#powerpc-x-darwin">powerpc-*-darwin*</a> +</li><li> <a href="#powerpc-x-elf">powerpc-*-elf</a> +</li><li> <a href="#powerpc-x-linux-gnu">powerpc*-*-linux-gnu*</a> +</li><li> <a href="#powerpc-x-netbsd">powerpc-*-netbsd*</a> +</li><li> <a href="#powerpc-x-eabisim">powerpc-*-eabisim</a> +</li><li> <a href="#powerpc-x-eabi">powerpc-*-eabi</a> +</li><li> <a href="#powerpcle-x-elf">powerpcle-*-elf</a> +</li><li> <a href="#powerpcle-x-eabisim">powerpcle-*-eabisim</a> +</li><li> <a href="#powerpcle-x-eabi">powerpcle-*-eabi</a> +</li><li> <a href="#s390-x-linux">s390-*-linux*</a> +</li><li> <a href="#s390x-x-linux">s390x-*-linux*</a> +</li><li> <a href="#s390x-ibm-tpf">s390x-ibm-tpf*</a> +</li><li> <a href="#x-x-solaris2">*-*-solaris2*</a> +</li><li> <a href="#sparc-x-x">sparc*-*-*</a> +</li><li> <a href="#sparc-sun-solaris2">sparc-sun-solaris2*</a> +</li><li> <a href="#sparc-sun-solaris210">sparc-sun-solaris2.10</a> +</li><li> <a href="#sparc-x-linux">sparc-*-linux*</a> +</li><li> <a href="#sparc64-x-solaris2">sparc64-*-solaris2*</a> +</li><li> <a href="#sparcv9-x-solaris2">sparcv9-*-solaris2*</a> +</li><li> <a href="#c6x-x-x">c6x-*-*</a> +</li><li> <a href="#tilegx-x-linux">tilegx-*-linux*</a> +</li><li> <a href="#tilegxbe-x-linux">tilegxbe-*-linux*</a> +</li><li> <a href="#tilepro-x-linux">tilepro-*-linux*</a> +</li><li> <a href="#x-x-vxworks">*-*-vxworks*</a> +</li><li> <a href="#x86-64-x-x">x86_64-*-*, amd64-*-*</a> +</li><li> <a href="#x86-64-x-solaris210">x86_64-*-solaris2.1[0-9]*</a> +</li><li> <a href="#xtensa-x-elf">xtensa*-*-elf</a> +</li><li> <a href="#xtensa-x-linux">xtensa*-*-linux*</a> +</li><li> <a href="#windows">Microsoft Windows</a> +</li><li> <a href="#x-x-cygwin">*-*-cygwin</a> +</li><li> <a href="#x-x-interix">*-*-interix</a> +</li><li> <a href="#x-x-mingw32">*-*-mingw32</a> +</li><li> <a href="#os2">OS/2</a> +</li><li> <a href="#older">Older systems</a> +</li></ul> + +<ul> +<li> <a href="#elf">all ELF targets</a> (SVR4, Solaris 2, etc.) +</li></ul> + + +<!-- -------- host/target specific issues start here ---------------- --> +<hr /><a name="alpha_002dx_002dx"></a><a name="alpha_002a_002d_002a_002d_002a"></a> +<h3 class="heading">alpha*-*-*</h3> +<p>This section contains general configuration information for all +alpha-based platforms using ELF (in particular, ignore this section for +DEC OSF/1, Digital UNIX and Tru64 UNIX). In addition to reading this +section, please read all other sections that match your target. +</p> +<p>We require binutils 2.11.2 or newer. +Previous binutils releases had a number of problems with DWARF 2 +debugging information, not the least of which is incorrect linking of +shared libraries. +</p> +<hr /><a name="alpha_002ddec_002dosf51"></a><a name="alpha_002a_002ddec_002dosf5_002e1"></a> +<h3 class="heading">alpha*-dec-osf5.1</h3> +<p>Systems using processors that implement the DEC Alpha architecture and +are running the DEC/Compaq/HP Unix (DEC OSF/1, Digital UNIX, or Compaq/HP +Tru64 UNIX) operating system, for example the DEC Alpha AXP systems. +</p> +<p>Support for Tru64 UNIX V5.1 has been removed in GCC 4.8. As of GCC 4.6, +support for Tru64 UNIX V4.0 and V5.0 has been removed. As of GCC 3.2, +versions before <code>alpha*-dec-osf4</code> are no longer supported. (These +are the versions which identify themselves as DEC OSF/1.) +</p> +<hr /><a name="amd64_002dx_002dsolaris210"></a><a name="amd64_002d_002a_002dsolaris2_002e1_005b0_002d9_005d_002a"></a> +<h3 class="heading">amd64-*-solaris2.1[0-9]*</h3> +<p>This is a synonym for ‘<samp>x86_64-*-solaris2.1[0-9]*</samp>’. +</p> +<hr /><a name="arc_002dx_002delf32"></a><a name="arc_002d_002a_002delf32"></a> +<h3 class="heading">arc-*-elf32</h3> + +<p>Use ‘<samp>configure --target=arc-elf32 --with-cpu=<var>cpu</var> --enable-languages="c,c++"</samp>’ +to configure GCC, with <var>cpu</var> being one of ‘<samp>arc600</samp>’, ‘<samp>arc601</samp>’, +or ‘<samp>arc700</samp>’. +</p> +<hr /><a name="arc_002dlinux_002duclibc"></a><a name="arc_002dlinux_002duclibc-1"></a> +<h3 class="heading">arc-linux-uclibc</h3> + +<p>Use ‘<samp>configure --target=arc-linux-uclibc --with-cpu=arc700 --enable-languages="c,c++"</samp>’ to configure GCC. +</p> +<hr /><a name="arm_002dx_002deabi"></a><a name="arm_002d_002a_002deabi"></a> +<h3 class="heading">arm-*-eabi</h3> +<p>ARM-family processors. Subtargets that use the ELF object format +require GNU binutils 2.13 or newer. Such subtargets include: +<code>arm-*-netbsdelf</code>, <code>arm-*-*linux-*</code> +and <code>arm-*-rtemseabi</code>. +</p> +<hr /><a name="avr"></a><a name="avr-1"></a> +<h3 class="heading">avr</h3> <p>ATMEL AVR-family micro controllers. These are used in embedded -applications. There are no standard Unix configurations. +applications. There are no standard Unix configurations. See “AVR Options” in the main manual for the list of supported MCU types. - - <p>Use ‘<samp><span class="samp">configure --target=avr --enable-languages="c"</span></samp>’ to configure GCC. - - <p>Further installation notes and other useful information about AVR tools +</p> +<p>Use ‘<samp>configure --target=avr --enable-languages="c"</samp>’ to configure GCC. +</p> +<p>Further installation notes and other useful information about AVR tools can also be obtained from: - - <ul> -<li><a href="http://www.nongnu.org/avr/">http://www.nongnu.org/avr/</a> -<li><a href="http://www.amelek.gda.pl/avr/">http://www.amelek.gda.pl/avr/</a> -</ul> - - <p>We <em>strongly</em> recommend using binutils 2.13 or newer. - - <p>The following error: -<pre class="smallexample"> Error: register required -</pre> - <p>indicates that you should upgrade to a newer version of the binutils. - - <p><hr /> - -<h3 class="heading"><a name="TOC5"></a><a name="bfin"></a>Blackfin</h3> - -<p>The Blackfin processor, an Analog Devices DSP. +</p> +<ul> +<li> <a href="http://www.nongnu.org/avr/">http://www.nongnu.org/avr/</a> +</li><li> <a href="http://www.amelek.gda.pl/avr/">http://www.amelek.gda.pl/avr/</a> +</li></ul> + +<p>We <em>strongly</em> recommend using binutils 2.13 or newer. +</p> +<p>The following error: +</p><div class="smallexample"> +<pre class="smallexample">Error: register required +</pre></div> + +<p>indicates that you should upgrade to a newer version of the binutils. +</p> +<hr /><a name="bfin"></a><a name="Blackfin"></a> +<h3 class="heading">Blackfin</h3> +<p>The Blackfin processor, an Analog Devices DSP. See “Blackfin Options” in the main manual - - <p>More information, and a version of binutils with support for this processor, +</p> +<p>More information, and a version of binutils with support for this processor, is available at <a href="http://blackfin.uclinux.org">http://blackfin.uclinux.org</a> - - <p><hr /> - -<h3 class="heading"><a name="TOC6"></a><a name="cr16"></a>CR16</h3> - -<p>The CR16 CompactRISC architecture is a 16-bit architecture. This architecture is -used in embedded applications. - - <p>See “CR16 Options” in the main manual for a list of CR16-specific options. - - <p>Use ‘<samp><span class="samp">configure --target=cr16-elf --enable-languages=c,c++</span></samp>’ to configure -GCC for building a CR16 elf cross-compiler. - - <p>Use ‘<samp><span class="samp">configure --target=cr16-uclinux --enable-languages=c,c++</span></samp>’ to configure -GCC for building a CR16 uclinux cross-compiler. - - <p><hr /> - -<h3 class="heading"><a name="TOC7"></a><a name="cris"></a>CRIS</h3> - +</p> +<hr /><a name="cr16"></a><a name="CR16"></a> +<h3 class="heading">CR16</h3> +<p>The CR16 CompactRISC architecture is a 16-bit architecture. This +architecture is used in embedded applications. +</p> + +<p>See “CR16 Options” in the main manual for a list of CR16-specific options. +</p> +<p>Use ‘<samp>configure --target=cr16-elf --enable-languages=c,c++</samp>’ to configure +GCC for building a CR16 elf cross-compiler. +</p> +<p>Use ‘<samp>configure --target=cr16-uclinux --enable-languages=c,c++</samp>’ to +configure GCC for building a CR16 uclinux cross-compiler. +</p> +<hr /><a name="cris"></a><a name="CRIS"></a> +<h3 class="heading">CRIS</h3> <p>CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip series. These are used in embedded applications. - - <p>See “CRIS Options” in the main manual +</p> +<p>See “CRIS Options” in the main manual for a list of CRIS-specific options. - - <p>There are a few different CRIS targets: - <dl> -<dt><code>cris-axis-elf</code><dd>Mainly for monolithic embedded systems. Includes a multilib for the -‘<samp><span class="samp">v10</span></samp>’ core used in ‘<samp><span class="samp">ETRAX 100 LX</span></samp>’. -<br><dt><code>cris-axis-linux-gnu</code><dd>A GNU/Linux port for the CRIS architecture, currently targeting -‘<samp><span class="samp">ETRAX 100 LX</span></samp>’ by default. +</p> +<p>There are a few different CRIS targets: +</p><dl compact="compact"> +<dt><code>cris-axis-elf</code></dt> +<dd><p>Mainly for monolithic embedded systems. Includes a multilib for the +‘<samp>v10</samp>’ core used in ‘<samp>ETRAX 100 LX</samp>’. +</p></dd> +<dt><code>cris-axis-linux-gnu</code></dt> +<dd><p>A GNU/Linux port for the CRIS architecture, currently targeting +‘<samp>ETRAX 100 LX</samp>’ by default. +</p></dd> </dl> - <p>For <code>cris-axis-elf</code> you need binutils 2.11 +<p>For <code>cris-axis-elf</code> you need binutils 2.11 or newer. For <code>cris-axis-linux-gnu</code> you need binutils 2.12 or newer. - - <p>Pre-packaged tools can be obtained from +</p> +<p>Pre-packaged tools can be obtained from <a href="ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/">ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/</a>. More information about this platform is available at <a href="http://developer.axis.com/">http://developer.axis.com/</a>. - - <p><hr /> - -<h3 class="heading"><a name="TOC8"></a><a name="dos"></a>DOS</h3> - +</p> +<hr /><a name="dos"></a><a name="DOS"></a> +<h3 class="heading">DOS</h3> <p>Please have a look at the <a href="binaries.html">binaries page</a>. - - <p>You cannot install GCC by itself on MSDOS; it will not compile under +</p> +<p>You cannot install GCC by itself on MSDOS; it will not compile under any MSDOS compiler except itself. You need to get the complete compilation package DJGPP, which includes binaries as well as sources, and includes all the necessary compilation tools and libraries. - - <p><hr /> - -<h3 class="heading"><a name="TOC9"></a><a name="epiphany_002dx_002delf"></a>epiphany-*-elf</h3> - -<p>Adapteva Epiphany. +</p> +<hr /><a name="epiphany_002dx_002delf"></a><a name="epiphany_002d_002a_002delf"></a> +<h3 class="heading">epiphany-*-elf</h3> +<p>Adapteva Epiphany. This configuration is intended for embedded systems. - - <p><hr /> - -<h3 class="heading"><a name="TOC10"></a><a name="x_002dx_002dfreebsd"></a>*-*-freebsd*</h3> - +</p> +<hr /><a name="x_002dx_002dfreebsd"></a><a name="g_t_002a_002d_002a_002dfreebsd_002a"></a> +<h3 class="heading">*-*-freebsd*</h3> <p>Support for FreeBSD 1 was discontinued in GCC 3.2. Support for FreeBSD 2 (and any mutant a.out variants of FreeBSD 3) was discontinued in GCC 4.0. - - <p>In order to better utilize FreeBSD base system functionality and match +</p> +<p>In order to better utilize FreeBSD base system functionality and match the configuration of the system compiler, GCC 4.5 and above as well as GCC 4.4 past 2010-06-20 leverage SSP support in libc (which is present on FreeBSD 7 or later) and the use of <code>__cxa_atexit</code> by default (on FreeBSD 6 or later). The use of <code>dl_iterate_phdr</code> inside -<samp><span class="file">libgcc_s.so.1</span></samp> and boehm-gc (on FreeBSD 7 or later) is enabled +<samp>libgcc_s.so.1</samp> and boehm-gc (on FreeBSD 7 or later) is enabled by GCC 4.5 and above. - - <p>We support FreeBSD using the ELF file format with DWARF 2 debugging -for all CPU architectures. You may use <samp><span class="option">-gstabs</span></samp> instead of -<samp><span class="option">-g</span></samp>, if you really want the old debugging format. There are +</p> +<p>We support FreeBSD using the ELF file format with DWARF 2 debugging +for all CPU architectures. You may use <samp>-gstabs</samp> instead of +<samp>-g</samp>, if you really want the old debugging format. There are no known issues with mixing object files and libraries with different debugging formats. Otherwise, this release of GCC should now match more of the configuration used in the stock FreeBSD configuration of -GCC. In particular, <samp><span class="option">--enable-threads</span></samp> is now configured by +GCC. In particular, <samp>--enable-threads</samp> is now configured by default. However, as a general user, do not attempt to replace the system compiler with this release. Known to bootstrap and check with good results on FreeBSD 7.2-STABLE. In the past, known to bootstrap and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4, 4.5, 4.8, 4.9 and 5-CURRENT. - - <p>The version of binutils installed in <samp><span class="file">/usr/bin</span></samp> probably works +</p> +<p>The version of binutils installed in <samp>/usr/bin</samp> probably works with this release of GCC. Bootstrapping against the latest GNU -binutils and/or the version found in <samp><span class="file">/usr/ports/devel/binutils</span></samp> has +binutils and/or the version found in <samp>/usr/ports/devel/binutils</samp> has been known to enable additional features and improve overall testsuite results. However, it is currently known that boehm-gc (which itself is required for java) may not configure properly on FreeBSD prior to the FreeBSD 7.0 release with GNU binutils after 2.16.1. - - <p><hr /> - -<h3 class="heading"><a name="TOC11"></a><a name="h8300_002dhms"></a>h8300-hms</h3> - +</p> +<hr /><a name="h8300_002dhms"></a><a name="h8300_002dhms-1"></a> +<h3 class="heading">h8300-hms</h3> <p>Renesas H8/300 series of processors. - - <p>Please have a look at the <a href="binaries.html">binaries page</a>. - - <p>The calling convention and structure layout has changed in release 2.6. +</p> +<p>Please have a look at the <a href="binaries.html">binaries page</a>. +</p> +<p>The calling convention and structure layout has changed in release 2.6. All code must be recompiled. The calling convention now passes the first three arguments in function calls in registers. Structures are no longer a multiple of 2 bytes. - - <p><hr /> - -<h3 class="heading"><a name="TOC12"></a><a name="hppa_002dhp_002dhpux"></a>hppa*-hp-hpux*</h3> - +</p> +<hr /><a name="hppa_002dhp_002dhpux"></a><a name="hppa_002a_002dhp_002dhpux_002a"></a> +<h3 class="heading">hppa*-hp-hpux*</h3> <p>Support for HP-UX version 9 and older was discontinued in GCC 3.4. - - <p>We require using gas/binutils on all hppa platforms. Version 2.19 or +</p> +<p>We require using gas/binutils on all hppa platforms. Version 2.19 or later is recommended. - - <p>It may be helpful to configure GCC with the -<a href="./configure.html#with-gnu-as"><samp><span class="option">--with-gnu-as</span></samp></a> and -<samp><span class="option">--with-as=...</span></samp> options to ensure that GCC can find GAS. - - <p>The HP assembler should not be used with GCC. It is rarely tested and may -not work. It shouldn't be used with any languages other than C due to its +</p> +<p>It may be helpful to configure GCC with the +<a href="./configure.html#with-gnu-as"><samp>--with-gnu-as</samp></a> and +<samp>--with-as=…</samp> options to ensure that GCC can find GAS. +</p> +<p>The HP assembler should not be used with GCC. It is rarely tested and may +not work. It shouldn’t be used with any languages other than C due to its many limitations. - - <p>Specifically, <samp><span class="option">-g</span></samp> does not work (HP-UX uses a peculiar debugging +</p> +<p>Specifically, <samp>-g</samp> does not work (HP-UX uses a peculiar debugging format which GCC does not know about). It also inserts timestamps into each object file it creates, causing the 3-stage comparison test to fail during a bootstrap. You should be able to continue by saying -‘<samp><span class="samp">make all-host all-target</span></samp>’ after getting the failure from ‘<samp><span class="samp">make</span></samp>’. - - <p>Various GCC features are not supported. For example, it does not support weak +‘<samp>make all-host all-target</samp>’ after getting the failure from ‘<samp>make</samp>’. +</p> +<p>Various GCC features are not supported. For example, it does not support weak symbols or alias definitions. As a result, explicit template instantiations are required when using C++. This makes it difficult if not impossible to build many C++ applications. - - <p>There are two default scheduling models for instructions. These are +</p> +<p>There are two default scheduling models for instructions. These are PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc -architecture specified for the target machine when configuring. +architecture specified for the target machine when configuring. PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when -the target is a ‘<samp><span class="samp">hppa1*</span></samp>’ machine. - - <p>The PROCESSOR_8000 model is not well suited to older processors. Thus, +the target is a ‘<samp>hppa1*</samp>’ machine. +</p> +<p>The PROCESSOR_8000 model is not well suited to older processors. Thus, it is important to completely specify the machine architecture when configuring if you want a model other than PROCESSOR_8000. The macro TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different default scheduling model is desired. - - <p>As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10 -through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later. +</p> +<p>As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10 +through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later. This namespace change might cause problems when bootstrapping with an earlier version of GCC or the HP compiler as essentially the same namespace is required for an entire build. This problem can be avoided -in a number of ways. With HP cc, <samp><span class="env">UNIX_STD</span></samp> can be set to ‘<samp><span class="samp">95</span></samp>’ -or ‘<samp><span class="samp">98</span></samp>’. Another way is to add an appropriate set of predefines -to <samp><span class="env">CC</span></samp>. The description for the <samp><span class="option">munix=</span></samp> option contains +in a number of ways. With HP cc, <code>UNIX_STD</code> can be set to ‘<samp>95</samp>’ +or ‘<samp>98</samp>’. Another way is to add an appropriate set of predefines +to <code>CC</code>. The description for the <samp>munix=</samp> option contains a list of the predefines used with each standard. - - <p>More specific information to ‘<samp><span class="samp">hppa*-hp-hpux*</span></samp>’ targets follows. - - <p><hr /> - -<h3 class="heading"><a name="TOC13"></a><a name="hppa_002dhp_002dhpux10"></a>hppa*-hp-hpux10</h3> - +</p> +<p>More specific information to ‘<samp>hppa*-hp-hpux*</samp>’ targets follows. +</p> +<hr /><a name="hppa_002dhp_002dhpux10"></a><a name="hppa_002a_002dhp_002dhpux10"></a> +<h3 class="heading">hppa*-hp-hpux10</h3> <p>For hpux10.20, we <em>highly</em> recommend you pick up the latest sed patch <code>PHCO_19798</code> from HP. - - <p>The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces are +</p> +<p>The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces are used for one-only code and data. This resolves many of the previous problems in using C++ on this target. However, the ABI is not compatible with the one implemented under HP-UX 11 using secondary definitions. - - <p><hr /> - -<h3 class="heading"><a name="TOC14"></a><a name="hppa_002dhp_002dhpux11"></a>hppa*-hp-hpux11</h3> - +</p> +<hr /><a name="hppa_002dhp_002dhpux11"></a><a name="hppa_002a_002dhp_002dhpux11"></a> +<h3 class="heading">hppa*-hp-hpux11</h3> <p>GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot be used to compile GCC 3.0 and up. - - <p>The libffi and libjava libraries haven't been ported to 64-bit HP-UX and don't build. - - <p>Refer to <a href="binaries.html">binaries</a> for information about obtaining +</p> +<p>The libffi and libjava libraries haven’t been ported to 64-bit HP-UX and don’t build. +</p> +<p>Refer to <a href="binaries.html">binaries</a> for information about obtaining precompiled GCC binaries for HP-UX. Precompiled binaries must be obtained -to build the Ada language as it can't be bootstrapped using C. Ada is +to build the Ada language as it can’t be bootstrapped using C. Ada is only available for the 32-bit PA-RISC runtime. - - <p>Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The -bundled compiler supports only traditional C; you will need either HP's +</p> +<p>Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The +bundled compiler supports only traditional C; you will need either HP’s unbundled compiler, or a binary distribution of GCC. - - <p>It is possible to build GCC 3.3 starting with the bundled HP compiler, +</p> +<p>It is possible to build GCC 3.3 starting with the bundled HP compiler, but the process requires several steps. GCC 3.3 can then be used to build later versions. The fastjar program contains ISO C code and -can't be built with the HP bundled compiler. This problem can be +can’t be built with the HP bundled compiler. This problem can be avoided by not building the Java language. For example, use the -<samp><span class="option">--enable-languages="c,c++,f77,objc"</span></samp> option in your configure +<samp>--enable-languages="c,c++,f77,objc"</samp> option in your configure command. - - <p>There are several possible approaches to building the distribution. +</p> +<p>There are several possible approaches to building the distribution. Binutils can be built first using the HP tools. Then, the GCC distribution can be built. The second approach is to build GCC -first using the HP tools, then build binutils, then rebuild GCC. +first using the HP tools, then build binutils, then rebuild GCC. There have been problems with various binary distributions, so it is best not to start from a binary distribution. - - <p>On 64-bit capable systems, there are two distinct targets. Different +</p> +<p>On 64-bit capable systems, there are two distinct targets. Different installation prefixes must be used if both are to be installed on -the same system. The ‘<samp><span class="samp">hppa[1-2]*-hp-hpux11*</span></samp>’ target generates code -for the 32-bit PA-RISC runtime architecture and uses the HP linker. -The ‘<samp><span class="samp">hppa64-hp-hpux11*</span></samp>’ target generates 64-bit code for the +the same system. The ‘<samp>hppa[1-2]*-hp-hpux11*</samp>’ target generates code +for the 32-bit PA-RISC runtime architecture and uses the HP linker. +The ‘<samp>hppa64-hp-hpux11*</samp>’ target generates 64-bit code for the PA-RISC 2.0 architecture. - - <p>The script config.guess now selects the target type based on the compiler -detected during configuration. You must define <samp><span class="env">PATH</span></samp> or <samp><span class="env">CC</span></samp> so -that configure finds an appropriate compiler for the initial bootstrap. -When <samp><span class="env">CC</span></samp> is used, the definition should contain the options that are -needed whenever <samp><span class="env">CC</span></samp> is used. - - <p>Specifically, options that determine the runtime architecture must be -in <samp><span class="env">CC</span></samp> to correctly select the target for the build. It is also -convenient to place many other compiler options in <samp><span class="env">CC</span></samp>. For example, -<samp><span class="env">CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"</span></samp> +</p> +<p>The script config.guess now selects the target type based on the compiler +detected during configuration. You must define <code>PATH</code> or <code>CC</code> so +that configure finds an appropriate compiler for the initial bootstrap. +When <code>CC</code> is used, the definition should contain the options that are +needed whenever <code>CC</code> is used. +</p> +<p>Specifically, options that determine the runtime architecture must be +in <code>CC</code> to correctly select the target for the build. It is also +convenient to place many other compiler options in <code>CC</code>. For example, +<code>CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"</code> can be used to bootstrap the GCC 3.3 branch with the HP compiler in -64-bit K&R/bundled mode. The <samp><span class="option">+DA2.0W</span></samp> option will result in -the automatic selection of the ‘<samp><span class="samp">hppa64-hp-hpux11*</span></samp>’ target. The +64-bit K&R/bundled mode. The <samp>+DA2.0W</samp> option will result in +the automatic selection of the ‘<samp>hppa64-hp-hpux11*</samp>’ target. The macro definition table of cpp needs to be increased for a successful build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to be defined when building with the bundled compiler, or when using the -<samp><span class="option">-Ac</span></samp> option. These defines aren't necessary with <samp><span class="option">-Ae</span></samp>. - - <p>It is best to explicitly configure the ‘<samp><span class="samp">hppa64-hp-hpux11*</span></samp>’ target -with the <samp><span class="option">--with-ld=...</span></samp> option. This overrides the standard +<samp>-Ac</samp> option. These defines aren’t necessary with <samp>-Ae</samp>. +</p> +<p>It is best to explicitly configure the ‘<samp>hppa64-hp-hpux11*</samp>’ target +with the <samp>--with-ld=…</samp> option. This overrides the standard search for ld. The two linkers supported on this target require different commands. The default linker is determined during configuration. As a -result, it's not possible to switch linkers in the middle of a GCC build. +result, it’s not possible to switch linkers in the middle of a GCC build. This has been reported to sometimes occur in unified builds of binutils and GCC. - - <p>A recent linker patch must be installed for the correct operation of +</p> +<p>A recent linker patch must be installed for the correct operation of GCC 3.3 and later. <code>PHSS_26559</code> and <code>PHSS_24304</code> are the oldest linker patches that are known to work. They are for HP-UX 11.00 and 11.11, respectively. <code>PHSS_24303</code>, the companion to -<code>PHSS_24304</code>, might be usable but it hasn't been tested. These +<code>PHSS_24304</code>, might be usable but it hasn’t been tested. These patches have been superseded. Consult the HP patch database to obtain the currently recommended linker patch for your system. - - <p>The patches are necessary for the support of weak symbols on the +</p> +<p>The patches are necessary for the support of weak symbols on the 32-bit port, and for the running of initializers and finalizers. Weak symbols are implemented using SOM secondary definition symbols. Prior -to HP-UX 11, there are bugs in the linker support for secondary symbols. +to HP-UX 11, there are bugs in the linker support for secondary symbols. The patches correct a problem of linker core dumps creating shared libraries containing secondary symbols, as well as various other linking issues involving secondary symbols. - - <p>GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to +</p> +<p>GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to run initializers and finalizers on the 64-bit port. The 32-bit port -uses the linker <samp><span class="option">+init</span></samp> and <samp><span class="option">+fini</span></samp> options for the same +uses the linker <samp>+init</samp> and <samp>+fini</samp> options for the same purpose. The patches correct various problems with the +init/+fini options, including program core dumps. Binutils 2.14 corrects a -problem on the 64-bit port resulting from HP's non-standard use of +problem on the 64-bit port resulting from HP’s non-standard use of the .init and .fini sections for array initializers and finalizers. - - <p>Although the HP and GNU linkers are both supported for the -‘<samp><span class="samp">hppa64-hp-hpux11*</span></samp>’ target, it is strongly recommended that the +</p> +<p>Although the HP and GNU linkers are both supported for the +‘<samp>hppa64-hp-hpux11*</samp>’ target, it is strongly recommended that the HP linker be used for link editing on this target. - - <p>At this time, the GNU linker does not support the creation of long -branch stubs. As a result, it can't successfully link binaries +</p> +<p>At this time, the GNU linker does not support the creation of long +branch stubs. As a result, it can’t successfully link binaries containing branch offsets larger than 8 megabytes. In addition, there are problems linking shared libraries, linking executables -with <samp><span class="option">-static</span></samp>, and with dwarf2 unwind and exception support. -It also doesn't provide stubs for internal calls to global functions -in shared libraries, so these calls can't be overloaded. - - <p>The HP dynamic loader does not support GNU symbol versioning, so symbol +with <samp>-static</samp>, and with dwarf2 unwind and exception support. +It also doesn’t provide stubs for internal calls to global functions +in shared libraries, so these calls can’t be overloaded. +</p> +<p>The HP dynamic loader does not support GNU symbol versioning, so symbol versioning is not supported. It may be necessary to disable symbol -versioning with <samp><span class="option">--disable-symvers</span></samp> when using GNU ld. - - <p>POSIX threads are the default. The optional DCE thread library is not -supported, so <samp><span class="option">--enable-threads=dce</span></samp> does not work. - - <p><hr /> - -<h3 class="heading"><a name="TOC15"></a><a name="x_002dx_002dlinux_002dgnu"></a>*-*-linux-gnu</h3> - +versioning with <samp>--disable-symvers</samp> when using GNU ld. +</p> +<p>POSIX threads are the default. The optional DCE thread library is not +supported, so <samp>--enable-threads=dce</samp> does not work. +</p> +<hr /><a name="x_002dx_002dlinux_002dgnu"></a><a name="g_t_002a_002d_002a_002dlinux_002dgnu"></a> +<h3 class="heading">*-*-linux-gnu</h3> <p>Versions of libstdc++-v3 starting with 3.2.1 require bug fixes present in glibc 2.2.5 and later. More information is available in the libstdc++-v3 documentation. - - <p><hr /> - -<h3 class="heading"><a name="TOC16"></a><a name="ix86_002dx_002dlinux"></a>i?86-*-linux*</h3> - -<p>As of GCC 3.3, binutils 2.13.1 or later is required for this platform. +</p> +<hr /><a name="ix86_002dx_002dlinux"></a><a name="i_003f86_002d_002a_002dlinux_002a"></a> +<h3 class="heading">i?86-*-linux*</h3> +<p>As of GCC 3.3, binutils 2.13.1 or later is required for this platform. See <a href="http://gcc.gnu.org/PR10877">bug 10877</a> for more information. - - <p>If you receive Signal 11 errors when building on GNU/Linux, then it is +</p> +<p>If you receive Signal 11 errors when building on GNU/Linux, then it is possible you have a hardware problem. Further information on this can be found on <a href="http://www.bitwizard.nl/sig11/">www.bitwizard.nl</a>. - - <p><hr /> - -<h3 class="heading"><a name="TOC17"></a><a name="ix86_002dx_002dsolaris289"></a>i?86-*-solaris2.[89]</h3> - -<p>The Sun assembler in Solaris 8 and 9 has several bugs and limitations. +</p> +<hr /><a name="ix86_002dx_002dsolaris29"></a><a name="i_003f86_002d_002a_002dsolaris2_002e9"></a> +<h3 class="heading">i?86-*-solaris2.9</h3> +<p>The Sun assembler in Solaris 9 has several bugs and limitations. While GCC works around them, several features are missing, so it is -<!-- FIXME: which ones? --> recommended to use the GNU assembler instead. There is no bundled version, but the current version, from GNU binutils 2.22, is known to work. - - <p>Solaris 2/x86 doesn't support the execution of SSE/SSE2 instructions +</p> +<p>Solaris 2/x86 doesn’t support the execution of SSE/SSE2 instructions before Solaris 9 4/04, even if the CPU supports them. Programs will receive <code>SIGILL</code> if they try. The fix is available both in -Solaris 9 Update 6 and kernel patch 112234-12 or newer. There is no -corresponding patch for Solaris 8. To avoid this problem, -<samp><span class="option">-march</span></samp> defaults to ‘<samp><span class="samp">pentiumpro</span></samp>’ on Solaris 8 and 9. If +Solaris 9 Update 6 and kernel patch 112234-12 or newer. To +avoid this problem, +<samp>-march</samp> defaults to ‘<samp>pentiumpro</samp>’ on Solaris 9. If you have the patch installed, you can configure GCC with an appropriate -<samp><span class="option">--with-arch</span></samp> option, but need GNU <samp><span class="command">as</span></samp> for SSE2 support. - - <p><hr /> - -<h3 class="heading"><a name="TOC18"></a><a name="ix86_002dx_002dsolaris210"></a>i?86-*-solaris2.10</h3> - +<samp>--with-arch</samp> option, but need GNU <code>as</code> for SSE2 support. +</p> +<hr /><a name="ix86_002dx_002dsolaris210"></a><a name="i_003f86_002d_002a_002dsolaris2_002e10"></a> +<h3 class="heading">i?86-*-solaris2.10</h3> <p>Use this for Solaris 10 or later on x86 and x86-64 systems. Starting -with GCC 4.7, there is also a 64-bit ‘<samp><span class="samp">amd64-*-solaris2.1[0-9]*</span></samp>’ or -‘<samp><span class="samp">x86_64-*-solaris2.1[0-9]*</span></samp>’ configuration that corresponds to -‘<samp><span class="samp">sparcv9-sun-solaris2*</span></samp>’. - - <p>It is recommended that you configure GCC to use the GNU assembler, in -<samp><span class="file">/usr/sfw/bin/gas</span></samp>. The versions included in Solaris 10, from GNU +with GCC 4.7, there is also a 64-bit ‘<samp>amd64-*-solaris2.1[0-9]*</samp>’ or +‘<samp>x86_64-*-solaris2.1[0-9]*</samp>’ configuration that corresponds to +‘<samp>sparcv9-sun-solaris2*</samp>’. +</p> +<p>It is recommended that you configure GCC to use the GNU assembler, in +<samp>/usr/sfw/bin/gas</samp>. The versions included in Solaris 10, from GNU binutils 2.15, and Solaris 11, from GNU binutils 2.19, work fine, although the current version, from GNU binutils 2.22, is known to work, too. Recent versions of the Sun assembler in -<samp><span class="file">/usr/ccs/bin/as</span></samp> work almost as well, though. -<!-- FIXME: as patch requirements? --> - - <p>For linking, the Sun linker, is preferred. If you want to use the GNU -linker instead, which is available in <samp><span class="file">/usr/sfw/bin/gld</span></samp>, note that +<samp>/usr/ccs/bin/as</samp> work almost as well, though. +</p> +<p>For linking, the Sun linker, is preferred. If you want to use the GNU +linker instead, which is available in <samp>/usr/sfw/bin/gld</samp>, note that due to a packaging bug the version in Solaris 10, from GNU binutils 2.15, cannot be used, while the version in Solaris 11, from GNU binutils 2.19, works, as does the latest version, from GNU binutils 2.22. - - <p>To use GNU <samp><span class="command">as</span></samp>, configure with the options -<samp><span class="option">--with-gnu-as --with-as=/usr/sfw/bin/gas</span></samp>. It may be necessary -to configure with <samp><span class="option">--without-gnu-ld --with-ld=/usr/ccs/bin/ld</span></samp> to -guarantee use of Sun <samp><span class="command">ld</span></samp>. -<!-- FIXME: why -without-gnu-ld -with-ld? --> - - <p><hr /> - -<h3 class="heading"><a name="TOC19"></a><a name="ia64_002dx_002dlinux"></a>ia64-*-linux</h3> - +</p> +<p>To use GNU <code>as</code>, configure with the options +<samp>--with-gnu-as --with-as=/usr/sfw/bin/gas</samp>. It may be necessary +to configure with <samp>--without-gnu-ld --with-ld=/usr/ccs/bin/ld</samp> to +guarantee use of Sun <code>ld</code>. +</p> +<hr /><a name="ia64_002dx_002dlinux"></a><a name="ia64_002d_002a_002dlinux"></a> +<h3 class="heading">ia64-*-linux</h3> <p>IA-64 processor (also known as IPF, or Itanium Processor Family) running GNU/Linux. - - <p>If you are using the installed system libunwind library with -<samp><span class="option">--with-system-libunwind</span></samp>, then you must use libunwind 0.98 or +</p> +<p>If you are using the installed system libunwind library with +<samp>--with-system-libunwind</samp>, then you must use libunwind 0.98 or later. - - <p>None of the following versions of GCC has an ABI that is compatible +</p> +<p>None of the following versions of GCC has an ABI that is compatible with any of the other versions in this list, with the exception that Red Hat 2.96 and Trillian 000171 are compatible with each other: -3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717. -This primarily affects C++ programs and programs that create shared libraries. -GCC 3.1 or later is recommended for compiling linux, the kernel. +3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717. +This primarily affects C++ programs and programs that create shared libraries. +GCC 3.1 or later is recommended for compiling linux, the kernel. As of version 3.1 GCC is believed to be fully ABI compliant, and hence no more major ABI changes are expected. - - <p><hr /> - -<h3 class="heading"><a name="TOC20"></a><a name="ia64_002dx_002dhpux"></a>ia64-*-hpux*</h3> - +</p> +<hr /><a name="ia64_002dx_002dhpux"></a><a name="ia64_002d_002a_002dhpux_002a"></a> +<h3 class="heading">ia64-*-hpux*</h3> <p>Building GCC on this target requires the GNU Assembler. The bundled HP assembler will not work. To prevent GCC from using the wrong assembler, -the option <samp><span class="option">--with-gnu-as</span></samp> may be necessary. - - <p>The GCC libunwind library has not been ported to HPUX. This means that for -GCC versions 3.2.3 and earlier, <samp><span class="option">--enable-libunwind-exceptions</span></samp> -is required to build GCC. For GCC 3.3 and later, this is the default. -For gcc 3.4.3 and later, <samp><span class="option">--enable-libunwind-exceptions</span></samp> is +the option <samp>--with-gnu-as</samp> may be necessary. +</p> +<p>The GCC libunwind library has not been ported to HPUX. This means that for +GCC versions 3.2.3 and earlier, <samp>--enable-libunwind-exceptions</samp> +is required to build GCC. For GCC 3.3 and later, this is the default. +For gcc 3.4.3 and later, <samp>--enable-libunwind-exceptions</samp> is removed and the system libunwind library will always be used. - - <p><hr /> -<!-- rs6000-ibm-aix*, powerpc-ibm-aix* --> - -<h3 class="heading"><a name="TOC21"></a><a name="x_002dibm_002daix"></a>*-ibm-aix*</h3> - -<p>Support for AIX version 3 and older was discontinued in GCC 3.4. +</p> +<hr /><a name="aarch64_002dx_002dx"></a><a name="aarch64_002a_002d_002a_002d_002a"></a> +<h3 class="heading">aarch64*-*-*</h3> +<p>Binutils pre 2.24 does not have support for selecting <samp>-mabi</samp> and +does not support ILP32. If it is used to build GCC 4.9 or later, GCC will +not support option <samp>-mabi=ilp32</samp>. +</p> +<p>To enable a workaround for the Cortex-A53 erratum number 835769 by default +(for all CPUs regardless of -mcpu option given) at configure time use the +<samp>--enable-fix-cortex-a53-835769</samp> option. This will enable the fix by +default and can be explicitly disabled during during compilation by passing the +<samp>-mno-fix-cortex-a53-835769</samp> option. Conversely, +<samp>--disable-fix-cortex-a53-835769</samp> will disable the workaround by +default. The workaround is disabled by default if neither of +<samp>--enable-fix-cortex-a53-835769</samp> or +<samp>--disable-fix-cortex-a53-835769</samp> is given at configure time. +</p> +<hr /> +<!-- rs6000-ibm-aix*, powerpc-ibm-aix* --><a name="x_002dibm_002daix"></a><a name="g_t_002a_002dibm_002daix_002a"></a> +<h3 class="heading">*-ibm-aix*</h3> +<p>Support for AIX version 3 and older was discontinued in GCC 3.4. Support for AIX version 4.2 and older was discontinued in GCC 4.5. - - <p>“out of memory” bootstrap failures may indicate a problem with +</p> +<p>“out of memory” bootstrap failures may indicate a problem with process resource limits (ulimit). Hard limits are configured in the -<samp><span class="file">/etc/security/limits</span></samp> system configuration file. - - <p>GCC can bootstrap with recent versions of IBM XLC, but bootstrapping +<samp>/etc/security/limits</samp> system configuration file. +</p> +<p>GCC can bootstrap with recent versions of IBM XLC, but bootstrapping with an earlier release of GCC is recommended. Bootstrapping with XLC requires a larger data segment, which can be enabled through the <var>LDR_CNTRL</var> environment variable, e.g., - -<pre class="smallexample"> % LDR_CNTRL=MAXDATA=0x50000000 - % export LDR_CNTRL -</pre> - <p>One can start with a pre-compiled version of GCC to build from -sources. One may delete GCC's “fixed” header files when starting +</p> +<div class="smallexample"> +<pre class="smallexample">% LDR_CNTRL=MAXDATA=0x50000000 +% export LDR_CNTRL +</pre></div> + +<p>One can start with a pre-compiled version of GCC to build from +sources. One may delete GCC’s “fixed” header files when starting with a version of GCC built for an earlier release of AIX. - - <p>To speed up the configuration phases of bootstrapping and installing GCC, -one may use GNU Bash instead of AIX <samp><span class="command">/bin/sh</span></samp>, e.g., - -<pre class="smallexample"> % CONFIG_SHELL=/opt/freeware/bin/bash - % export CONFIG_SHELL -</pre> - <p>and then proceed as described in <a href="build.html">the build instructions</a>, where we strongly recommend specifying an absolute path +</p> +<p>To speed up the configuration phases of bootstrapping and installing GCC, +one may use GNU Bash instead of AIX <code>/bin/sh</code>, e.g., +</p> +<div class="smallexample"> +<pre class="smallexample">% CONFIG_SHELL=/opt/freeware/bin/bash +% export CONFIG_SHELL +</pre></div> + +<p>and then proceed as described in <a href="build.html">the build +instructions</a>, where we strongly recommend specifying an absolute path to invoke <var>srcdir</var>/configure. - - <p>Because GCC on AIX is built as a 32-bit executable by default, +</p> +<p>Because GCC on AIX is built as a 32-bit executable by default, (although it can generate 64-bit programs) the GMP and MPFR libraries required by gfortran must be 32-bit libraries. Building GMP and MPFR as static archive libraries works better than shared libraries. - - <p>Errors involving <code>alloca</code> when building GCC generally are due +</p> +<p>Errors involving <code>alloca</code> when building GCC generally are due to an incorrect definition of <code>CC</code> in the Makefile or mixing files compiled with the native C compiler and GCC. During the stage1 phase of -the build, the native AIX compiler <strong>must</strong> be invoked as <samp><span class="command">cc</span></samp> -(not <samp><span class="command">xlc</span></samp>). Once <samp><span class="command">configure</span></samp> has been informed of -<samp><span class="command">xlc</span></samp>, one needs to use ‘<samp><span class="samp">make distclean</span></samp>’ to remove the -configure cache files and ensure that <samp><span class="env">CC</span></samp> environment variable -does not provide a definition that will confuse <samp><span class="command">configure</span></samp>. +the build, the native AIX compiler <strong>must</strong> be invoked as <code>cc</code> +(not <code>xlc</code>). Once <code>configure</code> has been informed of +<code>xlc</code>, one needs to use ‘<samp>make distclean</samp>’ to remove the +configure cache files and ensure that <code>CC</code> environment variable +does not provide a definition that will confuse <code>configure</code>. If this error occurs during stage2 or later, then the problem most likely is the version of Make (see above). - - <p>The native <samp><span class="command">as</span></samp> and <samp><span class="command">ld</span></samp> are recommended for bootstrapping -on AIX. The GNU Assembler, GNU Linker, and GNU Binutils version 2.20 -is required to bootstrap on AIX 5. The native AIX tools do -interoperate with GCC. - - <p>AIX 5.3 TL10, AIX 6.1 TL05 and AIX 7.1 TL00 introduced an AIX +</p> +<p>The native <code>as</code> and <code>ld</code> are recommended for +bootstrapping on AIX. The GNU Assembler, GNU Linker, and GNU +Binutils version 2.20 is the minimum level that supports bootstrap on +AIX 5. The GNU Assembler has not been updated to support AIX 6 or +AIX 7. The native AIX tools do interoperate with GCC. +</p> +<p>AIX 5.3 TL10, AIX 6.1 TL05 and AIX 7.1 TL00 introduced an AIX assembler change that sometimes produces corrupt assembly files causing AIX linker errors. The bug breaks GCC bootstrap on AIX and can cause compilation failures with existing GCC installations. An AIX iFix for AIX 5.3 is available (APAR IZ98385 for AIX 5.3 TL10, APAR -IZ98477 for AIX 5.3 TL11 and IZ98134 for AIX 5.3 TL12). Fixes for AIX -6.1 (APAR IZ98732 for AIX 6.1 TL05 and APAR IZ98861 for AIX 6.1 TL06) -and AIX 7.1 are in verification and packaging phases. - - <p>Building <samp><span class="file">libstdc++.a</span></samp> requires a fix for an AIX Assembler bug +IZ98477 for AIX 5.3 TL11 and IZ98134 for AIX 5.3 TL12). AIX 5.3 TL11 SP8, +AIX 5.3 TL12 SP5, AIX 6.1 TL04 SP11, AIX 6.1 TL05 SP7, AIX 6.1 TL06 SP6, +AIX 6.1 TL07 and AIX 7.1 TL01 should include the fix. +</p> +<p>Building <samp>libstdc++.a</samp> requires a fix for an AIX Assembler bug APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a fix for another AIX Assembler bug and a co-dependent AIX Archiver fix referenced as APAR IY53606 (AIX 5.2) or as APAR IY54774 (AIX 5.1) - - <p>‘<samp><span class="samp">libstdc++</span></samp>’ in GCC 3.4 increments the major version number of the -shared object and GCC installation places the <samp><span class="file">libstdc++.a</span></samp> +</p> +<p>‘<samp>libstdc++</samp>’ in GCC 3.4 increments the major version number of the +shared object and GCC installation places the <samp>libstdc++.a</samp> shared library in a common location which will overwrite the and GCC 3.3 version of the shared library. Applications either need to be re-linked against the new shared library or the GCC 3.1 and GCC 3.3 -versions of the ‘<samp><span class="samp">libstdc++</span></samp>’ shared object needs to be available -to the AIX runtime loader. The GCC 3.1 ‘<samp><span class="samp">libstdc++.so.4</span></samp>’, if -present, and GCC 3.3 ‘<samp><span class="samp">libstdc++.so.5</span></samp>’ shared objects can be +versions of the ‘<samp>libstdc++</samp>’ shared object needs to be available +to the AIX runtime loader. The GCC 3.1 ‘<samp>libstdc++.so.4</samp>’, if +present, and GCC 3.3 ‘<samp>libstdc++.so.5</samp>’ shared objects can be installed for runtime dynamic loading using the following steps to set -the ‘<samp><span class="samp">F_LOADONLY</span></samp>’ flag in the shared object for <em>each</em> -multilib <samp><span class="file">libstdc++.a</span></samp> installed: - - <p>Extract the shared objects from the currently installed -<samp><span class="file">libstdc++.a</span></samp> archive: -<pre class="smallexample"> % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5 -</pre> - <p>Enable the ‘<samp><span class="samp">F_LOADONLY</span></samp>’ flag so that the shared object will be +the ‘<samp>F_LOADONLY</samp>’ flag in the shared object for <em>each</em> +multilib <samp>libstdc++.a</samp> installed: +</p> +<p>Extract the shared objects from the currently installed +<samp>libstdc++.a</samp> archive: +</p><div class="smallexample"> +<pre class="smallexample">% ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5 +</pre></div> + +<p>Enable the ‘<samp>F_LOADONLY</samp>’ flag so that the shared object will be available for runtime dynamic loading, but not linking: -<pre class="smallexample"> % strip -e libstdc++.so.4 libstdc++.so.5 -</pre> - <p>Archive the runtime-only shared object in the GCC 3.4 -<samp><span class="file">libstdc++.a</span></samp> archive: -<pre class="smallexample"> % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5 -</pre> - <p>Linking executables and shared libraries may produce warnings of +</p><div class="smallexample"> +<pre class="smallexample">% strip -e libstdc++.so.4 libstdc++.so.5 +</pre></div> + +<p>Archive the runtime-only shared object in the GCC 3.4 +<samp>libstdc++.a</samp> archive: +</p><div class="smallexample"> +<pre class="smallexample">% ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5 +</pre></div> + +<p>Linking executables and shared libraries may produce warnings of duplicate symbols. The assembly files generated by GCC for AIX always have included multiple symbol definitions for certain global variable and function declarations in the original program. The warnings should not prevent the linker from producing a correct library or runnable executable. - - <p>AIX 4.3 utilizes a “large format” archive to support both 32-bit and +</p> +<p>AIX 4.3 utilizes a “large format” archive to support both 32-bit and 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1 -to parse archive libraries did not handle the new format correctly. +to parse archive libraries did not handle the new format correctly. These routines are used by GCC and result in error messages during linking such as “not a COFF file”. The version of the routines shipped -with AIX 4.3.1 should work for a 32-bit environment. The <samp><span class="option">-g</span></samp> +with AIX 4.3.1 should work for a 32-bit environment. The <samp>-g</samp> option of the archive command may be used to create archives of 32-bit objects using the original “small format”. A correct version of the routines is shipped with AIX 4.3.2 and above. - - <p>Some versions of the AIX binder (linker) can fail with a relocation -overflow severe error when the <samp><span class="option">-bbigtoc</span></samp> option is used to link +</p> +<p>Some versions of the AIX binder (linker) can fail with a relocation +overflow severe error when the <samp>-bbigtoc</samp> option is used to link GCC-produced object files into an executable that overflows the TOC. A fix for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is available from IBM Customer Support and from its <a href="http://techsupport.services.ibm.com/">techsupport.services.ibm.com</a> website as PTF U455193. - - <p>The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core +</p> +<p>The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core with a segmentation fault when invoked by any version of GCC. A fix for APAR IX87327 is available from IBM Customer Support and from its <a href="http://techsupport.services.ibm.com/">techsupport.services.ibm.com</a> website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above. - - <p>The initial assembler shipped with AIX 4.3.0 generates incorrect object +</p> +<p>The initial assembler shipped with AIX 4.3.0 generates incorrect object files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS TO ASSEMBLE/BIND) is available from IBM Customer Support and from its <a href="http://techsupport.services.ibm.com/">techsupport.services.ibm.com</a> website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above. - - <p>AIX provides National Language Support (NLS). Compilers and assemblers +</p> +<p>AIX provides National Language Support (NLS). Compilers and assemblers use NLS to support locale-specific representations of various data -formats including floating-point numbers (e.g., ‘<samp><span class="samp">.</span></samp>’ vs ‘<samp><span class="samp">,</span></samp>’ for +formats including floating-point numbers (e.g., ‘<samp>.</samp>’ vs ‘<samp>,</samp>’ for separating decimal fractions). There have been problems reported where GCC does not produce the same floating-point formats that the assembler -expects. If one encounters this problem, set the <samp><span class="env">LANG</span></samp> -environment variable to ‘<samp><span class="samp">C</span></samp>’ or ‘<samp><span class="samp">En_US</span></samp>’. - - <p>A default can be specified with the <samp><span class="option">-mcpu=</span><var>cpu_type</var></samp> -switch and using the configure option <samp><span class="option">--with-cpu-</span><var>cpu_type</var></samp>. - - <p><hr /> - -<h3 class="heading"><a name="TOC22"></a><a name="iq2000_002dx_002delf"></a>iq2000-*-elf</h3> - +expects. If one encounters this problem, set the <code>LANG</code> +environment variable to ‘<samp>C</samp>’ or ‘<samp>En_US</samp>’. +</p> +<p>A default can be specified with the <samp>-mcpu=<var>cpu_type</var></samp> +switch and using the configure option <samp>--with-cpu-<var>cpu_type</var></samp>. +</p> +<hr /><a name="iq2000_002dx_002delf"></a><a name="iq2000_002d_002a_002delf"></a> +<h3 class="heading">iq2000-*-elf</h3> <p>Vitesse IQ2000 processors. These are used in embedded applications. There are no standard Unix configurations. - - <p><hr /> - -<h3 class="heading"><a name="TOC23"></a><a name="lm32_002dx_002delf"></a>lm32-*-elf</h3> - -<p>Lattice Mico32 processor. +</p> +<hr /><a name="lm32_002dx_002delf"></a><a name="lm32_002d_002a_002delf"></a> +<h3 class="heading">lm32-*-elf</h3> +<p>Lattice Mico32 processor. This configuration is intended for embedded systems. - - <p><hr /> - -<h3 class="heading"><a name="TOC24"></a><a name="lm32_002dx_002duclinux"></a>lm32-*-uclinux</h3> - -<p>Lattice Mico32 processor. +</p> +<hr /><a name="lm32_002dx_002duclinux"></a><a name="lm32_002d_002a_002duclinux"></a> +<h3 class="heading">lm32-*-uclinux</h3> +<p>Lattice Mico32 processor. This configuration is intended for embedded systems running uClinux. - - <p><hr /> - -<h3 class="heading"><a name="TOC25"></a><a name="m32c_002dx_002delf"></a>m32c-*-elf</h3> - -<p>Renesas M32C processor. +</p> +<hr /><a name="m32c_002dx_002delf"></a><a name="m32c_002d_002a_002delf"></a> +<h3 class="heading">m32c-*-elf</h3> +<p>Renesas M32C processor. This configuration is intended for embedded systems. - - <p><hr /> - -<h3 class="heading"><a name="TOC26"></a><a name="m32r_002dx_002delf"></a>m32r-*-elf</h3> - -<p>Renesas M32R processor. +</p> +<hr /><a name="m32r_002dx_002delf"></a><a name="m32r_002d_002a_002delf"></a> +<h3 class="heading">m32r-*-elf</h3> +<p>Renesas M32R processor. This configuration is intended for embedded systems. - - <p><hr /> - -<h3 class="heading"><a name="TOC27"></a><a name="m68k_002dx_002dx"></a>m68k-*-*</h3> - +</p> +<hr /><a name="m68k_002dx_002dx"></a><a name="m68k_002d_002a_002d_002a"></a> +<h3 class="heading">m68k-*-*</h3> <p>By default, -‘<samp><span class="samp">m68k-*-elf*</span></samp>’, ‘<samp><span class="samp">m68k-*-rtems</span></samp>’, ‘<samp><span class="samp">m68k-*-uclinux</span></samp>’ and -‘<samp><span class="samp">m68k-*-linux</span></samp>’ +‘<samp>m68k-*-elf*</samp>’, ‘<samp>m68k-*-rtems</samp>’, ‘<samp>m68k-*-uclinux</samp>’ and +‘<samp>m68k-*-linux</samp>’ build libraries for both M680x0 and ColdFire processors. If you only need the M680x0 libraries, you can omit the ColdFire ones by passing -<samp><span class="option">--with-arch=m68k</span></samp> to <samp><span class="command">configure</span></samp>. Alternatively, you -can omit the M680x0 libraries by passing <samp><span class="option">--with-arch=cf</span></samp> to -<samp><span class="command">configure</span></samp>. These targets default to 5206 or 5475 code as +<samp>--with-arch=m68k</samp> to <code>configure</code>. Alternatively, you +can omit the M680x0 libraries by passing <samp>--with-arch=cf</samp> to +<code>configure</code>. These targets default to 5206 or 5475 code as appropriate for the target system when -configured with <samp><span class="option">--with-arch=cf</span></samp> and 68020 code otherwise. - - <p>The ‘<samp><span class="samp">m68k-*-netbsd</span></samp>’ and -‘<samp><span class="samp">m68k-*-openbsd</span></samp>’ targets also support the <samp><span class="option">--with-arch</span></samp> +configured with <samp>--with-arch=cf</samp> and 68020 code otherwise. +</p> +<p>The ‘<samp>m68k-*-netbsd</samp>’ and +‘<samp>m68k-*-openbsd</samp>’ targets also support the <samp>--with-arch</samp> option. They will generate ColdFire CFV4e code when configured with -<samp><span class="option">--with-arch=cf</span></samp> and 68020 code otherwise. - - <p>You can override the default processors listed above by configuring -with <samp><span class="option">--with-cpu=</span><var>target</var></samp>. This <var>target</var> can either -be a <samp><span class="option">-mcpu</span></samp> argument or one of the following values: -‘<samp><span class="samp">m68000</span></samp>’, ‘<samp><span class="samp">m68010</span></samp>’, ‘<samp><span class="samp">m68020</span></samp>’, ‘<samp><span class="samp">m68030</span></samp>’, -‘<samp><span class="samp">m68040</span></samp>’, ‘<samp><span class="samp">m68060</span></samp>’, ‘<samp><span class="samp">m68020-40</span></samp>’ and ‘<samp><span class="samp">m68020-60</span></samp>’. - - <p>GCC requires at least binutils version 2.17 on these targets. - - <p><hr /> - -<h3 class="heading"><a name="TOC28"></a><a name="m68k_002dx_002duclinux"></a>m68k-*-uclinux</h3> - +<samp>--with-arch=cf</samp> and 68020 code otherwise. +</p> +<p>You can override the default processors listed above by configuring +with <samp>--with-cpu=<var>target</var></samp>. This <var>target</var> can either +be a <samp>-mcpu</samp> argument or one of the following values: +‘<samp>m68000</samp>’, ‘<samp>m68010</samp>’, ‘<samp>m68020</samp>’, ‘<samp>m68030</samp>’, +‘<samp>m68040</samp>’, ‘<samp>m68060</samp>’, ‘<samp>m68020-40</samp>’ and ‘<samp>m68020-60</samp>’. +</p> +<p>GCC requires at least binutils version 2.17 on these targets. +</p> +<hr /><a name="m68k_002dx_002duclinux"></a><a name="m68k_002d_002a_002duclinux"></a> +<h3 class="heading">m68k-*-uclinux</h3> <p>GCC 4.3 changed the uClinux configuration so that it uses the -‘<samp><span class="samp">m68k-linux-gnu</span></samp>’ ABI rather than the ‘<samp><span class="samp">m68k-elf</span></samp>’ ABI. +‘<samp>m68k-linux-gnu</samp>’ ABI rather than the ‘<samp>m68k-elf</samp>’ ABI. It also added improved support for C++ and flat shared libraries, both of which were ABI changes. - - <p><hr /> - -<h3 class="heading"><a name="TOC29"></a><a name="mep_002dx_002delf"></a>mep-*-elf</h3> - -<p>Toshiba Media embedded Processor. +</p> +<hr /><a name="mep_002dx_002delf"></a><a name="mep_002d_002a_002delf"></a> +<h3 class="heading">mep-*-elf</h3> +<p>Toshiba Media embedded Processor. This configuration is intended for embedded systems. - - <p><hr /> - -<h3 class="heading"><a name="TOC30"></a><a name="microblaze_002dx_002delf"></a>microblaze-*-elf</h3> - -<p>Xilinx MicroBlaze processor. +</p> +<hr /><a name="microblaze_002dx_002delf"></a><a name="microblaze_002d_002a_002delf"></a> +<h3 class="heading">microblaze-*-elf</h3> +<p>Xilinx MicroBlaze processor. This configuration is intended for embedded systems. - - <p><hr /> - -<h3 class="heading"><a name="TOC31"></a><a name="mips_002dx_002dx"></a>mips-*-*</h3> - +</p> +<hr /><a name="mips_002dx_002dx"></a><a name="mips_002d_002a_002d_002a"></a> +<h3 class="heading">mips-*-*</h3> <p>If on a MIPS system you get an error message saying “does not have gp -sections for all it's [sic] sectons [sic]”, don't worry about it. This +sections for all it’s [sic] sectons [sic]”, don’t worry about it. This happens whenever you use GAS with the MIPS linker, but there is not really anything wrong, and it is okay to use the output file. You can stop such warnings by installing the GNU linker. - - <p>It would be nice to extend GAS to produce the gp tables, but they are +</p> +<p>It would be nice to extend GAS to produce the gp tables, but they are optional, and there should not be a warning about their absence. - - <p>The libstdc++ atomic locking routines for MIPS targets requires MIPS II +</p> +<p>The libstdc++ atomic locking routines for MIPS targets requires MIPS II and later. A patch went in just after the GCC 3.3 release to -make ‘<samp><span class="samp">mips*-*-*</span></samp>’ use the generic implementation instead. You can also -configure for ‘<samp><span class="samp">mipsel-elf</span></samp>’ as a workaround. The -‘<samp><span class="samp">mips*-*-linux*</span></samp>’ target continues to use the MIPS II routines. More +make ‘<samp>mips*-*-*</samp>’ use the generic implementation instead. You can also +configure for ‘<samp>mipsel-elf</samp>’ as a workaround. The +‘<samp>mips*-*-linux*</samp>’ target continues to use the MIPS II routines. More work on this is expected in future releases. +</p> -<!-- If you make -with-llsc the default for another target, please also --> -<!-- update the description of the -with-llsc option. --> - <p>The built-in <code>__sync_*</code> functions are available on MIPS II and -later systems and others that support the ‘<samp><span class="samp">ll</span></samp>’, ‘<samp><span class="samp">sc</span></samp>’ and -‘<samp><span class="samp">sync</span></samp>’ instructions. This can be overridden by passing -<samp><span class="option">--with-llsc</span></samp> or <samp><span class="option">--without-llsc</span></samp> when configuring GCC. +<p>The built-in <code>__sync_*</code> functions are available on MIPS II and +later systems and others that support the ‘<samp>ll</samp>’, ‘<samp>sc</samp>’ and +‘<samp>sync</samp>’ instructions. This can be overridden by passing +<samp>--with-llsc</samp> or <samp>--without-llsc</samp> when configuring GCC. Since the Linux kernel emulates these instructions if they are -missing, the default for ‘<samp><span class="samp">mips*-*-linux*</span></samp>’ targets is -<samp><span class="option">--with-llsc</span></samp>. The <samp><span class="option">--with-llsc</span></samp> and -<samp><span class="option">--without-llsc</span></samp> configure options may be overridden at compile -time by passing the <samp><span class="option">-mllsc</span></samp> or <samp><span class="option">-mno-llsc</span></samp> options to +missing, the default for ‘<samp>mips*-*-linux*</samp>’ targets is +<samp>--with-llsc</samp>. The <samp>--with-llsc</samp> and +<samp>--without-llsc</samp> configure options may be overridden at compile +time by passing the <samp>-mllsc</samp> or <samp>-mno-llsc</samp> options to the compiler. - - <p>MIPS systems check for division by zero (unless -<samp><span class="option">-mno-check-zero-division</span></samp> is passed to the compiler) by +</p> +<p>MIPS systems check for division by zero (unless +<samp>-mno-check-zero-division</samp> is passed to the compiler) by generating either a conditional trap or a break instruction. Using trap results in smaller code, but is only supported on MIPS II and later. Also, some versions of the Linux kernel have a bug that prevents trap from generating the proper signal (<code>SIGFPE</code>). To enable -the use of break, use the <samp><span class="option">--with-divide=breaks</span></samp> -<samp><span class="command">configure</span></samp> option when configuring GCC. The default is to +the use of break, use the <samp>--with-divide=breaks</samp> +<code>configure</code> option when configuring GCC. The default is to use traps on systems that support them. - - <p>The assembler from GNU binutils 2.17 and earlier has a bug in the way +</p> +<p>The assembler from GNU binutils 2.17 and earlier has a bug in the way it sorts relocations for REL targets (o32, o64, EABI). This can cause bad code to be generated for simple C++ programs. Also the linker from GNU binutils versions prior to 2.17 has a bug which causes the -runtime linker stubs in very large programs, like <samp><span class="file">libgcj.so</span></samp>, to +runtime linker stubs in very large programs, like <samp>libgcj.so</samp>, to be incorrectly generated. GNU Binutils 2.18 and later (and snapshots made after Nov. 9, 2006) should be free from both of these problems. - - <p><hr /> - -<h3 class="heading"><a name="TOC32"></a><a name="mips_002dsgi_002dirix5"></a>mips-sgi-irix5</h3> - +</p> +<hr /><a name="mips_002dsgi_002dirix5"></a><a name="mips_002dsgi_002dirix5-1"></a> +<h3 class="heading">mips-sgi-irix5</h3> <p>Support for IRIX 5 has been removed in GCC 4.6. - - <p><hr /> - -<h3 class="heading"><a name="TOC33"></a><a name="mips_002dsgi_002dirix6"></a>mips-sgi-irix6</h3> - -<p>Support for IRIX 6.5 has been obsoleted in GCC 4.7, but can still be -enabled by configuring with <samp><span class="option">--enable-obsolete</span></samp>. Support will be -removed in GCC 4.8. Support for IRIX 6 releases before 6.5 has been -removed in GCC 4.6, as well as support for the O32 ABI. It is -<em>strongly</em> recommended to upgrade to at least IRIX 6.5.18. This -release introduced full ISO C99 support, though for the N32 and N64 ABIs -only. - - <p>To build and use GCC on IRIX 6.5, you need the IRIX Development Foundation -(IDF) and IRIX Development Libraries (IDL). They are included with the -IRIX 6.5 media. - - <p>If you are using SGI's MIPSpro <samp><span class="command">cc</span></samp> as your bootstrap compiler, you must -ensure that the N32 ABI is in use. To test this, compile a simple C -file with <samp><span class="command">cc</span></samp> and then run <samp><span class="command">file</span></samp> on the -resulting object file. The output should look like: - -<pre class="smallexample"> test.o: ELF N32 MSB ... -</pre> - <p class="noindent">If you see: - -<pre class="smallexample"> test.o: ELF 32-bit MSB ... -</pre> - <p class="noindent">or - -<pre class="smallexample"> test.o: ELF 64-bit MSB ... -</pre> - <p class="noindent">then your version of <samp><span class="command">cc</span></samp> uses the O32 or N64 ABI by default. You -should set the environment variable <samp><span class="env">CC</span></samp> to ‘<samp><span class="samp">cc -n32</span></samp>’ -before configuring GCC. - - <p>If you want the resulting <samp><span class="command">gcc</span></samp> to run on old 32-bit systems -with the MIPS R4400 CPU, you need to ensure that only code for the ‘<samp><span class="samp">mips3</span></samp>’ -instruction set architecture (ISA) is generated. While GCC 3.x does -this correctly, both GCC 2.95 and SGI's MIPSpro <samp><span class="command">cc</span></samp> may change -the ISA depending on the machine where GCC is built. Using one of them -as the bootstrap compiler may result in ‘<samp><span class="samp">mips4</span></samp>’ code, which won't run at -all on ‘<samp><span class="samp">mips3</span></samp>’-only systems. For the test program above, you should see: - -<pre class="smallexample"> test.o: ELF N32 MSB mips-3 ... -</pre> - <p class="noindent">If you get: - -<pre class="smallexample"> test.o: ELF N32 MSB mips-4 ... -</pre> - <p class="noindent">instead, you should set the environment variable <samp><span class="env">CC</span></samp> to ‘<samp><span class="samp">cc --n32 -mips3</span></samp>’ or ‘<samp><span class="samp">gcc -mips3</span></samp>’ respectively before configuring GCC. - - <p>MIPSpro C 7.4 may cause bootstrap failures, due to a bug when inlining -<code>memcmp</code>. Either add <code>-U__INLINE_INTRINSICS</code> to the <samp><span class="env">CC</span></samp> -environment variable as a workaround or upgrade to MIPSpro C 7.4.1m. - - <p>GCC on IRIX 6.5 is usually built to support the N32 and N64 ABIs. If -you build GCC on a system that doesn't have the N64 libraries installed -or cannot run 64-bit binaries, -you need to configure with <samp><span class="option">--disable-multilib</span></samp> so GCC doesn't -try to use them. -Look for <samp><span class="file">/usr/lib64/libc.so.1</span></samp> to see if you -have the 64-bit libraries installed. - - <p>GCC must be configured with GNU <samp><span class="command">as</span></samp>. The latest version, from GNU -binutils 2.22, is known to work. On the other hand, bootstrap fails -with GNU <samp><span class="command">ld</span></samp> at least since GNU binutils 2.17. - - <p>The <samp><span class="option">--enable-libgcj</span></samp> -option is disabled by default: IRIX 6 uses a very low default limit -(20480) for the command line length. Although <samp><span class="command">libtool</span></samp> contains a -workaround for this problem, at least the N64 ‘<samp><span class="samp">libgcj</span></samp>’ is known not -to build despite this, running into an internal error of the native -<samp><span class="command">ld</span></samp>. A sure fix is to increase this limit (‘<samp><span class="samp">ncargs</span></samp>’) to -its maximum of 262144 bytes. If you have root access, you can use the -<samp><span class="command">systune</span></samp> command to do this. -<!-- FIXME: does this work with current libtool? --> - - <p><code>wchar_t</code> support in ‘<samp><span class="samp">libstdc++</span></samp>’ is not available for old -IRIX 6.5.x releases, x < 19. The problem cannot be autodetected -and in order to build GCC for such targets you need to configure with -<samp><span class="option">--disable-wchar_t</span></samp>. - - <p><hr /> - -<h3 class="heading"><a name="TOC34"></a><a name="moxie_002dx_002delf"></a>moxie-*-elf</h3> - -<p>The moxie processor. See <a href="http://moxielogic.org/">http://moxielogic.org/</a> for more -information about this processor. - - <p><hr /> - -<h3 class="heading"><a name="TOC35"></a><a name="powerpc_002dx_002dx"></a>powerpc-*-*</h3> - -<p>You can specify a default version for the <samp><span class="option">-mcpu=</span><var>cpu_type</var></samp> -switch by using the configure option <samp><span class="option">--with-cpu-</span><var>cpu_type</var></samp>. - - <p>You will need +</p> +<hr /><a name="mips_002dsgi_002dirix6"></a><a name="mips_002dsgi_002dirix6-1"></a> +<h3 class="heading">mips-sgi-irix6</h3> +<p>Support for IRIX 6.5 has been removed in GCC 4.8. Support for IRIX 6 +releases before 6.5 has been removed in GCC 4.6, as well as support for +the O32 ABI. +</p> +<hr /><a name="moxie_002dx_002delf"></a><a name="moxie_002d_002a_002delf"></a> +<h3 class="heading">moxie-*-elf</h3> +<p>The moxie processor. +</p> +<hr /><a name="msp430_002dx_002delf"></a><a name="msp430_002d_002a_002delf"></a> +<h3 class="heading">msp430-*-elf</h3> +<p>TI MSP430 processor. +This configuration is intended for embedded systems. +</p> +<hr /><a name="nds32le_002dx_002delf"></a><a name="nds32le_002d_002a_002delf"></a> +<h3 class="heading">nds32le-*-elf</h3> +<p>Andes NDS32 target in little endian mode. +</p> +<hr /><a name="nds32be_002dx_002delf"></a><a name="nds32be_002d_002a_002delf"></a> +<h3 class="heading">nds32be-*-elf</h3> +<p>Andes NDS32 target in big endian mode. +</p> +<hr /><a name="powerpc_002dx_002dx"></a><a name="powerpc_002d_002a_002d_002a"></a> +<h3 class="heading">powerpc-*-*</h3> +<p>You can specify a default version for the <samp>-mcpu=<var>cpu_type</var></samp> +switch by using the configure option <samp>--with-cpu-<var>cpu_type</var></samp>. +</p> +<p>You will need <a href="ftp://ftp.kernel.org/pub/linux/devel/binutils">binutils 2.15</a> or newer for a working GCC. - - <p><hr /> - -<h3 class="heading"><a name="TOC36"></a><a name="powerpc_002dx_002ddarwin"></a>powerpc-*-darwin*</h3> - +</p> +<hr /><a name="powerpc_002dx_002ddarwin"></a><a name="powerpc_002d_002a_002ddarwin_002a"></a> +<h3 class="heading">powerpc-*-darwin*</h3> <p>PowerPC running Darwin (Mac OS X kernel). - - <p>Pre-installed versions of Mac OS X may not include any developer tools, +</p> +<p>Pre-installed versions of Mac OS X may not include any developer tools, meaning that you will not be able to build GCC from source. Tool binaries are available at <a href="http://opensource.apple.com/">http://opensource.apple.com/</a>. - - <p>This version of GCC requires at least cctools-590.36. The +</p> +<p>This version of GCC requires at least cctools-590.36. The cctools-590.36 package referenced from <a href="http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html">http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html</a> will not work on systems older than 10.3.9 (aka darwin7.9.0). - - <p><hr /> - -<h3 class="heading"><a name="TOC37"></a><a name="powerpc_002dx_002delf"></a>powerpc-*-elf</h3> - +</p> +<hr /><a name="powerpc_002dx_002delf"></a><a name="powerpc_002d_002a_002delf"></a> +<h3 class="heading">powerpc-*-elf</h3> <p>PowerPC system in big endian mode, running System V.4. - - <p><hr /> - -<h3 class="heading"><a name="TOC38"></a><a name="powerpc_002dx_002dlinux_002dgnu"></a>powerpc*-*-linux-gnu*</h3> - +</p> +<hr /><a name="powerpc_002dx_002dlinux_002dgnu"></a><a name="powerpc_002a_002d_002a_002dlinux_002dgnu_002a"></a> +<h3 class="heading">powerpc*-*-linux-gnu*</h3> <p>PowerPC system in big endian mode running Linux. - - <p><hr /> - -<h3 class="heading"><a name="TOC39"></a><a name="powerpc_002dx_002dnetbsd"></a>powerpc-*-netbsd*</h3> - +</p> +<hr /><a name="powerpc_002dx_002dnetbsd"></a><a name="powerpc_002d_002a_002dnetbsd_002a"></a> +<h3 class="heading">powerpc-*-netbsd*</h3> <p>PowerPC system in big endian mode running NetBSD. - - <p><hr /> - -<h3 class="heading"><a name="TOC40"></a><a name="powerpc_002dx_002deabisim"></a>powerpc-*-eabisim</h3> - +</p> +<hr /><a name="powerpc_002dx_002deabisim"></a><a name="powerpc_002d_002a_002deabisim"></a> +<h3 class="heading">powerpc-*-eabisim</h3> <p>Embedded PowerPC system in big endian mode for use in running under the PSIM simulator. - - <p><hr /> - -<h3 class="heading"><a name="TOC41"></a><a name="powerpc_002dx_002deabi"></a>powerpc-*-eabi</h3> - +</p> +<hr /><a name="powerpc_002dx_002deabi"></a><a name="powerpc_002d_002a_002deabi"></a> +<h3 class="heading">powerpc-*-eabi</h3> <p>Embedded PowerPC system in big endian mode. - - <p><hr /> - -<h3 class="heading"><a name="TOC42"></a><a name="powerpcle_002dx_002delf"></a>powerpcle-*-elf</h3> - +</p> +<hr /><a name="powerpcle_002dx_002delf"></a><a name="powerpcle_002d_002a_002delf"></a> +<h3 class="heading">powerpcle-*-elf</h3> <p>PowerPC system in little endian mode, running System V.4. - - <p><hr /> - -<h3 class="heading"><a name="TOC43"></a><a name="powerpcle_002dx_002deabisim"></a>powerpcle-*-eabisim</h3> - +</p> +<hr /><a name="powerpcle_002dx_002deabisim"></a><a name="powerpcle_002d_002a_002deabisim"></a> +<h3 class="heading">powerpcle-*-eabisim</h3> <p>Embedded PowerPC system in little endian mode for use in running under the PSIM simulator. - - <p><hr /> - -<h3 class="heading"><a name="TOC44"></a><a name="powerpcle_002dx_002deabi"></a>powerpcle-*-eabi</h3> - +</p> +<hr /><a name="powerpcle_002dx_002deabi"></a><a name="powerpcle_002d_002a_002deabi"></a> +<h3 class="heading">powerpcle-*-eabi</h3> <p>Embedded PowerPC system in little endian mode. - - <p><hr /> - -<h3 class="heading"><a name="TOC45"></a><a name="rl78_002dx_002delf"></a>rl78-*-elf</h3> - -<p>The Renesas RL78 processor. +</p> +<hr /><a name="rl78_002dx_002delf"></a><a name="rl78_002d_002a_002delf"></a> +<h3 class="heading">rl78-*-elf</h3> +<p>The Renesas RL78 processor. This configuration is intended for embedded systems. - - <p><hr /> - -<h3 class="heading"><a name="TOC46"></a><a name="rx_002dx_002delf"></a>rx-*-elf</h3> - +</p> +<hr /><a name="rx_002dx_002delf"></a><a name="rx_002d_002a_002delf"></a> +<h3 class="heading">rx-*-elf</h3> <p>The Renesas RX processor. See <a href="http://eu.renesas.com/fmwk.jsp?cnt=rx600_series_landing.jsp&fp=/products/mpumcu/rx_family/rx600_series">http://eu.renesas.com/fmwk.jsp?cnt=rx600_series_landing.jsp&fp=/products/mpumcu/rx_family/rx600_series</a> for more information about this processor. - - <p><hr /> - -<h3 class="heading"><a name="TOC47"></a><a name="s390_002dx_002dlinux"></a>s390-*-linux*</h3> - +</p> +<hr /><a name="s390_002dx_002dlinux"></a><a name="s390_002d_002a_002dlinux_002a"></a> +<h3 class="heading">s390-*-linux*</h3> <p>S/390 system running GNU/Linux for S/390. - - <p><hr /> - -<h3 class="heading"><a name="TOC48"></a><a name="s390x_002dx_002dlinux"></a>s390x-*-linux*</h3> - +</p> +<hr /><a name="s390x_002dx_002dlinux"></a><a name="s390x_002d_002a_002dlinux_002a"></a> +<h3 class="heading">s390x-*-linux*</h3> <p>zSeries system (64-bit) running GNU/Linux for zSeries. - - <p><hr /> - -<h3 class="heading"><a name="TOC49"></a><a name="s390x_002dibm_002dtpf"></a>s390x-ibm-tpf*</h3> - +</p> +<hr /><a name="s390x_002dibm_002dtpf"></a><a name="s390x_002dibm_002dtpf_002a"></a> +<h3 class="heading">s390x-ibm-tpf*</h3> <p>zSeries system (64-bit) running TPF. This platform is supported as cross-compilation target only. - - <p><hr /><!-- Please use Solaris 2 to refer to all release of Solaris, starting --> -<!-- with 2.0 until 2.6, 7, 8, etc. Solaris 1 was a marketing name for --> -<!-- SunOS 4 releases which we don't use to avoid confusion. Solaris --> -<!-- alone is too unspecific and must be avoided. --> - -<h3 class="heading"><a name="TOC50"></a><a name="x_002dx_002dsolaris2"></a>*-*-solaris2*</h3> - -<p>Support for Solaris 8 has been obsoleted in GCC 4.7, but can still be -enabled by configuring with <samp><span class="option">--enable-obsolete</span></samp>. Support will be -removed in GCC 4.8. Support for Solaris 7 has been removed in GCC 4.6. - - <p>Sun does not ship a C compiler with Solaris 2 before Solaris 10, though +</p> +<hr /><a name="x_002dx_002dsolaris2"></a><a name="g_t_002a_002d_002a_002dsolaris2_002a"></a> +<h3 class="heading">*-*-solaris2*</h3> +<p>Support for Solaris 9 has been obsoleted in GCC 4.9, but can still be +enabled by configuring with <samp>--enable-obsolete</samp>. Support will be +removed in GCC 4.10. Support for Solaris 8 has removed in GCC 4.8. +Support for Solaris 7 has been removed in GCC 4.6. +</p> +<p>Sun does not ship a C compiler with Solaris 2 before Solaris 10, though you can download the Sun Studio compilers for free. In Solaris 10 and -11, GCC 3.4.3 is available as <samp><span class="command">/usr/sfw/bin/gcc</span></samp>. Solaris 11 -also provides GCC 4.5.2 as <samp><span class="command">/usr/gcc/4.5/bin/gcc</span></samp>. Alternatively, +11, GCC 3.4.3 is available as <code>/usr/sfw/bin/gcc</code>. Solaris 11 +also provides GCC 4.5.2 as <code>/usr/gcc/4.5/bin/gcc</code>. Alternatively, you can install a pre-built GCC to bootstrap and install GCC. See the <a href="binaries.html">binaries page</a> for details. - - <p>The Solaris 2 <samp><span class="command">/bin/sh</span></samp> will often fail to configure -‘<samp><span class="samp">libstdc++-v3</span></samp>’, ‘<samp><span class="samp">boehm-gc</span></samp>’ or ‘<samp><span class="samp">libjava</span></samp>’. We therefore +</p> +<p>The Solaris 2 <code>/bin/sh</code> will often fail to configure +‘<samp>libstdc++-v3</samp>’, ‘<samp>boehm-gc</samp>’ or ‘<samp>libjava</samp>’. We therefore recommend using the following initial sequence of commands +</p> +<div class="smallexample"> +<pre class="smallexample">% CONFIG_SHELL=/bin/ksh +% export CONFIG_SHELL +</pre></div> -<pre class="smallexample"> % CONFIG_SHELL=/bin/ksh - % export CONFIG_SHELL -</pre> - <p class="noindent">and proceed as described in <a href="configure.html">the configure instructions</a>. +<p>and proceed as described in <a href="configure.html">the configure instructions</a>. In addition we strongly recommend specifying an absolute path to invoke -<samp><var>srcdir</var><span class="command">/configure</span></samp>. - - <p>Solaris 2 comes with a number of optional OS packages. Some of these +<code><var>srcdir</var>/configure</code>. +</p> +<p>Solaris 2 comes with a number of optional OS packages. Some of these are needed to use GCC fully, namely <code>SUNWarc</code>, <code>SUNWbtool</code>, <code>SUNWesu</code>, <code>SUNWhea</code>, <code>SUNWlibm</code>, <code>SUNWsprot</code>, and <code>SUNWtoo</code>. If you did not install all optional packages when installing Solaris 2, you will need to verify that the packages that GCC needs are installed. - - <p>To check whether an optional package is installed, use -the <samp><span class="command">pkginfo</span></samp> command. To add an optional package, use the -<samp><span class="command">pkgadd</span></samp> command. For further details, see the Solaris 2 +</p> +<p>To check whether an optional package is installed, use +the <code>pkginfo</code> command. To add an optional package, use the +<code>pkgadd</code> command. For further details, see the Solaris 2 documentation. - - <p>Trying to use the linker and other tools in -<samp><span class="file">/usr/ucb</span></samp> to install GCC has been observed to cause trouble. +</p> +<p>Trying to use the linker and other tools in +<samp>/usr/ucb</samp> to install GCC has been observed to cause trouble. For example, the linker may hang indefinitely. The fix is to remove -<samp><span class="file">/usr/ucb</span></samp> from your <samp><span class="env">PATH</span></samp>. - - <p>The build process works more smoothly with the legacy Sun tools so, if you -have <samp><span class="file">/usr/xpg4/bin</span></samp> in your <samp><span class="env">PATH</span></samp>, we recommend that you place -<samp><span class="file">/usr/bin</span></samp> before <samp><span class="file">/usr/xpg4/bin</span></samp> for the duration of the build. - - <p>We recommend the use of the Sun assembler or the GNU assembler, in -conjunction with the Sun linker. The GNU <samp><span class="command">as</span></samp> +<samp>/usr/ucb</samp> from your <code>PATH</code>. +</p> +<p>The build process works more smoothly with the legacy Sun tools so, if you +have <samp>/usr/xpg4/bin</samp> in your <code>PATH</code>, we recommend that you place +<samp>/usr/bin</samp> before <samp>/usr/xpg4/bin</samp> for the duration of the build. +</p> +<p>We recommend the use of the Sun assembler or the GNU assembler, in +conjunction with the Sun linker. The GNU <code>as</code> versions included in Solaris 10, from GNU binutils 2.15, and Solaris 11, from GNU binutils 2.19, are known to work. They can be found in -<samp><span class="file">/usr/sfw/bin/gas</span></samp>. Current versions of GNU binutils (2.22) +<samp>/usr/sfw/bin/gas</samp>. Current versions of GNU binutils (2.22) are known to work as well. Note that your mileage may vary if you use a combination of the GNU tools and the Sun tools: while the -combination GNU <samp><span class="command">as</span></samp> + Sun <samp><span class="command">ld</span></samp> should reasonably work, -the reverse combination Sun <samp><span class="command">as</span></samp> + GNU <samp><span class="command">ld</span></samp> may fail to -build or cause memory corruption at runtime in some cases for C++ programs. -<!-- FIXME: still? --> -GNU <samp><span class="command">ld</span></samp> usually works as well, although the version included in +combination GNU <code>as</code> + Sun <code>ld</code> should reasonably work, +the reverse combination Sun <code>as</code> + GNU <code>ld</code> may fail to +build or cause memory corruption at runtime in some cases for C++ programs. +GNU <code>ld</code> usually works as well, although the version included in Solaris 10 cannot be used due to several bugs. Again, the current version (2.22) is known to work, but generally lacks platform specific -features, so better stay with Sun <samp><span class="command">ld</span></samp>. To use the LTO linker -plugin (<samp><span class="option">-fuse-linker-plugin</span></samp>) with GNU <samp><span class="command">ld</span></samp>, GNU -binutils <em>must</em> be configured with <samp><span class="option">--enable-largefile</span></samp>. - - <p>To enable symbol versioning in ‘<samp><span class="samp">libstdc++</span></samp>’ with Sun <samp><span class="command">ld</span></samp>, -you need to have any version of GNU <samp><span class="command">c++filt</span></samp>, which is part of -GNU binutils. ‘<samp><span class="samp">libstdc++</span></samp>’ symbol versioning will be disabled if no -appropriate version is found. Sun <samp><span class="command">c++filt</span></samp> from the Sun Studio +features, so better stay with Sun <code>ld</code>. To use the LTO linker +plugin (<samp>-fuse-linker-plugin</samp>) with GNU <code>ld</code>, GNU +binutils <em>must</em> be configured with <samp>--enable-largefile</samp>. +</p> +<p>To enable symbol versioning in ‘<samp>libstdc++</samp>’ with Sun <code>ld</code>, +you need to have any version of GNU <code>c++filt</code>, which is part of +GNU binutils. ‘<samp>libstdc++</samp>’ symbol versioning will be disabled if no +appropriate version is found. Sun <code>c++filt</code> from the Sun Studio compilers does <em>not</em> work. - - <p>Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or -newer: <samp><span class="command">g++</span></samp> will complain that types are missing. These headers +</p> +<p>Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or +newer: <code>g++</code> will complain that types are missing. These headers assume that omitting the type means <code>int</code>; this assumption worked for C90 but is wrong for C++, and is now wrong for C99 also. - - <p><samp><span class="command">g++</span></samp> accepts such (invalid) constructs with the option -<samp><span class="option">-fpermissive</span></samp>; it will assume that any missing type is <code>int</code> -(as defined by C90). - - <p>There are patches for Solaris 8 (108652-24 or newer for SPARC, -108653-22 for Intel) that fix this bug. - - <p>Sun bug 4927647 sometimes causes random spurious testsuite failures -related to missing diagnostic output. This bug doesn't affect GCC -itself, rather it is a kernel bug triggered by the <samp><span class="command">expect</span></samp> +</p> +<p>Sun bug 4927647 sometimes causes random spurious testsuite failures +related to missing diagnostic output. This bug doesn’t affect GCC +itself, rather it is a kernel bug triggered by the <code>expect</code> program which is used only by the GCC testsuite driver. When the bug -causes the <samp><span class="command">expect</span></samp> program to miss anticipated output, extra +causes the <code>expect</code> program to miss anticipated output, extra testsuite failures appear. - - <p>There are patches for Solaris 8 (117350-12 or newer for SPARC, -117351-12 or newer for Intel) and Solaris 9 (117171-11 or newer for +</p> +<p>There are patches for Solaris 9 (117171-11 or newer for SPARC, 117172-11 or newer for Intel) that address this problem. - - <p>Solaris 8 provides an alternate implementation of the thread -library ‘<samp><span class="samp">libthread</span></samp>’. It is required for TLS support and has -been made the default in Solaris 9, so it is always used on -Solaris 8. - - <p>Thread-local storage (TLS) is supported in Solaris 8 and 9, but requires -some patches. The ‘<samp><span class="samp">libthread</span></samp>’ patches provide the -<code>__tls_get_addr</code> (SPARC, 64-bit x86) resp. <code>___tls_get_addr</code> -(32-bit x86) functions. On Solaris 8, you need 108993-26 or newer on -SPARC, 108994-26 or newer on Intel. On Solaris 9, the necessary support +</p> +<p>Thread-local storage (TLS) is supported in Solaris 9, but requires +some patches. The ‘<samp>libthread</samp>’ patches provide the +<code>__tls_get_addr</code> (SPARC, 64-bit x86) resp. <code>___tls_get_addr</code> +(32-bit x86) functions. On Solaris 9, the necessary support on SPARC is present since FCS, while 114432-05 or newer is required on -Intel. Additionally, on Solaris 8, patch 109147-14 or newer on SPARC or -109148-22 or newer on Intel are required for the Sun <samp><span class="command">ld</span></samp> and -runtime linker (<samp><span class="command">ld.so.1</span></samp>) support. Again, Solaris 9/SPARC -works since FCS, while 113986-02 is required on Intel. The linker -patches must be installed even if GNU <samp><span class="command">ld</span></samp> is used. Sun -<samp><span class="command">as</span></samp> in Solaris 8 and 9 doesn't support the necessary -relocations, so GNU <samp><span class="command">as</span></samp> must be used. The <samp><span class="command">configure</span></samp> +Intel. Additionally, on Solaris 9/x86, patch 113986-02 or newer is +required for the Sun <code>ld</code> and runtime linker (<code>ld.so.1</code>) +support, while Solaris 9/SPARC works since FCS. The linker +patches must be installed even if GNU <code>ld</code> is used. Sun +<code>as</code> in Solaris 9 doesn’t support the necessary +relocations, so GNU <code>as</code> must be used. The <code>configure</code> script checks for those prerequisites and automatically enables TLS support if they are met. Although those minimal patch versions should work, it is recommended to use the latest patch versions which include additional bug fixes. - - <p><hr /> - -<h3 class="heading"><a name="TOC51"></a><a name="sparc_002dx_002dx"></a>sparc*-*-*</h3> - +</p> +<hr /><a name="sparc_002dx_002dx"></a><a name="sparc_002a_002d_002a_002d_002a"></a> +<h3 class="heading">sparc*-*-*</h3> <p>This section contains general configuration information for all SPARC-based platforms. In addition to reading this section, please read all other sections that match your target. - - <p>Newer versions of the GNU Multiple Precision Library (GMP), the MPFR +</p> +<p>Newer versions of the GNU Multiple Precision Library (GMP), the MPFR library and the MPC library are known to be miscompiled by earlier versions of GCC on these platforms. We therefore recommend the use of the exact versions of these libraries listed as minimal versions in <a href="prerequisites.html">the prerequisites</a>. - - <p><hr /> - -<h3 class="heading"><a name="TOC52"></a><a name="sparc_002dsun_002dsolaris2"></a>sparc-sun-solaris2*</h3> - +</p> +<hr /><a name="sparc_002dsun_002dsolaris2"></a><a name="sparc_002dsun_002dsolaris2_002a"></a> +<h3 class="heading">sparc-sun-solaris2*</h3> <p>When GCC is configured to use GNU binutils 2.14 or later, the binaries -produced are smaller than the ones produced using Sun's native tools; +produced are smaller than the ones produced using Sun’s native tools; this difference is quite significant for binaries containing debugging information. - - <p>Starting with Solaris 7, the operating system is capable of executing +</p> +<p>Starting with Solaris 7, the operating system is capable of executing 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports -this; the <samp><span class="option">-m64</span></samp> option enables 64-bit code generation. +this; the <samp>-m64</samp> option enables 64-bit code generation. However, if all you want is code tuned for the UltraSPARC CPU, you -should try the <samp><span class="option">-mtune=ultrasparc</span></samp> option instead, which produces +should try the <samp>-mtune=ultrasparc</samp> option instead, which produces code that, unlike full 64-bit code, can still run on non-UltraSPARC machines. - - <p>When configuring on a Solaris 7 or later system that is running a kernel +</p> +<p>When configuring on a Solaris 7 or later system that is running a kernel that supports only 32-bit binaries, one must configure with -<samp><span class="option">--disable-multilib</span></samp>, since we will not be able to build the +<samp>--disable-multilib</samp>, since we will not be able to build the 64-bit target libraries. - - <p>GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of +</p> +<p>GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of the GNU compiler (especially GCC 3.0.x versions), which lead to the miscompilation of the stage1 compiler and the subsequent failure of the bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary stage, i.e. to bootstrap that compiler with the base compiler and then use it to bootstrap the final compiler. - - <p>GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE Studio 7) +</p> +<p>GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE Studio 7) and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a bootstrap failure in form of a miscompilation of the stage1 compiler by the Sun compiler. This is Sun bug 4974440. This is fixed with patch 112760-07. - - <p>GCC 3.4 changed the default debugging format from Stabs to DWARF-2 for +</p> +<p>GCC 3.4 changed the default debugging format from Stabs to DWARF-2 for 32-bit code on Solaris 7 and later. If you use the Sun assembler, this change apparently runs afoul of Sun bug 4910101 (which is referenced as -an x86-only problem by Sun, probably because they do not use DWARF-2). +an x86-only problem by Sun, probably because they do not use DWARF-2). A symptom of the problem is that you cannot compile C++ programs like -<samp><span class="command">groff</span></samp> 1.19.1 without getting messages similar to the following: - -<pre class="smallexample"> ld: warning: relocation error: R_SPARC_UA32: ... - external symbolic relocation against non-allocatable section - .debug_info cannot be processed at runtime: relocation ignored. -</pre> - <p class="noindent">To work around this problem, compile with <samp><span class="option">-gstabs+</span></samp> instead of -plain <samp><span class="option">-g</span></samp>. - - <p>When configuring the GNU Multiple Precision Library (GMP), the MPFR +<code>groff</code> 1.19.1 without getting messages similar to the following: +</p> +<div class="smallexample"> +<pre class="smallexample">ld: warning: relocation error: R_SPARC_UA32: … + external symbolic relocation against non-allocatable section + .debug_info cannot be processed at runtime: relocation ignored. +</pre></div> + +<p>To work around this problem, compile with <samp>-gstabs+</samp> instead of +plain <samp>-g</samp>. +</p> +<p>When configuring the GNU Multiple Precision Library (GMP), the MPFR library or the MPC library on a Solaris 7 or later system, the canonical -target triplet must be specified as the <samp><span class="command">build</span></samp> parameter on the -configure line. This target triplet can be obtained by invoking <samp><span class="command">./config.guess</span></samp> in the toplevel source directory of GCC (and +target triplet must be specified as the <code>build</code> parameter on the +configure line. This target triplet can be obtained by invoking <code>./config.guess</code> in the toplevel source directory of GCC (and not that of GMP or MPFR or MPC). For example on a Solaris 9 system: +</p> +<div class="smallexample"> +<pre class="smallexample">% ./configure --build=sparc-sun-solaris2.9 --prefix=xxx +</pre></div> -<pre class="smallexample"> % ./configure --build=sparc-sun-solaris2.9 --prefix=xxx -</pre> - <p><hr /> - -<h3 class="heading"><a name="TOC53"></a><a name="sparc_002dsun_002dsolaris210"></a>sparc-sun-solaris2.10</h3> - +<hr /><a name="sparc_002dsun_002dsolaris210"></a><a name="sparc_002dsun_002dsolaris2_002e10"></a> +<h3 class="heading">sparc-sun-solaris2.10</h3> <p>There is a bug in older versions of the Sun assembler which breaks thread-local storage (TLS). A typical error message is +</p> +<div class="smallexample"> +<pre class="smallexample">ld: fatal: relocation error: R_SPARC_TLS_LE_HIX22: file /var/tmp//ccamPA1v.o: + symbol <unknown>: bad symbol type SECT: symbol type must be TLS +</pre></div> -<pre class="smallexample"> ld: fatal: relocation error: R_SPARC_TLS_LE_HIX22: file /var/tmp//ccamPA1v.o: - symbol <unknown>: bad symbol type SECT: symbol type must be TLS -</pre> - <p class="noindent">This bug is fixed in Sun patch 118683-03 or later. - - <p><hr /> - -<h3 class="heading"><a name="TOC54"></a><a name="sparc_002dx_002dlinux"></a>sparc-*-linux*</h3> +<p>This bug is fixed in Sun patch 118683-03 or later. +</p> +<hr /><a name="sparc_002dx_002dlinux"></a><a name="sparc_002d_002a_002dlinux_002a"></a> +<h3 class="heading">sparc-*-linux*</h3> <p>GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4 or newer on this platform. All earlier binutils and glibc releases mishandled unaligned relocations on <code>sparc-*-*</code> targets. +</p> - <p><hr /> - -<h3 class="heading"><a name="TOC55"></a><a name="sparc64_002dx_002dsolaris2"></a>sparc64-*-solaris2*</h3> - +<hr /><a name="sparc64_002dx_002dsolaris2"></a><a name="sparc64_002d_002a_002dsolaris2_002a"></a> +<h3 class="heading">sparc64-*-solaris2*</h3> <p>When configuring the GNU Multiple Precision Library (GMP), the MPFR library or the MPC library, the canonical target triplet must be specified -as the <samp><span class="command">build</span></samp> parameter on the configure line. For example +as the <code>build</code> parameter on the configure line. For example on a Solaris 9 system: +</p> +<div class="smallexample"> +<pre class="smallexample">% ./configure --build=sparc64-sun-solaris2.9 --prefix=xxx +</pre></div> -<pre class="smallexample"> % ./configure --build=sparc64-sun-solaris2.9 --prefix=xxx -</pre> - <p>The following compiler flags must be specified in the configure +<p>The following compiler flags must be specified in the configure step in order to bootstrap this target with the Sun compiler: - -<pre class="smallexample"> % CC="cc -xarch=v9 -xildoff" <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>] -</pre> - <p class="noindent"><samp><span class="option">-xarch=v9</span></samp> specifies the SPARC-V9 architecture to the Sun toolchain -and <samp><span class="option">-xildoff</span></samp> turns off the incremental linker. - - <p><hr /> - -<h3 class="heading"><a name="TOC56"></a><a name="sparcv9_002dx_002dsolaris2"></a>sparcv9-*-solaris2*</h3> - -<p>This is a synonym for ‘<samp><span class="samp">sparc64-*-solaris2*</span></samp>’. - - <p><hr /> - -<h3 class="heading"><a name="TOC57"></a><a name="c6x_002dx_002dx"></a>c6x-*-*</h3> - +</p> +<div class="smallexample"> +<pre class="smallexample">% CC="cc -xarch=v9 -xildoff" <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>] +</pre></div> + +<p><samp>-xarch=v9</samp> specifies the SPARC-V9 architecture to the Sun toolchain +and <samp>-xildoff</samp> turns off the incremental linker. +</p> +<hr /><a name="sparcv9_002dx_002dsolaris2"></a><a name="sparcv9_002d_002a_002dsolaris2_002a"></a> +<h3 class="heading">sparcv9-*-solaris2*</h3> +<p>This is a synonym for ‘<samp>sparc64-*-solaris2*</samp>’. +</p> +<hr /><a name="c6x_002dx_002dx"></a><a name="c6x_002d_002a_002d_002a"></a> +<h3 class="heading">c6x-*-*</h3> <p>The C6X family of processors. This port requires binutils-2.22 or newer. - - <p><hr /> - -<h3 class="heading"><a name="TOC58"></a><a name="tilegx_002d_002a_002dlinux"></a>tilegx-*-linux*</h3> - -<p>The TILE-Gx processor running GNU/Linux. This port requires -binutils-2.22 or newer. - - <p><hr /> - -<h3 class="heading"><a name="TOC59"></a><a name="tilepro_002d_002a_002dlinux"></a>tilepro-*-linux*</h3> - +</p> +<hr /><a name="tilegx_002d_002a_002dlinux"></a><a name="tilegx_002d_002a_002dlinux_002a"></a> +<h3 class="heading">tilegx-*-linux*</h3> +<p>The TILE-Gx processor in little endian mode, running GNU/Linux. This +port requires binutils-2.22 or newer. +</p> +<hr /><a name="tilegxbe_002d_002a_002dlinux"></a><a name="tilegxbe_002d_002a_002dlinux_002a"></a> +<h3 class="heading">tilegxbe-*-linux*</h3> +<p>The TILE-Gx processor in big endian mode, running GNU/Linux. This +port requires binutils-2.23 or newer. +</p> +<hr /><a name="tilepro_002d_002a_002dlinux"></a><a name="tilepro_002d_002a_002dlinux_002a"></a> +<h3 class="heading">tilepro-*-linux*</h3> <p>The TILEPro processor running GNU/Linux. This port requires binutils-2.22 or newer. - - <p><hr /> - -<h3 class="heading"><a name="TOC60"></a><a name="x_002dx_002dvxworks"></a>*-*-vxworks*</h3> - +</p> +<hr /><a name="x_002dx_002dvxworks"></a><a name="g_t_002a_002d_002a_002dvxworks_002a"></a> +<h3 class="heading">*-*-vxworks*</h3> <p>Support for VxWorks is in flux. At present GCC supports <em>only</em> the -very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC. -We welcome patches for other architectures supported by VxWorks 5.5. +very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC. +We welcome patches for other architectures supported by VxWorks 5.5. Support for VxWorks AE would also be welcome; we believe this is merely a matter of writing an appropriate “configlette” (see below). We are not interested in supporting older, a.out or COFF-based, versions of VxWorks in GCC 3. - - <p>VxWorks comes with an older version of GCC installed in -<samp><var>$WIND_BASE</var><span class="file">/host</span></samp>; we recommend you do not overwrite it. -Choose an installation <var>prefix</var> entirely outside <var>$WIND_BASE</var>. -Before running <samp><span class="command">configure</span></samp>, create the directories <samp><var>prefix</var></samp> -and <samp><var>prefix</var><span class="file">/bin</span></samp>. Link or copy the appropriate assembler, -linker, etc. into <samp><var>prefix</var><span class="file">/bin</span></samp>, and set your <var>PATH</var> to -include that directory while running both <samp><span class="command">configure</span></samp> and -<samp><span class="command">make</span></samp>. - - <p>You must give <samp><span class="command">configure</span></samp> the -<samp><span class="option">--with-headers=</span><var>$WIND_BASE</var><span class="option">/target/h</span></samp> switch so that it can +</p> +<p>VxWorks comes with an older version of GCC installed in +<samp><var>$WIND_BASE</var>/host</samp>; we recommend you do not overwrite it. +Choose an installation <var>prefix</var> entirely outside <var>$WIND_BASE</var>. +Before running <code>configure</code>, create the directories <samp><var>prefix</var></samp> +and <samp><var>prefix</var>/bin</samp>. Link or copy the appropriate assembler, +linker, etc. into <samp><var>prefix</var>/bin</samp>, and set your <var>PATH</var> to +include that directory while running both <code>configure</code> and +<code>make</code>. +</p> +<p>You must give <code>configure</code> the +<samp>--with-headers=<var>$WIND_BASE</var>/target/h</samp> switch so that it can find the VxWorks system headers. Since VxWorks is a cross compilation -target only, you must also specify <samp><span class="option">--target=</span><var>target</var></samp>. -<samp><span class="command">configure</span></samp> will attempt to create the directory -<samp><var>prefix</var><span class="file">/</span><var>target</var><span class="file">/sys-include</span></samp> and copy files into it; -make sure the user running <samp><span class="command">configure</span></samp> has sufficient privilege +target only, you must also specify <samp>--target=<var>target</var></samp>. +<code>configure</code> will attempt to create the directory +<samp><var>prefix</var>/<var>target</var>/sys-include</samp> and copy files into it; +make sure the user running <code>configure</code> has sufficient privilege to do so. - - <p>GCC's exception handling runtime requires a special “configlette” -module, <samp><span class="file">contrib/gthr_supp_vxw_5x.c</span></samp>. Follow the instructions in +</p> +<p>GCC’s exception handling runtime requires a special “configlette” +module, <samp>contrib/gthr_supp_vxw_5x.c</samp>. Follow the instructions in that file to add the module to your kernel build. (Future versions of VxWorks will incorporate this module.) - - <p><hr /> - -<h3 class="heading"><a name="TOC61"></a><a name="x86_002d64_002dx_002dx"></a>x86_64-*-*, amd64-*-*</h3> - +</p> +<hr /><a name="x86_002d64_002dx_002dx"></a><a name="x86_005f64_002d_002a_002d_002a_002c-amd64_002d_002a_002d_002a"></a> +<h3 class="heading">x86_64-*-*, amd64-*-*</h3> <p>GCC supports the x86-64 architecture implemented by the AMD64 processor -(amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD. +(amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD. On GNU/Linux the default is a bi-arch compiler which is able to generate -both 64-bit x86-64 and 32-bit x86 code (via the <samp><span class="option">-m32</span></samp> switch). - - <p><hr /> - -<h3 class="heading"><a name="TOC62"></a><a name="x86_002d64_002dx_002dsolaris210"></a>x86_64-*-solaris2.1[0-9]*</h3> - +both 64-bit x86-64 and 32-bit x86 code (via the <samp>-m32</samp> switch). +</p> +<hr /><a name="x86_002d64_002dx_002dsolaris210"></a><a name="x86_005f64_002d_002a_002dsolaris2_002e1_005b0_002d9_005d_002a"></a> +<h3 class="heading">x86_64-*-solaris2.1[0-9]*</h3> <p>GCC also supports the x86-64 architecture implemented by the AMD64 -processor (‘<samp><span class="samp">amd64-*-*</span></samp>’ is an alias for ‘<samp><span class="samp">x86_64-*-*</span></samp>’) on +processor (‘<samp>amd64-*-*</samp>’ is an alias for ‘<samp>x86_64-*-*</samp>’) on Solaris 10 or later. Unlike other systems, without special options a bi-arch compiler is built which generates 32-bit code by default, but -can generate 64-bit x86-64 code with the <samp><span class="option">-m64</span></samp> switch. Since +can generate 64-bit x86-64 code with the <samp>-m64</samp> switch. Since GCC 4.7, there is also configuration that defaults to 64-bit code, but -can generate 32-bit code with <samp><span class="option">-m32</span></samp>. To configure and build -this way, you have to provide all support libraries like <samp><span class="file">libgmp</span></samp> -as 64-bit code, configure with <samp><span class="option">--target=x86_64-pc-solaris2.1x</span></samp> -and ‘<samp><span class="samp">CC=gcc -m64</span></samp>’. - - <p><hr /> - -<h3 class="heading"><a name="TOC63"></a><a name="xtensa_002dx_002delf"></a>xtensa*-*-elf</h3> - +can generate 32-bit code with <samp>-m32</samp>. To configure and build +this way, you have to provide all support libraries like <samp>libgmp</samp> +as 64-bit code, configure with <samp>--target=x86_64-pc-solaris2.1x</samp> +and ‘<samp>CC=gcc -m64</samp>’. +</p> +<hr /><a name="xtensa_002dx_002delf"></a><a name="xtensa_002a_002d_002a_002delf"></a> +<h3 class="heading">xtensa*-*-elf</h3> <p>This target is intended for embedded Xtensa systems using the -‘<samp><span class="samp">newlib</span></samp>’ C library. It uses ELF but does not support shared +‘<samp>newlib</samp>’ C library. It uses ELF but does not support shared objects. Designed-defined instructions specified via the Tensilica Instruction Extension (TIE) language are only supported through inline assembly. - - <p>The Xtensa configuration information must be specified prior to -building GCC. The <samp><span class="file">include/xtensa-config.h</span></samp> header +</p> +<p>The Xtensa configuration information must be specified prior to +building GCC. The <samp>include/xtensa-config.h</samp> header file contains the configuration information. If you created your own Xtensa configuration with the Xtensa Processor Generator, the downloaded files include a customized copy of this header file, which you can use to replace the default header file. - - <p><hr /> - -<h3 class="heading"><a name="TOC64"></a><a name="xtensa_002dx_002dlinux"></a>xtensa*-*-linux*</h3> - +</p> +<hr /><a name="xtensa_002dx_002dlinux"></a><a name="xtensa_002a_002d_002a_002dlinux_002a"></a> +<h3 class="heading">xtensa*-*-linux*</h3> <p>This target is for Xtensa systems running GNU/Linux. It supports ELF shared objects and the GNU C library (glibc). It also generates position-independent code (PIC) regardless of whether the -<samp><span class="option">-fpic</span></samp> or <samp><span class="option">-fPIC</span></samp> options are used. In other +<samp>-fpic</samp> or <samp>-fPIC</samp> options are used. In other respects, this target is the same as the -<a href="#xtensa*-*-elf">‘<samp><span class="samp">xtensa*-*-elf</span></samp>’</a> target. - - <p><hr /> - -<h3 class="heading"><a name="TOC65"></a><a name="windows"></a>Microsoft Windows</h3> - -<h4 class="subheading"><a name="TOC66"></a>Intel 16-bit versions</h4> +<a href="#xtensa*-*-elf">‘<samp>xtensa*-*-elf</samp>’</a> target. +</p> +<hr /><a name="windows"></a><a name="Microsoft-Windows"></a> +<h3 class="heading">Microsoft Windows</h3> +<a name="Intel-16_002dbit-versions"></a> +<h4 class="subheading">Intel 16-bit versions</h4> <p>The 16-bit versions of Microsoft Windows, such as Windows 3.1, are not supported. - - <p>However, the 32-bit port has limited support for Microsoft +</p> +<p>However, the 32-bit port has limited support for Microsoft Windows 3.11 in the Win32s environment, as a target only. See below. - -<h4 class="subheading"><a name="TOC67"></a>Intel 32-bit versions</h4> - +</p> +<a name="Intel-32_002dbit-versions"></a> +<h4 class="subheading">Intel 32-bit versions</h4> <p>The 32-bit versions of Windows, including Windows 95, Windows NT, Windows XP, and Windows Vista, are supported by several different target platforms. These targets differ in which Windows subsystem they target and which C libraries are used. - - <ul> -<li>Cygwin <a href="#x-x-cygwin">*-*-cygwin</a>: Cygwin provides a user-space -Linux API emulation layer in the Win32 subsystem. -<li>Interix <a href="#x-x-interix">*-*-interix</a>: The Interix subsystem -provides native support for POSIX. -<li>MinGW <a href="#x-x-mingw32">*-*-mingw32</a>: MinGW is a native GCC port for -the Win32 subsystem that provides a subset of POSIX. -<li>MKS i386-pc-mks: NuTCracker from MKS. See -<a href="http://www.mkssoftware.com/">http://www.mkssoftware.com/</a> for more information. -</ul> - -<h4 class="subheading"><a name="TOC68"></a>Intel 64-bit versions</h4> - +</p> +<ul> +<li> Cygwin <a href="#x-x-cygwin">*-*-cygwin</a>: Cygwin provides a user-space +Linux API emulation layer in the Win32 subsystem. +</li><li> Interix <a href="#x-x-interix">*-*-interix</a>: The Interix subsystem +provides native support for POSIX. +</li><li> MinGW <a href="#x-x-mingw32">*-*-mingw32</a>: MinGW is a native GCC port for +the Win32 subsystem that provides a subset of POSIX. +</li><li> MKS i386-pc-mks: NuTCracker from MKS. See +<a href="http://www.mkssoftware.com/">http://www.mkssoftware.com/</a> for more information. +</li></ul> + +<a name="Intel-64_002dbit-versions"></a> +<h4 class="subheading">Intel 64-bit versions</h4> <p>GCC contains support for x86-64 using the mingw-w64 -runtime library, available from <a href="http://mingw-w64.sourceforge.net/">http://mingw-w64.sourceforge.net/</a>. +runtime library, available from <a href="http://mingw-w64.sourceforge.net/">http://mingw-w64.sourceforge.net/</a>. This library should be used with the target triple x86_64-pc-mingw32. - - <p>Presently Windows for Itanium is not supported. - -<h4 class="subheading"><a name="TOC69"></a>Windows CE</h4> - +</p> +<p>Presently Windows for Itanium is not supported. +</p> +<a name="Windows-CE"></a> +<h4 class="subheading">Windows CE</h4> <p>Windows CE is supported as a target only on Hitachi SuperH (sh-wince-pe), and MIPS (mips-wince-pe). - -<h4 class="subheading"><a name="TOC70"></a>Other Windows Platforms</h4> - +</p> +<a name="Other-Windows-Platforms"></a> +<h4 class="subheading">Other Windows Platforms</h4> <p>GCC no longer supports Windows NT on the Alpha or PowerPC. - - <p>GCC no longer supports the Windows POSIX subsystem. However, it does +</p> +<p>GCC no longer supports the Windows POSIX subsystem. However, it does support the Interix subsystem. See above. - - <p>Old target names including *-*-winnt and *-*-windowsnt are no longer used. - - <p>PW32 (i386-pc-pw32) support was never completed, and the project seems to +</p> +<p>Old target names including *-*-winnt and *-*-windowsnt are no longer used. +</p> +<p>PW32 (i386-pc-pw32) support was never completed, and the project seems to be inactive. See <a href="http://pw32.sourceforge.net/">http://pw32.sourceforge.net/</a> for more information. - - <p>UWIN support has been removed due to a lack of maintenance. - - <p><hr /> - -<h3 class="heading"><a name="TOC71"></a><a name="x_002dx_002dcygwin"></a>*-*-cygwin</h3> - +</p> +<p>UWIN support has been removed due to a lack of maintenance. +</p> +<hr /><a name="x_002dx_002dcygwin"></a><a name="g_t_002a_002d_002a_002dcygwin"></a> +<h3 class="heading">*-*-cygwin</h3> <p>Ports of GCC are included with the <a href="http://www.cygwin.com/">Cygwin environment</a>. - - <p>GCC will build under Cygwin without modification; it does not build -with Microsoft's C++ compiler and there are no plans to make it do so. - - <p>The Cygwin native compiler can be configured to target any 32-bit x86 +</p> +<p>GCC will build under Cygwin without modification; it does not build +with Microsoft’s C++ compiler and there are no plans to make it do so. +</p> +<p>The Cygwin native compiler can be configured to target any 32-bit x86 cpu architecture desired; the default is i686-pc-cygwin. It should be used with as up-to-date a version of binutils as possible; use either the latest official GNU binutils release in the Cygwin distribution, or version 2.20 or above if building your own. - - <p><hr /> - -<h3 class="heading"><a name="TOC72"></a><a name="x_002dx_002dinterix"></a>*-*-interix</h3> - +</p> +<hr /><a name="x_002dx_002dinterix"></a><a name="g_t_002a_002d_002a_002dinterix"></a> +<h3 class="heading">*-*-interix</h3> <p>The Interix target is used by OpenNT, Interix, Services For UNIX (SFU), and Subsystem for UNIX-based Applications (SUA). Applications compiled with this target run in the Interix subsystem, which is separate from the Win32 subsystem. This target was last known to work in GCC 3.3. - - <p><hr /> - -<h3 class="heading"><a name="TOC73"></a><a name="x_002dx_002dmingw32"></a>*-*-mingw32</h3> - -<p>GCC will build with and support only MinGW runtime 3.12 and later. +</p> +<hr /><a name="x_002dx_002dmingw32"></a><a name="g_t_002a_002d_002a_002dmingw32"></a> +<h3 class="heading">*-*-mingw32</h3> +<p>GCC will build with and support only MinGW runtime 3.12 and later. Earlier versions of headers are incompatible with the new default semantics of <code>extern inline</code> in <code>-std=c99</code> and <code>-std=gnu99</code> modes. - - <p><hr /> - -<h3 class="heading"><a name="TOC74"></a><a name="older"></a>Older systems</h3> - +</p> +<hr /><a name="older"></a><a name="Older-systems"></a> +<h3 class="heading">Older systems</h3> <p>GCC contains support files for many older (1980s and early 1990s) Unix variants. For the most part, support for these systems has not been deliberately removed, but it has not been maintained for several years and may suffer from bitrot. - - <p>Starting with GCC 3.1, each release has a list of “obsoleted” systems. +</p> +<p>Starting with GCC 3.1, each release has a list of “obsoleted” systems. Support for these systems is still present in that release, but -<samp><span class="command">configure</span></samp> will fail unless the <samp><span class="option">--enable-obsolete</span></samp> +<code>configure</code> will fail unless the <samp>--enable-obsolete</samp> option is given. Unless a maintainer steps forward, support for these systems will be removed from the next release of GCC. - - <p>Support for old systems as hosts for GCC can cause problems if the +</p> +<p>Support for old systems as hosts for GCC can cause problems if the workarounds for compiler, library and operating system bugs affect the cleanliness or maintainability of the rest of GCC. In some cases, to bring GCC up on such a system, if still possible with current GCC, may require first installing an old version of GCC which did work on that system, and using it to compile a more recent GCC, to avoid bugs in the vendor compiler. Old releases of GCC 1 and GCC 2 are available in the -<samp><span class="file">old-releases</span></samp> directory on the <a href="../mirrors.html">GCC mirror sites</a>. Header bugs may generally be avoided using -<samp><span class="command">fixincludes</span></samp>, but bugs or deficiencies in libraries and the +<samp>old-releases</samp> directory on the <a href="../mirrors.html">GCC mirror +sites</a>. Header bugs may generally be avoided using +<code>fixincludes</code>, but bugs or deficiencies in libraries and the operating system may still cause problems. - - <p>Support for older systems as targets for cross-compilation is less +</p> +<p>Support for older systems as targets for cross-compilation is less problematic than support for them as hosts for GCC; if an enthusiast wishes to make such a target work again (including resurrecting any of the targets that never worked with GCC 2, starting from the last @@ -1579,31 +1433,32 @@ version before they were removed), patches <a href="../contribute.html">following the usual requirements</a> would be likely to be accepted, since they should not affect the support for more modern targets. - - <p>For some systems, old versions of GNU binutils may also be useful, -and are available from <samp><span class="file">pub/binutils/old-releases</span></samp> on +</p> +<p>For some systems, old versions of GNU binutils may also be useful, +and are available from <samp>pub/binutils/old-releases</samp> on <a href="http://sourceware.org/mirrors.html">sourceware.org mirror sites</a>. - - <p>Some of the information on specific systems above relates to +</p> +<p>Some of the information on specific systems above relates to such older systems, but much of the information about GCC on such systems (which may no longer be applicable to current GCC) is to be found in the GCC texinfo manual. - - <p><hr /> - -<h3 class="heading"><a name="TOC75"></a><a name="elf"></a>all ELF targets (SVR4, Solaris 2, etc.)</h3> - +</p> +<hr /><a name="elf"></a><a name="all-ELF-targets-_0028SVR4_002c-Solaris-2_002c-etc_002e_0029"></a> +<h3 class="heading">all ELF targets (SVR4, Solaris 2, etc.)</h3> <p>C++ support is significantly better on ELF targets if you use the <a href="./configure.html#with-gnu-ld">GNU linker</a>; duplicate copies of inlines, vtables and template instantiations will be discarded automatically. +</p> + +<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> -<!-- ***Old documentation****************************************************** --> -<!-- ***GFDL******************************************************************** --> -<!-- *************************************************************************** --> -<!-- Part 6 The End of the Document --> -</body></html> +</body> +</html> diff --git a/INSTALL/test.html b/INSTALL/test.html index 359bfec9de..3cd3ad5741 100644 --- a/INSTALL/test.html +++ b/INSTALL/test.html @@ -1,236 +1,315 @@ -<html lang="en"> -<head> -<title>Installing GCC: Testing</title> -<meta http-equiv="Content-Type" content="text/html"> -<meta name="description" content="Installing GCC: Testing"> -<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, 1989, 1992, 1993, 1994, 1995, 1996, 1997, -1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, -2010 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-2014 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: Testing</h1> -<a name="index-Testing-1"></a><a name="index-Installing-GCC_003a-Testing-2"></a><a name="index-Testsuite-3"></a> -Before you install GCC, we encourage you to run the testsuites and to + +<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000"> +<h1 class="settitle" align="center">Installing GCC</h1> + + + + + + + + + + + + + + + + + + + + + +<a name="index-Testing"></a> +<a name="index-Installing-GCC_003a-Testing"></a> +<a name="index-Testsuite"></a> + +<p>Before you install GCC, we encourage you to run the testsuites and to compare your results with results from a similar configuration that have been submitted to the -<a href="http://gcc.gnu.org/ml/gcc-testresults/">gcc-testresults mailing list</a>. +<a href="http://gcc.gnu.org/ml/gcc-testresults/">gcc-testresults mailing list</a>. Some of these archived results are linked from the build status lists at <a href="http://gcc.gnu.org/buildstat.html">http://gcc.gnu.org/buildstat.html</a>, although not everyone who -reports a successful build runs the testsuites and submits the results. +reports a successful build runs the testsuites and submits the results. This step is optional and may require you to download additional software, but it can give you confidence in your new GCC installation or point out problems before you install and start using your new GCC. - - <p>First, you must have <a href="download.html">downloaded the testsuites</a>. +</p> +<p>First, you must have <a href="download.html">downloaded the testsuites</a>. These are part of the full distribution, but if you downloaded the “core” compiler plus any front ends, you must download the testsuites separately. - - <p>Second, you must have the testing tools installed. This includes +</p> +<p>Second, you must have the testing tools installed. This includes <a href="http://www.gnu.org/software/dejagnu/">DejaGnu</a>, Tcl, and Expect; the DejaGnu site has links to these. - - <p>If the directories where <samp><span class="command">runtest</span></samp> and <samp><span class="command">expect</span></samp> were -installed are not in the <samp><span class="env">PATH</span></samp>, you may need to set the following +</p> +<p>If the directories where <code>runtest</code> and <code>expect</code> were +installed are not in the <code>PATH</code>, you may need to set the following environment variables appropriately, as in the following example (which -assumes that DejaGnu has been installed under <samp><span class="file">/usr/local</span></samp>): - -<pre class="smallexample"> TCL_LIBRARY = /usr/local/share/tcl8.0 - DEJAGNULIBS = /usr/local/share/dejagnu -</pre> - <p>(On systems such as Cygwin, these paths are required to be actual +assumes that DejaGnu has been installed under <samp>/usr/local</samp>): +</p> +<div class="smallexample"> +<pre class="smallexample">TCL_LIBRARY = /usr/local/share/tcl8.0 +DEJAGNULIBS = /usr/local/share/dejagnu +</pre></div> + +<p>(On systems such as Cygwin, these paths are required to be actual paths, not mounts or links; presumably this is due to some lack of portability in the DejaGnu code.) +</p> + +<p>Finally, you can run the testsuite (which may take a long time): +</p><div class="smallexample"> +<pre class="smallexample">cd <var>objdir</var>; make -k check +</pre></div> - <p>Finally, you can run the testsuite (which may take a long time): -<pre class="smallexample"> cd <var>objdir</var>; make -k check -</pre> - <p>This will test various components of GCC, such as compiler +<p>This will test various components of GCC, such as compiler front ends and runtime libraries. While running the testsuite, DejaGnu might emit some harmless messages resembling -‘<samp><span class="samp">WARNING: Couldn't find the global config file.</span></samp>’ or -‘<samp><span class="samp">WARNING: Couldn't find tool init file</span></samp>’ that can be ignored. - - <p>If you are testing a cross-compiler, you may want to run the testsuite +‘<samp>WARNING: Couldn't find the global config file.</samp>’ or +‘<samp>WARNING: Couldn't find tool init file</samp>’ that can be ignored. +</p> +<p>If you are testing a cross-compiler, you may want to run the testsuite on a simulator as described at <a href="http://gcc.gnu.org/simtest-howto.html">http://gcc.gnu.org/simtest-howto.html</a>. - -<h3 class="section"><a name="TOC0"></a>How can you run the testsuite on selected tests?</h3> +</p> +<a name="How-can-you-run-the-testsuite-on-selected-tests_003f"></a> +<h3 class="section">How can you run the testsuite on selected tests?</h3> <p>In order to run sets of tests selectively, there are targets -‘<samp><span class="samp">make check-gcc</span></samp>’ and language specific ‘<samp><span class="samp">make check-c</span></samp>’, -‘<samp><span class="samp">make check-c++</span></samp>’, ‘<samp><span class="samp">make check-fortran</span></samp>’, ‘<samp><span class="samp">make check-java</span></samp>’, -‘<samp><span class="samp">make check-ada</span></samp>’, ‘<samp><span class="samp">make check-objc</span></samp>’, ‘<samp><span class="samp">make check-obj-c++</span></samp>’, -‘<samp><span class="samp">make check-lto</span></samp>’ -in the <samp><span class="file">gcc</span></samp> subdirectory of the object directory. You can also -just run ‘<samp><span class="samp">make check</span></samp>’ in a subdirectory of the object directory. - - <p>A more selective way to just run all <samp><span class="command">gcc</span></samp> execute tests in the +‘<samp>make check-gcc</samp>’ and language specific ‘<samp>make check-c</samp>’, +‘<samp>make check-c++</samp>’, ‘<samp>make check-fortran</samp>’, ‘<samp>make check-java</samp>’, +‘<samp>make check-ada</samp>’, ‘<samp>make check-objc</samp>’, ‘<samp>make check-obj-c++</samp>’, +‘<samp>make check-lto</samp>’ +in the <samp>gcc</samp> subdirectory of the object directory. You can also +just run ‘<samp>make check</samp>’ in a subdirectory of the object directory. +</p> + +<p>A more selective way to just run all <code>gcc</code> execute tests in the testsuite is to use - -<pre class="smallexample"> make check-gcc RUNTESTFLAGS="execute.exp <var>other-options</var>" -</pre> - <p>Likewise, in order to run only the <samp><span class="command">g++</span></samp> “old-deja” tests in -the testsuite with filenames matching ‘<samp><span class="samp">9805*</span></samp>’, you would use - -<pre class="smallexample"> make check-g++ RUNTESTFLAGS="old-deja.exp=9805* <var>other-options</var>" -</pre> - <p>The <samp><span class="file">*.exp</span></samp> files are located in the testsuite directories of the GCC -source, the most important ones being <samp><span class="file">compile.exp</span></samp>, -<samp><span class="file">execute.exp</span></samp>, <samp><span class="file">dg.exp</span></samp> and <samp><span class="file">old-deja.exp</span></samp>. -To get a list of the possible <samp><span class="file">*.exp</span></samp> files, pipe the -output of ‘<samp><span class="samp">make check</span></samp>’ into a file and look at the -‘<samp><span class="samp">Running ... .exp</span></samp>’ lines. - -<h3 class="section"><a name="TOC1"></a>Passing options and running multiple testsuites</h3> +</p> +<div class="smallexample"> +<pre class="smallexample">make check-gcc RUNTESTFLAGS="execute.exp <var>other-options</var>" +</pre></div> + +<p>Likewise, in order to run only the <code>g++</code> “old-deja” tests in +the testsuite with filenames matching ‘<samp>9805*</samp>’, you would use +</p> +<div class="smallexample"> +<pre class="smallexample">make check-g++ RUNTESTFLAGS="old-deja.exp=9805* <var>other-options</var>" +</pre></div> + +<p>The <samp>*.exp</samp> files are located in the testsuite directories of the GCC +source, the most important ones being <samp>compile.exp</samp>, +<samp>execute.exp</samp>, <samp>dg.exp</samp> and <samp>old-deja.exp</samp>. +To get a list of the possible <samp>*.exp</samp> files, pipe the +output of ‘<samp>make check</samp>’ into a file and look at the +‘<samp>Running … .exp</samp>’ lines. +</p> +<a name="Passing-options-and-running-multiple-testsuites"></a> +<h3 class="section">Passing options and running multiple testsuites</h3> <p>You can pass multiple options to the testsuite using the -‘<samp><span class="samp">--target_board</span></samp>’ option of DejaGNU, either passed as part of -‘<samp><span class="samp">RUNTESTFLAGS</span></samp>’, or directly to <samp><span class="command">runtest</span></samp> if you prefer to +‘<samp>--target_board</samp>’ option of DejaGNU, either passed as part of +‘<samp>RUNTESTFLAGS</samp>’, or directly to <code>runtest</code> if you prefer to work outside the makefiles. For example, +</p> +<div class="smallexample"> +<pre class="smallexample">make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fmerge-constants" +</pre></div> -<pre class="smallexample"> make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fmerge-constants" -</pre> - <p>will run the standard <samp><span class="command">g++</span></samp> testsuites (“unix” is the target name +<p>will run the standard <code>g++</code> testsuites (“unix” is the target name for a standard native testsuite situation), passing -‘<samp><span class="samp">-O3 -fmerge-constants</span></samp>’ to the compiler on every test, i.e., +‘<samp>-O3 -fmerge-constants</samp>’ to the compiler on every test, i.e., slashes separate options. - - <p>You can run the testsuites multiple times using combinations of options +</p> +<p>You can run the testsuites multiple times using combinations of options with a syntax similar to the brace expansion of popular shells: +</p> +<div class="smallexample"> +<pre class="smallexample">…"--target_board=arm-sim\{-mhard-float,-msoft-float\}\{-O1,-O2,-O3,\}" +</pre></div> -<pre class="smallexample"> ..."--target_board=arm-sim\{-mhard-float,-msoft-float\}\{-O1,-O2,-O3,\}" -</pre> - <p>(Note the empty option caused by the trailing comma in the final group.) -The following will run each testsuite eight times using the ‘<samp><span class="samp">arm-sim</span></samp>’ +<p>(Note the empty option caused by the trailing comma in the final group.) +The following will run each testsuite eight times using the ‘<samp>arm-sim</samp>’ target, as if you had specified all possible combinations yourself: - -<pre class="smallexample"> --target_board=arm-sim/-mhard-float/-O1 - --target_board=arm-sim/-mhard-float/-O2 - --target_board=arm-sim/-mhard-float/-O3 - --target_board=arm-sim/-mhard-float - --target_board=arm-sim/-msoft-float/-O1 - --target_board=arm-sim/-msoft-float/-O2 - --target_board=arm-sim/-msoft-float/-O3 - --target_board=arm-sim/-msoft-float -</pre> - <p>They can be combined as many times as you wish, in arbitrary ways. This +</p> +<div class="smallexample"> +<pre class="smallexample">--target_board='arm-sim/-mhard-float/-O1 \ + arm-sim/-mhard-float/-O2 \ + arm-sim/-mhard-float/-O3 \ + arm-sim/-mhard-float \ + arm-sim/-msoft-float/-O1 \ + arm-sim/-msoft-float/-O2 \ + arm-sim/-msoft-float/-O3 \ + arm-sim/-msoft-float' +</pre></div> + +<p>They can be combined as many times as you wish, in arbitrary ways. This list: - -<pre class="smallexample"> ..."--target_board=unix/-Wextra\{-O3,-fno-strength\}\{-fomit-frame,\}" -</pre> - <p>will generate four combinations, all involving ‘<samp><span class="samp">-Wextra</span></samp>’. - - <p>The disadvantage to this method is that the testsuites are run in serial, +</p> +<div class="smallexample"> +<pre class="smallexample">…"--target_board=unix/-Wextra\{-O3,-fno-strength\}\{-fomit-frame,\}" +</pre></div> + +<p>will generate four combinations, all involving ‘<samp>-Wextra</samp>’. +</p> +<p>The disadvantage to this method is that the testsuites are run in serial, which is a waste on multiprocessor systems. For users with GNU Make and a shell which performs brace expansion, you can run the testsuites in -parallel by having the shell perform the combinations and <samp><span class="command">make</span></samp> -do the parallel runs. Instead of using ‘<samp><span class="samp">--target_board</span></samp>’, use a +parallel by having the shell perform the combinations and <code>make</code> +do the parallel runs. Instead of using ‘<samp>--target_board</samp>’, use a special makefile target: - -<pre class="smallexample"> make -j<var>N</var> check-<var>testsuite</var>//<var>test-target</var>/<var>option1</var>/<var>option2</var>/... -</pre> - <p>For example, - -<pre class="smallexample"> make -j3 check-gcc//sh-hms-sim/{-m1,-m2,-m3,-m3e,-m4}/{,-nofpu} -</pre> - <p>will run three concurrent “make-gcc” testsuites, eventually testing all +</p> +<div class="smallexample"> +<pre class="smallexample">make -j<var>N</var> check-<var>testsuite</var>//<var>test-target</var>/<var>option1</var>/<var>option2</var>/… +</pre></div> + +<p>For example, +</p> +<div class="smallexample"> +<pre class="smallexample">make -j3 check-gcc//sh-hms-sim/{-m1,-m2,-m3,-m3e,-m4}/{,-nofpu} +</pre></div> + +<p>will run three concurrent “make-gcc” testsuites, eventually testing all ten combinations as described above. Note that this is currently only -supported in the <samp><span class="file">gcc</span></samp> subdirectory. (To see how this works, try -typing <samp><span class="command">echo</span></samp> before the example given here.) +supported in the <samp>gcc</samp> subdirectory. (To see how this works, try +typing <code>echo</code> before the example given here.) +</p> -<h3 class="section"><a name="TOC2"></a>Additional testing for Java Class Libraries</h3> +<a name="Additional-testing-for-Java-Class-Libraries"></a> +<h3 class="section">Additional testing for Java Class Libraries</h3> -<p>The Java runtime tests can be executed via ‘<samp><span class="samp">make check</span></samp>’ -in the <samp><var>target</var><span class="file">/libjava/testsuite</span></samp> directory in +<p>The Java runtime tests can be executed via ‘<samp>make check</samp>’ +in the <samp><var>target</var>/libjava/testsuite</samp> directory in the build tree. - - <p>The <a href="http://sourceware.org/mauve/">Mauve Project</a> provides +</p> +<p>The <a href="http://sourceware.org/mauve/">Mauve Project</a> provides a suite of tests for the Java Class Libraries. This suite can be run as part of libgcj testing by placing the Mauve tree within the libjava -testsuite at <samp><span class="file">libjava/testsuite/libjava.mauve/mauve</span></samp>, or by -specifying the location of that tree when invoking ‘<samp><span class="samp">make</span></samp>’, as in -‘<samp><span class="samp">make MAUVEDIR=~/mauve check</span></samp>’. - -<h3 class="section"><a name="TOC3"></a>How to interpret test results</h3> - -<p>The result of running the testsuite are various <samp><span class="file">*.sum</span></samp> and <samp><span class="file">*.log</span></samp> -files in the testsuite subdirectories. The <samp><span class="file">*.log</span></samp> files contain a +testsuite at <samp>libjava/testsuite/libjava.mauve/mauve</samp>, or by +specifying the location of that tree when invoking ‘<samp>make</samp>’, as in +‘<samp>make MAUVEDIR=~/mauve check</samp>’. +</p> +<a name="How-to-interpret-test-results"></a> +<h3 class="section">How to interpret test results</h3> + +<p>The result of running the testsuite are various <samp>*.sum</samp> and <samp>*.log</samp> +files in the testsuite subdirectories. The <samp>*.log</samp> files contain a detailed log of the compiler invocations and the corresponding -results, the <samp><span class="file">*.sum</span></samp> files summarize the results. These summaries +results, the <samp>*.sum</samp> files summarize the results. These summaries contain status codes for all tests: - - <ul> -<li>PASS: the test passed as expected -<li>XPASS: the test unexpectedly passed -<li>FAIL: the test unexpectedly failed -<li>XFAIL: the test failed as expected -<li>UNSUPPORTED: the test is not supported on this platform -<li>ERROR: the testsuite detected an error -<li>WARNING: the testsuite detected a possible problem -</ul> - - <p>It is normal for some tests to report unexpected failures. At the +</p> +<ul> +<li> PASS: the test passed as expected +</li><li> XPASS: the test unexpectedly passed +</li><li> FAIL: the test unexpectedly failed +</li><li> XFAIL: the test failed as expected +</li><li> UNSUPPORTED: the test is not supported on this platform +</li><li> ERROR: the testsuite detected an error +</li><li> WARNING: the testsuite detected a possible problem +</li></ul> + +<p>It is normal for some tests to report unexpected failures. At the current time the testing harness does not allow fine grained control over whether or not a test is expected to fail. This problem should be fixed in future releases. +</p> -<h3 class="section"><a name="TOC4"></a>Submitting test results</h3> +<a name="Submitting-test-results"></a> +<h3 class="section">Submitting test results</h3> <p>If you want to report the results to the GCC project, use the -<samp><span class="file">contrib/test_summary</span></samp> shell script. Start it in the <var>objdir</var> with - -<pre class="smallexample"> <var>srcdir</var>/contrib/test_summary -p your_commentary.txt \ - -m gcc-testresults@gcc.gnu.org |sh -</pre> - <p>This script uses the <samp><span class="command">Mail</span></samp> program to send the results, so -make sure it is in your <samp><span class="env">PATH</span></samp>. The file <samp><span class="file">your_commentary.txt</span></samp> is +<samp>contrib/test_summary</samp> shell script. Start it in the <var>objdir</var> with +</p> +<div class="smallexample"> +<pre class="smallexample"><var>srcdir</var>/contrib/test_summary -p your_commentary.txt \ + -m gcc-testresults@gcc.gnu.org |sh +</pre></div> + +<p>This script uses the <code>Mail</code> program to send the results, so +make sure it is in your <code>PATH</code>. The file <samp>your_commentary.txt</samp> is prepended to the testsuite summary and should contain any special remarks you have on your results or your build environment. Please do not edit the testsuite result block or the subject line, as these messages may be automatically processed. +</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> -<!-- ***Final install*********************************************************** --> -<!-- ***Binaries**************************************************************** --> -<!-- ***Specific**************************************************************** --> -<!-- ***Old documentation****************************************************** --> -<!-- ***GFDL******************************************************************** --> -<!-- *************************************************************************** --> -<!-- Part 6 The End of the Document --> -</body></html> +</body> +</html> |