0
|
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.12">
|
|
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, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
|
|
11 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007,
|
|
12 2008 Free Software Foundation, Inc.
|
|
13
|
|
14 Permission is granted to copy, distribute and/or modify this document
|
|
15 under the terms of the GNU Free Documentation License, Version 1.2 or
|
|
16 any later version published by the Free Software Foundation; with no
|
|
17 Invariant Sections, the Front-Cover texts being (a) (see below), and
|
|
18 with the Back-Cover Texts being (b) (see below). A copy of the
|
|
19 license is included in the section entitled "GNU Free Documentation License".
|
|
20
|
|
21 (a) The FSF's Front-Cover Text is:
|
|
22
|
|
23 A GNU Manual
|
|
24
|
|
25 (b) The FSF's Back-Cover Text is:
|
|
26
|
|
27 You have freedom to copy and modify this GNU Manual, like GNU
|
|
28 software. Copies published by the Free Software Foundation raise
|
|
29 funds for GNU development.-->
|
|
30 <meta http-equiv="Content-Style-Type" content="text/css">
|
|
31 <style type="text/css"><!--
|
|
32 pre.display { font-family:inherit }
|
|
33 pre.format { font-family:inherit }
|
|
34 pre.smalldisplay { font-family:inherit; font-size:smaller }
|
|
35 pre.smallformat { font-family:inherit; font-size:smaller }
|
|
36 pre.smallexample { font-size:smaller }
|
|
37 pre.smalllisp { font-size:smaller }
|
|
38 span.sc { font-variant:small-caps }
|
|
39 span.roman { font-family:serif; font-weight:normal; }
|
|
40 span.sansserif { font-family:sans-serif; font-weight:normal; }
|
|
41 --></style>
|
|
42 </head>
|
|
43 <body>
|
|
44 <h1 class="settitle">Host/Target specific installation notes for GCC</h1>
|
|
45 <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>
|
|
46 Please read this document carefully <em>before</em> installing the
|
|
47 GNU Compiler Collection on your machine.
|
|
48
|
|
49 <p>Note that this list of install notes is <em>not</em> a list of supported
|
|
50 hosts or targets. Not all supported hosts and targets are listed
|
|
51 here, only the ones that require host-specific or target-specific
|
|
52 information are.
|
|
53
|
|
54 <ul>
|
|
55 <li><a href="#alpha-x-x">alpha*-*-*</a>
|
|
56 <li><a href="#alpha-dec-osf">alpha*-dec-osf*</a>
|
|
57 <li><a href="#arc-x-elf">arc-*-elf</a>
|
|
58 <li><a href="#arm-x-elf">arm-*-elf</a>
|
|
59 <a href="#arm-x-coff">arm-*-coff</a>
|
|
60 <a href="#arm-x-aout">arm-*-aout</a>
|
|
61 <li><a href="#avr">avr</a>
|
|
62 <li><a href="#bfin">Blackfin</a>
|
|
63 <li><a href="#dos">DOS</a>
|
|
64 <li><a href="#x-x-freebsd">*-*-freebsd*</a>
|
|
65 <li><a href="#h8300-hms">h8300-hms</a>
|
|
66 <li><a href="#hppa-hp-hpux">hppa*-hp-hpux*</a>
|
|
67 <li><a href="#hppa-hp-hpux10">hppa*-hp-hpux10</a>
|
|
68 <li><a href="#hppa-hp-hpux11">hppa*-hp-hpux11</a>
|
|
69 <li><a href="#x-x-linux-gnu">*-*-linux-gnu</a>
|
|
70 <li><a href="#ix86-x-linux">i?86-*-linux*</a>
|
|
71 <li><a href="#ix86-x-solaris210">i?86-*-solaris2.10</a>
|
|
72 <li><a href="#ia64-x-linux">ia64-*-linux</a>
|
|
73 <li><a href="#ia64-x-hpux">ia64-*-hpux*</a>
|
|
74 <li><a href="#x-ibm-aix">*-ibm-aix*</a>
|
|
75 <li><a href="#iq2000-x-elf">iq2000-*-elf</a>
|
|
76 <li><a href="#m32c-x-elf">m32c-*-elf</a>
|
|
77 <li><a href="#m32r-x-elf">m32r-*-elf</a>
|
|
78 <li><a href="#m6811-elf">m6811-elf</a>
|
|
79 <li><a href="#m6812-elf">m6812-elf</a>
|
|
80 <li><a href="#m68k-x-x">m68k-*-*</a>
|
|
81 <li><a href="#m68k-uclinux">m68k-uclinux</a>
|
|
82 <li><a href="#mips-x-x">mips-*-*</a>
|
|
83 <li><a href="#mips-sgi-irix5">mips-sgi-irix5</a>
|
|
84 <li><a href="#mips-sgi-irix6">mips-sgi-irix6</a>
|
|
85 <li><a href="#powerpc-x-x">powerpc*-*-*</a>
|
|
86 <li><a href="#powerpc-x-darwin">powerpc-*-darwin*</a>
|
|
87 <li><a href="#powerpc-x-elf">powerpc-*-elf</a>
|
|
88 <li><a href="#powerpc-x-linux-gnu">powerpc*-*-linux-gnu*</a>
|
|
89 <li><a href="#powerpc-x-netbsd">powerpc-*-netbsd*</a>
|
|
90 <li><a href="#powerpc-x-eabisim">powerpc-*-eabisim</a>
|
|
91 <li><a href="#powerpc-x-eabi">powerpc-*-eabi</a>
|
|
92 <li><a href="#powerpcle-x-elf">powerpcle-*-elf</a>
|
|
93 <li><a href="#powerpcle-x-eabisim">powerpcle-*-eabisim</a>
|
|
94 <li><a href="#powerpcle-x-eabi">powerpcle-*-eabi</a>
|
|
95 <li><a href="#s390-x-linux">s390-*-linux*</a>
|
|
96 <li><a href="#s390x-x-linux">s390x-*-linux*</a>
|
|
97 <li><a href="#s390x-ibm-tpf">s390x-ibm-tpf*</a>
|
|
98 <li><a href="#x-x-solaris2">*-*-solaris2*</a>
|
|
99 <li><a href="#sparc-sun-solaris2">sparc-sun-solaris2*</a>
|
|
100 <li><a href="#sparc-sun-solaris27">sparc-sun-solaris2.7</a>
|
|
101 <li><a href="#sparc-x-linux">sparc-*-linux*</a>
|
|
102 <li><a href="#sparc64-x-solaris2">sparc64-*-solaris2*</a>
|
|
103 <li><a href="#sparcv9-x-solaris2">sparcv9-*-solaris2*</a>
|
|
104 <li><a href="#x-x-vxworks">*-*-vxworks*</a>
|
|
105 <li><a href="#x86-64-x-x">x86_64-*-*</a> amd64-*-*
|
|
106 <li><a href="#xtensa-x-elf">xtensa*-*-elf</a>
|
|
107 <li><a href="#xtensa-x-linux">xtensa*-*-linux*</a>
|
|
108 <li><a href="#windows">Microsoft Windows</a>
|
|
109 <li><a href="#x-x-cygwin">*-*-cygwin</a>
|
|
110 <li><a href="#x-x-interix">*-*-interix</a>
|
|
111 <li><a href="#x-x-mingw">*-*-mingw</a>
|
|
112 <li><a href="#os2">OS/2</a>
|
|
113 <li><a href="#older">Older systems</a>
|
|
114 </ul>
|
|
115
|
|
116 <ul>
|
|
117 <li><a href="#elf">all ELF targets</a> (SVR4, Solaris 2, etc.)
|
|
118 </ul>
|
|
119
|
|
120 <p><!-- -------- host/target specific issues start here ---------------- -->
|
|
121 <hr />
|
|
122
|
|
123 <h3 class="heading"><a name="TOC0"></a><a name="alpha_002dx_002dx"></a>alpha*-*-*</h3>
|
|
124
|
|
125 <p>This section contains general configuration information for all
|
|
126 alpha-based platforms using ELF (in particular, ignore this section for
|
|
127 DEC OSF/1, Digital UNIX and Tru64 UNIX). In addition to reading this
|
|
128 section, please read all other sections that match your target.
|
|
129
|
|
130 <p>We require binutils 2.11.2 or newer.
|
|
131 Previous binutils releases had a number of problems with DWARF 2
|
|
132 debugging information, not the least of which is incorrect linking of
|
|
133 shared libraries.
|
|
134
|
|
135 <p><hr />
|
|
136
|
|
137 <h3 class="heading"><a name="TOC1"></a><a name="alpha_002ddec_002dosf"></a>alpha*-dec-osf*</h3>
|
|
138
|
|
139 <p>Systems using processors that implement the DEC Alpha architecture and
|
|
140 are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq
|
|
141 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
|
|
142
|
|
143 <p>As of GCC 3.2, versions before <code>alpha*-dec-osf4</code> are no longer
|
|
144 supported. (These are the versions which identify themselves as DEC
|
|
145 OSF/1.)
|
|
146
|
|
147 <p>In Digital Unix V4.0, virtual memory exhausted bootstrap failures
|
|
148 may be fixed by configuring with <samp><span class="option">--with-gc=simple</span></samp>,
|
|
149 reconfiguring Kernel Virtual Memory and Swap parameters
|
|
150 per the <samp><span class="command">/usr/sbin/sys_check</span></samp> Tuning Suggestions,
|
|
151 or applying the patch in
|
|
152 <a href="http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html">http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html</a>.
|
|
153
|
|
154 <p>In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
|
|
155 currently (2001-06-13) work with <samp><span class="command">mips-tfile</span></samp>. As a workaround,
|
|
156 we need to use the old assembler, invoked via the barely documented
|
|
157 <samp><span class="option">-oldas</span></samp> option. To bootstrap GCC, you either need to use the
|
|
158 Compaq C Compiler:
|
|
159
|
|
160 <pre class="smallexample"> % CC=cc <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>]
|
|
161 </pre>
|
|
162 <p>or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
|
|
163
|
|
164 <pre class="smallexample"> % CC=gcc -Wa,-oldas <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>]
|
|
165 </pre>
|
|
166 <p>As of GNU binutils 2.11.2, neither GNU <samp><span class="command">as</span></samp> nor GNU <samp><span class="command">ld</span></samp>
|
|
167 are supported on Tru64 UNIX, so you must not configure GCC with
|
|
168 <samp><span class="option">--with-gnu-as</span></samp> or <samp><span class="option">--with-gnu-ld</span></samp>.
|
|
169
|
|
170 <p>GCC writes a ‘<samp><span class="samp">.verstamp</span></samp>’ directive to the assembler output file
|
|
171 unless it is built as a cross-compiler. It gets the version to use from
|
|
172 the system header file <samp><span class="file">/usr/include/stamp.h</span></samp>. If you install a
|
|
173 new version of DEC Unix, you should rebuild GCC to pick up the new version
|
|
174 stamp.
|
|
175
|
|
176 <p>‘<samp><span class="samp">make compare</span></samp>’ may fail on old versions of DEC Unix unless you add
|
|
177 <samp><span class="option">-save-temps</span></samp> to <code>BOOT_CFLAGS</code>. On these systems, the name
|
|
178 of the assembler input file is stored in the object file, and that makes
|
|
179 comparison fail if it differs between the <code>stage1</code> and
|
|
180 <code>stage2</code> compilations. The option <samp><span class="option">-save-temps</span></samp> forces a
|
|
181 fixed name to be used for the assembler input file, instead of a
|
|
182 randomly chosen name in <samp><span class="file">/tmp</span></samp>. Do not add <samp><span class="option">-save-temps</span></samp>
|
|
183 unless the comparisons fail without that option. If you add
|
|
184 <samp><span class="option">-save-temps</span></samp>, you will have to manually delete the ‘<samp><span class="samp">.i</span></samp>’ and
|
|
185 ‘<samp><span class="samp">.s</span></samp>’ files after each series of compilations.
|
|
186
|
|
187 <p>GCC now supports both the native (ECOFF) debugging format used by DBX
|
|
188 and GDB and an encapsulated STABS format for use only with GDB. See the
|
|
189 discussion of the <samp><span class="option">--with-stabs</span></samp> option of <samp><span class="file">configure</span></samp> above
|
|
190 for more information on these formats and how to select them.
|
|
191
|
|
192 <p>There is a bug in DEC's assembler that produces incorrect line numbers
|
|
193 for ECOFF format when the ‘<samp><span class="samp">.align</span></samp>’ directive is used. To work
|
|
194 around this problem, GCC will not emit such alignment directives
|
|
195 while writing ECOFF format debugging information even if optimization is
|
|
196 being performed. Unfortunately, this has the very undesirable
|
|
197 side-effect that code addresses when <samp><span class="option">-O</span></samp> is specified are
|
|
198 different depending on whether or not <samp><span class="option">-g</span></samp> is also specified.
|
|
199
|
|
200 <p>To avoid this behavior, specify <samp><span class="option">-gstabs+</span></samp> and use GDB instead of
|
|
201 DBX. DEC is now aware of this problem with the assembler and hopes to
|
|
202 provide a fix shortly.
|
|
203
|
|
204 <p><hr />
|
|
205
|
|
206 <h3 class="heading"><a name="TOC2"></a><a name="arc_002dx_002delf"></a>arc-*-elf</h3>
|
|
207
|
|
208 <p>Argonaut ARC processor.
|
|
209 This configuration is intended for embedded systems.
|
|
210
|
|
211 <p><hr />
|
|
212
|
|
213 <h3 class="heading"><a name="TOC3"></a><a name="arm_002dx_002delf"></a>arm-*-elf</h3>
|
|
214
|
|
215 <p>ARM-family processors. Subtargets that use the ELF object format
|
|
216 require GNU binutils 2.13 or newer. Such subtargets include:
|
|
217 <code>arm-*-freebsd</code>, <code>arm-*-netbsdelf</code>, <code>arm-*-*linux</code>
|
|
218 and <code>arm-*-rtems</code>.
|
|
219
|
|
220 <p><hr />
|
|
221
|
|
222 <h3 class="heading"><a name="TOC4"></a><a name="arm_002dx_002dcoff"></a>arm-*-coff</h3>
|
|
223
|
|
224 <p>ARM-family processors. Note that there are two different varieties
|
|
225 of PE format subtarget supported: <code>arm-wince-pe</code> and
|
|
226 <code>arm-pe</code> as well as a standard COFF target <code>arm-*-coff</code>.
|
|
227
|
|
228 <p><hr />
|
|
229
|
|
230 <h3 class="heading"><a name="TOC5"></a><a name="arm_002dx_002daout"></a>arm-*-aout</h3>
|
|
231
|
|
232 <p>ARM-family processors. These targets support the AOUT file format:
|
|
233 <code>arm-*-aout</code>, <code>arm-*-netbsd</code>.
|
|
234
|
|
235 <p><hr />
|
|
236
|
|
237 <h3 class="heading"><a name="TOC6"></a><a name="avr"></a>avr</h3>
|
|
238
|
|
239 <p>ATMEL AVR-family micro controllers. These are used in embedded
|
|
240 applications. There are no standard Unix configurations.
|
|
241 See “AVR Options” in the main manual
|
|
242 for the list of supported MCU types.
|
|
243
|
|
244 <p>Use ‘<samp><span class="samp">configure --target=avr --enable-languages="c"</span></samp>’ to configure GCC.
|
|
245
|
|
246 <p>Further installation notes and other useful information about AVR tools
|
|
247 can also be obtained from:
|
|
248
|
|
249 <ul>
|
|
250 <li><a href="http://www.nongnu.org/avr/">http://www.nongnu.org/avr/</a>
|
|
251 <li><a href="http://home.overta.ru/users/denisc/">http://home.overta.ru/users/denisc/</a>
|
|
252 <li><a href="http://www.amelek.gda.pl/avr/">http://www.amelek.gda.pl/avr/</a>
|
|
253 </ul>
|
|
254
|
|
255 <p>We <em>strongly</em> recommend using binutils 2.13 or newer.
|
|
256
|
|
257 <p>The following error:
|
|
258 <pre class="smallexample"> Error: register required
|
|
259 </pre>
|
|
260 <p>indicates that you should upgrade to a newer version of the binutils.
|
|
261
|
|
262 <p><hr />
|
|
263
|
|
264 <h3 class="heading"><a name="TOC7"></a><a name="bfin"></a>Blackfin</h3>
|
|
265
|
|
266 <p>The Blackfin processor, an Analog Devices DSP.
|
|
267 See “Blackfin Options” in the main manual
|
|
268
|
|
269 <p>More information, and a version of binutils with support for this processor,
|
|
270 is available at <a href="http://blackfin.uclinux.org">http://blackfin.uclinux.org</a>
|
|
271
|
|
272 <p><hr />
|
|
273
|
|
274 <h3 class="heading"><a name="TOC8"></a><a name="cris"></a>CRIS</h3>
|
|
275
|
|
276 <p>CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
|
|
277 series. These are used in embedded applications.
|
|
278
|
|
279 <p>See “CRIS Options” in the main manual
|
|
280 for a list of CRIS-specific options.
|
|
281
|
|
282 <p>There are a few different CRIS targets:
|
|
283 <dl>
|
|
284 <dt><code>cris-axis-elf</code><dd>Mainly for monolithic embedded systems. Includes a multilib for the
|
|
285 ‘<samp><span class="samp">v10</span></samp>’ core used in ‘<samp><span class="samp">ETRAX 100 LX</span></samp>’.
|
|
286 <br><dt><code>cris-axis-linux-gnu</code><dd>A GNU/Linux port for the CRIS architecture, currently targeting
|
|
287 ‘<samp><span class="samp">ETRAX 100 LX</span></samp>’ by default.
|
|
288 </dl>
|
|
289
|
|
290 <p>For <code>cris-axis-elf</code> you need binutils 2.11
|
|
291 or newer. For <code>cris-axis-linux-gnu</code> you need binutils 2.12 or newer.
|
|
292
|
|
293 <p>Pre-packaged tools can be obtained from
|
|
294 <a href="ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/">ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/</a>. More
|
|
295 information about this platform is available at
|
|
296 <a href="http://developer.axis.com/">http://developer.axis.com/</a>.
|
|
297
|
|
298 <p><hr />
|
|
299
|
|
300 <h3 class="heading"><a name="TOC9"></a><a name="crx"></a>CRX</h3>
|
|
301
|
|
302 <p>The CRX CompactRISC architecture is a low-power 32-bit architecture with
|
|
303 fast context switching and architectural extensibility features.
|
|
304
|
|
305 <p>See “CRX Options” in the main manual for a list of CRX-specific options.
|
|
306
|
|
307 <p>Use ‘<samp><span class="samp">configure --target=crx-elf --enable-languages=c,c++</span></samp>’ to configure
|
|
308 GCC for building a CRX cross-compiler. The option ‘<samp><span class="samp">--target=crx-elf</span></samp>’
|
|
309 is also used to build the ‘<samp><span class="samp">newlib</span></samp>’ C library for CRX.
|
|
310
|
|
311 <p>It is also possible to build libstdc++-v3 for the CRX architecture. This
|
|
312 needs to be done in a separate step with the following configure settings:
|
|
313 ‘<samp><span class="samp">gcc/libstdc++-v3/configure --host=crx-elf --with-newlib
|
|
314 --enable-sjlj-exceptions --enable-cxx-flags='-fexceptions -frtti'</span></samp>’
|
|
315
|
|
316 <p><hr />
|
|
317
|
|
318 <h3 class="heading"><a name="TOC10"></a><a name="dos"></a>DOS</h3>
|
|
319
|
|
320 <p>Please have a look at the <a href="binaries.html">binaries page</a>.
|
|
321
|
|
322 <p>You cannot install GCC by itself on MSDOS; it will not compile under
|
|
323 any MSDOS compiler except itself. You need to get the complete
|
|
324 compilation package DJGPP, which includes binaries as well as sources,
|
|
325 and includes all the necessary compilation tools and libraries.
|
|
326
|
|
327 <p><hr />
|
|
328
|
|
329 <h3 class="heading"><a name="TOC11"></a><a name="x_002dx_002dfreebsd"></a>*-*-freebsd*</h3>
|
|
330
|
|
331 <p>The version of binutils installed in <samp><span class="file">/usr/bin</span></samp> probably works with
|
|
332 this release of GCC. However, on FreeBSD 4, bootstrapping against the
|
|
333 latest FSF binutils is known to improve overall testsuite results; and,
|
|
334 on FreeBSD/alpha, using binutils 2.14 or later is required to build libjava.
|
|
335
|
|
336 <p>Support for FreeBSD 1 was discontinued in GCC 3.2.
|
|
337
|
|
338 <p>Support for FreeBSD 2 will be discontinued after GCC 3.4. The
|
|
339 following was true for GCC 3.1 but the current status is unknown.
|
|
340 For FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
|
|
341 configuration support and files as shipped with GCC 2.95 are still in
|
|
342 place. FreeBSD 2.2.7 has been known to bootstrap completely; however,
|
|
343 it is unknown which version of binutils was used (it is assumed that it
|
|
344 was the system copy in <samp><span class="file">/usr/bin</span></samp>) and C++ EH failures were noted.
|
|
345
|
|
346 <p>For FreeBSD using the ELF file format: DWARF 2 debugging is now the
|
|
347 default for all CPU architectures. It had been the default on
|
|
348 FreeBSD/alpha since its inception. You may use <samp><span class="option">-gstabs</span></samp> instead
|
|
349 of <samp><span class="option">-g</span></samp>, if you really want the old debugging format. There are
|
|
350 no known issues with mixing object files and libraries with different
|
|
351 debugging formats. Otherwise, this release of GCC should now match more
|
|
352 of the configuration used in the stock FreeBSD configuration of GCC. In
|
|
353 particular, <samp><span class="option">--enable-threads</span></samp> is now configured by default.
|
|
354 However, as a general user, do not attempt to replace the system
|
|
355 compiler with this release. Known to bootstrap and check with good
|
|
356 results on FreeBSD 4.9-STABLE and 5-CURRENT. In the past, known to
|
|
357 bootstrap and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2,
|
|
358 4.3, 4.4, 4.5, 4.8-STABLE.
|
|
359
|
|
360 <p>In principle, <samp><span class="option">--enable-threads</span></samp> is now compatible with
|
|
361 <samp><span class="option">--enable-libgcj</span></samp> on FreeBSD. However, it has only been built
|
|
362 and tested on ‘<samp><span class="samp">i386-*-freebsd[45]</span></samp>’ and ‘<samp><span class="samp">alpha-*-freebsd[45]</span></samp>’.
|
|
363 The static
|
|
364 library may be incorrectly built (symbols are missing at link time).
|
|
365 There is a rare timing-based startup hang (probably involves an
|
|
366 assumption about the thread library). Multi-threaded boehm-gc (required for
|
|
367 libjava) exposes severe threaded signal-handling bugs on FreeBSD before
|
|
368 4.5-RELEASE. Other CPU architectures
|
|
369 supported by FreeBSD will require additional configuration tuning in, at
|
|
370 the very least, both boehm-gc and libffi.
|
|
371
|
|
372 <p>Shared <samp><span class="file">libgcc_s.so</span></samp> is now built and installed by default.
|
|
373
|
|
374 <p><hr />
|
|
375
|
|
376 <h3 class="heading"><a name="TOC12"></a><a name="h8300_002dhms"></a>h8300-hms</h3>
|
|
377
|
|
378 <p>Renesas H8/300 series of processors.
|
|
379
|
|
380 <p>Please have a look at the <a href="binaries.html">binaries page</a>.
|
|
381
|
|
382 <p>The calling convention and structure layout has changed in release 2.6.
|
|
383 All code must be recompiled. The calling convention now passes the
|
|
384 first three arguments in function calls in registers. Structures are no
|
|
385 longer a multiple of 2 bytes.
|
|
386
|
|
387 <p><hr />
|
|
388
|
|
389 <h3 class="heading"><a name="TOC13"></a><a name="hppa_002dhp_002dhpux"></a>hppa*-hp-hpux*</h3>
|
|
390
|
|
391 <p>Support for HP-UX version 9 and older was discontinued in GCC 3.4.
|
|
392
|
|
393 <p>We require using gas/binutils on all hppa platforms. Version 2.19 or
|
|
394 later is recommended.
|
|
395
|
|
396 <p>It may be helpful to configure GCC with the
|
|
397 <a href="./configure.html#with-gnu-as"><samp><span class="option">--with-gnu-as</span></samp></a> and
|
|
398 <samp><span class="option">--with-as=...</span></samp> options to ensure that GCC can find GAS.
|
|
399
|
|
400 <p>The HP assembler should not be used with GCC. It is rarely tested and may
|
|
401 not work. It shouldn't be used with any languages other than C due to its
|
|
402 many limitations.
|
|
403
|
|
404 <p>Specifically, <samp><span class="option">-g</span></samp> does not work (HP-UX uses a peculiar debugging
|
|
405 format which GCC does not know about). It also inserts timestamps
|
|
406 into each object file it creates, causing the 3-stage comparison test to
|
|
407 fail during a bootstrap. You should be able to continue by saying
|
|
408 ‘<samp><span class="samp">make all-host all-target</span></samp>’ after getting the failure from ‘<samp><span class="samp">make</span></samp>’.
|
|
409
|
|
410 <p>Various GCC features are not supported. For example, it does not support weak
|
|
411 symbols or alias definitions. As a result, explicit template instantiations
|
|
412 are required when using C++. This makes it difficult if not impossible to
|
|
413 build many C++ applications.
|
|
414
|
|
415 <p>There are two default scheduling models for instructions. These are
|
|
416 PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
|
|
417 architecture specified for the target machine when configuring.
|
|
418 PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
|
|
419 the target is a ‘<samp><span class="samp">hppa1*</span></samp>’ machine.
|
|
420
|
|
421 <p>The PROCESSOR_8000 model is not well suited to older processors. Thus,
|
|
422 it is important to completely specify the machine architecture when
|
|
423 configuring if you want a model other than PROCESSOR_8000. The macro
|
|
424 TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
|
|
425 default scheduling model is desired.
|
|
426
|
|
427 <p>As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10
|
|
428 through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later.
|
|
429 This namespace change might cause problems when bootstrapping with
|
|
430 an earlier version of GCC or the HP compiler as essentially the same
|
|
431 namespace is required for an entire build. This problem can be avoided
|
|
432 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>’
|
|
433 or ‘<samp><span class="samp">98</span></samp>’. Another way is to add an appropriate set of predefines
|
|
434 to <samp><span class="env">CC</span></samp>. The description for the <samp><span class="option">munix=</span></samp> option contains
|
|
435 a list of the predefines used with each standard.
|
|
436
|
|
437 <p>More specific information to ‘<samp><span class="samp">hppa*-hp-hpux*</span></samp>’ targets follows.
|
|
438
|
|
439 <p><hr />
|
|
440
|
|
441 <h3 class="heading"><a name="TOC14"></a><a name="hppa_002dhp_002dhpux10"></a>hppa*-hp-hpux10</h3>
|
|
442
|
|
443 <p>For hpux10.20, we <em>highly</em> recommend you pick up the latest sed patch
|
|
444 <code>PHCO_19798</code> from HP. HP has two sites which provide patches free of
|
|
445 charge:
|
|
446
|
|
447 <ul>
|
|
448 <li><a href="http://us.itrc.hp.com/service/home/home.do">US, Canada, Asia-Pacific, and
|
|
449 Latin-America</a><li><a href="http://europe.itrc.hp.com/service/home/home.do">http://europe.itrc.hp.com/service/home/home.do</a> Europe.
|
|
450 </ul>
|
|
451
|
|
452 <p>The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces are
|
|
453 used for one-only code and data. This resolves many of the previous
|
|
454 problems in using C++ on this target. However, the ABI is not compatible
|
|
455 with the one implemented under HP-UX 11 using secondary definitions.
|
|
456
|
|
457 <p><hr />
|
|
458
|
|
459 <h3 class="heading"><a name="TOC15"></a><a name="hppa_002dhp_002dhpux11"></a>hppa*-hp-hpux11</h3>
|
|
460
|
|
461 <p>GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot
|
|
462 be used to compile GCC 3.0 and up.
|
|
463
|
|
464 <p>The libffi and libjava libraries haven't been ported to 64-bit HP-UX and don't build.
|
|
465
|
|
466 <p>Refer to <a href="binaries.html">binaries</a> for information about obtaining
|
|
467 precompiled GCC binaries for HP-UX. Precompiled binaries must be obtained
|
|
468 to build the Ada language as it can't be bootstrapped using C. Ada is
|
|
469 only available for the 32-bit PA-RISC runtime.
|
|
470
|
|
471 <p>Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The
|
|
472 bundled compiler supports only traditional C; you will need either HP's
|
|
473 unbundled compiler, or a binary distribution of GCC.
|
|
474
|
|
475 <p>It is possible to build GCC 3.3 starting with the bundled HP compiler,
|
|
476 but the process requires several steps. GCC 3.3 can then be used to
|
|
477 build later versions. The fastjar program contains ISO C code and
|
|
478 can't be built with the HP bundled compiler. This problem can be
|
|
479 avoided by not building the Java language. For example, use the
|
|
480 <samp><span class="option">--enable-languages="c,c++,f77,objc"</span></samp> option in your configure
|
|
481 command.
|
|
482
|
|
483 <p>There are several possible approaches to building the distribution.
|
|
484 Binutils can be built first using the HP tools. Then, the GCC
|
|
485 distribution can be built. The second approach is to build GCC
|
|
486 first using the HP tools, then build binutils, then rebuild GCC.
|
|
487 There have been problems with various binary distributions, so it
|
|
488 is best not to start from a binary distribution.
|
|
489
|
|
490 <p>On 64-bit capable systems, there are two distinct targets. Different
|
|
491 installation prefixes must be used if both are to be installed on
|
|
492 the same system. The ‘<samp><span class="samp">hppa[1-2]*-hp-hpux11*</span></samp>’ target generates code
|
|
493 for the 32-bit PA-RISC runtime architecture and uses the HP linker.
|
|
494 The ‘<samp><span class="samp">hppa64-hp-hpux11*</span></samp>’ target generates 64-bit code for the
|
|
495 PA-RISC 2.0 architecture.
|
|
496
|
|
497 <p>The script config.guess now selects the target type based on the compiler
|
|
498 detected during configuration. You must define <samp><span class="env">PATH</span></samp> or <samp><span class="env">CC</span></samp> so
|
|
499 that configure finds an appropriate compiler for the initial bootstrap.
|
|
500 When <samp><span class="env">CC</span></samp> is used, the definition should contain the options that are
|
|
501 needed whenever <samp><span class="env">CC</span></samp> is used.
|
|
502
|
|
503 <p>Specifically, options that determine the runtime architecture must be
|
|
504 in <samp><span class="env">CC</span></samp> to correctly select the target for the build. It is also
|
|
505 convenient to place many other compiler options in <samp><span class="env">CC</span></samp>. For example,
|
|
506 <samp><span class="env">CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"</span></samp>
|
|
507 can be used to bootstrap the GCC 3.3 branch with the HP compiler in
|
|
508 64-bit K&R/bundled mode. The <samp><span class="option">+DA2.0W</span></samp> option will result in
|
|
509 the automatic selection of the ‘<samp><span class="samp">hppa64-hp-hpux11*</span></samp>’ target. The
|
|
510 macro definition table of cpp needs to be increased for a successful
|
|
511 build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to
|
|
512 be defined when building with the bundled compiler, or when using the
|
|
513 <samp><span class="option">-Ac</span></samp> option. These defines aren't necessary with <samp><span class="option">-Ae</span></samp>.
|
|
514
|
|
515 <p>It is best to explicitly configure the ‘<samp><span class="samp">hppa64-hp-hpux11*</span></samp>’ target
|
|
516 with the <samp><span class="option">--with-ld=...</span></samp> option. This overrides the standard
|
|
517 search for ld. The two linkers supported on this target require different
|
|
518 commands. The default linker is determined during configuration. As a
|
|
519 result, it's not possible to switch linkers in the middle of a GCC build.
|
|
520 This has been reported to sometimes occur in unified builds of binutils
|
|
521 and GCC.
|
|
522
|
|
523 <p>A recent linker patch must be installed for the correct operation of
|
|
524 GCC 3.3 and later. <code>PHSS_26559</code> and <code>PHSS_24304</code> are the
|
|
525 oldest linker patches that are known to work. They are for HP-UX
|
|
526 11.00 and 11.11, respectively. <code>PHSS_24303</code>, the companion to
|
|
527 <code>PHSS_24304</code>, might be usable but it hasn't been tested. These
|
|
528 patches have been superseded. Consult the HP patch database to obtain
|
|
529 the currently recommended linker patch for your system.
|
|
530
|
|
531 <p>The patches are necessary for the support of weak symbols on the
|
|
532 32-bit port, and for the running of initializers and finalizers. Weak
|
|
533 symbols are implemented using SOM secondary definition symbols. Prior
|
|
534 to HP-UX 11, there are bugs in the linker support for secondary symbols.
|
|
535 The patches correct a problem of linker core dumps creating shared
|
|
536 libraries containing secondary symbols, as well as various other
|
|
537 linking issues involving secondary symbols.
|
|
538
|
|
539 <p>GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
|
|
540 run initializers and finalizers on the 64-bit port. The 32-bit port
|
|
541 uses the linker <samp><span class="option">+init</span></samp> and <samp><span class="option">+fini</span></samp> options for the same
|
|
542 purpose. The patches correct various problems with the +init/+fini
|
|
543 options, including program core dumps. Binutils 2.14 corrects a
|
|
544 problem on the 64-bit port resulting from HP's non-standard use of
|
|
545 the .init and .fini sections for array initializers and finalizers.
|
|
546
|
|
547 <p>Although the HP and GNU linkers are both supported for the
|
|
548 ‘<samp><span class="samp">hppa64-hp-hpux11*</span></samp>’ target, it is strongly recommended that the
|
|
549 HP linker be used for link editing on this target.
|
|
550
|
|
551 <p>At this time, the GNU linker does not support the creation of long
|
|
552 branch stubs. As a result, it can't successfully link binaries
|
|
553 containing branch offsets larger than 8 megabytes. In addition,
|
|
554 there are problems linking shared libraries, linking executables
|
|
555 with <samp><span class="option">-static</span></samp>, and with dwarf2 unwind and exception support.
|
|
556 It also doesn't provide stubs for internal calls to global functions
|
|
557 in shared libraries, so these calls can't be overloaded.
|
|
558
|
|
559 <p>The HP dynamic loader does not support GNU symbol versioning, so symbol
|
|
560 versioning is not supported. It may be necessary to disable symbol
|
|
561 versioning with <samp><span class="option">--disable-symvers</span></samp> when using GNU ld.
|
|
562
|
|
563 <p>POSIX threads are the default. The optional DCE thread library is not
|
|
564 supported, so <samp><span class="option">--enable-threads=dce</span></samp> does not work.
|
|
565
|
|
566 <p><hr />
|
|
567
|
|
568 <h3 class="heading"><a name="TOC16"></a><a name="x_002dx_002dlinux_002dgnu"></a>*-*-linux-gnu</h3>
|
|
569
|
|
570 <p>Versions of libstdc++-v3 starting with 3.2.1 require bug fixes present
|
|
571 in glibc 2.2.5 and later. More information is available in the
|
|
572 libstdc++-v3 documentation.
|
|
573
|
|
574 <p><hr />
|
|
575
|
|
576 <h3 class="heading"><a name="TOC17"></a><a name="ix86_002dx_002dlinux"></a>i?86-*-linux*</h3>
|
|
577
|
|
578 <p>As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
|
|
579 See <a href="http://gcc.gnu.org/PR10877">bug 10877</a> for more information.
|
|
580
|
|
581 <p>If you receive Signal 11 errors when building on GNU/Linux, then it is
|
|
582 possible you have a hardware problem. Further information on this can be
|
|
583 found on <a href="http://www.bitwizard.nl/sig11/">www.bitwizard.nl</a>.
|
|
584
|
|
585 <p><hr />
|
|
586
|
|
587 <h3 class="heading"><a name="TOC18"></a><a name="ix86_002dx_002dsolaris210"></a>i?86-*-solaris2.10</h3>
|
|
588
|
|
589 <p>Use this for Solaris 10 or later on x86 and x86-64 systems. This
|
|
590 configuration is supported by GCC 4.0 and later versions only.
|
|
591
|
|
592 <p>It is recommended that you configure GCC to use the GNU assembler in
|
|
593 <samp><span class="file">/usr/sfw/bin/gas</span></samp> but the Sun linker, using the options
|
|
594 <samp><span class="option">--with-gnu-as --with-as=/usr/sfw/bin/gas --without-gnu-ld
|
|
595 --with-ld=/usr/ccs/bin/ld</span></samp>.
|
|
596
|
|
597 <p><hr />
|
|
598
|
|
599 <h3 class="heading"><a name="TOC19"></a><a name="ia64_002dx_002dlinux"></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 />
|
|
618
|
|
619 <h3 class="heading"><a name="TOC20"></a><a name="ia64_002dx_002dhpux"></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* -->
|
|
633
|
|
634 <h3 class="heading"><a name="TOC21"></a><a name="x_002dibm_002daix"></a>*-ibm-aix*</h3>
|
|
635
|
|
636 <p>Support for AIX version 3 and older was discontinued in GCC 3.4.
|
|
637
|
|
638 <p>“out of memory” bootstrap failures may indicate a problem with
|
|
639 process resource limits (ulimit). Hard limits are configured in the
|
|
640 <samp><span class="file">/etc/security/limits</span></samp> system configuration file.
|
|
641
|
|
642 <p>To speed up the configuration phases of bootstrapping and installing GCC,
|
|
643 one may use GNU Bash instead of AIX <samp><span class="command">/bin/sh</span></samp>, e.g.,
|
|
644
|
|
645 <pre class="smallexample"> % CONFIG_SHELL=/opt/freeware/bin/bash
|
|
646 % export CONFIG_SHELL
|
|
647 </pre>
|
|
648 <p>and then proceed as described in <a href="build.html">the build instructions</a>, where we strongly recommend specifying an absolute path
|
|
649 to invoke <var>srcdir</var>/configure.
|
|
650
|
|
651 <p>Because GCC on AIX is built as a 32-bit executable by default,
|
|
652 (although it can generate 64-bit programs) the GMP and MPFR libraries
|
|
653 required by gfortran must be 32-bit libraries. Building GMP and MPFR
|
|
654 as static archive libraries works better than shared libraries.
|
|
655
|
|
656 <p>Errors involving <code>alloca</code> when building GCC generally are due
|
|
657 to an incorrect definition of <code>CC</code> in the Makefile or mixing files
|
|
658 compiled with the native C compiler and GCC. During the stage1 phase of
|
|
659 the build, the native AIX compiler <strong>must</strong> be invoked as <samp><span class="command">cc</span></samp>
|
|
660 (not <samp><span class="command">xlc</span></samp>). Once <samp><span class="command">configure</span></samp> has been informed of
|
|
661 <samp><span class="command">xlc</span></samp>, one needs to use ‘<samp><span class="samp">make distclean</span></samp>’ to remove the
|
|
662 configure cache files and ensure that <samp><span class="env">CC</span></samp> environment variable
|
|
663 does not provide a definition that will confuse <samp><span class="command">configure</span></samp>.
|
|
664 If this error occurs during stage2 or later, then the problem most likely
|
|
665 is the version of Make (see above).
|
|
666
|
|
667 <p>The native <samp><span class="command">as</span></samp> and <samp><span class="command">ld</span></samp> are recommended for bootstrapping
|
|
668 on AIX 4 and required for bootstrapping on AIX 5L. The GNU Assembler
|
|
669 reports that it supports WEAK symbols on AIX 4, which causes GCC to try to
|
|
670 utilize weak symbol functionality although it is not supported. The GNU
|
|
671 Assembler and Linker do not support AIX 5L sufficiently to bootstrap GCC.
|
|
672 The native AIX tools do interoperate with GCC.
|
|
673
|
|
674 <p>Building <samp><span class="file">libstdc++.a</span></samp> requires a fix for an AIX Assembler bug
|
|
675 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a
|
|
676 fix for another AIX Assembler bug and a co-dependent AIX Archiver fix
|
|
677 referenced as APAR IY53606 (AIX 5.2) or a APAR IY54774 (AIX 5.1)
|
|
678
|
|
679 <p>‘<samp><span class="samp">libstdc++</span></samp>’ in GCC 3.4 increments the major version number of the
|
|
680 shared object and GCC installation places the <samp><span class="file">libstdc++.a</span></samp>
|
|
681 shared library in a common location which will overwrite the and GCC
|
|
682 3.3 version of the shared library. Applications either need to be
|
|
683 re-linked against the new shared library or the GCC 3.1 and GCC 3.3
|
|
684 versions of the ‘<samp><span class="samp">libstdc++</span></samp>’ shared object needs to be available
|
|
685 to the AIX runtime loader. The GCC 3.1 ‘<samp><span class="samp">libstdc++.so.4</span></samp>’, if
|
|
686 present, and GCC 3.3 ‘<samp><span class="samp">libstdc++.so.5</span></samp>’ shared objects can be
|
|
687 installed for runtime dynamic loading using the following steps to set
|
|
688 the ‘<samp><span class="samp">F_LOADONLY</span></samp>’ flag in the shared object for <em>each</em>
|
|
689 multilib <samp><span class="file">libstdc++.a</span></samp> installed:
|
|
690
|
|
691 <p>Extract the shared objects from the currently installed
|
|
692 <samp><span class="file">libstdc++.a</span></samp> archive:
|
|
693 <pre class="smallexample"> % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
|
|
694 </pre>
|
|
695 <p>Enable the ‘<samp><span class="samp">F_LOADONLY</span></samp>’ flag so that the shared object will be
|
|
696 available for runtime dynamic loading, but not linking:
|
|
697 <pre class="smallexample"> % strip -e libstdc++.so.4 libstdc++.so.5
|
|
698 </pre>
|
|
699 <p>Archive the runtime-only shared object in the GCC 3.4
|
|
700 <samp><span class="file">libstdc++.a</span></samp> archive:
|
|
701 <pre class="smallexample"> % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
|
|
702 </pre>
|
|
703 <p>Linking executables and shared libraries may produce warnings of
|
|
704 duplicate symbols. The assembly files generated by GCC for AIX always
|
|
705 have included multiple symbol definitions for certain global variable
|
|
706 and function declarations in the original program. The warnings should
|
|
707 not prevent the linker from producing a correct library or runnable
|
|
708 executable.
|
|
709
|
|
710 <p>AIX 4.3 utilizes a “large format” archive to support both 32-bit and
|
|
711 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
|
|
712 to parse archive libraries did not handle the new format correctly.
|
|
713 These routines are used by GCC and result in error messages during
|
|
714 linking such as “not a COFF file”. The version of the routines shipped
|
|
715 with AIX 4.3.1 should work for a 32-bit environment. The <samp><span class="option">-g</span></samp>
|
|
716 option of the archive command may be used to create archives of 32-bit
|
|
717 objects using the original “small format”. A correct version of the
|
|
718 routines is shipped with AIX 4.3.2 and above.
|
|
719
|
|
720 <p>Some versions of the AIX binder (linker) can fail with a relocation
|
|
721 overflow severe error when the <samp><span class="option">-bbigtoc</span></samp> option is used to link
|
|
722 GCC-produced object files into an executable that overflows the TOC. A fix
|
|
723 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
|
|
724 available from IBM Customer Support and from its
|
|
725 <a href="http://techsupport.services.ibm.com/">techsupport.services.ibm.com</a>
|
|
726 website as PTF U455193.
|
|
727
|
|
728 <p>The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
|
|
729 with a segmentation fault when invoked by any version of GCC. A fix for
|
|
730 APAR IX87327 is available from IBM Customer Support and from its
|
|
731 <a href="http://techsupport.services.ibm.com/">techsupport.services.ibm.com</a>
|
|
732 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
|
|
733
|
|
734 <p>The initial assembler shipped with AIX 4.3.0 generates incorrect object
|
|
735 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
|
|
736 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
|
|
737 <a href="http://techsupport.services.ibm.com/">techsupport.services.ibm.com</a>
|
|
738 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
|
|
739
|
|
740 <p>AIX provides National Language Support (NLS). Compilers and assemblers
|
|
741 use NLS to support locale-specific representations of various data
|
|
742 formats including floating-point numbers (e.g., ‘<samp><span class="samp">.</span></samp>’ vs ‘<samp><span class="samp">,</span></samp>’ for
|
|
743 separating decimal fractions). There have been problems reported where
|
|
744 GCC does not produce the same floating-point formats that the assembler
|
|
745 expects. If one encounters this problem, set the <samp><span class="env">LANG</span></samp>
|
|
746 environment variable to ‘<samp><span class="samp">C</span></samp>’ or ‘<samp><span class="samp">En_US</span></samp>’.
|
|
747
|
|
748 <p>By default, GCC for AIX 4.1 and above produces code that can be used on
|
|
749 both Power or PowerPC processors.
|
|
750
|
|
751 <p>A default can be specified with the <samp><span class="option">-mcpu=</span><var>cpu_type</var></samp>
|
|
752 switch and using the configure option <samp><span class="option">--with-cpu-</span><var>cpu_type</var></samp>.
|
|
753
|
|
754 <p><hr />
|
|
755
|
|
756 <h3 class="heading"><a name="TOC22"></a><a name="iq2000_002dx_002delf"></a>iq2000-*-elf</h3>
|
|
757
|
|
758 <p>Vitesse IQ2000 processors. These are used in embedded
|
|
759 applications. There are no standard Unix configurations.
|
|
760
|
|
761 <p><hr />
|
|
762
|
|
763 <h3 class="heading"><a name="TOC23"></a><a name="m32c_002dx_002delf"></a>m32c-*-elf</h3>
|
|
764
|
|
765 <p>Renesas M32C processor.
|
|
766 This configuration is intended for embedded systems.
|
|
767
|
|
768 <p><hr />
|
|
769
|
|
770 <h3 class="heading"><a name="TOC24"></a><a name="m32r_002dx_002delf"></a>m32r-*-elf</h3>
|
|
771
|
|
772 <p>Renesas M32R processor.
|
|
773 This configuration is intended for embedded systems.
|
|
774
|
|
775 <p><hr />
|
|
776
|
|
777 <h3 class="heading"><a name="TOC25"></a><a name="m6811_002delf"></a>m6811-elf</h3>
|
|
778
|
|
779 <p>Motorola 68HC11 family micro controllers. These are used in embedded
|
|
780 applications. There are no standard Unix configurations.
|
|
781
|
|
782 <p><hr />
|
|
783
|
|
784 <h3 class="heading"><a name="TOC26"></a><a name="m6812_002delf"></a>m6812-elf</h3>
|
|
785
|
|
786 <p>Motorola 68HC12 family micro controllers. These are used in embedded
|
|
787 applications. There are no standard Unix configurations.
|
|
788
|
|
789 <p><hr />
|
|
790
|
|
791 <h3 class="heading"><a name="TOC27"></a><a name="m68k_002dx_002dx"></a>m68k-*-*</h3>
|
|
792
|
|
793 <p>By default, ‘<samp><span class="samp">m68k-*-aout</span></samp>’, ‘<samp><span class="samp">m68k-*-coff*</span></samp>’,
|
|
794 ‘<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
|
|
795 ‘<samp><span class="samp">m68k-*-linux</span></samp>’
|
|
796 build libraries for both M680x0 and ColdFire processors. If you only
|
|
797 need the M680x0 libraries, you can omit the ColdFire ones by passing
|
|
798 <samp><span class="option">--with-arch=m68k</span></samp> to <samp><span class="command">configure</span></samp>. Alternatively, you
|
|
799 can omit the M680x0 libraries by passing <samp><span class="option">--with-arch=cf</span></samp> to
|
|
800 <samp><span class="command">configure</span></samp>. These targets default to 5206 or 5475 code as
|
|
801 appropriate for the target system when
|
|
802 configured with <samp><span class="option">--with-arch=cf</span></samp> and 68020 code otherwise.
|
|
803
|
|
804 <p>The ‘<samp><span class="samp">m68k-*-netbsd</span></samp>’ and
|
|
805 ‘<samp><span class="samp">m68k-*-openbsd</span></samp>’ targets also support the <samp><span class="option">--with-arch</span></samp>
|
|
806 option. They will generate ColdFire CFV4e code when configured with
|
|
807 <samp><span class="option">--with-arch=cf</span></samp> and 68020 code otherwise.
|
|
808
|
|
809 <p>You can override the default processors listed above by configuring
|
|
810 with <samp><span class="option">--with-cpu=</span><var>target</var></samp>. This <var>target</var> can either
|
|
811 be a <samp><span class="option">-mcpu</span></samp> argument or one of the following values:
|
|
812 ‘<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>’,
|
|
813 ‘<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>’.
|
|
814
|
|
815 <p><hr />
|
|
816
|
|
817 <h3 class="heading"><a name="TOC28"></a><a name="m68k_002dx_002duclinux"></a>m68k-*-uclinux</h3>
|
|
818
|
|
819 <p>GCC 4.3 changed the uClinux configuration so that it uses the
|
|
820 ‘<samp><span class="samp">m68k-linux-gnu</span></samp>’ ABI rather than the ‘<samp><span class="samp">m68k-elf</span></samp>’ ABI.
|
|
821 It also added improved support for C++ and flat shared libraries,
|
|
822 both of which were ABI changes. However, you can still use the
|
|
823 original ABI by configuring for ‘<samp><span class="samp">m68k-uclinuxoldabi</span></samp>’ or
|
|
824 ‘<samp><span class="samp">m68k-</span><var>vendor</var><span class="samp">-uclinuxoldabi</span></samp>’.
|
|
825
|
|
826 <p><hr />
|
|
827
|
|
828 <h3 class="heading"><a name="TOC29"></a><a name="mips_002dx_002dx"></a>mips-*-*</h3>
|
|
829
|
|
830 <p>If on a MIPS system you get an error message saying “does not have gp
|
|
831 sections for all it's [sic] sectons [sic]”, don't worry about it. This
|
|
832 happens whenever you use GAS with the MIPS linker, but there is not
|
|
833 really anything wrong, and it is okay to use the output file. You can
|
|
834 stop such warnings by installing the GNU linker.
|
|
835
|
|
836 <p>It would be nice to extend GAS to produce the gp tables, but they are
|
|
837 optional, and there should not be a warning about their absence.
|
|
838
|
|
839 <p>The libstdc++ atomic locking routines for MIPS targets requires MIPS II
|
|
840 and later. A patch went in just after the GCC 3.3 release to
|
|
841 make ‘<samp><span class="samp">mips*-*-*</span></samp>’ use the generic implementation instead. You can also
|
|
842 configure for ‘<samp><span class="samp">mipsel-elf</span></samp>’ as a workaround. The
|
|
843 ‘<samp><span class="samp">mips*-*-linux*</span></samp>’ target continues to use the MIPS II routines. More
|
|
844 work on this is expected in future releases.
|
|
845
|
|
846 <!-- If you make -with-llsc the default for another target, please also -->
|
|
847 <!-- update the description of the -with-llsc option. -->
|
|
848 <p>The built-in <code>__sync_*</code> functions are available on MIPS II and
|
|
849 later systems and others that support the ‘<samp><span class="samp">ll</span></samp>’, ‘<samp><span class="samp">sc</span></samp>’ and
|
|
850 ‘<samp><span class="samp">sync</span></samp>’ instructions. This can be overridden by passing
|
|
851 <samp><span class="option">--with-llsc</span></samp> or <samp><span class="option">--without-llsc</span></samp> when configuring GCC.
|
|
852 Since the Linux kernel emulates these instructions if they are
|
|
853 missing, the default for ‘<samp><span class="samp">mips*-*-linux*</span></samp>’ targets is
|
|
854 <samp><span class="option">--with-llsc</span></samp>. The <samp><span class="option">--with-llsc</span></samp> and
|
|
855 <samp><span class="option">--without-llsc</span></samp> configure options may be overridden at compile
|
|
856 time by passing the <samp><span class="option">-mllsc</span></samp> or <samp><span class="option">-mno-llsc</span></samp> options to
|
|
857 the compiler.
|
|
858
|
|
859 <p>MIPS systems check for division by zero (unless
|
|
860 <samp><span class="option">-mno-check-zero-division</span></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><span class="option">--with-divide=breaks</span></samp>
|
|
866 <samp><span class="command">configure</span></samp> option when configuring GCC. The default is to
|
|
867 use traps on systems that support them.
|
|
868
|
|
869 <p>Cross-compilers for the MIPS as target using the MIPS assembler
|
|
870 currently do not work, because the auxiliary programs
|
|
871 <samp><span class="file">mips-tdump.c</span></samp> and <samp><span class="file">mips-tfile.c</span></samp> can't be compiled on
|
|
872 anything but a MIPS. It does work to cross compile for a MIPS
|
|
873 if you use the GNU assembler and linker.
|
|
874
|
|
875 <p>The assembler from GNU binutils 2.17 and earlier has a bug in the way
|
|
876 it sorts relocations for REL targets (o32, o64, EABI). This can cause
|
|
877 bad code to be generated for simple C++ programs. Also the linker
|
|
878 from GNU binutils versions prior to 2.17 has a bug which causes the
|
|
879 runtime linker stubs in very large programs, like <samp><span class="file">libgcj.so</span></samp>, to
|
|
880 be incorrectly generated. GNU Binutils 2.18 and later (and snapshots
|
|
881 made after Nov. 9, 2006) should be free from both of these problems.
|
|
882
|
|
883 <p><hr />
|
|
884
|
|
885 <h3 class="heading"><a name="TOC30"></a><a name="mips_002dsgi_002dirix5"></a>mips-sgi-irix5</h3>
|
|
886
|
|
887 <p>In order to compile GCC on an SGI running IRIX 5, the ‘<samp><span class="samp">compiler_dev.hdr</span></samp>’
|
|
888 subsystem must be installed from the IDO CD-ROM supplied by SGI.
|
|
889 It is also available for download from
|
|
890 <a href="ftp://ftp.sgi.com/sgi/IRIX5.3/iris-development-option-5.3.tardist">ftp://ftp.sgi.com/sgi/IRIX5.3/iris-development-option-5.3.tardist</a>.
|
|
891
|
|
892 <p>If you use the MIPS C compiler to bootstrap, it may be necessary
|
|
893 to increase its table size for switch statements with the
|
|
894 <samp><span class="option">-Wf,-XNg1500</span></samp> option. If you use the <samp><span class="option">-O2</span></samp>
|
|
895 optimization option, you also need to use <samp><span class="option">-Olimit 3000</span></samp>.
|
|
896
|
|
897 <p>To enable debugging under IRIX 5, you must use GNU binutils 2.15 or
|
|
898 later, and use the <samp><span class="option">--with-gnu-ld</span></samp> <samp><span class="command">configure</span></samp> option
|
|
899 when configuring GCC. You need to use GNU <samp><span class="command">ar</span></samp> and <samp><span class="command">nm</span></samp>,
|
|
900 also distributed with GNU binutils.
|
|
901
|
|
902 <p>Some users have reported that <samp><span class="command">/bin/sh</span></samp> will hang during bootstrap.
|
|
903 This problem can be avoided by running the commands:
|
|
904
|
|
905 <pre class="smallexample"> % CONFIG_SHELL=/bin/ksh
|
|
906 % export CONFIG_SHELL
|
|
907 </pre>
|
|
908 <p>before starting the build.
|
|
909
|
|
910 <p><hr />
|
|
911
|
|
912 <h3 class="heading"><a name="TOC31"></a><a name="mips_002dsgi_002dirix6"></a>mips-sgi-irix6</h3>
|
|
913
|
|
914 <p>If you are using SGI's MIPSpro <samp><span class="command">cc</span></samp> as your bootstrap compiler, you must
|
|
915 ensure that the N32 ABI is in use. To test this, compile a simple C
|
|
916 file with <samp><span class="command">cc</span></samp> and then run <samp><span class="command">file</span></samp> on the
|
|
917 resulting object file. The output should look like:
|
|
918
|
|
919 <pre class="smallexample"> test.o: ELF N32 MSB ...
|
|
920 </pre>
|
|
921 <p>If you see:
|
|
922
|
|
923 <pre class="smallexample"> test.o: ELF 32-bit MSB ...
|
|
924 </pre>
|
|
925 <p>or
|
|
926
|
|
927 <pre class="smallexample"> test.o: ELF 64-bit MSB ...
|
|
928 </pre>
|
|
929 <p>then your version of <samp><span class="command">cc</span></samp> uses the O32 or N64 ABI by default. You
|
|
930 should set the environment variable <samp><span class="env">CC</span></samp> to ‘<samp><span class="samp">cc -n32</span></samp>’
|
|
931 before configuring GCC.
|
|
932
|
|
933 <p>If you want the resulting <samp><span class="command">gcc</span></samp> to run on old 32-bit systems
|
|
934 with the MIPS R4400 CPU, you need to ensure that only code for the ‘<samp><span class="samp">mips3</span></samp>’
|
|
935 instruction set architecture (ISA) is generated. While GCC 3.x does
|
|
936 this correctly, both GCC 2.95 and SGI's MIPSpro <samp><span class="command">cc</span></samp> may change
|
|
937 the ISA depending on the machine where GCC is built. Using one of them
|
|
938 as the bootstrap compiler may result in ‘<samp><span class="samp">mips4</span></samp>’ code, which won't run at
|
|
939 all on ‘<samp><span class="samp">mips3</span></samp>’-only systems. For the test program above, you should see:
|
|
940
|
|
941 <pre class="smallexample"> test.o: ELF N32 MSB mips-3 ...
|
|
942 </pre>
|
|
943 <p>If you get:
|
|
944
|
|
945 <pre class="smallexample"> test.o: ELF N32 MSB mips-4 ...
|
|
946 </pre>
|
|
947 <p>instead, you should set the environment variable <samp><span class="env">CC</span></samp> to ‘<samp><span class="samp">cc
|
|
948 -n32 -mips3</span></samp>’ or ‘<samp><span class="samp">gcc -mips3</span></samp>’ respectively before configuring GCC.
|
|
949
|
|
950 <p>MIPSpro C 7.4 may cause bootstrap failures, due to a bug when inlining
|
|
951 <code>memcmp</code>. Either add <code>-U__INLINE_INTRINSICS</code> to the <samp><span class="env">CC</span></samp>
|
|
952 environment variable as a workaround or upgrade to MIPSpro C 7.4.1m.
|
|
953
|
|
954 <p>GCC on IRIX 6 is usually built to support the N32, O32 and N64 ABIs. If
|
|
955 you build GCC on a system that doesn't have the N64 libraries installed
|
|
956 or cannot run 64-bit binaries,
|
|
957 you need to configure with <samp><span class="option">--disable-multilib</span></samp> so GCC doesn't
|
|
958 try to use them. This will disable building the O32 libraries, too.
|
|
959 Look for <samp><span class="file">/usr/lib64/libc.so.1</span></samp> to see if you
|
|
960 have the 64-bit libraries installed.
|
|
961
|
|
962 <p>To enable debugging for the O32 ABI, you must use GNU <samp><span class="command">as</span></samp> from
|
|
963 GNU binutils 2.15 or later. You may also use GNU <samp><span class="command">ld</span></samp>, but
|
|
964 this is not required and currently causes some problems with Ada.
|
|
965
|
|
966 <p>The <samp><span class="option">--enable-libgcj</span></samp>
|
|
967 option is disabled by default: IRIX 6 uses a very low default limit
|
|
968 (20480) for the command line length. Although <samp><span class="command">libtool</span></samp> contains a
|
|
969 workaround for this problem, at least the N64 ‘<samp><span class="samp">libgcj</span></samp>’ is known not
|
|
970 to build despite this, running into an internal error of the native
|
|
971 <samp><span class="command">ld</span></samp>. A sure fix is to increase this limit (‘<samp><span class="samp">ncargs</span></samp>’) to
|
|
972 its maximum of 262144 bytes. If you have root access, you can use the
|
|
973 <samp><span class="command">systune</span></samp> command to do this.
|
|
974
|
|
975 <p><code>wchar_t</code> support in ‘<samp><span class="samp">libstdc++</span></samp>’ is not available for old
|
|
976 IRIX 6.5.x releases, x < 19. The problem cannot be autodetected
|
|
977 and in order to build GCC for such targets you need to configure with
|
|
978 <samp><span class="option">--disable-wchar_t</span></samp>.
|
|
979
|
|
980 <p>See <a href="http://freeware.sgi.com/">http://freeware.sgi.com/</a> for more
|
|
981 information about using GCC on IRIX platforms.
|
|
982
|
|
983 <p><hr />
|
|
984
|
|
985 <h3 class="heading"><a name="TOC32"></a><a name="powerpc_002dx_002dx"></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 />
|
|
995
|
|
996 <h3 class="heading"><a name="TOC33"></a><a name="powerpc_002dx_002ddarwin"></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://developer.apple.com/darwin/projects/compiler/">http://developer.apple.com/darwin/projects/compiler/</a> (free
|
|
1004 registration required).
|
|
1005
|
|
1006 <p>This version of GCC requires at least cctools-590.36. The
|
|
1007 cctools-590.36 package referenced from
|
|
1008 <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
|
|
1009 on systems older than 10.3.9 (aka darwin7.9.0).
|
|
1010
|
|
1011 <p><hr />
|
|
1012
|
|
1013 <h3 class="heading"><a name="TOC34"></a><a name="powerpc_002dx_002delf"></a>powerpc-*-elf</h3>
|
|
1014
|
|
1015 <p>PowerPC system in big endian mode, running System V.4.
|
|
1016
|
|
1017 <p><hr />
|
|
1018
|
|
1019 <h3 class="heading"><a name="TOC35"></a><a name="powerpc_002dx_002dlinux_002dgnu"></a>powerpc*-*-linux-gnu*</h3>
|
|
1020
|
|
1021 <p>PowerPC system in big endian mode running Linux.
|
|
1022
|
|
1023 <p><hr />
|
|
1024
|
|
1025 <h3 class="heading"><a name="TOC36"></a><a name="powerpc_002dx_002dnetbsd"></a>powerpc-*-netbsd*</h3>
|
|
1026
|
|
1027 <p>PowerPC system in big endian mode running NetBSD.
|
|
1028
|
|
1029 <p><hr />
|
|
1030
|
|
1031 <h3 class="heading"><a name="TOC37"></a><a name="powerpc_002dx_002deabisim"></a>powerpc-*-eabisim</h3>
|
|
1032
|
|
1033 <p>Embedded PowerPC system in big endian mode for use in running under the
|
|
1034 PSIM simulator.
|
|
1035
|
|
1036 <p><hr />
|
|
1037
|
|
1038 <h3 class="heading"><a name="TOC38"></a><a name="powerpc_002dx_002deabi"></a>powerpc-*-eabi</h3>
|
|
1039
|
|
1040 <p>Embedded PowerPC system in big endian mode.
|
|
1041
|
|
1042 <p><hr />
|
|
1043
|
|
1044 <h3 class="heading"><a name="TOC39"></a><a name="powerpcle_002dx_002delf"></a>powerpcle-*-elf</h3>
|
|
1045
|
|
1046 <p>PowerPC system in little endian mode, running System V.4.
|
|
1047
|
|
1048 <p><hr />
|
|
1049
|
|
1050 <h3 class="heading"><a name="TOC40"></a><a name="powerpcle_002dx_002deabisim"></a>powerpcle-*-eabisim</h3>
|
|
1051
|
|
1052 <p>Embedded PowerPC system in little endian mode for use in running under
|
|
1053 the PSIM simulator.
|
|
1054
|
|
1055 <p><hr />
|
|
1056
|
|
1057 <h3 class="heading"><a name="TOC41"></a><a name="powerpcle_002dx_002deabi"></a>powerpcle-*-eabi</h3>
|
|
1058
|
|
1059 <p>Embedded PowerPC system in little endian mode.
|
|
1060
|
|
1061 <p><hr />
|
|
1062
|
|
1063 <h3 class="heading"><a name="TOC42"></a><a name="s390_002dx_002dlinux"></a>s390-*-linux*</h3>
|
|
1064
|
|
1065 <p>S/390 system running GNU/Linux for S/390.
|
|
1066
|
|
1067 <p><hr />
|
|
1068
|
|
1069 <h3 class="heading"><a name="TOC43"></a><a name="s390x_002dx_002dlinux"></a>s390x-*-linux*</h3>
|
|
1070
|
|
1071 <p>zSeries system (64-bit) running GNU/Linux for zSeries.
|
|
1072
|
|
1073 <p><hr />
|
|
1074
|
|
1075 <h3 class="heading"><a name="TOC44"></a><a name="s390x_002dibm_002dtpf"></a>s390x-ibm-tpf*</h3>
|
|
1076
|
|
1077 <p>zSeries system (64-bit) running TPF. This platform is
|
|
1078 supported as cross-compilation target only.
|
|
1079
|
|
1080 <p><hr /><!-- Please use Solaris 2 to refer to all release of Solaris, starting -->
|
|
1081 <!-- with 2.0 until 2.6, 7, 8, etc. Solaris 1 was a marketing name for -->
|
|
1082 <!-- SunOS 4 releases which we don't use to avoid confusion. Solaris -->
|
|
1083 <!-- alone is too unspecific and must be avoided. -->
|
|
1084
|
|
1085 <h3 class="heading"><a name="TOC45"></a><a name="x_002dx_002dsolaris2"></a>*-*-solaris2*</h3>
|
|
1086
|
|
1087 <p>Sun does not ship a C compiler with Solaris 2. To bootstrap and install
|
|
1088 GCC you first have to install a pre-built compiler, see the
|
|
1089 <a href="binaries.html">binaries page</a> for details.
|
|
1090
|
|
1091 <p>The Solaris 2 <samp><span class="command">/bin/sh</span></samp> will often fail to configure
|
|
1092 <samp><span class="file">libstdc++-v3</span></samp>, <samp><span class="file">boehm-gc</span></samp> or <samp><span class="file">libjava</span></samp>. We therefore
|
|
1093 recommend using the following initial sequence of commands
|
|
1094
|
|
1095 <pre class="smallexample"> % CONFIG_SHELL=/bin/ksh
|
|
1096 % export CONFIG_SHELL
|
|
1097 </pre>
|
|
1098 <p>and proceed as described in <a href="configure.html">the configure instructions</a>.
|
|
1099 In addition we strongly recommend specifying an absolute path to invoke
|
|
1100 <var>srcdir</var>/configure.
|
|
1101
|
|
1102 <p>Solaris 2 comes with a number of optional OS packages. Some of these
|
|
1103 are needed to use GCC fully, namely <code>SUNWarc</code>,
|
|
1104 <code>SUNWbtool</code>, <code>SUNWesu</code>, <code>SUNWhea</code>, <code>SUNWlibm</code>,
|
|
1105 <code>SUNWsprot</code>, and <code>SUNWtoo</code>. If you did not install all
|
|
1106 optional packages when installing Solaris 2, you will need to verify that
|
|
1107 the packages that GCC needs are installed.
|
|
1108
|
|
1109 <p>To check whether an optional package is installed, use
|
|
1110 the <samp><span class="command">pkginfo</span></samp> command. To add an optional package, use the
|
|
1111 <samp><span class="command">pkgadd</span></samp> command. For further details, see the Solaris 2
|
|
1112 documentation.
|
|
1113
|
|
1114 <p>Trying to use the linker and other tools in
|
|
1115 <samp><span class="file">/usr/ucb</span></samp> to install GCC has been observed to cause trouble.
|
|
1116 For example, the linker may hang indefinitely. The fix is to remove
|
|
1117 <samp><span class="file">/usr/ucb</span></samp> from your <samp><span class="env">PATH</span></samp>.
|
|
1118
|
|
1119 <p>The build process works more smoothly with the legacy Sun tools so, if you
|
|
1120 have <samp><span class="file">/usr/xpg4/bin</span></samp> in your <samp><span class="env">PATH</span></samp>, we recommend that you place
|
|
1121 <samp><span class="file">/usr/bin</span></samp> before <samp><span class="file">/usr/xpg4/bin</span></samp> for the duration of the build.
|
|
1122
|
|
1123 <p>We recommend the use of GNU binutils 2.14 or later, or the vendor tools
|
|
1124 (Sun <samp><span class="command">as</span></samp>, Sun <samp><span class="command">ld</span></samp>). Note that your mileage may vary
|
|
1125 if you use a combination of the GNU tools and the Sun tools: while the
|
|
1126 combination GNU <samp><span class="command">as</span></samp> + Sun <samp><span class="command">ld</span></samp> should reasonably work,
|
|
1127 the reverse combination Sun <samp><span class="command">as</span></samp> + GNU <samp><span class="command">ld</span></samp> is known to
|
|
1128 cause memory corruption at runtime in some cases for C++ programs.
|
|
1129
|
|
1130 <p>The stock GNU binutils 2.15 release is broken on this platform because of a
|
|
1131 single bug. It has been fixed on the 2.15 branch in the CVS repository.
|
|
1132 You can obtain a working version by checking out the binutils-2_15-branch
|
|
1133 from the CVS repository or applying the patch
|
|
1134 <a href="http://sourceware.org/ml/binutils-cvs/2004-09/msg00036.html">http://sourceware.org/ml/binutils-cvs/2004-09/msg00036.html</a> to the
|
|
1135 release.
|
|
1136
|
|
1137 <p>We recommend the use of GNU binutils 2.16 or later in conjunction with GCC
|
|
1138 4.x, or the vendor tools (Sun <samp><span class="command">as</span></samp>, Sun <samp><span class="command">ld</span></samp>). However,
|
|
1139 for Solaris 10 and above, an additional patch is required in order for the
|
|
1140 GNU linker to be able to cope with a new flavor of shared libraries. You
|
|
1141 can obtain a working version by checking out the binutils-2_16-branch from
|
|
1142 the CVS repository or applying the patch
|
|
1143 <a href="http://sourceware.org/ml/binutils-cvs/2005-07/msg00122.html">http://sourceware.org/ml/binutils-cvs/2005-07/msg00122.html</a> to the
|
|
1144 release.
|
|
1145
|
|
1146 <p>Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
|
|
1147 newer: <samp><span class="command">g++</span></samp> will complain that types are missing. These headers
|
|
1148 assume that omitting the type means <code>int</code>; this assumption worked for
|
|
1149 C89 but is wrong for C++, and is now wrong for C99 also.
|
|
1150
|
|
1151 <p><samp><span class="command">g++</span></samp> accepts such (invalid) constructs with the option
|
|
1152 <samp><span class="option">-fpermissive</span></samp>; it will assume that any missing type is <code>int</code>
|
|
1153 (as defined by C89).
|
|
1154
|
|
1155 <p>There are patches for Solaris 7 (108376-21 or newer for SPARC,
|
|
1156 108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC,
|
|
1157 108653-22 for Intel) that fix this bug.
|
|
1158
|
|
1159 <p>Sun bug 4927647 sometimes causes random spurious testsuite failures
|
|
1160 related to missing diagnostic output. This bug doesn't affect GCC
|
|
1161 itself, rather it is a kernel bug triggered by the <samp><span class="command">expect</span></samp>
|
|
1162 program which is used only by the GCC testsuite driver. When the bug
|
|
1163 causes the <samp><span class="command">expect</span></samp> program to miss anticipated output, extra
|
|
1164 testsuite failures appear.
|
|
1165
|
|
1166 <p>There are patches for Solaris 8 (117350-12 or newer for SPARC,
|
|
1167 117351-12 or newer for Intel) and Solaris 9 (117171-11 or newer for
|
|
1168 SPARC, 117172-11 or newer for Intel) that address this problem.
|
|
1169
|
|
1170 <p><hr />
|
|
1171
|
|
1172 <h3 class="heading"><a name="TOC46"></a><a name="sparc_002dsun_002dsolaris2"></a>sparc-sun-solaris2*</h3>
|
|
1173
|
|
1174 <p>When GCC is configured to use binutils 2.14 or later the binaries
|
|
1175 produced are smaller than the ones produced using Sun's native tools;
|
|
1176 this difference is quite significant for binaries containing debugging
|
|
1177 information.
|
|
1178
|
|
1179 <p>Starting with Solaris 7, the operating system is capable of executing
|
|
1180 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
|
|
1181 this; the <samp><span class="option">-m64</span></samp> option enables 64-bit code generation.
|
|
1182 However, if all you want is code tuned for the UltraSPARC CPU, you
|
|
1183 should try the <samp><span class="option">-mtune=ultrasparc</span></samp> option instead, which produces
|
|
1184 code that, unlike full 64-bit code, can still run on non-UltraSPARC
|
|
1185 machines.
|
|
1186
|
|
1187 <p>When configuring on a Solaris 7 or later system that is running a kernel
|
|
1188 that supports only 32-bit binaries, one must configure with
|
|
1189 <samp><span class="option">--disable-multilib</span></samp>, since we will not be able to build the
|
|
1190 64-bit target libraries.
|
|
1191
|
|
1192 <p>GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of
|
|
1193 the GNU compiler (especially GCC 3.0.x versions), which lead to the
|
|
1194 miscompilation of the stage1 compiler and the subsequent failure of the
|
|
1195 bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary
|
|
1196 stage, i.e. to bootstrap that compiler with the base compiler and then
|
|
1197 use it to bootstrap the final compiler.
|
|
1198
|
|
1199 <p>GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE Studio 7)
|
|
1200 and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a bootstrap
|
|
1201 failure in form of a miscompilation of the stage1 compiler by the Sun
|
|
1202 compiler. This is Sun bug 4974440. This is fixed with patch 112760-07.
|
|
1203
|
|
1204 <p>GCC 3.4 changed the default debugging format from STABS to DWARF-2 for
|
|
1205 32-bit code on Solaris 7 and later. If you use the Sun assembler, this
|
|
1206 change apparently runs afoul of Sun bug 4910101 (which is referenced as
|
|
1207 a x86-only problem by Sun, probably because they do not use DWARF-2).
|
|
1208 A symptom of the problem is that you cannot compile C++ programs like
|
|
1209 <samp><span class="command">groff</span></samp> 1.19.1 without getting messages similar to the following:
|
|
1210
|
|
1211 <pre class="smallexample"> ld: warning: relocation error: R_SPARC_UA32: ...
|
|
1212 external symbolic relocation against non-allocatable section
|
|
1213 .debug_info cannot be processed at runtime: relocation ignored.
|
|
1214 </pre>
|
|
1215 <p>To work around this problem, compile with <samp><span class="option">-gstabs+</span></samp> instead of
|
|
1216 plain <samp><span class="option">-g</span></samp>.
|
|
1217
|
|
1218 <p>When configuring the GNU Multiple Precision Library (GMP) or the MPFR
|
|
1219 library on a Solaris 7 or later system, the canonical target triplet
|
|
1220 must be specified as the <samp><span class="command">build</span></samp> parameter on the configure
|
|
1221 line. This triplet can be obtained by invoking ./config.guess in
|
|
1222 the toplevel source directory of GCC (and not that of GMP or MPFR).
|
|
1223 For example on a Solaris 7 system:
|
|
1224
|
|
1225 <pre class="smallexample"> % ./configure --build=sparc-sun-solaris2.7 --prefix=xxx
|
|
1226 </pre>
|
|
1227 <p><hr />
|
|
1228
|
|
1229 <h3 class="heading"><a name="TOC47"></a><a name="sparc_002dsun_002dsolaris27"></a>sparc-sun-solaris2.7</h3>
|
|
1230
|
|
1231 <p>Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in
|
|
1232 the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8
|
|
1233 and later, including all EGCS releases. Sun formerly recommended
|
|
1234 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to
|
|
1235 recommend it only for people who use Sun's compilers.
|
|
1236
|
|
1237 <p>Here are some workarounds to this problem:
|
|
1238 <ul>
|
|
1239 <li>Do not install Sun patch 107058-01 until after Sun releases a
|
|
1240 complete patch for bug 4210064. This is the simplest course to take,
|
|
1241 unless you must also use Sun's C compiler. Unfortunately 107058-01
|
|
1242 is preinstalled on some new Solaris 7-based hosts, so you may have to
|
|
1243 back it out.
|
|
1244
|
|
1245 <li>Copy the original, unpatched Solaris 7
|
|
1246 <samp><span class="command">/usr/ccs/bin/as</span></samp> into
|
|
1247 <samp><span class="command">/usr/local/libexec/gcc/sparc-sun-solaris2.7/3.4/as</span></samp>,
|
|
1248 adjusting the latter name to fit your local conventions and software
|
|
1249 version numbers.
|
|
1250
|
|
1251 <li>Install Sun patch 106950-03 (1999-05-25) or later. Nobody with
|
|
1252 both 107058-01 and 106950-03 installed has reported the bug with GCC
|
|
1253 and Sun's dynamic linker. This last course of action is riskiest,
|
|
1254 for two reasons. First, you must install 106950 on all hosts that
|
|
1255 run code generated by GCC; it doesn't suffice to install it only on
|
|
1256 the hosts that run GCC itself. Second, Sun says that 106950-03 is
|
|
1257 only a partial fix for bug 4210064, but Sun doesn't know whether the
|
|
1258 partial fix is adequate for GCC. Revision -08 or later should fix
|
|
1259 the bug. The current (as of 2004-05-23) revision is -24, and is included in
|
|
1260 the Solaris 7 Recommended Patch Cluster.
|
|
1261 </ul>
|
|
1262
|
|
1263 <p>GCC 3.3 triggers a bug in version 5.0 Alpha 03/27/98 of the Sun assembler,
|
|
1264 which causes a bootstrap failure when linking the 64-bit shared version of
|
|
1265 libgcc. A typical error message is:
|
|
1266
|
|
1267 <pre class="smallexample"> ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o:
|
|
1268 symbol <unknown>: offset 0xffffffff7ec133e7 is non-aligned.
|
|
1269 </pre>
|
|
1270 <p>This bug has been fixed in the final 5.0 version of the assembler.
|
|
1271
|
|
1272 <p>A similar problem was reported for version Sun WorkShop 6 99/08/18 of the
|
|
1273 Sun assembler, which causes a bootstrap failure with GCC 4.0.0:
|
|
1274
|
|
1275 <pre class="smallexample"> ld: fatal: relocation error: R_SPARC_DISP32:
|
|
1276 file .libs/libstdc++.lax/libsupc++convenience.a/vterminate.o:
|
|
1277 symbol <unknown>: offset 0xfccd33ad is non-aligned
|
|
1278 </pre>
|
|
1279 <p>This bug has been fixed in more recent revisions of the assembler.
|
|
1280
|
|
1281 <p><hr />
|
|
1282
|
|
1283 <h3 class="heading"><a name="TOC48"></a><a name="sparc_002dx_002dlinux"></a>sparc-*-linux*</h3>
|
|
1284
|
|
1285 <p>GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
|
|
1286 or newer on this platform. All earlier binutils and glibc
|
|
1287 releases mishandled unaligned relocations on <code>sparc-*-*</code> targets.
|
|
1288
|
|
1289 <p><hr />
|
|
1290
|
|
1291 <h3 class="heading"><a name="TOC49"></a><a name="sparc64_002dx_002dsolaris2"></a>sparc64-*-solaris2*</h3>
|
|
1292
|
|
1293 <p>When configuring the GNU Multiple Precision Library (GMP) or the
|
|
1294 MPFR library, the canonical target triplet must be specified as
|
|
1295 the <samp><span class="command">build</span></samp> parameter on the configure line. For example
|
|
1296 on a Solaris 7 system:
|
|
1297
|
|
1298 <pre class="smallexample"> % ./configure --build=sparc64-sun-solaris2.7 --prefix=xxx
|
|
1299 </pre>
|
|
1300 <p>The following compiler flags must be specified in the configure
|
|
1301 step in order to bootstrap this target with the Sun compiler:
|
|
1302
|
|
1303 <pre class="smallexample"> % CC="cc -xarch=v9 -xildoff" <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>]
|
|
1304 </pre>
|
|
1305 <p><samp><span class="option">-xarch=v9</span></samp> specifies the SPARC-V9 architecture to the Sun toolchain
|
|
1306 and <samp><span class="option">-xildoff</span></samp> turns off the incremental linker.
|
|
1307
|
|
1308 <p><hr />
|
|
1309
|
|
1310 <h3 class="heading"><a name="TOC50"></a><a name="sparcv9_002dx_002dsolaris2"></a>sparcv9-*-solaris2*</h3>
|
|
1311
|
|
1312 <p>This is a synonym for sparc64-*-solaris2*.
|
|
1313
|
|
1314 <p><hr />
|
|
1315
|
|
1316 <h3 class="heading"><a name="TOC51"></a><a name="x_002dx_002dvxworks"></a>*-*-vxworks*</h3>
|
|
1317
|
|
1318 <p>Support for VxWorks is in flux. At present GCC supports <em>only</em> the
|
|
1319 very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC.
|
|
1320 We welcome patches for other architectures supported by VxWorks 5.5.
|
|
1321 Support for VxWorks AE would also be welcome; we believe this is merely
|
|
1322 a matter of writing an appropriate “configlette” (see below). We are
|
|
1323 not interested in supporting older, a.out or COFF-based, versions of
|
|
1324 VxWorks in GCC 3.
|
|
1325
|
|
1326 <p>VxWorks comes with an older version of GCC installed in
|
|
1327 <samp><var>$WIND_BASE</var><span class="file">/host</span></samp>; we recommend you do not overwrite it.
|
|
1328 Choose an installation <var>prefix</var> entirely outside <var>$WIND_BASE</var>.
|
|
1329 Before running <samp><span class="command">configure</span></samp>, create the directories <samp><var>prefix</var></samp>
|
|
1330 and <samp><var>prefix</var><span class="file">/bin</span></samp>. Link or copy the appropriate assembler,
|
|
1331 linker, etc. into <samp><var>prefix</var><span class="file">/bin</span></samp>, and set your <var>PATH</var> to
|
|
1332 include that directory while running both <samp><span class="command">configure</span></samp> and
|
|
1333 <samp><span class="command">make</span></samp>.
|
|
1334
|
|
1335 <p>You must give <samp><span class="command">configure</span></samp> the
|
|
1336 <samp><span class="option">--with-headers=</span><var>$WIND_BASE</var><span class="option">/target/h</span></samp> switch so that it can
|
|
1337 find the VxWorks system headers. Since VxWorks is a cross compilation
|
|
1338 target only, you must also specify <samp><span class="option">--target=</span><var>target</var></samp>.
|
|
1339 <samp><span class="command">configure</span></samp> will attempt to create the directory
|
|
1340 <samp><var>prefix</var><span class="file">/</span><var>target</var><span class="file">/sys-include</span></samp> and copy files into it;
|
|
1341 make sure the user running <samp><span class="command">configure</span></samp> has sufficient privilege
|
|
1342 to do so.
|
|
1343
|
|
1344 <p>GCC's exception handling runtime requires a special “configlette”
|
|
1345 module, <samp><span class="file">contrib/gthr_supp_vxw_5x.c</span></samp>. Follow the instructions in
|
|
1346 that file to add the module to your kernel build. (Future versions of
|
|
1347 VxWorks will incorporate this module.)
|
|
1348
|
|
1349 <p><hr />
|
|
1350
|
|
1351 <h3 class="heading"><a name="TOC52"></a><a name="x86_002d64_002dx_002dx"></a>x86_64-*-*, amd64-*-*</h3>
|
|
1352
|
|
1353 <p>GCC supports the x86-64 architecture implemented by the AMD64 processor
|
|
1354 (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD.
|
|
1355 On GNU/Linux the default is a bi-arch compiler which is able to generate
|
|
1356 both 64-bit x86-64 and 32-bit x86 code (via the <samp><span class="option">-m32</span></samp> switch).
|
|
1357
|
|
1358 <p><hr />
|
|
1359
|
|
1360 <h3 class="heading"><a name="TOC53"></a><a name="xtensa_002dx_002delf"></a>xtensa*-*-elf</h3>
|
|
1361
|
|
1362 <p>This target is intended for embedded Xtensa systems using the
|
|
1363 ‘<samp><span class="samp">newlib</span></samp>’ C library. It uses ELF but does not support shared
|
|
1364 objects. Designed-defined instructions specified via the
|
|
1365 Tensilica Instruction Extension (TIE) language are only supported
|
|
1366 through inline assembly.
|
|
1367
|
|
1368 <p>The Xtensa configuration information must be specified prior to
|
|
1369 building GCC. The <samp><span class="file">include/xtensa-config.h</span></samp> header
|
|
1370 file contains the configuration information. If you created your
|
|
1371 own Xtensa configuration with the Xtensa Processor Generator, the
|
|
1372 downloaded files include a customized copy of this header file,
|
|
1373 which you can use to replace the default header file.
|
|
1374
|
|
1375 <p><hr />
|
|
1376
|
|
1377 <h3 class="heading"><a name="TOC54"></a><a name="xtensa_002dx_002dlinux"></a>xtensa*-*-linux*</h3>
|
|
1378
|
|
1379 <p>This target is for Xtensa systems running GNU/Linux. It supports ELF
|
|
1380 shared objects and the GNU C library (glibc). It also generates
|
|
1381 position-independent code (PIC) regardless of whether the
|
|
1382 <samp><span class="option">-fpic</span></samp> or <samp><span class="option">-fPIC</span></samp> options are used. In other
|
|
1383 respects, this target is the same as the
|
|
1384 <a href="#xtensa*-*-elf">‘<samp><span class="samp">xtensa*-*-elf</span></samp>’</a> target.
|
|
1385
|
|
1386 <p><hr />
|
|
1387
|
|
1388 <h3 class="heading"><a name="TOC55"></a><a name="windows"></a>Microsoft Windows</h3>
|
|
1389
|
|
1390 <h4 class="subheading"><a name="TOC56"></a>Intel 16-bit versions</h4>
|
|
1391
|
|
1392 <p>The 16-bit versions of Microsoft Windows, such as Windows 3.1, are not
|
|
1393 supported.
|
|
1394
|
|
1395 <p>However, the 32-bit port has limited support for Microsoft
|
|
1396 Windows 3.11 in the Win32s environment, as a target only. See below.
|
|
1397
|
|
1398 <h4 class="subheading"><a name="TOC57"></a>Intel 32-bit versions</h4>
|
|
1399
|
|
1400 <p>The 32-bit versions of Windows, including Windows 95, Windows NT, Windows
|
|
1401 XP, and Windows Vista, are supported by several different target
|
|
1402 platforms. These targets differ in which Windows subsystem they target
|
|
1403 and which C libraries are used.
|
|
1404
|
|
1405 <ul>
|
|
1406 <li>Cygwin <a href="#x-x-cygwin">*-*-cygwin</a>: Cygwin provides a user-space
|
|
1407 Linux API emulation layer in the Win32 subsystem.
|
|
1408 <li>Interix <a href="#x-x-interix">*-*-interix</a>: The Interix subsystem
|
|
1409 provides native support for POSIX.
|
|
1410 <li>MinGW <a href="#x-x-mingw">*-*-mingw</a>: MinGW is a native GCC port for
|
|
1411 the Win32 subsystem that provides a subset of POSIX.
|
|
1412 <li>MKS i386-pc-mks: NuTCracker from MKS. See
|
|
1413 <a href="http://www.mkssoftware.com/">http://www.mkssoftware.com/</a> for more information.
|
|
1414 </ul>
|
|
1415
|
|
1416 <h4 class="subheading"><a name="TOC58"></a>Intel 64-bit versions</h4>
|
|
1417
|
|
1418 <p>GCC contains support for x86-64 using the mingw-w64
|
|
1419 runtime library, available from <a href="http://mingw-w64.sourceforge.net/">http://mingw-w64.sourceforge.net/</a>.
|
|
1420 This library should be used with the target triple x86_64-pc-mingw32.
|
|
1421
|
|
1422 <p>Presently Windows for Itanium is not supported.
|
|
1423
|
|
1424 <h4 class="subheading"><a name="TOC59"></a>Windows CE</h4>
|
|
1425
|
|
1426 <p>Windows CE is supported as a target only on ARM (arm-wince-pe), Hitachi
|
|
1427 SuperH (sh-wince-pe), and MIPS (mips-wince-pe).
|
|
1428
|
|
1429 <h4 class="subheading"><a name="TOC60"></a>Other Windows Platforms</h4>
|
|
1430
|
|
1431 <p>GCC no longer supports Windows NT on the Alpha or PowerPC.
|
|
1432
|
|
1433 <p>GCC no longer supports the Windows POSIX subsystem. However, it does
|
|
1434 support the Interix subsystem. See above.
|
|
1435
|
|
1436 <p>Old target names including *-*-winnt and *-*-windowsnt are no longer used.
|
|
1437
|
|
1438 <p>PW32 (i386-pc-pw32) support was never completed, and the project seems to
|
|
1439 be inactive. See <a href="http://pw32.sourceforge.net/">http://pw32.sourceforge.net/</a> for more information.
|
|
1440
|
|
1441 <p>UWIN support has been removed due to a lack of maintenance.
|
|
1442
|
|
1443 <p><hr />
|
|
1444
|
|
1445 <h3 class="heading"><a name="TOC61"></a><a name="x_002dx_002dcygwin"></a>*-*-cygwin</h3>
|
|
1446
|
|
1447 <p>Ports of GCC are included with the
|
|
1448 <a href="http://www.cygwin.com/">Cygwin environment</a>.
|
|
1449
|
|
1450 <p>GCC will build under Cygwin without modification; it does not build
|
|
1451 with Microsoft's C++ compiler and there are no plans to make it do so.
|
|
1452
|
|
1453 <p>Cygwin can be compiled with i?86-pc-cygwin.
|
|
1454
|
|
1455 <p><hr />
|
|
1456
|
|
1457 <h3 class="heading"><a name="TOC62"></a><a name="x_002dx_002dinterix"></a>*-*-interix</h3>
|
|
1458
|
|
1459 <p>The Interix target is used by OpenNT, Interix, Services For UNIX (SFU),
|
|
1460 and Subsystem for UNIX-based Applications (SUA). Applications compiled
|
|
1461 with this target run in the Interix subsystem, which is separate from
|
|
1462 the Win32 subsystem. This target was last known to work in GCC 3.3.
|
|
1463
|
|
1464 <p>For more information, see <a href="http://www.interix.com/">http://www.interix.com/</a>.
|
|
1465
|
|
1466 <p><hr />
|
|
1467
|
|
1468 <h3 class="heading"><a name="TOC63"></a><a name="x_002dx_002dmingw32"></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 />
|
|
1475
|
|
1476 <h3 class="heading"><a name="TOC64"></a><a name="os2"></a>OS/2</h3>
|
|
1477
|
|
1478 <p>GCC does not currently support OS/2. However, Andrew Zabolotny has been
|
|
1479 working on a generic OS/2 port with pgcc. The current code can be found
|
|
1480 at <a href="http://www.goof.com/pcg/os2/">http://www.goof.com/pcg/os2/</a>.
|
|
1481
|
|
1482 <p><hr />
|
|
1483
|
|
1484 <h3 class="heading"><a name="TOC65"></a><a name="older"></a>Older systems</h3>
|
|
1485
|
|
1486 <p>GCC contains support files for many older (1980s and early
|
|
1487 1990s) Unix variants. For the most part, support for these systems
|
|
1488 has not been deliberately removed, but it has not been maintained for
|
|
1489 several years and may suffer from bitrot.
|
|
1490
|
|
1491 <p>Starting with GCC 3.1, each release has a list of “obsoleted” systems.
|
|
1492 Support for these systems is still present in that release, but
|
|
1493 <samp><span class="command">configure</span></samp> will fail unless the <samp><span class="option">--enable-obsolete</span></samp>
|
|
1494 option is given. Unless a maintainer steps forward, support for these
|
|
1495 systems will be removed from the next release of GCC.
|
|
1496
|
|
1497 <p>Support for old systems as hosts for GCC can cause problems if the
|
|
1498 workarounds for compiler, library and operating system bugs affect the
|
|
1499 cleanliness or maintainability of the rest of GCC. In some cases, to
|
|
1500 bring GCC up on such a system, if still possible with current GCC, may
|
|
1501 require first installing an old version of GCC which did work on that
|
|
1502 system, and using it to compile a more recent GCC, to avoid bugs in the
|
|
1503 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
|
|
1504 <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
|
|
1505 <samp><span class="command">fixincludes</span></samp>, but bugs or deficiencies in libraries and the
|
|
1506 operating system may still cause problems.
|
|
1507
|
|
1508 <p>Support for older systems as targets for cross-compilation is less
|
|
1509 problematic than support for them as hosts for GCC; if an enthusiast
|
|
1510 wishes to make such a target work again (including resurrecting any of
|
|
1511 the targets that never worked with GCC 2, starting from the last
|
|
1512 version before they were removed), patches
|
|
1513 <a href="../contribute.html">following the usual requirements</a> would be
|
|
1514 likely to be accepted, since they should not affect the support for more
|
|
1515 modern targets.
|
|
1516
|
|
1517 <p>For some systems, old versions of GNU binutils may also be useful,
|
|
1518 and are available from <samp><span class="file">pub/binutils/old-releases</span></samp> on
|
|
1519 <a href="http://sourceware.org/mirrors.html">sourceware.org mirror sites</a>.
|
|
1520
|
|
1521 <p>Some of the information on specific systems above relates to
|
|
1522 such older systems, but much of the information
|
|
1523 about GCC on such systems (which may no longer be applicable to
|
|
1524 current GCC) is to be found in the GCC texinfo manual.
|
|
1525
|
|
1526 <p><hr />
|
|
1527
|
|
1528 <h3 class="heading"><a name="TOC66"></a><a name="elf"></a>all ELF targets (SVR4, Solaris 2, etc.)</h3>
|
|
1529
|
|
1530 <p>C++ support is significantly better on ELF targets if you use the
|
|
1531 <a href="./configure.html#with-gnu-ld">GNU linker</a>; duplicate copies of
|
|
1532 inlines, vtables and template instantiations will be discarded
|
|
1533 automatically.
|
|
1534
|
|
1535 <p><hr />
|
|
1536 <p><a href="./index.html">Return to the GCC Installation page</a>
|
|
1537
|
|
1538 <!-- ***Old documentation****************************************************** -->
|
|
1539 <!-- ***GFDL******************************************************************** -->
|
|
1540 <!-- *************************************************************************** -->
|
|
1541 <!-- Part 6 The End of the Document -->
|
|
1542 </body></html>
|
|
1543
|