diff options
| author | Lorry Tar Creator <lorry-tar-importer@baserock.org> | 2013-04-11 09:13:11 +0000 |
|---|---|---|
| committer | <> | 2014-04-23 12:05:38 +0000 |
| commit | 6af3fdec2262dd94954acc5e426ef71cbd4521d3 (patch) | |
| tree | 9be02de9a80f7935892a2d03741adee44723e65d /INSTALL | |
| parent | 19be2b4342ac32e9edc78ce6fed8f61b63ae98d1 (diff) | |
| download | gcc-tarball-6af3fdec2262dd94954acc5e426ef71cbd4521d3.tar.gz | |
Imported from /home/lorry/working-area/delta_gcc-tarball/gcc-4.7.3.tar.bz2.gcc-4.7.3
Diffstat (limited to 'INSTALL')
| -rw-r--r-- | INSTALL/binaries.html | 2 | ||||
| -rw-r--r-- | INSTALL/build.html | 2 | ||||
| -rw-r--r-- | INSTALL/configure.html | 127 | ||||
| -rw-r--r-- | INSTALL/download.html | 2 | ||||
| -rw-r--r-- | INSTALL/finalinstall.html | 2 | ||||
| -rw-r--r-- | INSTALL/gfdl.html | 2 | ||||
| -rw-r--r-- | INSTALL/index.html | 2 | ||||
| -rw-r--r-- | INSTALL/old.html | 14 | ||||
| -rw-r--r-- | INSTALL/prerequisites.html | 48 | ||||
| -rw-r--r-- | INSTALL/specific.html | 326 | ||||
| -rw-r--r-- | INSTALL/test.html | 7 |
11 files changed, 317 insertions, 217 deletions
diff --git a/INSTALL/binaries.html b/INSTALL/binaries.html index f360b1a8ae..40eb488064 100644 --- a/INSTALL/binaries.html +++ b/INSTALL/binaries.html @@ -3,7 +3,7 @@ <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.13"> +<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"> <!-- diff --git a/INSTALL/build.html b/INSTALL/build.html index 644900fd69..d70e10a5a6 100644 --- a/INSTALL/build.html +++ b/INSTALL/build.html @@ -3,7 +3,7 @@ <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.13"> +<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"> <!-- diff --git a/INSTALL/configure.html b/INSTALL/configure.html index 902fa9a117..1a83c50f98 100644 --- a/INSTALL/configure.html +++ b/INSTALL/configure.html @@ -3,7 +3,7 @@ <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.13"> +<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"> <!-- @@ -197,6 +197,12 @@ 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. +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>. +See “Spec Files” in the main manual + </dl> <br><dt><code>--program-prefix=</code><var>prefix</var><dd>GCC supports some transformations of the names of its programs when @@ -312,6 +318,13 @@ 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 +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 +<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 the target platform. Unlike GCC 2.95.x and earlier, shared libraries are enabled by default on all platforms that support shared libraries. @@ -415,6 +428,19 @@ 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. +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 +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>. +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 libraries to support different target variants, calling conventions, etc. should not be built. The default is to build a @@ -423,9 +449,7 @@ 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>arc-*-elf*</code><dd>biendian. - - <br><dt><code>arm-*-*</code><dd>fpu, 26bit, underscore, interwork, biendian, nofmult. +<dt><code>arm-*-*</code><dd>fpu, 26bit, underscore, interwork, biendian, nofmult. <br><dt><code>m68*-*-*</code><dd>softfloat, m68881, m68000, m68020. @@ -437,35 +461,45 @@ sysv, aix. </dl> <br><dt><code>--with-multilib-list=</code><var>list</var><dt><code>--without-multilib-list</code><dd>Specify what multilibs to build. -Currently only implemented for sh*-*-*. +Currently only implemented for sh*-*-* and x86-64-*-linux*. - <p><var>list</var> is a comma separated list of CPU names. These must be of the + <dl> +<dt><code>sh*-*-*</code><dd><var>list</var> is a comma separated list of CPU names. These must be of the form <code>sh*</code> or <code>m*</code> (in which case they match the compiler option for that processor). The list should not contain any endian options - these are handled by <samp><span class="option">--with-endian</span></samp>. - <p>If <var>list</var> is empty, then there will be no multilibs for extra + <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> + <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>’ (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 + <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 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>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 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>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 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 +<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. +</dl> + <br><dt><code>--with-endian=</code><var>endians</var><dd>Specify what endians to use. Currently only implemented for sh*-*-*. @@ -499,24 +533,15 @@ 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>gnat</code><dd>Ada tasking support. For non-Ada programs, this setting is equivalent -to ‘<samp><span class="samp">single</span></samp>’. When used in conjunction with the Ada run time, it -causes GCC to use the same thread primitives as Ada uses. This option -is necessary when using both Ada and the back end exception handling, -which is the default for most Ada targets. -<br><dt><code>mach</code><dd>Generic MACH thread support, known to work on NeXTSTEP. (Please note -that the file needed to support this configuration, <samp><span class="file">gthr-mach.h</span></samp>, is -missing and thus this setting will cause a known bootstrap failure.) +<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>posix95</code><dd>Generic POSIX/Unix95 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>solaris</code><dd>Sun Solaris 2/Unix International thread support. Only use this if you -really need to use this legacy API instead of the default, ‘<samp><span class="samp">posix</span></samp>’. +<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. -<br><dt><code>nks</code><dd>Novell Kernel Services thread support. </dl> <br><dt><code>--enable-tls</code><dd>Specify that the target supports TLS (Thread Local Storage). Usually @@ -546,6 +571,10 @@ 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>. 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, +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. @@ -563,7 +592,7 @@ systems that support conditional traps). <!-- 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-lsc</span></samp> option is passed. This is the default for +<samp><span class="option">-mno-llsc</span></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. @@ -588,7 +617,7 @@ 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-indirect-function</code><dd>Define if you want to enable the <code>ifunc</code> attribute. This option is + <br><dt><code>--enable-gnu-indirect-function</code><dd>Define if you want to enable the <code>ifunc</code> attribute. This option is currently only available on systems with GNU libc on certain targets. <br><dt><code>--enable-target-optspace</code><dd>Specify that target @@ -611,6 +640,11 @@ will try to guess whether the <code>.init_array</code> and <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 disabled. This is because it can only be rebuilt if the complete source @@ -712,8 +746,8 @@ 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. On mips-linux, this will build a tri-arch compiler (ABI o32/n32/64), defaulted to o32. -Currently, this option only affects sparc-linux, powerpc-linux, x86-linux -and mips-linux. +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. See “RS/6000 and PowerPC Options” in the main manual @@ -844,10 +878,11 @@ 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 do not have GMP (the GNU Multiple Precision library), the MPFR + <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 library and/or the MPC library installed in a standard location and -you want to build GCC, you can explicitly specify the directory where -they are installed (‘<samp><span class="samp">--with-gmp=</span><var>gmpinstalldir</var></samp>’, +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 @@ -922,6 +957,10 @@ option), if the linker supports it. If you specify 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 +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 static data members and inline function local statics. Enabled by default for a native toolchain with an assembler that accepts it and @@ -945,7 +984,7 @@ See <samp><span class="option">-fuse-linker-plugin</span></samp> for details. <dt><code>--with-sysroot</code><dt><code>--with-sysroot=</code><var>dir</var><dd>Tells GCC to consider <var>dir</var> as the root of a tree that contains (a subset of) the root filesystem of the target operating system. Target system headers, libraries and run-time object files will be -searched in there. More specifically, this acts as if +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 compiler. The specified directory is not copied into the install tree, unlike the options <samp><span class="option">--with-headers</span></samp> and @@ -960,6 +999,10 @@ 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> +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 @@ -972,6 +1015,10 @@ which you are installing GCC and your target libraries. 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> +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. The <var>dir</var> argument specifies a directory which has the target include @@ -997,6 +1044,15 @@ 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 +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>. +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.) 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 @@ -1157,6 +1213,9 @@ not specified, then the Python modules are installed in $(prefix)/share/python. <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 +libraries. + <dl> <dt><code>ansi</code><dd>Use the single-byte <code>char</code> and the Win32 A functions natively, translating to and from UNICODE when using these functions. If diff --git a/INSTALL/download.html b/INSTALL/download.html index 68d0ba324c..cbd0cffbca 100644 --- a/INSTALL/download.html +++ b/INSTALL/download.html @@ -3,7 +3,7 @@ <title>Downloading GCC</title> <meta http-equiv="Content-Type" content="text/html"> <meta name="description" content="Downloading GCC"> -<meta name="generator" content="makeinfo 4.13"> +<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"> <!-- diff --git a/INSTALL/finalinstall.html b/INSTALL/finalinstall.html index 73b882093b..04c4e43bd4 100644 --- a/INSTALL/finalinstall.html +++ b/INSTALL/finalinstall.html @@ -3,7 +3,7 @@ <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.13"> +<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"> <!-- diff --git a/INSTALL/gfdl.html b/INSTALL/gfdl.html index d4f387c888..0e8c13d826 100644 --- a/INSTALL/gfdl.html +++ b/INSTALL/gfdl.html @@ -3,7 +3,7 @@ <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.13"> +<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"> <!-- diff --git a/INSTALL/index.html b/INSTALL/index.html index 9b294f2c01..6dbc332332 100644 --- a/INSTALL/index.html +++ b/INSTALL/index.html @@ -3,7 +3,7 @@ <title>Installing GCC</title> <meta http-equiv="Content-Type" content="text/html"> <meta name="description" content="Installing GCC"> -<meta name="generator" content="makeinfo 4.13"> +<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"> <!-- diff --git a/INSTALL/old.html b/INSTALL/old.html index b0e26b99ac..370568e1ff 100644 --- a/INSTALL/old.html +++ b/INSTALL/old.html @@ -3,7 +3,7 @@ <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.13"> +<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"> <!-- @@ -115,7 +115,7 @@ Here are the possible CPU types: <!-- 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, hppa1.0, hppa1.1, i370, i386, i486, i586, i686, i786, i860, i960, ip2k, m32r, -m68000, m68k, m6811, m6812, m88k, mcore, mips, mipsel, mips64, mips64el, +m68000, m68k, m88k, mcore, mips, mipsel, mips64, mips64el, mn10200, mn10300, ns32k, pdp11, powerpc, powerpcle, romp, rs6000, sh, sparc, sparclite, sparc64, v850, vax, we32k. </blockquote> @@ -193,16 +193,6 @@ sun4, symmetry, tower-32, tower. <p class="noindent">Remember that a machine name specifies both the cpu type and the company name. -If you want to install your own homemade configuration files, you can -use ‘<samp><span class="samp">local</span></samp>’ as the company name to access them. If you use -configuration ‘<samp><var>cpu</var><span class="samp">-local</span></samp>’, the configuration name -without the cpu prefix -is used to form the configuration file names. - - <p>Thus, if you specify ‘<samp><span class="samp">m68k-local</span></samp>’, configuration uses -files <samp><span class="file">m68k.md</span></samp>, <samp><span class="file">local.h</span></samp>, <samp><span class="file">m68k.c</span></samp>, -<samp><span class="file">xm-local.h</span></samp>, <samp><span class="file">t-local</span></samp>, and <samp><span class="file">x-local</span></samp>, all in the -directory <samp><span class="file">config/m68k</span></samp>. <hr /> <p><a href="./index.html">Return to the GCC Installation page</a> diff --git a/INSTALL/prerequisites.html b/INSTALL/prerequisites.html index f5d374626b..2d3d972e9c 100644 --- a/INSTALL/prerequisites.html +++ b/INSTALL/prerequisites.html @@ -3,7 +3,7 @@ <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.13"> +<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"> <!-- @@ -107,10 +107,8 @@ systems' <samp><span class="command">tar</span></samp> programs will also work, 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>. A helper -script needs ‘<samp><span class="samp">Glob.pm</span></samp>’, which is missing from <samp><span class="command">perl</span></samp> 5.005 -included in Solaris 8. The bundled <samp><span class="command">perl</span></samp> in Solaris 9 and up -works. +<samp><span class="option">--disable-symvers</span></samp>. The bundled <samp><span class="command">perl</span></samp> 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>. @@ -128,34 +126,36 @@ 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 documented. We appreciate bug reports about problems with -newer versions, though. +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 you do not have it installed in your -library search path, you will have to configure with the +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 +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>. Alternatively, 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 together with GCC. +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 -<a href="http://www.mpfr.org/">http://www.mpfr.org/</a>. The <samp><span class="option">--with-mpfr</span></samp> configure -option should be used if your MPFR Library is not installed in your -default library search path. See also <samp><span class="option">--with-mpfr-lib</span></samp> and -<samp><span class="option">--with-mpfr-include</span></samp>. Alternatively, if a MPFR source -distribution is found in a subdirectory of your GCC sources named -<samp><span class="file">mpfr</span></samp>, it will be built together with GCC. +<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 +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 -<a href="http://www.multiprecision.org/">http://www.multiprecision.org/</a>. The <samp><span class="option">--with-mpc</span></samp> -configure option should be used if your MPC Library is not installed -in your default library search path. See also <samp><span class="option">--with-mpc-lib</span></samp> -and <samp><span class="option">--with-mpc-include</span></samp>. Alternatively, if an MPC source -distribution is found in a subdirectory of your GCC sources named -<samp><span class="file">mpc</span></samp>, it will be built together with GCC. +<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 +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. @@ -271,7 +271,7 @@ the GCC-specific entry point. You can download a suitable jar from <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 -searched in system locations but can be configured with +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 diff --git a/INSTALL/specific.html b/INSTALL/specific.html index 86c987b08f..3de182f62d 100644 --- a/INSTALL/specific.html +++ b/INSTALL/specific.html @@ -3,7 +3,7 @@ <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.13"> +<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"> <!-- @@ -54,8 +54,8 @@ 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="#arc-x-elf">arc-*-elf</a> -<li><a href="#arm-x-elf">arm-*-elf</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> @@ -76,8 +76,6 @@ information are. <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="#m6811-elf">m6811-elf</a> -<li><a href="#m6812-elf">m6812-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> @@ -105,8 +103,12 @@ information are. <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> @@ -144,10 +146,12 @@ shared libraries. 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>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.) As of GCC 4.6, support for Tru64 UNIX V4.0 and V5.0 has been -removed. + <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 @@ -157,10 +161,14 @@ or applying the patch in 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.21, neither GNU <samp><span class="command">as</span></samp> nor GNU <samp><span class="command">ld</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 @@ -188,19 +196,18 @@ provide a fix shortly. <!-- FIXME: still applicable? --> <p><hr /> -<h3 class="heading"><a name="TOC2"></a><a name="arc_002dx_002delf"></a>arc-*-elf</h3> +<h3 class="heading"><a name="TOC2"></a><a name="amd64_002dx_002dsolaris210"></a>amd64-*-solaris2.1[0-9]*</h3> -<p>Argonaut ARC processor. -This configuration is intended for embedded systems. +<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_002delf"></a>arm-*-elf</h3> +<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-*-freebsd</code>, <code>arm-*-netbsdelf</code>, <code>arm-*-*linux</code> -and <code>arm-*-rtems</code>. +<code>arm-*-netbsdelf</code>, <code>arm-*-*linux-gnueabi*</code> +and <code>arm-*-rtemseabi</code>. <p><hr /> @@ -240,7 +247,22 @@ is available at <a href="http://blackfin.uclinux.org">http://blackfin.uclinux.or <p><hr /> -<h3 class="heading"><a name="TOC6"></a><a name="cris"></a>CRIS</h3> +<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>CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip series. These are used in embedded applications. @@ -266,25 +288,6 @@ information about this platform is available at <p><hr /> -<h3 class="heading"><a name="TOC7"></a><a name="crx"></a>CRX</h3> - -<p>The CRX CompactRISC architecture is a low-power 32-bit architecture with -fast context switching and architectural extensibility features. - - <p>See “CRX Options” in the main manual for a list of CRX-specific options. - - <p>Use ‘<samp><span class="samp">configure --target=crx-elf --enable-languages=c,c++</span></samp>’ to configure -GCC for building a CRX cross-compiler. The option ‘<samp><span class="samp">--target=crx-elf</span></samp>’ -is also used to build the ‘<samp><span class="samp">newlib</span></samp>’ C library for CRX. - - <p>It is also possible to build libstdc++-v3 for the CRX architecture. This -needs to be done in a separate step with the following configure settings: - -<pre class="smallexample"> gcc/libstdc++-v3/configure --host=crx-elf --with-newlib \ - --enable-sjlj-exceptions --enable-cxx-flags='-fexceptions -frtti' -</pre> - <p><hr /> - <h3 class="heading"><a name="TOC8"></a><a name="dos"></a>DOS</h3> <p>Please have a look at the <a href="binaries.html">binaries page</a>. @@ -296,7 +299,14 @@ and includes all the necessary compilation tools and libraries. <p><hr /> -<h3 class="heading"><a name="TOC9"></a><a name="x_002dx_002dfreebsd"></a>*-*-freebsd*</h3> +<h3 class="heading"><a name="TOC9"></a><a name="epiphany_002dx_002delf"></a>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>Support for FreeBSD 1 was discontinued in GCC 3.2. Support for FreeBSD 2 (and any mutant a.out variants of FreeBSD 3) was @@ -333,7 +343,7 @@ the FreeBSD 7.0 release with GNU binutils after 2.16.1. <p><hr /> -<h3 class="heading"><a name="TOC10"></a><a name="h8300_002dhms"></a>h8300-hms</h3> +<h3 class="heading"><a name="TOC11"></a><a name="h8300_002dhms"></a>h8300-hms</h3> <p>Renesas H8/300 series of processors. @@ -346,7 +356,7 @@ longer a multiple of 2 bytes. <p><hr /> -<h3 class="heading"><a name="TOC11"></a><a name="hppa_002dhp_002dhpux"></a>hppa*-hp-hpux*</h3> +<h3 class="heading"><a name="TOC12"></a><a name="hppa_002dhp_002dhpux"></a>hppa*-hp-hpux*</h3> <p>Support for HP-UX version 9 and older was discontinued in GCC 3.4. @@ -398,7 +408,7 @@ a list of the predefines used with each standard. <p><hr /> -<h3 class="heading"><a name="TOC12"></a><a name="hppa_002dhp_002dhpux10"></a>hppa*-hp-hpux10</h3> +<h3 class="heading"><a name="TOC13"></a><a name="hppa_002dhp_002dhpux10"></a>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. @@ -410,7 +420,7 @@ with the one implemented under HP-UX 11 using secondary definitions. <p><hr /> -<h3 class="heading"><a name="TOC13"></a><a name="hppa_002dhp_002dhpux11"></a>hppa*-hp-hpux11</h3> +<h3 class="heading"><a name="TOC14"></a><a name="hppa_002dhp_002dhpux11"></a>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. @@ -519,7 +529,7 @@ supported, so <samp><span class="option">--enable-threads=dce</span></samp> does <p><hr /> -<h3 class="heading"><a name="TOC14"></a><a name="x_002dx_002dlinux_002dgnu"></a>*-*-linux-gnu</h3> +<h3 class="heading"><a name="TOC15"></a><a name="x_002dx_002dlinux_002dgnu"></a>*-*-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 @@ -527,7 +537,7 @@ libstdc++-v3 documentation. <p><hr /> -<h3 class="heading"><a name="TOC15"></a><a name="ix86_002dx_002dlinux"></a>i?86-*-linux*</h3> +<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. See <a href="http://gcc.gnu.org/PR10877">bug 10877</a> for more information. @@ -538,13 +548,13 @@ found on <a href="http://www.bitwizard.nl/sig11/">www.bitwizard.nl</a>. <p><hr /> -<h3 class="heading"><a name="TOC16"></a><a name="ix86_002dx_002dsolaris289"></a>i?86-*-solaris2.[89]</h3> +<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. 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.21, is known to +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 @@ -558,19 +568,18 @@ you have the patch installed, you can configure GCC with an appropriate <p><hr /> -<h3 class="heading"><a name="TOC17"></a><a name="ix86_002dx_002dsolaris210"></a>i?86-*-solaris2.10</h3> +<h3 class="heading"><a name="TOC18"></a><a name="ix86_002dx_002dsolaris210"></a>i?86-*-solaris2.10</h3> -<p>Use this for Solaris 10 or later on x86 and x86-64 systems. This -configuration is supported by GCC 4.0 and later versions only. Unlike -‘<samp><span class="samp">sparcv9-sun-solaris2*</span></samp>’, there is no corresponding 64-bit -configuration like ‘<samp><span class="samp">amd64-*-solaris2*</span></samp>’ or ‘<samp><span class="samp">x86_64-*-solaris2*</span></samp>’. -<!-- FIXME: will there ever be? --> +<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 binutils 2.15, and Solaris 11, from GNU binutils 2.19, work fine, although the current version, from GNU binutils -2.21, is known to work, too. Recent versions of the Sun assembler in +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? --> @@ -578,7 +587,7 @@ although the current version, from GNU binutils linker instead, which is available in <samp><span class="file">/usr/sfw/bin/gld</span></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.21. +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 @@ -588,7 +597,7 @@ guarantee use of Sun <samp><span class="command">ld</span></samp>. <p><hr /> -<h3 class="heading"><a name="TOC18"></a><a name="ia64_002dx_002dlinux"></a>ia64-*-linux</h3> +<h3 class="heading"><a name="TOC19"></a><a name="ia64_002dx_002dlinux"></a>ia64-*-linux</h3> <p>IA-64 processor (also known as IPF, or Itanium Processor Family) running GNU/Linux. @@ -608,7 +617,7 @@ more major ABI changes are expected. <p><hr /> -<h3 class="heading"><a name="TOC19"></a><a name="ia64_002dx_002dhpux"></a>ia64-*-hpux*</h3> +<h3 class="heading"><a name="TOC20"></a><a name="ia64_002dx_002dhpux"></a>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, @@ -623,7 +632,7 @@ removed and the system libunwind library will always be used. <p><hr /> <!-- rs6000-ibm-aix*, powerpc-ibm-aix* --> -<h3 class="heading"><a name="TOC20"></a><a name="x_002dibm_002daix"></a>*-ibm-aix*</h3> +<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. Support for AIX version 4.2 and older was discontinued in GCC 4.5. @@ -674,6 +683,15 @@ 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 +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 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 @@ -753,56 +771,42 @@ switch and using the configure option <samp><span class="option">--with-cpu-</sp <p><hr /> -<h3 class="heading"><a name="TOC21"></a><a name="iq2000_002dx_002delf"></a>iq2000-*-elf</h3> +<h3 class="heading"><a name="TOC22"></a><a name="iq2000_002dx_002delf"></a>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="TOC22"></a><a name="lm32_002dx_002delf"></a>lm32-*-elf</h3> +<h3 class="heading"><a name="TOC23"></a><a name="lm32_002dx_002delf"></a>lm32-*-elf</h3> <p>Lattice Mico32 processor. This configuration is intended for embedded systems. <p><hr /> -<h3 class="heading"><a name="TOC23"></a><a name="lm32_002dx_002duclinux"></a>lm32-*-uclinux</h3> +<h3 class="heading"><a name="TOC24"></a><a name="lm32_002dx_002duclinux"></a>lm32-*-uclinux</h3> <p>Lattice Mico32 processor. This configuration is intended for embedded systems running uClinux. <p><hr /> -<h3 class="heading"><a name="TOC24"></a><a name="m32c_002dx_002delf"></a>m32c-*-elf</h3> +<h3 class="heading"><a name="TOC25"></a><a name="m32c_002dx_002delf"></a>m32c-*-elf</h3> <p>Renesas M32C processor. This configuration is intended for embedded systems. <p><hr /> -<h3 class="heading"><a name="TOC25"></a><a name="m32r_002dx_002delf"></a>m32r-*-elf</h3> +<h3 class="heading"><a name="TOC26"></a><a name="m32r_002dx_002delf"></a>m32r-*-elf</h3> <p>Renesas M32R processor. This configuration is intended for embedded systems. <p><hr /> -<h3 class="heading"><a name="TOC26"></a><a name="m6811_002delf"></a>m6811-elf</h3> - -<p>Motorola 68HC11 family micro controllers. These are used in embedded -applications. There are no standard Unix configurations. - - <p><hr /> - -<h3 class="heading"><a name="TOC27"></a><a name="m6812_002delf"></a>m6812-elf</h3> - -<p>Motorola 68HC12 family micro controllers. These are used in embedded -applications. There are no standard Unix configurations. - - <p><hr /> - -<h3 class="heading"><a name="TOC28"></a><a name="m68k_002dx_002dx"></a>m68k-*-*</h3> +<h3 class="heading"><a name="TOC27"></a><a name="m68k_002dx_002dx"></a>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 @@ -826,34 +830,34 @@ be a <samp><span class="option">-mcpu</span></samp> argument or one of the follo ‘<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="TOC29"></a><a name="m68k_002dx_002duclinux"></a>m68k-*-uclinux</h3> +<h3 class="heading"><a name="TOC28"></a><a name="m68k_002dx_002duclinux"></a>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. It also added improved support for C++ and flat shared libraries, -both of which were ABI changes. However, you can still use the -original ABI by configuring for ‘<samp><span class="samp">m68k-uclinuxoldabi</span></samp>’ or -‘<samp><span class="samp">m68k-</span><var>vendor</var><span class="samp">-uclinuxoldabi</span></samp>’. +both of which were ABI changes. <p><hr /> -<h3 class="heading"><a name="TOC30"></a><a name="mep_002dx_002delf"></a>mep-*-elf</h3> +<h3 class="heading"><a name="TOC29"></a><a name="mep_002dx_002delf"></a>mep-*-elf</h3> <p>Toshiba Media embedded Processor. This configuration is intended for embedded systems. <p><hr /> -<h3 class="heading"><a name="TOC31"></a><a name="microblaze_002dx_002delf"></a>microblaze-*-elf</h3> +<h3 class="heading"><a name="TOC30"></a><a name="microblaze_002dx_002delf"></a>microblaze-*-elf</h3> <p>Xilinx MicroBlaze processor. This configuration is intended for embedded systems. <p><hr /> -<h3 class="heading"><a name="TOC32"></a><a name="mips_002dx_002dx"></a>mips-*-*</h3> +<h3 class="heading"><a name="TOC31"></a><a name="mips_002dx_002dx"></a>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 @@ -894,12 +898,6 @@ the use of break, use the <samp><span class="option">--with-divide=breaks</span> <samp><span class="command">configure</span></samp> option when configuring GCC. The default is to use traps on systems that support them. - <p>Cross-compilers for the MIPS as target using the MIPS assembler -currently do not work, because the auxiliary programs -<samp><span class="file">mips-tdump.c</span></samp> and <samp><span class="file">mips-tfile.c</span></samp> can't be compiled on -anything but a MIPS. It does work to cross compile for a MIPS -if you use the GNU assembler and linker. - <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 @@ -910,19 +908,21 @@ made after Nov. 9, 2006) should be free from both of these problems. <p><hr /> -<h3 class="heading"><a name="TOC33"></a><a name="mips_002dsgi_002dirix5"></a>mips-sgi-irix5</h3> +<h3 class="heading"><a name="TOC32"></a><a name="mips_002dsgi_002dirix5"></a>mips-sgi-irix5</h3> <p>Support for IRIX 5 has been removed in GCC 4.6. <p><hr /> -<h3 class="heading"><a name="TOC34"></a><a name="mips_002dsgi_002dirix6"></a>mips-sgi-irix6</h3> +<h3 class="heading"><a name="TOC33"></a><a name="mips_002dsgi_002dirix6"></a>mips-sgi-irix6</h3> -<p>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>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 @@ -977,7 +977,7 @@ Look for <samp><span class="file">/usr/lib64/libc.so.1</span></samp> to see if y 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.21, is known to work. On the other hand, bootstrap fails +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> @@ -997,14 +997,14 @@ and in order to build GCC for such targets you need to configure with <p><hr /> -<h3 class="heading"><a name="TOC35"></a><a name="moxie_002dx_002delf"></a>moxie-*-elf</h3> +<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="TOC36"></a><a name="powerpc_002dx_002dx"></a>powerpc-*-*</h3> +<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>. @@ -1015,7 +1015,7 @@ or newer for a working GCC. <p><hr /> -<h3 class="heading"><a name="TOC37"></a><a name="powerpc_002dx_002ddarwin"></a>powerpc-*-darwin*</h3> +<h3 class="heading"><a name="TOC36"></a><a name="powerpc_002dx_002ddarwin"></a>powerpc-*-darwin*</h3> <p>PowerPC running Darwin (Mac OS X kernel). @@ -1031,56 +1031,63 @@ on systems older than 10.3.9 (aka darwin7.9.0). <p><hr /> -<h3 class="heading"><a name="TOC38"></a><a name="powerpc_002dx_002delf"></a>powerpc-*-elf</h3> +<h3 class="heading"><a name="TOC37"></a><a name="powerpc_002dx_002delf"></a>powerpc-*-elf</h3> <p>PowerPC system in big endian mode, running System V.4. <p><hr /> -<h3 class="heading"><a name="TOC39"></a><a name="powerpc_002dx_002dlinux_002dgnu"></a>powerpc*-*-linux-gnu*</h3> +<h3 class="heading"><a name="TOC38"></a><a name="powerpc_002dx_002dlinux_002dgnu"></a>powerpc*-*-linux-gnu*</h3> <p>PowerPC system in big endian mode running Linux. <p><hr /> -<h3 class="heading"><a name="TOC40"></a><a name="powerpc_002dx_002dnetbsd"></a>powerpc-*-netbsd*</h3> +<h3 class="heading"><a name="TOC39"></a><a name="powerpc_002dx_002dnetbsd"></a>powerpc-*-netbsd*</h3> <p>PowerPC system in big endian mode running NetBSD. <p><hr /> -<h3 class="heading"><a name="TOC41"></a><a name="powerpc_002dx_002deabisim"></a>powerpc-*-eabisim</h3> +<h3 class="heading"><a name="TOC40"></a><a name="powerpc_002dx_002deabisim"></a>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="TOC42"></a><a name="powerpc_002dx_002deabi"></a>powerpc-*-eabi</h3> +<h3 class="heading"><a name="TOC41"></a><a name="powerpc_002dx_002deabi"></a>powerpc-*-eabi</h3> <p>Embedded PowerPC system in big endian mode. <p><hr /> -<h3 class="heading"><a name="TOC43"></a><a name="powerpcle_002dx_002delf"></a>powerpcle-*-elf</h3> +<h3 class="heading"><a name="TOC42"></a><a name="powerpcle_002dx_002delf"></a>powerpcle-*-elf</h3> <p>PowerPC system in little endian mode, running System V.4. <p><hr /> -<h3 class="heading"><a name="TOC44"></a><a name="powerpcle_002dx_002deabisim"></a>powerpcle-*-eabisim</h3> +<h3 class="heading"><a name="TOC43"></a><a name="powerpcle_002dx_002deabisim"></a>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="TOC45"></a><a name="powerpcle_002dx_002deabi"></a>powerpcle-*-eabi</h3> +<h3 class="heading"><a name="TOC44"></a><a name="powerpcle_002dx_002deabi"></a>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. +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>The Renesas RX processor. See @@ -1113,10 +1120,14 @@ supported as cross-compilation target only. <h3 class="heading"><a name="TOC50"></a><a name="x_002dx_002dsolaris2"></a>*-*-solaris2*</h3> -<p>Support for Solaris 7 has been removed in GCC 4.6. +<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, though you can download -the Sun Studio compilers for free. Alternatively, + <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, you can install a pre-built GCC to bootstrap and install GCC. See the <a href="binaries.html">binaries page</a> for details. @@ -1156,17 +1167,19 @@ have <samp><span class="file">/usr/xpg4/bin</span></samp> in your <samp><span cl conjunction with the Sun linker. The GNU <samp><span class="command">as</span></samp> 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.21) +<samp><span class="file">/usr/sfw/bin/gas</span></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> is known to -cause memory corruption at runtime in some cases for C++ programs. +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 Solaris 10 cannot be used due to several bugs. Again, the current -version (2.21) is known to work, but generally lacks platform specific -features, so better stay with Sun <samp><span class="command">ld</span></samp>. +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 @@ -1197,10 +1210,10 @@ testsuite failures appear. 117351-12 or newer for Intel) and 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 libraries, -‘<samp><span class="samp">libpthread</span></samp>’ and ‘<samp><span class="samp">libthread</span></samp>’. They are required for TLS -support and have been made the default in Solaris 9, so they are always -used on Solaris 8. + <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 @@ -1314,9 +1327,9 @@ releases mishandled unaligned relocations on <code>sparc-*-*</code> targets. <h3 class="heading"><a name="TOC55"></a><a name="sparc64_002dx_002dsolaris2"></a>sparc64-*-solaris2*</h3> -<p>When configuring the GNU Multiple Precision Library (GMP) or the -MPFR library, the canonical target triplet must be specified as -the <samp><span class="command">build</span></samp> parameter on the configure line. For example +<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 on a Solaris 9 system: <pre class="smallexample"> % ./configure --build=sparc64-sun-solaris2.9 --prefix=xxx @@ -1337,7 +1350,27 @@ and <samp><span class="option">-xildoff</span></samp> turns off the incremental <p><hr /> -<h3 class="heading"><a name="TOC57"></a><a name="x_002dx_002dvxworks"></a>*-*-vxworks*</h3> +<h3 class="heading"><a name="TOC57"></a><a name="c6x_002dx_002dx"></a>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>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>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. @@ -1372,7 +1405,7 @@ VxWorks will incorporate this module.) <p><hr /> -<h3 class="heading"><a name="TOC58"></a><a name="x86_002d64_002dx_002dx"></a>x86_64-*-*, amd64-*-*</h3> +<h3 class="heading"><a name="TOC61"></a><a name="x86_002d64_002dx_002dx"></a>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. @@ -1381,7 +1414,22 @@ both 64-bit x86-64 and 32-bit x86 code (via the <samp><span class="option">-m32< <p><hr /> -<h3 class="heading"><a name="TOC59"></a><a name="xtensa_002dx_002delf"></a>xtensa*-*-elf</h3> +<h3 class="heading"><a name="TOC62"></a><a name="x86_002d64_002dx_002dsolaris210"></a>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 +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 +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> <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 @@ -1398,7 +1446,7 @@ which you can use to replace the default header file. <p><hr /> -<h3 class="heading"><a name="TOC60"></a><a name="xtensa_002dx_002dlinux"></a>xtensa*-*-linux*</h3> +<h3 class="heading"><a name="TOC64"></a><a name="xtensa_002dx_002dlinux"></a>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 @@ -1409,9 +1457,9 @@ respects, this target is the same as the <p><hr /> -<h3 class="heading"><a name="TOC61"></a><a name="windows"></a>Microsoft Windows</h3> +<h3 class="heading"><a name="TOC65"></a><a name="windows"></a>Microsoft Windows</h3> -<h4 class="subheading"><a name="TOC62"></a>Intel 16-bit versions</h4> +<h4 class="subheading"><a name="TOC66"></a>Intel 16-bit versions</h4> <p>The 16-bit versions of Microsoft Windows, such as Windows 3.1, are not supported. @@ -1419,7 +1467,7 @@ supported. <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="TOC63"></a>Intel 32-bit versions</h4> +<h4 class="subheading"><a name="TOC67"></a>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 @@ -1437,7 +1485,7 @@ the Win32 subsystem that provides a subset of POSIX. <a href="http://www.mkssoftware.com/">http://www.mkssoftware.com/</a> for more information. </ul> -<h4 class="subheading"><a name="TOC64"></a>Intel 64-bit versions</h4> +<h4 class="subheading"><a name="TOC68"></a>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>. @@ -1445,12 +1493,12 @@ 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="TOC65"></a>Windows CE</h4> +<h4 class="subheading"><a name="TOC69"></a>Windows CE</h4> -<p>Windows CE is supported as a target only on ARM (arm-wince-pe), Hitachi +<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="TOC66"></a>Other Windows Platforms</h4> +<h4 class="subheading"><a name="TOC70"></a>Other Windows Platforms</h4> <p>GCC no longer supports Windows NT on the Alpha or PowerPC. @@ -1466,7 +1514,7 @@ be inactive. See <a href="http://pw32.sourceforge.net/">http://pw32.sourceforge <p><hr /> -<h3 class="heading"><a name="TOC67"></a><a name="x_002dx_002dcygwin"></a>*-*-cygwin</h3> +<h3 class="heading"><a name="TOC71"></a><a name="x_002dx_002dcygwin"></a>*-*-cygwin</h3> <p>Ports of GCC are included with the <a href="http://www.cygwin.com/">Cygwin environment</a>. @@ -1482,7 +1530,7 @@ or version 2.20 or above if building your own. <p><hr /> -<h3 class="heading"><a name="TOC68"></a><a name="x_002dx_002dinterix"></a>*-*-interix</h3> +<h3 class="heading"><a name="TOC72"></a><a name="x_002dx_002dinterix"></a>*-*-interix</h3> <p>The Interix target is used by OpenNT, Interix, Services For UNIX (SFU), and Subsystem for UNIX-based Applications (SUA). Applications compiled @@ -1491,7 +1539,7 @@ the Win32 subsystem. This target was last known to work in GCC 3.3. <p><hr /> -<h3 class="heading"><a name="TOC69"></a><a name="x_002dx_002dmingw32"></a>*-*-mingw32</h3> +<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. Earlier versions of headers are incompatible with the new default semantics @@ -1499,7 +1547,7 @@ of <code>extern inline</code> in <code>-std=c99</code> and <code>-std=gnu99</cod <p><hr /> -<h3 class="heading"><a name="TOC70"></a><a name="older"></a>Older systems</h3> +<h3 class="heading"><a name="TOC74"></a><a name="older"></a>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 @@ -1543,7 +1591,7 @@ current GCC) is to be found in the GCC texinfo manual. <p><hr /> -<h3 class="heading"><a name="TOC71"></a><a name="elf"></a>all ELF targets (SVR4, Solaris 2, etc.)</h3> +<h3 class="heading"><a name="TOC75"></a><a name="elf"></a>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 diff --git a/INSTALL/test.html b/INSTALL/test.html index ce8556bd61..359bfec9de 100644 --- a/INSTALL/test.html +++ b/INSTALL/test.html @@ -3,7 +3,7 @@ <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.13"> +<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"> <!-- @@ -90,7 +90,10 @@ on a simulator as described at <a href="http://gcc.gnu.org/simtest-howto.html">h <h3 class="section"><a name="TOC0"></a>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 ‘<samp><span class="samp">make check-g++</span></samp>’ +‘<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. |