diff options
Diffstat (limited to 'gcc-4.8/INSTALL/specific.html')
| -rw-r--r-- | gcc-4.8/INSTALL/specific.html | 84 |
1 files changed, 42 insertions, 42 deletions
diff --git a/gcc-4.8/INSTALL/specific.html b/gcc-4.8/INSTALL/specific.html index caf81b60b..f4cbbe229 100644 --- a/gcc-4.8/INSTALL/specific.html +++ b/gcc-4.8/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"> <!-- @@ -47,7 +47,7 @@ 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 have to. +information have to. <ul> <li><a href="#alpha-x-x">alpha*-*-*</a> @@ -169,7 +169,7 @@ and <code>arm-*-rtemseabi</code>. <h3 class="heading"><a name="TOC4"></a><a name="avr"></a>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. @@ -194,7 +194,7 @@ can also be obtained from: <h3 class="heading"><a name="TOC5"></a><a name="bfin"></a>Blackfin</h3> -<p>The Blackfin processor, an Analog Devices DSP. +<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, @@ -204,7 +204,7 @@ is available at <a href="http://blackfin.uclinux.org">http://blackfin.uclinux.or <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 +<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. @@ -256,7 +256,7 @@ and includes all the necessary compilation tools and libraries. <h3 class="heading"><a name="TOC9"></a><a name="epiphany_002dx_002delf"></a>epiphany-*-elf</h3> -<p>Adapteva Epiphany. +<p>Adapteva Epiphany. This configuration is intended for embedded systems. <p><hr /> @@ -339,7 +339,7 @@ build many C++ applications. <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. @@ -350,7 +350,7 @@ 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. +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 @@ -402,20 +402,20 @@ command. <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 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. +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 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. +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. @@ -450,7 +450,7 @@ the currently recommended linker patch for your system. <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. @@ -494,7 +494,7 @@ libstdc++-v3 documentation. <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>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 @@ -505,7 +505,7 @@ found on <a href="http://www.bitwizard.nl/sig11/">www.bitwizard.nl</a>. <h3 class="heading"><a name="TOC17"></a><a name="ix86_002dx_002dsolaris29"></a>i?86-*-solaris2.9</h3> -<p>The Sun assembler in Solaris 9 has several bugs and limitations. +<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 @@ -564,9 +564,9 @@ later. <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. @@ -580,7 +580,7 @@ the option <samp><span class="option">--with-gnu-as</span></samp> may be necessa <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. +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 removed and the system libunwind library will always be used. @@ -589,7 +589,7 @@ removed and the system libunwind library will always be used. <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>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 @@ -686,7 +686,7 @@ executable. <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> @@ -736,28 +736,28 @@ applications. There are no standard Unix configurations. <h3 class="heading"><a name="TOC23"></a><a name="lm32_002dx_002delf"></a>lm32-*-elf</h3> -<p>Lattice Mico32 processor. +<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>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>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>Renesas M32R processor. This configuration is intended for embedded systems. <p><hr /> @@ -801,14 +801,14 @@ both of which were ABI changes. <h3 class="heading"><a name="TOC29"></a><a name="mep_002dx_002delf"></a>mep-*-elf</h3> -<p>Toshiba Media embedded Processor. +<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>Xilinx MicroBlaze processor. This configuration is intended for embedded systems. <p><hr /> @@ -963,7 +963,7 @@ the PSIM simulator. <h3 class="heading"><a name="TOC45"></a><a name="rl78_002dx_002delf"></a>rl78-*-elf</h3> -<p>The Renesas RL78 processor. +<p>The Renesas RL78 processor. This configuration is intended for embedded systems. <p><hr /> @@ -1051,7 +1051,7 @@ 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. +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 @@ -1148,13 +1148,13 @@ 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 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. + 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>. @@ -1175,7 +1175,7 @@ not that of GMP or MPFR or MPC). For example on a Solaris 9 system: thread-local storage (TLS). A typical error message is <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 + 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. @@ -1237,8 +1237,8 @@ binutils-2.22 or newer. <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. -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 @@ -1246,7 +1246,7 @@ 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>. +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 @@ -1272,7 +1272,7 @@ VxWorks will incorporate this module.) <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. +(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). @@ -1340,19 +1340,19 @@ 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. +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. +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. +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. +<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>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. @@ -1405,7 +1405,7 @@ the Win32 subsystem. This target was last known to work in GCC 3.3. <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>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. |