specific.html revision 1.18 1 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
2 <html>
3 <!-- Copyright (C) 1988-2024 Free Software Foundation, Inc.
4
5 Permission is granted to copy, distribute and/or modify this document
6 under the terms of the GNU Free Documentation License, Version 1.3 or
7 any later version published by the Free Software Foundation; with no
8 Invariant Sections, the Front-Cover texts being (a) (see below), and
9 with the Back-Cover Texts being (b) (see below). A copy of the
10 license is included in the section entitled "GNU
11 Free Documentation License".
12
13 (a) The FSF's Front-Cover Text is:
14
15 A GNU Manual
16
17 (b) The FSF's Back-Cover Text is:
18
19 You have freedom to copy and modify this GNU Manual, like GNU
20 software. Copies published by the Free Software Foundation raise
21 funds for GNU development. -->
22 <!-- Created by GNU Texinfo 6.5, http://www.gnu.org/software/texinfo/ -->
23 <head>
24 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
25 <title>Host/Target specific installation notes for GCC</title>
26
27 <meta name="description" content="Host/Target specific installation notes for GCC">
28 <meta name="keywords" content="Host/Target specific installation notes for GCC">
29 <meta name="resource-type" content="document">
30 <meta name="distribution" content="global">
31 <meta name="Generator" content="makeinfo">
32 <style type="text/css">
33 <!--
34 a.summary-letter {text-decoration: none}
35 blockquote.indentedblock {margin-right: 0em}
36 blockquote.smallindentedblock {margin-right: 0em; font-size: smaller}
37 blockquote.smallquotation {font-size: smaller}
38 div.display {margin-left: 3.2em}
39 div.example {margin-left: 3.2em}
40 div.lisp {margin-left: 3.2em}
41 div.smalldisplay {margin-left: 3.2em}
42 div.smallexample {margin-left: 3.2em}
43 div.smalllisp {margin-left: 3.2em}
44 kbd {font-style: oblique}
45 pre.display {font-family: inherit}
46 pre.format {font-family: inherit}
47 pre.menu-comment {font-family: serif}
48 pre.menu-preformatted {font-family: serif}
49 pre.smalldisplay {font-family: inherit; font-size: smaller}
50 pre.smallexample {font-size: smaller}
51 pre.smallformat {font-family: inherit; font-size: smaller}
52 pre.smalllisp {font-size: smaller}
53 span.nolinebreak {white-space: nowrap}
54 span.roman {font-family: initial; font-weight: normal}
55 span.sansserif {font-family: sans-serif; font-weight: normal}
56 ul.no-bullet {list-style: none}
57 -->
58 </style>
59
60
61 </head>
62
63 <body lang="en">
64 <h1 class="settitle" align="center">Host/Target specific installation notes for GCC</h1>
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92 <a name="index-Specific"></a>
93 <a name="index-Specific-installation-notes"></a>
94 <a name="index-Target-specific-installation"></a>
95 <a name="index-Host-specific-installation"></a>
96 <a name="index-Target-specific-installation-notes"></a>
97
98 <p>Please read this document carefully <em>before</em> installing the
99 GNU Compiler Collection on your machine.
100 </p>
101 <p>Note that this list of install notes is <em>not</em> a list of supported
102 hosts or targets. Not all supported hosts and targets are listed
103 here, only the ones that require host-specific or target-specific
104 information have to.
105 </p>
106 <ul>
107 <li> <a href="#aarch64-x-x">aarch64*-*-*</a>
108 </li><li> <a href="#amdgcn-x-amdhsa">amdgcn-*-amdhsa</a>
109 </li><li> <a href="#amd64-x-solaris2">amd64-*-solaris2*</a>
110 </li><li> <a href="#arc-x-elf32">arc-*-elf32</a>
111 </li><li> <a href="#arc-linux-uclibc">arc-linux-uclibc</a>
112 </li><li> <a href="#arm-x-eabi">arm-*-eabi</a>
113 </li><li> <a href="#avr">avr</a>
114 </li><li> <a href="#bfin">Blackfin</a>
115 </li><li> <a href="#cris">cris</a>
116 </li><li> <a href="#dos">DOS</a>
117 </li><li> <a href="#epiphany-x-elf">epiphany-*-elf</a>
118 </li><li> <a href="#ft32-x-elf">ft32-*-elf</a>
119 </li><li> <a href="#x-x-freebsd">*-*-freebsd*</a>
120 </li><li> <a href="#h8300-hms">h8300-hms</a>
121 </li><li> <a href="#hppa-hp-hpux">hppa*-hp-hpux*</a>
122 </li><li> <a href="#hppa-hp-hpux11">hppa*-hp-hpux11</a>
123 </li><li> <a href="#x-x-linux-gnu">*-*-linux-gnu</a>
124 </li><li> <a href="#ix86-x-linux">i?86-*-linux*</a>
125 </li><li> <a href="#ix86-x-solaris2">i?86-*-solaris2*</a>
126 </li><li> <a href="#ia64-x-linux">ia64-*-linux</a>
127 </li><li> <a href="#ia64-x-hpux">ia64-*-hpux*</a>
128 </li><li> <a href="#x-ibm-aix">*-ibm-aix*</a>
129 </li><li> <a href="#iq2000-x-elf">iq2000-*-elf</a>
130 </li><li> <a href="#loongarch">loongarch</a>
131 </li><li> <a href="#lm32-x-elf">lm32-*-elf</a>
132 </li><li> <a href="#lm32-x-uclinux">lm32-*-uclinux</a>
133 </li><li> <a href="#m32c-x-elf">m32c-*-elf</a>
134 </li><li> <a href="#m32r-x-elf">m32r-*-elf</a>
135 </li><li> <a href="#m68k-x-x">m68k-*-*</a>
136 </li><li> <a href="#m68k-x-uclinux">m68k-*-uclinux</a>
137 </li><li> <a href="#microblaze-x-elf">microblaze-*-elf</a>
138 </li><li> <a href="#mips-x-x">mips-*-*</a>
139 </li><li> <a href="#moxie-x-elf">moxie-*-elf</a>
140 </li><li> <a href="#msp430-x-elf">msp430-*-elf</a>
141 </li><li> <a href="#nds32le-x-elf">nds32le-*-elf</a>
142 </li><li> <a href="#nds32be-x-elf">nds32be-*-elf</a>
143 </li><li> <a href="#nvptx-x-none">nvptx-*-none</a>
144 </li><li> <a href="#or1k-x-elf">or1k-*-elf</a>
145 </li><li> <a href="#or1k-x-linux">or1k-*-linux</a>
146 </li><li> <a href="#powerpc-x-x">powerpc*-*-*</a>
147 </li><li> <a href="#powerpc-x-darwin">powerpc-*-darwin*</a>
148 </li><li> <a href="#powerpc-x-elf">powerpc-*-elf</a>
149 </li><li> <a href="#powerpc-x-linux-gnu">powerpc*-*-linux-gnu*</a>
150 </li><li> <a href="#powerpc-x-netbsd">powerpc-*-netbsd*</a>
151 </li><li> <a href="#powerpc-x-eabisim">powerpc-*-eabisim</a>
152 </li><li> <a href="#powerpc-x-eabi">powerpc-*-eabi</a>
153 </li><li> <a href="#powerpcle-x-elf">powerpcle-*-elf</a>
154 </li><li> <a href="#powerpcle-x-eabisim">powerpcle-*-eabisim</a>
155 </li><li> <a href="#powerpcle-x-eabi">powerpcle-*-eabi</a>
156 </li><li> <a href="#riscv32-x-elf">riscv32-*-elf</a>
157 </li><li> <a href="#riscv32-x-linux">riscv32-*-linux</a>
158 </li><li> <a href="#riscv64-x-elf">riscv64-*-elf</a>
159 </li><li> <a href="#riscv64-x-linux">riscv64-*-linux</a>
160 </li><li> <a href="#rl78-x-elf">rl78-*-elf</a>
161 </li><li> <a href="#rx-x-elf">rx-*-elf</a>
162 </li><li> <a href="#s390-x-linux">s390-*-linux*</a>
163 </li><li> <a href="#s390x-x-linux">s390x-*-linux*</a>
164 </li><li> <a href="#s390x-ibm-tpf">s390x-ibm-tpf*</a>
165 </li><li> <a href="#x-x-solaris2">*-*-solaris2*</a>
166 </li><li> <a href="#sparc-x-x">sparc*-*-*</a>
167 </li><li> <a href="#sparc-sun-solaris2">sparc-sun-solaris2*</a>
168 </li><li> <a href="#sparc-x-linux">sparc-*-linux*</a>
169 </li><li> <a href="#sparc64-x-solaris2">sparc64-*-solaris2*</a>
170 </li><li> <a href="#sparcv9-x-solaris2">sparcv9-*-solaris2*</a>
171 </li><li> <a href="#c6x-x-x">c6x-*-*</a>
172 </li><li> <a href="#visium-x-elf">visium-*-elf</a>
173 </li><li> <a href="#x-x-vxworks">*-*-vxworks*</a>
174 </li><li> <a href="#x86-64-x-x">x86_64-*-*, amd64-*-*</a>
175 </li><li> <a href="#x86-64-x-solaris2">x86_64-*-solaris2*</a>
176 </li><li> <a href="#xtensa-x-elf">xtensa*-*-elf</a>
177 </li><li> <a href="#xtensa-x-linux">xtensa*-*-linux*</a>
178 </li><li> <a href="#windows">Microsoft Windows</a>
179 </li><li> <a href="#x-x-cygwin">*-*-cygwin</a>
180 </li><li> <a href="#x-x-mingw32">*-*-mingw32</a>
181 </li><li> <a href="#os2">OS/2</a>
182 </li><li> <a href="#older">Older systems</a>
183 </li></ul>
184
185 <ul>
186 <li> <a href="#elf">all ELF targets</a> (SVR4, Solaris, etc.)
187 </li></ul>
188
189
190 <!-- -------- host/target specific issues start here ---------------- -->
191 <hr />
192 <a name="aarch64-x-x"></a><a name="aarch64*-*-*"></a>
193 <h3 class="heading">aarch64*-*-*</h3>
194 <p>Binutils pre 2.24 does not have support for selecting <samp>-mabi</samp> and
195 does not support ILP32. If it is used to build GCC 4.9 or later, GCC will
196 not support option <samp>-mabi=ilp32</samp>.
197 </p>
198 <p>To enable a workaround for the Cortex-A53 erratum number 835769 by default
199 (for all CPUs regardless of -mcpu option given) at configure time use the
200 <samp>--enable-fix-cortex-a53-835769</samp> option. This will enable the fix by
201 default and can be explicitly disabled during compilation by passing the
202 <samp>-mno-fix-cortex-a53-835769</samp> option. Conversely,
203 <samp>--disable-fix-cortex-a53-835769</samp> will disable the workaround by
204 default. The workaround is disabled by default if neither of
205 <samp>--enable-fix-cortex-a53-835769</samp> or
206 <samp>--disable-fix-cortex-a53-835769</samp> is given at configure time.
207 </p>
208 <p>To enable a workaround for the Cortex-A53 erratum number 843419 by default
209 (for all CPUs regardless of -mcpu option given) at configure time use the
210 <samp>--enable-fix-cortex-a53-843419</samp> option. This workaround is applied at
211 link time. Enabling the workaround will cause GCC to pass the relevant option
212 to the linker. It can be explicitly disabled during compilation by passing the
213 <samp>-mno-fix-cortex-a53-843419</samp> option. Conversely,
214 <samp>--disable-fix-cortex-a53-843419</samp> will disable the workaround by default.
215 The workaround is disabled by default if neither of
216 <samp>--enable-fix-cortex-a53-843419</samp> or
217 <samp>--disable-fix-cortex-a53-843419</samp> is given at configure time.
218 </p>
219 <p>To enable Branch Target Identification Mechanism and Return Address Signing by
220 default at configure time use the <samp>--enable-standard-branch-protection</samp>
221 option. This is equivalent to having <samp>-mbranch-protection=standard</samp>
222 during compilation. This can be explicitly disabled during compilation by
223 passing the <samp>-mbranch-protection=none</samp> option which turns off all
224 types of branch protections. Conversely,
225 <samp>--disable-standard-branch-protection</samp> will disable both the
226 protections by default. This mechanism is turned off by default if neither
227 of the options are given at configure time.
228 </p>
229 <hr />
230 <a name="amd64-x-solaris2"></a><a name="amd64-*-solaris2*"></a>
231 <h3 class="heading">amd64-*-solaris2*</h3>
232 <p>This is a synonym for ‘<samp>x86_64-*-solaris2*</samp>’.
233 </p>
234 <hr />
235 <a name="amdgcn-x-amdhsa"></a><a name="amdgcn-*-amdhsa"></a>
236 <h3 class="heading">amdgcn-*-amdhsa</h3>
237 <p>AMD GCN GPU target.
238 </p>
239 <p>Instead of GNU Binutils, you will need to install LLVM 15, or later, and copy
240 <samp>bin/llvm-mc</samp> to <samp>amdgcn-amdhsa/bin/as</samp>,
241 <samp>bin/lld</samp> to <samp>amdgcn-amdhsa/bin/ld</samp>,
242 <samp>bin/llvm-nm</samp> to <samp>amdgcn-amdhsa/bin/nm</samp>, and
243 <samp>bin/llvm-ar</samp> to both <samp>bin/amdgcn-amdhsa-ar</samp> and
244 <samp>bin/amdgcn-amdhsa-ranlib</samp>. Note that LLVM 13.0.1 or LLVM 14 can be used
245 by specifying a <code>--with-multilib-list=</code> that does not list <code>gfx1100</code>
246 and <code>gfx1103</code>.
247 </p>
248 <p>Use Newlib (4.3.0 or newer; 4.4.0 contains some improvements and git commit
249 7dd4eb1db (2025-03-25, post-4.4.0) fixes device console output for GFX10 and
250 GFX11 devices).
251 </p>
252 <p>To run the binaries, install the HSA Runtime from the
253 <a href="https://rocm.docs.amd.com/">ROCm Platform</a>, and use
254 <samp>libexec/gcc/amdhsa-amdhsa/<var>version</var>/gcn-run</samp> to launch them
255 on the GPU.
256 </p>
257 <p>To enable support for GCN3 Fiji devices (gfx803), GCC has to be configured with
258 <samp>--with-arch=<code>fiji</code></samp> or
259 <samp>--with-multilib-list=<code>fiji</code>,...</samp>. Note that support for Fiji
260 devices has been removed in ROCm 4.0 and support in LLVM was deprecated and has
261 been removed in LLVM 18.
262 </p>
263 <hr />
264 <a name="arc-x-elf32"></a><a name="arc-*-elf32"></a>
265 <h3 class="heading">arc-*-elf32</h3>
266
267 <p>Use ‘<samp>configure --target=arc-elf32 --with-cpu=<var>cpu</var> --enable-languages="c,c++"</samp>’
268 to configure GCC, with <var>cpu</var> being one of ‘<samp>arc600</samp>’, ‘<samp>arc601</samp>’,
269 or ‘<samp>arc700</samp>’.
270 </p>
271 <hr />
272 <a name="arc-linux-uclibc"></a><a name="arc-linux-uclibc-1"></a>
273 <h3 class="heading">arc-linux-uclibc</h3>
274
275 <p>Use ‘<samp>configure --target=arc-linux-uclibc --with-cpu=arc700 --enable-languages="c,c++"</samp>’ to configure GCC.
276 </p>
277 <hr />
278 <a name="arm-x-eabi"></a><a name="arm-*-eabi"></a>
279 <h3 class="heading">arm-*-eabi</h3>
280 <p>ARM-family processors.
281 </p>
282 <p>Building the Ada frontend commonly fails (an infinite loop executing
283 <code>xsinfo</code>) if the host compiler is GNAT 4.8. Host compilers built from the
284 GNAT 4.6, 4.9 or 5 release branches are known to succeed.
285 </p>
286 <hr />
287 <a name="avr"></a><a name="avr-1"></a>
288 <h3 class="heading">avr</h3>
289 <p>ATMEL AVR-family micro controllers. These are used in embedded
290 applications. There are no standard Unix configurations.
291 See “AVR Options” in the main manual
292 for the list of supported MCU types.
293 </p>
294 <p>Use ‘<samp>configure --target=avr --enable-languages="c"</samp>’ to configure GCC.
295 </p>
296 <p>Further installation notes and other useful information about AVR tools
297 can also be obtained from:
298 </p>
299 <ul>
300 <li> <a href="http://www.nongnu.org/avr/">http://www.nongnu.org/avr/</a>
301 </li><li> <a href="http://www.amelek.gda.pl/avr/">http://www.amelek.gda.pl/avr/</a>
302 </li></ul>
303
304 <p>The following error:
305 </p><div class="smallexample">
306 <pre class="smallexample">Error: register required
307 </pre></div>
308
309 <p>indicates that you should upgrade to a newer version of the binutils.
310 </p>
311 <hr />
312 <a name="bfin"></a><a name="Blackfin"></a>
313 <h3 class="heading">Blackfin</h3>
314 <p>The Blackfin processor, an Analog Devices DSP.
315 See “Blackfin Options” in the main manual
316 </p>
317 <p>More information, and a version of binutils with support for this processor,
318 are available at <a href="https://sourceforge.net/projects/adi-toolchain/">https://sourceforge.net/projects/adi-toolchain/</a>.
319 </p>
320 <hr />
321 <a name="cris"></a><a name="CRIS"></a>
322 <h3 class="heading">CRIS</h3>
323 <p>CRIS is a CPU architecture in Axis Communications systems-on-a-chip, for
324 example the ETRAX series. These are used in embedded applications.
325 </p>
326 <p>See “CRIS Options” in the main manual
327 for a list of CRIS-specific options.
328 </p>
329 <p>Use ‘<samp>configure --target=cris-elf</samp>’ to configure GCC for building
330 a cross-compiler for CRIS.
331 <hr />
332 <a name="dos"></a></p><a name="DOS"></a>
333 <h3 class="heading">DOS</h3>
334 <p>Please have a look at the <a href="binaries.html">binaries page</a>.
335 </p>
336 <p>You cannot install GCC by itself on MSDOS; it will not compile under
337 any MSDOS compiler except itself. You need to get the complete
338 compilation package DJGPP, which includes binaries as well as sources,
339 and includes all the necessary compilation tools and libraries.
340 </p>
341 <hr />
342 <a name="epiphany-x-elf"></a><a name="epiphany-*-elf"></a>
343 <h3 class="heading">epiphany-*-elf</h3>
344 <p>Adapteva Epiphany.
345 This configuration is intended for embedded systems.
346 </p>
347 <hr />
348 <a name="x-x-freebsd"></a><a name="g_t*-*-freebsd*"></a>
349 <h3 class="heading">*-*-freebsd*</h3>
350 <p>We support FreeBSD using the ELF file format with DWARF 2 debugging
351 for all CPU architectures. There are
352 no known issues with mixing object files and libraries with different
353 debugging formats.
354 </p>
355 <p>We recommend bootstrapping against the latest GNU binutils or the
356 version found in the <samp>devel/binutils</samp> port. This also has been
357 known to enable additional features and improve overall testsuite
358 results.
359 </p>
360 <p>Ada and D (or rather their respective libraries) are broken on
361 FreeBSD/i386. This also affects building 32-bit libraries on
362 FreeBSD/amd64, so configure with <samp>--disable-multilib</samp>
363 there in case you are building one of these front ends.
364 </p>
365 <p>Go (or rather libgo) is generally broken on FreeBSD.
366 </p>
367 <hr />
368 <a name="ft32-x-elf"></a><a name="ft32-*-elf"></a>
369 <h3 class="heading">ft32-*-elf</h3>
370 <p>The FT32 processor.
371 This configuration is intended for embedded systems.
372 </p>
373 <hr />
374 <a name="h8300-hms"></a><a name="h8300-hms-1"></a>
375 <h3 class="heading">h8300-hms</h3>
376 <p>Renesas H8/300 series of processors.
377 </p>
378 <p>Please have a look at the <a href="binaries.html">binaries page</a>.
379 </p>
380 <p>The calling convention and structure layout has changed in release 2.6.
381 All code must be recompiled. The calling convention now passes the
382 first three arguments in function calls in registers. Structures are no
383 longer a multiple of 2 bytes.
384 </p>
385 <hr />
386 <a name="hppa-hp-hpux"></a><a name="hppa*-hp-hpux*"></a>
387 <h3 class="heading">hppa*-hp-hpux*</h3>
388 <p>We require using gas on all hppa platforms. Version 2.19 or
389 later is recommended.
390 </p>
391 <p>It may be helpful to configure GCC with the
392 <a href="./configure.html#with-gnu-as"><samp>--with-gnu-as</samp></a> and
393 <samp>--with-as=…</samp> options to ensure that GCC can find GAS.
394 </p>
395 <p>There are two default scheduling models for instructions. These are
396 PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
397 architecture specified for the target machine when configuring.
398 PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
399 the target is a ‘<samp>hppa1*</samp>’ machine.
400 </p>
401 <p>The PROCESSOR_8000 model is not well suited to older processors. Thus,
402 it is important to completely specify the machine architecture when
403 configuring if you want a model other than PROCESSOR_8000. The macro
404 TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
405 default scheduling model is desired.
406 </p>
407 <p>As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10
408 through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later.
409 This namespace change might cause problems when bootstrapping with
410 an earlier version of GCC or the HP compiler as essentially the same
411 namespace is required for an entire build. This problem can be avoided
412 in a number of ways. With HP cc, <code>UNIX_STD</code> can be set to ‘<samp>95</samp>’
413 or ‘<samp>98</samp>’. Another way is to add an appropriate set of predefines
414 to <code>CC</code>. The description for the <samp>munix=</samp> option contains
415 a list of the predefines used with each standard.
416 </p>
417 <p>More specific information to ‘<samp>hppa*-hp-hpux*</samp>’ targets follows.
418 </p>
419 <hr />
420 <a name="hppa-hp-hpux11"></a><a name="hppa*-hp-hpux11"></a>
421 <h3 class="heading">hppa*-hp-hpux11</h3>
422 <p>Refer to <a href="binaries.html">binaries</a> for information about obtaining
423 precompiled GCC binaries for HP-UX. Precompiled binaries must be obtained
424 to build the Ada language as it cannot be bootstrapped using C. Ada is
425 only available for the 32-bit PA-RISC runtime.
426 </p>
427 <p>Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The
428 bundled compiler supports only traditional C; you will need either HP’s
429 unbundled compiler, or a binary distribution of GCC.
430 </p>
431 <p>It is possible to build GCC 3.3 starting with the bundled HP compiler,
432 but the process requires several steps. GCC 3.3 can then be used to
433 build later versions.
434 </p>
435 <p>There are several possible approaches to building the distribution.
436 Binutils can be built first using the HP tools. Then, the GCC
437 distribution can be built. The second approach is to build GCC
438 first using the HP tools, then build binutils, then rebuild GCC.
439 There have been problems with various binary distributions, so it
440 is best not to start from a binary distribution.
441 </p>
442 <p>On 64-bit capable systems, there are two distinct targets. Different
443 installation prefixes must be used if both are to be installed on
444 the same system. The ‘<samp>hppa[1-2]*-hp-hpux11*</samp>’ target generates code
445 for the 32-bit PA-RISC runtime architecture and uses the HP linker.
446 The ‘<samp>hppa64-hp-hpux11*</samp>’ target generates 64-bit code for the
447 PA-RISC 2.0 architecture.
448 </p>
449 <p>The script config.guess now selects the target type based on the compiler
450 detected during configuration. You must define <code>PATH</code> or <code>CC</code> so
451 that configure finds an appropriate compiler for the initial bootstrap.
452 When <code>CC</code> is used, the definition should contain the options that are
453 needed whenever <code>CC</code> is used.
454 </p>
455 <p>Specifically, options that determine the runtime architecture must be
456 in <code>CC</code> to correctly select the target for the build. It is also
457 convenient to place many other compiler options in <code>CC</code>. For example,
458 <code>CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"</code>
459 can be used to bootstrap the GCC 3.3 branch with the HP compiler in
460 64-bit K&R/bundled mode. The <samp>+DA2.0W</samp> option will result in
461 the automatic selection of the ‘<samp>hppa64-hp-hpux11*</samp>’ target. The
462 macro definition table of cpp needs to be increased for a successful
463 build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to
464 be defined when building with the bundled compiler, or when using the
465 <samp>-Ac</samp> option. These defines aren’t necessary with <samp>-Ae</samp>.
466 </p>
467 <p>It is best to explicitly configure the ‘<samp>hppa64-hp-hpux11*</samp>’ target
468 with the <samp>--with-ld=…</samp> option. This overrides the standard
469 search for ld. The two linkers supported on this target require different
470 commands. The default linker is determined during configuration. As a
471 result, it’s not possible to switch linkers in the middle of a GCC build.
472 This has been reported to sometimes occur in unified builds of binutils
473 and GCC.
474 </p>
475 <p>A recent linker patch must be installed for the correct operation of
476 GCC 3.3 and later. <code>PHSS_26559</code> and <code>PHSS_24304</code> are the
477 oldest linker patches that are known to work. They are for HP-UX
478 11.00 and 11.11, respectively. <code>PHSS_24303</code>, the companion to
479 <code>PHSS_24304</code>, might be usable but it hasn’t been tested. These
480 patches have been superseded. Consult the HP patch database to obtain
481 the currently recommended linker patch for your system.
482 </p>
483 <p>The patches are necessary for the support of weak symbols on the
484 32-bit port, and for the running of initializers and finalizers. Weak
485 symbols are implemented using SOM secondary definition symbols. Prior
486 to HP-UX 11, there are bugs in the linker support for secondary symbols.
487 The patches correct a problem of linker core dumps creating shared
488 libraries containing secondary symbols, as well as various other
489 linking issues involving secondary symbols.
490 </p>
491 <p>GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
492 run initializers and finalizers on the 64-bit port. The 32-bit port
493 uses the linker <samp>+init</samp> and <samp>+fini</samp> options for the same
494 purpose. The patches correct various problems with the +init/+fini
495 options, including program core dumps. Binutils 2.14 corrects a
496 problem on the 64-bit port resulting from HP’s non-standard use of
497 the .init and .fini sections for array initializers and finalizers.
498 </p>
499 <p>Only the HP linker is supported for the ‘<samp>hppa64-hp-hpux11*</samp>’ target.
500 </p>
501 <p>At this time, the GNU linker does not support the creation of long
502 branch stubs. As a result, it cannot successfully link binaries
503 containing branch offsets larger than 8 megabytes. In addition,
504 there are problems linking shared libraries, linking executables
505 with <samp>-static</samp>, and with dwarf2 unwind and exception support.
506 It also doesn’t provide stubs for internal calls to global functions
507 in shared libraries, so these calls cannot be overloaded.
508 </p>
509 <p>The HP dynamic loader does not support GNU symbol versioning, so symbol
510 versioning is not supported. It may be necessary to disable symbol
511 versioning with <samp>--disable-symvers</samp> when using GNU ld.
512 </p>
513 <p>POSIX threads are the default. The optional DCE thread library is not
514 supported, so <samp>--enable-threads=dce</samp> does not work.
515 </p>
516 <hr />
517 <a name="x-x-linux-gnu"></a><a name="g_t*-*-linux-gnu"></a>
518 <h3 class="heading">*-*-linux-gnu</h3>
519 <p>The <code>.init_array</code> and <code>.fini_array</code> sections are enabled
520 unconditionally which requires at least glibc 2.1 and binutils 2.12.
521 </p>
522 <p>Versions of libstdc++-v3 starting with 3.2.1 require bug fixes present
523 in glibc 2.2.5 and later. More information is available in the
524 libstdc++-v3 documentation.
525 </p>
526 <hr />
527 <a name="ix86-x-linux"></a><a name="i_003f86-*-linux*"></a>
528 <h3 class="heading">i?86-*-linux*</h3>
529 <p>As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
530 See <a href="https://gcc.gnu.org/PR10877">bug 10877</a> for more information.
531 </p>
532 <p>If you receive Signal 11 errors when building on GNU/Linux, then it is
533 possible you have a hardware problem. Further information on this can be
534 found on <a href="https://www.bitwizard.nl/sig11/">www.bitwizard.nl</a>.
535 </p>
536 <hr />
537 <a name="ix86-x-solaris2"></a><a name="i_003f86-*-solaris2*"></a>
538 <h3 class="heading">i?86-*-solaris2*</h3>
539 <p>Use this for Solaris 11.3 or later on x86 and x86-64 systems. Starting
540 with GCC 4.7, there is also a 64-bit ‘<samp>amd64-*-solaris2*</samp>’ or
541 ‘<samp>x86_64-*-solaris2*</samp>’ configuration that corresponds to
542 ‘<samp>sparcv9-sun-solaris2*</samp>’.
543 </p>
544 <hr />
545 <a name="ia64-x-linux"></a><a name="ia64-*-linux"></a>
546 <h3 class="heading">ia64-*-linux</h3>
547 <p>IA-64 processor (also known as IPF, or Itanium Processor Family)
548 running GNU/Linux.
549 </p>
550 <p>If you are using the installed system libunwind library with
551 <samp>--with-system-libunwind</samp>, then you must use libunwind 0.98 or
552 later.
553 </p>
554 <hr />
555 <a name="ia64-x-hpux"></a><a name="ia64-*-hpux*"></a>
556 <h3 class="heading">ia64-*-hpux*</h3>
557 <p>Building GCC on this target requires the GNU Assembler. The bundled HP
558 assembler will not work. To prevent GCC from using the wrong assembler,
559 the option <samp>--with-gnu-as</samp> may be necessary.
560 </p>
561 <hr />
562 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
563 <a name="x-ibm-aix"></a><a name="g_t*-ibm-aix*"></a>
564 <h3 class="heading">*-ibm-aix*</h3>
565 <p>Support for AIX version 3 and older was discontinued in GCC 3.4.
566 Support for AIX version 4.2 and older was discontinued in GCC 4.5.
567 </p>
568 <p>“out of memory” bootstrap failures may indicate a problem with
569 process resource limits (ulimit). Hard limits are configured in the
570 <samp>/etc/security/limits</samp> system configuration file.
571 </p>
572 <p>GCC 4.9 and above require a C++ compiler for bootstrap. IBM VAC++ / xlC
573 cannot bootstrap GCC. xlc can bootstrap an older version of GCC and
574 G++ can bootstrap recent releases of GCC.
575 </p>
576 <p>GCC can bootstrap with recent versions of IBM XLC, but bootstrapping
577 with an earlier release of GCC is recommended. Bootstrapping with XLC
578 requires a larger data segment, which can be enabled through the
579 <var>LDR_CNTRL</var> environment variable, e.g.,
580 </p>
581 <div class="smallexample">
582 <pre class="smallexample">% LDR_CNTRL=MAXDATA=0x50000000
583 % export LDR_CNTRL
584 </pre></div>
585
586 <p>One can start with a pre-compiled version of GCC to build from
587 sources. One may delete GCC’s “fixed” header files when starting
588 with a version of GCC built for an earlier release of AIX.
589 </p>
590 <p>To speed up the configuration phases of bootstrapping and installing GCC,
591 one may use GNU Bash instead of AIX <code>/bin/sh</code>, e.g.,
592 </p>
593 <div class="smallexample">
594 <pre class="smallexample">% CONFIG_SHELL=/opt/freeware/bin/bash
595 % export CONFIG_SHELL
596 </pre></div>
597
598 <p>and then proceed as described in <a href="build.html">the build
599 instructions</a>, where we strongly recommend specifying an absolute path
600 to invoke <var>srcdir</var>/configure.
601 </p>
602 <p>Because GCC on AIX is built as a 32-bit executable by default,
603 (although it can generate 64-bit programs) the GMP and MPFR libraries
604 required by gfortran must be 32-bit libraries. Building GMP and MPFR
605 as static archive libraries works better than shared libraries.
606 </p>
607 <p>Errors involving <code>alloca</code> when building GCC generally are due
608 to an incorrect definition of <code>CC</code> in the Makefile or mixing files
609 compiled with the native C compiler and GCC. During the stage1 phase of
610 the build, the native AIX compiler <strong>must</strong> be invoked as <code>cc</code>
611 (not <code>xlc</code>). Once <code>configure</code> has been informed of
612 <code>xlc</code>, one needs to use ‘<samp>make distclean</samp>’ to remove the
613 configure cache files and ensure that <code>CC</code> environment variable
614 does not provide a definition that will confuse <code>configure</code>.
615 If this error occurs during stage2 or later, then the problem most likely
616 is the version of Make (see above).
617 </p>
618 <p>The native <code>as</code> and <code>ld</code> are recommended for
619 bootstrapping on AIX. The GNU Assembler, GNU Linker, and GNU
620 Binutils version 2.20 is the minimum level that supports bootstrap on
621 AIX 5. The GNU Assembler has not been updated to support AIX 6 or
622 AIX 7. The native AIX tools do interoperate with GCC.
623 </p>
624 <p>AIX 7.1 added partial support for DWARF debugging, but full support
625 requires AIX 7.1 TL03 SP7 that supports additional DWARF sections and
626 fixes a bug in the assembler. AIX 7.1 TL03 SP5 distributed a version
627 of libm.a missing important symbols; a fix for IV77796 will be
628 included in SP6.
629 </p>
630 <p>AIX 5.3 TL10, AIX 6.1 TL05 and AIX 7.1 TL00 introduced an AIX
631 assembler change that sometimes produces corrupt assembly files
632 causing AIX linker errors. The bug breaks GCC bootstrap on AIX and
633 can cause compilation failures with existing GCC installations. An
634 AIX iFix for AIX 5.3 is available (APAR IZ98385 for AIX 5.3 TL10, APAR
635 IZ98477 for AIX 5.3 TL11 and IZ98134 for AIX 5.3 TL12). AIX 5.3 TL11 SP8,
636 AIX 5.3 TL12 SP5, AIX 6.1 TL04 SP11, AIX 6.1 TL05 SP7, AIX 6.1 TL06 SP6,
637 AIX 6.1 TL07 and AIX 7.1 TL01 should include the fix.
638 </p>
639 <p>Building <samp>libstdc++.a</samp> requires a fix for an AIX Assembler bug
640 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a
641 fix for another AIX Assembler bug and a co-dependent AIX Archiver fix
642 referenced as APAR IY53606 (AIX 5.2) or as APAR IY54774 (AIX 5.1)
643 </p>
644 <a name="TransferAixShobj"></a><p>‘<samp>libstdc++</samp>’ in GCC 3.4 increments the major version number of the
645 shared object and GCC installation places the <samp>libstdc++.a</samp>
646 shared library in a common location which will overwrite the and GCC
647 3.3 version of the shared library. Applications either need to be
648 re-linked against the new shared library or the GCC 3.1 and GCC 3.3
649 versions of the ‘<samp>libstdc++</samp>’ shared object needs to be available
650 to the AIX runtime loader. The GCC 3.1 ‘<samp>libstdc++.so.4</samp>’, if
651 present, and GCC 3.3 ‘<samp>libstdc++.so.5</samp>’ shared objects can be
652 installed for runtime dynamic loading using the following steps to set
653 the ‘<samp>F_LOADONLY</samp>’ flag in the shared object for <em>each</em>
654 multilib <samp>libstdc++.a</samp> installed:
655 </p>
656 <p>Extract the shared objects from the currently installed
657 <samp>libstdc++.a</samp> archive:
658 </p><div class="smallexample">
659 <pre class="smallexample">% ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
660 </pre></div>
661
662 <p>Enable the ‘<samp>F_LOADONLY</samp>’ flag so that the shared object will be
663 available for runtime dynamic loading, but not linking:
664 </p><div class="smallexample">
665 <pre class="smallexample">% strip -e libstdc++.so.4 libstdc++.so.5
666 </pre></div>
667
668 <p>Archive the runtime-only shared object in the GCC 3.4
669 <samp>libstdc++.a</samp> archive:
670 </p><div class="smallexample">
671 <pre class="smallexample">% ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
672 </pre></div>
673
674 <p>Eventually, the
675 <a href="./configure.html#WithAixSoname"><samp>--with-aix-soname=svr4</samp></a>
676 configure option may drop the need for this procedure for libraries that
677 support it.
678 </p>
679 <p>Linking executables and shared libraries may produce warnings of
680 duplicate symbols. The assembly files generated by GCC for AIX always
681 have included multiple symbol definitions for certain global variable
682 and function declarations in the original program. The warnings should
683 not prevent the linker from producing a correct library or runnable
684 executable.
685 </p>
686 <p>AIX 4.3 utilizes a “large format” archive to support both 32-bit and
687 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
688 to parse archive libraries did not handle the new format correctly.
689 These routines are used by GCC and result in error messages during
690 linking such as “not a COFF file”. The version of the routines shipped
691 with AIX 4.3.1 should work for a 32-bit environment. The <samp>-g</samp>
692 option of the archive command may be used to create archives of 32-bit
693 objects using the original “small format”. A correct version of the
694 routines is shipped with AIX 4.3.2 and above.
695 </p>
696 <p>Some versions of the AIX binder (linker) can fail with a relocation
697 overflow severe error when the <samp>-bbigtoc</samp> option is used to link
698 GCC-produced object files into an executable that overflows the TOC. A fix
699 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
700 available from IBM Customer Support and from its
701 <a href="https://techsupport.services.ibm.com/">techsupport.services.ibm.com</a>
702 website as PTF U455193.
703 </p>
704 <p>The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
705 with a segmentation fault when invoked by any version of GCC. A fix for
706 APAR IX87327 is available from IBM Customer Support and from its
707 <a href="https://techsupport.services.ibm.com/">techsupport.services.ibm.com</a>
708 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
709 </p>
710 <p>The initial assembler shipped with AIX 4.3.0 generates incorrect object
711 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
712 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
713 <a href="https://techsupport.services.ibm.com/">techsupport.services.ibm.com</a>
714 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
715 </p>
716 <p>AIX provides National Language Support (NLS). Compilers and assemblers
717 use NLS to support locale-specific representations of various data
718 formats including floating-point numbers (e.g., ‘<samp>.</samp>’ vs ‘<samp>,</samp>’ for
719 separating decimal fractions). There have been problems reported where
720 GCC does not produce the same floating-point formats that the assembler
721 expects. If one encounters this problem, set the <code>LANG</code>
722 environment variable to ‘<samp>C</samp>’ or ‘<samp>En_US</samp>’.
723 </p>
724 <p>A default can be specified with the <samp>-mcpu=<var>cpu_type</var></samp>
725 switch and using the configure option <samp>--with-cpu-<var>cpu_type</var></samp>.
726 </p>
727 <hr />
728 <a name="iq2000-x-elf"></a><a name="iq2000-*-elf"></a>
729 <h3 class="heading">iq2000-*-elf</h3>
730 <p>Vitesse IQ2000 processors. These are used in embedded
731 applications. There are no standard Unix configurations.
732 </p>
733 <hr />
734 <a name="lm32-x-elf"></a><a name="lm32-*-elf"></a>
735 <h3 class="heading">lm32-*-elf</h3>
736 <p>Lattice Mico32 processor.
737 This configuration is intended for embedded systems.
738 </p>
739 <hr />
740 <a name="lm32-x-uclinux"></a><a name="lm32-*-uclinux"></a>
741 <h3 class="heading">lm32-*-uclinux</h3>
742 <p>Lattice Mico32 processor.
743 This configuration is intended for embedded systems running uClinux.
744 </p>
745 <hr />
746 <a name="loongarch"></a><a name="LoongArch"></a>
747 <h3 class="heading">LoongArch</h3>
748 <p>LoongArch processor.
749 The following LoongArch targets are available:
750 </p><dl compact="compact">
751 <dt><code>loongarch64-linux-gnu*</code></dt>
752 <dd><p>LoongArch processor running GNU/Linux. This target triplet may be coupled
753 with a small set of possible suffixes to identify their default ABI type:
754 </p><dl compact="compact">
755 <dt><code>f64</code></dt>
756 <dd><p>Uses <code>lp64d/base</code> ABI by default.
757 </p></dd>
758 <dt><code>f32</code></dt>
759 <dd><p>Uses <code>lp64f/base</code> ABI by default.
760 </p></dd>
761 <dt><code>sf</code></dt>
762 <dd><p>Uses <code>lp64s/base</code> ABI by default.
763 </p></dd>
764 </dl>
765
766 </dd>
767 <dt><code>loongarch64-linux-gnu</code></dt>
768 <dd><p>Same as <code>loongarch64-linux-gnuf64</code> for legacy support.
769 </p></dd>
770 </dl>
771
772 <p>More information about LoongArch can be found at
773 <a href="https://github.com/loongson/LoongArch-Documentation">https://github.com/loongson/LoongArch-Documentation</a>.
774 </p>
775 <hr />
776 <a name="m32c-x-elf"></a><a name="m32c-*-elf"></a>
777 <h3 class="heading">m32c-*-elf</h3>
778 <p>Renesas M32C processor.
779 This configuration is intended for embedded systems.
780 </p>
781 <hr />
782 <a name="m32r-x-elf"></a><a name="m32r-*-elf"></a>
783 <h3 class="heading">m32r-*-elf</h3>
784 <p>Renesas M32R processor.
785 This configuration is intended for embedded systems.
786 </p>
787 <hr />
788 <a name="m68k-x-x"></a><a name="m68k-*-*"></a>
789 <h3 class="heading">m68k-*-*</h3>
790 <p>By default,
791 ‘<samp>m68k-*-elf*</samp>’, ‘<samp>m68k-*-rtems</samp>’, ‘<samp>m68k-*-uclinux</samp>’ and
792 ‘<samp>m68k-*-linux</samp>’
793 build libraries for both M680x0 and ColdFire processors. If you only
794 need the M680x0 libraries, you can omit the ColdFire ones by passing
795 <samp>--with-arch=m68k</samp> to <code>configure</code>. Alternatively, you
796 can omit the M680x0 libraries by passing <samp>--with-arch=cf</samp> to
797 <code>configure</code>. These targets default to 5206 or 5475 code as
798 appropriate for the target system when
799 configured with <samp>--with-arch=cf</samp> and 68020 code otherwise.
800 </p>
801 <p>The ‘<samp>m68k-*-netbsd</samp>’ and
802 ‘<samp>m68k-*-openbsd</samp>’ targets also support the <samp>--with-arch</samp>
803 option. They will generate ColdFire CFV4e code when configured with
804 <samp>--with-arch=cf</samp> and 68020 code otherwise.
805 </p>
806 <p>You can override the default processors listed above by configuring
807 with <samp>--with-cpu=<var>target</var></samp>. This <var>target</var> can either
808 be a <samp>-mcpu</samp> argument or one of the following values:
809 ‘<samp>m68000</samp>’, ‘<samp>m68010</samp>’, ‘<samp>m68020</samp>’, ‘<samp>m68030</samp>’,
810 ‘<samp>m68040</samp>’, ‘<samp>m68060</samp>’, ‘<samp>m68020-40</samp>’ and ‘<samp>m68020-60</samp>’.
811 </p>
812 <p>GCC requires at least binutils version 2.17 on these targets.
813 </p>
814 <hr />
815 <a name="m68k-x-uclinux"></a><a name="m68k-*-uclinux"></a>
816 <h3 class="heading">m68k-*-uclinux</h3>
817 <p>GCC 4.3 changed the uClinux configuration so that it uses the
818 ‘<samp>m68k-linux-gnu</samp>’ ABI rather than the ‘<samp>m68k-elf</samp>’ ABI.
819 It also added improved support for C++ and flat shared libraries,
820 both of which were ABI changes.
821 </p>
822 <hr />
823 <a name="microblaze-x-elf"></a><a name="microblaze-*-elf"></a>
824 <h3 class="heading">microblaze-*-elf</h3>
825 <p>Xilinx MicroBlaze processor.
826 This configuration is intended for embedded systems.
827 </p>
828 <hr />
829 <a name="mips-x-x"></a><a name="mips-*-*"></a>
830 <h3 class="heading">mips-*-*</h3>
831 <p>If on a MIPS system you get an error message saying “does not have gp
832 sections for all it’s [sic] sectons [sic]”, don’t worry about it. This
833 happens whenever you use GAS with the MIPS linker, but there is not
834 really anything wrong, and it is okay to use the output file. You can
835 stop such warnings by installing the GNU linker.
836 </p>
837 <p>It would be nice to extend GAS to produce the gp tables, but they are
838 optional, and there should not be a warning about their absence.
839 </p>
840 <p>The libstdc++ atomic locking routines for MIPS targets requires MIPS II
841 and later. A patch went in just after the GCC 3.3 release to
842 make ‘<samp>mips*-*-*</samp>’ use the generic implementation instead. You can also
843 configure for ‘<samp>mipsel-elf</samp>’ as a workaround. The
844 ‘<samp>mips*-*-linux*</samp>’ target continues to use the MIPS II routines. More
845 work on this is expected in future releases.
846 </p>
847
848 <p>The built-in <code>__sync_*</code> functions are available on MIPS II and
849 later systems and others that support the ‘<samp>ll</samp>’, ‘<samp>sc</samp>’ and
850 ‘<samp>sync</samp>’ instructions. This can be overridden by passing
851 <samp>--with-llsc</samp> or <samp>--without-llsc</samp> when configuring GCC.
852 Since the Linux kernel emulates these instructions if they are
853 missing, the default for ‘<samp>mips*-*-linux*</samp>’ targets is
854 <samp>--with-llsc</samp>. The <samp>--with-llsc</samp> and
855 <samp>--without-llsc</samp> configure options may be overridden at compile
856 time by passing the <samp>-mllsc</samp> or <samp>-mno-llsc</samp> options to
857 the compiler.
858 </p>
859 <p>MIPS systems check for division by zero (unless
860 <samp>-mno-check-zero-division</samp> is passed to the compiler) by
861 generating either a conditional trap or a break instruction. Using
862 trap results in smaller code, but is only supported on MIPS II and
863 later. Also, some versions of the Linux kernel have a bug that
864 prevents trap from generating the proper signal (<code>SIGFPE</code>). To enable
865 the use of break, use the <samp>--with-divide=breaks</samp>
866 <code>configure</code> option when configuring GCC. The default is to
867 use traps on systems that support them.
868 </p>
869 <hr />
870 <a name="moxie-x-elf"></a><a name="moxie-*-elf"></a>
871 <h3 class="heading">moxie-*-elf</h3>
872 <p>The moxie processor.
873 </p>
874 <hr />
875 <a name="msp430-x-elf"></a><a name="msp430-*-elf*"></a>
876 <h3 class="heading">msp430-*-elf*</h3>
877 <p>TI MSP430 processor.
878 This configuration is intended for embedded systems.
879 </p>
880 <p>‘<samp>msp430-*-elf</samp>’ is the standard configuration with most GCC
881 features enabled by default.
882 </p>
883 <p>‘<samp>msp430-*-elfbare</samp>’ is tuned for a bare-metal environment, and disables
884 features related to shared libraries and other functionality not used for
885 this device. This reduces code and data usage of the GCC libraries, resulting
886 in a minimal run-time environment by default.
887 </p>
888 <p>Features disabled by default include:
889 </p><ul>
890 <li> transactional memory
891 </li><li> __cxa_atexit
892 </li></ul>
893
894 <hr />
895 <a name="nds32le-x-elf"></a><a name="nds32le-*-elf"></a>
896 <h3 class="heading">nds32le-*-elf</h3>
897 <p>Andes NDS32 target in little endian mode.
898 </p>
899 <hr />
900 <a name="nds32be-x-elf"></a><a name="nds32be-*-elf"></a>
901 <h3 class="heading">nds32be-*-elf</h3>
902 <p>Andes NDS32 target in big endian mode.
903 </p>
904 <hr />
905 <a name="nvptx-x-none"></a><a name="nvptx-*-none"></a>
906 <h3 class="heading">nvptx-*-none</h3>
907 <p>Nvidia PTX target.
908 </p>
909 <p>Instead of GNU binutils, you will need to install
910 <a href="https://github.com/SourceryTools/nvptx-tools">nvptx-tools</a>.
911 Tell GCC where to find it:
912 <samp>--with-build-time-tools=[install-nvptx-tools]/nvptx-none/bin</samp>.
913 </p>
914 <p>You will need newlib 4.3.0 or later. It can be
915 automatically built together with GCC. For this, add a symbolic link
916 to nvptx-newlib’s <samp>newlib</samp> directory to the directory containing
917 the GCC sources.
918 </p>
919 <p>Use the <samp>--disable-sjlj-exceptions</samp> and
920 <samp>--enable-newlib-io-long-long</samp> options when configuring.
921 </p>
922 <p>The <samp>--with-arch</samp> option may be specified to override the
923 default value for the <samp>-march</samp> option, and to also build
924 corresponding target libraries.
925 The default is <samp>--with-arch=sm_30</samp>.
926 </p>
927 <p>For example, if <samp>--with-arch=sm_70</samp> is specified,
928 <samp>-march=sm_30</samp> and <samp>-march=sm_70</samp> target libraries are
929 built, and code generation defaults to <samp>-march=sm_70</samp>.
930 </p>
931 <hr />
932 <a name="or1k-x-elf"></a><a name="or1k-*-elf"></a>
933 <h3 class="heading">or1k-*-elf</h3>
934 <p>The OpenRISC 1000 32-bit processor with delay slots.
935 This configuration is intended for embedded systems.
936 </p>
937 <hr />
938 <a name="or1k-x-linux"></a><a name="or1k-*-linux"></a>
939 <h3 class="heading">or1k-*-linux</h3>
940 <p>The OpenRISC 1000 32-bit processor with delay slots.
941 </p>
942 <hr />
943 <a name="powerpc-x-x"></a><a name="powerpc-*-*"></a>
944 <h3 class="heading">powerpc-*-*</h3>
945 <p>You can specify a default version for the <samp>-mcpu=<var>cpu_type</var></samp>
946 switch by using the configure option <samp>--with-cpu-<var>cpu_type</var></samp>.
947 </p>
948 <p>You will need GNU binutils 2.20 or newer.
949 </p>
950 <hr />
951 <a name="powerpc-x-darwin"></a><a name="powerpc-*-darwin*"></a>
952 <h3 class="heading">powerpc-*-darwin*</h3>
953 <p>PowerPC running Darwin (Mac OS X kernel).
954 </p>
955 <p>Pre-installed versions of Mac OS X may not include any developer tools,
956 meaning that you will not be able to build GCC from source. Tool
957 binaries are available at
958 <a href="https://opensource.apple.com">https://opensource.apple.com</a>.
959 </p>
960 <p>This version of GCC requires at least cctools-590.36. The
961 cctools-590.36 package referenced from
962 <a href="https://gcc.gnu.org/ml/gcc/2006-03/msg00507.html">https://gcc.gnu.org/ml/gcc/2006-03/msg00507.html</a> will not work
963 on systems older than 10.3.9 (aka darwin7.9.0).
964 </p>
965 <hr />
966 <a name="powerpc-x-elf"></a><a name="powerpc-*-elf"></a>
967 <h3 class="heading">powerpc-*-elf</h3>
968 <p>PowerPC system in big endian mode, running System V.4.
969 </p>
970 <hr />
971 <a name="powerpc-x-linux-gnu"></a><a name="powerpc*-*-linux-gnu*"></a>
972 <h3 class="heading">powerpc*-*-linux-gnu*</h3>
973 <p>PowerPC system in big endian mode running Linux.
974 </p>
975 <hr />
976 <a name="powerpc-x-netbsd"></a><a name="powerpc-*-netbsd*"></a>
977 <h3 class="heading">powerpc-*-netbsd*</h3>
978 <p>PowerPC system in big endian mode running NetBSD.
979 </p>
980 <hr />
981 <a name="powerpc-x-eabisim"></a><a name="powerpc-*-eabisim"></a>
982 <h3 class="heading">powerpc-*-eabisim</h3>
983 <p>Embedded PowerPC system in big endian mode for use in running under the
984 PSIM simulator.
985 </p>
986 <hr />
987 <a name="powerpc-x-eabi"></a><a name="powerpc-*-eabi"></a>
988 <h3 class="heading">powerpc-*-eabi</h3>
989 <p>Embedded PowerPC system in big endian mode.
990 </p>
991 <hr />
992 <a name="powerpcle-x-elf"></a><a name="powerpcle-*-elf"></a>
993 <h3 class="heading">powerpcle-*-elf</h3>
994 <p>PowerPC system in little endian mode, running System V.4.
995 </p>
996 <hr />
997 <a name="powerpcle-x-eabisim"></a><a name="powerpcle-*-eabisim"></a>
998 <h3 class="heading">powerpcle-*-eabisim</h3>
999 <p>Embedded PowerPC system in little endian mode for use in running under
1000 the PSIM simulator.
1001 </p>
1002 <hr />
1003 <a name="powerpcle-x-eabi"></a><a name="powerpcle-*-eabi"></a>
1004 <h3 class="heading">powerpcle-*-eabi</h3>
1005 <p>Embedded PowerPC system in little endian mode.
1006 </p>
1007 <hr />
1008 <a name="rl78-x-elf"></a><a name="rl78-*-elf"></a>
1009 <h3 class="heading">rl78-*-elf</h3>
1010 <p>The Renesas RL78 processor.
1011 This configuration is intended for embedded systems.
1012 </p>
1013 <hr />
1014 <a name="riscv32-x-elf"></a><a name="riscv32-*-elf"></a>
1015 <h3 class="heading">riscv32-*-elf</h3>
1016 <p>The RISC-V RV32 instruction set.
1017 This configuration is intended for embedded systems.
1018 This (and all other RISC-V) targets require the binutils 2.30 release.
1019 </p>
1020 <hr />
1021 <a name="riscv32-x-linux"></a><a name="riscv32-*-linux"></a>
1022 <h3 class="heading">riscv32-*-linux</h3>
1023 <p>The RISC-V RV32 instruction set running GNU/Linux.
1024 This (and all other RISC-V) targets require the binutils 2.30 release.
1025 </p>
1026 <hr />
1027 <a name="riscv64-x-elf"></a><a name="riscv64-*-elf"></a>
1028 <h3 class="heading">riscv64-*-elf</h3>
1029 <p>The RISC-V RV64 instruction set.
1030 This configuration is intended for embedded systems.
1031 This (and all other RISC-V) targets require the binutils 2.30 release.
1032 </p>
1033 <hr />
1034 <a name="riscv64-x-linux"></a><a name="riscv64-*-linux"></a>
1035 <h3 class="heading">riscv64-*-linux</h3>
1036 <p>The RISC-V RV64 instruction set running GNU/Linux.
1037 This (and all other RISC-V) targets require the binutils 2.30 release.
1038 </p>
1039 <hr />
1040 <a name="rx-x-elf"></a><a name="rx-*-elf"></a>
1041 <h3 class="heading">rx-*-elf</h3>
1042 <p>The Renesas RX processor.
1043 </p>
1044 <hr />
1045 <a name="s390-x-linux"></a><a name="s390-*-linux*"></a>
1046 <h3 class="heading">s390-*-linux*</h3>
1047 <p>S/390 system running GNU/Linux for S/390.
1048 </p>
1049 <hr />
1050 <a name="s390x-x-linux"></a><a name="s390x-*-linux*"></a>
1051 <h3 class="heading">s390x-*-linux*</h3>
1052 <p>zSeries system (64-bit) running GNU/Linux for zSeries.
1053 </p>
1054 <hr />
1055 <a name="s390x-ibm-tpf"></a><a name="s390x-ibm-tpf*"></a>
1056 <h3 class="heading">s390x-ibm-tpf*</h3>
1057 <p>zSeries system (64-bit) running TPF. This platform is
1058 supported as cross-compilation target only.
1059 </p>
1060 <hr />
1061 <a name="x-x-solaris2"></a><a name="g_t*-*-solaris2*"></a>
1062 <h3 class="heading">*-*-solaris2*</h3>
1063 <p>Support for Solaris 11.3 and earlier has been obsoleted in GCC 13, but
1064 can still be enabled by configuring with <samp>--enable-obsolete</samp>.
1065 Support for Solaris 10 has been removed in GCC 10. Support for Solaris
1066 9 has been removed in GCC 5. Support for Solaris 8 has been removed in
1067 GCC 4.8. Support for Solaris 7 has been removed in GCC 4.6.
1068 </p>
1069 <p>Solaris 11.3 provides GCC 4.5.2, 4.7.3, and 4.8.2 as
1070 <code>/usr/gcc/4.5/bin/gcc</code> or similar. Solaris 11.4
1071 provides one or more of GCC 5, 7, 9, 10, 11, and 12.
1072 </p>
1073 <p>You need to install the <code>system/header</code>, <code>system/linker</code>, and
1074 <code>developer/assembler</code> packages.
1075 </p>
1076 <p>Trying to use the compatibility tools in <samp>/usr/ucb</samp>, from the
1077 <code>compatibility/ucb</code> package, to install GCC has been observed to
1078 cause trouble. The fix is to remove <samp>/usr/ucb</samp> from your
1079 <code>PATH</code>.
1080 </p>
1081 <p>The build process works more smoothly with the legacy Solaris tools so,
1082 if you have <samp>/usr/xpg4/bin</samp> in your <code>PATH</code>, we recommend that
1083 you place <samp>/usr/bin</samp> before <samp>/usr/xpg4/bin</samp> for the duration
1084 of the build.
1085 </p>
1086 <p>We recommend the use of the Solaris assembler or the GNU assembler, in
1087 conjunction with the Solaris linker.
1088 </p>
1089 <p>The GNU <code>as</code> versions included in Solaris 11.3, from GNU
1090 binutils 2.23.1 or newer (in <samp>/usr/bin/gas</samp> and
1091 <samp>/usr/gnu/bin/as</samp>), are known to work. The version from GNU
1092 binutils 2.40 is known to work as well. Recent versions of the Solaris
1093 assembler in <samp>/usr/bin/as</samp> work almost as well, though. To use GNU
1094 <code>as</code>, configure with the options <samp>--with-gnu-as
1095 --with-as=/usr/gnu/bin/as</samp>.
1096 </p>
1097 <p>For linking, the Solaris linker is preferred. If you want to use the
1098 GNU linker instead, the version in Solaris 11.3, from GNU binutils
1099 2.23.1 or newer (in <samp>/usr/gnu/bin/ld</samp> and <samp>/usr/bin/gld</samp>),
1100 works, as does the version from GNU binutils 2.40. However, it
1101 generally lacks platform specific features, so better stay with Solaris
1102 <code>ld</code>. To use the LTO linker plugin
1103 (<samp>-fuse-linker-plugin</samp>) with GNU <code>ld</code>, GNU binutils
1104 <em>must</em> be configured with <samp>--enable-largefile</samp>. To use
1105 Solaris <code>ld</code>, we recommend to configure with
1106 <samp>--without-gnu-ld --with-ld=/usr/bin/ld</samp> to guarantee the
1107 right linker is found irrespective of the user’s <code>PATH</code>.
1108 </p>
1109 <p>Note that your mileage may vary if you use a combination of the GNU
1110 tools and the Solaris tools: while the combination GNU <code>as</code> and
1111 Solaris <code>ld</code> works well, the reverse combination Solaris
1112 <code>as</code> with GNU <code>ld</code> may fail to build or cause memory
1113 corruption at runtime in some cases for C++ programs.
1114 </p>
1115 <p>To enable symbol versioning in ‘<samp>libstdc++</samp>’ and other runtime
1116 libraries with the Solaris linker, you need to have any version of GNU
1117 <code>c++filt</code>, which is part of GNU binutils. Symbol versioning
1118 will be disabled if no appropriate version is found. Solaris
1119 <code>c++filt</code> from the Solaris Studio compilers does <em>not</em>
1120 work.
1121 </p>
1122 <p>In order to build the GNU Ada compiler, GNAT, a working GNAT is needed.
1123 Since Solaris 11.4 SRU 39, GNAT 11 or 12 is bundled in the
1124 <code>developer/gcc/gcc-gnat</code> package.
1125 </p>
1126 <p>In order to build the GNU D compiler, GDC, a working ‘<samp>libphobos</samp>’ is
1127 needed. That library wasn’t built by default in GCC 9–11 on SPARC, or
1128 on x86 when the Solaris assembler is used, but can be enabled by
1129 configuring with <samp>--enable-libphobos</samp>. Also, GDC 9.4.0 is
1130 required on x86, while GDC 9.3.0 is known to work on SPARC.
1131 </p>
1132 <p>The versions of the GNU Multiple Precision Library (GMP), the MPFR
1133 library and the MPC library bundled with Solaris 11.3 and later are
1134 usually recent enough to match GCC’s requirements. There are two
1135 caveats:
1136 </p>
1137 <ul>
1138 <li> While the version of the GMP library in Solaris 11.3 works with GCC, you
1139 need to configure with <samp>--with-gmp-include=/usr/include/gmp</samp>.
1140
1141 </li><li> The version of the MPFR libary included in Solaris 11.3 is too old; you
1142 need to provide a more recent one.
1143
1144 </li></ul>
1145
1146 <hr />
1147 <a name="sparc-x-x"></a><a name="sparc*-*-*"></a>
1148 <h3 class="heading">sparc*-*-*</h3>
1149 <p>This section contains general configuration information for all
1150 SPARC-based platforms. In addition to reading this section, please
1151 read all other sections that match your target.
1152 </p>
1153 <p>Newer versions of the GNU Multiple Precision Library (GMP), the MPFR
1154 library and the MPC library are known to be miscompiled by earlier
1155 versions of GCC on these platforms. We therefore recommend the use
1156 of the exact versions of these libraries listed as minimal versions
1157 in <a href="prerequisites.html">the prerequisites</a>.
1158 </p>
1159 <hr />
1160 <a name="sparc-sun-solaris2"></a><a name="sparc-sun-solaris2*"></a>
1161 <h3 class="heading">sparc-sun-solaris2*</h3>
1162 <p>When GCC is configured to use GNU binutils 2.14 or later, the binaries
1163 produced are smaller than the ones produced using Solaris native tools;
1164 this difference is quite significant for binaries containing debugging
1165 information.
1166 </p>
1167 <p>Starting with Solaris 7, the operating system is capable of executing
1168 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
1169 this; the <samp>-m64</samp> option enables 64-bit code generation.
1170 </p>
1171 <p>When configuring the GNU Multiple Precision Library (GMP), the MPFR
1172 library or the MPC library on Solaris, the canonical target triplet must
1173 be specified as the <code>build</code> parameter on the <code>configure</code>
1174 line. This target triplet can be obtained by invoking
1175 <code>./config.guess</code> in the toplevel source directory of GCC (and
1176 not that of GMP or MPFR or MPC). For example:
1177 </p>
1178 <div class="smallexample">
1179 <pre class="smallexample">% <var>srcdir</var>/configure --build=sparc-sun-solaris2.11 --prefix=<var>dirname</var>
1180 </pre></div>
1181
1182 <hr />
1183 <a name="sparc-x-linux"></a><a name="sparc-*-linux*"></a>
1184 <h3 class="heading">sparc-*-linux*</h3>
1185
1186 <hr />
1187 <a name="sparc64-x-solaris2"></a><a name="sparc64-*-solaris2*"></a>
1188 <h3 class="heading">sparc64-*-solaris2*</h3>
1189 <p>This is a synonym for ‘<samp>sparcv9-*-solaris2*</samp>’.
1190 </p>
1191 <hr />
1192 <a name="sparcv9-x-solaris2"></a><a name="sparcv9-*-solaris2*"></a>
1193 <h3 class="heading">sparcv9-*-solaris2*</h3>
1194
1195 <p>When configuring a 64-bit-default GCC on Solaris/SPARC, you must use a
1196 build compiler that generates 64-bit code, either by default or by
1197 specifying ‘<samp>CC='gcc -m64' CXX='g++ -m64' GDC='gdc -m64'</samp>’ to <code>configure</code>.
1198 Additionally, you <em>must</em> pass <samp>--build=sparcv9-sun-solaris2.11</samp>
1199 or <samp>--build=sparc64-sun-solaris2.11</samp> because <samp>config.guess</samp>
1200 misdetects this situation, which can cause build failures.
1201 </p>
1202 <p>When configuring the GNU Multiple Precision Library (GMP), the MPFR
1203 library or the MPC library, the canonical target triplet must be specified
1204 as the <code>build</code> parameter on the <code>configure</code> line. For example:
1205 </p>
1206 <div class="smallexample">
1207 <pre class="smallexample">% <var>srcdir</var>/configure --build=sparcv9-sun-solaris2.11 --prefix=<var>dirname</var>
1208 </pre></div>
1209
1210 <hr />
1211 <a name="c6x-x-x"></a><a name="c6x-*-*"></a>
1212 <h3 class="heading">c6x-*-*</h3>
1213 <p>The C6X family of processors. This port requires binutils-2.22 or newer.
1214 </p>
1215 <hr />
1216 <a name="visium-x-elf"></a><a name="visium-*-elf"></a>
1217 <h3 class="heading">visium-*-elf</h3>
1218 <p>CDS VISIUMcore processor.
1219 This configuration is intended for embedded systems.
1220 </p>
1221 <hr />
1222 <a name="x-x-vxworks"></a><a name="g_t*-*-vxworks*"></a>
1223 <h3 class="heading">*-*-vxworks*</h3>
1224 <p>Support for VxWorks is in flux. At present GCC supports <em>only</em> the
1225 very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC.
1226 We welcome patches for other architectures supported by VxWorks 5.5.
1227 Support for VxWorks AE would also be welcome; we believe this is merely
1228 a matter of writing an appropriate “configlette” (see below). We are
1229 not interested in supporting older, a.out or COFF-based, versions of
1230 VxWorks in GCC 3.
1231 </p>
1232 <p>VxWorks comes with an older version of GCC installed in
1233 <samp><var>$WIND_BASE</var>/host</samp>; we recommend you do not overwrite it.
1234 Choose an installation <var>prefix</var> entirely outside <var>$WIND_BASE</var>.
1235 Before running <code>configure</code>, create the directories <samp><var>prefix</var></samp>
1236 and <samp><var>prefix</var>/bin</samp>. Link or copy the appropriate assembler,
1237 linker, etc. into <samp><var>prefix</var>/bin</samp>, and set your <var>PATH</var> to
1238 include that directory while running both <code>configure</code> and
1239 <code>make</code>.
1240 </p>
1241 <p>You must give <code>configure</code> the
1242 <samp>--with-headers=<var>$WIND_BASE</var>/target/h</samp> switch so that it can
1243 find the VxWorks system headers. Since VxWorks is a cross compilation
1244 target only, you must also specify <samp>--target=<var>target</var></samp>.
1245 <code>configure</code> will attempt to create the directory
1246 <samp><var>prefix</var>/<var>target</var>/sys-include</samp> and copy files into it;
1247 make sure the user running <code>configure</code> has sufficient privilege
1248 to do so.
1249 </p>
1250 <p>GCC’s exception handling runtime requires a special “configlette”
1251 module, <samp>contrib/gthr_supp_vxw_5x.c</samp>. Follow the instructions in
1252 that file to add the module to your kernel build. (Future versions of
1253 VxWorks will incorporate this module.)
1254 </p>
1255 <hr />
1256 <a name="x86-64-x-x"></a><a name="x86_005f64-*-*_002c-amd64-*-*"></a>
1257 <h3 class="heading">x86_64-*-*, amd64-*-*</h3>
1258 <p>GCC supports the x86-64 architecture implemented by the AMD64 processor
1259 (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD.
1260 On GNU/Linux the default is a bi-arch compiler which is able to generate
1261 both 64-bit x86-64 and 32-bit x86 code (via the <samp>-m32</samp> switch).
1262 </p>
1263 <hr />
1264 <a name="x86-64-x-solaris2"></a><a name="x86_005f64-*-solaris2*"></a>
1265 <h3 class="heading">x86_64-*-solaris2*</h3>
1266 <p>GCC also supports the x86-64 architecture implemented by the AMD64
1267 processor (‘<samp>amd64-*-*</samp>’ is an alias for ‘<samp>x86_64-*-*</samp>’).
1268 Unlike other systems, without special options a
1269 bi-arch compiler is built which generates 32-bit code by default, but
1270 can generate 64-bit x86-64 code with the <samp>-m64</samp> switch. Since
1271 GCC 4.7, there is also a configuration that defaults to 64-bit code, but
1272 can generate 32-bit code with <samp>-m32</samp>. To configure and build
1273 this way, you have to provide all support libraries like <samp>libgmp</samp>
1274 as 64-bit code, configure with <samp>--target=x86_64-pc-solaris2.11</samp>
1275 and ‘<samp>CC=gcc -m64</samp>’.
1276 </p>
1277 <hr />
1278 <a name="xtensa-x-elf"></a><a name="xtensa*-*-elf"></a>
1279 <h3 class="heading">xtensa*-*-elf</h3>
1280 <p>This target is intended for embedded Xtensa systems using the
1281 ‘<samp>newlib</samp>’ C library. It uses ELF but does not support shared
1282 objects. Designed-defined instructions specified via the
1283 Tensilica Instruction Extension (TIE) language are only supported
1284 through inline assembly.
1285 </p>
1286 <p>The Xtensa configuration information must be specified prior to
1287 building GCC. The <samp>include/xtensa-config.h</samp> header
1288 file contains the configuration information. If you created your
1289 own Xtensa configuration with the Xtensa Processor Generator, the
1290 downloaded files include a customized copy of this header file,
1291 which you can use to replace the default header file.
1292 </p>
1293 <hr />
1294 <a name="xtensa-x-linux"></a><a name="xtensa*-*-linux*"></a>
1295 <h3 class="heading">xtensa*-*-linux*</h3>
1296 <p>This target is for Xtensa systems running GNU/Linux. It supports ELF
1297 shared objects and the GNU C library (glibc). It also generates
1298 position-independent code (PIC) regardless of whether the
1299 <samp>-fpic</samp> or <samp>-fPIC</samp> options are used. In other
1300 respects, this target is the same as the
1301 <a href="#xtensa*-*-elf">‘<samp>xtensa*-*-elf</samp>’</a> target.
1302 </p>
1303 <hr />
1304 <a name="windows"></a><a name="Microsoft-Windows"></a>
1305 <h3 class="heading">Microsoft Windows</h3>
1306
1307 <a name="Intel-16-bit-versions"></a>
1308 <h4 class="subheading">Intel 16-bit versions</h4>
1309 <p>The 16-bit versions of Microsoft Windows, such as Windows 3.1, are not
1310 supported.
1311 </p>
1312 <p>However, the 32-bit port has limited support for Microsoft
1313 Windows 3.11 in the Win32s environment, as a target only. See below.
1314 </p>
1315 <a name="Intel-32-bit-versions"></a>
1316 <h4 class="subheading">Intel 32-bit versions</h4>
1317 <p>The 32-bit versions of Windows, including Windows 95, Windows NT, Windows
1318 XP, and Windows Vista, are supported by several different target
1319 platforms. These targets differ in which Windows subsystem they target
1320 and which C libraries are used.
1321 </p>
1322 <ul>
1323 <li> Cygwin <a href="#x-x-cygwin">*-*-cygwin</a>: Cygwin provides a user-space
1324 Linux API emulation layer in the Win32 subsystem.
1325 </li><li> MinGW <a href="#x-x-mingw32">*-*-mingw32</a>: MinGW is a native GCC port for
1326 the Win32 subsystem that provides a subset of POSIX.
1327 </li><li> MKS i386-pc-mks: NuTCracker from MKS. See
1328 <a href="https://www.mkssoftware.com">https://www.mkssoftware.com</a> for more information.
1329 </li></ul>
1330
1331 <a name="Intel-64-bit-versions"></a>
1332 <h4 class="subheading">Intel 64-bit versions</h4>
1333 <p>GCC contains support for x86-64 using the mingw-w64
1334 runtime library, available from <a href="https://www.mingw-w64.org/downloads/">https://www.mingw-w64.org/downloads/</a>.
1335 This library should be used with the target triple x86_64-pc-mingw32.
1336 </p>
1337 <a name="Windows-CE"></a>
1338 <h4 class="subheading">Windows CE</h4>
1339 <p>Windows CE is supported as a target only on Hitachi
1340 SuperH (sh-wince-pe), and MIPS (mips-wince-pe).
1341 </p>
1342 <a name="Other-Windows-Platforms"></a>
1343 <h4 class="subheading">Other Windows Platforms</h4>
1344 <p>GCC no longer supports Windows NT on the Alpha or PowerPC.
1345 </p>
1346 <p>GCC no longer supports the Windows POSIX subsystem. However, it does
1347 support the Interix subsystem. See above.
1348 </p>
1349 <p>Old target names including *-*-winnt and *-*-windowsnt are no longer used.
1350 </p>
1351 <p>UWIN support has been removed due to a lack of maintenance.
1352 </p>
1353 <hr />
1354 <a name="x-x-cygwin"></a><a name="g_t*-*-cygwin"></a>
1355 <h3 class="heading">*-*-cygwin</h3>
1356 <p>Ports of GCC are included with the
1357 <a href="http://www.cygwin.com/">Cygwin environment</a>.
1358 </p>
1359 <p>GCC will build under Cygwin without modification; it does not build
1360 with Microsoft’s C++ compiler and there are no plans to make it do so.
1361 </p>
1362 <p>The Cygwin native compiler can be configured to target any 32-bit x86
1363 cpu architecture desired; the default is i686-pc-cygwin. It should be
1364 used with as up-to-date a version of binutils as possible; use either
1365 the latest official GNU binutils release in the Cygwin distribution,
1366 or version 2.20 or above if building your own.
1367 </p>
1368 <hr />
1369 <a name="x-x-mingw32"></a><a name="g_t*-*-mingw32"></a>
1370 <h3 class="heading">*-*-mingw32</h3>
1371 <p>GCC will build with and support only MinGW runtime 3.12 and later.
1372 Earlier versions of headers are incompatible with the new default semantics
1373 of <code>extern inline</code> in <code>-std=c99</code> and <code>-std=gnu99</code> modes.
1374 </p>
1375 <p>To support emitting DWARF debugging info you need to use GNU binutils
1376 version 2.16 or above containing support for the <code>.secrel32</code>
1377 assembler pseudo-op.
1378 </p>
1379 <hr />
1380 <a name="older"></a><a name="Older-systems"></a>
1381 <h3 class="heading">Older systems</h3>
1382 <p>GCC contains support files for many older (1980s and early
1383 1990s) Unix variants. For the most part, support for these systems
1384 has not been deliberately removed, but it has not been maintained for
1385 several years and may suffer from bitrot.
1386 </p>
1387 <p>Starting with GCC 3.1, each release has a list of “obsoleted” systems.
1388 Support for these systems is still present in that release, but
1389 <code>configure</code> will fail unless the <samp>--enable-obsolete</samp>
1390 option is given. Unless a maintainer steps forward, support for these
1391 systems will be removed from the next release of GCC.
1392 </p>
1393 <p>Support for old systems as hosts for GCC can cause problems if the
1394 workarounds for compiler, library and operating system bugs affect the
1395 cleanliness or maintainability of the rest of GCC. In some cases, to
1396 bring GCC up on such a system, if still possible with current GCC, may
1397 require first installing an old version of GCC which did work on that
1398 system, and using it to compile a more recent GCC, to avoid bugs in the
1399 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
1400 <samp>old-releases</samp> directory on the <a href="../mirrors.html">GCC mirror
1401 sites</a>. Header bugs may generally be avoided using
1402 <code>fixincludes</code>, but bugs or deficiencies in libraries and the
1403 operating system may still cause problems.
1404 </p>
1405 <p>Support for older systems as targets for cross-compilation is less
1406 problematic than support for them as hosts for GCC; if an enthusiast
1407 wishes to make such a target work again (including resurrecting any of
1408 the targets that never worked with GCC 2, starting from the last
1409 version before they were removed), patches
1410 <a href="../contribute.html">following the usual requirements</a> would be
1411 likely to be accepted, since they should not affect the support for more
1412 modern targets.
1413 </p>
1414 <p>For some systems, old versions of GNU binutils may also be useful,
1415 and are available from <samp>pub/binutils/old-releases</samp> on
1416 <a href="https://sourceware.org/mirrors.html">sourceware.org mirror sites</a>.
1417 </p>
1418 <p>Some of the information on specific systems above relates to
1419 such older systems, but much of the information
1420 about GCC on such systems (which may no longer be applicable to
1421 current GCC) is to be found in the GCC texinfo manual.
1422 </p>
1423 <hr />
1424 <a name="elf"></a><a name="all-ELF-targets-_0028SVR4_002c-Solaris_002c-etc_002e_0029"></a>
1425 <h3 class="heading">all ELF targets (SVR4, Solaris, etc.)</h3>
1426 <p>C++ support is significantly better on ELF targets if you use the
1427 <a href="./configure.html#with-gnu-ld">GNU linker</a>; duplicate copies of
1428 inlines, vtables and template instantiations will be discarded
1429 automatically.
1430 </p>
1431
1432 <hr />
1433 <p>
1434 <p><a href="./index.html">Return to the GCC Installation page</a>
1435 </p>
1436
1437
1438
1439
1440
1441 </body>
1442 </html>
1443