specific.html revision 1.7 1 <html lang="en">
2 <head>
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">
9 <!--
10 Copyright (C) 1988-2017 Free Software Foundation, Inc.
11
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".
18
19 (a) The FSF's Front-Cover Text is:
20
21 A GNU Manual
22
23 (b) The FSF's Back-Cover Text is:
24
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; }
39 --></style>
40 </head>
41 <body>
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.
46
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
50 information have to.
51
52 <ul>
53 <li><a href="#aarch64-x-x">aarch64*-*-*</a>
54 <li><a href="#alpha-x-x">alpha*-*-*</a>
55 <li><a href="#alpha-dec-osf51">alpha*-dec-osf5.1</a>
56 <li><a href="#amd64-x-solaris210">amd64-*-solaris2.10</a>
57 <li><a href="#arm-x-eabi">arm-*-eabi</a>
58 <li><a href="#avr">avr</a>
59 <li><a href="#bfin">Blackfin</a>
60 <li><a href="#dos">DOS</a>
61 <li><a href="#x-x-freebsd">*-*-freebsd*</a>
62 <li><a href="#h8300-hms">h8300-hms</a>
63 <li><a href="#hppa-hp-hpux">hppa*-hp-hpux*</a>
64 <li><a href="#hppa-hp-hpux10">hppa*-hp-hpux10</a>
65 <li><a href="#hppa-hp-hpux11">hppa*-hp-hpux11</a>
66 <li><a href="#x-x-linux-gnu">*-*-linux-gnu</a>
67 <li><a href="#ix86-x-linux">i?86-*-linux*</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="#nds32le-x-elf">nds32le-*-elf</a>
85 <li><a href="#nds32be-x-elf">nds32be-*-elf</a>
86 <li><a href="#nvptx-x-none">nvptx-*-none</a>
87 <li><a href="#powerpc-x-x">powerpc*-*-*</a>
88 <li><a href="#powerpc-x-darwin">powerpc-*-darwin*</a>
89 <li><a href="#powerpc-x-elf">powerpc-*-elf</a>
90 <li><a href="#powerpc-x-linux-gnu">powerpc*-*-linux-gnu*</a>
91 <li><a href="#powerpc-x-netbsd">powerpc-*-netbsd*</a>
92 <li><a href="#powerpc-x-eabisim">powerpc-*-eabisim</a>
93 <li><a href="#powerpc-x-eabi">powerpc-*-eabi</a>
94 <li><a href="#powerpcle-x-elf">powerpcle-*-elf</a>
95 <li><a href="#powerpcle-x-eabisim">powerpcle-*-eabisim</a>
96 <li><a href="#powerpcle-x-eabi">powerpcle-*-eabi</a>
97 <li><a href="#s390-x-linux">s390-*-linux*</a>
98 <li><a href="#s390x-x-linux">s390x-*-linux*</a>
99 <li><a href="#s390x-ibm-tpf">s390x-ibm-tpf*</a>
100 <li><a href="#x-x-solaris2">*-*-solaris2*</a>
101 <li><a href="#sparc-x-x">sparc*-*-*</a>
102 <li><a href="#sparc-sun-solaris2">sparc-sun-solaris2*</a>
103 <li><a href="#sparc-sun-solaris210">sparc-sun-solaris2.10</a>
104 <li><a href="#sparc-x-linux">sparc-*-linux*</a>
105 <li><a href="#sparc64-x-solaris2">sparc64-*-solaris2*</a>
106 <li><a href="#sparcv9-x-solaris2">sparcv9-*-solaris2*</a>
107 <li><a href="#c6x-x-x">c6x-*-*</a>
108 <li><a href="#tilegx-x-linux">tilegx-*-linux*</a>
109 <li><a href="#tilegxbe-x-linux">tilegxbe-*-linux*</a>
110 <li><a href="#tilepro-x-linux">tilepro-*-linux*</a>
111 <li><a href="#visium-x-elf">visium-*-elf</a>
112 <li><a href="#x-x-vxworks">*-*-vxworks*</a>
113 <li><a href="#x86-64-x-x">x86_64-*-*</a> amd64-*-*
114 <li><a href="#x86-64-x-solaris210">x86_64-*-solaris2.1[0-9]*</a>
115 <li><a href="#xtensa-x-elf">xtensa*-*-elf</a>
116 <li><a href="#xtensa-x-linux">xtensa*-*-linux*</a>
117 <li><a href="#windows">Microsoft Windows</a>
118 <li><a href="#x-x-cygwin">*-*-cygwin</a>
119 <li><a href="#x-x-interix">*-*-interix</a>
120 <li><a href="#x-x-mingw32">*-*-mingw32</a>
121 <li><a href="#os2">OS/2</a>
122 <li><a href="#older">Older systems</a>
123 </ul>
124
125 <ul>
126 <li><a href="#elf">all ELF targets</a> (SVR4, Solaris 2, etc.)
127 </ul>
128
129 <p><!-- -------- host/target specific issues start here ---------------- -->
130 <hr /><a name="aarch64_002dx_002dx"></a>
131
132 <h3 class="heading"><a name="TOC0"></a>aarch64*-*-*</h3>
133
134 <p>Binutils pre 2.24 does not have support for selecting <samp><span class="option">-mabi</span></samp> and
135 does not support ILP32. If it is used to build GCC 4.9 or later, GCC will
136 not support option <samp><span class="option">-mabi=ilp32</span></samp>.
137
138 <p>To enable a workaround for the Cortex-A53 erratum number 835769 by default
139 (for all CPUs regardless of -mcpu option given) at configure time use the
140 <samp><span class="option">--enable-fix-cortex-a53-835769</span></samp> option. This will enable the fix by
141 default and can be explicitly disabled during compilation by passing the
142 <samp><span class="option">-mno-fix-cortex-a53-835769</span></samp> option. Conversely,
143 <samp><span class="option">--disable-fix-cortex-a53-835769</span></samp> will disable the workaround by
144 default. The workaround is disabled by default if neither of
145 <samp><span class="option">--enable-fix-cortex-a53-835769</span></samp> or
146 <samp><span class="option">--disable-fix-cortex-a53-835769</span></samp> is given at configure time.
147
148 <p>To enable a workaround for the Cortex-A53 erratum number 843419 by default
149 (for all CPUs regardless of -mcpu option given) at configure time use the
150 <samp><span class="option">--enable-fix-cortex-a53-843419</span></samp> option. This workaround is applied at
151 link time. Enabling the workaround will cause GCC to pass the relevant option
152 to the linker. It can be explicitly disabled during compilation by passing the
153 <samp><span class="option">-mno-fix-cortex-a53-843419</span></samp> option. Conversely,
154 <samp><span class="option">--disable-fix-cortex-a53-843419</span></samp> will disable the workaround by default.
155 The workaround is disabled by default if neither of
156 <samp><span class="option">--enable-fix-cortex-a53-843419</span></samp> or
157 <samp><span class="option">--disable-fix-cortex-a53-843419</span></samp> is given at configure time.
158
159 <p><hr /><a name="alpha_002dx_002dx"></a>
160
161 <h3 class="heading"><a name="TOC1"></a>alpha*-*-*</h3>
162
163 <p>This section contains general configuration information for all
164 alpha-based platforms using ELF (in particular, ignore this section for
165 DEC OSF/1, Digital UNIX and Tru64 UNIX). In addition to reading this
166 section, please read all other sections that match your target.
167
168 <p>We require binutils 2.11.2 or newer.
169 Previous binutils releases had a number of problems with DWARF 2
170 debugging information, not the least of which is incorrect linking of
171 shared libraries.
172
173 <p><hr /><a name="alpha_002ddec_002dosf51"></a>
174
175 <h3 class="heading"><a name="TOC2"></a>alpha*-dec-osf5.1</h3>
176
177 <p>Systems using processors that implement the DEC Alpha architecture and
178 are running the DEC/Compaq/HP Unix (DEC OSF/1, Digital UNIX, or Compaq/HP
179 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
180
181 <p>Support for Tru64 UNIX V5.1 has been removed in GCC 4.8. As of GCC 4.6,
182 support for Tru64 UNIX V4.0 and V5.0 has been removed. As of GCC 3.2,
183 versions before <code>alpha*-dec-osf4</code> are no longer supported. (These
184 are the versions which identify themselves as DEC OSF/1.)
185
186 <p><hr /><a name="amd64_002dx_002dsolaris210"></a>
187
188 <h3 class="heading"><a name="TOC3"></a>amd64-*-solaris2.1[0-9]*</h3>
189
190 <p>This is a synonym for ‘<samp><span class="samp">x86_64-*-solaris2.1[0-9]*</span></samp>’.
191
192 <p><hr /><a name="arc_002dx_002delf32"></a>
193
194 <h3 class="heading"><a name="TOC4"></a>arc-*-elf32</h3>
195
196 <p>Use ‘<samp><span class="samp">configure --target=arc-elf32 --with-cpu=</span><var>cpu</var><span class="samp"> --enable-languages="c,c++"</span></samp>’
197 to configure GCC, with <var>cpu</var> being one of ‘<samp><span class="samp">arc600</span></samp>’, ‘<samp><span class="samp">arc601</span></samp>’,
198 or ‘<samp><span class="samp">arc700</span></samp>’.
199
200 <p><hr /><a name="arc_002dlinux_002duclibc"></a>
201
202 <h3 class="heading"><a name="TOC5"></a>arc-linux-uclibc</h3>
203
204 <p>Use ‘<samp><span class="samp">configure --target=arc-linux-uclibc --with-cpu=arc700 --enable-languages="c,c++"</span></samp>’ to configure GCC.
205
206 <p><hr /><a name="arm_002dx_002deabi"></a>
207
208 <h3 class="heading"><a name="TOC6"></a>arm-*-eabi</h3>
209
210 <p>ARM-family processors. Subtargets that use the ELF object format
211 require GNU binutils 2.13 or newer. Such subtargets include:
212 <code>arm-*-netbsdelf</code>, <code>arm-*-*linux-*</code>
213 and <code>arm-*-rtemseabi</code>.
214
215 <p>Building the Ada frontend commonly fails (an infinite loop executing
216 <code>xsinfo</code>) if the host compiler is GNAT 4.8. Host compilers built from the
217 GNAT 4.6, 4.9 or 5 release branches are known to succeed.
218
219 <p><hr /><a name="avr"></a>
220
221 <h3 class="heading"><a name="TOC7"></a>avr</h3>
222
223 <p>ATMEL AVR-family micro controllers. These are used in embedded
224 applications. There are no standard Unix configurations.
225 See “AVR Options” in the main manual
226 for the list of supported MCU types.
227
228 <p>Use ‘<samp><span class="samp">configure --target=avr --enable-languages="c"</span></samp>’ to configure GCC.
229
230 <p>Further installation notes and other useful information about AVR tools
231 can also be obtained from:
232
233 <ul>
234 <li><a href="http://www.nongnu.org/avr/">http://www.nongnu.org/avr/</a>
235 <li><a href="http://www.amelek.gda.pl/avr/">http://www.amelek.gda.pl/avr/</a>
236 </ul>
237
238 <p>We <em>strongly</em> recommend using binutils 2.13 or newer.
239
240 <p>The following error:
241 <pre class="smallexample"> Error: register required
242 </pre>
243 <p>indicates that you should upgrade to a newer version of the binutils.
244
245 <p><hr /><a name="bfin"></a>
246
247 <h3 class="heading"><a name="TOC8"></a>Blackfin</h3>
248
249 <p>The Blackfin processor, an Analog Devices DSP.
250 See “Blackfin Options” in the main manual
251
252 <p>More information, and a version of binutils with support for this processor,
253 is available at <a href="http://blackfin.uclinux.org">http://blackfin.uclinux.org</a>
254
255 <p><hr /><a name="cr16"></a>
256
257 <h3 class="heading"><a name="TOC9"></a>CR16</h3>
258
259 <p>The CR16 CompactRISC architecture is a 16-bit architecture. This
260 architecture is used in embedded applications.
261
262 <p>See “CR16 Options” in the main manual for a list of CR16-specific options.
263
264 <p>Use ‘<samp><span class="samp">configure --target=cr16-elf --enable-languages=c,c++</span></samp>’ to configure
265 GCC for building a CR16 elf cross-compiler.
266
267 <p>Use ‘<samp><span class="samp">configure --target=cr16-uclinux --enable-languages=c,c++</span></samp>’ to
268 configure GCC for building a CR16 uclinux cross-compiler.
269
270 <p><hr /><a name="cris"></a>
271
272 <h3 class="heading"><a name="TOC10"></a>CRIS</h3>
273
274 <p>CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
275 series. These are used in embedded applications.
276
277 <p>See “CRIS Options” in the main manual
278 for a list of CRIS-specific options.
279
280 <p>There are a few different CRIS targets:
281 <dl>
282 <dt><code>cris-axis-elf</code><dd>Mainly for monolithic embedded systems. Includes a multilib for the
283 ‘<samp><span class="samp">v10</span></samp>’ core used in ‘<samp><span class="samp">ETRAX 100 LX</span></samp>’.
284 <br><dt><code>cris-axis-linux-gnu</code><dd>A GNU/Linux port for the CRIS architecture, currently targeting
285 ‘<samp><span class="samp">ETRAX 100 LX</span></samp>’ by default.
286 </dl>
287
288 <p>For <code>cris-axis-elf</code> you need binutils 2.11
289 or newer. For <code>cris-axis-linux-gnu</code> you need binutils 2.12 or newer.
290
291 <p>Pre-packaged tools can be obtained from
292 <a href="ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/">ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/</a>. More
293 information about this platform is available at
294 <a href="http://developer.axis.com/">http://developer.axis.com/</a>.
295
296 <p><hr /><a name="dos"></a>
297
298 <h3 class="heading"><a name="TOC11"></a>DOS</h3>
299
300 <p>Please have a look at the <a href="binaries.html">binaries page</a>.
301
302 <p>You cannot install GCC by itself on MSDOS; it will not compile under
303 any MSDOS compiler except itself. You need to get the complete
304 compilation package DJGPP, which includes binaries as well as sources,
305 and includes all the necessary compilation tools and libraries.
306
307 <p><hr /><a name="epiphany_002dx_002delf"></a>
308
309 <h3 class="heading"><a name="TOC12"></a>epiphany-*-elf</h3>
310
311 <p>Adapteva Epiphany.
312 This configuration is intended for embedded systems.
313
314 <p><hr /><a name="x_002dx_002dfreebsd"></a>
315
316 <h3 class="heading"><a name="TOC13"></a>*-*-freebsd*</h3>
317
318 <p>Support for FreeBSD 1 was discontinued in GCC 3.2. Support for
319 FreeBSD 2 (and any mutant a.out variants of FreeBSD 3) was
320 discontinued in GCC 4.0.
321
322 <p>In order to better utilize FreeBSD base system functionality and match
323 the configuration of the system compiler, GCC 4.5 and above as well as
324 GCC 4.4 past 2010-06-20 leverage SSP support in libc (which is present
325 on FreeBSD 7 or later) and the use of <code>__cxa_atexit</code> by default
326 (on FreeBSD 6 or later). The use of <code>dl_iterate_phdr</code> inside
327 <samp><span class="file">libgcc_s.so.1</span></samp> and boehm-gc (on FreeBSD 7 or later) is enabled
328 by GCC 4.5 and above.
329
330 <p>We support FreeBSD using the ELF file format with DWARF 2 debugging
331 for all CPU architectures. You may use <samp><span class="option">-gstabs</span></samp> instead of
332 <samp><span class="option">-g</span></samp>, if you really want the old debugging format. There are
333 no known issues with mixing object files and libraries with different
334 debugging formats. Otherwise, this release of GCC should now match
335 more of the configuration used in the stock FreeBSD configuration of
336 GCC. In particular, <samp><span class="option">--enable-threads</span></samp> is now configured by
337 default. However, as a general user, do not attempt to replace the
338 system compiler with this release. Known to bootstrap and check with
339 good results on FreeBSD 7.2-STABLE. In the past, known to bootstrap
340 and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4,
341 4.5, 4.8, 4.9 and 5-CURRENT.
342
343 <p>The version of binutils installed in <samp><span class="file">/usr/bin</span></samp> probably works
344 with this release of GCC. Bootstrapping against the latest GNU
345 binutils and/or the version found in <samp><span class="file">/usr/ports/devel/binutils</span></samp> has
346 been known to enable additional features and improve overall testsuite
347 results. However, it is currently known that boehm-gc (which itself
348 is required for java) may not configure properly on FreeBSD prior to
349 the FreeBSD 7.0 release with GNU binutils after 2.16.1.
350
351 <p><hr /><a name="ft32_002dx_002delf"></a>
352
353 <h3 class="heading"><a name="TOC14"></a>ft32-*-elf</h3>
354
355 <p>The FT32 processor.
356 This configuration is intended for embedded systems.
357
358 <p><hr /><a name="h8300_002dhms"></a>
359
360 <h3 class="heading"><a name="TOC15"></a>h8300-hms</h3>
361
362 <p>Renesas H8/300 series of processors.
363
364 <p>Please have a look at the <a href="binaries.html">binaries page</a>.
365
366 <p>The calling convention and structure layout has changed in release 2.6.
367 All code must be recompiled. The calling convention now passes the
368 first three arguments in function calls in registers. Structures are no
369 longer a multiple of 2 bytes.
370
371 <p><hr /><a name="hppa_002dhp_002dhpux"></a>
372
373 <h3 class="heading"><a name="TOC16"></a>hppa*-hp-hpux*</h3>
374
375 <p>Support for HP-UX version 9 and older was discontinued in GCC 3.4.
376
377 <p>We require using gas/binutils on all hppa platforms. Version 2.19 or
378 later is recommended.
379
380 <p>It may be helpful to configure GCC with the
381 <a href="./configure.html#with-gnu-as"><samp><span class="option">--with-gnu-as</span></samp></a> and
382 <samp><span class="option">--with-as=...</span></samp> options to ensure that GCC can find GAS.
383
384 <p>The HP assembler should not be used with GCC. It is rarely tested and may
385 not work. It shouldn't be used with any languages other than C due to its
386 many limitations.
387
388 <p>Specifically, <samp><span class="option">-g</span></samp> does not work (HP-UX uses a peculiar debugging
389 format which GCC does not know about). It also inserts timestamps
390 into each object file it creates, causing the 3-stage comparison test to
391 fail during a bootstrap. You should be able to continue by saying
392 ‘<samp><span class="samp">make all-host all-target</span></samp>’ after getting the failure from ‘<samp><span class="samp">make</span></samp>’.
393
394 <p>Various GCC features are not supported. For example, it does not support weak
395 symbols or alias definitions. As a result, explicit template instantiations
396 are required when using C++. This makes it difficult if not impossible to
397 build many C++ applications.
398
399 <p>There are two default scheduling models for instructions. These are
400 PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
401 architecture specified for the target machine when configuring.
402 PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
403 the target is a ‘<samp><span class="samp">hppa1*</span></samp>’ machine.
404
405 <p>The PROCESSOR_8000 model is not well suited to older processors. Thus,
406 it is important to completely specify the machine architecture when
407 configuring if you want a model other than PROCESSOR_8000. The macro
408 TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
409 default scheduling model is desired.
410
411 <p>As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10
412 through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later.
413 This namespace change might cause problems when bootstrapping with
414 an earlier version of GCC or the HP compiler as essentially the same
415 namespace is required for an entire build. This problem can be avoided
416 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>’
417 or ‘<samp><span class="samp">98</span></samp>’. Another way is to add an appropriate set of predefines
418 to <samp><span class="env">CC</span></samp>. The description for the <samp><span class="option">munix=</span></samp> option contains
419 a list of the predefines used with each standard.
420
421 <p>More specific information to ‘<samp><span class="samp">hppa*-hp-hpux*</span></samp>’ targets follows.
422
423 <p><hr /><a name="hppa_002dhp_002dhpux10"></a>
424
425 <h3 class="heading"><a name="TOC17"></a>hppa*-hp-hpux10</h3>
426
427 <p>For hpux10.20, we <em>highly</em> recommend you pick up the latest sed patch
428 <code>PHCO_19798</code> from HP.
429
430 <p>The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces are
431 used for one-only code and data. This resolves many of the previous
432 problems in using C++ on this target. However, the ABI is not compatible
433 with the one implemented under HP-UX 11 using secondary definitions.
434
435 <p><hr /><a name="hppa_002dhp_002dhpux11"></a>
436
437 <h3 class="heading"><a name="TOC18"></a>hppa*-hp-hpux11</h3>
438
439 <p>GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot
440 be used to compile GCC 3.0 and up.
441
442 <p>The libffi and libjava libraries haven't been ported to 64-bit HP-UX and don't build.
443
444 <p>Refer to <a href="binaries.html">binaries</a> for information about obtaining
445 precompiled GCC binaries for HP-UX. Precompiled binaries must be obtained
446 to build the Ada language as it can't be bootstrapped using C. Ada is
447 only available for the 32-bit PA-RISC runtime.
448
449 <p>Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The
450 bundled compiler supports only traditional C; you will need either HP's
451 unbundled compiler, or a binary distribution of GCC.
452
453 <p>It is possible to build GCC 3.3 starting with the bundled HP compiler,
454 but the process requires several steps. GCC 3.3 can then be used to
455 build later versions. The fastjar program contains ISO C code and
456 can't be built with the HP bundled compiler. This problem can be
457 avoided by not building the Java language. For example, use the
458 <samp><span class="option">--enable-languages="c,c++,f77,objc"</span></samp> option in your configure
459 command.
460
461 <p>There are several possible approaches to building the distribution.
462 Binutils can be built first using the HP tools. Then, the GCC
463 distribution can be built. The second approach is to build GCC
464 first using the HP tools, then build binutils, then rebuild GCC.
465 There have been problems with various binary distributions, so it
466 is best not to start from a binary distribution.
467
468 <p>On 64-bit capable systems, there are two distinct targets. Different
469 installation prefixes must be used if both are to be installed on
470 the same system. The ‘<samp><span class="samp">hppa[1-2]*-hp-hpux11*</span></samp>’ target generates code
471 for the 32-bit PA-RISC runtime architecture and uses the HP linker.
472 The ‘<samp><span class="samp">hppa64-hp-hpux11*</span></samp>’ target generates 64-bit code for the
473 PA-RISC 2.0 architecture.
474
475 <p>The script config.guess now selects the target type based on the compiler
476 detected during configuration. You must define <samp><span class="env">PATH</span></samp> or <samp><span class="env">CC</span></samp> so
477 that configure finds an appropriate compiler for the initial bootstrap.
478 When <samp><span class="env">CC</span></samp> is used, the definition should contain the options that are
479 needed whenever <samp><span class="env">CC</span></samp> is used.
480
481 <p>Specifically, options that determine the runtime architecture must be
482 in <samp><span class="env">CC</span></samp> to correctly select the target for the build. It is also
483 convenient to place many other compiler options in <samp><span class="env">CC</span></samp>. For example,
484 <samp><span class="env">CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"</span></samp>
485 can be used to bootstrap the GCC 3.3 branch with the HP compiler in
486 64-bit K&R/bundled mode. The <samp><span class="option">+DA2.0W</span></samp> option will result in
487 the automatic selection of the ‘<samp><span class="samp">hppa64-hp-hpux11*</span></samp>’ target. The
488 macro definition table of cpp needs to be increased for a successful
489 build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to
490 be defined when building with the bundled compiler, or when using the
491 <samp><span class="option">-Ac</span></samp> option. These defines aren't necessary with <samp><span class="option">-Ae</span></samp>.
492
493 <p>It is best to explicitly configure the ‘<samp><span class="samp">hppa64-hp-hpux11*</span></samp>’ target
494 with the <samp><span class="option">--with-ld=...</span></samp> option. This overrides the standard
495 search for ld. The two linkers supported on this target require different
496 commands. The default linker is determined during configuration. As a
497 result, it's not possible to switch linkers in the middle of a GCC build.
498 This has been reported to sometimes occur in unified builds of binutils
499 and GCC.
500
501 <p>A recent linker patch must be installed for the correct operation of
502 GCC 3.3 and later. <code>PHSS_26559</code> and <code>PHSS_24304</code> are the
503 oldest linker patches that are known to work. They are for HP-UX
504 11.00 and 11.11, respectively. <code>PHSS_24303</code>, the companion to
505 <code>PHSS_24304</code>, might be usable but it hasn't been tested. These
506 patches have been superseded. Consult the HP patch database to obtain
507 the currently recommended linker patch for your system.
508
509 <p>The patches are necessary for the support of weak symbols on the
510 32-bit port, and for the running of initializers and finalizers. Weak
511 symbols are implemented using SOM secondary definition symbols. Prior
512 to HP-UX 11, there are bugs in the linker support for secondary symbols.
513 The patches correct a problem of linker core dumps creating shared
514 libraries containing secondary symbols, as well as various other
515 linking issues involving secondary symbols.
516
517 <p>GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
518 run initializers and finalizers on the 64-bit port. The 32-bit port
519 uses the linker <samp><span class="option">+init</span></samp> and <samp><span class="option">+fini</span></samp> options for the same
520 purpose. The patches correct various problems with the +init/+fini
521 options, including program core dumps. Binutils 2.14 corrects a
522 problem on the 64-bit port resulting from HP's non-standard use of
523 the .init and .fini sections for array initializers and finalizers.
524
525 <p>Although the HP and GNU linkers are both supported for the
526 ‘<samp><span class="samp">hppa64-hp-hpux11*</span></samp>’ target, it is strongly recommended that the
527 HP linker be used for link editing on this target.
528
529 <p>At this time, the GNU linker does not support the creation of long
530 branch stubs. As a result, it can't successfully link binaries
531 containing branch offsets larger than 8 megabytes. In addition,
532 there are problems linking shared libraries, linking executables
533 with <samp><span class="option">-static</span></samp>, and with dwarf2 unwind and exception support.
534 It also doesn't provide stubs for internal calls to global functions
535 in shared libraries, so these calls can't be overloaded.
536
537 <p>The HP dynamic loader does not support GNU symbol versioning, so symbol
538 versioning is not supported. It may be necessary to disable symbol
539 versioning with <samp><span class="option">--disable-symvers</span></samp> when using GNU ld.
540
541 <p>POSIX threads are the default. The optional DCE thread library is not
542 supported, so <samp><span class="option">--enable-threads=dce</span></samp> does not work.
543
544 <p><hr /><a name="x_002dx_002dlinux_002dgnu"></a>
545
546 <h3 class="heading"><a name="TOC19"></a>*-*-linux-gnu</h3>
547
548 <p>Versions of libstdc++-v3 starting with 3.2.1 require bug fixes present
549 in glibc 2.2.5 and later. More information is available in the
550 libstdc++-v3 documentation.
551
552 <p><hr /><a name="ix86_002dx_002dlinux"></a>
553
554 <h3 class="heading"><a name="TOC20"></a>i?86-*-linux*</h3>
555
556 <p>As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
557 See <a href="http://gcc.gnu.org/PR10877">bug 10877</a> for more information.
558
559 <p>If you receive Signal 11 errors when building on GNU/Linux, then it is
560 possible you have a hardware problem. Further information on this can be
561 found on <a href="http://www.bitwizard.nl/sig11/">www.bitwizard.nl</a>.
562
563 <p><hr /><a name="ix86_002dx_002dsolaris210"></a>
564
565 <h3 class="heading"><a name="TOC21"></a>i?86-*-solaris2.10</h3>
566
567 <p>Use this for Solaris 10 or later on x86 and x86-64 systems. Starting
568 with GCC 4.7, there is also a 64-bit ‘<samp><span class="samp">amd64-*-solaris2.1[0-9]*</span></samp>’ or
569 ‘<samp><span class="samp">x86_64-*-solaris2.1[0-9]*</span></samp>’ configuration that corresponds to
570 ‘<samp><span class="samp">sparcv9-sun-solaris2*</span></samp>’.
571
572 <p>It is recommended that you configure GCC to use the GNU assembler. The
573 versions included in Solaris 10, from GNU binutils 2.15 (in
574 <samp><span class="file">/usr/sfw/bin/gas</span></samp>), and Solaris 11, from GNU binutils 2.19 or
575 newer (also available as <samp><span class="file">/usr/bin/gas</span></samp> and
576 <samp><span class="file">/usr/gnu/bin/as</span></samp>), work fine. Please note that the current
577 version, from GNU binutils 2.26, only works on Solaris 12 when using the
578 Solaris linker. On Solaris 10 and 11, you either have to wait for GNU
579 binutils 2.26.1 or newer, or stay with GNU binutils 2.25.1. Recent
580 versions of the Solaris assembler in <samp><span class="file">/usr/ccs/bin/as</span></samp> work almost
581 as well, though.
582 <!-- FIXME: as patch requirements? -->
583
584 <p>For linking, the Solaris linker, is preferred. If you want to use the GNU
585 linker instead, note that due to a packaging bug the version in Solaris
586 10, from GNU binutils 2.15 (in <samp><span class="file">/usr/sfw/bin/gld</span></samp>), cannot be used,
587 while the version in Solaris 11, from GNU binutils 2.19 or newer (also
588 in <samp><span class="file">/usr/gnu/bin/ld</span></samp> and <samp><span class="file">/usr/bin/gld</span></samp>), works, as does the
589 latest version, from GNU binutils 2.26.
590
591 <p>To use GNU <samp><span class="command">as</span></samp>, configure with the options
592 <samp><span class="option">--with-gnu-as --with-as=/usr/sfw/bin/gas</span></samp>. It may be necessary
593 to configure with <samp><span class="option">--without-gnu-ld --with-ld=/usr/ccs/bin/ld</span></samp> to
594 guarantee use of Sun <samp><span class="command">ld</span></samp>.
595 <!-- FIXME: why -without-gnu-ld -with-ld? -->
596
597 <p><hr /><a name="ia64_002dx_002dlinux"></a>
598
599 <h3 class="heading"><a name="TOC22"></a>ia64-*-linux</h3>
600
601 <p>IA-64 processor (also known as IPF, or Itanium Processor Family)
602 running GNU/Linux.
603
604 <p>If you are using the installed system libunwind library with
605 <samp><span class="option">--with-system-libunwind</span></samp>, then you must use libunwind 0.98 or
606 later.
607
608 <p>None of the following versions of GCC has an ABI that is compatible
609 with any of the other versions in this list, with the exception that
610 Red Hat 2.96 and Trillian 000171 are compatible with each other:
611 3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
612 This primarily affects C++ programs and programs that create shared libraries.
613 GCC 3.1 or later is recommended for compiling linux, the kernel.
614 As of version 3.1 GCC is believed to be fully ABI compliant, and hence no
615 more major ABI changes are expected.
616
617 <p><hr /><a name="ia64_002dx_002dhpux"></a>
618
619 <h3 class="heading"><a name="TOC23"></a>ia64-*-hpux*</h3>
620
621 <p>Building GCC on this target requires the GNU Assembler. The bundled HP
622 assembler will not work. To prevent GCC from using the wrong assembler,
623 the option <samp><span class="option">--with-gnu-as</span></samp> may be necessary.
624
625 <p>The GCC libunwind library has not been ported to HPUX. This means that for
626 GCC versions 3.2.3 and earlier, <samp><span class="option">--enable-libunwind-exceptions</span></samp>
627 is required to build GCC. For GCC 3.3 and later, this is the default.
628 For gcc 3.4.3 and later, <samp><span class="option">--enable-libunwind-exceptions</span></samp> is
629 removed and the system libunwind library will always be used.
630
631 <p><hr />
632 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* --><a name="x_002dibm_002daix"></a>
633
634 <h3 class="heading"><a name="TOC24"></a>*-ibm-aix*</h3>
635
636 <p>Support for AIX version 3 and older was discontinued in GCC 3.4.
637 Support for AIX version 4.2 and older was discontinued in GCC 4.5.
638
639 <p>“out of memory” bootstrap failures may indicate a problem with
640 process resource limits (ulimit). Hard limits are configured in the
641 <samp><span class="file">/etc/security/limits</span></samp> system configuration file.
642
643 <p>GCC 4.9 and above require a C++ compiler for bootstrap. IBM VAC++ / xlC
644 cannot bootstrap GCC. xlc can bootstrap an older version of GCC and
645 G++ can bootstrap recent releases of GCC.
646
647 <p>GCC can bootstrap with recent versions of IBM XLC, but bootstrapping
648 with an earlier release of GCC is recommended. Bootstrapping with XLC
649 requires a larger data segment, which can be enabled through the
650 <var>LDR_CNTRL</var> environment variable, e.g.,
651
652 <pre class="smallexample"> % LDR_CNTRL=MAXDATA=0x50000000
653 % export LDR_CNTRL
654 </pre>
655 <p>One can start with a pre-compiled version of GCC to build from
656 sources. One may delete GCC's “fixed” header files when starting
657 with a version of GCC built for an earlier release of AIX.
658
659 <p>To speed up the configuration phases of bootstrapping and installing GCC,
660 one may use GNU Bash instead of AIX <samp><span class="command">/bin/sh</span></samp>, e.g.,
661
662 <pre class="smallexample"> % CONFIG_SHELL=/opt/freeware/bin/bash
663 % export CONFIG_SHELL
664 </pre>
665 <p>and then proceed as described in <a href="build.html">the build instructions</a>, where we strongly recommend specifying an absolute path
666 to invoke <var>srcdir</var>/configure.
667
668 <p>Because GCC on AIX is built as a 32-bit executable by default,
669 (although it can generate 64-bit programs) the GMP and MPFR libraries
670 required by gfortran must be 32-bit libraries. Building GMP and MPFR
671 as static archive libraries works better than shared libraries.
672
673 <p>Errors involving <code>alloca</code> when building GCC generally are due
674 to an incorrect definition of <code>CC</code> in the Makefile or mixing files
675 compiled with the native C compiler and GCC. During the stage1 phase of
676 the build, the native AIX compiler <strong>must</strong> be invoked as <samp><span class="command">cc</span></samp>
677 (not <samp><span class="command">xlc</span></samp>). Once <samp><span class="command">configure</span></samp> has been informed of
678 <samp><span class="command">xlc</span></samp>, one needs to use ‘<samp><span class="samp">make distclean</span></samp>’ to remove the
679 configure cache files and ensure that <samp><span class="env">CC</span></samp> environment variable
680 does not provide a definition that will confuse <samp><span class="command">configure</span></samp>.
681 If this error occurs during stage2 or later, then the problem most likely
682 is the version of Make (see above).
683
684 <p>The native <samp><span class="command">as</span></samp> and <samp><span class="command">ld</span></samp> are recommended for
685 bootstrapping on AIX. The GNU Assembler, GNU Linker, and GNU
686 Binutils version 2.20 is the minimum level that supports bootstrap on
687 AIX 5. The GNU Assembler has not been updated to support AIX 6 or
688 AIX 7. The native AIX tools do interoperate with GCC.
689
690 <p>AIX 7.1 added partial support for DWARF debugging, but full support
691 requires AIX 7.1 TL03 SP7 that supports additional DWARF sections and
692 fixes a bug in the assembler. AIX 7.1 TL03 SP5 distributed a version
693 of libm.a missing important symbols; a fix for IV77796 will be
694 included in SP6.
695
696 <p>AIX 5.3 TL10, AIX 6.1 TL05 and AIX 7.1 TL00 introduced an AIX
697 assembler change that sometimes produces corrupt assembly files
698 causing AIX linker errors. The bug breaks GCC bootstrap on AIX and
699 can cause compilation failures with existing GCC installations. An
700 AIX iFix for AIX 5.3 is available (APAR IZ98385 for AIX 5.3 TL10, APAR
701 IZ98477 for AIX 5.3 TL11 and IZ98134 for AIX 5.3 TL12). AIX 5.3 TL11 SP8,
702 AIX 5.3 TL12 SP5, AIX 6.1 TL04 SP11, AIX 6.1 TL05 SP7, AIX 6.1 TL06 SP6,
703 AIX 6.1 TL07 and AIX 7.1 TL01 should include the fix.
704
705 <p>Building <samp><span class="file">libstdc++.a</span></samp> requires a fix for an AIX Assembler bug
706 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a
707 fix for another AIX Assembler bug and a co-dependent AIX Archiver fix
708 referenced as APAR IY53606 (AIX 5.2) or as APAR IY54774 (AIX 5.1)
709
710 <p><a name="TransferAixShobj"></a>‘<samp><span class="samp">libstdc++</span></samp>’ in GCC 3.4 increments the major version number of the
711 shared object and GCC installation places the <samp><span class="file">libstdc++.a</span></samp>
712 shared library in a common location which will overwrite the and GCC
713 3.3 version of the shared library. Applications either need to be
714 re-linked against the new shared library or the GCC 3.1 and GCC 3.3
715 versions of the ‘<samp><span class="samp">libstdc++</span></samp>’ shared object needs to be available
716 to the AIX runtime loader. The GCC 3.1 ‘<samp><span class="samp">libstdc++.so.4</span></samp>’, if
717 present, and GCC 3.3 ‘<samp><span class="samp">libstdc++.so.5</span></samp>’ shared objects can be
718 installed for runtime dynamic loading using the following steps to set
719 the ‘<samp><span class="samp">F_LOADONLY</span></samp>’ flag in the shared object for <em>each</em>
720 multilib <samp><span class="file">libstdc++.a</span></samp> installed:
721
722 <p>Extract the shared objects from the currently installed
723 <samp><span class="file">libstdc++.a</span></samp> archive:
724 <pre class="smallexample"> % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
725 </pre>
726 <p>Enable the ‘<samp><span class="samp">F_LOADONLY</span></samp>’ flag so that the shared object will be
727 available for runtime dynamic loading, but not linking:
728 <pre class="smallexample"> % strip -e libstdc++.so.4 libstdc++.so.5
729 </pre>
730 <p>Archive the runtime-only shared object in the GCC 3.4
731 <samp><span class="file">libstdc++.a</span></samp> archive:
732 <pre class="smallexample"> % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
733 </pre>
734 <p>Eventually, the
735 <a href="./configure.html#WithAixSoname"><samp><span class="option">--with-aix-soname=svr4</span></samp></a>
736 configure option may drop the need for this procedure for libraries that
737 support it.
738
739 <p>Linking executables and shared libraries may produce warnings of
740 duplicate symbols. The assembly files generated by GCC for AIX always
741 have included multiple symbol definitions for certain global variable
742 and function declarations in the original program. The warnings should
743 not prevent the linker from producing a correct library or runnable
744 executable.
745
746 <p>AIX 4.3 utilizes a “large format” archive to support both 32-bit and
747 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
748 to parse archive libraries did not handle the new format correctly.
749 These routines are used by GCC and result in error messages during
750 linking such as “not a COFF file”. The version of the routines shipped
751 with AIX 4.3.1 should work for a 32-bit environment. The <samp><span class="option">-g</span></samp>
752 option of the archive command may be used to create archives of 32-bit
753 objects using the original “small format”. A correct version of the
754 routines is shipped with AIX 4.3.2 and above.
755
756 <p>Some versions of the AIX binder (linker) can fail with a relocation
757 overflow severe error when the <samp><span class="option">-bbigtoc</span></samp> option is used to link
758 GCC-produced object files into an executable that overflows the TOC. A fix
759 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
760 available from IBM Customer Support and from its
761 <a href="http://techsupport.services.ibm.com/">techsupport.services.ibm.com</a>
762 website as PTF U455193.
763
764 <p>The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
765 with a segmentation fault when invoked by any version of GCC. A fix for
766 APAR IX87327 is available from IBM Customer Support and from its
767 <a href="http://techsupport.services.ibm.com/">techsupport.services.ibm.com</a>
768 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
769
770 <p>The initial assembler shipped with AIX 4.3.0 generates incorrect object
771 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
772 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
773 <a href="http://techsupport.services.ibm.com/">techsupport.services.ibm.com</a>
774 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
775
776 <p>AIX provides National Language Support (NLS). Compilers and assemblers
777 use NLS to support locale-specific representations of various data
778 formats including floating-point numbers (e.g., ‘<samp><span class="samp">.</span></samp>’ vs ‘<samp><span class="samp">,</span></samp>’ for
779 separating decimal fractions). There have been problems reported where
780 GCC does not produce the same floating-point formats that the assembler
781 expects. If one encounters this problem, set the <samp><span class="env">LANG</span></samp>
782 environment variable to ‘<samp><span class="samp">C</span></samp>’ or ‘<samp><span class="samp">En_US</span></samp>’.
783
784 <p>A default can be specified with the <samp><span class="option">-mcpu=</span><var>cpu_type</var></samp>
785 switch and using the configure option <samp><span class="option">--with-cpu-</span><var>cpu_type</var></samp>.
786
787 <p><hr /><a name="iq2000_002dx_002delf"></a>
788
789 <h3 class="heading"><a name="TOC25"></a>iq2000-*-elf</h3>
790
791 <p>Vitesse IQ2000 processors. These are used in embedded
792 applications. There are no standard Unix configurations.
793
794 <p><hr /><a name="lm32_002dx_002delf"></a>
795
796 <h3 class="heading"><a name="TOC26"></a>lm32-*-elf</h3>
797
798 <p>Lattice Mico32 processor.
799 This configuration is intended for embedded systems.
800
801 <p><hr /><a name="lm32_002dx_002duclinux"></a>
802
803 <h3 class="heading"><a name="TOC27"></a>lm32-*-uclinux</h3>
804
805 <p>Lattice Mico32 processor.
806 This configuration is intended for embedded systems running uClinux.
807
808 <p><hr /><a name="m32c_002dx_002delf"></a>
809
810 <h3 class="heading"><a name="TOC28"></a>m32c-*-elf</h3>
811
812 <p>Renesas M32C processor.
813 This configuration is intended for embedded systems.
814
815 <p><hr /><a name="m32r_002dx_002delf"></a>
816
817 <h3 class="heading"><a name="TOC29"></a>m32r-*-elf</h3>
818
819 <p>Renesas M32R processor.
820 This configuration is intended for embedded systems.
821
822 <p><hr /><a name="m68k_002dx_002dx"></a>
823
824 <h3 class="heading"><a name="TOC30"></a>m68k-*-*</h3>
825
826 <p>By default,
827 ‘<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
828 ‘<samp><span class="samp">m68k-*-linux</span></samp>’
829 build libraries for both M680x0 and ColdFire processors. If you only
830 need the M680x0 libraries, you can omit the ColdFire ones by passing
831 <samp><span class="option">--with-arch=m68k</span></samp> to <samp><span class="command">configure</span></samp>. Alternatively, you
832 can omit the M680x0 libraries by passing <samp><span class="option">--with-arch=cf</span></samp> to
833 <samp><span class="command">configure</span></samp>. These targets default to 5206 or 5475 code as
834 appropriate for the target system when
835 configured with <samp><span class="option">--with-arch=cf</span></samp> and 68020 code otherwise.
836
837 <p>The ‘<samp><span class="samp">m68k-*-netbsd</span></samp>’ and
838 ‘<samp><span class="samp">m68k-*-openbsd</span></samp>’ targets also support the <samp><span class="option">--with-arch</span></samp>
839 option. They will generate ColdFire CFV4e code when configured with
840 <samp><span class="option">--with-arch=cf</span></samp> and 68020 code otherwise.
841
842 <p>You can override the default processors listed above by configuring
843 with <samp><span class="option">--with-cpu=</span><var>target</var></samp>. This <var>target</var> can either
844 be a <samp><span class="option">-mcpu</span></samp> argument or one of the following values:
845 ‘<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>’,
846 ‘<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>’.
847
848 <p>GCC requires at least binutils version 2.17 on these targets.
849
850 <p><hr /><a name="m68k_002dx_002duclinux"></a>
851
852 <h3 class="heading"><a name="TOC31"></a>m68k-*-uclinux</h3>
853
854 <p>GCC 4.3 changed the uClinux configuration so that it uses the
855 ‘<samp><span class="samp">m68k-linux-gnu</span></samp>’ ABI rather than the ‘<samp><span class="samp">m68k-elf</span></samp>’ ABI.
856 It also added improved support for C++ and flat shared libraries,
857 both of which were ABI changes.
858
859 <p><hr /><a name="mep_002dx_002delf"></a>
860
861 <h3 class="heading"><a name="TOC32"></a>mep-*-elf</h3>
862
863 <p>Toshiba Media embedded Processor.
864 This configuration is intended for embedded systems.
865
866 <p><hr /><a name="microblaze_002dx_002delf"></a>
867
868 <h3 class="heading"><a name="TOC33"></a>microblaze-*-elf</h3>
869
870 <p>Xilinx MicroBlaze processor.
871 This configuration is intended for embedded systems.
872
873 <p><hr /><a name="mips_002dx_002dx"></a>
874
875 <h3 class="heading"><a name="TOC34"></a>mips-*-*</h3>
876
877 <p>If on a MIPS system you get an error message saying “does not have gp
878 sections for all it's [sic] sectons [sic]”, don't worry about it. This
879 happens whenever you use GAS with the MIPS linker, but there is not
880 really anything wrong, and it is okay to use the output file. You can
881 stop such warnings by installing the GNU linker.
882
883 <p>It would be nice to extend GAS to produce the gp tables, but they are
884 optional, and there should not be a warning about their absence.
885
886 <p>The libstdc++ atomic locking routines for MIPS targets requires MIPS II
887 and later. A patch went in just after the GCC 3.3 release to
888 make ‘<samp><span class="samp">mips*-*-*</span></samp>’ use the generic implementation instead. You can also
889 configure for ‘<samp><span class="samp">mipsel-elf</span></samp>’ as a workaround. The
890 ‘<samp><span class="samp">mips*-*-linux*</span></samp>’ target continues to use the MIPS II routines. More
891 work on this is expected in future releases.
892
893 <!-- If you make -with-llsc the default for another target, please also -->
894 <!-- update the description of the -with-llsc option. -->
895 <p>The built-in <code>__sync_*</code> functions are available on MIPS II and
896 later systems and others that support the ‘<samp><span class="samp">ll</span></samp>’, ‘<samp><span class="samp">sc</span></samp>’ and
897 ‘<samp><span class="samp">sync</span></samp>’ instructions. This can be overridden by passing
898 <samp><span class="option">--with-llsc</span></samp> or <samp><span class="option">--without-llsc</span></samp> when configuring GCC.
899 Since the Linux kernel emulates these instructions if they are
900 missing, the default for ‘<samp><span class="samp">mips*-*-linux*</span></samp>’ targets is
901 <samp><span class="option">--with-llsc</span></samp>. The <samp><span class="option">--with-llsc</span></samp> and
902 <samp><span class="option">--without-llsc</span></samp> configure options may be overridden at compile
903 time by passing the <samp><span class="option">-mllsc</span></samp> or <samp><span class="option">-mno-llsc</span></samp> options to
904 the compiler.
905
906 <p>MIPS systems check for division by zero (unless
907 <samp><span class="option">-mno-check-zero-division</span></samp> is passed to the compiler) by
908 generating either a conditional trap or a break instruction. Using
909 trap results in smaller code, but is only supported on MIPS II and
910 later. Also, some versions of the Linux kernel have a bug that
911 prevents trap from generating the proper signal (<code>SIGFPE</code>). To enable
912 the use of break, use the <samp><span class="option">--with-divide=breaks</span></samp>
913 <samp><span class="command">configure</span></samp> option when configuring GCC. The default is to
914 use traps on systems that support them.
915
916 <p>The assembler from GNU binutils 2.17 and earlier has a bug in the way
917 it sorts relocations for REL targets (o32, o64, EABI). This can cause
918 bad code to be generated for simple C++ programs. Also the linker
919 from GNU binutils versions prior to 2.17 has a bug which causes the
920 runtime linker stubs in very large programs, like <samp><span class="file">libgcj.so</span></samp>, to
921 be incorrectly generated. GNU Binutils 2.18 and later (and snapshots
922 made after Nov. 9, 2006) should be free from both of these problems.
923
924 <p><hr /><a name="mips_002dsgi_002dirix5"></a>
925
926 <h3 class="heading"><a name="TOC35"></a>mips-sgi-irix5</h3>
927
928 <p>Support for IRIX 5 has been removed in GCC 4.6.
929
930 <p><hr /><a name="mips_002dsgi_002dirix6"></a>
931
932 <h3 class="heading"><a name="TOC36"></a>mips-sgi-irix6</h3>
933
934 <p>Support for IRIX 6.5 has been removed in GCC 4.8. Support for IRIX 6
935 releases before 6.5 has been removed in GCC 4.6, as well as support for
936 the O32 ABI.
937
938 <p><hr /><a name="moxie_002dx_002delf"></a>
939
940 <h3 class="heading"><a name="TOC37"></a>moxie-*-elf</h3>
941
942 <p>The moxie processor.
943
944 <p><hr /><a name="msp430_002dx_002delf"></a>
945
946 <h3 class="heading"><a name="TOC38"></a>msp430-*-elf</h3>
947
948 <p>TI MSP430 processor.
949 This configuration is intended for embedded systems.
950
951 <p><hr /><a name="nds32le_002dx_002delf"></a>
952
953 <h3 class="heading"><a name="TOC39"></a>nds32le-*-elf</h3>
954
955 <p>Andes NDS32 target in little endian mode.
956
957 <p><hr /><a name="nds32be_002dx_002delf"></a>
958
959 <h3 class="heading"><a name="TOC40"></a>nds32be-*-elf</h3>
960
961 <p>Andes NDS32 target in big endian mode.
962
963 <p><hr /><a name="nvptx_002dx_002dnone"></a>
964
965 <h3 class="heading"><a name="TOC41"></a>nvptx-*-none</h3>
966
967 <p>Nvidia PTX target.
968
969 <p>Instead of GNU binutils, you will need to install
970 <a href="https://github.com/MentorEmbedded/nvptx-tools/">nvptx-tools</a>.
971 Tell GCC where to find it:
972 <samp><span class="option">--with-build-time-tools=[install-nvptx-tools]/nvptx-none/bin</span></samp>.
973
974 <p>A nvptx port of newlib is available at
975 <a href="https://github.com/MentorEmbedded/nvptx-newlib/">nvptx-newlib</a>.
976 It can be automatically built together with GCC. For this, add a
977 symbolic link to nvptx-newlib's <samp><span class="file">newlib</span></samp> directory to the
978 directory containing the GCC sources.
979
980 <p>Use the <samp><span class="option">--disable-sjlj-exceptions</span></samp> and
981 <samp><span class="option">--enable-newlib-io-long-long</span></samp> options when configuring.
982
983 <p><hr /><a name="powerpc_002dx_002dx"></a>
984
985 <h3 class="heading"><a name="TOC42"></a>powerpc-*-*</h3>
986
987 <p>You can specify a default version for the <samp><span class="option">-mcpu=</span><var>cpu_type</var></samp>
988 switch by using the configure option <samp><span class="option">--with-cpu-</span><var>cpu_type</var></samp>.
989
990 <p>You will need
991 <a href="ftp://ftp.kernel.org/pub/linux/devel/binutils">binutils 2.15</a>
992 or newer for a working GCC.
993
994 <p><hr /><a name="powerpc_002dx_002ddarwin"></a>
995
996 <h3 class="heading"><a name="TOC43"></a>powerpc-*-darwin*</h3>
997
998 <p>PowerPC running Darwin (Mac OS X kernel).
999
1000 <p>Pre-installed versions of Mac OS X may not include any developer tools,
1001 meaning that you will not be able to build GCC from source. Tool
1002 binaries are available at
1003 <a href="http://opensource.apple.com/">http://opensource.apple.com/</a>.
1004
1005 <p>This version of GCC requires at least cctools-590.36. The
1006 cctools-590.36 package referenced from
1007 <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
1008 on systems older than 10.3.9 (aka darwin7.9.0).
1009
1010 <p><hr /><a name="powerpc_002dx_002delf"></a>
1011
1012 <h3 class="heading"><a name="TOC44"></a>powerpc-*-elf</h3>
1013
1014 <p>PowerPC system in big endian mode, running System V.4.
1015
1016 <p><hr /><a name="powerpc_002dx_002dlinux_002dgnu"></a>
1017
1018 <h3 class="heading"><a name="TOC45"></a>powerpc*-*-linux-gnu*</h3>
1019
1020 <p>PowerPC system in big endian mode running Linux.
1021
1022 <p><hr /><a name="powerpc_002dx_002dnetbsd"></a>
1023
1024 <h3 class="heading"><a name="TOC46"></a>powerpc-*-netbsd*</h3>
1025
1026 <p>PowerPC system in big endian mode running NetBSD.
1027
1028 <p><hr /><a name="powerpc_002dx_002deabisim"></a>
1029
1030 <h3 class="heading"><a name="TOC47"></a>powerpc-*-eabisim</h3>
1031
1032 <p>Embedded PowerPC system in big endian mode for use in running under the
1033 PSIM simulator.
1034
1035 <p><hr /><a name="powerpc_002dx_002deabi"></a>
1036
1037 <h3 class="heading"><a name="TOC48"></a>powerpc-*-eabi</h3>
1038
1039 <p>Embedded PowerPC system in big endian mode.
1040
1041 <p><hr /><a name="powerpcle_002dx_002delf"></a>
1042
1043 <h3 class="heading"><a name="TOC49"></a>powerpcle-*-elf</h3>
1044
1045 <p>PowerPC system in little endian mode, running System V.4.
1046
1047 <p><hr /><a name="powerpcle_002dx_002deabisim"></a>
1048
1049 <h3 class="heading"><a name="TOC50"></a>powerpcle-*-eabisim</h3>
1050
1051 <p>Embedded PowerPC system in little endian mode for use in running under
1052 the PSIM simulator.
1053
1054 <p><hr /><a name="powerpcle_002dx_002deabi"></a>
1055
1056 <h3 class="heading"><a name="TOC51"></a>powerpcle-*-eabi</h3>
1057
1058 <p>Embedded PowerPC system in little endian mode.
1059
1060 <p><hr /><a name="rl78_002dx_002delf"></a>
1061
1062 <h3 class="heading"><a name="TOC52"></a>rl78-*-elf</h3>
1063
1064 <p>The Renesas RL78 processor.
1065 This configuration is intended for embedded systems.
1066
1067 <p><hr /><a name="rx_002dx_002delf"></a>
1068
1069 <h3 class="heading"><a name="TOC53"></a>rx-*-elf</h3>
1070
1071 <p>The Renesas RX processor. See
1072 <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>
1073 for more information about this processor.
1074
1075 <p><hr /><a name="s390_002dx_002dlinux"></a>
1076
1077 <h3 class="heading"><a name="TOC54"></a>s390-*-linux*</h3>
1078
1079 <p>S/390 system running GNU/Linux for S/390.
1080
1081 <p><hr /><a name="s390x_002dx_002dlinux"></a>
1082
1083 <h3 class="heading"><a name="TOC55"></a>s390x-*-linux*</h3>
1084
1085 <p>zSeries system (64-bit) running GNU/Linux for zSeries.
1086
1087 <p><hr /><a name="s390x_002dibm_002dtpf"></a>
1088
1089 <h3 class="heading"><a name="TOC56"></a>s390x-ibm-tpf*</h3>
1090
1091 <p>zSeries system (64-bit) running TPF. This platform is
1092 supported as cross-compilation target only.
1093
1094 <p><hr /><!-- Please use Solaris 2 to refer to all release of Solaris, starting -->
1095 <!-- with 2.0 until 2.6, 7, 8, etc. Solaris 1 was a marketing name for -->
1096 <!-- SunOS 4 releases which we don't use to avoid confusion. Solaris -->
1097 <!-- alone is too unspecific and must be avoided. -->
1098 <a name="x_002dx_002dsolaris2"></a>
1099
1100 <h3 class="heading"><a name="TOC57"></a>*-*-solaris2*</h3>
1101
1102 <p>Support for Solaris 9 has been removed in GCC 5. Support for Solaris
1103 8 has been removed in GCC 4.8. Support for Solaris 7 has been removed
1104 in GCC 4.6.
1105
1106 <p>Sun does not ship a C compiler with Solaris 2 before Solaris 10, though
1107 you can download the Sun Studio compilers for free. In Solaris 10 and
1108 11, GCC 3.4.3 is available as <samp><span class="command">/usr/sfw/bin/gcc</span></samp>. Solaris 11
1109 also provides GCC 4.5.2, 4.7.3, and 4.8.2 as
1110 <samp><span class="command">/usr/gcc/4.5/bin/gcc</span></samp> or similar. Alternatively,
1111 you can install a pre-built GCC to bootstrap and install GCC. See the
1112 <a href="binaries.html">binaries page</a> for details.
1113
1114 <p>The Solaris 2 <samp><span class="command">/bin/sh</span></samp> will often fail to configure
1115 ‘<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
1116 recommend using the following initial sequence of commands
1117
1118 <pre class="smallexample"> % CONFIG_SHELL=/bin/ksh
1119 % export CONFIG_SHELL
1120 </pre>
1121 <p class="noindent">and proceed as described in <a href="configure.html">the configure instructions</a>.
1122 In addition we strongly recommend specifying an absolute path to invoke
1123 <samp><var>srcdir</var><span class="command">/configure</span></samp>.
1124
1125 <p>Solaris 10 comes with a number of optional OS packages. Some of these
1126 are needed to use GCC fully, namely <code>SUNWarc</code>,
1127 <code>SUNWbtool</code>, <code>SUNWesu</code>, <code>SUNWhea</code>, <code>SUNWlibm</code>,
1128 <code>SUNWsprot</code>, and <code>SUNWtoo</code>. If you did not install all
1129 optional packages when installing Solaris 10, you will need to verify that
1130 the packages that GCC needs are installed.
1131 To check whether an optional package is installed, use
1132 the <samp><span class="command">pkginfo</span></samp> command. To add an optional package, use the
1133 <samp><span class="command">pkgadd</span></samp> command. For further details, see the Solaris 10
1134 documentation.
1135
1136 <p>Starting with Solaris 11, the package management has changed, so you
1137 need to check for <code>system/header</code>, <code>system/linker</code>, and
1138 <code>developer/assembler</code> packages. Checking for and installing
1139 packages is done with the <samp><span class="command">pkg</span></samp> command now.
1140
1141 <p>Trying to use the linker and other tools in
1142 <samp><span class="file">/usr/ucb</span></samp> to install GCC has been observed to cause trouble.
1143 For example, the linker may hang indefinitely. The fix is to remove
1144 <samp><span class="file">/usr/ucb</span></samp> from your <samp><span class="env">PATH</span></samp>.
1145
1146 <p>The build process works more smoothly with the legacy Sun tools so, if you
1147 have <samp><span class="file">/usr/xpg4/bin</span></samp> in your <samp><span class="env">PATH</span></samp>, we recommend that you place
1148 <samp><span class="file">/usr/bin</span></samp> before <samp><span class="file">/usr/xpg4/bin</span></samp> for the duration of the build.
1149
1150 <p>We recommend the use of the Solaris assembler or the GNU assembler, in
1151 conjunction with the Solaris linker. The GNU <samp><span class="command">as</span></samp>
1152 versions included in Solaris 10, from GNU binutils 2.15 (in
1153 <samp><span class="file">/usr/sfw/bin/gas</span></samp>), and Solaris 11,
1154 from GNU binutils 2.19 or newer (also in <samp><span class="file">/usr/bin/gas</span></samp> and
1155 <samp><span class="file">/usr/gnu/bin/as</span></samp>), are known to work.
1156 Current versions of GNU binutils (2.26)
1157 are known to work as well, with the caveat mentioned in
1158 <a href="#ix86-x-solaris210">i?86-*-solaris2.10</a> . Note that your mileage may vary
1159 if you use a combination of the GNU tools and the Solaris tools: while the
1160 combination GNU <samp><span class="command">as</span></samp> + Sun <samp><span class="command">ld</span></samp> should reasonably work,
1161 the reverse combination Sun <samp><span class="command">as</span></samp> + GNU <samp><span class="command">ld</span></samp> may fail to
1162 build or cause memory corruption at runtime in some cases for C++ programs.
1163 <!-- FIXME: still? -->
1164 GNU <samp><span class="command">ld</span></samp> usually works as well, although the version included in
1165 Solaris 10 cannot be used due to several bugs. Again, the current
1166 version (2.26) is known to work, but generally lacks platform specific
1167 features, so better stay with Solaris <samp><span class="command">ld</span></samp>. To use the LTO linker
1168 plugin (<samp><span class="option">-fuse-linker-plugin</span></samp>) with GNU <samp><span class="command">ld</span></samp>, GNU
1169 binutils <em>must</em> be configured with <samp><span class="option">--enable-largefile</span></samp>.
1170
1171 <p>To enable symbol versioning in ‘<samp><span class="samp">libstdc++</span></samp>’ with the Solaris linker,
1172 you need to have any version of GNU <samp><span class="command">c++filt</span></samp>, which is part of
1173 GNU binutils. ‘<samp><span class="samp">libstdc++</span></samp>’ symbol versioning will be disabled if no
1174 appropriate version is found. Solaris <samp><span class="command">c++filt</span></samp> from the Solaris
1175 Studio compilers does <em>not</em> work.
1176
1177 <p>GNU <samp><span class="command">make</span></samp> version 3.81 or later is required to build libjava
1178 with the Solaris linker.
1179
1180 <p>Sun bug 4927647 sometimes causes random spurious testsuite failures
1181 related to missing diagnostic output. This bug doesn't affect GCC
1182 itself, rather it is a kernel bug triggered by the <samp><span class="command">expect</span></samp>
1183 program which is used only by the GCC testsuite driver. When the bug
1184 causes the <samp><span class="command">expect</span></samp> program to miss anticipated output, extra
1185 testsuite failures appear.
1186
1187 <p><hr /><a name="sparc_002dx_002dx"></a>
1188
1189 <h3 class="heading"><a name="TOC58"></a>sparc*-*-*</h3>
1190
1191 <p>This section contains general configuration information for all
1192 SPARC-based platforms. In addition to reading this section, please
1193 read all other sections that match your target.
1194
1195 <p>Newer versions of the GNU Multiple Precision Library (GMP), the MPFR
1196 library and the MPC library are known to be miscompiled by earlier
1197 versions of GCC on these platforms. We therefore recommend the use
1198 of the exact versions of these libraries listed as minimal versions
1199 in <a href="prerequisites.html">the prerequisites</a>.
1200
1201 <p><hr /><a name="sparc_002dsun_002dsolaris2"></a>
1202
1203 <h3 class="heading"><a name="TOC59"></a>sparc-sun-solaris2*</h3>
1204
1205 <p>When GCC is configured to use GNU binutils 2.14 or later, the binaries
1206 produced are smaller than the ones produced using Sun's native tools;
1207 this difference is quite significant for binaries containing debugging
1208 information.
1209
1210 <p>Starting with Solaris 7, the operating system is capable of executing
1211 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
1212 this; the <samp><span class="option">-m64</span></samp> option enables 64-bit code generation.
1213 However, if all you want is code tuned for the UltraSPARC CPU, you
1214 should try the <samp><span class="option">-mtune=ultrasparc</span></samp> option instead, which produces
1215 code that, unlike full 64-bit code, can still run on non-UltraSPARC
1216 machines.
1217
1218 <p>When configuring the GNU Multiple Precision Library (GMP), the MPFR
1219 library or the MPC library on a Solaris 7 or later system, the canonical
1220 target triplet must be specified as the <samp><span class="command">build</span></samp> parameter on the
1221 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
1222 not that of GMP or MPFR or MPC). For example on a Solaris 9 system:
1223
1224 <pre class="smallexample"> % ./configure --build=sparc-sun-solaris2.9 --prefix=xxx
1225 </pre>
1226 <p><hr /><a name="sparc_002dsun_002dsolaris210"></a>
1227
1228 <h3 class="heading"><a name="TOC60"></a>sparc-sun-solaris2.10</h3>
1229
1230 <p>There is a bug in older versions of the Sun assembler which breaks
1231 thread-local storage (TLS). A typical error message is
1232
1233 <pre class="smallexample"> ld: fatal: relocation error: R_SPARC_TLS_LE_HIX22: file /var/tmp//ccamPA1v.o:
1234 symbol <unknown>: bad symbol type SECT: symbol type must be TLS
1235 </pre>
1236 <p class="noindent">This bug is fixed in Sun patch 118683-03 or later.
1237
1238 <p><hr /><a name="sparc_002dx_002dlinux"></a>
1239
1240 <h3 class="heading"><a name="TOC61"></a>sparc-*-linux*</h3>
1241
1242 <p>GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
1243 or newer on this platform. All earlier binutils and glibc
1244 releases mishandled unaligned relocations on <code>sparc-*-*</code> targets.
1245
1246 <p><hr /><a name="sparc64_002dx_002dsolaris2"></a>
1247
1248 <h3 class="heading"><a name="TOC62"></a>sparc64-*-solaris2*</h3>
1249
1250 <p>When configuring the GNU Multiple Precision Library (GMP), the MPFR
1251 library or the MPC library, the canonical target triplet must be specified
1252 as the <samp><span class="command">build</span></samp> parameter on the configure line. For example
1253 on a Solaris 9 system:
1254
1255 <pre class="smallexample"> % ./configure --build=sparc64-sun-solaris2.9 --prefix=xxx
1256 </pre>
1257 <p><hr /><a name="sparcv9_002dx_002dsolaris2"></a>
1258
1259 <h3 class="heading"><a name="TOC63"></a>sparcv9-*-solaris2*</h3>
1260
1261 <p>This is a synonym for ‘<samp><span class="samp">sparc64-*-solaris2*</span></samp>’.
1262
1263 <p><hr /><a name="c6x_002dx_002dx"></a>
1264
1265 <h3 class="heading"><a name="TOC64"></a>c6x-*-*</h3>
1266
1267 <p>The C6X family of processors. This port requires binutils-2.22 or newer.
1268
1269 <p><hr /><a name="tilegx_002d_002a_002dlinux"></a>
1270
1271 <h3 class="heading"><a name="TOC65"></a>tilegx-*-linux*</h3>
1272
1273 <p>The TILE-Gx processor in little endian mode, running GNU/Linux. This
1274 port requires binutils-2.22 or newer.
1275
1276 <p><hr /><a name="tilegxbe_002d_002a_002dlinux"></a>
1277
1278 <h3 class="heading"><a name="TOC66"></a>tilegxbe-*-linux*</h3>
1279
1280 <p>The TILE-Gx processor in big endian mode, running GNU/Linux. This
1281 port requires binutils-2.23 or newer.
1282
1283 <p><hr /><a name="tilepro_002d_002a_002dlinux"></a>
1284
1285 <h3 class="heading"><a name="TOC67"></a>tilepro-*-linux*</h3>
1286
1287 <p>The TILEPro processor running GNU/Linux. This port requires
1288 binutils-2.22 or newer.
1289
1290 <p><hr /><a name="visium_002dx_002delf"></a>
1291
1292 <h3 class="heading"><a name="TOC68"></a>visium-*-elf</h3>
1293
1294 <p>CDS VISIUMcore processor.
1295 This configuration is intended for embedded systems.
1296
1297 <p><hr /><a name="x_002dx_002dvxworks"></a>
1298
1299 <h3 class="heading"><a name="TOC69"></a>*-*-vxworks*</h3>
1300
1301 <p>Support for VxWorks is in flux. At present GCC supports <em>only</em> the
1302 very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC.
1303 We welcome patches for other architectures supported by VxWorks 5.5.
1304 Support for VxWorks AE would also be welcome; we believe this is merely
1305 a matter of writing an appropriate “configlette” (see below). We are
1306 not interested in supporting older, a.out or COFF-based, versions of
1307 VxWorks in GCC 3.
1308
1309 <p>VxWorks comes with an older version of GCC installed in
1310 <samp><var>$WIND_BASE</var><span class="file">/host</span></samp>; we recommend you do not overwrite it.
1311 Choose an installation <var>prefix</var> entirely outside <var>$WIND_BASE</var>.
1312 Before running <samp><span class="command">configure</span></samp>, create the directories <samp><var>prefix</var></samp>
1313 and <samp><var>prefix</var><span class="file">/bin</span></samp>. Link or copy the appropriate assembler,
1314 linker, etc. into <samp><var>prefix</var><span class="file">/bin</span></samp>, and set your <var>PATH</var> to
1315 include that directory while running both <samp><span class="command">configure</span></samp> and
1316 <samp><span class="command">make</span></samp>.
1317
1318 <p>You must give <samp><span class="command">configure</span></samp> the
1319 <samp><span class="option">--with-headers=</span><var>$WIND_BASE</var><span class="option">/target/h</span></samp> switch so that it can
1320 find the VxWorks system headers. Since VxWorks is a cross compilation
1321 target only, you must also specify <samp><span class="option">--target=</span><var>target</var></samp>.
1322 <samp><span class="command">configure</span></samp> will attempt to create the directory
1323 <samp><var>prefix</var><span class="file">/</span><var>target</var><span class="file">/sys-include</span></samp> and copy files into it;
1324 make sure the user running <samp><span class="command">configure</span></samp> has sufficient privilege
1325 to do so.
1326
1327 <p>GCC's exception handling runtime requires a special “configlette”
1328 module, <samp><span class="file">contrib/gthr_supp_vxw_5x.c</span></samp>. Follow the instructions in
1329 that file to add the module to your kernel build. (Future versions of
1330 VxWorks will incorporate this module.)
1331
1332 <p><hr /><a name="x86_002d64_002dx_002dx"></a>
1333
1334 <h3 class="heading"><a name="TOC70"></a>x86_64-*-*, amd64-*-*</h3>
1335
1336 <p>GCC supports the x86-64 architecture implemented by the AMD64 processor
1337 (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD.
1338 On GNU/Linux the default is a bi-arch compiler which is able to generate
1339 both 64-bit x86-64 and 32-bit x86 code (via the <samp><span class="option">-m32</span></samp> switch).
1340
1341 <p><hr /><a name="x86_002d64_002dx_002dsolaris210"></a>
1342
1343 <h3 class="heading"><a name="TOC71"></a>x86_64-*-solaris2.1[0-9]*</h3>
1344
1345 <p>GCC also supports the x86-64 architecture implemented by the AMD64
1346 processor (‘<samp><span class="samp">amd64-*-*</span></samp>’ is an alias for ‘<samp><span class="samp">x86_64-*-*</span></samp>’) on
1347 Solaris 10 or later. Unlike other systems, without special options a
1348 bi-arch compiler is built which generates 32-bit code by default, but
1349 can generate 64-bit x86-64 code with the <samp><span class="option">-m64</span></samp> switch. Since
1350 GCC 4.7, there is also a configuration that defaults to 64-bit code, but
1351 can generate 32-bit code with <samp><span class="option">-m32</span></samp>. To configure and build
1352 this way, you have to provide all support libraries like <samp><span class="file">libgmp</span></samp>
1353 as 64-bit code, configure with <samp><span class="option">--target=x86_64-pc-solaris2.1x</span></samp>
1354 and ‘<samp><span class="samp">CC=gcc -m64</span></samp>’.
1355
1356 <p><hr /><a name="xtensa_002dx_002delf"></a>
1357
1358 <h3 class="heading"><a name="TOC72"></a>xtensa*-*-elf</h3>
1359
1360 <p>This target is intended for embedded Xtensa systems using the
1361 ‘<samp><span class="samp">newlib</span></samp>’ C library. It uses ELF but does not support shared
1362 objects. Designed-defined instructions specified via the
1363 Tensilica Instruction Extension (TIE) language are only supported
1364 through inline assembly.
1365
1366 <p>The Xtensa configuration information must be specified prior to
1367 building GCC. The <samp><span class="file">include/xtensa-config.h</span></samp> header
1368 file contains the configuration information. If you created your
1369 own Xtensa configuration with the Xtensa Processor Generator, the
1370 downloaded files include a customized copy of this header file,
1371 which you can use to replace the default header file.
1372
1373 <p><hr /><a name="xtensa_002dx_002dlinux"></a>
1374
1375 <h3 class="heading"><a name="TOC73"></a>xtensa*-*-linux*</h3>
1376
1377 <p>This target is for Xtensa systems running GNU/Linux. It supports ELF
1378 shared objects and the GNU C library (glibc). It also generates
1379 position-independent code (PIC) regardless of whether the
1380 <samp><span class="option">-fpic</span></samp> or <samp><span class="option">-fPIC</span></samp> options are used. In other
1381 respects, this target is the same as the
1382 <a href="#xtensa*-*-elf">‘<samp><span class="samp">xtensa*-*-elf</span></samp>’</a> target.
1383
1384 <p><hr /><a name="windows"></a>
1385
1386 <h3 class="heading"><a name="TOC74"></a>Microsoft Windows</h3>
1387
1388 <h4 class="subheading"><a name="TOC75"></a>Intel 16-bit versions</h4>
1389
1390 <p>The 16-bit versions of Microsoft Windows, such as Windows 3.1, are not
1391 supported.
1392
1393 <p>However, the 32-bit port has limited support for Microsoft
1394 Windows 3.11 in the Win32s environment, as a target only. See below.
1395
1396 <h4 class="subheading"><a name="TOC76"></a>Intel 32-bit versions</h4>
1397
1398 <p>The 32-bit versions of Windows, including Windows 95, Windows NT, Windows
1399 XP, and Windows Vista, are supported by several different target
1400 platforms. These targets differ in which Windows subsystem they target
1401 and which C libraries are used.
1402
1403 <ul>
1404 <li>Cygwin <a href="#x-x-cygwin">*-*-cygwin</a>: Cygwin provides a user-space
1405 Linux API emulation layer in the Win32 subsystem.
1406 <li>Interix <a href="#x-x-interix">*-*-interix</a>: The Interix subsystem
1407 provides native support for POSIX.
1408 <li>MinGW <a href="#x-x-mingw32">*-*-mingw32</a>: MinGW is a native GCC port for
1409 the Win32 subsystem that provides a subset of POSIX.
1410 <li>MKS i386-pc-mks: NuTCracker from MKS. See
1411 <a href="http://www.mkssoftware.com/">http://www.mkssoftware.com/</a> for more information.
1412 </ul>
1413
1414 <h4 class="subheading"><a name="TOC77"></a>Intel 64-bit versions</h4>
1415
1416 <p>GCC contains support for x86-64 using the mingw-w64
1417 runtime library, available from <a href="http://mingw-w64.sourceforge.net/">http://mingw-w64.sourceforge.net/</a>.
1418 This library should be used with the target triple x86_64-pc-mingw32.
1419
1420 <p>Presently Windows for Itanium is not supported.
1421
1422 <h4 class="subheading"><a name="TOC78"></a>Windows CE</h4>
1423
1424 <p>Windows CE is supported as a target only on Hitachi
1425 SuperH (sh-wince-pe), and MIPS (mips-wince-pe).
1426
1427 <h4 class="subheading"><a name="TOC79"></a>Other Windows Platforms</h4>
1428
1429 <p>GCC no longer supports Windows NT on the Alpha or PowerPC.
1430
1431 <p>GCC no longer supports the Windows POSIX subsystem. However, it does
1432 support the Interix subsystem. See above.
1433
1434 <p>Old target names including *-*-winnt and *-*-windowsnt are no longer used.
1435
1436 <p>PW32 (i386-pc-pw32) support was never completed, and the project seems to
1437 be inactive. See <a href="http://pw32.sourceforge.net/">http://pw32.sourceforge.net/</a> for more information.
1438
1439 <p>UWIN support has been removed due to a lack of maintenance.
1440
1441 <p><hr /><a name="x_002dx_002dcygwin"></a>
1442
1443 <h3 class="heading"><a name="TOC80"></a>*-*-cygwin</h3>
1444
1445 <p>Ports of GCC are included with the
1446 <a href="http://www.cygwin.com/">Cygwin environment</a>.
1447
1448 <p>GCC will build under Cygwin without modification; it does not build
1449 with Microsoft's C++ compiler and there are no plans to make it do so.
1450
1451 <p>The Cygwin native compiler can be configured to target any 32-bit x86
1452 cpu architecture desired; the default is i686-pc-cygwin. It should be
1453 used with as up-to-date a version of binutils as possible; use either
1454 the latest official GNU binutils release in the Cygwin distribution,
1455 or version 2.20 or above if building your own.
1456
1457 <p><hr /><a name="x_002dx_002dinterix"></a>
1458
1459 <h3 class="heading"><a name="TOC81"></a>*-*-interix</h3>
1460
1461 <p>The Interix target is used by OpenNT, Interix, Services For UNIX (SFU),
1462 and Subsystem for UNIX-based Applications (SUA). Applications compiled
1463 with this target run in the Interix subsystem, which is separate from
1464 the Win32 subsystem. This target was last known to work in GCC 3.3.
1465
1466 <p><hr /><a name="x_002dx_002dmingw32"></a>
1467
1468 <h3 class="heading"><a name="TOC82"></a>*-*-mingw32</h3>
1469
1470 <p>GCC will build with and support only MinGW runtime 3.12 and later.
1471 Earlier versions of headers are incompatible with the new default semantics
1472 of <code>extern inline</code> in <code>-std=c99</code> and <code>-std=gnu99</code> modes.
1473
1474 <p><hr /><a name="older"></a>
1475
1476 <h3 class="heading"><a name="TOC83"></a>Older systems</h3>
1477
1478 <p>GCC contains support files for many older (1980s and early
1479 1990s) Unix variants. For the most part, support for these systems
1480 has not been deliberately removed, but it has not been maintained for
1481 several years and may suffer from bitrot.
1482
1483 <p>Starting with GCC 3.1, each release has a list of “obsoleted” systems.
1484 Support for these systems is still present in that release, but
1485 <samp><span class="command">configure</span></samp> will fail unless the <samp><span class="option">--enable-obsolete</span></samp>
1486 option is given. Unless a maintainer steps forward, support for these
1487 systems will be removed from the next release of GCC.
1488
1489 <p>Support for old systems as hosts for GCC can cause problems if the
1490 workarounds for compiler, library and operating system bugs affect the
1491 cleanliness or maintainability of the rest of GCC. In some cases, to
1492 bring GCC up on such a system, if still possible with current GCC, may
1493 require first installing an old version of GCC which did work on that
1494 system, and using it to compile a more recent GCC, to avoid bugs in the
1495 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
1496 <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
1497 <samp><span class="command">fixincludes</span></samp>, but bugs or deficiencies in libraries and the
1498 operating system may still cause problems.
1499
1500 <p>Support for older systems as targets for cross-compilation is less
1501 problematic than support for them as hosts for GCC; if an enthusiast
1502 wishes to make such a target work again (including resurrecting any of
1503 the targets that never worked with GCC 2, starting from the last
1504 version before they were removed), patches
1505 <a href="../contribute.html">following the usual requirements</a> would be
1506 likely to be accepted, since they should not affect the support for more
1507 modern targets.
1508
1509 <p>For some systems, old versions of GNU binutils may also be useful,
1510 and are available from <samp><span class="file">pub/binutils/old-releases</span></samp> on
1511 <a href="http://sourceware.org/mirrors.html">sourceware.org mirror sites</a>.
1512
1513 <p>Some of the information on specific systems above relates to
1514 such older systems, but much of the information
1515 about GCC on such systems (which may no longer be applicable to
1516 current GCC) is to be found in the GCC texinfo manual.
1517
1518 <p><hr /><a name="elf"></a>
1519
1520 <h3 class="heading"><a name="TOC84"></a>all ELF targets (SVR4, Solaris 2, etc.)</h3>
1521
1522 <p>C++ support is significantly better on ELF targets if you use the
1523 <a href="./configure.html#with-gnu-ld">GNU linker</a>; duplicate copies of
1524 inlines, vtables and template instantiations will be discarded
1525 automatically.
1526
1527 <p><hr />
1528 <p><a href="./index.html">Return to the GCC Installation page</a>
1529
1530 <!-- ***Old documentation****************************************************** -->
1531 <!-- ***GFDL******************************************************************** -->
1532 <!-- *************************************************************************** -->
1533 <!-- Part 6 The End of the Document -->
1534 </body></html>
1535
1536