3 <title>Host/Target specific installation notes for GCC</title>
4 <meta http-equiv="Content-Type" content="text/html">
5 <meta name="description" content="Host/Target specific installation notes for GCC">
6 <meta name="generator" content="makeinfo 4.13">
7 <link title="Top" rel="top" href="#Top">
8 <link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
10 Copyright (C) 1988-2013 Free Software Foundation, Inc.
12 Permission is granted to copy, distribute and/or modify this document
13 under the terms of the GNU Free Documentation License, Version 1.3 or
14 any later version published by the Free Software Foundation; with no
15 Invariant Sections, the Front-Cover texts being (a) (see below), and
16 with the Back-Cover Texts being (b) (see below). A copy of the
17 license is included in the section entitled "GNU Free Documentation License".
19 (a) The FSF's Front-Cover Text is:
23 (b) The FSF's Back-Cover Text is:
25 You have freedom to copy and modify this GNU Manual, like GNU
26 software. Copies published by the Free Software Foundation raise
27 funds for GNU development.-->
28 <meta http-equiv="Content-Style-Type" content="text/css">
29 <style type="text/css"><!--
30 pre.display { font-family:inherit }
31 pre.format { font-family:inherit }
32 pre.smalldisplay { font-family:inherit; font-size:smaller }
33 pre.smallformat { font-family:inherit; font-size:smaller }
34 pre.smallexample { font-size:smaller }
35 pre.smalllisp { font-size:smaller }
36 span.sc { font-variant:small-caps }
37 span.roman { font-family:serif; font-weight:normal; }
38 span.sansserif { font-family:sans-serif; font-weight:normal; }
42 <h1 class="settitle">Host/Target specific installation notes for GCC</h1>
43 <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>
44 Please read this document carefully <em>before</em> installing the
45 GNU Compiler Collection on your machine.
47 <p>Note that this list of install notes is <em>not</em> a list of supported
48 hosts or targets. Not all supported hosts and targets are listed
49 here, only the ones that require host-specific or target-specific
53 <li><a href="#alpha-x-x">alpha*-*-*</a>
54 <li><a href="#alpha-dec-osf51">alpha*-dec-osf5.1</a>
55 <li><a href="#amd64-x-solaris210">amd64-*-solaris2.10</a>
56 <li><a href="#arm-x-eabi">arm-*-eabi</a>
57 <li><a href="#avr">avr</a>
58 <li><a href="#bfin">Blackfin</a>
59 <li><a href="#dos">DOS</a>
60 <li><a href="#x-x-freebsd">*-*-freebsd*</a>
61 <li><a href="#h8300-hms">h8300-hms</a>
62 <li><a href="#hppa-hp-hpux">hppa*-hp-hpux*</a>
63 <li><a href="#hppa-hp-hpux10">hppa*-hp-hpux10</a>
64 <li><a href="#hppa-hp-hpux11">hppa*-hp-hpux11</a>
65 <li><a href="#x-x-linux-gnu">*-*-linux-gnu</a>
66 <li><a href="#ix86-x-linux">i?86-*-linux*</a>
67 <li><a href="#ix86-x-solaris289">i?86-*-solaris2.9</a>
68 <li><a href="#ix86-x-solaris210">i?86-*-solaris2.10</a>
69 <li><a href="#ia64-x-linux">ia64-*-linux</a>
70 <li><a href="#ia64-x-hpux">ia64-*-hpux*</a>
71 <li><a href="#x-ibm-aix">*-ibm-aix*</a>
72 <li><a href="#iq2000-x-elf">iq2000-*-elf</a>
73 <li><a href="#lm32-x-elf">lm32-*-elf</a>
74 <li><a href="#lm32-x-uclinux">lm32-*-uclinux</a>
75 <li><a href="#m32c-x-elf">m32c-*-elf</a>
76 <li><a href="#m32r-x-elf">m32r-*-elf</a>
77 <li><a href="#m68k-x-x">m68k-*-*</a>
78 <li><a href="#m68k-uclinux">m68k-uclinux</a>
79 <li><a href="#mep-x-elf">mep-*-elf</a>
80 <li><a href="#microblaze-x-elf">microblaze-*-elf</a>
81 <li><a href="#mips-x-x">mips-*-*</a>
82 <li><a href="#mips-sgi-irix5">mips-sgi-irix5</a>
83 <li><a href="#mips-sgi-irix6">mips-sgi-irix6</a>
84 <li><a href="#powerpc-x-x">powerpc*-*-*</a>
85 <li><a href="#powerpc-x-darwin">powerpc-*-darwin*</a>
86 <li><a href="#powerpc-x-elf">powerpc-*-elf</a>
87 <li><a href="#powerpc-x-linux-gnu">powerpc*-*-linux-gnu*</a>
88 <li><a href="#powerpc-x-netbsd">powerpc-*-netbsd*</a>
89 <li><a href="#powerpc-x-eabisim">powerpc-*-eabisim</a>
90 <li><a href="#powerpc-x-eabi">powerpc-*-eabi</a>
91 <li><a href="#powerpcle-x-elf">powerpcle-*-elf</a>
92 <li><a href="#powerpcle-x-eabisim">powerpcle-*-eabisim</a>
93 <li><a href="#powerpcle-x-eabi">powerpcle-*-eabi</a>
94 <li><a href="#s390-x-linux">s390-*-linux*</a>
95 <li><a href="#s390x-x-linux">s390x-*-linux*</a>
96 <li><a href="#s390x-ibm-tpf">s390x-ibm-tpf*</a>
97 <li><a href="#x-x-solaris2">*-*-solaris2*</a>
98 <li><a href="#sparc-x-x">sparc*-*-*</a>
99 <li><a href="#sparc-sun-solaris2">sparc-sun-solaris2*</a>
100 <li><a href="#sparc-sun-solaris210">sparc-sun-solaris2.10</a>
101 <li><a href="#sparc-x-linux">sparc-*-linux*</a>
102 <li><a href="#sparc64-x-solaris2">sparc64-*-solaris2*</a>
103 <li><a href="#sparcv9-x-solaris2">sparcv9-*-solaris2*</a>
104 <li><a href="#c6x-x-x">c6x-*-*</a>
105 <li><a href="#tilegx-x-linux">tilegx-*-linux*</a>
106 <li><a href="#tilepro-x-linux">tilepro-*-linux*</a>
107 <li><a href="#x-x-vxworks">*-*-vxworks*</a>
108 <li><a href="#x86-64-x-x">x86_64-*-*</a> amd64-*-*
109 <li><a href="#x86-64-x-solaris210">x86_64-*-solaris2.1[0-9]*</a>
110 <li><a href="#xtensa-x-elf">xtensa*-*-elf</a>
111 <li><a href="#xtensa-x-linux">xtensa*-*-linux*</a>
112 <li><a href="#windows">Microsoft Windows</a>
113 <li><a href="#x-x-cygwin">*-*-cygwin</a>
114 <li><a href="#x-x-interix">*-*-interix</a>
115 <li><a href="#x-x-mingw32">*-*-mingw32</a>
116 <li><a href="#os2">OS/2</a>
117 <li><a href="#older">Older systems</a>
121 <li><a href="#elf">all ELF targets</a> (SVR4, Solaris 2, etc.)
124 <p><!-- -------- host/target specific issues start here ---------------- -->
127 <h3 class="heading"><a name="TOC0"></a><a name="alpha_002dx_002dx"></a>alpha*-*-*</h3>
129 <p>This section contains general configuration information for all
130 alpha-based platforms using ELF (in particular, ignore this section for
131 DEC OSF/1, Digital UNIX and Tru64 UNIX). In addition to reading this
132 section, please read all other sections that match your target.
134 <p>We require binutils 2.11.2 or newer.
135 Previous binutils releases had a number of problems with DWARF 2
136 debugging information, not the least of which is incorrect linking of
141 <h3 class="heading"><a name="TOC1"></a><a name="alpha_002ddec_002dosf51"></a>alpha*-dec-osf5.1</h3>
143 <p>Systems using processors that implement the DEC Alpha architecture and
144 are running the DEC/Compaq/HP Unix (DEC OSF/1, Digital UNIX, or Compaq/HP
145 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
147 <p>Support for Tru64 UNIX V5.1 has been removed in GCC 4.8. As of GCC 4.6,
148 support for Tru64 UNIX V4.0 and V5.0 has been removed. As of GCC 3.2,
149 versions before <code>alpha*-dec-osf4</code> are no longer supported. (These
150 are the versions which identify themselves as DEC OSF/1.)
154 <h3 class="heading"><a name="TOC2"></a><a name="amd64_002dx_002dsolaris210"></a>amd64-*-solaris2.1[0-9]*</h3>
156 <p>This is a synonym for ‘<samp><span class="samp">x86_64-*-solaris2.1[0-9]*</span></samp>’.
160 <h3 class="heading"><a name="TOC3"></a><a name="arm_002dx_002deabi"></a>arm-*-eabi</h3>
162 <p>ARM-family processors. Subtargets that use the ELF object format
163 require GNU binutils 2.13 or newer. Such subtargets include:
164 <code>arm-*-netbsdelf</code>, <code>arm-*-*linux-*</code>
165 and <code>arm-*-rtemseabi</code>.
169 <h3 class="heading"><a name="TOC4"></a><a name="avr"></a>avr</h3>
171 <p>ATMEL AVR-family micro controllers. These are used in embedded
172 applications. There are no standard Unix configurations.
173 See “AVR Options” in the main manual
174 for the list of supported MCU types.
176 <p>Use ‘<samp><span class="samp">configure --target=avr --enable-languages="c"</span></samp>’ to configure GCC.
178 <p>Further installation notes and other useful information about AVR tools
179 can also be obtained from:
182 <li><a href="http://www.nongnu.org/avr/">http://www.nongnu.org/avr/</a>
183 <li><a href="http://www.amelek.gda.pl/avr/">http://www.amelek.gda.pl/avr/</a>
186 <p>We <em>strongly</em> recommend using binutils 2.13 or newer.
188 <p>The following error:
189 <pre class="smallexample"> Error: register required
191 <p>indicates that you should upgrade to a newer version of the binutils.
195 <h3 class="heading"><a name="TOC5"></a><a name="bfin"></a>Blackfin</h3>
197 <p>The Blackfin processor, an Analog Devices DSP.
198 See “Blackfin Options” in the main manual
200 <p>More information, and a version of binutils with support for this processor,
201 is available at <a href="http://blackfin.uclinux.org">http://blackfin.uclinux.org</a>
205 <h3 class="heading"><a name="TOC6"></a><a name="cr16"></a>CR16</h3>
207 <p>The CR16 CompactRISC architecture is a 16-bit architecture. This architecture is
208 used in embedded applications.
210 <p>See “CR16 Options” in the main manual for a list of CR16-specific options.
212 <p>Use ‘<samp><span class="samp">configure --target=cr16-elf --enable-languages=c,c++</span></samp>’ to configure
213 GCC for building a CR16 elf cross-compiler.
215 <p>Use ‘<samp><span class="samp">configure --target=cr16-uclinux --enable-languages=c,c++</span></samp>’ to configure
216 GCC for building a CR16 uclinux cross-compiler.
220 <h3 class="heading"><a name="TOC7"></a><a name="cris"></a>CRIS</h3>
222 <p>CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
223 series. These are used in embedded applications.
225 <p>See “CRIS Options” in the main manual
226 for a list of CRIS-specific options.
228 <p>There are a few different CRIS targets:
230 <dt><code>cris-axis-elf</code><dd>Mainly for monolithic embedded systems. Includes a multilib for the
231 ‘<samp><span class="samp">v10</span></samp>’ core used in ‘<samp><span class="samp">ETRAX 100 LX</span></samp>’.
232 <br><dt><code>cris-axis-linux-gnu</code><dd>A GNU/Linux port for the CRIS architecture, currently targeting
233 ‘<samp><span class="samp">ETRAX 100 LX</span></samp>’ by default.
236 <p>For <code>cris-axis-elf</code> you need binutils 2.11
237 or newer. For <code>cris-axis-linux-gnu</code> you need binutils 2.12 or newer.
239 <p>Pre-packaged tools can be obtained from
240 <a href="ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/">ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/</a>. More
241 information about this platform is available at
242 <a href="http://developer.axis.com/">http://developer.axis.com/</a>.
246 <h3 class="heading"><a name="TOC8"></a><a name="dos"></a>DOS</h3>
248 <p>Please have a look at the <a href="binaries.html">binaries page</a>.
250 <p>You cannot install GCC by itself on MSDOS; it will not compile under
251 any MSDOS compiler except itself. You need to get the complete
252 compilation package DJGPP, which includes binaries as well as sources,
253 and includes all the necessary compilation tools and libraries.
257 <h3 class="heading"><a name="TOC9"></a><a name="epiphany_002dx_002delf"></a>epiphany-*-elf</h3>
259 <p>Adapteva Epiphany.
260 This configuration is intended for embedded systems.
264 <h3 class="heading"><a name="TOC10"></a><a name="x_002dx_002dfreebsd"></a>*-*-freebsd*</h3>
266 <p>Support for FreeBSD 1 was discontinued in GCC 3.2. Support for
267 FreeBSD 2 (and any mutant a.out variants of FreeBSD 3) was
268 discontinued in GCC 4.0.
270 <p>In order to better utilize FreeBSD base system functionality and match
271 the configuration of the system compiler, GCC 4.5 and above as well as
272 GCC 4.4 past 2010-06-20 leverage SSP support in libc (which is present
273 on FreeBSD 7 or later) and the use of <code>__cxa_atexit</code> by default
274 (on FreeBSD 6 or later). The use of <code>dl_iterate_phdr</code> inside
275 <samp><span class="file">libgcc_s.so.1</span></samp> and boehm-gc (on FreeBSD 7 or later) is enabled
276 by GCC 4.5 and above.
278 <p>We support FreeBSD using the ELF file format with DWARF 2 debugging
279 for all CPU architectures. You may use <samp><span class="option">-gstabs</span></samp> instead of
280 <samp><span class="option">-g</span></samp>, if you really want the old debugging format. There are
281 no known issues with mixing object files and libraries with different
282 debugging formats. Otherwise, this release of GCC should now match
283 more of the configuration used in the stock FreeBSD configuration of
284 GCC. In particular, <samp><span class="option">--enable-threads</span></samp> is now configured by
285 default. However, as a general user, do not attempt to replace the
286 system compiler with this release. Known to bootstrap and check with
287 good results on FreeBSD 7.2-STABLE. In the past, known to bootstrap
288 and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4,
289 4.5, 4.8, 4.9 and 5-CURRENT.
291 <p>The version of binutils installed in <samp><span class="file">/usr/bin</span></samp> probably works
292 with this release of GCC. Bootstrapping against the latest GNU
293 binutils and/or the version found in <samp><span class="file">/usr/ports/devel/binutils</span></samp> has
294 been known to enable additional features and improve overall testsuite
295 results. However, it is currently known that boehm-gc (which itself
296 is required for java) may not configure properly on FreeBSD prior to
297 the FreeBSD 7.0 release with GNU binutils after 2.16.1.
301 <h3 class="heading"><a name="TOC11"></a><a name="h8300_002dhms"></a>h8300-hms</h3>
303 <p>Renesas H8/300 series of processors.
305 <p>Please have a look at the <a href="binaries.html">binaries page</a>.
307 <p>The calling convention and structure layout has changed in release 2.6.
308 All code must be recompiled. The calling convention now passes the
309 first three arguments in function calls in registers. Structures are no
310 longer a multiple of 2 bytes.
314 <h3 class="heading"><a name="TOC12"></a><a name="hppa_002dhp_002dhpux"></a>hppa*-hp-hpux*</h3>
316 <p>Support for HP-UX version 9 and older was discontinued in GCC 3.4.
318 <p>We require using gas/binutils on all hppa platforms. Version 2.19 or
319 later is recommended.
321 <p>It may be helpful to configure GCC with the
322 <a href="./configure.html#with-gnu-as"><samp><span class="option">--with-gnu-as</span></samp></a> and
323 <samp><span class="option">--with-as=...</span></samp> options to ensure that GCC can find GAS.
325 <p>The HP assembler should not be used with GCC. It is rarely tested and may
326 not work. It shouldn't be used with any languages other than C due to its
329 <p>Specifically, <samp><span class="option">-g</span></samp> does not work (HP-UX uses a peculiar debugging
330 format which GCC does not know about). It also inserts timestamps
331 into each object file it creates, causing the 3-stage comparison test to
332 fail during a bootstrap. You should be able to continue by saying
333 ‘<samp><span class="samp">make all-host all-target</span></samp>’ after getting the failure from ‘<samp><span class="samp">make</span></samp>’.
335 <p>Various GCC features are not supported. For example, it does not support weak
336 symbols or alias definitions. As a result, explicit template instantiations
337 are required when using C++. This makes it difficult if not impossible to
338 build many C++ applications.
340 <p>There are two default scheduling models for instructions. These are
341 PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
342 architecture specified for the target machine when configuring.
343 PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
344 the target is a ‘<samp><span class="samp">hppa1*</span></samp>’ machine.
346 <p>The PROCESSOR_8000 model is not well suited to older processors. Thus,
347 it is important to completely specify the machine architecture when
348 configuring if you want a model other than PROCESSOR_8000. The macro
349 TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
350 default scheduling model is desired.
352 <p>As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10
353 through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later.
354 This namespace change might cause problems when bootstrapping with
355 an earlier version of GCC or the HP compiler as essentially the same
356 namespace is required for an entire build. This problem can be avoided
357 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>’
358 or ‘<samp><span class="samp">98</span></samp>’. Another way is to add an appropriate set of predefines
359 to <samp><span class="env">CC</span></samp>. The description for the <samp><span class="option">munix=</span></samp> option contains
360 a list of the predefines used with each standard.
362 <p>More specific information to ‘<samp><span class="samp">hppa*-hp-hpux*</span></samp>’ targets follows.
366 <h3 class="heading"><a name="TOC13"></a><a name="hppa_002dhp_002dhpux10"></a>hppa*-hp-hpux10</h3>
368 <p>For hpux10.20, we <em>highly</em> recommend you pick up the latest sed patch
369 <code>PHCO_19798</code> from HP.
371 <p>The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces are
372 used for one-only code and data. This resolves many of the previous
373 problems in using C++ on this target. However, the ABI is not compatible
374 with the one implemented under HP-UX 11 using secondary definitions.
378 <h3 class="heading"><a name="TOC14"></a><a name="hppa_002dhp_002dhpux11"></a>hppa*-hp-hpux11</h3>
380 <p>GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot
381 be used to compile GCC 3.0 and up.
383 <p>The libffi and libjava libraries haven't been ported to 64-bit HP-UX and don't build.
385 <p>Refer to <a href="binaries.html">binaries</a> for information about obtaining
386 precompiled GCC binaries for HP-UX. Precompiled binaries must be obtained
387 to build the Ada language as it can't be bootstrapped using C. Ada is
388 only available for the 32-bit PA-RISC runtime.
390 <p>Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The
391 bundled compiler supports only traditional C; you will need either HP's
392 unbundled compiler, or a binary distribution of GCC.
394 <p>It is possible to build GCC 3.3 starting with the bundled HP compiler,
395 but the process requires several steps. GCC 3.3 can then be used to
396 build later versions. The fastjar program contains ISO C code and
397 can't be built with the HP bundled compiler. This problem can be
398 avoided by not building the Java language. For example, use the
399 <samp><span class="option">--enable-languages="c,c++,f77,objc"</span></samp> option in your configure
402 <p>There are several possible approaches to building the distribution.
403 Binutils can be built first using the HP tools. Then, the GCC
404 distribution can be built. The second approach is to build GCC
405 first using the HP tools, then build binutils, then rebuild GCC.
406 There have been problems with various binary distributions, so it
407 is best not to start from a binary distribution.
409 <p>On 64-bit capable systems, there are two distinct targets. Different
410 installation prefixes must be used if both are to be installed on
411 the same system. The ‘<samp><span class="samp">hppa[1-2]*-hp-hpux11*</span></samp>’ target generates code
412 for the 32-bit PA-RISC runtime architecture and uses the HP linker.
413 The ‘<samp><span class="samp">hppa64-hp-hpux11*</span></samp>’ target generates 64-bit code for the
414 PA-RISC 2.0 architecture.
416 <p>The script config.guess now selects the target type based on the compiler
417 detected during configuration. You must define <samp><span class="env">PATH</span></samp> or <samp><span class="env">CC</span></samp> so
418 that configure finds an appropriate compiler for the initial bootstrap.
419 When <samp><span class="env">CC</span></samp> is used, the definition should contain the options that are
420 needed whenever <samp><span class="env">CC</span></samp> is used.
422 <p>Specifically, options that determine the runtime architecture must be
423 in <samp><span class="env">CC</span></samp> to correctly select the target for the build. It is also
424 convenient to place many other compiler options in <samp><span class="env">CC</span></samp>. For example,
425 <samp><span class="env">CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"</span></samp>
426 can be used to bootstrap the GCC 3.3 branch with the HP compiler in
427 64-bit K&R/bundled mode. The <samp><span class="option">+DA2.0W</span></samp> option will result in
428 the automatic selection of the ‘<samp><span class="samp">hppa64-hp-hpux11*</span></samp>’ target. The
429 macro definition table of cpp needs to be increased for a successful
430 build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to
431 be defined when building with the bundled compiler, or when using the
432 <samp><span class="option">-Ac</span></samp> option. These defines aren't necessary with <samp><span class="option">-Ae</span></samp>.
434 <p>It is best to explicitly configure the ‘<samp><span class="samp">hppa64-hp-hpux11*</span></samp>’ target
435 with the <samp><span class="option">--with-ld=...</span></samp> option. This overrides the standard
436 search for ld. The two linkers supported on this target require different
437 commands. The default linker is determined during configuration. As a
438 result, it's not possible to switch linkers in the middle of a GCC build.
439 This has been reported to sometimes occur in unified builds of binutils
442 <p>A recent linker patch must be installed for the correct operation of
443 GCC 3.3 and later. <code>PHSS_26559</code> and <code>PHSS_24304</code> are the
444 oldest linker patches that are known to work. They are for HP-UX
445 11.00 and 11.11, respectively. <code>PHSS_24303</code>, the companion to
446 <code>PHSS_24304</code>, might be usable but it hasn't been tested. These
447 patches have been superseded. Consult the HP patch database to obtain
448 the currently recommended linker patch for your system.
450 <p>The patches are necessary for the support of weak symbols on the
451 32-bit port, and for the running of initializers and finalizers. Weak
452 symbols are implemented using SOM secondary definition symbols. Prior
453 to HP-UX 11, there are bugs in the linker support for secondary symbols.
454 The patches correct a problem of linker core dumps creating shared
455 libraries containing secondary symbols, as well as various other
456 linking issues involving secondary symbols.
458 <p>GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
459 run initializers and finalizers on the 64-bit port. The 32-bit port
460 uses the linker <samp><span class="option">+init</span></samp> and <samp><span class="option">+fini</span></samp> options for the same
461 purpose. The patches correct various problems with the +init/+fini
462 options, including program core dumps. Binutils 2.14 corrects a
463 problem on the 64-bit port resulting from HP's non-standard use of
464 the .init and .fini sections for array initializers and finalizers.
466 <p>Although the HP and GNU linkers are both supported for the
467 ‘<samp><span class="samp">hppa64-hp-hpux11*</span></samp>’ target, it is strongly recommended that the
468 HP linker be used for link editing on this target.
470 <p>At this time, the GNU linker does not support the creation of long
471 branch stubs. As a result, it can't successfully link binaries
472 containing branch offsets larger than 8 megabytes. In addition,
473 there are problems linking shared libraries, linking executables
474 with <samp><span class="option">-static</span></samp>, and with dwarf2 unwind and exception support.
475 It also doesn't provide stubs for internal calls to global functions
476 in shared libraries, so these calls can't be overloaded.
478 <p>The HP dynamic loader does not support GNU symbol versioning, so symbol
479 versioning is not supported. It may be necessary to disable symbol
480 versioning with <samp><span class="option">--disable-symvers</span></samp> when using GNU ld.
482 <p>POSIX threads are the default. The optional DCE thread library is not
483 supported, so <samp><span class="option">--enable-threads=dce</span></samp> does not work.
487 <h3 class="heading"><a name="TOC15"></a><a name="x_002dx_002dlinux_002dgnu"></a>*-*-linux-gnu</h3>
489 <p>Versions of libstdc++-v3 starting with 3.2.1 require bug fixes present
490 in glibc 2.2.5 and later. More information is available in the
491 libstdc++-v3 documentation.
495 <h3 class="heading"><a name="TOC16"></a><a name="ix86_002dx_002dlinux"></a>i?86-*-linux*</h3>
497 <p>As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
498 See <a href="http://gcc.gnu.org/PR10877">bug 10877</a> for more information.
500 <p>If you receive Signal 11 errors when building on GNU/Linux, then it is
501 possible you have a hardware problem. Further information on this can be
502 found on <a href="http://www.bitwizard.nl/sig11/">www.bitwizard.nl</a>.
506 <h3 class="heading"><a name="TOC17"></a><a name="ix86_002dx_002dsolaris29"></a>i?86-*-solaris2.9</h3>
508 <p>The Sun assembler in Solaris 9 has several bugs and limitations.
509 While GCC works around them, several features are missing, so it is
510 <!-- FIXME: which ones? -->
511 recommended to use the GNU assembler instead. There is no bundled
512 version, but the current version, from GNU binutils 2.22, is known to
515 <p>Solaris 2/x86 doesn't support the execution of SSE/SSE2 instructions
516 before Solaris 9 4/04, even if the CPU supports them. Programs will
517 receive <code>SIGILL</code> if they try. The fix is available both in
518 Solaris 9 Update 6 and kernel patch 112234-12 or newer. To
520 <samp><span class="option">-march</span></samp> defaults to ‘<samp><span class="samp">pentiumpro</span></samp>’ on Solaris 9. If
521 you have the patch installed, you can configure GCC with an appropriate
522 <samp><span class="option">--with-arch</span></samp> option, but need GNU <samp><span class="command">as</span></samp> for SSE2 support.
526 <h3 class="heading"><a name="TOC18"></a><a name="ix86_002dx_002dsolaris210"></a>i?86-*-solaris2.10</h3>
528 <p>Use this for Solaris 10 or later on x86 and x86-64 systems. Starting
529 with GCC 4.7, there is also a 64-bit ‘<samp><span class="samp">amd64-*-solaris2.1[0-9]*</span></samp>’ or
530 ‘<samp><span class="samp">x86_64-*-solaris2.1[0-9]*</span></samp>’ configuration that corresponds to
531 ‘<samp><span class="samp">sparcv9-sun-solaris2*</span></samp>’.
533 <p>It is recommended that you configure GCC to use the GNU assembler, in
534 <samp><span class="file">/usr/sfw/bin/gas</span></samp>. The versions included in Solaris 10, from GNU
535 binutils 2.15, and Solaris 11, from GNU binutils 2.19, work fine,
536 although the current version, from GNU binutils
537 2.22, is known to work, too. Recent versions of the Sun assembler in
538 <samp><span class="file">/usr/ccs/bin/as</span></samp> work almost as well, though.
539 <!-- FIXME: as patch requirements? -->
541 <p>For linking, the Sun linker, is preferred. If you want to use the GNU
542 linker instead, which is available in <samp><span class="file">/usr/sfw/bin/gld</span></samp>, note that
543 due to a packaging bug the version in Solaris 10, from GNU binutils
544 2.15, cannot be used, while the version in Solaris 11, from GNU binutils
545 2.19, works, as does the latest version, from GNU binutils 2.22.
547 <p>To use GNU <samp><span class="command">as</span></samp>, configure with the options
548 <samp><span class="option">--with-gnu-as --with-as=/usr/sfw/bin/gas</span></samp>. It may be necessary
549 to configure with <samp><span class="option">--without-gnu-ld --with-ld=/usr/ccs/bin/ld</span></samp> to
550 guarantee use of Sun <samp><span class="command">ld</span></samp>.
551 <!-- FIXME: why -without-gnu-ld -with-ld? -->
555 <h3 class="heading"><a name="TOC19"></a><a name="ia64_002dx_002dlinux"></a>ia64-*-linux</h3>
557 <p>IA-64 processor (also known as IPF, or Itanium Processor Family)
560 <p>If you are using the installed system libunwind library with
561 <samp><span class="option">--with-system-libunwind</span></samp>, then you must use libunwind 0.98 or
564 <p>None of the following versions of GCC has an ABI that is compatible
565 with any of the other versions in this list, with the exception that
566 Red Hat 2.96 and Trillian 000171 are compatible with each other:
567 3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
568 This primarily affects C++ programs and programs that create shared libraries.
569 GCC 3.1 or later is recommended for compiling linux, the kernel.
570 As of version 3.1 GCC is believed to be fully ABI compliant, and hence no
571 more major ABI changes are expected.
575 <h3 class="heading"><a name="TOC20"></a><a name="ia64_002dx_002dhpux"></a>ia64-*-hpux*</h3>
577 <p>Building GCC on this target requires the GNU Assembler. The bundled HP
578 assembler will not work. To prevent GCC from using the wrong assembler,
579 the option <samp><span class="option">--with-gnu-as</span></samp> may be necessary.
581 <p>The GCC libunwind library has not been ported to HPUX. This means that for
582 GCC versions 3.2.3 and earlier, <samp><span class="option">--enable-libunwind-exceptions</span></samp>
583 is required to build GCC. For GCC 3.3 and later, this is the default.
584 For gcc 3.4.3 and later, <samp><span class="option">--enable-libunwind-exceptions</span></samp> is
585 removed and the system libunwind library will always be used.
588 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
590 <h3 class="heading"><a name="TOC21"></a><a name="x_002dibm_002daix"></a>*-ibm-aix*</h3>
592 <p>Support for AIX version 3 and older was discontinued in GCC 3.4.
593 Support for AIX version 4.2 and older was discontinued in GCC 4.5.
595 <p>“out of memory” bootstrap failures may indicate a problem with
596 process resource limits (ulimit). Hard limits are configured in the
597 <samp><span class="file">/etc/security/limits</span></samp> system configuration file.
599 <p>GCC can bootstrap with recent versions of IBM XLC, but bootstrapping
600 with an earlier release of GCC is recommended. Bootstrapping with XLC
601 requires a larger data segment, which can be enabled through the
602 <var>LDR_CNTRL</var> environment variable, e.g.,
604 <pre class="smallexample"> % LDR_CNTRL=MAXDATA=0x50000000
607 <p>One can start with a pre-compiled version of GCC to build from
608 sources. One may delete GCC's “fixed” header files when starting
609 with a version of GCC built for an earlier release of AIX.
611 <p>To speed up the configuration phases of bootstrapping and installing GCC,
612 one may use GNU Bash instead of AIX <samp><span class="command">/bin/sh</span></samp>, e.g.,
614 <pre class="smallexample"> % CONFIG_SHELL=/opt/freeware/bin/bash
615 % export CONFIG_SHELL
617 <p>and then proceed as described in <a href="build.html">the build instructions</a>, where we strongly recommend specifying an absolute path
618 to invoke <var>srcdir</var>/configure.
620 <p>Because GCC on AIX is built as a 32-bit executable by default,
621 (although it can generate 64-bit programs) the GMP and MPFR libraries
622 required by gfortran must be 32-bit libraries. Building GMP and MPFR
623 as static archive libraries works better than shared libraries.
625 <p>Errors involving <code>alloca</code> when building GCC generally are due
626 to an incorrect definition of <code>CC</code> in the Makefile or mixing files
627 compiled with the native C compiler and GCC. During the stage1 phase of
628 the build, the native AIX compiler <strong>must</strong> be invoked as <samp><span class="command">cc</span></samp>
629 (not <samp><span class="command">xlc</span></samp>). Once <samp><span class="command">configure</span></samp> has been informed of
630 <samp><span class="command">xlc</span></samp>, one needs to use ‘<samp><span class="samp">make distclean</span></samp>’ to remove the
631 configure cache files and ensure that <samp><span class="env">CC</span></samp> environment variable
632 does not provide a definition that will confuse <samp><span class="command">configure</span></samp>.
633 If this error occurs during stage2 or later, then the problem most likely
634 is the version of Make (see above).
636 <p>The native <samp><span class="command">as</span></samp> and <samp><span class="command">ld</span></samp> are recommended for
637 bootstrapping on AIX. The GNU Assembler, GNU Linker, and GNU
638 Binutils version 2.20 is the minimum level that supports bootstrap on
639 AIX 5. The GNU Assembler has not been updated to support AIX 6 or
640 AIX 7. The native AIX tools do interoperate with GCC.
642 <p>AIX 5.3 TL10, AIX 6.1 TL05 and AIX 7.1 TL00 introduced an AIX
643 assembler change that sometimes produces corrupt assembly files
644 causing AIX linker errors. The bug breaks GCC bootstrap on AIX and
645 can cause compilation failures with existing GCC installations. An
646 AIX iFix for AIX 5.3 is available (APAR IZ98385 for AIX 5.3 TL10, APAR
647 IZ98477 for AIX 5.3 TL11 and IZ98134 for AIX 5.3 TL12). AIX 5.3 TL11 SP8,
648 AIX 5.3 TL12 SP5, AIX 6.1 TL04 SP11, AIX 6.1 TL05 SP7, AIX 6.1 TL06 SP6,
649 AIX 6.1 TL07 and AIX 7.1 TL01 should include the fix.
651 <p>Building <samp><span class="file">libstdc++.a</span></samp> requires a fix for an AIX Assembler bug
652 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a
653 fix for another AIX Assembler bug and a co-dependent AIX Archiver fix
654 referenced as APAR IY53606 (AIX 5.2) or as APAR IY54774 (AIX 5.1)
656 <p>‘<samp><span class="samp">libstdc++</span></samp>’ in GCC 3.4 increments the major version number of the
657 shared object and GCC installation places the <samp><span class="file">libstdc++.a</span></samp>
658 shared library in a common location which will overwrite the and GCC
659 3.3 version of the shared library. Applications either need to be
660 re-linked against the new shared library or the GCC 3.1 and GCC 3.3
661 versions of the ‘<samp><span class="samp">libstdc++</span></samp>’ shared object needs to be available
662 to the AIX runtime loader. The GCC 3.1 ‘<samp><span class="samp">libstdc++.so.4</span></samp>’, if
663 present, and GCC 3.3 ‘<samp><span class="samp">libstdc++.so.5</span></samp>’ shared objects can be
664 installed for runtime dynamic loading using the following steps to set
665 the ‘<samp><span class="samp">F_LOADONLY</span></samp>’ flag in the shared object for <em>each</em>
666 multilib <samp><span class="file">libstdc++.a</span></samp> installed:
668 <p>Extract the shared objects from the currently installed
669 <samp><span class="file">libstdc++.a</span></samp> archive:
670 <pre class="smallexample"> % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
672 <p>Enable the ‘<samp><span class="samp">F_LOADONLY</span></samp>’ flag so that the shared object will be
673 available for runtime dynamic loading, but not linking:
674 <pre class="smallexample"> % strip -e libstdc++.so.4 libstdc++.so.5
676 <p>Archive the runtime-only shared object in the GCC 3.4
677 <samp><span class="file">libstdc++.a</span></samp> archive:
678 <pre class="smallexample"> % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
680 <p>Linking executables and shared libraries may produce warnings of
681 duplicate symbols. The assembly files generated by GCC for AIX always
682 have included multiple symbol definitions for certain global variable
683 and function declarations in the original program. The warnings should
684 not prevent the linker from producing a correct library or runnable
687 <p>AIX 4.3 utilizes a “large format” archive to support both 32-bit and
688 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
689 to parse archive libraries did not handle the new format correctly.
690 These routines are used by GCC and result in error messages during
691 linking such as “not a COFF file”. The version of the routines shipped
692 with AIX 4.3.1 should work for a 32-bit environment. The <samp><span class="option">-g</span></samp>
693 option of the archive command may be used to create archives of 32-bit
694 objects using the original “small format”. A correct version of the
695 routines is shipped with AIX 4.3.2 and above.
697 <p>Some versions of the AIX binder (linker) can fail with a relocation
698 overflow severe error when the <samp><span class="option">-bbigtoc</span></samp> option is used to link
699 GCC-produced object files into an executable that overflows the TOC. A fix
700 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
701 available from IBM Customer Support and from its
702 <a href="http://techsupport.services.ibm.com/">techsupport.services.ibm.com</a>
703 website as PTF U455193.
705 <p>The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
706 with a segmentation fault when invoked by any version of GCC. A fix for
707 APAR IX87327 is available from IBM Customer Support and from its
708 <a href="http://techsupport.services.ibm.com/">techsupport.services.ibm.com</a>
709 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
711 <p>The initial assembler shipped with AIX 4.3.0 generates incorrect object
712 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
713 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
714 <a href="http://techsupport.services.ibm.com/">techsupport.services.ibm.com</a>
715 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
717 <p>AIX provides National Language Support (NLS). Compilers and assemblers
718 use NLS to support locale-specific representations of various data
719 formats including floating-point numbers (e.g., ‘<samp><span class="samp">.</span></samp>’ vs ‘<samp><span class="samp">,</span></samp>’ for
720 separating decimal fractions). There have been problems reported where
721 GCC does not produce the same floating-point formats that the assembler
722 expects. If one encounters this problem, set the <samp><span class="env">LANG</span></samp>
723 environment variable to ‘<samp><span class="samp">C</span></samp>’ or ‘<samp><span class="samp">En_US</span></samp>’.
725 <p>A default can be specified with the <samp><span class="option">-mcpu=</span><var>cpu_type</var></samp>
726 switch and using the configure option <samp><span class="option">--with-cpu-</span><var>cpu_type</var></samp>.
730 <h3 class="heading"><a name="TOC22"></a><a name="iq2000_002dx_002delf"></a>iq2000-*-elf</h3>
732 <p>Vitesse IQ2000 processors. These are used in embedded
733 applications. There are no standard Unix configurations.
737 <h3 class="heading"><a name="TOC23"></a><a name="lm32_002dx_002delf"></a>lm32-*-elf</h3>
739 <p>Lattice Mico32 processor.
740 This configuration is intended for embedded systems.
744 <h3 class="heading"><a name="TOC24"></a><a name="lm32_002dx_002duclinux"></a>lm32-*-uclinux</h3>
746 <p>Lattice Mico32 processor.
747 This configuration is intended for embedded systems running uClinux.
751 <h3 class="heading"><a name="TOC25"></a><a name="m32c_002dx_002delf"></a>m32c-*-elf</h3>
753 <p>Renesas M32C processor.
754 This configuration is intended for embedded systems.
758 <h3 class="heading"><a name="TOC26"></a><a name="m32r_002dx_002delf"></a>m32r-*-elf</h3>
760 <p>Renesas M32R processor.
761 This configuration is intended for embedded systems.
765 <h3 class="heading"><a name="TOC27"></a><a name="m68k_002dx_002dx"></a>m68k-*-*</h3>
768 ‘<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
769 ‘<samp><span class="samp">m68k-*-linux</span></samp>’
770 build libraries for both M680x0 and ColdFire processors. If you only
771 need the M680x0 libraries, you can omit the ColdFire ones by passing
772 <samp><span class="option">--with-arch=m68k</span></samp> to <samp><span class="command">configure</span></samp>. Alternatively, you
773 can omit the M680x0 libraries by passing <samp><span class="option">--with-arch=cf</span></samp> to
774 <samp><span class="command">configure</span></samp>. These targets default to 5206 or 5475 code as
775 appropriate for the target system when
776 configured with <samp><span class="option">--with-arch=cf</span></samp> and 68020 code otherwise.
778 <p>The ‘<samp><span class="samp">m68k-*-netbsd</span></samp>’ and
779 ‘<samp><span class="samp">m68k-*-openbsd</span></samp>’ targets also support the <samp><span class="option">--with-arch</span></samp>
780 option. They will generate ColdFire CFV4e code when configured with
781 <samp><span class="option">--with-arch=cf</span></samp> and 68020 code otherwise.
783 <p>You can override the default processors listed above by configuring
784 with <samp><span class="option">--with-cpu=</span><var>target</var></samp>. This <var>target</var> can either
785 be a <samp><span class="option">-mcpu</span></samp> argument or one of the following values:
786 ‘<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>’,
787 ‘<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>’.
789 <p>GCC requires at least binutils version 2.17 on these targets.
793 <h3 class="heading"><a name="TOC28"></a><a name="m68k_002dx_002duclinux"></a>m68k-*-uclinux</h3>
795 <p>GCC 4.3 changed the uClinux configuration so that it uses the
796 ‘<samp><span class="samp">m68k-linux-gnu</span></samp>’ ABI rather than the ‘<samp><span class="samp">m68k-elf</span></samp>’ ABI.
797 It also added improved support for C++ and flat shared libraries,
798 both of which were ABI changes.
802 <h3 class="heading"><a name="TOC29"></a><a name="mep_002dx_002delf"></a>mep-*-elf</h3>
804 <p>Toshiba Media embedded Processor.
805 This configuration is intended for embedded systems.
809 <h3 class="heading"><a name="TOC30"></a><a name="microblaze_002dx_002delf"></a>microblaze-*-elf</h3>
811 <p>Xilinx MicroBlaze processor.
812 This configuration is intended for embedded systems.
816 <h3 class="heading"><a name="TOC31"></a><a name="mips_002dx_002dx"></a>mips-*-*</h3>
818 <p>If on a MIPS system you get an error message saying “does not have gp
819 sections for all it's [sic] sectons [sic]”, don't worry about it. This
820 happens whenever you use GAS with the MIPS linker, but there is not
821 really anything wrong, and it is okay to use the output file. You can
822 stop such warnings by installing the GNU linker.
824 <p>It would be nice to extend GAS to produce the gp tables, but they are
825 optional, and there should not be a warning about their absence.
827 <p>The libstdc++ atomic locking routines for MIPS targets requires MIPS II
828 and later. A patch went in just after the GCC 3.3 release to
829 make ‘<samp><span class="samp">mips*-*-*</span></samp>’ use the generic implementation instead. You can also
830 configure for ‘<samp><span class="samp">mipsel-elf</span></samp>’ as a workaround. The
831 ‘<samp><span class="samp">mips*-*-linux*</span></samp>’ target continues to use the MIPS II routines. More
832 work on this is expected in future releases.
834 <!-- If you make -with-llsc the default for another target, please also -->
835 <!-- update the description of the -with-llsc option. -->
836 <p>The built-in <code>__sync_*</code> functions are available on MIPS II and
837 later systems and others that support the ‘<samp><span class="samp">ll</span></samp>’, ‘<samp><span class="samp">sc</span></samp>’ and
838 ‘<samp><span class="samp">sync</span></samp>’ instructions. This can be overridden by passing
839 <samp><span class="option">--with-llsc</span></samp> or <samp><span class="option">--without-llsc</span></samp> when configuring GCC.
840 Since the Linux kernel emulates these instructions if they are
841 missing, the default for ‘<samp><span class="samp">mips*-*-linux*</span></samp>’ targets is
842 <samp><span class="option">--with-llsc</span></samp>. The <samp><span class="option">--with-llsc</span></samp> and
843 <samp><span class="option">--without-llsc</span></samp> configure options may be overridden at compile
844 time by passing the <samp><span class="option">-mllsc</span></samp> or <samp><span class="option">-mno-llsc</span></samp> options to
847 <p>MIPS systems check for division by zero (unless
848 <samp><span class="option">-mno-check-zero-division</span></samp> is passed to the compiler) by
849 generating either a conditional trap or a break instruction. Using
850 trap results in smaller code, but is only supported on MIPS II and
851 later. Also, some versions of the Linux kernel have a bug that
852 prevents trap from generating the proper signal (<code>SIGFPE</code>). To enable
853 the use of break, use the <samp><span class="option">--with-divide=breaks</span></samp>
854 <samp><span class="command">configure</span></samp> option when configuring GCC. The default is to
855 use traps on systems that support them.
857 <p>The assembler from GNU binutils 2.17 and earlier has a bug in the way
858 it sorts relocations for REL targets (o32, o64, EABI). This can cause
859 bad code to be generated for simple C++ programs. Also the linker
860 from GNU binutils versions prior to 2.17 has a bug which causes the
861 runtime linker stubs in very large programs, like <samp><span class="file">libgcj.so</span></samp>, to
862 be incorrectly generated. GNU Binutils 2.18 and later (and snapshots
863 made after Nov. 9, 2006) should be free from both of these problems.
867 <h3 class="heading"><a name="TOC32"></a><a name="mips_002dsgi_002dirix5"></a>mips-sgi-irix5</h3>
869 <p>Support for IRIX 5 has been removed in GCC 4.6.
873 <h3 class="heading"><a name="TOC33"></a><a name="mips_002dsgi_002dirix6"></a>mips-sgi-irix6</h3>
875 <p>Support for IRIX 6.5 has been removed in GCC 4.8. Support for IRIX 6
876 releases before 6.5 has been removed in GCC 4.6, as well as support for
881 <h3 class="heading"><a name="TOC34"></a><a name="moxie_002dx_002delf"></a>moxie-*-elf</h3>
883 <p>The moxie processor.
887 <h3 class="heading"><a name="TOC35"></a><a name="powerpc_002dx_002dx"></a>powerpc-*-*</h3>
889 <p>You can specify a default version for the <samp><span class="option">-mcpu=</span><var>cpu_type</var></samp>
890 switch by using the configure option <samp><span class="option">--with-cpu-</span><var>cpu_type</var></samp>.
893 <a href="ftp://ftp.kernel.org/pub/linux/devel/binutils">binutils 2.15</a>
894 or newer for a working GCC.
898 <h3 class="heading"><a name="TOC36"></a><a name="powerpc_002dx_002ddarwin"></a>powerpc-*-darwin*</h3>
900 <p>PowerPC running Darwin (Mac OS X kernel).
902 <p>Pre-installed versions of Mac OS X may not include any developer tools,
903 meaning that you will not be able to build GCC from source. Tool
904 binaries are available at
905 <a href="http://opensource.apple.com/">http://opensource.apple.com/</a>.
907 <p>This version of GCC requires at least cctools-590.36. The
908 cctools-590.36 package referenced from
909 <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
910 on systems older than 10.3.9 (aka darwin7.9.0).
914 <h3 class="heading"><a name="TOC37"></a><a name="powerpc_002dx_002delf"></a>powerpc-*-elf</h3>
916 <p>PowerPC system in big endian mode, running System V.4.
920 <h3 class="heading"><a name="TOC38"></a><a name="powerpc_002dx_002dlinux_002dgnu"></a>powerpc*-*-linux-gnu*</h3>
922 <p>PowerPC system in big endian mode running Linux.
926 <h3 class="heading"><a name="TOC39"></a><a name="powerpc_002dx_002dnetbsd"></a>powerpc-*-netbsd*</h3>
928 <p>PowerPC system in big endian mode running NetBSD.
932 <h3 class="heading"><a name="TOC40"></a><a name="powerpc_002dx_002deabisim"></a>powerpc-*-eabisim</h3>
934 <p>Embedded PowerPC system in big endian mode for use in running under the
939 <h3 class="heading"><a name="TOC41"></a><a name="powerpc_002dx_002deabi"></a>powerpc-*-eabi</h3>
941 <p>Embedded PowerPC system in big endian mode.
945 <h3 class="heading"><a name="TOC42"></a><a name="powerpcle_002dx_002delf"></a>powerpcle-*-elf</h3>
947 <p>PowerPC system in little endian mode, running System V.4.
951 <h3 class="heading"><a name="TOC43"></a><a name="powerpcle_002dx_002deabisim"></a>powerpcle-*-eabisim</h3>
953 <p>Embedded PowerPC system in little endian mode for use in running under
958 <h3 class="heading"><a name="TOC44"></a><a name="powerpcle_002dx_002deabi"></a>powerpcle-*-eabi</h3>
960 <p>Embedded PowerPC system in little endian mode.
964 <h3 class="heading"><a name="TOC45"></a><a name="rl78_002dx_002delf"></a>rl78-*-elf</h3>
966 <p>The Renesas RL78 processor.
967 This configuration is intended for embedded systems.
971 <h3 class="heading"><a name="TOC46"></a><a name="rx_002dx_002delf"></a>rx-*-elf</h3>
973 <p>The Renesas RX processor. See
974 <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>
975 for more information about this processor.
979 <h3 class="heading"><a name="TOC47"></a><a name="s390_002dx_002dlinux"></a>s390-*-linux*</h3>
981 <p>S/390 system running GNU/Linux for S/390.
985 <h3 class="heading"><a name="TOC48"></a><a name="s390x_002dx_002dlinux"></a>s390x-*-linux*</h3>
987 <p>zSeries system (64-bit) running GNU/Linux for zSeries.
991 <h3 class="heading"><a name="TOC49"></a><a name="s390x_002dibm_002dtpf"></a>s390x-ibm-tpf*</h3>
993 <p>zSeries system (64-bit) running TPF. This platform is
994 supported as cross-compilation target only.
996 <p><hr /><!-- Please use Solaris 2 to refer to all release of Solaris, starting -->
997 <!-- with 2.0 until 2.6, 7, 8, etc. Solaris 1 was a marketing name for -->
998 <!-- SunOS 4 releases which we don't use to avoid confusion. Solaris -->
999 <!-- alone is too unspecific and must be avoided. -->
1001 <h3 class="heading"><a name="TOC50"></a><a name="x_002dx_002dsolaris2"></a>*-*-solaris2*</h3>
1003 <p>Support for Solaris 8 has removed in GCC 4.8. Support for Solaris 7 has
1004 been removed in GCC 4.6.
1006 <p>Sun does not ship a C compiler with Solaris 2 before Solaris 10, though
1007 you can download the Sun Studio compilers for free. In Solaris 10 and
1008 11, GCC 3.4.3 is available as <samp><span class="command">/usr/sfw/bin/gcc</span></samp>. Solaris 11
1009 also provides GCC 4.5.2 as <samp><span class="command">/usr/gcc/4.5/bin/gcc</span></samp>. Alternatively,
1010 you can install a pre-built GCC to bootstrap and install GCC. See the
1011 <a href="binaries.html">binaries page</a> for details.
1013 <p>The Solaris 2 <samp><span class="command">/bin/sh</span></samp> will often fail to configure
1014 ‘<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
1015 recommend using the following initial sequence of commands
1017 <pre class="smallexample"> % CONFIG_SHELL=/bin/ksh
1018 % export CONFIG_SHELL
1020 <p class="noindent">and proceed as described in <a href="configure.html">the configure instructions</a>.
1021 In addition we strongly recommend specifying an absolute path to invoke
1022 <samp><var>srcdir</var><span class="command">/configure</span></samp>.
1024 <p>Solaris 2 comes with a number of optional OS packages. Some of these
1025 are needed to use GCC fully, namely <code>SUNWarc</code>,
1026 <code>SUNWbtool</code>, <code>SUNWesu</code>, <code>SUNWhea</code>, <code>SUNWlibm</code>,
1027 <code>SUNWsprot</code>, and <code>SUNWtoo</code>. If you did not install all
1028 optional packages when installing Solaris 2, you will need to verify that
1029 the packages that GCC needs are installed.
1031 <p>To check whether an optional package is installed, use
1032 the <samp><span class="command">pkginfo</span></samp> command. To add an optional package, use the
1033 <samp><span class="command">pkgadd</span></samp> command. For further details, see the Solaris 2
1036 <p>Trying to use the linker and other tools in
1037 <samp><span class="file">/usr/ucb</span></samp> to install GCC has been observed to cause trouble.
1038 For example, the linker may hang indefinitely. The fix is to remove
1039 <samp><span class="file">/usr/ucb</span></samp> from your <samp><span class="env">PATH</span></samp>.
1041 <p>The build process works more smoothly with the legacy Sun tools so, if you
1042 have <samp><span class="file">/usr/xpg4/bin</span></samp> in your <samp><span class="env">PATH</span></samp>, we recommend that you place
1043 <samp><span class="file">/usr/bin</span></samp> before <samp><span class="file">/usr/xpg4/bin</span></samp> for the duration of the build.
1045 <p>We recommend the use of the Sun assembler or the GNU assembler, in
1046 conjunction with the Sun linker. The GNU <samp><span class="command">as</span></samp>
1047 versions included in Solaris 10, from GNU binutils 2.15, and Solaris 11,
1048 from GNU binutils 2.19, are known to work. They can be found in
1049 <samp><span class="file">/usr/sfw/bin/gas</span></samp>. Current versions of GNU binutils (2.22)
1050 are known to work as well. Note that your mileage may vary
1051 if you use a combination of the GNU tools and the Sun tools: while the
1052 combination GNU <samp><span class="command">as</span></samp> + Sun <samp><span class="command">ld</span></samp> should reasonably work,
1053 the reverse combination Sun <samp><span class="command">as</span></samp> + GNU <samp><span class="command">ld</span></samp> may fail to
1054 build or cause memory corruption at runtime in some cases for C++ programs.
1055 <!-- FIXME: still? -->
1056 GNU <samp><span class="command">ld</span></samp> usually works as well, although the version included in
1057 Solaris 10 cannot be used due to several bugs. Again, the current
1058 version (2.22) is known to work, but generally lacks platform specific
1059 features, so better stay with Sun <samp><span class="command">ld</span></samp>. To use the LTO linker
1060 plugin (<samp><span class="option">-fuse-linker-plugin</span></samp>) with GNU <samp><span class="command">ld</span></samp>, GNU
1061 binutils <em>must</em> be configured with <samp><span class="option">--enable-largefile</span></samp>.
1063 <p>To enable symbol versioning in ‘<samp><span class="samp">libstdc++</span></samp>’ with Sun <samp><span class="command">ld</span></samp>,
1064 you need to have any version of GNU <samp><span class="command">c++filt</span></samp>, which is part of
1065 GNU binutils. ‘<samp><span class="samp">libstdc++</span></samp>’ symbol versioning will be disabled if no
1066 appropriate version is found. Sun <samp><span class="command">c++filt</span></samp> from the Sun Studio
1067 compilers does <em>not</em> work.
1069 <p>Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
1070 newer: <samp><span class="command">g++</span></samp> will complain that types are missing. These headers
1071 assume that omitting the type means <code>int</code>; this assumption worked for
1072 C90 but is wrong for C++, and is now wrong for C99 also.
1074 <p>Sun bug 4927647 sometimes causes random spurious testsuite failures
1075 related to missing diagnostic output. This bug doesn't affect GCC
1076 itself, rather it is a kernel bug triggered by the <samp><span class="command">expect</span></samp>
1077 program which is used only by the GCC testsuite driver. When the bug
1078 causes the <samp><span class="command">expect</span></samp> program to miss anticipated output, extra
1079 testsuite failures appear.
1081 <p>There are patches for Solaris 9 (117171-11 or newer for
1082 SPARC, 117172-11 or newer for Intel) that address this problem.
1084 <p>Thread-local storage (TLS) is supported in Solaris 9, but requires
1085 some patches. The ‘<samp><span class="samp">libthread</span></samp>’ patches provide the
1086 <code>__tls_get_addr</code> (SPARC, 64-bit x86) resp. <code>___tls_get_addr</code>
1087 (32-bit x86) functions. On Solaris 9, the necessary support
1088 on SPARC is present since FCS, while 114432-05 or newer is required on
1089 Intel. Additionally, on Solaris 9/x86, patch 113986-02 or newer is
1090 required for the Sun <samp><span class="command">ld</span></samp> and runtime linker (<samp><span class="command">ld.so.1</span></samp>)
1091 support, while Solaris 9/SPARC works since FCS. The linker
1092 patches must be installed even if GNU <samp><span class="command">ld</span></samp> is used. Sun
1093 <samp><span class="command">as</span></samp> in Solaris 9 doesn't support the necessary
1094 relocations, so GNU <samp><span class="command">as</span></samp> must be used. The <samp><span class="command">configure</span></samp>
1095 script checks for those prerequisites and automatically enables TLS
1096 support if they are met. Although those minimal patch versions should
1097 work, it is recommended to use the latest patch versions which include
1098 additional bug fixes.
1102 <h3 class="heading"><a name="TOC51"></a><a name="sparc_002dx_002dx"></a>sparc*-*-*</h3>
1104 <p>This section contains general configuration information for all
1105 SPARC-based platforms. In addition to reading this section, please
1106 read all other sections that match your target.
1108 <p>Newer versions of the GNU Multiple Precision Library (GMP), the MPFR
1109 library and the MPC library are known to be miscompiled by earlier
1110 versions of GCC on these platforms. We therefore recommend the use
1111 of the exact versions of these libraries listed as minimal versions
1112 in <a href="prerequisites.html">the prerequisites</a>.
1116 <h3 class="heading"><a name="TOC52"></a><a name="sparc_002dsun_002dsolaris2"></a>sparc-sun-solaris2*</h3>
1118 <p>When GCC is configured to use GNU binutils 2.14 or later, the binaries
1119 produced are smaller than the ones produced using Sun's native tools;
1120 this difference is quite significant for binaries containing debugging
1123 <p>Starting with Solaris 7, the operating system is capable of executing
1124 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
1125 this; the <samp><span class="option">-m64</span></samp> option enables 64-bit code generation.
1126 However, if all you want is code tuned for the UltraSPARC CPU, you
1127 should try the <samp><span class="option">-mtune=ultrasparc</span></samp> option instead, which produces
1128 code that, unlike full 64-bit code, can still run on non-UltraSPARC
1131 <p>When configuring on a Solaris 7 or later system that is running a kernel
1132 that supports only 32-bit binaries, one must configure with
1133 <samp><span class="option">--disable-multilib</span></samp>, since we will not be able to build the
1134 64-bit target libraries.
1136 <p>GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of
1137 the GNU compiler (especially GCC 3.0.x versions), which lead to the
1138 miscompilation of the stage1 compiler and the subsequent failure of the
1139 bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary
1140 stage, i.e. to bootstrap that compiler with the base compiler and then
1141 use it to bootstrap the final compiler.
1143 <p>GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE Studio 7)
1144 and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a bootstrap
1145 failure in form of a miscompilation of the stage1 compiler by the Sun
1146 compiler. This is Sun bug 4974440. This is fixed with patch 112760-07.
1148 <p>GCC 3.4 changed the default debugging format from Stabs to DWARF-2 for
1149 32-bit code on Solaris 7 and later. If you use the Sun assembler, this
1150 change apparently runs afoul of Sun bug 4910101 (which is referenced as
1151 an x86-only problem by Sun, probably because they do not use DWARF-2).
1152 A symptom of the problem is that you cannot compile C++ programs like
1153 <samp><span class="command">groff</span></samp> 1.19.1 without getting messages similar to the following:
1155 <pre class="smallexample"> ld: warning: relocation error: R_SPARC_UA32: ...
1156 external symbolic relocation against non-allocatable section
1157 .debug_info cannot be processed at runtime: relocation ignored.
1159 <p class="noindent">To work around this problem, compile with <samp><span class="option">-gstabs+</span></samp> instead of
1160 plain <samp><span class="option">-g</span></samp>.
1162 <p>When configuring the GNU Multiple Precision Library (GMP), the MPFR
1163 library or the MPC library on a Solaris 7 or later system, the canonical
1164 target triplet must be specified as the <samp><span class="command">build</span></samp> parameter on the
1165 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
1166 not that of GMP or MPFR or MPC). For example on a Solaris 9 system:
1168 <pre class="smallexample"> % ./configure --build=sparc-sun-solaris2.9 --prefix=xxx
1172 <h3 class="heading"><a name="TOC53"></a><a name="sparc_002dsun_002dsolaris210"></a>sparc-sun-solaris2.10</h3>
1174 <p>There is a bug in older versions of the Sun assembler which breaks
1175 thread-local storage (TLS). A typical error message is
1177 <pre class="smallexample"> ld: fatal: relocation error: R_SPARC_TLS_LE_HIX22: file /var/tmp//ccamPA1v.o:
1178 symbol <unknown>: bad symbol type SECT: symbol type must be TLS
1180 <p class="noindent">This bug is fixed in Sun patch 118683-03 or later.
1184 <h3 class="heading"><a name="TOC54"></a><a name="sparc_002dx_002dlinux"></a>sparc-*-linux*</h3>
1186 <p>GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
1187 or newer on this platform. All earlier binutils and glibc
1188 releases mishandled unaligned relocations on <code>sparc-*-*</code> targets.
1192 <h3 class="heading"><a name="TOC55"></a><a name="sparc64_002dx_002dsolaris2"></a>sparc64-*-solaris2*</h3>
1194 <p>When configuring the GNU Multiple Precision Library (GMP), the MPFR
1195 library or the MPC library, the canonical target triplet must be specified
1196 as the <samp><span class="command">build</span></samp> parameter on the configure line. For example
1197 on a Solaris 9 system:
1199 <pre class="smallexample"> % ./configure --build=sparc64-sun-solaris2.9 --prefix=xxx
1201 <p>The following compiler flags must be specified in the configure
1202 step in order to bootstrap this target with the Sun compiler:
1204 <pre class="smallexample"> % CC="cc -xarch=v9 -xildoff" <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>]
1206 <p class="noindent"><samp><span class="option">-xarch=v9</span></samp> specifies the SPARC-V9 architecture to the Sun toolchain
1207 and <samp><span class="option">-xildoff</span></samp> turns off the incremental linker.
1211 <h3 class="heading"><a name="TOC56"></a><a name="sparcv9_002dx_002dsolaris2"></a>sparcv9-*-solaris2*</h3>
1213 <p>This is a synonym for ‘<samp><span class="samp">sparc64-*-solaris2*</span></samp>’.
1217 <h3 class="heading"><a name="TOC57"></a><a name="c6x_002dx_002dx"></a>c6x-*-*</h3>
1219 <p>The C6X family of processors. This port requires binutils-2.22 or newer.
1223 <h3 class="heading"><a name="TOC58"></a><a name="tilegx_002d_002a_002dlinux"></a>tilegx-*-linux*</h3>
1225 <p>The TILE-Gx processor running GNU/Linux. This port requires
1226 binutils-2.22 or newer.
1230 <h3 class="heading"><a name="TOC59"></a><a name="tilepro_002d_002a_002dlinux"></a>tilepro-*-linux*</h3>
1232 <p>The TILEPro processor running GNU/Linux. This port requires
1233 binutils-2.22 or newer.
1237 <h3 class="heading"><a name="TOC60"></a><a name="x_002dx_002dvxworks"></a>*-*-vxworks*</h3>
1239 <p>Support for VxWorks is in flux. At present GCC supports <em>only</em> the
1240 very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC.
1241 We welcome patches for other architectures supported by VxWorks 5.5.
1242 Support for VxWorks AE would also be welcome; we believe this is merely
1243 a matter of writing an appropriate “configlette” (see below). We are
1244 not interested in supporting older, a.out or COFF-based, versions of
1247 <p>VxWorks comes with an older version of GCC installed in
1248 <samp><var>$WIND_BASE</var><span class="file">/host</span></samp>; we recommend you do not overwrite it.
1249 Choose an installation <var>prefix</var> entirely outside <var>$WIND_BASE</var>.
1250 Before running <samp><span class="command">configure</span></samp>, create the directories <samp><var>prefix</var></samp>
1251 and <samp><var>prefix</var><span class="file">/bin</span></samp>. Link or copy the appropriate assembler,
1252 linker, etc. into <samp><var>prefix</var><span class="file">/bin</span></samp>, and set your <var>PATH</var> to
1253 include that directory while running both <samp><span class="command">configure</span></samp> and
1254 <samp><span class="command">make</span></samp>.
1256 <p>You must give <samp><span class="command">configure</span></samp> the
1257 <samp><span class="option">--with-headers=</span><var>$WIND_BASE</var><span class="option">/target/h</span></samp> switch so that it can
1258 find the VxWorks system headers. Since VxWorks is a cross compilation
1259 target only, you must also specify <samp><span class="option">--target=</span><var>target</var></samp>.
1260 <samp><span class="command">configure</span></samp> will attempt to create the directory
1261 <samp><var>prefix</var><span class="file">/</span><var>target</var><span class="file">/sys-include</span></samp> and copy files into it;
1262 make sure the user running <samp><span class="command">configure</span></samp> has sufficient privilege
1265 <p>GCC's exception handling runtime requires a special “configlette”
1266 module, <samp><span class="file">contrib/gthr_supp_vxw_5x.c</span></samp>. Follow the instructions in
1267 that file to add the module to your kernel build. (Future versions of
1268 VxWorks will incorporate this module.)
1272 <h3 class="heading"><a name="TOC61"></a><a name="x86_002d64_002dx_002dx"></a>x86_64-*-*, amd64-*-*</h3>
1274 <p>GCC supports the x86-64 architecture implemented by the AMD64 processor
1275 (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD.
1276 On GNU/Linux the default is a bi-arch compiler which is able to generate
1277 both 64-bit x86-64 and 32-bit x86 code (via the <samp><span class="option">-m32</span></samp> switch).
1281 <h3 class="heading"><a name="TOC62"></a><a name="x86_002d64_002dx_002dsolaris210"></a>x86_64-*-solaris2.1[0-9]*</h3>
1283 <p>GCC also supports the x86-64 architecture implemented by the AMD64
1284 processor (‘<samp><span class="samp">amd64-*-*</span></samp>’ is an alias for ‘<samp><span class="samp">x86_64-*-*</span></samp>’) on
1285 Solaris 10 or later. Unlike other systems, without special options a
1286 bi-arch compiler is built which generates 32-bit code by default, but
1287 can generate 64-bit x86-64 code with the <samp><span class="option">-m64</span></samp> switch. Since
1288 GCC 4.7, there is also configuration that defaults to 64-bit code, but
1289 can generate 32-bit code with <samp><span class="option">-m32</span></samp>. To configure and build
1290 this way, you have to provide all support libraries like <samp><span class="file">libgmp</span></samp>
1291 as 64-bit code, configure with <samp><span class="option">--target=x86_64-pc-solaris2.1x</span></samp>
1292 and ‘<samp><span class="samp">CC=gcc -m64</span></samp>’.
1296 <h3 class="heading"><a name="TOC63"></a><a name="xtensa_002dx_002delf"></a>xtensa*-*-elf</h3>
1298 <p>This target is intended for embedded Xtensa systems using the
1299 ‘<samp><span class="samp">newlib</span></samp>’ C library. It uses ELF but does not support shared
1300 objects. Designed-defined instructions specified via the
1301 Tensilica Instruction Extension (TIE) language are only supported
1302 through inline assembly.
1304 <p>The Xtensa configuration information must be specified prior to
1305 building GCC. The <samp><span class="file">include/xtensa-config.h</span></samp> header
1306 file contains the configuration information. If you created your
1307 own Xtensa configuration with the Xtensa Processor Generator, the
1308 downloaded files include a customized copy of this header file,
1309 which you can use to replace the default header file.
1313 <h3 class="heading"><a name="TOC64"></a><a name="xtensa_002dx_002dlinux"></a>xtensa*-*-linux*</h3>
1315 <p>This target is for Xtensa systems running GNU/Linux. It supports ELF
1316 shared objects and the GNU C library (glibc). It also generates
1317 position-independent code (PIC) regardless of whether the
1318 <samp><span class="option">-fpic</span></samp> or <samp><span class="option">-fPIC</span></samp> options are used. In other
1319 respects, this target is the same as the
1320 <a href="#xtensa*-*-elf">‘<samp><span class="samp">xtensa*-*-elf</span></samp>’</a> target.
1324 <h3 class="heading"><a name="TOC65"></a><a name="windows"></a>Microsoft Windows</h3>
1326 <h4 class="subheading"><a name="TOC66"></a>Intel 16-bit versions</h4>
1328 <p>The 16-bit versions of Microsoft Windows, such as Windows 3.1, are not
1331 <p>However, the 32-bit port has limited support for Microsoft
1332 Windows 3.11 in the Win32s environment, as a target only. See below.
1334 <h4 class="subheading"><a name="TOC67"></a>Intel 32-bit versions</h4>
1336 <p>The 32-bit versions of Windows, including Windows 95, Windows NT, Windows
1337 XP, and Windows Vista, are supported by several different target
1338 platforms. These targets differ in which Windows subsystem they target
1339 and which C libraries are used.
1342 <li>Cygwin <a href="#x-x-cygwin">*-*-cygwin</a>: Cygwin provides a user-space
1343 Linux API emulation layer in the Win32 subsystem.
1344 <li>Interix <a href="#x-x-interix">*-*-interix</a>: The Interix subsystem
1345 provides native support for POSIX.
1346 <li>MinGW <a href="#x-x-mingw32">*-*-mingw32</a>: MinGW is a native GCC port for
1347 the Win32 subsystem that provides a subset of POSIX.
1348 <li>MKS i386-pc-mks: NuTCracker from MKS. See
1349 <a href="http://www.mkssoftware.com/">http://www.mkssoftware.com/</a> for more information.
1352 <h4 class="subheading"><a name="TOC68"></a>Intel 64-bit versions</h4>
1354 <p>GCC contains support for x86-64 using the mingw-w64
1355 runtime library, available from <a href="http://mingw-w64.sourceforge.net/">http://mingw-w64.sourceforge.net/</a>.
1356 This library should be used with the target triple x86_64-pc-mingw32.
1358 <p>Presently Windows for Itanium is not supported.
1360 <h4 class="subheading"><a name="TOC69"></a>Windows CE</h4>
1362 <p>Windows CE is supported as a target only on Hitachi
1363 SuperH (sh-wince-pe), and MIPS (mips-wince-pe).
1365 <h4 class="subheading"><a name="TOC70"></a>Other Windows Platforms</h4>
1367 <p>GCC no longer supports Windows NT on the Alpha or PowerPC.
1369 <p>GCC no longer supports the Windows POSIX subsystem. However, it does
1370 support the Interix subsystem. See above.
1372 <p>Old target names including *-*-winnt and *-*-windowsnt are no longer used.
1374 <p>PW32 (i386-pc-pw32) support was never completed, and the project seems to
1375 be inactive. See <a href="http://pw32.sourceforge.net/">http://pw32.sourceforge.net/</a> for more information.
1377 <p>UWIN support has been removed due to a lack of maintenance.
1381 <h3 class="heading"><a name="TOC71"></a><a name="x_002dx_002dcygwin"></a>*-*-cygwin</h3>
1383 <p>Ports of GCC are included with the
1384 <a href="http://www.cygwin.com/">Cygwin environment</a>.
1386 <p>GCC will build under Cygwin without modification; it does not build
1387 with Microsoft's C++ compiler and there are no plans to make it do so.
1389 <p>The Cygwin native compiler can be configured to target any 32-bit x86
1390 cpu architecture desired; the default is i686-pc-cygwin. It should be
1391 used with as up-to-date a version of binutils as possible; use either
1392 the latest official GNU binutils release in the Cygwin distribution,
1393 or version 2.20 or above if building your own.
1397 <h3 class="heading"><a name="TOC72"></a><a name="x_002dx_002dinterix"></a>*-*-interix</h3>
1399 <p>The Interix target is used by OpenNT, Interix, Services For UNIX (SFU),
1400 and Subsystem for UNIX-based Applications (SUA). Applications compiled
1401 with this target run in the Interix subsystem, which is separate from
1402 the Win32 subsystem. This target was last known to work in GCC 3.3.
1406 <h3 class="heading"><a name="TOC73"></a><a name="x_002dx_002dmingw32"></a>*-*-mingw32</h3>
1408 <p>GCC will build with and support only MinGW runtime 3.12 and later.
1409 Earlier versions of headers are incompatible with the new default semantics
1410 of <code>extern inline</code> in <code>-std=c99</code> and <code>-std=gnu99</code> modes.
1414 <h3 class="heading"><a name="TOC74"></a><a name="older"></a>Older systems</h3>
1416 <p>GCC contains support files for many older (1980s and early
1417 1990s) Unix variants. For the most part, support for these systems
1418 has not been deliberately removed, but it has not been maintained for
1419 several years and may suffer from bitrot.
1421 <p>Starting with GCC 3.1, each release has a list of “obsoleted” systems.
1422 Support for these systems is still present in that release, but
1423 <samp><span class="command">configure</span></samp> will fail unless the <samp><span class="option">--enable-obsolete</span></samp>
1424 option is given. Unless a maintainer steps forward, support for these
1425 systems will be removed from the next release of GCC.
1427 <p>Support for old systems as hosts for GCC can cause problems if the
1428 workarounds for compiler, library and operating system bugs affect the
1429 cleanliness or maintainability of the rest of GCC. In some cases, to
1430 bring GCC up on such a system, if still possible with current GCC, may
1431 require first installing an old version of GCC which did work on that
1432 system, and using it to compile a more recent GCC, to avoid bugs in the
1433 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
1434 <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
1435 <samp><span class="command">fixincludes</span></samp>, but bugs or deficiencies in libraries and the
1436 operating system may still cause problems.
1438 <p>Support for older systems as targets for cross-compilation is less
1439 problematic than support for them as hosts for GCC; if an enthusiast
1440 wishes to make such a target work again (including resurrecting any of
1441 the targets that never worked with GCC 2, starting from the last
1442 version before they were removed), patches
1443 <a href="../contribute.html">following the usual requirements</a> would be
1444 likely to be accepted, since they should not affect the support for more
1447 <p>For some systems, old versions of GNU binutils may also be useful,
1448 and are available from <samp><span class="file">pub/binutils/old-releases</span></samp> on
1449 <a href="http://sourceware.org/mirrors.html">sourceware.org mirror sites</a>.
1451 <p>Some of the information on specific systems above relates to
1452 such older systems, but much of the information
1453 about GCC on such systems (which may no longer be applicable to
1454 current GCC) is to be found in the GCC texinfo manual.
1458 <h3 class="heading"><a name="TOC75"></a><a name="elf"></a>all ELF targets (SVR4, Solaris 2, etc.)</h3>
1460 <p>C++ support is significantly better on ELF targets if you use the
1461 <a href="./configure.html#with-gnu-ld">GNU linker</a>; duplicate copies of
1462 inlines, vtables and template instantiations will be discarded
1466 <p><a href="./index.html">Return to the GCC Installation page</a>
1468 <!-- ***Old documentation****************************************************** -->
1469 <!-- ***GFDL******************************************************************** -->
1470 <!-- *************************************************************************** -->
1471 <!-- Part 6 The End of the Document -->