]>
Commit | Line | Data |
---|---|---|
f42974dc DW |
1 | \input texinfo.tex @c -*-texinfo-*- |
2 | @c @ifnothtml | |
3 | @c %**start of header | |
d7f8491b | 4 | @setfilename gccinstall.info |
f42974dc DW |
5 | @settitle Installing GCC |
6 | @setchapternewpage odd | |
7 | @c %**end of header | |
8 | @c @end ifnothtml | |
9 | ||
10 | @c Specify title for specific html page | |
11 | @ifset indexhtml | |
12 | @settitle Installing GCC | |
13 | @end ifset | |
14 | @ifset specifichtml | |
15 | @settitle Host/Target specific installation notes for GCC | |
16 | @end ifset | |
67b1fbb9 KG |
17 | @ifset prerequisiteshtml |
18 | @settitle Prerequisites for GCC | |
19 | @end ifset | |
f42974dc DW |
20 | @ifset downloadhtml |
21 | @settitle Downloading GCC | |
22 | @end ifset | |
23 | @ifset configurehtml | |
24 | @settitle Installing GCC: Configuration | |
25 | @end ifset | |
26 | @ifset buildhtml | |
27 | @settitle Installing GCC: Building | |
28 | @end ifset | |
29 | @ifset testhtml | |
30 | @settitle Installing GCC: Testing | |
31 | @end ifset | |
32 | @ifset finalinstallhtml | |
33 | @settitle Installing GCC: Final installation | |
34 | @end ifset | |
35 | @ifset binarieshtml | |
36 | @settitle Installing GCC: Binaries | |
37 | @end ifset | |
73e2155a JM |
38 | @ifset oldhtml |
39 | @settitle Installing GCC: Old documentation | |
40 | @end ifset | |
aed5964b JM |
41 | @ifset gfdlhtml |
42 | @settitle Installing GCC: GNU Free Documentation License | |
43 | @end ifset | |
f42974dc | 44 | |
aed5964b | 45 | @c Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, |
daef8bbd | 46 | @c 1999, 2000, 2001, 2002, 2003, 2004 Free Software Foundation, Inc. |
f42974dc DW |
47 | @c *** Converted to texinfo by Dean Wakerley, dean@wakerley.com |
48 | ||
49 | @c Include everything if we're not making html | |
50 | @ifnothtml | |
51 | @set indexhtml | |
52 | @set specifichtml | |
67b1fbb9 | 53 | @set prerequisiteshtml |
f42974dc DW |
54 | @set downloadhtml |
55 | @set configurehtml | |
56 | @set buildhtml | |
57 | @set testhtml | |
58 | @set finalinstallhtml | |
59 | @set binarieshtml | |
73e2155a | 60 | @set oldhtml |
aed5964b | 61 | @set gfdlhtml |
f42974dc DW |
62 | @end ifnothtml |
63 | ||
64 | @c Part 2 Summary Description and Copyright | |
bdefb2ab | 65 | @copying |
aed5964b | 66 | Copyright @copyright{} 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, |
daef8bbd | 67 | 1999, 2000, 2001, 2002, 2003, 2004 Free Software Foundation, Inc. |
aed5964b JM |
68 | @sp 1 |
69 | Permission is granted to copy, distribute and/or modify this document | |
b3a8389d | 70 | under the terms of the GNU Free Documentation License, Version 1.2 or |
aed5964b JM |
71 | any later version published by the Free Software Foundation; with no |
72 | Invariant Sections, the Front-Cover texts being (a) (see below), and | |
73 | with the Back-Cover Texts being (b) (see below). A copy of the | |
74 | license is included in the section entitled ``@uref{./gfdl.html,,GNU | |
75 | Free Documentation License}''. | |
76 | ||
77 | (a) The FSF's Front-Cover Text is: | |
78 | ||
79 | A GNU Manual | |
80 | ||
81 | (b) The FSF's Back-Cover Text is: | |
82 | ||
83 | You have freedom to copy and modify this GNU Manual, like GNU | |
84 | software. Copies published by the Free Software Foundation raise | |
85 | funds for GNU development. | |
bdefb2ab | 86 | @end copying |
f42974dc | 87 | @ifinfo |
bdefb2ab | 88 | @insertcopying |
f42974dc | 89 | @end ifinfo |
802f6d4b JM |
90 | @dircategory Programming |
91 | @direntry | |
92 | * gccinstall: (gccinstall). Installing the GNU Compiler Collection. | |
93 | @end direntry | |
f42974dc DW |
94 | |
95 | @c Part 3 Titlepage and Copyright | |
96 | @titlepage | |
97 | @sp 10 | |
98 | @comment The title is printed in a large font. | |
ef88b07d | 99 | @center @titlefont{Installing GCC} |
f42974dc DW |
100 | |
101 | @c The following two commands start the copyright page. | |
102 | @page | |
ef88b07d | 103 | @vskip 0pt plus 1filll |
bdefb2ab | 104 | @insertcopying |
f42974dc DW |
105 | @end titlepage |
106 | ||
107 | @c Part 4 Top node and Master Menu | |
108 | @ifinfo | |
109 | @node Top, , , (dir) | |
110 | @comment node-name, next, Previous, up | |
111 | ||
112 | @menu | |
113 | * Installing GCC:: This document describes the generic installation | |
114 | procedure for GCC as well as detailing some target | |
f9047ed3 | 115 | specific installation instructions. |
f42974dc DW |
116 | |
117 | * Specific:: Host/target specific installation notes for GCC. | |
118 | * Binaries:: Where to get pre-compiled binaries. | |
119 | ||
73e2155a JM |
120 | * Old:: Old installation documentation. |
121 | ||
aed5964b | 122 | * GNU Free Documentation License:: How you can copy and share this manual. |
f42974dc DW |
123 | * Concept Index:: This index has two entries. |
124 | @end menu | |
125 | @end ifinfo | |
126 | ||
127 | @c Part 5 The Body of the Document | |
128 | @c ***Installing GCC********************************************************** | |
6cfb3f16 | 129 | @ifnothtml |
f42974dc DW |
130 | @comment node-name, next, previous, up |
131 | @node Installing GCC, Binaries, , Top | |
6cfb3f16 | 132 | @end ifnothtml |
f42974dc | 133 | @ifset indexhtml |
f42974dc DW |
134 | @ifnothtml |
135 | @chapter Installing GCC | |
136 | @end ifnothtml | |
137 | ||
138 | The latest version of this document is always available at | |
f9047ed3 | 139 | @uref{http://gcc.gnu.org/install/,,http://gcc.gnu.org/install/}. |
f42974dc DW |
140 | |
141 | This document describes the generic installation procedure for GCC as well | |
f9047ed3 | 142 | as detailing some target specific installation instructions. |
f42974dc | 143 | |
f9047ed3 JM |
144 | GCC includes several components that previously were separate distributions |
145 | with their own installation instructions. This document supersedes all | |
eea81d3e | 146 | package specific installation instructions. |
f42974dc | 147 | |
f9047ed3 | 148 | @emph{Before} starting the build/install procedure please check the |
f42974dc | 149 | @ifnothtml |
eea81d3e | 150 | @ref{Specific, host/target specific installation notes}. |
f42974dc | 151 | @end ifnothtml |
c009f01f | 152 | @ifhtml |
f9047ed3 | 153 | @uref{specific.html,,host/target specific installation notes}. |
c009f01f | 154 | @end ifhtml |
f9047ed3 | 155 | We recommend you browse the entire generic installation instructions before |
f42974dc DW |
156 | you proceed. |
157 | ||
c009f01f | 158 | Lists of successful builds for released versions of GCC are |
daf2f129 | 159 | available at @uref{http://gcc.gnu.org/buildstat.html}. |
c009f01f JJ |
160 | These lists are updated as new information becomes available. |
161 | ||
f9047ed3 | 162 | The installation procedure itself is broken into five steps. |
f42974dc DW |
163 | |
164 | @ifinfo | |
165 | @menu | |
67b1fbb9 | 166 | * Prerequisites:: |
f42974dc DW |
167 | * Downloading the source:: |
168 | * Configuration:: | |
169 | * Building:: | |
170 | * Testing:: (optional) | |
171 | * Final install:: | |
172 | @end menu | |
173 | @end ifinfo | |
c009f01f | 174 | @ifhtml |
f42974dc | 175 | @enumerate |
f9047ed3 | 176 | @item |
67b1fbb9 KG |
177 | @uref{prerequisites.html,,Prerequisites} |
178 | @item | |
f42974dc | 179 | @uref{download.html,,Downloading the source} |
f42974dc | 180 | @item |
f9047ed3 JM |
181 | @uref{configure.html,,Configuration} |
182 | @item | |
183 | @uref{build.html,,Building} | |
184 | @item | |
185 | @uref{test.html,,Testing} (optional) | |
f42974dc DW |
186 | @item |
187 | @uref{finalinstall.html,,Final install} | |
188 | @end enumerate | |
c009f01f | 189 | @end ifhtml |
f42974dc | 190 | |
38209993 | 191 | Please note that GCC does not support @samp{make uninstall} and probably |
f9047ed3 | 192 | won't do so in the near future as this would open a can of worms. Instead, |
f42974dc | 193 | we suggest that you install GCC into a directory of its own and simply |
38209993 | 194 | remove that directory when you do not need that specific version of GCC |
eea81d3e RO |
195 | any longer, and, if shared libraries are installed there as well, no |
196 | more binaries exist that use them. | |
f42974dc | 197 | |
73e2155a JM |
198 | @ifhtml |
199 | There are also some @uref{old.html,,old installation instructions}, | |
200 | which are mostly obsolete but still contain some information which has | |
201 | not yet been merged into the main part of this manual. | |
202 | @end ifhtml | |
203 | ||
f42974dc | 204 | @html |
b8db17af | 205 | <hr /> |
f42974dc DW |
206 | <p> |
207 | @end html | |
208 | @ifhtml | |
209 | @uref{./index.html,,Return to the GCC Installation page} | |
aed5964b | 210 | |
bdefb2ab | 211 | @insertcopying |
f42974dc DW |
212 | @end ifhtml |
213 | @end ifset | |
214 | ||
67b1fbb9 KG |
215 | @c ***Prerequisites************************************************** |
216 | @ifnothtml | |
217 | @comment node-name, next, previous, up | |
218 | @node Prerequisites, Downloading the source, , Installing GCC | |
219 | @end ifnothtml | |
220 | @ifset prerequisiteshtml | |
221 | @ifnothtml | |
222 | @chapter Prerequisites | |
223 | @end ifnothtml | |
224 | @cindex Prerequisites | |
225 | ||
226 | GCC requires that various tools and packages be available for use in the | |
227 | build procedure. Modifying GCC sources requires additional tools | |
228 | described below. | |
229 | ||
230 | @heading Tools/packages necessary for building GCC | |
231 | @table @asis | |
232 | @item ISO C90 compiler | |
233 | Necessary to bootstrap the GCC package, although versions of GCC prior | |
234 | to 3.4 also allow bootstrapping with a traditional (K&R) C compiler. | |
235 | ||
236 | To make all languages in a cross-compiler or other configuration where | |
237 | 3-stage bootstrap is not performed, you need to start with an existing | |
238 | GCC binary (version 2.95 or later) because source code for language | |
239 | frontends other than C might use GCC extensions. | |
240 | ||
241 | @item GNAT | |
242 | ||
243 | In order to build the Ada compiler (GNAT) you must already have GNAT | |
244 | installed because portions of the Ada frontend are written in Ada (with | |
245 | GNAT extensions.) Refer to the Ada installation instructions for more | |
246 | specific information. | |
247 | ||
248 | @item A ``working'' POSIX compatible shell, or GNU bash | |
249 | ||
250 | Necessary when running @command{configure} because some | |
251 | @command{/bin/sh} shells have bugs and may crash when configuring the | |
252 | target libraries. In other cases, @command{/bin/sh} or even some | |
253 | @command{ksh} have disastrous corner-case performance problems. This | |
254 | can cause target @command{configure} runs to literally take days to | |
255 | complete in some cases. | |
256 | ||
257 | So on some platforms @command{/bin/ksh} is sufficient, on others it | |
258 | isn't. See the host/target specific instructions for your platform, or | |
259 | use @command{bash} to be sure. Then set @env{CONFIG_SHELL} in your | |
260 | environment to your ``good'' shell prior to running | |
261 | @command{configure}/@command{make}. | |
262 | ||
daf2f129 | 263 | @command{zsh} is not a fully compliant POSIX shell and will not |
a755e3c5 | 264 | work when configuring GCC. |
1b49d06f | 265 | |
67b1fbb9 KG |
266 | @item GNU binutils |
267 | ||
268 | Necessary in some circumstances, optional in others. See the | |
269 | host/target specific instructions for your platform for the exact | |
270 | requirements. | |
271 | ||
272 | @item gzip version 1.2.4 (or later) or | |
273 | @itemx bzip2 version 1.0.2 (or later) | |
274 | ||
275 | Necessary to uncompress GCC @command{tar} files when source code is | |
276 | obtained via FTP mirror sites. | |
277 | ||
e158a5fb MM |
278 | @item GNU make version 3.79.1 (or later) |
279 | ||
280 | You must have GNU make installed to build GCC. | |
281 | ||
67b1fbb9 KG |
282 | @item GNU tar version 1.12 (or later) |
283 | ||
284 | Necessary (only on some platforms) to untar the source code. Many | |
285 | systems' @command{tar} programs will also work, only try GNU | |
286 | @command{tar} if you have problems. | |
287 | ||
bda4d063 TS |
288 | @item GNU Multiple Precision Library (GMP) version 4.0 (or later) |
289 | ||
290 | Necessary to build the Fortran frontend. If you don't have it | |
291 | installed in your library search path, you will have to configure with | |
292 | the @option{--with-gmp} or @option{--with-gmp-dir} configure option. | |
293 | ||
bebf829d PB |
294 | @item MPFR Library |
295 | ||
296 | Necessary to build the Fortran frontend. It can be downloaded from | |
999f4d5e | 297 | @uref{http://www.mpfr.org/}. It is also included in the current GMP |
bebf829d PB |
298 | release (4.1.3) when configured with @option{--enable-mpfr}. |
299 | ||
300 | The @option{--with-mpfr} or @option{--with-mpfr-dir} configure option should | |
301 | be used if your MPFR Library is not installed in your library search path. | |
302 | ||
67b1fbb9 KG |
303 | @end table |
304 | ||
305 | ||
306 | @heading Tools/packages necessary for modifying GCC | |
307 | @table @asis | |
0dce8934 | 308 | @item autoconf versions 2.13 and 2.59 |
67b1fbb9 KG |
309 | @itemx GNU m4 version 1.4 (or later) |
310 | ||
89acbae0 | 311 | Necessary when modifying @file{configure.ac}, @file{aclocal.m4}, etc.@: |
4f3ce03f | 312 | to regenerate @file{configure} and @file{config.in} files. Most |
5d75ba94 NN |
313 | directories require autoconf 2.59 (exactly), but the toplevel |
314 | still requires autoconf 2.13 (exactly). | |
67b1fbb9 | 315 | |
e3f92d3b | 316 | @item automake versions 1.8.5 and 1.9.1 |
67b1fbb9 KG |
317 | |
318 | Necessary when modifying a @file{Makefile.am} file to regenerate its | |
ce5c1cf3 KC |
319 | associated @file{Makefile.in}. |
320 | ||
321 | Much of GCC does not use automake, so directly edit the @file{Makefile.in} | |
322 | file. Specifically this applies to the @file{gcc}, @file{intl}, | |
078e3ffe PB |
323 | @file{libcpp}, @file{libiberty}, @file{libobjc} directories as well |
324 | as any of their subdirectories. | |
ce5c1cf3 | 325 | |
7fb654ef PC |
326 | The Java directory @file{libjava} and the @file{libstdc++-v3} directory |
327 | require automake 1.9.1. Every other directory should work with either | |
328 | automake 1.8.5 and automake 1.9.1, but most of them have been tested only | |
329 | with automake 1.8.5 so far. | |
ccfca4ae | 330 | |
4f3ce03f JM |
331 | @item gettext version 0.12 (or later) |
332 | ||
333 | Needed to regenerate @file{gcc.pot}. | |
67b1fbb9 KG |
334 | |
335 | @item gperf version 2.7.2 (or later) | |
336 | ||
337 | Necessary when modifying @command{gperf} input files, e.g.@: | |
338 | @file{gcc/cp/cfns.gperf} to regenerate its associated header file, e.g.@: | |
339 | @file{gcc/cp/cfns.h}. | |
340 | ||
341 | @item expect version ??? | |
342 | @itemx tcl version ??? | |
cfc984b5 | 343 | @itemx dejagnu version 1.4.4 (or later) |
67b1fbb9 KG |
344 | |
345 | Necessary to run the GCC testsuite. | |
346 | ||
347 | @item autogen version 5.5.4 (or later) and | |
348 | @itemx guile version 1.4.1 (or later) | |
349 | ||
350 | Necessary to regenerate @file{fixinc/fixincl.x} from | |
351 | @file{fixinc/inclhack.def} and @file{fixinc/*.tpl}. | |
352 | ||
353 | Necessary to run the @file{fixinc} @command{make check}. | |
354 | ||
ce5c1cf3 | 355 | Necessary to regenerate the top level @file{Makefile.in} file from |
67b1fbb9 KG |
356 | @file{Makefile.tpl} and @file{Makefile.def}. |
357 | ||
358 | @item GNU Bison version 1.28 (or later) | |
359 | Berkeley @command{yacc} (@command{byacc}) is also reported to work other | |
360 | than for java. | |
361 | ||
362 | Necessary when modifying @file{*.y} files. | |
363 | ||
364 | Necessary to build GCC during development because the generated output | |
365 | files are not included in the CVS repository. They are included in | |
366 | releases. | |
367 | ||
368 | @item Flex version 2.5.4 (or later) | |
369 | ||
370 | Necessary when modifying @file{*.l} files. | |
371 | ||
372 | Necessary to build GCC during development because the generated output | |
373 | files are not included in the CVS repository. They are included in | |
374 | releases. | |
375 | ||
376 | @item Texinfo version 4.2 (or later) | |
377 | ||
378 | Necessary for running @command{makeinfo} when modifying @file{*.texi} | |
379 | files to test your changes. | |
380 | ||
381 | Necessary to build GCC documentation during development because the | |
382 | generated output files are not included in the CVS repository. They are | |
383 | included in releases. | |
384 | ||
385 | @item @TeX{} (any working version) | |
386 | ||
387 | Necessary for running @command{texi2dvi}, used when running | |
388 | @command{make dvi} to create DVI files. | |
389 | ||
390 | @item cvs version 1.10 (or later) | |
391 | @itemx ssh (any version) | |
392 | ||
393 | Necessary to access the CVS repository. Public releases and weekly | |
394 | snapshots of the development sources are also available via FTP. | |
395 | ||
396 | @item perl version 5.6.1 (or later) | |
397 | ||
398 | Necessary when regenerating @file{Makefile} dependencies in libiberty. | |
4f3ce03f JM |
399 | Necessary when regenerating @file{libiberty/functions.texi}. |
400 | Necessary when generating manpages from Texinfo manuals. | |
401 | Used by various scripts to generate some files included in CVS (mainly | |
402 | Unicode-related and rarely changing) from source tables. | |
67b1fbb9 KG |
403 | |
404 | @item GNU diffutils version 2.7 (or later) | |
405 | ||
406 | Necessary when creating changes to GCC source code to submit for review. | |
407 | ||
408 | @item patch version 2.5.4 (or later) | |
409 | ||
410 | Necessary when applying patches, created with @command{diff}, to one's | |
411 | own sources. | |
412 | ||
413 | @end table | |
414 | ||
415 | @html | |
416 | <hr /> | |
417 | <p> | |
418 | @end html | |
419 | @ifhtml | |
420 | @uref{./index.html,,Return to the GCC Installation page} | |
421 | @end ifhtml | |
422 | @end ifset | |
423 | ||
f42974dc | 424 | @c ***Downloading the source************************************************** |
6cfb3f16 | 425 | @ifnothtml |
f42974dc | 426 | @comment node-name, next, previous, up |
67b1fbb9 | 427 | @node Downloading the source, Configuration, Prerequisites, Installing GCC |
6cfb3f16 | 428 | @end ifnothtml |
f42974dc | 429 | @ifset downloadhtml |
f42974dc DW |
430 | @ifnothtml |
431 | @chapter Downloading GCC | |
432 | @end ifnothtml | |
433 | @cindex Downloading GCC | |
434 | @cindex Downloading the Source | |
435 | ||
eea81d3e RO |
436 | GCC is distributed via @uref{http://gcc.gnu.org/cvs.html,,CVS} and FTP |
437 | tarballs compressed with @command{gzip} or | |
6cfb3f16 | 438 | @command{bzip2}. It is possible to download a full distribution or specific |
f42974dc DW |
439 | components. |
440 | ||
962e6e00 | 441 | Please refer to the @uref{http://gcc.gnu.org/releases.html,,releases web page} |
161d7b59 | 442 | for information on how to obtain GCC@. |
f42974dc | 443 | |
6de9cd9a DN |
444 | The full distribution includes the C, C++, Objective-C, Fortran 77, Fortran |
445 | (in case of GCC 3.5 and later), Java, and Ada (in case of GCC 3.1 and later) | |
446 | compilers. The full distribution also includes runtime libraries for C++, | |
447 | Objective-C, Fortran 77, Fortran, and Java. In GCC 3.0 and later versions, | |
448 | GNU compiler testsuites are also included in the full distribution. | |
f42974dc DW |
449 | |
450 | If you choose to download specific components, you must download the core | |
eea81d3e | 451 | GCC distribution plus any language specific distributions you wish to |
6c0a4eab | 452 | use. The core distribution includes the C language front end as well as the |
767094dd | 453 | shared components. Each language has a tarball which includes the language |
6c0a4eab | 454 | front end as well as the language runtime (when appropriate). |
f42974dc DW |
455 | |
456 | Unpack the core distribution as well as any language specific | |
457 | distributions in the same directory. | |
458 | ||
459 | If you also intend to build binutils (either to upgrade an existing | |
460 | installation or for use in place of the corresponding tools of your | |
461 | OS), unpack the binutils distribution either in the same directory or | |
462 | a separate one. In the latter case, add symbolic links to any | |
463 | components of the binutils you intend to build alongside the compiler | |
6cfb3f16 JM |
464 | (@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld}, |
465 | @file{opcodes}, @dots{}) to the directory containing the GCC sources. | |
f42974dc DW |
466 | |
467 | @html | |
b8db17af | 468 | <hr /> |
f42974dc DW |
469 | <p> |
470 | @end html | |
471 | @ifhtml | |
472 | @uref{./index.html,,Return to the GCC Installation page} | |
473 | @end ifhtml | |
474 | @end ifset | |
475 | ||
476 | @c ***Configuration*********************************************************** | |
6cfb3f16 | 477 | @ifnothtml |
f42974dc DW |
478 | @comment node-name, next, previous, up |
479 | @node Configuration, Building, Downloading the source, Installing GCC | |
6cfb3f16 | 480 | @end ifnothtml |
f42974dc | 481 | @ifset configurehtml |
f42974dc DW |
482 | @ifnothtml |
483 | @chapter Installing GCC: Configuration | |
484 | @end ifnothtml | |
485 | @cindex Configuration | |
486 | @cindex Installing GCC: Configuration | |
487 | ||
488 | Like most GNU software, GCC must be configured before it can be built. | |
489 | This document describes the recommended configuration procedure | |
490 | for both native and cross targets. | |
491 | ||
38209993 LG |
492 | We use @var{srcdir} to refer to the toplevel source directory for |
493 | GCC; we use @var{objdir} to refer to the toplevel build/object directory. | |
494 | ||
495 | If you obtained the sources via CVS, @var{srcdir} must refer to the top | |
496 | @file{gcc} directory, the one where the @file{MAINTAINERS} can be found, | |
497 | and not its @file{gcc} subdirectory, otherwise the build will fail. | |
f42974dc | 498 | |
b4b0fb02 RO |
499 | If either @var{srcdir} or @var{objdir} is located on an automounted NFS |
500 | file system, the shell's built-in @command{pwd} command will return | |
501 | temporary pathnames. Using these can lead to various sorts of build | |
502 | problems. To avoid this issue, set the @env{PWDCMD} environment | |
503 | variable to an automounter-aware @command{pwd} command, e.g., | |
7ba4ca63 | 504 | @command{pawd} or @samp{amq -w}, during the configuration and build |
b4b0fb02 RO |
505 | phases. |
506 | ||
102b60d1 GP |
507 | First, we @strong{highly} recommend that GCC be built into a |
508 | separate directory than the sources which does @strong{not} reside | |
509 | within the source tree. This is how we generally build GCC; building | |
510 | where @var{srcdir} == @var{objdir} should still work, but doesn't | |
511 | get extensive testing; building where @var{objdir} is a subdirectory | |
512 | of @var{srcdir} is unsupported. | |
f42974dc | 513 | |
eea81d3e | 514 | If you have previously built GCC in the same directory for a |
f85b8d1a | 515 | different target machine, do @samp{make distclean} to delete all files |
377dfc82 GP |
516 | that might be invalid. One of the files this deletes is @file{Makefile}; |
517 | if @samp{make distclean} complains that @file{Makefile} does not exist | |
518 | or issues a message like ``don't know how to make distclean'' it probably | |
519 | means that the directory is already suitably clean. However, with the | |
520 | recommended method of building in a separate @var{objdir}, you should | |
521 | simply use a different @var{objdir} for each target. | |
f85b8d1a | 522 | |
38209993 LG |
523 | Second, when configuring a native system, either @command{cc} or |
524 | @command{gcc} must be in your path or you must set @env{CC} in | |
df002c7d DE |
525 | your environment before running configure. Otherwise the configuration |
526 | scripts may fail. | |
f42974dc | 527 | |
eea81d3e RO |
528 | Note that the bootstrap compiler and the resulting GCC must be link |
529 | compatible, else the bootstrap will fail with linker errors about | |
530 | incompatible object file formats. Several multilibed targets are | |
e69aa433 GP |
531 | affected by this requirement, see |
532 | @ifnothtml | |
533 | @ref{Specific, host/target specific installation notes}. | |
534 | @end ifnothtml | |
c009f01f | 535 | @ifhtml |
e69aa433 | 536 | @uref{specific.html,,host/target specific installation notes}. |
c009f01f | 537 | @end ifhtml |
eea81d3e | 538 | |
f42974dc DW |
539 | To configure GCC: |
540 | ||
3ab51846 | 541 | @smallexample |
38209993 LG |
542 | % mkdir @var{objdir} |
543 | % cd @var{objdir} | |
eea81d3e | 544 | % @var{srcdir}/configure [@var{options}] [@var{target}] |
3ab51846 | 545 | @end smallexample |
f42974dc DW |
546 | |
547 | ||
ef88b07d | 548 | @heading Target specification |
f42974dc DW |
549 | @itemize @bullet |
550 | @item | |
38209993 | 551 | GCC has code to correctly determine the correct value for @var{target} |
f9047ed3 | 552 | for nearly all native systems. Therefore, we highly recommend you not |
f42974dc DW |
553 | provide a configure target when configuring a native compiler. |
554 | ||
555 | @item | |
6cfb3f16 | 556 | @var{target} must be specified as @option{--target=@var{target}} |
f9047ed3 | 557 | when configuring a cross compiler; examples of valid targets would be |
a4a4b1d3 | 558 | m68k-coff, sh-elf, etc. |
f42974dc DW |
559 | |
560 | @item | |
6cfb3f16 | 561 | Specifying just @var{target} instead of @option{--target=@var{target}} |
38209993 | 562 | implies that the host defaults to @var{target}. |
f42974dc DW |
563 | @end itemize |
564 | ||
565 | ||
ef88b07d | 566 | @heading Options specification |
f42974dc | 567 | |
ef88b07d | 568 | Use @var{options} to override several configure time options for |
7ba4ca63 | 569 | GCC@. A list of supported @var{options} follows; @samp{configure |
80f9249a JM |
570 | --help} may list other options, but those not listed below may not |
571 | work and should not normally be used. | |
f42974dc | 572 | |
c1c3bb0c ME |
573 | Note that each @option{--enable} option has a corresponding |
574 | @option{--disable} option and that each @option{--with} option has a | |
575 | corresponding @option{--without} option. | |
576 | ||
ef88b07d JM |
577 | @table @code |
578 | @item --prefix=@var{dirname} | |
579 | Specify the toplevel installation | |
f42974dc DW |
580 | directory. This is the recommended way to install the tools into a directory |
581 | other than the default. The toplevel installation directory defaults to | |
6cfb3f16 | 582 | @file{/usr/local}. |
f42974dc | 583 | |
38209993 | 584 | We @strong{highly} recommend against @var{dirname} being the same or a |
a7582c8c BE |
585 | subdirectory of @var{objdir} or vice versa. If specifying a directory |
586 | beneath a user's home directory tree, some shells will not expand | |
587 | @var{dirname} correctly if it contains the @samp{~} metacharacter; use | |
588 | @env{$HOME} instead. | |
f42974dc | 589 | |
8e5f33ff GK |
590 | The following standard @command{autoconf} options are supported. Normally you |
591 | should not need to use these options. | |
ef88b07d | 592 | @table @code |
ab130aa5 JM |
593 | @item --exec-prefix=@var{dirname} |
594 | Specify the toplevel installation directory for architecture-dependent | |
595 | files. The default is @file{@var{prefix}}. | |
596 | ||
597 | @item --bindir=@var{dirname} | |
598 | Specify the installation directory for the executables called by users | |
599 | (such as @command{gcc} and @command{g++}). The default is | |
600 | @file{@var{exec-prefix}/bin}. | |
601 | ||
602 | @item --libdir=@var{dirname} | |
603 | Specify the installation directory for object code libraries and | |
8e5f33ff GK |
604 | internal data files of GCC@. The default is @file{@var{exec-prefix}/lib}. |
605 | ||
606 | @item --libexecdir=@var{dirname} | |
607 | Specify the installation directory for internal executables of GCC@. | |
608 | The default is @file{@var{exec-prefix}/libexec}. | |
ab130aa5 JM |
609 | |
610 | @item --with-slibdir=@var{dirname} | |
611 | Specify the installation directory for the shared libgcc library. The | |
612 | default is @file{@var{libdir}}. | |
613 | ||
614 | @item --infodir=@var{dirname} | |
615 | Specify the installation directory for documentation in info format. | |
616 | The default is @file{@var{prefix}/info}. | |
617 | ||
8567c70f TT |
618 | @item --datadir=@var{dirname} |
619 | Specify the installation directory for some architecture-independent | |
620 | data files referenced by GCC@. The default is @file{@var{prefix}/share}. | |
621 | ||
ab130aa5 JM |
622 | @item --mandir=@var{dirname} |
623 | Specify the installation directory for manual pages. The default is | |
624 | @file{@var{prefix}/man}. (Note that the manual pages are only extracts from | |
8e9a4a45 | 625 | the full GCC manuals, which are provided in Texinfo format. The manpages |
ab130aa5 JM |
626 | are derived by an automatic conversion process from parts of the full |
627 | manual.) | |
628 | ||
ef88b07d JM |
629 | @item --with-gxx-include-dir=@var{dirname} |
630 | Specify | |
eea81d3e | 631 | the installation directory for G++ header files. The default is |
e0b24bce | 632 | @file{@var{prefix}/include/c++/@var{version}}. |
ecb7d6b3 | 633 | |
ef88b07d | 634 | @end table |
f42974dc | 635 | |
b21d216c AF |
636 | @item --program-prefix=@var{prefix} |
637 | GCC supports some transformations of the names of its programs when | |
638 | installing them. This option prepends @var{prefix} to the names of | |
639 | programs to install in @var{bindir} (see above). For example, specifying | |
640 | @option{--program-prefix=foo-} would result in @samp{gcc} | |
641 | being installed as @file{/usr/local/bin/foo-gcc}. | |
642 | ||
643 | @item --program-suffix=@var{suffix} | |
644 | Appends @var{suffix} to the names of programs to install in @var{bindir} | |
645 | (see above). For example, specifying @option{--program-suffix=-3.1} | |
646 | would result in @samp{gcc} being installed as | |
647 | @file{/usr/local/bin/gcc-3.1}. | |
648 | ||
649 | @item --program-transform-name=@var{pattern} | |
650 | Applies the @samp{sed} script @var{pattern} to be applied to the names | |
651 | of programs to install in @var{bindir} (see above). @var{pattern} has to | |
652 | consist of one or more basic @samp{sed} editing commands, separated by | |
653 | semicolons. For example, if you want the @samp{gcc} program name to be | |
654 | transformed to the installed program @file{/usr/local/bin/myowngcc} and | |
655 | the @samp{g++} program name to be transformed to | |
656 | @file{/usr/local/bin/gspecial++} without changing other program names, | |
657 | you could use the pattern | |
658 | @option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'} | |
659 | to achieve this effect. | |
660 | ||
661 | All three options can be combined and used together, resulting in more | |
662 | complex conversion patterns. As a basic rule, @var{prefix} (and | |
663 | @var{suffix}) are prepended (appended) before further transformations | |
664 | can happen with a special transformation script @var{pattern}. | |
665 | ||
8c085f6f | 666 | As currently implemented, this option only takes effect for native |
b21d216c | 667 | builds; cross compiler binaries' names are not transformed even when a |
8c085f6f | 668 | transformation is explicitly asked for by one of these options. |
b21d216c AF |
669 | |
670 | For native builds, some of the installed programs are also installed | |
671 | with the target alias in front of their name, as in | |
672 | @samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen | |
673 | before the target alias is prepended to the name - so, specifying | |
674 | @option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the | |
675 | resulting binary would be installed as | |
676 | @file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}. | |
677 | ||
8ecab453 | 678 | As a last shortcoming, none of the installed Ada programs are |
b21d216c AF |
679 | transformed yet, which will be fixed in some time. |
680 | ||
ef88b07d JM |
681 | @item --with-local-prefix=@var{dirname} |
682 | Specify the | |
6ac48571 JM |
683 | installation directory for local include files. The default is |
684 | @file{/usr/local}. Specify this option if you want the compiler to | |
685 | search directory @file{@var{dirname}/include} for locally installed | |
686 | header files @emph{instead} of @file{/usr/local/include}. | |
687 | ||
688 | You should specify @option{--with-local-prefix} @strong{only} if your | |
689 | site has a different convention (not @file{/usr/local}) for where to put | |
690 | site-specific files. | |
691 | ||
692 | The default value for @option{--with-local-prefix} is @file{/usr/local} | |
693 | regardless of the value of @option{--prefix}. Specifying | |
694 | @option{--prefix} has no effect on which directory GCC searches for | |
695 | local header files. This may seem counterintuitive, but actually it is | |
696 | logical. | |
697 | ||
698 | The purpose of @option{--prefix} is to specify where to @emph{install | |
699 | GCC}. The local header files in @file{/usr/local/include}---if you put | |
161d7b59 | 700 | any in that directory---are not part of GCC@. They are part of other |
6ac48571 JM |
701 | programs---perhaps many others. (GCC installs its own header files in |
702 | another directory which is based on the @option{--prefix} value.) | |
703 | ||
48209ce5 JDA |
704 | Both the local-prefix include directory and the GCC-prefix include |
705 | directory are part of GCC's "system include" directories. Although these | |
706 | two directories are not fixed, they need to be searched in the proper | |
707 | order for the correct processing of the include_next directive. The | |
708 | local-prefix include directory is searched before the GCC-prefix | |
709 | include directory. Another characteristic of system include directories | |
710 | is that pedantic warnings are turned off for headers in these directories. | |
711 | ||
712 | Some autoconf macros add @option{-I @var{directory}} options to the | |
713 | compiler command line, to ensure that directories containing installed | |
714 | packages' headers are searched. When @var{directory} is one of GCC's | |
715 | system include directories, GCC will ignore the option so that system | |
716 | directories continue to be processed in the correct order. This | |
717 | may result in a search order different from what was specified but the | |
718 | directory will still be searched. | |
719 | ||
720 | GCC automatically searches for ordinary libraries using | |
721 | @env{GCC_EXEC_PREFIX}. Thus, when the same installation prefix is | |
722 | used for both GCC and packages, GCC will automatically search for | |
723 | both headers and libraries. This provides a configuration that is | |
724 | easy to use. GCC behaves in a manner similar to that when it is | |
725 | installed as a system compiler in @file{/usr}. | |
726 | ||
727 | Sites that need to install multiple versions of GCC may not want to | |
728 | use the above simple configuration. It is possible to use the | |
729 | @option{--program-prefix}, @option{--program-suffix} and | |
730 | @option{--program-transform-name} options to install multiple versions | |
731 | into a single directory, but it may be simpler to use different prefixes | |
732 | and the @option{--with-local-prefix} option to specify the location of the | |
733 | site-specific files for each version. It will then be necessary for | |
734 | users to specify explicitly the location of local site libraries | |
735 | (e.g., with @env{LIBRARY_PATH}). | |
736 | ||
737 | The same value can be used for both @option{--with-local-prefix} and | |
738 | @option{--prefix} provided it is not @file{/usr}. This can be used | |
739 | to avoid the default search of @file{/usr/local/include}. | |
740 | ||
6ac48571 JM |
741 | @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}! |
742 | The directory you use for @option{--with-local-prefix} @strong{must not} | |
743 | contain any of the system's standard header files. If it did contain | |
744 | them, certain programs would be miscompiled (including GNU Emacs, on | |
745 | certain targets), because this would override and nullify the header | |
4c64396e | 746 | file corrections made by the @command{fixincludes} script. |
6ac48571 JM |
747 | |
748 | Indications are that people who use this option use it based on mistaken | |
749 | ideas of what it is for. People use it as if it specified where to | |
161d7b59 | 750 | install part of GCC@. Perhaps they make this assumption because |
6ac48571 JM |
751 | installing GCC creates the directory. |
752 | ||
6cfb3f16 | 753 | @item --enable-shared[=@var{package}[,@dots{}]] |
0cb98517 AO |
754 | Build shared versions of libraries, if shared libraries are supported on |
755 | the target platform. Unlike GCC 2.95.x and earlier, shared libraries | |
07659e97 | 756 | are enabled by default on all platforms that support shared libraries. |
0cb98517 AO |
757 | |
758 | If a list of packages is given as an argument, build shared libraries | |
759 | only for the listed packages. For other packages, only static libraries | |
760 | will be built. Package names currently recognized in the GCC tree are | |
761 | @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not | |
e22df315 | 762 | @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc}, |
07659e97 | 763 | @samp{ada}, @samp{libada}, @samp{libjava} and @samp{libobjc}. |
55c45226 | 764 | Note @samp{libiberty} does not support shared libraries at all. |
0cb98517 AO |
765 | |
766 | Use @option{--disable-shared} to build only static libraries. Note that | |
767 | @option{--disable-shared} does not accept a list of package names as | |
768 | argument, only @option{--enable-shared} does. | |
f42974dc | 769 | |
ef88b07d JM |
770 | @item @anchor{with-gnu-as}--with-gnu-as |
771 | Specify that the compiler should assume that the | |
767094dd | 772 | assembler it finds is the GNU assembler. However, this does not modify |
377dfc82 GP |
773 | the rules to find an assembler and will result in confusion if the |
774 | assembler found is not actually the GNU assembler. (Confusion may also | |
8c26c999 JM |
775 | result if the compiler finds the GNU assembler but has not been |
776 | configured with @option{--with-gnu-as}.) If you have more than one | |
38209993 | 777 | assembler installed on your system, you may want to use this option in |
eea81d3e | 778 | connection with @option{--with-as=@var{pathname}}. |
38209993 | 779 | |
8c085f6f JJ |
780 | The following systems are the only ones where it makes a difference |
781 | whether you use the GNU assembler. On any other system, | |
782 | @option{--with-gnu-as} has no effect. | |
783 | ||
2ff16718 | 784 | @itemize @bullet |
8c085f6f JJ |
785 | @item @samp{hppa1.0-@var{any}-@var{any}} |
786 | @item @samp{hppa1.1-@var{any}-@var{any}} | |
787 | @item @samp{i386-@var{any}-sysv} | |
8c085f6f JJ |
788 | @item @samp{m68k-bull-sysv} |
789 | @item @samp{m68k-hp-hpux} | |
8c085f6f JJ |
790 | @item @samp{m68000-hp-hpux} |
791 | @item @samp{m68000-att-sysv} | |
8f2afc21 EB |
792 | @item @samp{sparc-sun-solaris2.@var{any}} |
793 | @item @samp{sparc64-@var{any}-solaris2.@var{any}} | |
8c085f6f | 794 | @end itemize |
8c26c999 | 795 | |
8f2afc21 | 796 | On the systems listed above (except for the HP-PA, the SPARC, for ISC on |
82563d35 RS |
797 | the 386, if you use the GNU assembler, you should also use the GNU linker |
798 | (and specify @option{--with-gnu-ld}). | |
8c26c999 | 799 | |
8f2afc21 | 800 | @item @anchor{with-as}--with-as=@var{pathname} |
ef88b07d | 801 | Specify that the |
38209993 LG |
802 | compiler should use the assembler pointed to by @var{pathname}, rather |
803 | than the one found by the standard rules to find an assembler, which | |
804 | are: | |
f42974dc DW |
805 | @itemize @bullet |
806 | @item | |
8e5f33ff GK |
807 | Check the @file{@var{libexec}/gcc/@var{target}/@var{version}} |
808 | directory, where @var{libexec} defaults to | |
809 | @file{@var{exec-prefix}/libexec} and @var{exec-prefix} defaults to | |
810 | @var{prefix} which defaults to @file{/usr/local} unless overridden by | |
811 | the @option{--prefix=@var{pathname}} switch described | |
812 | above. @var{target} is the target system triple, such as | |
813 | @samp{sparc-sun-solaris2.7}, and @var{version} denotes the GCC | |
814 | version, such as 3.0. | |
f42974dc | 815 | @item |
e979f9e8 | 816 | Check operating system specific directories (e.g.@: @file{/usr/ccs/bin} on |
250d5688 | 817 | Sun Solaris 2). |
f42974dc | 818 | @end itemize |
767094dd | 819 | Note that these rules do not check for the value of @env{PATH}. You may |
38209993 LG |
820 | want to use @option{--with-as} if no assembler is installed in the |
821 | directories listed above, or if you have multiple assemblers installed | |
822 | and want to choose one that is not found by the above rules. | |
f42974dc | 823 | |
ef88b07d JM |
824 | @item @anchor{with-gnu-ld}--with-gnu-ld |
825 | Same as @uref{#with-gnu-as,,@option{--with-gnu-as}} | |
8f2afc21 | 826 | but for the linker. |
f42974dc | 827 | |
eea81d3e | 828 | @item --with-ld=@var{pathname} |
8f2afc21 EB |
829 | Same as @uref{#with-as,,@option{--with-as}} |
830 | but for the linker. | |
f42974dc | 831 | |
ef88b07d JM |
832 | @item --with-stabs |
833 | Specify that stabs debugging | |
38209993 LG |
834 | information should be used instead of whatever format the host normally |
835 | uses. Normally GCC uses the same debug format as the host system. | |
f42974dc | 836 | |
8c26c999 JM |
837 | On MIPS based systems and on Alphas, you must specify whether you want |
838 | GCC to create the normal ECOFF debugging format, or to use BSD-style | |
839 | stabs passed through the ECOFF symbol table. The normal ECOFF debug | |
161d7b59 JM |
840 | format cannot fully handle languages other than C@. BSD stabs format can |
841 | handle other languages, but it only works with the GNU debugger GDB@. | |
8c26c999 JM |
842 | |
843 | Normally, GCC uses the ECOFF debugging format by default; if you | |
161d7b59 | 844 | prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@. |
8c26c999 JM |
845 | |
846 | No matter which default you choose when you configure GCC, the user | |
847 | can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly | |
848 | the debug format for a particular compilation. | |
849 | ||
850 | @option{--with-stabs} is meaningful on the ISC system on the 386, also, if | |
851 | @option{--with-gas} is used. It selects use of stabs debugging | |
852 | information embedded in COFF output. This kind of debugging information | |
853 | supports C++ well; ordinary COFF debugging information does not. | |
854 | ||
855 | @option{--with-stabs} is also meaningful on 386 systems running SVR4. It | |
856 | selects use of stabs debugging information embedded in ELF output. The | |
857 | C++ compiler currently (2.6.0) does not support the DWARF debugging | |
858 | information normally used on 386 SVR4 platforms; stabs provide a | |
859 | workable alternative. This requires gas and gdb, as the normal SVR4 | |
860 | tools can not generate or interpret stabs. | |
861 | ||
eea81d3e | 862 | @item --disable-multilib |
ef88b07d | 863 | Specify that multiple target |
eea81d3e RO |
864 | libraries to support different target variants, calling |
865 | conventions, etc should not be built. The default is to build a | |
866 | predefined set of them. | |
f42974dc | 867 | |
e8515283 DE |
868 | Some targets provide finer-grained control over which multilibs are built |
869 | (e.g., @option{--disable-softfloat}): | |
870 | @table @code | |
e8515283 DE |
871 | @item arc-*-elf* |
872 | biendian. | |
873 | ||
874 | @item arm-*-* | |
875 | fpu, 26bit, underscore, interwork, biendian, nofmult. | |
876 | ||
877 | @item m68*-*-* | |
878 | softfloat, m68881, m68000, m68020. | |
879 | ||
880 | @item mips*-*-* | |
881 | single-float, biendian, softfloat. | |
882 | ||
883 | @item powerpc*-*-*, rs6000*-*-* | |
884 | aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian, | |
f282ffb3 | 885 | sysv, aix. |
e8515283 DE |
886 | |
887 | @end table | |
888 | ||
ef88b07d JM |
889 | @item --enable-threads |
890 | Specify that the target | |
38209993 LG |
891 | supports threads. This affects the Objective-C compiler and runtime |
892 | library, and exception handling for other languages like C++ and Java. | |
6ac48571 | 893 | On some systems, this is the default. |
f42974dc | 894 | |
f6160ed5 LR |
895 | In general, the best (and, in many cases, the only known) threading |
896 | model available will be configured for use. Beware that on some | |
2dd76960 | 897 | systems, GCC has not been taught what threading models are generally |
3c6bb1db LR |
898 | available for the system. In this case, @option{--enable-threads} is an |
899 | alias for @option{--enable-threads=single}. | |
f6160ed5 LR |
900 | |
901 | @item --disable-threads | |
902 | Specify that threading support should be disabled for the system. | |
3c6bb1db | 903 | This is an alias for @option{--enable-threads=single}. |
f6160ed5 | 904 | |
ef88b07d JM |
905 | @item --enable-threads=@var{lib} |
906 | Specify that | |
38209993 LG |
907 | @var{lib} is the thread support library. This affects the Objective-C |
908 | compiler and runtime library, and exception handling for other languages | |
f85b8d1a JM |
909 | like C++ and Java. The possibilities for @var{lib} are: |
910 | ||
911 | @table @code | |
912 | @item aix | |
913 | AIX thread support. | |
914 | @item dce | |
915 | DCE thread support. | |
4c80872c RK |
916 | @item gnat |
917 | Ada tasking support. For non-Ada programs, this setting is equivalent | |
918 | to @samp{single}. When used in conjunction with the Ada run time, it | |
919 | causes GCC to use the same thread primitives as Ada uses. This option | |
920 | is necessary when using both Ada and the back end exception handling, | |
921 | which is the default for most Ada targets. | |
f85b8d1a | 922 | @item mach |
eea81d3e | 923 | Generic MACH thread support, known to work on NeXTSTEP@. (Please note |
3c6bb1db | 924 | that the file needed to support this configuration, @file{gthr-mach.h}, is |
f6160ed5 LR |
925 | missing and thus this setting will cause a known bootstrap failure.) |
926 | @item no | |
927 | This is an alias for @samp{single}. | |
f85b8d1a | 928 | @item posix |
c771326b | 929 | Generic POSIX thread support. |
f6160ed5 LR |
930 | @item rtems |
931 | RTEMS thread support. | |
f85b8d1a JM |
932 | @item single |
933 | Disable thread support, should work for all platforms. | |
934 | @item solaris | |
eea81d3e | 935 | Sun Solaris 2 thread support. |
f85b8d1a JM |
936 | @item vxworks |
937 | VxWorks thread support. | |
938 | @item win32 | |
939 | Microsoft Win32 API thread support. | |
61fec9ff JB |
940 | @item nks |
941 | Novell Kernel Services thread support. | |
f85b8d1a | 942 | @end table |
f42974dc | 943 | |
ef88b07d | 944 | @item --with-cpu=@var{cpu} |
7816bea0 DJ |
945 | Specify which cpu variant the compiler should generate code for by default. |
946 | @var{cpu} will be used as the default value of the @option{-mcpu=} switch. | |
947 | This option is only supported on some targets, including ARM, i386, PowerPC, | |
948 | and SPARC@. | |
949 | ||
950 | @item --with-schedule=@var{cpu} | |
951 | @itemx --with-arch=@var{cpu} | |
952 | @itemx --with-tune=@var{cpu} | |
953 | @itemx --with-abi=@var{abi} | |
9b66ebb1 | 954 | @itemx --with-fpu=@var{type} |
7816bea0 DJ |
955 | @itemx --with-float=@var{type} |
956 | These configure options provide default values for the @option{-mschedule=}, | |
9b66ebb1 PB |
957 | @option{-march=}, @option{-mtune=}, @option{-mabi=}, and @option{-mfpu=} |
958 | options and for @option{-mhard-float} or @option{-msoft-float}. As with | |
959 | @option{--with-cpu}, which switches will be accepted and acceptable values | |
960 | of the arguments depend on the target. | |
f42974dc | 961 | |
a004eb82 AH |
962 | @item --enable-altivec |
963 | Specify that the target supports AltiVec vector enhancements. This | |
964 | option will adjust the ABI for AltiVec enhancements, as well as generate | |
965 | AltiVec code when appropriate. This option is only available for | |
966 | PowerPC systems. | |
967 | ||
354b7da5 DH |
968 | @item --enable-__cxa_atexit |
969 | Define if you want to use __cxa_atexit, rather than atexit, to | |
970 | register C++ destructors for local statics and global objects. | |
971 | This is essential for fully standards-compliant handling of | |
972 | destructors, but requires __cxa_atexit in libc. This option is currently | |
e53e0c56 | 973 | only available on systems with GNU libc. When enabled, this will cause |
354b7da5 DH |
974 | @option{-fuse-cxa-exit} to be passed by default. |
975 | ||
ef88b07d JM |
976 | @item --enable-target-optspace |
977 | Specify that target | |
38209993 LG |
978 | libraries should be optimized for code space instead of code speed. |
979 | This is the default for the m32r platform. | |
f42974dc | 980 | |
ab130aa5 JM |
981 | @item --disable-cpp |
982 | Specify that a user visible @command{cpp} program should not be installed. | |
983 | ||
984 | @item --with-cpp-install-dir=@var{dirname} | |
985 | Specify that the user visible @command{cpp} program should be installed | |
986 | in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}. | |
f42974dc | 987 | |
07cf4226 DM |
988 | @item --enable-initfini-array |
989 | Force the use of sections @code{.init_array} and @code{.fini_array} | |
990 | (instead of @code{.init} and @code{.fini}) for constructors and | |
991 | destructors. Option @option{--disable-initfini-array} has the | |
992 | opposite effect. If neither option is specified, the configure script | |
993 | will try to guess whether the @code{.init_array} and | |
994 | @code{.fini_array} sections are supported and, if they are, use them. | |
995 | ||
ef88b07d JM |
996 | @item --enable-maintainer-mode |
997 | The build rules that | |
6cfb3f16 | 998 | regenerate the GCC master message catalog @file{gcc.pot} are normally |
767094dd JM |
999 | disabled. This is because it can only be rebuilt if the complete source |
1000 | tree is present. If you have changed the sources and want to rebuild the | |
6ac48571 | 1001 | catalog, configuring with @option{--enable-maintainer-mode} will enable |
767094dd | 1002 | this. Note that you need a recent version of the @code{gettext} tools |
6ac48571 JM |
1003 | to do so. |
1004 | ||
51b9ff45 KC |
1005 | @item --enable-generated-files-in-srcdir |
1006 | Neither the .c and .h files that are generated from bison and flex nor the | |
1007 | info manuals and man pages that are built from the .texi files are present | |
1008 | in the CVS development tree. When building GCC from that development tree, | |
1009 | or from a snapshot which are created from CVS, then those generated files | |
1010 | are placed in your build directory, which allows for the source to be in a | |
1011 | readonly directory. | |
1012 | ||
1013 | If you configure with @option{--enable-generated-files-in-srcdir} then those | |
1014 | generated files will go into the source directory. This is mainly intended | |
1015 | for generating release or prerelease tarballs of the GCC sources, since it | |
1016 | is not a requirement that the users of source releases to have flex, bison, or | |
daf2f129 | 1017 | makeinfo. |
51b9ff45 | 1018 | |
ef88b07d JM |
1019 | @item --enable-version-specific-runtime-libs |
1020 | Specify | |
38209993 | 1021 | that runtime libraries should be installed in the compiler specific |
8e5f33ff GK |
1022 | subdirectory (@file{@var{libdir}/gcc}) rather than the usual places. In |
1023 | addition, @samp{libstdc++}'s include files will be installed into | |
1024 | @file{@var{libdir}} unless you overruled it by using | |
6cfb3f16 | 1025 | @option{--with-gxx-include-dir=@var{dirname}}. Using this option is |
38209993 | 1026 | particularly useful if you intend to use several versions of GCC in |
b9034bbd AJ |
1027 | parallel. This is currently supported by @samp{libgfortran}, |
1028 | @samp{libjava}, @samp{libmudflap}, @samp{libstdc++}, and @samp{libobjc}. | |
1029 | ||
38209993 | 1030 | |
ef88b07d JM |
1031 | @item --enable-languages=@var{lang1},@var{lang2},@dots{} |
1032 | Specify that only a particular subset of compilers and | |
767094dd | 1033 | their runtime libraries should be built. For a list of valid values for |
6cfb3f16 | 1034 | @var{langN} you can issue the following command in the |
eea81d3e | 1035 | @file{gcc} directory of your GCC source tree:@* |
3ab51846 | 1036 | @smallexample |
eea81d3e | 1037 | grep language= */config-lang.in |
3ab51846 | 1038 | @end smallexample |
eea81d3e | 1039 | Currently, you can use any of the following: |
6de9cd9a | 1040 | @code{ada}, @code{c}, @code{c++}, @code{f77}, @code{f95}, @code{java}, |
46e34f96 | 1041 | @code{objc}, @code{obj-c++}. |
8ecab453 | 1042 | Building the Ada compiler has special requirements, see below.@* |
38209993 | 1043 | If you do not pass this flag, all languages available in the @file{gcc} |
6cfb3f16 | 1044 | sub-tree will be configured. Re-defining @code{LANGUAGES} when calling |
ef88b07d | 1045 | @samp{make bootstrap} @strong{does not} work anymore, as those |
38209993 | 1046 | language sub-directories might not have been configured! |
f42974dc | 1047 | |
cd271054 AC |
1048 | @item --disable-libada |
1049 | Specify that the run-time libraries and tools used by GNAT should not | |
1050 | be built. This can be useful for debugging, or for compatibility with | |
c2910edf | 1051 | previous Ada build procedures, when it was required to explicitly |
cd271054 AC |
1052 | do a @samp{make -C gcc gnatlib_and_tools}. |
1053 | ||
ef88b07d JM |
1054 | @item --with-dwarf2 |
1055 | Specify that the compiler should | |
eea81d3e | 1056 | use DWARF 2 debugging information as the default. |
f85b8d1a JM |
1057 | |
1058 | @item --enable-win32-registry | |
eea81d3e | 1059 | @itemx --enable-win32-registry=@var{key} |
f85b8d1a | 1060 | @itemx --disable-win32-registry |
95fef11f | 1061 | The @option{--enable-win32-registry} option enables Microsoft Windows-hosted GCC |
f85b8d1a JM |
1062 | to look up installations paths in the registry using the following key: |
1063 | ||
1064 | @smallexample | |
eea81d3e | 1065 | @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}} |
f85b8d1a JM |
1066 | @end smallexample |
1067 | ||
eea81d3e RO |
1068 | @var{key} defaults to GCC version number, and can be overridden by the |
1069 | @option{--enable-win32-registry=@var{key}} option. Vendors and distributors | |
f85b8d1a JM |
1070 | who use custom installers are encouraged to provide a different key, |
1071 | perhaps one comprised of vendor name and GCC version number, to | |
767094dd | 1072 | avoid conflict with existing installations. This feature is enabled |
6cfb3f16 | 1073 | by default, and can be disabled by @option{--disable-win32-registry} |
f85b8d1a JM |
1074 | option. This option has no effect on the other hosts. |
1075 | ||
1076 | @item --nfp | |
1077 | Specify that the machine does not have a floating point unit. This | |
c9693e96 LH |
1078 | option only applies to @samp{m68k-sun-sunos@var{n}}. On any other |
1079 | system, @option{--nfp} has no effect. | |
f85b8d1a | 1080 | |
dd859b8a KG |
1081 | @item --enable-werror |
1082 | @itemx --disable-werror | |
1083 | @itemx --enable-werror=yes | |
1084 | @itemx --enable-werror=no | |
1085 | When you specify this option, it controls whether certain files in the | |
1086 | compiler are built with @option{-Werror} in bootstrap stage2 and later. | |
1087 | If you don't specify it, @option{-Werror} is turned on for the main | |
1088 | development trunk. However it defaults to off for release branches and | |
1089 | final releases. The specific files which get @option{-Werror} are | |
1090 | controlled by the Makefiles. | |
1091 | ||
f85b8d1a JM |
1092 | @item --enable-checking |
1093 | @itemx --enable-checking=@var{list} | |
1094 | When you specify this option, the compiler is built to perform checking | |
1095 | of tree node types when referencing fields of that node, and some other | |
1096 | internal consistency checks. This does not change the generated code, | |
1097 | but adds error checking within the compiler. This will slow down the | |
1098 | compiler and may only work properly if you are building the compiler | |
161d7b59 | 1099 | with GCC@. This is on by default when building from CVS or snapshots, |
f85b8d1a JM |
1100 | but off for releases. More control over the checks may be had by |
1101 | specifying @var{list}; the categories of checks available are | |
e1bbfc5c NS |
1102 | @samp{release}, @samp{assert}, @samp{misc}, @samp{tree}, @samp{gc}, |
1103 | @samp{rtl}, @samp{rtlflag}, @samp{fold}, @samp{gcac} and | |
1104 | @samp{valgrind}. The @samp{release} category enables only those checks | |
1105 | suitable for release builds, currently this is just @samp{assert}. The | |
1106 | check @samp{valgrind} requires the external @command{valgrind} | |
1107 | simulator, available from @uref{http://valgrind.kde.org/}. The checks | |
1108 | @samp{rtl}, @samp{gcac} and @samp{valgrind} are very expensive. The | |
1109 | default when @var{list} is not specified is | |
1110 | @samp{assert,misc,tree,gc,rtlflag}. That is also the default for | |
1111 | development builds, when @samp{--enable-checking} is not specified. For | |
1112 | release builds the default, when @samp{--enable-checking} is not given, | |
1113 | is @samp{release}. To disable all checking, @samp{--disable-checking} | |
1114 | must be explicitly requested. Disabling assertions will make the | |
1115 | compiler slightly faster but increase the risk of undetected internal | |
1116 | errors causing wrong code to be generated. | |
f85b8d1a | 1117 | |
22aa533e | 1118 | @item --enable-coverage |
31775d31 | 1119 | @itemx --enable-coverage=@var{level} |
22aa533e NS |
1120 | With this option, the compiler is built to collect self coverage |
1121 | information, every time it is run. This is for internal development | |
1122 | purposes, and only works when the compiler is being built with gcc. The | |
1123 | @var{level} argument controls whether the compiler is built optimized or | |
1124 | not, values are @samp{opt} and @samp{noopt}. For coverage analysis you | |
1125 | want to disable optimization, for performance analysis you want to | |
1126 | enable optimization. When coverage is enabled, the default level is | |
1127 | without optimization. | |
1128 | ||
439a7e54 | 1129 | @item --enable-gather-detailed-mem-stats |
95ea367d | 1130 | When this option is specified more detailed information on memory |
439a7e54 | 1131 | allocation is gathered. This information is printed when using |
daf2f129 | 1132 | @option{-fmem-report}. |
439a7e54 | 1133 | |
f85b8d1a JM |
1134 | @item --enable-nls |
1135 | @itemx --disable-nls | |
6cfb3f16 | 1136 | The @option{--enable-nls} option enables Native Language Support (NLS), |
f85b8d1a | 1137 | which lets GCC output diagnostics in languages other than American |
767094dd | 1138 | English. Native Language Support is enabled by default if not doing a |
161d7b59 | 1139 | canadian cross build. The @option{--disable-nls} option disables NLS@. |
f85b8d1a JM |
1140 | |
1141 | @item --with-included-gettext | |
c771326b | 1142 | If NLS is enabled, the @option{--with-included-gettext} option causes the build |
021c4bfd | 1143 | procedure to prefer its copy of GNU @command{gettext}. |
f85b8d1a JM |
1144 | |
1145 | @item --with-catgets | |
1146 | If NLS is enabled, and if the host lacks @code{gettext} but has the | |
1147 | inferior @code{catgets} interface, the GCC build procedure normally | |
1148 | ignores @code{catgets} and instead uses GCC's copy of the GNU | |
6cfb3f16 | 1149 | @code{gettext} library. The @option{--with-catgets} option causes the |
f85b8d1a | 1150 | build procedure to use the host's @code{catgets} in this situation. |
80f9249a | 1151 | |
5304400d CR |
1152 | @item --with-libiconv-prefix=@var{dir} |
1153 | Search for libiconv header files in @file{@var{dir}/include} and | |
1154 | libiconv library files in @file{@var{dir}/lib}. | |
1155 | ||
9340544b ZW |
1156 | @item --enable-obsolete |
1157 | Enable configuration for an obsoleted system. If you attempt to | |
1158 | configure GCC for a system (build, host, or target) which has been | |
1159 | obsoleted, and you do not specify this flag, configure will halt with an | |
1160 | error message. | |
1161 | ||
1162 | All support for systems which have been obsoleted in one release of GCC | |
1163 | is removed entirely in the next major release, unless someone steps | |
1164 | forward to maintain the port. | |
ef88b07d | 1165 | @end table |
f42974dc | 1166 | |
c1c3bb0c ME |
1167 | @subheading Cross-Compiler-Specific Options |
1168 | The following options only apply to building cross compilers. | |
ef88b07d | 1169 | @table @code |
4977bab6 ZW |
1170 | @item --with-sysroot |
1171 | @itemx --with-sysroot=@var{dir} | |
1172 | Tells GCC to consider @var{dir} as the root of a tree that contains a | |
1173 | (subset of) the root filesystem of the target operating system. | |
1174 | Target system headers, libraries and run-time object files will be | |
1175 | searched in there. The specified directory is not copied into the | |
1176 | install tree, unlike the options @option{--with-headers} and | |
1177 | @option{--with-libs} that this option obsoletes. The default value, | |
1178 | in case @option{--with-sysroot} is not given an argument, is | |
047d636f DJ |
1179 | @option{$@{gcc_tooldir@}/sys-root}. If the specified directory is a |
1180 | subdirectory of @option{$@{exec_prefix@}}, then it will be found relative to | |
1181 | the GCC binaries if the installation tree is moved. | |
4977bab6 | 1182 | |
65a824f6 JT |
1183 | @item --with-headers |
1184 | @itemx --with-headers=@var{dir} | |
4977bab6 | 1185 | Deprecated in favor of @option{--with-sysroot}. |
65a824f6 JT |
1186 | Specifies that target headers are available when building a cross compiler. |
1187 | The @var{dir} argument specifies a directory which has the target include | |
1188 | files. These include files will be copied into the @file{gcc} install | |
1189 | directory. @emph{This option with the @var{dir} argument is required} when | |
1190 | building a cross compiler, if @file{@var{prefix}/@var{target}/sys-include} | |
1191 | doesn't pre-exist. If @file{@var{prefix}/@var{target}/sys-include} does | |
1192 | pre-exist, the @var{dir} argument may be omitted. @command{fixincludes} | |
1193 | will be run on these files to make them compatible with GCC. | |
264d65c1 AP |
1194 | |
1195 | @item --without-headers | |
1196 | Tells GCC not use any target headers from a libc when building a cross | |
2dd76960 | 1197 | compiler. When crossing to GNU/Linux, you need the headers so GCC |
264d65c1 AP |
1198 | can build the exception handling for libgcc. |
1199 | See @uref{http://www.objsw.com/CrossGCC/,,CrossGCC} for more information | |
1200 | on this option. | |
1201 | ||
65a824f6 JT |
1202 | @item --with-libs |
1203 | @itemx --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}'' | |
4977bab6 | 1204 | Deprecated in favor of @option{--with-sysroot}. |
38209993 LG |
1205 | Specifies a list of directories which contain the target runtime |
1206 | libraries. These libraries will be copied into the @file{gcc} install | |
65a824f6 JT |
1207 | directory. If the directory list is omitted, this option has no |
1208 | effect. | |
ef88b07d | 1209 | @item --with-newlib |
eea81d3e | 1210 | Specifies that @samp{newlib} is |
38209993 | 1211 | being used as the target C library. This causes @code{__eprintf} to be |
eea81d3e RO |
1212 | omitted from @file{libgcc.a} on the assumption that it will be provided by |
1213 | @samp{newlib}. | |
ef88b07d | 1214 | @end table |
f9047ed3 | 1215 | |
bda4d063 TS |
1216 | @subheading Fortran-specific Option |
1217 | ||
1218 | The following options apply to the build of the Fortran front end. | |
1219 | ||
1220 | @table @code | |
1221 | ||
1222 | @item --with-gmp=@var{pathname} | |
bebf829d | 1223 | @itemx --with-mpfr=@var{pathname} |
bda4d063 | 1224 | @itemx --with-gmp-dir=@var{pathname} |
bebf829d PB |
1225 | @itemx --with-mpfr-dir=@var{pathname} |
1226 | If you don't have GMP (the GNU Multiple Precision library) and the MPFR | |
1227 | Libraries installed in a standard location and you want to build the Fortran | |
1228 | front-end, you can explicitly specify the directory where they are installed | |
1229 | (@samp{--with-gmp=gmpinstalldir}, @samp{--with-mpfr=mpfrinstalldir}) or where | |
1230 | you built them without installing (@samp{--with-gmp-dir=gmpbuilddir}, | |
1231 | @samp{--with-mpfr-dir=gmpbuilddir}). | |
bda4d063 TS |
1232 | |
1233 | @end table | |
1234 | ||
c1c3bb0c ME |
1235 | @subheading Java-Specific Options |
1236 | ||
1237 | The following option applies to the build of the Java front end. | |
1238 | ||
1239 | @table @code | |
1240 | @item --disable-libgcj | |
1241 | Specify that the run-time libraries | |
1242 | used by GCJ should not be built. This is useful in case you intend | |
1243 | to use GCJ with some other run-time, or you're going to install it | |
1244 | separately, or it just happens not to build on your particular | |
1245 | machine. In general, if the Java front end is enabled, the GCJ | |
1246 | libraries will be enabled too, unless they're known to not work on | |
1247 | the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you | |
1248 | may need to port it; in this case, before modifying the top-level | |
1249 | @file{configure.in} so that @samp{libgcj} is enabled by default on this platform, | |
1250 | you may use @option{--enable-libgcj} to override the default. | |
1251 | ||
1252 | @end table | |
1253 | ||
1254 | The following options apply to building @samp{libgcj}. | |
1255 | ||
1256 | @subsubheading General Options | |
1257 | ||
1258 | @table @code | |
1259 | @item --disable-getenv-properties | |
1260 | Don't set system properties from @env{GCJ_PROPERTIES}. | |
1261 | ||
1262 | @item --enable-hash-synchronization | |
1263 | Use a global hash table for monitor locks. Ordinarily, | |
1264 | @samp{libgcj}'s @samp{configure} script automatically makes | |
1265 | the correct choice for this option for your platform. Only use | |
1266 | this if you know you need the library to be configured differently. | |
1267 | ||
1268 | @item --enable-interpreter | |
1269 | Enable the Java interpreter. The interpreter is automatically | |
1270 | enabled by default on all platforms that support it. This option | |
1271 | is really only useful if you want to disable the interpreter | |
1272 | (using @option{--disable-interpreter}). | |
1273 | ||
1274 | @item --disable-java-net | |
1275 | Disable java.net. This disables the native part of java.net only, | |
1276 | using non-functional stubs for native method implementations. | |
1277 | ||
1278 | @item --disable-jvmpi | |
1279 | Disable JVMPI support. | |
1280 | ||
1281 | @item --with-ecos | |
1282 | Enable runtime eCos target support. | |
1283 | ||
1284 | @item --without-libffi | |
1285 | Don't use @samp{libffi}. This will disable the interpreter and JNI | |
1286 | support as well, as these require @samp{libffi} to work. | |
1287 | ||
1288 | @item --enable-libgcj-debug | |
1289 | Enable runtime debugging code. | |
1290 | ||
1291 | @item --enable-libgcj-multifile | |
1292 | If specified, causes all @file{.java} source files to be | |
1293 | compiled into @file{.class} files in one invocation of | |
1294 | @samp{gcj}. This can speed up build time, but is more | |
1295 | resource-intensive. If this option is unspecified or | |
1296 | disabled, @samp{gcj} is invoked once for each @file{.java} | |
1297 | file to compile into a @file{.class} file. | |
1298 | ||
1299 | @item --with-libiconv-prefix=DIR | |
1300 | Search for libiconv in @file{DIR/include} and @file{DIR/lib}. | |
1301 | ||
1302 | @item --enable-sjlj-exceptions | |
1303 | Force use of @code{builtin_setjmp} for exceptions. @samp{configure} | |
1304 | ordinarily picks the correct value based on the platform. Only use | |
1305 | this option if you are sure you need a different setting. | |
1306 | ||
1307 | @item --with-system-zlib | |
1308 | Use installed @samp{zlib} rather than that included with GCC@. | |
1309 | ||
1310 | @item --with-win32-nlsapi=ansi, unicows or unicode | |
1311 | Indicates how MinGW @samp{libgcj} translates between UNICODE | |
1312 | characters and the Win32 API. | |
1313 | @table @code | |
1314 | @item ansi | |
1315 | Use the single-byte @code{char} and the Win32 A functions natively, | |
1316 | translating to and from UNICODE when using these functions. If | |
1317 | unspecified, this is the default. | |
1318 | ||
1319 | @item unicows | |
1320 | Use the @code{WCHAR} and Win32 W functions natively. Adds | |
1321 | @code{-lunicows} to @file{libgcj.spec} to link with @samp{libunicows}. | |
1322 | @file{unicows.dll} needs to be deployed on Microsoft Windows 9X machines | |
1323 | running built executables. @file{libunicows.a}, an open-source | |
1324 | import library around Microsoft's @code{unicows.dll}, is obtained from | |
1325 | @uref{http://libunicows.sourceforge.net/}, which also gives details | |
1326 | on getting @file{unicows.dll} from Microsoft. | |
1327 | ||
1328 | @item unicode | |
1329 | Use the @code{WCHAR} and Win32 W functions natively. Does @emph{not} | |
1330 | add @code{-lunicows} to @file{libgcj.spec}. The built executables will | |
1331 | only run on Microsoft Windows NT and above. | |
1332 | @end table | |
1333 | @end table | |
1334 | ||
1335 | @subsubheading AWT-Specific Options | |
1336 | ||
1337 | @table @code | |
1338 | @item --with-x | |
1339 | Use the X Window System. | |
1340 | ||
1341 | @item --enable-java-awt=PEER(S) | |
1342 | Specifies the AWT peer library or libraries to build alongside | |
1343 | @samp{libgcj}. If this option is unspecified or disabled, AWT | |
1344 | will be non-functional. Current valid values are @option{gtk} and | |
1345 | @option{xlib}. Multiple libraries should be separated by a | |
1346 | comma (i.e. @option{--enable-java-awt=gtk,xlib}). | |
1347 | ||
1348 | @item --enable-gtk-cairo | |
1349 | Build the cairo Graphics2D implementation on GTK. | |
1350 | ||
1351 | @item --enable-java-gc=TYPE | |
1352 | Choose garbage collector. Defaults to @option{boehm} if unspecified. | |
1353 | ||
1354 | @item --disable-gtktest | |
1355 | Do not try to compile and run a test GTK+ program. | |
1356 | ||
1357 | @item --disable-glibtest | |
1358 | Do not try to compile and run a test GLIB program. | |
1359 | ||
1360 | @item --with-libart-prefix=PFX | |
1361 | Prefix where libart is installed (optional). | |
1362 | ||
1363 | @item --with-libart-exec-prefix=PFX | |
1364 | Exec prefix where libart is installed (optional). | |
1365 | ||
1366 | @item --disable-libarttest | |
1367 | Do not try to compile and run a test libart program. | |
1368 | ||
1369 | @end table | |
f42974dc DW |
1370 | |
1371 | @html | |
b8db17af | 1372 | <hr /> |
f42974dc DW |
1373 | <p> |
1374 | @end html | |
1375 | @ifhtml | |
1376 | @uref{./index.html,,Return to the GCC Installation page} | |
1377 | @end ifhtml | |
1378 | @end ifset | |
1379 | ||
1380 | @c ***Building**************************************************************** | |
6cfb3f16 | 1381 | @ifnothtml |
f42974dc DW |
1382 | @comment node-name, next, previous, up |
1383 | @node Building, Testing, Configuration, Installing GCC | |
6cfb3f16 | 1384 | @end ifnothtml |
f42974dc | 1385 | @ifset buildhtml |
f42974dc DW |
1386 | @ifnothtml |
1387 | @chapter Building | |
1388 | @end ifnothtml | |
1389 | @cindex Installing GCC: Building | |
1390 | ||
1391 | Now that GCC is configured, you are ready to build the compiler and | |
1392 | runtime libraries. | |
1393 | ||
b8df899a | 1394 | Some commands executed when making the compiler may fail (return a |
7ba4ca63 | 1395 | nonzero status) and be ignored by @command{make}. These failures, which |
b8df899a JM |
1396 | are often due to files that were not found, are expected, and can safely |
1397 | be ignored. | |
1398 | ||
1399 | It is normal to have compiler warnings when compiling certain files. | |
1400 | Unless you are a GCC developer, you can generally ignore these warnings | |
dd859b8a KG |
1401 | unless they cause compilation to fail. Developers should attempt to fix |
1402 | any warnings encountered, however they can temporarily continue past | |
1403 | warnings-as-errors by specifying the configure flag | |
1404 | @option{--disable-werror}. | |
b8df899a JM |
1405 | |
1406 | On certain old systems, defining certain environment variables such as | |
6cfb3f16 | 1407 | @env{CC} can interfere with the functioning of @command{make}. |
b8df899a JM |
1408 | |
1409 | If you encounter seemingly strange errors when trying to build the | |
1410 | compiler in a directory other than the source directory, it could be | |
1411 | because you have previously configured the compiler in the source | |
1412 | directory. Make sure you have done all the necessary preparations. | |
1413 | ||
1414 | If you build GCC on a BSD system using a directory stored in an old System | |
4c64396e | 1415 | V file system, problems may occur in running @command{fixincludes} if the |
b8df899a JM |
1416 | System V file system doesn't support symbolic links. These problems |
1417 | result in a failure to fix the declaration of @code{size_t} in | |
1418 | @file{sys/types.h}. If you find that @code{size_t} is a signed type and | |
1419 | that type mismatches occur, this could be the cause. | |
1420 | ||
161d7b59 | 1421 | The solution is not to use such a directory for building GCC@. |
f42974dc | 1422 | |
f85b8d1a JM |
1423 | When building from CVS or snapshots, or if you modify parser sources, |
1424 | you need the Bison parser generator installed. Any version 1.25 or | |
1425 | later should work; older versions may also work. If you do not modify | |
1426 | parser sources, releases contain the Bison-generated files and you do | |
1427 | not need Bison installed to build them. | |
1428 | ||
1429 | When building from CVS or snapshots, or if you modify Texinfo | |
a38f87a9 | 1430 | documentation, you need version 4.2 or later of Texinfo installed if you |
f85b8d1a JM |
1431 | want Info documentation to be regenerated. Releases contain Info |
1432 | documentation pre-built for the unmodified documentation in the release. | |
1433 | ||
f42974dc DW |
1434 | @section Building a native compiler |
1435 | ||
f9047ed3 | 1436 | For a native build issue the command @samp{make bootstrap}. This |
f42974dc DW |
1437 | will build the entire GCC system, which includes the following steps: |
1438 | ||
1439 | @itemize @bullet | |
1440 | @item | |
1441 | Build host tools necessary to build the compiler such as texinfo, bison, | |
1442 | gperf. | |
1443 | ||
1444 | @item | |
1445 | Build target tools for use by the compiler such as binutils (bfd, | |
eea81d3e | 1446 | binutils, gas, gprof, ld, and opcodes) |
f282ffb3 | 1447 | if they have been individually linked |
f42974dc DW |
1448 | or moved into the top level GCC source tree before configuring. |
1449 | ||
1450 | @item | |
1451 | Perform a 3-stage bootstrap of the compiler. | |
1452 | ||
1453 | @item | |
1454 | Perform a comparison test of the stage2 and stage3 compilers. | |
1455 | ||
1456 | @item | |
1457 | Build runtime libraries using the stage3 compiler from the previous step. | |
f9047ed3 | 1458 | |
f42974dc DW |
1459 | @end itemize |
1460 | ||
38209993 LG |
1461 | If you are short on disk space you might consider @samp{make |
1462 | bootstrap-lean} instead. This is identical to @samp{make | |
1463 | bootstrap} except that object files from the stage1 and | |
f42974dc DW |
1464 | stage2 of the 3-stage bootstrap of the compiler are deleted as |
1465 | soon as they are no longer needed. | |
1466 | ||
f42974dc DW |
1467 | If you want to save additional space during the bootstrap and in |
1468 | the final installation as well, you can build the compiler binaries | |
8c085f6f | 1469 | without debugging information as in the following example. This will save |
f42974dc DW |
1470 | roughly 40% of disk space both for the bootstrap and the final installation. |
1471 | (Libraries will still contain debugging information.) | |
1472 | ||
3ab51846 | 1473 | @smallexample |
8c085f6f JJ |
1474 | make CFLAGS='-O' LIBCFLAGS='-g -O2' \ |
1475 | LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap | |
3ab51846 | 1476 | @end smallexample |
8c085f6f | 1477 | |
eea81d3e RO |
1478 | If you wish to use non-default GCC flags when compiling the stage2 and |
1479 | stage3 compilers, set @code{BOOT_CFLAGS} on the command line when doing | |
f85b8d1a JM |
1480 | @samp{make bootstrap}. Non-default optimization flags are less well |
1481 | tested here than the default of @samp{-g -O2}, but should still work. | |
1482 | In a few cases, you may find that you need to specify special flags such | |
1483 | as @option{-msoft-float} here to complete the bootstrap; or, if the | |
1484 | native compiler miscompiles the stage1 compiler, you may need to work | |
1485 | around this, by choosing @code{BOOT_CFLAGS} to avoid the parts of the | |
1486 | stage1 compiler that were miscompiled, or by using @samp{make | |
1487 | bootstrap4} to increase the number of stages of bootstrap. | |
1488 | ||
c872077c AP |
1489 | Note that using non-standard @code{CFLAGS} can cause bootstrap to fail in |
1490 | @file{libiberty}, if these trigger a warning with the new compiler. For | |
1491 | example using @samp{-O2 -g -mcpu=i686} on @code{i686-pc-linux-gnu} will | |
1492 | cause bootstrap failure as @code{-mcpu=} is deprecated in 3.4.0 and above. | |
1493 | ||
1494 | ||
6cfb3f16 | 1495 | If you used the flag @option{--enable-languages=@dots{}} to restrict |
f42974dc | 1496 | the compilers to be built, only those you've actually enabled will be |
767094dd | 1497 | built. This will of course only build those runtime libraries, for |
f42974dc | 1498 | which the particular compiler has been built. Please note, |
eea81d3e | 1499 | that re-defining @env{LANGUAGES} when calling @samp{make bootstrap} |
ef88b07d | 1500 | @strong{does not} work anymore! |
f42974dc | 1501 | |
f85b8d1a | 1502 | If the comparison of stage2 and stage3 fails, this normally indicates |
eea81d3e | 1503 | that the stage2 compiler has compiled GCC incorrectly, and is therefore |
f85b8d1a JM |
1504 | a potentially serious bug which you should investigate and report. (On |
1505 | a few systems, meaningful comparison of object files is impossible; they | |
1506 | always appear ``different''. If you encounter this problem, you will | |
1507 | need to disable comparison in the @file{Makefile}.) | |
f42974dc DW |
1508 | |
1509 | @section Building a cross compiler | |
1510 | ||
1511 | We recommend reading the | |
1512 | @uref{http://www.objsw.com/CrossGCC/,,crossgcc FAQ} | |
1513 | for information about building cross compilers. | |
1514 | ||
1515 | When building a cross compiler, it is not generally possible to do a | |
1516 | 3-stage bootstrap of the compiler. This makes for an interesting problem | |
161d7b59 | 1517 | as parts of GCC can only be built with GCC@. |
f42974dc DW |
1518 | |
1519 | To build a cross compiler, we first recommend building and installing a | |
1520 | native compiler. You can then use the native GCC compiler to build the | |
635771af JM |
1521 | cross compiler. The installed native compiler needs to be GCC version |
1522 | 2.95 or later. | |
f42974dc DW |
1523 | |
1524 | Assuming you have already installed a native copy of GCC and configured | |
6cfb3f16 | 1525 | your cross compiler, issue the command @command{make}, which performs the |
f42974dc DW |
1526 | following steps: |
1527 | ||
1528 | @itemize @bullet | |
1529 | @item | |
1530 | Build host tools necessary to build the compiler such as texinfo, bison, | |
1531 | gperf. | |
1532 | ||
1533 | @item | |
1534 | Build target tools for use by the compiler such as binutils (bfd, | |
1535 | binutils, gas, gprof, ld, and opcodes) | |
1536 | if they have been individually linked or moved into the top level GCC source | |
1537 | tree before configuring. | |
1538 | ||
1539 | @item | |
1540 | Build the compiler (single stage only). | |
1541 | ||
1542 | @item | |
1543 | Build runtime libraries using the compiler from the previous step. | |
1544 | @end itemize | |
1545 | ||
1546 | Note that if an error occurs in any step the make process will exit. | |
1547 | ||
01e97976 JM |
1548 | If you are not building GNU binutils in the same source tree as GCC, |
1549 | you will need a cross-assembler and cross-linker installed before | |
1550 | configuring GCC@. Put them in the directory | |
1551 | @file{@var{prefix}/@var{target}/bin}. Here is a table of the tools | |
1552 | you should put in this directory: | |
1553 | ||
1554 | @table @file | |
1555 | @item as | |
1556 | This should be the cross-assembler. | |
1557 | ||
1558 | @item ld | |
1559 | This should be the cross-linker. | |
1560 | ||
1561 | @item ar | |
1562 | This should be the cross-archiver: a program which can manipulate | |
1563 | archive files (linker libraries) in the target machine's format. | |
1564 | ||
1565 | @item ranlib | |
1566 | This should be a program to construct a symbol table in an archive file. | |
1567 | @end table | |
1568 | ||
1569 | The installation of GCC will find these programs in that directory, | |
1570 | and copy or link them to the proper place to for the cross-compiler to | |
1571 | find them when run later. | |
1572 | ||
1573 | The easiest way to provide these files is to build the Binutils package. | |
1574 | Configure it with the same @option{--host} and @option{--target} | |
1575 | options that you use for configuring GCC, then build and install | |
1576 | them. They install their executables automatically into the proper | |
1577 | directory. Alas, they do not support all the targets that GCC | |
1578 | supports. | |
1579 | ||
1580 | If you are not building a C library in the same source tree as GCC, | |
1581 | you should also provide the target libraries and headers before | |
1582 | configuring GCC, specifying the directories with | |
1583 | @option{--with-sysroot} or @option{--with-headers} and | |
1584 | @option{--with-libs}. Many targets also require ``start files'' such | |
1585 | as @file{crt0.o} and | |
1586 | @file{crtn.o} which are linked into each executable. There may be several | |
1587 | alternatives for @file{crt0.o}, for use with profiling or other | |
1588 | compilation options. Check your target's definition of | |
1589 | @code{STARTFILE_SPEC} to find out what start files it uses. | |
1590 | ||
f42974dc DW |
1591 | @section Building in parallel |
1592 | ||
27a3e494 DE |
1593 | You can use @samp{make bootstrap MAKE="make -j 2" -j 2}, or just |
1594 | @samp{make -j 2 bootstrap} for GNU Make 3.79 and above, instead of | |
1595 | @samp{make bootstrap} to build GCC in parallel. | |
1596 | You can also specify a bigger number, and in most cases using a value | |
1597 | greater than the number of processors in your machine will result in | |
1598 | fewer and shorter I/O latency hits, thus improving overall throughput; | |
1599 | this is especially true for slow drives and network filesystems. | |
f42974dc | 1600 | |
e23381df GB |
1601 | @section Building the Ada compiler |
1602 | ||
1603 | In order to build GNAT, the Ada compiler, you need a working GNAT | |
3e98a119 | 1604 | compiler (GNAT version 3.14 or later, or GCC version 3.1 or later), |
af5734de | 1605 | including GNAT tools such as @command{gnatmake} and @command{gnatlink}, |
38e23049 | 1606 | since the Ada front end is written in Ada (with some |
e23381df GB |
1607 | GNAT-specific extensions), and GNU make. |
1608 | ||
38e23049 JM |
1609 | @command{configure} does not test whether the GNAT installation works |
1610 | and has a sufficiently recent version; if too old a GNAT version is | |
1611 | installed, the build will fail unless @option{--enable-languages} is | |
1612 | used to disable building the Ada front end. | |
e23381df | 1613 | |
8f231b5d JH |
1614 | @section Building with profile feedback |
1615 | ||
1616 | It is possible to use profile feedback to optimize the compiler itself. This | |
1617 | should result in a faster compiler binary. Experiments done on x86 using gcc | |
1618 | 3.3 showed approximately 7 percent speedup on compiling C programs. To | |
1619 | bootstrap compiler with profile feedback, use @code{make profiledbootstrap}. | |
1620 | ||
1621 | When @samp{make profiledbootstrap} is run, it will first build a @code{stage1} | |
1622 | compiler. This compiler is used to build a @code{stageprofile} compiler | |
1623 | instrumented to collect execution counts of instruction and branch | |
1624 | probabilities. Then runtime libraries are compiled with profile collected. | |
1625 | Finally a @code{stagefeedback} compiler is built using the information collected. | |
1626 | ||
1627 | Unlike @samp{make bootstrap} several additional restrictions apply. The | |
1628 | compiler used to build @code{stage1} needs to support a 64-bit integral type. | |
1629 | It is recommended to only use GCC for this. Also parallel make is currently | |
1630 | not supported since collisions in profile collecting may occur. | |
1631 | ||
f42974dc | 1632 | @html |
b8db17af | 1633 | <hr /> |
f42974dc DW |
1634 | <p> |
1635 | @end html | |
1636 | @ifhtml | |
1637 | @uref{./index.html,,Return to the GCC Installation page} | |
1638 | @end ifhtml | |
1639 | @end ifset | |
1640 | ||
1641 | @c ***Testing***************************************************************** | |
6cfb3f16 | 1642 | @ifnothtml |
f42974dc DW |
1643 | @comment node-name, next, previous, up |
1644 | @node Testing, Final install, Building, Installing GCC | |
6cfb3f16 | 1645 | @end ifnothtml |
f42974dc | 1646 | @ifset testhtml |
f42974dc DW |
1647 | @ifnothtml |
1648 | @chapter Installing GCC: Testing | |
1649 | @end ifnothtml | |
1650 | @cindex Testing | |
1651 | @cindex Installing GCC: Testing | |
1652 | @cindex Testsuite | |
1653 | ||
f97903cc JJ |
1654 | Before you install GCC, we encourage you to run the testsuites and to |
1655 | compare your results with results from a similar configuration that have | |
1656 | been submitted to the | |
1657 | @uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}. | |
05253aed JJ |
1658 | Some of these archived results are linked from the build status lists |
1659 | at @uref{http://gcc.gnu.org/buildstat.html}, although not everyone who | |
1660 | reports a successful build runs the testsuites and submits the results. | |
f97903cc JJ |
1661 | This step is optional and may require you to download additional software, |
1662 | but it can give you confidence in your new GCC installation or point out | |
1663 | problems before you install and start using your new GCC. | |
f42974dc | 1664 | |
f9047ed3 | 1665 | First, you must have @uref{download.html,,downloaded the testsuites}. |
f97903cc JJ |
1666 | These are part of the full distribution, but if you downloaded the |
1667 | ``core'' compiler plus any front ends, you must download the testsuites | |
1668 | separately. | |
f42974dc | 1669 | |
f97903cc | 1670 | Second, you must have the testing tools installed. This includes |
cfc984b5 MS |
1671 | @uref{http://www.gnu.org/software/dejagnu/,,DejaGnu} 1.4.4 and later, |
1672 | Tcl, and Expect; the DejaGnu site has links to these. | |
f42974dc | 1673 | |
8cacda7c GP |
1674 | If the directories where @command{runtest} and @command{expect} were |
1675 | installed are not in the @env{PATH}, you may need to set the following | |
1676 | environment variables appropriately, as in the following example (which | |
1677 | assumes that DejaGnu has been installed under @file{/usr/local}): | |
f42974dc | 1678 | |
3ab51846 | 1679 | @smallexample |
f42974dc DW |
1680 | TCL_LIBRARY = /usr/local/share/tcl8.0 |
1681 | DEJAGNULIBS = /usr/local/share/dejagnu | |
3ab51846 | 1682 | @end smallexample |
f42974dc | 1683 | |
8cacda7c | 1684 | (On systems such as Cygwin, these paths are required to be actual |
f42974dc | 1685 | paths, not mounts or links; presumably this is due to some lack of |
8cacda7c | 1686 | portability in the DejaGnu code.) |
ecb7d6b3 | 1687 | |
f42974dc DW |
1688 | |
1689 | Finally, you can run the testsuite (which may take a long time): | |
3ab51846 | 1690 | @smallexample |
ef88b07d | 1691 | cd @var{objdir}; make -k check |
3ab51846 | 1692 | @end smallexample |
f42974dc | 1693 | |
794aca5d WB |
1694 | This will test various components of GCC, such as compiler |
1695 | front ends and runtime libraries. While running the testsuite, DejaGnu | |
1696 | might emit some harmless messages resembling | |
daf2f129 | 1697 | @samp{WARNING: Couldn't find the global config file.} or |
794aca5d | 1698 | @samp{WARNING: Couldn't find tool init file} that can be ignored. |
06809951 | 1699 | |
962e6e00 | 1700 | @section How can you run the testsuite on selected tests? |
f42974dc | 1701 | |
794aca5d WB |
1702 | In order to run sets of tests selectively, there are targets |
1703 | @samp{make check-gcc} and @samp{make check-g++} | |
1704 | in the @file{gcc} subdirectory of the object directory. You can also | |
1705 | just run @samp{make check} in a subdirectory of the object directory. | |
1706 | ||
1707 | ||
1708 | A more selective way to just run all @command{gcc} execute tests in the | |
1709 | testsuite is to use | |
f42974dc | 1710 | |
3ab51846 | 1711 | @smallexample |
6cfb3f16 | 1712 | make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}" |
3ab51846 | 1713 | @end smallexample |
f42974dc | 1714 | |
794aca5d WB |
1715 | Likewise, in order to run only the @command{g++} ``old-deja'' tests in |
1716 | the testsuite with filenames matching @samp{9805*}, you would use | |
f42974dc | 1717 | |
3ab51846 | 1718 | @smallexample |
6cfb3f16 | 1719 | make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}" |
3ab51846 | 1720 | @end smallexample |
f42974dc | 1721 | |
6cfb3f16 JM |
1722 | The @file{*.exp} files are located in the testsuite directories of the GCC |
1723 | source, the most important ones being @file{compile.exp}, | |
1724 | @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}. | |
1725 | To get a list of the possible @file{*.exp} files, pipe the | |
38209993 | 1726 | output of @samp{make check} into a file and look at the |
6cfb3f16 | 1727 | @samp{Running @dots{} .exp} lines. |
f42974dc | 1728 | |
e08737dc PE |
1729 | @section Passing options and running multiple testsuites |
1730 | ||
1731 | You can pass multiple options to the testsuite using the | |
1732 | @samp{--target_board} option of DejaGNU, either passed as part of | |
1733 | @samp{RUNTESTFLAGS}, or directly to @command{runtest} if you prefer to | |
1734 | work outside the makefiles. For example, | |
1735 | ||
3ab51846 | 1736 | @smallexample |
e08737dc | 1737 | make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fno-strength-reduce" |
3ab51846 | 1738 | @end smallexample |
e08737dc PE |
1739 | |
1740 | will run the standard @command{g++} testsuites (``unix'' is the target name | |
1741 | for a standard native testsuite situation), passing | |
1742 | @samp{-O3 -fno-strength-reduce} to the compiler on every test, i.e., | |
1743 | slashes separate options. | |
1744 | ||
1745 | You can run the testsuites multiple times using combinations of options | |
1746 | with a syntax similar to the brace expansion of popular shells: | |
1747 | ||
3ab51846 | 1748 | @smallexample |
d817041f | 1749 | @dots{}"--target_board=arm-sim/@{-mhard-float,-msoft-float@}@{-O1,-O2,-O3,@}" |
3ab51846 | 1750 | @end smallexample |
e08737dc PE |
1751 | |
1752 | (Note the empty option caused by the trailing comma in the final group.) | |
1753 | The following will run each testsuite eight times using the @samp{arm-sim} | |
1754 | target, as if you had specified all possible combinations yourself: | |
1755 | ||
3ab51846 | 1756 | @smallexample |
e08737dc PE |
1757 | --target_board=arm-sim/-mhard-float/-O1 |
1758 | --target_board=arm-sim/-mhard-float/-O2 | |
1759 | --target_board=arm-sim/-mhard-float/-O3 | |
1760 | --target_board=arm-sim/-mhard-float | |
1761 | --target_board=arm-sim/-msoft-float/-O1 | |
1762 | --target_board=arm-sim/-msoft-float/-O2 | |
1763 | --target_board=arm-sim/-msoft-float/-O3 | |
1764 | --target_board=arm-sim/-msoft-float | |
3ab51846 | 1765 | @end smallexample |
e08737dc PE |
1766 | |
1767 | They can be combined as many times as you wish, in arbitrary ways. This | |
1768 | list: | |
1769 | ||
3ab51846 | 1770 | @smallexample |
e08737dc | 1771 | @dots{}"--target_board=unix/-Wextra@{-O3,-fno-strength-reduce@}@{-fomit-frame-pointer,@}" |
3ab51846 | 1772 | @end smallexample |
e08737dc PE |
1773 | |
1774 | will generate four combinations, all involving @samp{-Wextra}. | |
1775 | ||
1776 | The disadvantage to this method is that the testsuites are run in serial, | |
1777 | which is a waste on multiprocessor systems. For users with GNU Make and | |
1778 | a shell which performs brace expansion, you can run the testsuites in | |
1779 | parallel by having the shell perform the combinations and @command{make} | |
1780 | do the parallel runs. Instead of using @samp{--target_board}, use a | |
1781 | special makefile target: | |
1782 | ||
3ab51846 | 1783 | @smallexample |
e08737dc | 1784 | make -j@var{N} check-@var{testsuite}//@var{test-target}/@var{option1}/@var{option2}/@dots{} |
3ab51846 | 1785 | @end smallexample |
e08737dc PE |
1786 | |
1787 | For example, | |
1788 | ||
3ab51846 | 1789 | @smallexample |
e08737dc | 1790 | make -j3 check-gcc//sh-hms-sim/@{-m1,-m2,-m3,-m3e,-m4@}/@{,-nofpu@} |
3ab51846 | 1791 | @end smallexample |
e08737dc PE |
1792 | |
1793 | will run three concurrent ``make-gcc'' testsuites, eventually testing all | |
1794 | ten combinations as described above. Note that this is currently only | |
1795 | supported in the @file{gcc} subdirectory. (To see how this works, try | |
1796 | typing @command{echo} before the example given here.) | |
1797 | ||
1798 | ||
1799 | @section Additional testing for Java Class Libraries | |
1800 | ||
688d8b84 RM |
1801 | The Java runtime tests can be executed via @samp{make check} |
1802 | in the @file{@var{target}/libjava/testsuite} directory in | |
1803 | the build tree. | |
f702e700 | 1804 | |
f702e700 JJ |
1805 | The @uref{http://sources.redhat.com/mauve/,,Mauve Project} provides |
1806 | a suite of tests for the Java Class Libraries. This suite can be run | |
1807 | as part of libgcj testing by placing the Mauve tree within the libjava | |
1808 | testsuite at @file{libjava/testsuite/libjava.mauve/mauve}, or by | |
1809 | specifying the location of that tree when invoking @samp{make}, as in | |
1810 | @samp{make MAUVEDIR=~/mauve check}. | |
1811 | ||
582f6e6d | 1812 | @uref{http://www-124.ibm.com/developerworks/oss/cvs/jikes/~checkout~/jacks/jacks.html,,Jacks} |
2eac577f | 1813 | is a free testsuite that tests Java compiler front ends. This suite |
3b41afd9 | 1814 | can be run as part of libgcj testing by placing the Jacks tree within |
582f6e6d TT |
1815 | the libjava testsuite at @file{libjava/testsuite/libjava.jacks/jacks}. |
1816 | ||
f42974dc DW |
1817 | @section How to interpret test results |
1818 | ||
794aca5d | 1819 | The result of running the testsuite are various @file{*.sum} and @file{*.log} |
767094dd | 1820 | files in the testsuite subdirectories. The @file{*.log} files contain a |
f42974dc | 1821 | detailed log of the compiler invocations and the corresponding |
daf2f129 JM |
1822 | results, the @file{*.sum} files summarize the results. These summaries |
1823 | contain status codes for all tests: | |
f42974dc DW |
1824 | |
1825 | @itemize @bullet | |
1826 | @item | |
1827 | PASS: the test passed as expected | |
1828 | @item | |
1829 | XPASS: the test unexpectedly passed | |
1830 | @item | |
1831 | FAIL: the test unexpectedly failed | |
1832 | @item | |
1833 | XFAIL: the test failed as expected | |
1834 | @item | |
1835 | UNSUPPORTED: the test is not supported on this platform | |
1836 | @item | |
1837 | ERROR: the testsuite detected an error | |
1838 | @item | |
1839 | WARNING: the testsuite detected a possible problem | |
1840 | @end itemize | |
1841 | ||
38209993 | 1842 | It is normal for some tests to report unexpected failures. At the |
962e6e00 JM |
1843 | current time the testing harness does not allow fine grained control |
1844 | over whether or not a test is expected to fail. This problem should | |
1845 | be fixed in future releases. | |
f42974dc DW |
1846 | |
1847 | ||
1848 | @section Submitting test results | |
1849 | ||
1850 | If you want to report the results to the GCC project, use the | |
767094dd | 1851 | @file{contrib/test_summary} shell script. Start it in the @var{objdir} with |
f42974dc | 1852 | |
3ab51846 | 1853 | @smallexample |
6cfb3f16 JM |
1854 | @var{srcdir}/contrib/test_summary -p your_commentary.txt \ |
1855 | -m gcc-testresults@@gcc.gnu.org |sh | |
3ab51846 | 1856 | @end smallexample |
f42974dc | 1857 | |
6cfb3f16 | 1858 | This script uses the @command{Mail} program to send the results, so |
767094dd | 1859 | make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is |
f42974dc | 1860 | prepended to the testsuite summary and should contain any special |
767094dd | 1861 | remarks you have on your results or your build environment. Please |
f42974dc | 1862 | do not edit the testsuite result block or the subject line, as these |
05c425a9 | 1863 | messages may be automatically processed. |
f42974dc | 1864 | |
aed5964b | 1865 | @html |
b8db17af | 1866 | <hr /> |
aed5964b JM |
1867 | <p> |
1868 | @end html | |
1869 | @ifhtml | |
1870 | @uref{./index.html,,Return to the GCC Installation page} | |
1871 | @end ifhtml | |
f42974dc DW |
1872 | @end ifset |
1873 | ||
1874 | @c ***Final install*********************************************************** | |
6cfb3f16 | 1875 | @ifnothtml |
f42974dc DW |
1876 | @comment node-name, next, previous, up |
1877 | @node Final install, , Testing, Installing GCC | |
6cfb3f16 | 1878 | @end ifnothtml |
f42974dc | 1879 | @ifset finalinstallhtml |
f42974dc DW |
1880 | @ifnothtml |
1881 | @chapter Installing GCC: Final installation | |
1882 | @end ifnothtml | |
1883 | ||
eea81d3e | 1884 | Now that GCC has been built (and optionally tested), you can install it with |
3ab51846 | 1885 | @smallexample |
eea81d3e | 1886 | cd @var{objdir}; make install |
3ab51846 | 1887 | @end smallexample |
f42974dc | 1888 | |
06809951 GP |
1889 | We strongly recommend to install into a target directory where there is |
1890 | no previous version of GCC present. | |
1891 | ||
f42974dc | 1892 | That step completes the installation of GCC; user level binaries can |
8e5f33ff GK |
1893 | be found in @file{@var{prefix}/bin} where @var{prefix} is the value |
1894 | you specified with the @option{--prefix} to configure (or | |
1895 | @file{/usr/local} by default). (If you specified @option{--bindir}, | |
1896 | that directory will be used instead; otherwise, if you specified | |
1897 | @option{--exec-prefix}, @file{@var{exec-prefix}/bin} will be used.) | |
1898 | Headers for the C++ and Java libraries are installed in | |
1899 | @file{@var{prefix}/include}; libraries in @file{@var{libdir}} | |
1900 | (normally @file{@var{prefix}/lib}); internal parts of the compiler in | |
1901 | @file{@var{libdir}/gcc} and @file{@var{libexecdir}/gcc}; documentation | |
1902 | in info format in @file{@var{infodir}} (normally | |
1903 | @file{@var{prefix}/info}). | |
f42974dc | 1904 | |
53b50ac1 CC |
1905 | When installing cross-compilers, GCC's executables |
1906 | are not only installed into @file{@var{bindir}}, that | |
1907 | is, @file{@var{exec-prefix}/bin}, but additionally into | |
1908 | @file{@var{exec-prefix}/@var{target-alias}/bin}, if that directory | |
1909 | exists. Typically, such @dfn{tooldirs} hold target-specific | |
1910 | binutils, including assembler and linker. | |
1911 | ||
1912 | Installation into a temporary staging area or into a @command{chroot} | |
1913 | jail can be achieved with the command | |
1914 | ||
3ab51846 | 1915 | @smallexample |
53b50ac1 | 1916 | make DESTDIR=@var{path-to-rootdir} install |
3ab51846 | 1917 | @end smallexample |
53b50ac1 CC |
1918 | |
1919 | @noindent where @var{path-to-rootdir} is the absolute path of | |
1920 | a directory relative to which all installation paths will be | |
1921 | interpreted. Note that the directory specified by @code{DESTDIR} | |
1922 | need not exist yet; it will be created if necessary. | |
1923 | ||
1924 | There is a subtle point with tooldirs and @code{DESTDIR}: | |
1925 | If you relocate a cross-compiler installation with | |
1926 | e.g.@: @samp{DESTDIR=@var{rootdir}}, then the directory | |
1927 | @file{@var{rootdir}/@var{exec-prefix}/@var{target-alias}/bin} will | |
1928 | be filled with duplicated GCC executables only if it already exists, | |
1929 | it will not be created otherwise. This is regarded as a feature, | |
1930 | not as a bug, because it gives slightly more control to the packagers | |
1931 | using the @code{DESTDIR} feature. | |
1932 | ||
2b46bc67 | 1933 | If you built a released version of GCC using @samp{make bootstrap} then please |
f97a5bda JJ |
1934 | quickly review the build status page for your release, available from |
1935 | @uref{http://gcc.gnu.org/buildstat.html}. | |
c5997381 JJ |
1936 | If your system is not listed for the version of GCC that you built, |
1937 | send a note to | |
eea81d3e RO |
1938 | @email{gcc@@gcc.gnu.org} indicating |
1939 | that you successfully built and installed GCC. | |
c5997381 | 1940 | Include the following information: |
f42974dc | 1941 | |
c5997381 JJ |
1942 | @itemize @bullet |
1943 | @item | |
962e6e00 | 1944 | Output from running @file{@var{srcdir}/config.guess}. Do not send |
c5997381 JJ |
1945 | that file itself, just the one-line output from running it. |
1946 | ||
1947 | @item | |
2dd76960 | 1948 | The output of @samp{gcc -v} for your newly installed @command{gcc}. |
c5997381 JJ |
1949 | This tells us which version of GCC you built and the options you passed to |
1950 | configure. | |
1951 | ||
2b46bc67 JJ |
1952 | @item |
1953 | Whether you enabled all languages or a subset of them. If you used a | |
1954 | full distribution then this information is part of the configure | |
1955 | options in the output of @samp{gcc -v}, but if you downloaded the | |
1956 | ``core'' compiler plus additional front ends then it isn't apparent | |
1957 | which ones you built unless you tell us about it. | |
1958 | ||
c5997381 JJ |
1959 | @item |
1960 | If the build was for GNU/Linux, also include: | |
1961 | @itemize @bullet | |
1962 | @item | |
1963 | The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3); | |
1964 | this information should be available from @file{/etc/issue}. | |
1965 | ||
1966 | @item | |
1967 | The version of the Linux kernel, available from @samp{uname --version} | |
1968 | or @samp{uname -a}. | |
1969 | ||
1970 | @item | |
1971 | The version of glibc you used; for RPM-based systems like Red Hat, | |
b9da07da JJ |
1972 | Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version, |
1973 | and on systems like Debian and Progeny use @samp{dpkg -l libc6}. | |
c5997381 JJ |
1974 | @end itemize |
1975 | For other systems, you can include similar information if you think it is | |
1976 | relevant. | |
1977 | ||
1978 | @item | |
1979 | Any other information that you think would be useful to people building | |
1980 | GCC on the same configuration. The new entry in the build status list | |
1981 | will include a link to the archived copy of your message. | |
1982 | @end itemize | |
c009f01f JJ |
1983 | |
1984 | We'd also like to know if the | |
1985 | @ifnothtml | |
1986 | @ref{Specific, host/target specific installation notes} | |
1987 | @end ifnothtml | |
1988 | @ifhtml | |
1989 | @uref{specific.html,,host/target specific installation notes} | |
1990 | @end ifhtml | |
1991 | didn't include your host/target information or if that information is | |
1992 | incomplete or out of date. Send a note to | |
962e6e00 | 1993 | @email{gcc@@gcc.gnu.org} detailing how the information should be changed. |
f42974dc | 1994 | |
962e6e00 | 1995 | If you find a bug, please report it following the |
f42974dc DW |
1996 | @uref{../bugs.html,,bug reporting guidelines}. |
1997 | ||
ab130aa5 | 1998 | If you want to print the GCC manuals, do @samp{cd @var{objdir}; make |
a38f87a9 | 1999 | dvi}. You will need to have @command{texi2dvi} (version at least 4.2) |
ab130aa5 JM |
2000 | and @TeX{} installed. This creates a number of @file{.dvi} files in |
2001 | subdirectories of @file{@var{objdir}}; these may be converted for | |
2002 | printing with programs such as @command{dvips}. You can also | |
2003 | @uref{http://www.gnu.org/order/order.html,,buy printed manuals from the | |
2004 | Free Software Foundation}, though such manuals may not be for the most | |
161d7b59 | 2005 | recent version of GCC@. |
ab130aa5 | 2006 | |
f42974dc | 2007 | @html |
b8db17af | 2008 | <hr /> |
f42974dc DW |
2009 | <p> |
2010 | @end html | |
2011 | @ifhtml | |
2012 | @uref{./index.html,,Return to the GCC Installation page} | |
2013 | @end ifhtml | |
2014 | @end ifset | |
2015 | ||
2016 | @c ***Binaries**************************************************************** | |
6cfb3f16 | 2017 | @ifnothtml |
f42974dc DW |
2018 | @comment node-name, next, previous, up |
2019 | @node Binaries, Specific, Installing GCC, Top | |
6cfb3f16 | 2020 | @end ifnothtml |
f42974dc | 2021 | @ifset binarieshtml |
f42974dc DW |
2022 | @ifnothtml |
2023 | @chapter Installing GCC: Binaries | |
2024 | @end ifnothtml | |
2025 | @cindex Binaries | |
2026 | @cindex Installing GCC: Binaries | |
2027 | ||
161d7b59 | 2028 | We are often asked about pre-compiled versions of GCC@. While we cannot |
f42974dc DW |
2029 | provide these for all platforms, below you'll find links to binaries for |
2030 | various platforms where creating them by yourself is not easy due to various | |
2031 | reasons. | |
2032 | ||
2033 | Please note that we did not create these binaries, nor do we | |
2034 | support them. If you have any problems installing them, please | |
2035 | contact their makers. | |
2036 | ||
2037 | @itemize | |
2038 | @item | |
df002c7d DE |
2039 | AIX: |
2040 | @itemize | |
2041 | @item | |
ff4c5e7b | 2042 | @uref{http://www.bullfreeware.com,,Bull's Freeware and Shareware Archive for AIX}; |
df002c7d DE |
2043 | |
2044 | @item | |
8d5362b7 | 2045 | @uref{http://aixpdslib.seas.ucla.edu,,UCLA Software Library for AIX}. |
df002c7d | 2046 | @end itemize |
f42974dc DW |
2047 | |
2048 | @item | |
8d5362b7 GP |
2049 | DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}. |
2050 | ||
2051 | @item | |
71c6b994 KH |
2052 | Renesas H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU |
2053 | Development Tools for the Renesas H8/300[HS] Series}. | |
f42974dc | 2054 | |
f404402c MW |
2055 | @item |
2056 | HP-UX: | |
2057 | @itemize | |
f42974dc DW |
2058 | @item |
2059 | @uref{http://hpux.cae.wisc.edu/,,HP-UX Porting Center}; | |
2060 | ||
f404402c MW |
2061 | @item |
2062 | @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}. | |
2063 | @end itemize | |
2064 | ||
3e35d143 SC |
2065 | @item |
2066 | Motorola 68HC11/68HC12---@uref{http://www.gnu-m68hc11.org,,GNU | |
2067 | Development Tools for the Motorola 68HC11/68HC12}. | |
2068 | ||
f42974dc | 2069 | @item |
38209993 | 2070 | @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO |
8d5362b7 | 2071 | OpenServer/Unixware}. |
f42974dc DW |
2072 | |
2073 | @item | |
35113fde | 2074 | Sinix/Reliant Unix---@uref{ftp://ftp.fujitsu-siemens.com/pub/pd/gnu/gcc/,,Siemens}. |
daf2f129 | 2075 | |
8d5362b7 GP |
2076 | @item |
2077 | Solaris 2 (SPARC, Intel)---@uref{http://www.sunfreeware.com/,,Sunfreeware}. | |
f42974dc DW |
2078 | |
2079 | @item | |
8d5362b7 | 2080 | SGI---@uref{http://freeware.sgi.com/,,SGI Freeware}. |
f42974dc DW |
2081 | |
2082 | @item | |
05c425a9 | 2083 | Microsoft Windows: |
f42974dc DW |
2084 | @itemize |
2085 | @item | |
2086 | The @uref{http://sources.redhat.com/cygwin/,,Cygwin} project; | |
2087 | @item | |
cc92b8ab | 2088 | The @uref{http://www.mingw.org/,,MinGW} project. |
f42974dc DW |
2089 | @end itemize |
2090 | ||
2091 | @item | |
616de62f GP |
2092 | @uref{ftp://ftp.thewrittenword.com/packages/by-name/,,The |
2093 | Written Word} offers binaries for | |
2094 | AIX 4.3.2. | |
2095 | IRIX 6.5, | |
2096 | Digital UNIX 4.0D and 5.1, | |
2097 | GNU/Linux (i386), | |
2098 | HP-UX 10.20, 11.00, and 11.11, and | |
2099 | Solaris/SPARC 2.5.1, 2.6, 2.7, 8, and 9, | |
6512c54a GP |
2100 | |
2101 | @item | |
2102 | @uref{http://www.openpkg.org/,,OpenPKG} offers binaries for quite a | |
2103 | number of platforms. | |
f42974dc DW |
2104 | @end itemize |
2105 | ||
2106 | In addition to those specific offerings, you can get a binary | |
2107 | distribution CD-ROM from the | |
f9047ed3 | 2108 | @uref{http://www.fsf.org/order/order.html,,Free Software Foundation}. |
f42974dc | 2109 | It contains binaries for a number of platforms, and |
767094dd | 2110 | includes not only GCC, but other stuff as well. The current CD does |
f42974dc | 2111 | not contain the latest version of GCC, but it should allow |
767094dd | 2112 | bootstrapping the compiler. An updated version of that disk is in the |
f42974dc DW |
2113 | works. |
2114 | ||
2115 | @html | |
b8db17af | 2116 | <hr /> |
f42974dc DW |
2117 | <p> |
2118 | @end html | |
2119 | @ifhtml | |
2120 | @uref{./index.html,,Return to the GCC Installation page} | |
2121 | @end ifhtml | |
2122 | @end ifset | |
2123 | ||
2124 | @c ***Specific**************************************************************** | |
6cfb3f16 | 2125 | @ifnothtml |
f42974dc | 2126 | @comment node-name, next, previous, up |
73e2155a | 2127 | @node Specific, Old, Binaries, Top |
6cfb3f16 | 2128 | @end ifnothtml |
f42974dc | 2129 | @ifset specifichtml |
f42974dc DW |
2130 | @ifnothtml |
2131 | @chapter Host/target specific installation notes for GCC | |
2132 | @end ifnothtml | |
2133 | @cindex Specific | |
2134 | @cindex Specific installation notes | |
2135 | @cindex Target specific installation | |
2136 | @cindex Host specific installation | |
2137 | @cindex Target specific installation notes | |
2138 | ||
2139 | Please read this document carefully @emph{before} installing the | |
2140 | GNU Compiler Collection on your machine. | |
2141 | ||
ef88b07d | 2142 | @ifhtml |
f42974dc DW |
2143 | @itemize |
2144 | @item | |
333e14b0 | 2145 | @uref{#alpha*-*-*,,alpha*-*-*} |
f42974dc DW |
2146 | @item |
2147 | @uref{#alpha*-dec-osf*,,alpha*-dec-osf*} | |
2148 | @item | |
71b96724 RL |
2149 | @uref{#alphaev5-cray-unicosmk*,,alphaev5-cray-unicosmk*} |
2150 | @item | |
b8df899a JM |
2151 | @uref{#arc-*-elf,,arc-*-elf} |
2152 | @item | |
34e8290f NC |
2153 | @uref{#arm-*-elf,,arm-*-elf} |
2154 | @uref{#arm-*-coff,,arm-*-coff} | |
34e8290f | 2155 | @uref{#arm-*-aout,,arm-*-aout} |
b8df899a | 2156 | @item |
2aea0b53 | 2157 | @uref{#xscale-*-*,,xscale-*-*} |
476c334e | 2158 | @item |
f42974dc DW |
2159 | @uref{#avr,,avr} |
2160 | @item | |
0132e321 MH |
2161 | @uref{#c4x,,c4x} |
2162 | @item | |
f42974dc DW |
2163 | @uref{#dos,,DOS} |
2164 | @item | |
021c4bfd RO |
2165 | @uref{#*-*-freebsd*,,*-*-freebsd*} |
2166 | @item | |
f42974dc DW |
2167 | @uref{#h8300-hms,,h8300-hms} |
2168 | @item | |
2169 | @uref{#hppa*-hp-hpux*,,hppa*-hp-hpux*} | |
2170 | @item | |
f42974dc DW |
2171 | @uref{#hppa*-hp-hpux10,,hppa*-hp-hpux10} |
2172 | @item | |
2173 | @uref{#hppa*-hp-hpux11,,hppa*-hp-hpux11} | |
2174 | @item | |
2175 | @uref{#*-*-linux-gnu,,*-*-linux-gnu} | |
2176 | @item | |
b8df899a JM |
2177 | @uref{#ix86-*-linux*aout,,i?86-*-linux*aout} |
2178 | @item | |
f42974dc DW |
2179 | @uref{#ix86-*-linux*,,i?86-*-linux*} |
2180 | @item | |
2181 | @uref{#ix86-*-sco3.2v5*,,i?86-*-sco3.2v5*} | |
2182 | @item | |
f42974dc DW |
2183 | @uref{#ix86-*-udk,,i?86-*-udk} |
2184 | @item | |
b8df899a JM |
2185 | @uref{#ix86-*-esix,,i?86-*-esix} |
2186 | @item | |
b499d9ab JJ |
2187 | @uref{#ia64-*-linux,,ia64-*-linux} |
2188 | @item | |
959a73a4 DH |
2189 | @uref{#ia64-*-hpux*,,ia64-*-hpux*} |
2190 | @item | |
f42974dc DW |
2191 | @uref{#*-ibm-aix*,,*-ibm-aix*} |
2192 | @item | |
e3223ea2 DC |
2193 | @uref{#ip2k-*-elf,,ip2k-*-elf} |
2194 | @item | |
6b3d1e47 SC |
2195 | @uref{#iq2000-*-elf,,iq2000-*-elf} |
2196 | @item | |
b8df899a JM |
2197 | @uref{#m32r-*-elf,,m32r-*-elf} |
2198 | @item | |
b8df899a JM |
2199 | @uref{#m6811-elf,,m6811-elf} |
2200 | @item | |
2201 | @uref{#m6812-elf,,m6812-elf} | |
2202 | @item | |
b8df899a JM |
2203 | @uref{#m68k-hp-hpux,,m68k-hp-hpux} |
2204 | @item | |
b8df899a JM |
2205 | @uref{#mips-*-*,,mips-*-*} |
2206 | @item | |
b953cc4b | 2207 | @uref{#mips-sgi-irix5,,mips-sgi-irix5} |
f42974dc | 2208 | @item |
b953cc4b | 2209 | @uref{#mips-sgi-irix6,,mips-sgi-irix6} |
f42974dc | 2210 | @item |
021c4bfd RO |
2211 | @uref{#powerpc*-*-*,,powerpc*-*-*, powerpc-*-sysv4} |
2212 | @item | |
4f2b1139 SS |
2213 | @uref{#powerpc-*-darwin*,,powerpc-*-darwin*} |
2214 | @item | |
b8df899a JM |
2215 | @uref{#powerpc-*-elf,,powerpc-*-elf, powerpc-*-sysv4} |
2216 | @item | |
f42974dc DW |
2217 | @uref{#powerpc-*-linux-gnu*,,powerpc-*-linux-gnu*} |
2218 | @item | |
edf1b3f3 AC |
2219 | @uref{#powerpc-*-netbsd*,,powerpc-*-netbsd*} |
2220 | @item | |
b8df899a JM |
2221 | @uref{#powerpc-*-eabiaix,,powerpc-*-eabiaix} |
2222 | @item | |
2223 | @uref{#powerpc-*-eabisim,,powerpc-*-eabisim} | |
2224 | @item | |
2225 | @uref{#powerpc-*-eabi,,powerpc-*-eabi} | |
2226 | @item | |
2227 | @uref{#powerpcle-*-elf,,powerpcle-*-elf, powerpcle-*-sysv4} | |
2228 | @item | |
2229 | @uref{#powerpcle-*-eabisim,,powerpcle-*-eabisim} | |
2230 | @item | |
2231 | @uref{#powerpcle-*-eabi,,powerpcle-*-eabi} | |
2232 | @item | |
225cee28 | 2233 | @uref{#s390-*-linux*,,s390-*-linux*} |
91abf72d | 2234 | @item |
225cee28 | 2235 | @uref{#s390x-*-linux*,,s390x-*-linux*} |
91abf72d | 2236 | @item |
8bf06993 UW |
2237 | @uref{#s390x-ibm-tpf*,,s390x-ibm-tpf*} |
2238 | @item | |
250d5688 | 2239 | @uref{#*-*-solaris2*,,*-*-solaris2*} |
f42974dc | 2240 | @item |
250d5688 | 2241 | @uref{#sparc-sun-solaris2*,,sparc-sun-solaris2*} |
f42974dc DW |
2242 | @item |
2243 | @uref{#sparc-sun-solaris2.7,,sparc-sun-solaris2.7} | |
2244 | @item | |
c6fa9728 JS |
2245 | @uref{#sparc-*-linux*,,sparc-*-linux*} |
2246 | @item | |
0dc7ee3c | 2247 | @uref{#sparc64-*-solaris2*,,sparc64-*-solaris2*} |
f42974dc | 2248 | @item |
e403b4bc CR |
2249 | @uref{#sparcv9-*-solaris2*,,sparcv9-*-solaris2*} |
2250 | @item | |
b8df899a JM |
2251 | @uref{#*-*-sysv*,,*-*-sysv*} |
2252 | @item | |
2253 | @uref{#vax-dec-ultrix,,vax-dec-ultrix} | |
2254 | @item | |
4977bab6 ZW |
2255 | @uref{#*-*-vxworks*,,*-*-vxworks*} |
2256 | @item | |
7e081a0c AJ |
2257 | @uref{#x86_64-*-*,,x86_64-*-*, amd64-*-*} |
2258 | @item | |
fd29f6ea BW |
2259 | @uref{#xtensa-*-elf,,xtensa-*-elf} |
2260 | @item | |
2261 | @uref{#xtensa-*-linux*,,xtensa-*-linux*} | |
2262 | @item | |
f42974dc DW |
2263 | @uref{#windows,,Microsoft Windows} |
2264 | @item | |
2265 | @uref{#os2,,OS/2} | |
2266 | @item | |
2267 | @uref{#older,,Older systems} | |
2268 | @end itemize | |
2269 | ||
2270 | @itemize | |
2271 | @item | |
250d5688 | 2272 | @uref{#elf_targets,,all ELF targets} (SVR4, Solaris 2, etc.) |
f42974dc | 2273 | @end itemize |
ef88b07d | 2274 | @end ifhtml |
f42974dc DW |
2275 | |
2276 | ||
2277 | @html | |
2278 | <!-- -------- host/target specific issues start here ---------------- --> | |
b8db17af | 2279 | <hr /> |
f42974dc | 2280 | @end html |
333e14b0 LR |
2281 | @heading @anchor{alpha*-*-*}alpha*-*-* |
2282 | ||
2283 | This section contains general configuration information for all | |
2284 | alpha-based platforms using ELF (in particular, ignore this section for | |
161d7b59 | 2285 | DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this |
f2541106 | 2286 | section, please read all other sections that match your target. |
333e14b0 | 2287 | |
021c4bfd RO |
2288 | We require binutils 2.11.2 or newer. |
2289 | Previous binutils releases had a number of problems with DWARF 2 | |
333e14b0 LR |
2290 | debugging information, not the least of which is incorrect linking of |
2291 | shared libraries. | |
2292 | ||
b8df899a | 2293 | @html |
b8db17af | 2294 | <hr /> |
b8df899a | 2295 | @end html |
f2541106 | 2296 | @heading @anchor{alpha*-dec-osf*}alpha*-dec-osf* |
b8df899a | 2297 | Systems using processors that implement the DEC Alpha architecture and |
f2541106 RO |
2298 | are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq |
2299 | Tru64 UNIX) operating system, for example the DEC Alpha AXP systems. | |
2300 | ||
c7bdf0a6 ZW |
2301 | As of GCC 3.2, versions before @code{alpha*-dec-osf4} are no longer |
2302 | supported. (These are the versions which identify themselves as DEC | |
2303 | OSF/1.) | |
9340544b | 2304 | |
6e92b3a1 RB |
2305 | In Digital Unix V4.0, virtual memory exhausted bootstrap failures |
2306 | may be fixed by configuring with @option{--with-gc=simple}, | |
2307 | reconfiguring Kernel Virtual Memory and Swap parameters | |
2308 | per the @command{/usr/sbin/sys_check} Tuning Suggestions, | |
2309 | or applying the patch in | |
2310 | @uref{http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html}. | |
2311 | ||
f2541106 RO |
2312 | In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not |
2313 | currently (2001-06-13) work with @command{mips-tfile}. As a workaround, | |
2314 | we need to use the old assembler, invoked via the barely documented | |
2315 | @option{-oldas} option. To bootstrap GCC, you either need to use the | |
2316 | Compaq C Compiler: | |
2317 | ||
3ab51846 | 2318 | @smallexample |
eea81d3e | 2319 | % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}] |
3ab51846 | 2320 | @end smallexample |
f2541106 RO |
2321 | |
2322 | or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0: | |
2323 | ||
3ab51846 | 2324 | @smallexample |
eea81d3e | 2325 | % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}] |
3ab51846 | 2326 | @end smallexample |
b8df899a | 2327 | |
b953cc4b RO |
2328 | As of GNU binutils 2.11.2, neither GNU @command{as} nor GNU @command{ld} |
2329 | are supported on Tru64 UNIX, so you must not configure GCC with | |
2330 | @option{--with-gnu-as} or @option{--with-gnu-ld}. | |
2331 | ||
f0523f02 | 2332 | GCC writes a @samp{.verstamp} directive to the assembler output file |
b8df899a JM |
2333 | unless it is built as a cross-compiler. It gets the version to use from |
2334 | the system header file @file{/usr/include/stamp.h}. If you install a | |
2335 | new version of DEC Unix, you should rebuild GCC to pick up the new version | |
2336 | stamp. | |
2337 | ||
2338 | Note that since the Alpha is a 64-bit architecture, cross-compilers from | |
2339 | 32-bit machines will not generate code as efficient as that generated | |
2340 | when the compiler is running on a 64-bit machine because many | |
2341 | optimizations that depend on being able to represent a word on the | |
2342 | target in an integral value on the host cannot be performed. Building | |
2343 | cross-compilers on the Alpha for 32-bit machines has only been tested in | |
2344 | a few cases and may not work properly. | |
2345 | ||
7ba4ca63 | 2346 | @samp{make compare} may fail on old versions of DEC Unix unless you add |
6cfb3f16 | 2347 | @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the |
b8df899a JM |
2348 | assembler input file is stored in the object file, and that makes |
2349 | comparison fail if it differs between the @code{stage1} and | |
6cfb3f16 | 2350 | @code{stage2} compilations. The option @option{-save-temps} forces a |
b8df899a | 2351 | fixed name to be used for the assembler input file, instead of a |
6cfb3f16 | 2352 | randomly chosen name in @file{/tmp}. Do not add @option{-save-temps} |
b8df899a | 2353 | unless the comparisons fail without that option. If you add |
6cfb3f16 | 2354 | @option{-save-temps}, you will have to manually delete the @samp{.i} and |
b8df899a JM |
2355 | @samp{.s} files after each series of compilations. |
2356 | ||
f0523f02 | 2357 | GCC now supports both the native (ECOFF) debugging format used by DBX |
161d7b59 | 2358 | and GDB and an encapsulated STABS format for use only with GDB@. See the |
6cfb3f16 | 2359 | discussion of the @option{--with-stabs} option of @file{configure} above |
b8df899a JM |
2360 | for more information on these formats and how to select them. |
2361 | ||
2362 | There is a bug in DEC's assembler that produces incorrect line numbers | |
2363 | for ECOFF format when the @samp{.align} directive is used. To work | |
f0523f02 | 2364 | around this problem, GCC will not emit such alignment directives |
b8df899a JM |
2365 | while writing ECOFF format debugging information even if optimization is |
2366 | being performed. Unfortunately, this has the very undesirable | |
6cfb3f16 JM |
2367 | side-effect that code addresses when @option{-O} is specified are |
2368 | different depending on whether or not @option{-g} is also specified. | |
b8df899a | 2369 | |
6cfb3f16 | 2370 | To avoid this behavior, specify @option{-gstabs+} and use GDB instead of |
161d7b59 | 2371 | DBX@. DEC is now aware of this problem with the assembler and hopes to |
b8df899a JM |
2372 | provide a fix shortly. |
2373 | ||
71b96724 | 2374 | @html |
b8db17af | 2375 | <hr /> |
71b96724 RL |
2376 | @end html |
2377 | @heading @anchor{alphaev5-cray-unicosmk*}alphaev5-cray-unicosmk* | |
2378 | Cray T3E systems running Unicos/Mk. | |
2379 | ||
2380 | This port is incomplete and has many known bugs. We hope to improve the | |
2381 | support for this target soon. Currently, only the C front end is supported, | |
2382 | and it is not possible to build parallel applications. Cray modules are not | |
2383 | supported; in particular, Craylibs are assumed to be in | |
2384 | @file{/opt/ctl/craylibs/craylibs}. | |
2385 | ||
2386 | You absolutely @strong{must} use GNU make on this platform. Also, you | |
2387 | need to tell GCC where to find the assembler and the linker. The | |
2388 | simplest way to do so is by providing @option{--with-as} and | |
2389 | @option{--with-ld} to @file{configure}, e.g.@: | |
2390 | ||
3ab51846 | 2391 | @smallexample |
8c085f6f JJ |
2392 | configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld \ |
2393 | --enable-languages=c | |
3ab51846 | 2394 | @end smallexample |
71b96724 RL |
2395 | |
2396 | The comparison test during @samp{make bootstrap} fails on Unicos/Mk | |
2397 | because the assembler inserts timestamps into object files. You should | |
2398 | be able to work around this by doing @samp{make all} after getting this | |
2399 | failure. | |
2400 | ||
b8df899a | 2401 | @html |
b8db17af | 2402 | <hr /> |
b8df899a JM |
2403 | @end html |
2404 | @heading @anchor{arc-*-elf}arc-*-elf | |
2405 | Argonaut ARC processor. | |
2406 | This configuration is intended for embedded systems. | |
2407 | ||
2408 | @html | |
b8db17af | 2409 | <hr /> |
b8df899a | 2410 | @end html |
34e8290f | 2411 | @heading @anchor{arm-*-elf}arm-*-elf |
2aea0b53 | 2412 | @heading @anchor{xscale-*-*}xscale-*-* |
34e8290f NC |
2413 | ARM-family processors. Subtargets that use the ELF object format |
2414 | require GNU binutils 2.13 or newer. Such subtargets include: | |
2415 | @code{arm-*-freebsd}, @code{arm-*-netbsdelf}, @code{arm-*-*linux}, | |
2416 | @code{arm-*-rtems} and @code{arm-*-kaos}. | |
2417 | ||
2418 | @html | |
2419 | <hr /> | |
2420 | @end html | |
2421 | @heading @anchor{arm-*-coff}arm-*-coff | |
61aeb06f | 2422 | ARM-family processors. Note that there are two different varieties |
34e8290f NC |
2423 | of PE format subtarget supported: @code{arm-wince-pe} and |
2424 | @code{arm-pe} as well as a standard COFF target @code{arm-*-coff}. | |
2425 | ||
34e8290f NC |
2426 | @html |
2427 | <hr /> | |
2428 | @end html | |
2429 | @heading @anchor{arm-*-aout}arm-*-aout | |
2430 | ARM-family processors. These targets support the AOUT file format: | |
2431 | @code{arm-*-aout}, @code{arm-*-netbsd}. | |
476c334e | 2432 | |
f42974dc | 2433 | @html |
b8db17af | 2434 | <hr /> |
f42974dc | 2435 | @end html |
ef88b07d | 2436 | @heading @anchor{avr}avr |
f42974dc | 2437 | |
b8df899a | 2438 | ATMEL AVR-family micro controllers. These are used in embedded |
ca52d046 GP |
2439 | applications. There are no standard Unix configurations. |
2440 | @ifnothtml | |
2441 | @xref{AVR Options,, AVR Options, gcc, Using and Porting the GNU Compiler | |
2442 | Collection (GCC)}, | |
2443 | @end ifnothtml | |
98999d8b | 2444 | @ifhtml |
ca52d046 | 2445 | See ``AVR Options'' in the main manual |
98999d8b | 2446 | @end ifhtml |
ca52d046 | 2447 | for the list of supported MCU types. |
b8df899a | 2448 | |
161d7b59 | 2449 | Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@. |
f42974dc DW |
2450 | |
2451 | Further installation notes and other useful information about AVR tools | |
2452 | can also be obtained from: | |
2453 | ||
2454 | @itemize @bullet | |
2455 | @item | |
de7999ba MM |
2456 | @uref{http://www.openavr.org,,http://www.openavr.org} |
2457 | @item | |
d1a86812 | 2458 | @uref{http://home.overta.ru/users/denisc/,,http://home.overta.ru/users/denisc/} |
f42974dc | 2459 | @item |
d1a86812 | 2460 | @uref{http://www.amelek.gda.pl/avr/,,http://www.amelek.gda.pl/avr/} |
f42974dc DW |
2461 | @end itemize |
2462 | ||
de7999ba | 2463 | We @emph{strongly} recommend using binutils 2.13 or newer. |
f42974dc DW |
2464 | |
2465 | The following error: | |
3ab51846 | 2466 | @smallexample |
f42974dc | 2467 | Error: register required |
3ab51846 | 2468 | @end smallexample |
f42974dc DW |
2469 | |
2470 | indicates that you should upgrade to a newer version of the binutils. | |
2471 | ||
0132e321 | 2472 | @html |
b8db17af | 2473 | <hr /> |
0132e321 MH |
2474 | @end html |
2475 | @heading @anchor{c4x}c4x | |
2476 | ||
2477 | Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal | |
2478 | Processors. These are used in embedded applications. There are no | |
d8393f64 GP |
2479 | standard Unix configurations. |
2480 | @ifnothtml | |
2481 | @xref{TMS320C3x/C4x Options,, TMS320C3x/C4x Options, gcc, Using and | |
2482 | Porting the GNU Compiler Collection (GCC)}, | |
2483 | @end ifnothtml | |
98999d8b | 2484 | @ifhtml |
d8393f64 | 2485 | See ``TMS320C3x/C4x Options'' in the main manual |
98999d8b | 2486 | @end ifhtml |
d8393f64 | 2487 | for the list of supported MCU types. |
0132e321 MH |
2488 | |
2489 | GCC can be configured as a cross compiler for both the C3x and C4x | |
2490 | architectures on the same system. Use @samp{configure --target=c4x | |
2491 | --enable-languages="c,c++"} to configure. | |
2492 | ||
2493 | ||
2494 | Further installation notes and other useful information about C4x tools | |
2495 | can also be obtained from: | |
2496 | ||
2497 | @itemize @bullet | |
2498 | @item | |
d8393f64 | 2499 | @uref{http://www.elec.canterbury.ac.nz/c4x/,,http://www.elec.canterbury.ac.nz/c4x/} |
0132e321 MH |
2500 | @end itemize |
2501 | ||
0b85d816 | 2502 | @html |
b8db17af | 2503 | <hr /> |
0b85d816 HPN |
2504 | @end html |
2505 | @heading @anchor{cris}CRIS | |
2506 | ||
2507 | CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip | |
2508 | series. These are used in embedded applications. | |
2509 | ||
2510 | @ifnothtml | |
2511 | @xref{CRIS Options,, CRIS Options, gcc, Using and Porting the GNU Compiler | |
2512 | Collection (GCC)}, | |
2513 | @end ifnothtml | |
2514 | @ifhtml | |
2515 | See ``CRIS Options'' in the main manual | |
2516 | @end ifhtml | |
2517 | for a list of CRIS-specific options. | |
2518 | ||
2519 | There are a few different CRIS targets: | |
2520 | @table @code | |
2521 | @item cris-axis-aout | |
2522 | Old target. Includes a multilib for the @samp{elinux} a.out-based | |
2523 | target. No multilibs for newer architecture variants. | |
2524 | @item cris-axis-elf | |
2525 | Mainly for monolithic embedded systems. Includes a multilib for the | |
2526 | @samp{v10} core used in @samp{ETRAX 100 LX}. | |
2527 | @item cris-axis-linux-gnu | |
2528 | A GNU/Linux port for the CRIS architecture, currently targeting | |
2529 | @samp{ETRAX 100 LX} by default. | |
2530 | @end table | |
2531 | ||
2532 | For @code{cris-axis-aout} and @code{cris-axis-elf} you need binutils 2.11 | |
2533 | or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer. | |
2534 | ||
2535 | Pre-packaged tools can be obtained from | |
2536 | @uref{ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/}. More | |
2537 | information about this platform is available at | |
2538 | @uref{http://developer.axis.com/}. | |
2539 | ||
f42974dc | 2540 | @html |
b8db17af | 2541 | <hr /> |
f42974dc | 2542 | @end html |
ef88b07d | 2543 | @heading @anchor{dos}DOS |
f42974dc | 2544 | |
962e6e00 | 2545 | Please have a look at the @uref{binaries.html,,binaries page}. |
f42974dc | 2546 | |
f0523f02 | 2547 | You cannot install GCC by itself on MSDOS; it will not compile under |
f85b8d1a JM |
2548 | any MSDOS compiler except itself. You need to get the complete |
2549 | compilation package DJGPP, which includes binaries as well as sources, | |
2550 | and includes all the necessary compilation tools and libraries. | |
2551 | ||
021c4bfd | 2552 | @html |
b8db17af | 2553 | <hr /> |
021c4bfd RO |
2554 | @end html |
2555 | @heading @anchor{*-*-freebsd*}*-*-freebsd* | |
2556 | ||
f08dc6c1 LR |
2557 | The version of binutils installed in @file{/usr/bin} probably works with |
2558 | this release of GCC. However, on FreeBSD 4, bootstrapping against the | |
2559 | latest FSF binutils is known to improve overall testsuite results; and, | |
2560 | on FreeBSD/alpha, using binutils 2.14 or later is required to build libjava. | |
021c4bfd | 2561 | |
6a1dbbaf | 2562 | Support for FreeBSD 1 was discontinued in GCC 3.2. |
c7bdf0a6 | 2563 | |
f08dc6c1 LR |
2564 | Support for FreeBSD 2 will be discontinued after GCC 3.4. The |
2565 | following was true for GCC 3.1 but the current status is unknown. | |
c7bdf0a6 | 2566 | For FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All |
021c4bfd RO |
2567 | configuration support and files as shipped with GCC 2.95 are still in |
2568 | place. FreeBSD 2.2.7 has been known to bootstrap completely; however, | |
2569 | it is unknown which version of binutils was used (it is assumed that it | |
2570 | was the system copy in @file{/usr/bin}) and C++ EH failures were noted. | |
2571 | ||
2572 | For FreeBSD using the ELF file format: DWARF 2 debugging is now the | |
2573 | default for all CPU architectures. It had been the default on | |
2574 | FreeBSD/alpha since its inception. You may use @option{-gstabs} instead | |
2575 | of @option{-g}, if you really want the old debugging format. There are | |
2576 | no known issues with mixing object files and libraries with different | |
2577 | debugging formats. Otherwise, this release of GCC should now match more | |
2578 | of the configuration used in the stock FreeBSD configuration of GCC. In | |
2579 | particular, @option{--enable-threads} is now configured by default. | |
2580 | However, as a general user, do not attempt to replace the system | |
2581 | compiler with this release. Known to bootstrap and check with good | |
f08dc6c1 | 2582 | results on FreeBSD 4.9-STABLE and 5-CURRENT@. In the past, known to |
e4e7d312 | 2583 | bootstrap and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2, |
f08dc6c1 | 2584 | 4.3, 4.4, 4.5, 4.8-STABLE@. |
46fc709d LR |
2585 | |
2586 | In principle, @option{--enable-threads} is now compatible with | |
2587 | @option{--enable-libgcj} on FreeBSD@. However, it has only been built | |
e4e7d312 | 2588 | and tested on @samp{i386-*-freebsd[45]} and @samp{alpha-*-freebsd[45]}. |
8c085f6f | 2589 | The static |
6b976d99 LR |
2590 | library may be incorrectly built (symbols are missing at link time). |
2591 | There is a rare timing-based startup hang (probably involves an | |
c0478a66 | 2592 | assumption about the thread library). Multi-threaded boehm-gc (required for |
46fc709d | 2593 | libjava) exposes severe threaded signal-handling bugs on FreeBSD before |
e4e7d312 | 2594 | 4.5-RELEASE@. Other CPU architectures |
46fc709d LR |
2595 | supported by FreeBSD will require additional configuration tuning in, at |
2596 | the very least, both boehm-gc and libffi. | |
021c4bfd | 2597 | |
bc3a44db LR |
2598 | Shared @file{libgcc_s.so} is now built and installed by default. |
2599 | ||
f42974dc | 2600 | @html |
b8db17af | 2601 | <hr /> |
f42974dc | 2602 | @end html |
ef88b07d | 2603 | @heading @anchor{h8300-hms}h8300-hms |
71c6b994 | 2604 | Renesas H8/300 series of processors. |
f42974dc | 2605 | |
962e6e00 | 2606 | Please have a look at the @uref{binaries.html,,binaries page}. |
f42974dc | 2607 | |
b8df899a JM |
2608 | The calling convention and structure layout has changed in release 2.6. |
2609 | All code must be recompiled. The calling convention now passes the | |
2610 | first three arguments in function calls in registers. Structures are no | |
2611 | longer a multiple of 2 bytes. | |
2612 | ||
f42974dc | 2613 | @html |
b8db17af | 2614 | <hr /> |
f42974dc | 2615 | @end html |
ef88b07d | 2616 | @heading @anchor{hppa*-hp-hpux*}hppa*-hp-hpux* |
6a1dbbaf | 2617 | Support for HP-UX version 9 and older was discontinued in GCC 3.4. |
f42974dc | 2618 | |
9a55eab3 JDA |
2619 | We @emph{highly} recommend using gas/binutils on all hppa platforms; |
2620 | you may encounter a variety of problems when using the HP assembler. | |
f42974dc DW |
2621 | |
2622 | Specifically, @option{-g} does not work on HP-UX (since that system | |
d711cf67 JDA |
2623 | uses a peculiar debugging format which GCC does not know about), unless |
2624 | you use GAS and GDB. It may be helpful to configure GCC with the | |
38209993 | 2625 | @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and |
d711cf67 | 2626 | @option{--with-as=@dots{}} options to ensure that GCC can find GAS. |
f42974dc | 2627 | |
08b3d104 | 2628 | If you wish to use the pa-risc 2.0 architecture support with a 32-bit |
c5124497 JDA |
2629 | runtime, you must use either the HP assembler, or gas/binutils 2.11 |
2630 | or newer. | |
f42974dc | 2631 | |
d5355cb2 JDA |
2632 | There are two default scheduling models for instructions. These are |
2633 | PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc | |
2634 | architecture specified for the target machine when configuring. | |
2635 | PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when | |
2636 | the target is a @samp{hppa1*} machine. | |
806bf413 JDA |
2637 | |
2638 | The PROCESSOR_8000 model is not well suited to older processors. Thus, | |
2639 | it is important to completely specify the machine architecture when | |
2640 | configuring if you want a model other than PROCESSOR_8000. The macro | |
2641 | TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different | |
2642 | default scheduling model is desired. | |
2643 | ||
d711cf67 JDA |
2644 | As of GCC 3.5, GCC uses the UNIX 95 namespace for HP-UX 10.10 |
2645 | through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later. | |
2646 | This namespace change might cause problems when bootstrapping with | |
2647 | an earlier version of GCC or the HP compiler as essentially the same | |
2648 | namespace is required for an entire build. This problem can be avoided | |
2649 | in a number of ways. With HP cc, @env{UNIX_STD} can be set to @samp{95} | |
2650 | or @samp{98}. Another way is to add an appropriate set of predefines | |
2651 | to @env{CC}. The description for the @option{munix=} option contains | |
2652 | a list of the predefines used with each standard. | |
2653 | ||
021c4bfd | 2654 | More specific information to @samp{hppa*-hp-hpux*} targets follows. |
f42974dc | 2655 | |
f42974dc | 2656 | @html |
b8db17af | 2657 | <hr /> |
f42974dc | 2658 | @end html |
ef88b07d | 2659 | @heading @anchor{hppa*-hp-hpux10}hppa*-hp-hpux10 |
f42974dc | 2660 | |
f9047ed3 | 2661 | For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch |
161d7b59 | 2662 | @code{PHCO_19798} from HP@. HP has two sites which provide patches free of |
f42974dc DW |
2663 | charge: |
2664 | ||
2665 | @itemize @bullet | |
2666 | @item | |
2667 | @html | |
f401d0f5 | 2668 | <a href="http://us.itrc.hp.com/service/home/home.do">US, Canada, Asia-Pacific, and |
f42974dc DW |
2669 | Latin-America</a> |
2670 | @end html | |
2671 | @ifnothtml | |
f401d0f5 JDA |
2672 | @uref{http://us.itrc.hp.com/service/home/home.do,,} US, Canada, Asia-Pacific, |
2673 | and Latin-America. | |
f42974dc DW |
2674 | @end ifnothtml |
2675 | @item | |
f401d0f5 | 2676 | @uref{http://europe.itrc.hp.com/service/home/home.do,,} Europe. |
f42974dc DW |
2677 | @end itemize |
2678 | ||
2aea0b53 ZW |
2679 | The HP assembler on these systems has some problems. Most notably the |
2680 | assembler inserts timestamps into each object file it creates, causing | |
2681 | the 3-stage comparison test to fail during a @samp{make bootstrap}. | |
2682 | You should be able to continue by saying @samp{make all} after getting | |
2683 | the failure from @samp{make bootstrap}. | |
f42974dc | 2684 | |
9a55eab3 JDA |
2685 | GCC 3.5 requires CVS binutils as of April 28, 2004 or later. Earlier |
2686 | versions require binutils 2.8 or later. | |
2687 | ||
2688 | The C++ ABI has changed incompatibly in GCC 3.5. COMDAT subspaces are | |
2689 | used for one-only code and data. This resolves many of the previous | |
2690 | problems in using C++ on this target. However, the ABI is not compatible | |
2691 | with the one implemented under HP-UX 11 using secondary definitions. | |
f42974dc DW |
2692 | |
2693 | @html | |
b8db17af | 2694 | <hr /> |
f42974dc | 2695 | @end html |
ef88b07d | 2696 | @heading @anchor{hppa*-hp-hpux11}hppa*-hp-hpux11 |
f42974dc | 2697 | |
c5124497 JDA |
2698 | GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot |
2699 | be used to compile GCC 3.0 and up. | |
f269f54f | 2700 | |
c5124497 JDA |
2701 | Refer to @uref{binaries.html,,binaries} for information about obtaining |
2702 | precompiled GCC binaries for HP-UX. Precompiled binaries must be obtained | |
2703 | to build the Ada language as it can't be bootstrapped using C. Ada is | |
2704 | only available for the 32-bit PA-RISC runtime. The libffi and libjava | |
2705 | haven't been ported to HP-UX and don't build. | |
f401d0f5 | 2706 | |
c5124497 JDA |
2707 | It is possible to build GCC 3.3 starting with the bundled HP compiler, |
2708 | but the process requires several steps. GCC 3.3 can then be used to | |
2709 | build later versions. The fastjar program contains ISO C code and | |
2710 | can't be built with the HP bundled compiler. This problem can be | |
2711 | avoided by not building the Java language. For example, use the | |
2712 | @option{--enable-languages="c,c++,f77,objc"} option in your configure | |
2713 | command. | |
08b3d104 | 2714 | |
c5124497 JDA |
2715 | Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The |
2716 | bundled compiler supports only traditional C; you will need either HP's | |
2717 | unbundled compiler, or a binary distribution of GCC@. | |
8c085f6f | 2718 | |
c5124497 JDA |
2719 | There are several possible approaches to building the distribution. |
2720 | Binutils can be built first using the HP tools. Then, the GCC | |
2721 | distribution can be built. The second approach is to build GCC | |
2722 | first using the HP tools, then build binutils, then rebuild GCC. | |
2723 | There have been problems with various binary distributions, so it | |
2724 | is best not to start from a binary distribution. | |
2725 | ||
2726 | On 64-bit capable systems, there are two distinct targets. Different | |
2727 | installation prefixes must be used if both are to be installed on | |
2728 | the same system. The @samp{hppa[1-2]*-hp-hpux11*} target generates code | |
2729 | for the 32-bit PA-RISC runtime architecture and uses the HP linker. | |
2730 | The @samp{hppa64-hp-hpux11*} target generates 64-bit code for the | |
2731 | PA-RISC 2.0 architecture. The HP and GNU linkers are both supported | |
2732 | for this target. | |
2733 | ||
2734 | The script config.guess now selects the target type based on the compiler | |
2735 | detected during configuration. You must define @env{PATH} or @env{CC} so | |
2736 | that configure finds an appropriate compiler for the initial bootstrap. | |
2737 | When @env{CC} is used, the definition should contain the options that are | |
2738 | needed whenever @env{CC} is used. | |
2739 | ||
2740 | Specifically, options that determine the runtime architecture must be | |
2741 | in @env{CC} to correctly select the target for the build. It is also | |
2742 | convenient to place many other compiler options in @env{CC}. For example, | |
2743 | @env{CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"} | |
2744 | can be used to bootstrap the GCC 3.3 branch with the HP compiler in | |
2745 | 64-bit K&R/bundled mode. The @option{+DA2.0W} option will result in | |
2746 | the automatic selection of the @samp{hppa64-hp-hpux11*} target. The | |
2747 | macro definition table of cpp needs to be increased for a successful | |
2748 | build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to | |
2749 | be defined when building with the bundled compiler, or when using the | |
2750 | @option{-Ac} option. These defines aren't necessary with @option{-Ae}. | |
8c085f6f | 2751 | |
c5124497 JDA |
2752 | It is best to explicitly configure the @samp{hppa64-hp-hpux11*} target |
2753 | with the @option{--with-ld=@dots{}} option. This overrides the standard | |
2754 | search for ld. The two linkers supported on this target require different | |
2755 | commands. The default linker is determined during configuration. As a | |
2756 | result, it's not possible to switch linkers in the middle of a GCC build. | |
2757 | This has been been reported to sometimes occur in unified builds of | |
2758 | binutils and GCC. | |
2759 | ||
9a55eab3 JDA |
2760 | GCC 3.0 through 3.2 require binutils 2.11 or above. GCC 3.3 through |
2761 | GCC 3.5 require binutils 2.14 or later. | |
c5124497 JDA |
2762 | |
2763 | Although the HP assembler can be used for an initial build, it shouldn't | |
2764 | be used with any languages other than C and perhaps Fortran due to its | |
2765 | many limitations. For example, it does not support weak symbols or alias | |
2766 | definitions. As a result, explicit template instantiations are required | |
2767 | when using C++. This makes it difficult if not impossible to build many | |
2768 | C++ applications. You can't generate debugging information when using | |
2769 | the HP assembler. Finally, @samp{make bootstrap} fails in the final | |
2770 | comparison of object modules due to the time stamps that it inserts into | |
2771 | the modules. The bootstrap can be continued from this point with | |
2772 | @samp{make all}. | |
2773 | ||
2774 | A recent linker patch must be installed for the correct operation of | |
2775 | GCC 3.3 and later. @code{PHSS_26559} and @code{PHSS_24304} are the | |
2776 | oldest linker patches that are known to work. They are for HP-UX | |
2777 | 11.00 and 11.11, respectively. @code{PHSS_24303}, the companion to | |
2778 | @code{PHSS_24304}, might be usable but it hasn't been tested. These | |
2779 | patches have been superseded. Consult the HP patch database to obtain | |
2780 | the currently recommended linker patch for your system. | |
2781 | ||
2782 | The patches are necessary for the support of weak symbols on the | |
2783 | 32-bit port, and for the running of initializers and finalizers. Weak | |
2784 | symbols are implemented using SOM secondary definition symbols. Prior | |
2785 | to HP-UX 11, there are bugs in the linker support for secondary symbols. | |
2786 | The patches correct a problem of linker core dumps creating shared | |
2787 | libraries containing secondary symbols, as well as various other | |
2788 | linking issues involving secondary symbols. | |
2789 | ||
2790 | GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to | |
2791 | run initializers and finalizers on the 64-bit port. The 32-bit port | |
2792 | uses the linker @option{+init} and @option{+fini} options for the same | |
2793 | purpose. The patches correct various problems with the +init/+fini | |
2794 | options, including program core dumps. Binutils 2.14 corrects a | |
2795 | problem on the 64-bit port resulting from HP's non-standard use of | |
2796 | the .init and .fini sections for array initializers and finalizers. | |
f401d0f5 JDA |
2797 | |
2798 | There are a number of issues to consider in selecting which linker to | |
c5124497 | 2799 | use with the 64-bit port. The GNU 64-bit linker can only create dynamic |
f401d0f5 JDA |
2800 | binaries. The @option{-static} option causes linking with archive |
2801 | libraries but doesn't produce a truly static binary. Dynamic binaries | |
2802 | still require final binding by the dynamic loader to resolve a set of | |
2803 | dynamic-loader-defined symbols. The default behavior of the HP linker | |
2804 | is the same as the GNU linker. However, it can generate true 64-bit | |
2805 | static binaries using the @option{+compat} option. | |
2806 | ||
2807 | The HP 64-bit linker doesn't support linkonce semantics. As a | |
2808 | result, C++ programs have many more sections than they should. | |
2809 | ||
2810 | The GNU 64-bit linker has some issues with shared library support | |
2811 | and exceptions. As a result, we only support libgcc in archive | |
2812 | format. For similar reasons, dwarf2 unwind and exception support | |
2813 | are disabled. The GNU linker also has problems creating binaries | |
2814 | with @option{-static}. It doesn't provide stubs for internal | |
2815 | calls to global functions in shared libraries, so these calls | |
2816 | can't be overloaded. | |
581d9404 | 2817 | |
c5124497 JDA |
2818 | Thread support is not implemented in GCC 3.0 through 3.2, so the |
2819 | @option{--enable-threads} configure option does not work. In 3.3 | |
2820 | and later, POSIX threads are supported. The optional DCE thread | |
2821 | library is not supported. | |
581d9404 JDA |
2822 | |
2823 | This port still is undergoing significant development. | |
08b3d104 | 2824 | |
f42974dc | 2825 | @html |
b8db17af | 2826 | <hr /> |
f42974dc | 2827 | @end html |
ef88b07d | 2828 | @heading @anchor{*-*-linux-gnu}*-*-linux-gnu |
f42974dc | 2829 | |
9e80ada7 PE |
2830 | Versions of libstdc++-v3 starting with 3.2.1 require bugfixes present |
2831 | in glibc 2.2.5 and later. More information is available in the | |
2832 | libstdc++-v3 documentation. | |
2833 | ||
b8df899a | 2834 | @html |
b8db17af | 2835 | <hr /> |
b8df899a JM |
2836 | @end html |
2837 | @heading @anchor{ix86-*-linux*aout}i?86-*-linux*aout | |
2838 | Use this configuration to generate @file{a.out} binaries on Linux-based | |
41ca24de | 2839 | GNU systems. This configuration is being superseded. |
b8df899a | 2840 | |
f42974dc | 2841 | @html |
b8db17af | 2842 | <hr /> |
f42974dc | 2843 | @end html |
ef88b07d | 2844 | @heading @anchor{ix86-*-linux*}i?86-*-linux* |
f42974dc | 2845 | |
1ea6f4c8 DH |
2846 | As of GCC 3.3, binutils 2.13.1 or later is required for this platform. |
2847 | See @uref{http://gcc.gnu.org/PR10877,,bug 10877} for more information. | |
f42974dc DW |
2848 | |
2849 | If you receive Signal 11 errors when building on GNU/Linux, then it is | |
2850 | possible you have a hardware problem. Further information on this can be | |
2851 | found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}. | |
2852 | ||
2853 | @html | |
b8db17af | 2854 | <hr /> |
f42974dc | 2855 | @end html |
ef88b07d | 2856 | @heading @anchor{ix86-*-sco3.2v5*}i?86-*-sco3.2v5* |
b8df899a | 2857 | Use this for the SCO OpenServer Release 5 family of operating systems. |
f42974dc DW |
2858 | |
2859 | Unlike earlier versions of GCC, the ability to generate COFF with this | |
2860 | target is no longer provided. | |
2861 | ||
021c4bfd | 2862 | Earlier versions of GCC emitted DWARF 1 when generating ELF to allow |
f42974dc | 2863 | the system debugger to be used. That support was too burdensome to |
021c4bfd | 2864 | maintain. GCC now emits only DWARF 2 for this target. This means you |
f42974dc | 2865 | may use either the UDK debugger or GDB to debug programs built by this |
161d7b59 | 2866 | version of GCC@. |
f42974dc | 2867 | |
ac24fc99 KJ |
2868 | GCC is now only supported on releases 5.0.4 and later, and requires that |
2869 | you install Support Level Supplement OSS646B or later, and Support Level | |
2870 | Supplement OSS631C or later. If you are using release 5.0.7 of | |
2871 | OpenServer, you must have at least the first maintenance pack installed | |
2872 | (this includes the relevant portions of OSS646). OSS646, also known as | |
2873 | the "Execution Environment Update", provides updated link editors and | |
2874 | assemblers, as well as updated standard C and math libraries. The C | |
2875 | startup modules are also updated to support the System V gABI draft, and | |
0b4be7de | 2876 | GCC relies on that behavior. OSS631 provides a collection of commonly |
ac24fc99 KJ |
2877 | used open source libraries, some of which GCC depends on (such as GNU |
2878 | gettext and zlib). SCO OpenServer Release 5.0.7 has all of this built | |
2879 | in by default, but OSS631C and later also apply to that release. Please | |
2880 | visit | |
2881 | @uref{ftp://ftp.sco.com/pub/openserver5,,ftp://ftp.sco.com/pub/openserver5} | |
2882 | for the latest versions of these (and other potentially useful) | |
2883 | supplements. | |
2884 | ||
2885 | Although there is support for using the native assembler, it is | |
2886 | recommended that you configure GCC to use the GNU assembler. You do | |
2887 | this by using the flags | |
2888 | @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}}. You should | |
2889 | use a modern version of GNU binutils. Version 2.13.2.1 was used for all | |
2890 | testing. In general, only the @option{--with-gnu-as} option is tested. | |
2891 | A modern bintuils (as well as a plethora of other development related | |
2892 | GNU utilities) can be found in Support Level Supplement OSS658A, the | |
2893 | "GNU Development Tools" package. See the SCO web and ftp sites for details. | |
2894 | That package also contains the currently "officially supported" version of | |
daf2f129 | 2895 | GCC, version 2.95.3. It is useful for bootstrapping this version. |
f42974dc | 2896 | |
f42974dc | 2897 | @html |
b8db17af | 2898 | <hr /> |
f42974dc | 2899 | @end html |
ef88b07d | 2900 | @heading @anchor{ix86-*-udk}i?86-*-udk |
f42974dc DW |
2901 | |
2902 | This target emulates the SCO Universal Development Kit and requires that | |
f9047ed3 JM |
2903 | package be installed. (If it is installed, you will have a |
2904 | @file{/udk/usr/ccs/bin/cc} file present.) It's very much like the | |
b953cc4b | 2905 | @samp{i?86-*-unixware7*} target |
f42974dc DW |
2906 | but is meant to be used when hosting on a system where UDK isn't the |
2907 | default compiler such as OpenServer 5 or Unixware 2. This target will | |
f9047ed3 | 2908 | generate binaries that will run on OpenServer, Unixware 2, or Unixware 7, |
161d7b59 | 2909 | with the same warnings and caveats as the SCO UDK@. |
f42974dc | 2910 | |
f42974dc DW |
2911 | This target is a little tricky to build because we have to distinguish |
2912 | it from the native tools (so it gets headers, startups, and libraries | |
f9047ed3 | 2913 | from the right place) while making the tools not think we're actually |
f42974dc DW |
2914 | building a cross compiler. The easiest way to do this is with a configure |
2915 | command like this: | |
2916 | ||
3ab51846 | 2917 | @smallexample |
8c085f6f JJ |
2918 | CC=/udk/usr/ccs/bin/cc @var{/your/path/to}/gcc/configure \ |
2919 | --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk- | |
3ab51846 | 2920 | @end smallexample |
f42974dc | 2921 | |
6cfb3f16 | 2922 | @emph{You should substitute @samp{i686} in the above command with the appropriate |
f42974dc DW |
2923 | processor for your host.} |
2924 | ||
021c4bfd RO |
2925 | After the usual @samp{make bootstrap} and |
2926 | @samp{make install}, you can then access the UDK-targeted GCC | |
38209993 LG |
2927 | tools by adding @command{udk-} before the commonly known name. For |
2928 | example, to invoke the C compiler, you would use @command{udk-gcc}. | |
2929 | They will coexist peacefully with any native-target GCC tools you may | |
2930 | have installed. | |
f42974dc DW |
2931 | |
2932 | ||
b499d9ab | 2933 | @html |
b8db17af | 2934 | <hr /> |
b499d9ab JJ |
2935 | @end html |
2936 | @heading @anchor{ia64-*-linux}ia64-*-linux | |
2937 | IA-64 processor (also known as IPF, or Itanium Processor Family) | |
2938 | running GNU/Linux. | |
2939 | ||
443728bb L |
2940 | If you are using the installed system libunwind library with |
2941 | @option{--with-system-libunwind}, then you must use libunwind 0.98 or | |
2942 | later. | |
bcd11e5e | 2943 | |
b499d9ab JJ |
2944 | None of the following versions of GCC has an ABI that is compatible |
2945 | with any of the other versions in this list, with the exception that | |
2946 | Red Hat 2.96 and Trillian 000171 are compatible with each other: | |
41ca24de | 2947 | 3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717. |
b499d9ab | 2948 | This primarily affects C++ programs and programs that create shared libraries. |
41ca24de DH |
2949 | GCC 3.1 or later is recommended for compiling linux, the kernel. |
2950 | As of version 3.1 GCC is believed to be fully ABI compliant, and hence no | |
2951 | more major ABI changes are expected. | |
b499d9ab | 2952 | |
959a73a4 DH |
2953 | @html |
2954 | <hr /> | |
2955 | @end html | |
2956 | @heading @anchor{ia64-*-hpux*}ia64-*-hpux* | |
2957 | Building GCC on this target requires the GNU Assembler. The bundled HP | |
2958 | assembler will not work. To prevent GCC from using the wrong assembler, | |
2959 | the option @option{--with-gnu-as} may be necessary. | |
2960 | ||
2961 | The GCC libunwind library has not been ported to HPUX. This means that for | |
2962 | GCC versions 3.2.3 and earlier, @option{--enable-libunwind-exceptions} | |
2963 | is required to build GCC. For GCC 3.3 and later, this is the default. | |
443728bb L |
2964 | For gcc 3.4.3 and later, @option{--enable-libunwind-exceptions} is |
2965 | removed and the system libunwind library will always be used. | |
959a73a4 | 2966 | |
f42974dc | 2967 | @html |
b8db17af | 2968 | <hr /> |
f42974dc DW |
2969 | <!-- rs6000-ibm-aix*, powerpc-ibm-aix* --> |
2970 | @end html | |
ef88b07d | 2971 | @heading @anchor{*-ibm-aix*}*-ibm-aix* |
6a1dbbaf | 2972 | Support for AIX version 3 and older was discontinued in GCC 3.4. |
f42974dc | 2973 | |
41ca24de | 2974 | AIX Make frequently has problems with GCC makefiles. GNU Make 3.79.1 or |
f42974dc DW |
2975 | newer is recommended to build on this platform. |
2976 | ||
e8d8a034 DE |
2977 | To speed up the configuration phases of bootstrapping and installing GCC, |
2978 | one may use GNU Bash instead of AIX @command{/bin/sh}, e.g., | |
2979 | ||
2980 | @smallexample | |
2981 | % CONFIG_SHELL=/opt/freeware/bin/bash | |
2982 | % export CONFIG_SHELL | |
2983 | @end smallexample | |
2984 | ||
2985 | and then proceed as described in @uref{build.html,,the build instructions}, | |
2986 | where we strongly recommend using GNU make and specifying an absolute path | |
2987 | to invoke @var{srcdir}/configure. | |
2988 | ||
6cfb3f16 | 2989 | Errors involving @code{alloca} when building GCC generally are due |
021c4bfd | 2990 | to an incorrect definition of @code{CC} in the Makefile or mixing files |
161d7b59 | 2991 | compiled with the native C compiler and GCC@. During the stage1 phase of |
6cfb3f16 JM |
2992 | the build, the native AIX compiler @strong{must} be invoked as @command{cc} |
2993 | (not @command{xlc}). Once @command{configure} has been informed of | |
2994 | @command{xlc}, one needs to use @samp{make distclean} to remove the | |
38209993 | 2995 | configure cache files and ensure that @env{CC} environment variable |
f42974dc DW |
2996 | does not provide a definition that will confuse @command{configure}. |
2997 | If this error occurs during stage2 or later, then the problem most likely | |
2998 | is the version of Make (see above). | |
2999 | ||
f0483418 DE |
3000 | The native @command{as} and @command{ld} are recommended for bootstrapping |
3001 | on AIX 4 and required for bootstrapping on AIX 5L. The GNU Assembler | |
3002 | reports that it supports WEAK symbols on AIX 4, which causes GCC to try to | |
3003 | utilize weak symbol functionality although it is not supported. The GNU | |
3004 | Assembler and Linker do not support AIX 5L sufficiently to bootstrap GCC. | |
3005 | The native AIX tools do interoperate with GCC@. | |
df002c7d | 3006 | |
04d2be8e | 3007 | Building @file{libstdc++.a} requires a fix for an AIX Assembler bug |
bb674cef DE |
3008 | APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a |
3009 | fix for another AIX Assembler bug and a co-dependent AIX Archiver fix | |
06e7f299 | 3010 | referenced as APAR IY53606 (AIX 5.2) or a APAR IY54774 (AIX 5.1) |
2705baf5 | 3011 | |
bb674cef | 3012 | @samp{libstdc++} in GCC 3.4 increments the major version number of the |
fdf68669 | 3013 | shared object and GCC installation places the @file{libstdc++.a} |
bb674cef DE |
3014 | shared library in a common location which will overwrite the and GCC |
3015 | 3.3 version of the shared library. Applications either need to be | |
3016 | re-linked against the new shared library or the GCC 3.1 and GCC 3.3 | |
3017 | versions of the @samp{libstdc++} shared object needs to be available | |
3018 | to the AIX runtime loader. The GCC 3.1 @samp{libstdc++.so.4}, if | |
3019 | present, and GCC 3.3 @samp{libstdc++.so.5} shared objects can be | |
3020 | installed for runtime dynamic loading using the following steps to set | |
3021 | the @samp{F_LOADONLY} flag in the shared object for @emph{each} | |
fdf68669 DE |
3022 | multilib @file{libstdc++.a} installed: |
3023 | ||
bb674cef DE |
3024 | Extract the shared objects from the currently installed |
3025 | @file{libstdc++.a} archive: | |
3ab51846 | 3026 | @smallexample |
bb674cef | 3027 | % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5 |
3ab51846 | 3028 | @end smallexample |
fdf68669 DE |
3029 | |
3030 | Enable the @samp{F_LOADONLY} flag so that the shared object will be | |
3031 | available for runtime dynamic loading, but not linking: | |
3ab51846 | 3032 | @smallexample |
bb674cef | 3033 | % strip -e libstdc++.so.4 libstdc++.so.5 |
3ab51846 | 3034 | @end smallexample |
fdf68669 | 3035 | |
bb674cef | 3036 | Archive the runtime-only shared object in the GCC 3.4 |
fdf68669 | 3037 | @file{libstdc++.a} archive: |
3ab51846 | 3038 | @smallexample |
bb674cef | 3039 | % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5 |
3ab51846 | 3040 | @end smallexample |
fdf68669 | 3041 | |
df002c7d DE |
3042 | Linking executables and shared libraries may produce warnings of |
3043 | duplicate symbols. The assembly files generated by GCC for AIX always | |
3044 | have included multiple symbol definitions for certain global variable | |
3045 | and function declarations in the original program. The warnings should | |
3046 | not prevent the linker from producing a correct library or runnable | |
3047 | executable. | |
3048 | ||
6cfb3f16 | 3049 | AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and |
df002c7d DE |
3050 | 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1 |
3051 | to parse archive libraries did not handle the new format correctly. | |
3052 | These routines are used by GCC and result in error messages during | |
6cfb3f16 | 3053 | linking such as ``not a COFF file''. The version of the routines shipped |
df002c7d DE |
3054 | with AIX 4.3.1 should work for a 32-bit environment. The @option{-g} |
3055 | option of the archive command may be used to create archives of 32-bit | |
6cfb3f16 | 3056 | objects using the original ``small format''. A correct version of the |
d5d8d540 | 3057 | routines is shipped with AIX 4.3.2 and above. |
df002c7d | 3058 | |
f42974dc DW |
3059 | Some versions of the AIX binder (linker) can fail with a relocation |
3060 | overflow severe error when the @option{-bbigtoc} option is used to link | |
161d7b59 | 3061 | GCC-produced object files into an executable that overflows the TOC@. A fix |
f42974dc DW |
3062 | for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is |
3063 | available from IBM Customer Support and from its | |
d5d8d540 | 3064 | @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com} |
f42974dc DW |
3065 | website as PTF U455193. |
3066 | ||
df002c7d | 3067 | The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core |
161d7b59 | 3068 | with a segmentation fault when invoked by any version of GCC@. A fix for |
df002c7d | 3069 | APAR IX87327 is available from IBM Customer Support and from its |
d5d8d540 | 3070 | @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com} |
df002c7d | 3071 | website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above. |
f42974dc DW |
3072 | |
3073 | The initial assembler shipped with AIX 4.3.0 generates incorrect object | |
3074 | files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS | |
3075 | TO ASSEMBLE/BIND) is available from IBM Customer Support and from its | |
d5d8d540 | 3076 | @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com} |
f42974dc DW |
3077 | website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above. |
3078 | ||
161d7b59 | 3079 | AIX provides National Language Support (NLS)@. Compilers and assemblers |
df002c7d | 3080 | use NLS to support locale-specific representations of various data |
6cfb3f16 | 3081 | formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for |
df002c7d DE |
3082 | separating decimal fractions). There have been problems reported where |
3083 | GCC does not produce the same floating-point formats that the assembler | |
c771326b | 3084 | expects. If one encounters this problem, set the @env{LANG} |
6cfb3f16 | 3085 | environment variable to @samp{C} or @samp{En_US}. |
f42974dc | 3086 | |
5791e6da DE |
3087 | By default, GCC for AIX 4.1 and above produces code that can be used on |
3088 | both Power or PowerPC processors. | |
3089 | ||
d5d8d540 DE |
3090 | A default can be specified with the @option{-mcpu=@var{cpu_type}} |
3091 | switch and using the configure option @option{--with-cpu-@var{cpu_type}}. | |
f42974dc | 3092 | |
e3223ea2 | 3093 | @html |
b8db17af | 3094 | <hr /> |
e3223ea2 DC |
3095 | @end html |
3096 | @heading @anchor{ip2k-*-elf}ip2k-*-elf | |
3097 | Ubicom IP2022 micro controller. | |
3098 | This configuration is intended for embedded systems. | |
3099 | There are no standard Unix configurations. | |
3100 | ||
3101 | Use @samp{configure --target=ip2k-elf --enable-languages=c} to configure GCC@. | |
3102 | ||
6b3d1e47 SC |
3103 | @html |
3104 | <hr /> | |
3105 | @end html | |
3106 | @heading @anchor{iq2000-*-elf}iq2000-*-elf | |
3107 | Vitesse IQ2000 processors. These are used in embedded | |
3108 | applications. There are no standard Unix configurations. | |
3109 | ||
b8df899a | 3110 | @html |
b8db17af | 3111 | <hr /> |
b8df899a JM |
3112 | @end html |
3113 | @heading @anchor{m32r-*-elf}m32r-*-elf | |
25f47a4c | 3114 | Renesas M32R processor. |
b8df899a JM |
3115 | This configuration is intended for embedded systems. |
3116 | ||
b8df899a | 3117 | @html |
b8db17af | 3118 | <hr /> |
b8df899a JM |
3119 | @end html |
3120 | @heading @anchor{m6811-elf}m6811-elf | |
3121 | Motorola 68HC11 family micro controllers. These are used in embedded | |
3122 | applications. There are no standard Unix configurations. | |
3123 | ||
3124 | @html | |
b8db17af | 3125 | <hr /> |
b8df899a JM |
3126 | @end html |
3127 | @heading @anchor{m6812-elf}m6812-elf | |
3128 | Motorola 68HC12 family micro controllers. These are used in embedded | |
3129 | applications. There are no standard Unix configurations. | |
3130 | ||
b8df899a | 3131 | @html |
b8db17af | 3132 | <hr /> |
b8df899a JM |
3133 | @end html |
3134 | @heading @anchor{m68k-hp-hpux}m68k-hp-hpux | |
161d7b59 JM |
3135 | HP 9000 series 300 or 400 running HP-UX@. HP-UX version 8.0 has a bug in |
3136 | the assembler that prevents compilation of GCC@. This | |
b8df899a JM |
3137 | bug manifests itself during the first stage of compilation, while |
3138 | building @file{libgcc2.a}: | |
3139 | ||
3140 | @smallexample | |
3141 | _floatdisf | |
3142 | cc1: warning: `-g' option not supported on this version of GCC | |
3143 | cc1: warning: `-g1' option not supported on this version of GCC | |
3144 | ./xgcc: Internal compiler error: program as got fatal signal 11 | |
3145 | @end smallexample | |
3146 | ||
3147 | A patched version of the assembler is available as the file | |
3148 | @uref{ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler}. If you | |
3149 | have HP software support, the patch can also be obtained directly from | |
3150 | HP, as described in the following note: | |
3151 | ||
3152 | @quotation | |
3153 | This is the patched assembler, to patch SR#1653-010439, where the | |
3154 | assembler aborts on floating point constants. | |
3155 | ||
3156 | The bug is not really in the assembler, but in the shared library | |
3157 | version of the function ``cvtnum(3c)''. The bug on ``cvtnum(3c)'' is | |
3158 | SR#4701-078451. Anyway, the attached assembler uses the archive | |
3159 | library version of ``cvtnum(3c)'' and thus does not exhibit the bug. | |
3160 | @end quotation | |
3161 | ||
3162 | This patch is also known as PHCO_4484. | |
3163 | ||
41ca24de | 3164 | In addition gdb does not understand that native HP-UX format, so |
b8df899a JM |
3165 | you must use gas if you wish to use gdb. |
3166 | ||
3167 | On HP-UX version 8.05, but not on 8.07 or more recent versions, the | |
7ba4ca63 | 3168 | @command{fixproto} shell script triggers a bug in the system shell. If you |
b8df899a | 3169 | encounter this problem, upgrade your operating system or use BASH (the |
7ba4ca63 | 3170 | GNU shell) to run @command{fixproto}. This bug will cause the fixproto |
b8df899a JM |
3171 | program to report an error of the form: |
3172 | ||
3ab51846 | 3173 | @smallexample |
b8df899a | 3174 | ./fixproto: sh internal 1K buffer overflow |
3ab51846 | 3175 | @end smallexample |
b8df899a JM |
3176 | |
3177 | To fix this, you can also change the first line of the fixproto script | |
3178 | to look like: | |
3179 | ||
3ab51846 | 3180 | @smallexample |
b8df899a | 3181 | #!/bin/ksh |
3ab51846 | 3182 | @end smallexample |
b8df899a | 3183 | |
b8df899a | 3184 | @html |
b8db17af | 3185 | <hr /> |
b8df899a JM |
3186 | @end html |
3187 | @heading @anchor{mips-*-*}mips-*-* | |
b8df899a JM |
3188 | If on a MIPS system you get an error message saying ``does not have gp |
3189 | sections for all it's [sic] sectons [sic]'', don't worry about it. This | |
3190 | happens whenever you use GAS with the MIPS linker, but there is not | |
3191 | really anything wrong, and it is okay to use the output file. You can | |
3192 | stop such warnings by installing the GNU linker. | |
3193 | ||
3194 | It would be nice to extend GAS to produce the gp tables, but they are | |
3195 | optional, and there should not be a warning about their absence. | |
3196 | ||
26979a17 PE |
3197 | The libstdc++ atomic locking routines for MIPS targets requires MIPS II |
3198 | and later. A patch went in just after the GCC 3.3 release to | |
3199 | make @samp{mips*-*-*} use the generic implementation instead. You can also | |
3200 | configure for @samp{mipsel-elf} as a workaround. The | |
3201 | @samp{mips*-*-linux*} target continues to use the MIPS II routines. More | |
3202 | work on this is expected in future releases. | |
3203 | ||
01e97976 JM |
3204 | Cross-compilers for the Mips as target using the Mips assembler |
3205 | currently do not work, because the auxiliary programs | |
3206 | @file{mips-tdump.c} and @file{mips-tfile.c} can't be compiled on | |
3207 | anything but a Mips. It does work to cross compile for a Mips | |
3208 | if you use the GNU assembler and linker. | |
3209 | ||
5fb57097 EB |
3210 | @html |
3211 | <hr /> | |
3212 | @end html | |
b953cc4b RO |
3213 | @heading @anchor{mips-sgi-irix5}mips-sgi-irix5 |
3214 | ||
7e270317 RO |
3215 | In order to compile GCC on an SGI running IRIX 5, the @samp{compiler_dev.hdr} |
3216 | subsystem must be installed from the IDO CD-ROM supplied by SGI@. | |
3217 | It is also available for download from | |
8df5a2b4 | 3218 | @uref{ftp://ftp.sgi.com/sgi/IRIX5.3/iris-development-option-5.3.tardist}. |
f42974dc | 3219 | |
213ba345 RO |
3220 | If you use the MIPS C compiler to bootstrap, it may be necessary |
3221 | to increase its table size for switch statements with the | |
3222 | @option{-Wf,-XNg1500} option. If you use the @option{-O2} | |
3223 | optimization option, you also need to use @option{-Olimit 3000}. | |
f42974dc | 3224 | |
7e270317 | 3225 | To enable debugging under IRIX 5, you must use GNU binutils 2.15 or |
82563d35 RS |
3226 | later, and use the @option{--with-gnu-ld} @command{configure} option |
3227 | when configuring GCC@. You need to use GNU @command{ar} and @command{nm}, | |
3228 | also distributed with GNU binutils. | |
f42974dc DW |
3229 | |
3230 | @html | |
b8db17af | 3231 | <hr /> |
f42974dc | 3232 | @end html |
b953cc4b | 3233 | @heading @anchor{mips-sgi-irix6}mips-sgi-irix6 |
f42974dc | 3234 | |
7e270317 | 3235 | If you are using SGI's MIPSpro @command{cc} as your bootstrap compiler, you must |
f42974dc DW |
3236 | ensure that the N32 ABI is in use. To test this, compile a simple C |
3237 | file with @command{cc} and then run @command{file} on the | |
3238 | resulting object file. The output should look like: | |
3239 | ||
3ab51846 | 3240 | @smallexample |
213ba345 | 3241 | test.o: ELF N32 MSB @dots{} |
3ab51846 | 3242 | @end smallexample |
f42974dc DW |
3243 | |
3244 | If you see: | |
213ba345 | 3245 | |
3ab51846 | 3246 | @smallexample |
213ba345 | 3247 | test.o: ELF 32-bit MSB @dots{} |
3ab51846 | 3248 | @end smallexample |
213ba345 RO |
3249 | |
3250 | or | |
3251 | ||
3ab51846 | 3252 | @smallexample |
213ba345 | 3253 | test.o: ELF 64-bit MSB @dots{} |
3ab51846 | 3254 | @end smallexample |
f42974dc | 3255 | |
213ba345 | 3256 | then your version of @command{cc} uses the O32 or N64 ABI by default. You |
38209993 | 3257 | should set the environment variable @env{CC} to @samp{cc -n32} |
82563d35 | 3258 | before configuring GCC@. |
f42974dc | 3259 | |
0fca60ab | 3260 | If you want the resulting @command{gcc} to run on old 32-bit systems |
7e270317 | 3261 | with the MIPS R4400 CPU, you need to ensure that only code for the @samp{mips3} |
0fca60ab RO |
3262 | instruction set architecture (ISA) is generated. While GCC 3.x does |
3263 | this correctly, both GCC 2.95 and SGI's MIPSpro @command{cc} may change | |
3264 | the ISA depending on the machine where GCC is built. Using one of them | |
7e270317 RO |
3265 | as the bootstrap compiler may result in @samp{mips4} code, which won't run at |
3266 | all on @samp{mips3}-only systems. For the test program above, you should see: | |
0fca60ab | 3267 | |
3ab51846 | 3268 | @smallexample |
0fca60ab | 3269 | test.o: ELF N32 MSB mips-3 @dots{} |
3ab51846 | 3270 | @end smallexample |
0fca60ab RO |
3271 | |
3272 | If you get: | |
3273 | ||
3ab51846 | 3274 | @smallexample |
0fca60ab | 3275 | test.o: ELF N32 MSB mips-4 @dots{} |
3ab51846 | 3276 | @end smallexample |
0fca60ab RO |
3277 | |
3278 | instead, you should set the environment variable @env{CC} to @samp{cc | |
3279 | -n32 -mips3} or @samp{gcc -mips3} respectively before configuring GCC@. | |
3280 | ||
82563d35 RS |
3281 | MIPSpro C 7.4 may cause bootstrap failures, due to a bug when inlining |
3282 | @code{memcmp}. Either add @code{-U__INLINE_INTRINSICS} to the @env{CC} | |
3283 | environment variable as a workaround or upgrade to MIPSpro C 7.4.1m. | |
3284 | ||
7e270317 RO |
3285 | GCC on IRIX 6 is usually built to support the N32, O32 and N64 ABIs. If |
3286 | you build GCC on a system that doesn't have the N64 libraries installed | |
3287 | or cannot run 64-bit binaries, | |
213ba345 | 3288 | you need to configure with @option{--disable-multilib} so GCC doesn't |
7e270317 RO |
3289 | try to use them. This will disable building the O32 libraries, too. |
3290 | Look for @file{/usr/lib64/libc.so.1} to see if you | |
213ba345 RO |
3291 | have the 64-bit libraries installed. |
3292 | ||
7e270317 RO |
3293 | To enable debugging for the O32 ABI, you must use GNU @command{as} from |
3294 | GNU binutils 2.15 or later. You may also use GNU @command{ld}, but | |
3295 | this is not required and currently causes some problems with Ada. | |
f42974dc | 3296 | |
b953cc4b RO |
3297 | The @option{--enable-threads} option doesn't currently work, a patch is |
3298 | in preparation for a future release. The @option{--enable-libgcj} | |
3299 | option is disabled by default: IRIX 6 uses a very low default limit | |
7e270317 | 3300 | (20480) for the command line length. Although @command{libtool} contains a |
b953cc4b RO |
3301 | workaround for this problem, at least the N64 @samp{libgcj} is known not |
3302 | to build despite this, running into an internal error of the native | |
3303 | @command{ld}. A sure fix is to increase this limit (@samp{ncargs}) to | |
3304 | its maximum of 262144 bytes. If you have root access, you can use the | |
3305 | @command{systune} command to do this. | |
3306 | ||
7e270317 | 3307 | See @uref{http://freeware.sgi.com/} for more |
3aa8219e | 3308 | information about using GCC on IRIX platforms. |
f42974dc | 3309 | |
b8df899a | 3310 | @html |
b8db17af | 3311 | <hr /> |
b8df899a | 3312 | @end html |
021c4bfd | 3313 | @heading @anchor{powerpc*-*-*}powerpc-*-* |
b8df899a | 3314 | |
6cfb3f16 JM |
3315 | You can specify a default version for the @option{-mcpu=@var{cpu_type}} |
3316 | switch by using the configure option @option{--with-cpu-@var{cpu_type}}. | |
b8df899a | 3317 | |
4f2b1139 | 3318 | @html |
b8db17af | 3319 | <hr /> |
4f2b1139 SS |
3320 | @end html |
3321 | @heading @anchor{powerpc-*-darwin*}powerpc-*-darwin* | |
3322 | PowerPC running Darwin (Mac OS X kernel). | |
3323 | ||
4f2b1139 SS |
3324 | Pre-installed versions of Mac OS X may not include any developer tools, |
3325 | meaning that you will not be able to build GCC from source. Tool | |
3326 | binaries are available at | |
11292480 | 3327 | @uref{http://developer.apple.com/tools/compilers.html} (free |
4f2b1139 SS |
3328 | registration required). |
3329 | ||
aeb732c1 | 3330 | This version of GCC requires at least cctools-528. |
b89a3806 GK |
3331 | |
3332 | The version of GCC shipped by Apple typically includes a number of | |
3333 | extensions not available in a standard GCC release. These extensions | |
aeb732c1 | 3334 | are generally for backwards compatibility and best avoided. |
4f2b1139 | 3335 | |
021c4bfd | 3336 | @html |
b8db17af | 3337 | <hr /> |
021c4bfd RO |
3338 | @end html |
3339 | @heading @anchor{powerpc-*-elf}powerpc-*-elf, powerpc-*-sysv4 | |
3340 | PowerPC system in big endian mode, running System V.4. | |
3341 | ||
f42974dc | 3342 | @html |
b8db17af | 3343 | <hr /> |
f42974dc | 3344 | @end html |
ef88b07d | 3345 | @heading @anchor{powerpc-*-linux-gnu*}powerpc-*-linux-gnu* |
f42974dc | 3346 | |
f9047ed3 | 3347 | You will need |
e8a7b0c2 | 3348 | @uref{ftp://ftp.kernel.org/pub/linux/devel/binutils,,binutils 2.13.90.0.10} |
791a949f | 3349 | or newer for a working GCC@. |
f42974dc | 3350 | |
edf1b3f3 | 3351 | @html |
b8db17af | 3352 | <hr /> |
edf1b3f3 AC |
3353 | @end html |
3354 | @heading @anchor{powerpc-*-netbsd*}powerpc-*-netbsd* | |
3355 | PowerPC system in big endian mode running NetBSD@. To build the | |
a38f87a9 | 3356 | documentation you will need Texinfo version 4.2 (NetBSD 1.5.1 included |
edf1b3f3 AC |
3357 | Texinfo version 3.12). |
3358 | ||
b8df899a | 3359 | @html |
b8db17af | 3360 | <hr /> |
b8df899a JM |
3361 | @end html |
3362 | @heading @anchor{powerpc-*-eabisim}powerpc-*-eabisim | |
3363 | Embedded PowerPC system in big endian mode for use in running under the | |
3364 | PSIM simulator. | |
3365 | ||
b8df899a | 3366 | @html |
b8db17af | 3367 | <hr /> |
b8df899a JM |
3368 | @end html |
3369 | @heading @anchor{powerpc-*-eabi}powerpc-*-eabi | |
3370 | Embedded PowerPC system in big endian mode. | |
3371 | ||
b8df899a | 3372 | @html |
b8db17af | 3373 | <hr /> |
b8df899a JM |
3374 | @end html |
3375 | @heading @anchor{powerpcle-*-elf}powerpcle-*-elf, powerpcle-*-sysv4 | |
3376 | PowerPC system in little endian mode, running System V.4. | |
3377 | ||
b8df899a | 3378 | @html |
b8db17af | 3379 | <hr /> |
b8df899a JM |
3380 | @end html |
3381 | @heading @anchor{powerpcle-*-eabisim}powerpcle-*-eabisim | |
3382 | Embedded PowerPC system in little endian mode for use in running under | |
3383 | the PSIM simulator. | |
3384 | ||
3385 | @html | |
b8db17af | 3386 | <hr /> |
b8df899a JM |
3387 | @end html |
3388 | @heading @anchor{powerpcle-*-eabi}powerpcle-*-eabi | |
3389 | Embedded PowerPC system in little endian mode. | |
3390 | ||
91abf72d | 3391 | @html |
b8db17af | 3392 | <hr /> |
91abf72d HP |
3393 | @end html |
3394 | @heading @anchor{s390-*-linux*}s390-*-linux* | |
95fef11f | 3395 | S/390 system running GNU/Linux for S/390@. |
91abf72d HP |
3396 | |
3397 | @html | |
b8db17af | 3398 | <hr /> |
91abf72d HP |
3399 | @end html |
3400 | @heading @anchor{s390x-*-linux*}s390x-*-linux* | |
95fef11f | 3401 | zSeries system (64-bit) running GNU/Linux for zSeries@. |
91abf72d | 3402 | |
8bf06993 UW |
3403 | @html |
3404 | <hr /> | |
3405 | @end html | |
3406 | @heading @anchor{s390x-ibm-tpf*}s390x-ibm-tpf* | |
daf2f129 | 3407 | zSeries system (64-bit) running TPF. This platform is |
8bf06993 UW |
3408 | supported as cross-compilation target only. |
3409 | ||
f42974dc | 3410 | @html |
b8db17af | 3411 | <hr /> |
f42974dc | 3412 | @end html |
250d5688 | 3413 | @c Please use Solaris 2 to refer to all release of Solaris, starting |
1460af95 | 3414 | @c with 2.0 until 2.6, 7, 8, etc. Solaris 1 was a marketing name for |
250d5688 RO |
3415 | @c SunOS 4 releases which we don't use to avoid confusion. Solaris |
3416 | @c alone is too unspecific and must be avoided. | |
3417 | @heading @anchor{*-*-solaris2*}*-*-solaris2* | |
f42974dc | 3418 | |
250d5688 | 3419 | Sun does not ship a C compiler with Solaris 2. To bootstrap and install |
962e6e00 | 3420 | GCC you first have to install a pre-built compiler, see the |
dbd210ef | 3421 | @uref{binaries.html,,binaries page} for details. |
f42974dc | 3422 | |
250d5688 | 3423 | The Solaris 2 @command{/bin/sh} will often fail to configure |
92441f83 | 3424 | @file{libstdc++-v3}, @file{boehm-gc} or @file{libjava}. We therefore |
bc890961 EB |
3425 | recommend to use the following sequence of commands to bootstrap and |
3426 | install GCC: | |
3427 | ||
3428 | @smallexample | |
3429 | % CONFIG_SHELL=/bin/ksh | |
3430 | % export CONFIG_SHELL | |
bc890961 EB |
3431 | @end smallexample |
3432 | ||
37de1373 GP |
3433 | and then proceed as described in @uref{build.html,,the build instructions}. |
3434 | In addition we strongly recommend specifying an absolute path to invoke | |
3435 | @var{srcdir}/configure. | |
e6855a2d | 3436 | |
b8df899a | 3437 | Solaris 2 comes with a number of optional OS packages. Some of these |
92441f83 | 3438 | are needed to use GCC fully, namely @code{SUNWarc}, |
dbd210ef KC |
3439 | @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm}, |
3440 | @code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all | |
250d5688 | 3441 | optional packages when installing Solaris 2, you will need to verify that |
b8df899a JM |
3442 | the packages that GCC needs are installed. |
3443 | ||
3444 | To check whether an optional package is installed, use | |
dbd210ef | 3445 | the @command{pkginfo} command. To add an optional package, use the |
250d5688 | 3446 | @command{pkgadd} command. For further details, see the Solaris 2 |
b8df899a JM |
3447 | documentation. |
3448 | ||
250d5688 | 3449 | Trying to use the linker and other tools in |
b8df899a JM |
3450 | @file{/usr/ucb} to install GCC has been observed to cause trouble. |
3451 | For example, the linker may hang indefinitely. The fix is to remove | |
250d5688 | 3452 | @file{/usr/ucb} from your @env{PATH}. |
f42974dc | 3453 | |
bc890961 EB |
3454 | The build process works more smoothly with the legacy Sun tools so, if you |
3455 | have @file{/usr/xpg4/bin} in your @env{PATH}, we recommend that you place | |
3456 | @file{/usr/bin} before @file{/usr/xpg4/bin} for the duration of the build. | |
3457 | ||
021c4bfd RO |
3458 | All releases of GNU binutils prior to 2.11.2 have known bugs on this |
3459 | platform. We recommend the use of GNU binutils 2.11.2 or the vendor | |
3460 | tools (Sun @command{as}, Sun @command{ld}). | |
f42974dc | 3461 | |
250d5688 RO |
3462 | Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or |
3463 | newer: @command{g++} will complain that types are missing. These headers assume | |
3464 | that omitting the type means @code{int}; this assumption worked for C89 but | |
3465 | is wrong for C++, and is now wrong for C99 also. | |
3466 | ||
13ba36b4 | 3467 | @command{g++} accepts such (invalid) constructs with the option |
250d5688 RO |
3468 | @option{-fpermissive}; it |
3469 | will assume that any missing type is @code{int} (as defined by C89). | |
3470 | ||
3471 | There are patches for Solaris 2.6 (105633-56 or newer for SPARC, | |
3472 | 106248-42 or newer for Intel), Solaris 7 (108376-21 or newer for SPARC, | |
3473 | 108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC, | |
3474 | 108653-22 for Intel) that fix this bug. | |
f42974dc | 3475 | |
dbd210ef | 3476 | @html |
b8db17af | 3477 | <hr /> |
dbd210ef | 3478 | @end html |
250d5688 | 3479 | @heading @anchor{sparc-sun-solaris2*}sparc-sun-solaris2* |
dbd210ef | 3480 | |
1405141b DN |
3481 | When GCC is configured to use binutils 2.11.2 or later the binaries |
3482 | produced are smaller than the ones produced using Sun's native tools; | |
3483 | this difference is quite significant for binaries containing debugging | |
3484 | information. | |
3485 | ||
250d5688 | 3486 | Sun @command{as} 4.x is broken in that it cannot cope with long symbol names. |
dbd210ef KC |
3487 | A typical error message might look similar to the following: |
3488 | ||
8c085f6f JJ |
3489 | @smallexample |
3490 | /usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041: error: | |
3491 | can't compute value of an expression involving an external symbol. | |
3492 | @end smallexample | |
dbd210ef | 3493 | |
250d5688 RO |
3494 | This is Sun bug 4237974. This is fixed with patch 108908-02 for Solaris |
3495 | 2.6 and has been fixed in later (5.x) versions of the assembler, | |
3496 | starting with Solaris 7. | |
dbd210ef | 3497 | |
03b272d2 | 3498 | Starting with Solaris 7, the operating system is capable of executing |
975c6e4e RO |
3499 | 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports |
3500 | this; the @option{-m64} option enables 64-bit code generation. | |
3501 | However, if all you want is code tuned for the UltraSPARC CPU, you | |
3502 | should try the @option{-mtune=ultrasparc} option instead, which produces | |
3503 | code that, unlike full 64-bit code, can still run on non-UltraSPARC | |
edf1c8df | 3504 | machines. |
03b272d2 | 3505 | |
975c6e4e | 3506 | When configuring on a Solaris 7 or later system that is running a kernel |
8947df0c RH |
3507 | that supports only 32-bit binaries, one must configure with |
3508 | @option{--disable-multilib}, since we will not be able to build the | |
3509 | 64-bit target libraries. | |
3fc602a0 | 3510 | |
ae81c844 EB |
3511 | GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of |
3512 | the GNU compiler (especially GCC 3.0.x versions), which lead to the | |
3513 | miscompilation of the stage1 compiler and the subsequent failure of the | |
3514 | bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary | |
3515 | stage, i.e. to bootstrap that compiler with the base compiler and then | |
3516 | use it to bootstrap the final compiler. | |
3517 | ||
94b18ec1 EB |
3518 | GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE Studio 7) |
3519 | and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a bootstrap | |
3520 | failure in form of a miscompilation of the stage1 compiler by the Sun | |
3521 | compiler. This is Sun bug 4974440. This is fixed with patch 112760-07. | |
3522 | ||
1460af95 PE |
3523 | GCC 3.4 changed the default debugging format from STABS to DWARF-2 for |
3524 | 32-bit code on Solaris 7 and later. If you are using the Sun | |
3525 | assembler, this change apparently runs afoul of Sun bug 4910101, for | |
3526 | which (as of 2004-05-23) there is no fix. A symptom of the problem is | |
3527 | that you cannot compile C++ programs like @command{groff} 1.19.1 | |
3528 | without getting messages like @samp{ld: warning: relocation error: | |
3529 | R_SPARC_UA32 @dots{} external symbolic relocation against | |
3530 | non-allocatable section .debug_info; cannot be processed at runtime: | |
3531 | relocation ignored}. To work around this problem, compile with | |
3532 | @option{-gstabs+} instead of plain @option{-g}. | |
3533 | ||
f42974dc | 3534 | @html |
b8db17af | 3535 | <hr /> |
f42974dc | 3536 | @end html |
ef88b07d | 3537 | @heading @anchor{sparc-sun-solaris2.7}sparc-sun-solaris2.7 |
f42974dc | 3538 | |
250d5688 | 3539 | Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in |
f42974dc DW |
3540 | the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8 |
3541 | and later, including all EGCS releases. Sun formerly recommended | |
3542 | 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to | |
3543 | recommend it only for people who use Sun's compilers. | |
f9047ed3 | 3544 | |
f42974dc DW |
3545 | Here are some workarounds to this problem: |
3546 | @itemize @bullet | |
3547 | @item | |
3548 | Do not install Sun patch 107058-01 until after Sun releases a | |
3549 | complete patch for bug 4210064. This is the simplest course to take, | |
3550 | unless you must also use Sun's C compiler. Unfortunately 107058-01 | |
250d5688 | 3551 | is preinstalled on some new Solaris 7-based hosts, so you may have to |
f42974dc | 3552 | back it out. |
f9047ed3 | 3553 | |
f42974dc DW |
3554 | @item |
3555 | Copy the original, unpatched Solaris 7 | |
3556 | @command{/usr/ccs/bin/as} into | |
8e5f33ff | 3557 | @command{/usr/local/libexec/gcc/sparc-sun-solaris2.7/3.4/as}, |
f42974dc DW |
3558 | adjusting the latter name to fit your local conventions and software |
3559 | version numbers. | |
3560 | ||
3561 | @item | |
3562 | Install Sun patch 106950-03 (1999-05-25) or later. Nobody with | |
3563 | both 107058-01 and 106950-03 installed has reported the bug with GCC | |
3564 | and Sun's dynamic linker. This last course of action is riskiest, | |
3565 | for two reasons. First, you must install 106950 on all hosts that | |
3566 | run code generated by GCC; it doesn't suffice to install it only on | |
3567 | the hosts that run GCC itself. Second, Sun says that 106950-03 is | |
3568 | only a partial fix for bug 4210064, but Sun doesn't know whether the | |
161d7b59 | 3569 | partial fix is adequate for GCC@. Revision -08 or later should fix |
1460af95 | 3570 | the bug. The current (as of 2004-05-23) revision is -24, and is included in |
f282ffb3 | 3571 | the Solaris 7 Recommended Patch Cluster. |
f9047ed3 | 3572 | @end itemize |
f42974dc | 3573 | |
fdbf04c8 EB |
3574 | GCC 3.3 triggers a bug in version 5.0 Alpha 03/27/98 of the Sun assembler, |
3575 | which causes a bootstrap failure when linking the 64-bit shared version of | |
3576 | libgcc. A typical error message is: | |
3577 | ||
3578 | @smallexample | |
3579 | ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o: | |
3580 | symbol <unknown>: offset 0xffffffff7ec133e7 is non-aligned. | |
3581 | @end smallexample | |
3582 | ||
3583 | This bug has been fixed in the final 5.0 version of the assembler. | |
f42974dc | 3584 | |
c6fa9728 | 3585 | @html |
b8db17af | 3586 | <hr /> |
c6fa9728 JS |
3587 | @end html |
3588 | @heading @anchor{sparc-*-linux*}sparc-*-linux* | |
3589 | ||
3590 | GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4 | |
3591 | or newer on this platform. All earlier binutils and glibc | |
3592 | releases mishandled unaligned relocations on @code{sparc-*-*} targets. | |
3593 | ||
3594 | ||
f42974dc | 3595 | @html |
b8db17af | 3596 | <hr /> |
f42974dc | 3597 | @end html |
0dc7ee3c | 3598 | @heading @anchor{sparc64-*-solaris2*}sparc64-*-solaris2* |
e403b4bc CR |
3599 | |
3600 | The following compiler flags must be specified in the configure | |
3601 | step in order to bootstrap this target with the Sun compiler: | |
3602 | ||
3ab51846 | 3603 | @smallexample |
e403b4bc | 3604 | % CC="cc -xildoff -xarch=v9" @var{srcdir}/configure [@var{options}] [@var{target}] |
3ab51846 | 3605 | @end smallexample |
e403b4bc CR |
3606 | |
3607 | @option{-xildoff} turns off the incremental linker, and @option{-xarch=v9} | |
0dc7ee3c EB |
3608 | specifies the SPARC-V9 architecture to the Sun linker and assembler. |
3609 | ||
3610 | @html | |
3611 | <hr /> | |
3612 | @end html | |
3613 | @heading @anchor{sparcv9-*-solaris2*}sparcv9-*-solaris2* | |
3614 | ||
3615 | This is a synonym for sparc64-*-solaris2*. | |
f42974dc | 3616 | |
b8df899a | 3617 | @html |
b8db17af | 3618 | <hr /> |
b8df899a JM |
3619 | @end html |
3620 | @heading @anchor{#*-*-sysv*}*-*-sysv* | |
3621 | On System V release 3, you may get this error message | |
3622 | while linking: | |
3623 | ||
3624 | @smallexample | |
3625 | ld fatal: failed to write symbol name @var{something} | |
3626 | in strings table for file @var{whatever} | |
3627 | @end smallexample | |
3628 | ||
021c4bfd | 3629 | This probably indicates that the disk is full or your ulimit won't allow |
b8df899a JM |
3630 | the file to be as large as it needs to be. |
3631 | ||
3632 | This problem can also result because the kernel parameter @code{MAXUMEM} | |
3633 | is too small. If so, you must regenerate the kernel and make the value | |
3634 | much larger. The default value is reported to be 1024; a value of 32768 | |
3635 | is said to work. Smaller values may also work. | |
3636 | ||
3637 | On System V, if you get an error like this, | |
3638 | ||
3ab51846 | 3639 | @smallexample |
b8df899a JM |
3640 | /usr/local/lib/bison.simple: In function `yyparse': |
3641 | /usr/local/lib/bison.simple:625: virtual memory exhausted | |
3ab51846 | 3642 | @end smallexample |
b8df899a JM |
3643 | |
3644 | @noindent | |
021c4bfd | 3645 | that too indicates a problem with disk space, ulimit, or @code{MAXUMEM}. |
b8df899a | 3646 | |
f85b8d1a | 3647 | On a System V release 4 system, make sure @file{/usr/bin} precedes |
7ba4ca63 | 3648 | @file{/usr/ucb} in @code{PATH}. The @command{cc} command in |
f85b8d1a | 3649 | @file{/usr/ucb} uses libraries which have bugs. |
b8df899a JM |
3650 | |
3651 | @html | |
b8db17af | 3652 | <hr /> |
b8df899a JM |
3653 | @end html |
3654 | @heading @anchor{vax-dec-ultrix}vax-dec-ultrix | |
7ba4ca63 | 3655 | Don't try compiling with VAX C (@command{vcc}). It produces incorrect code |
b8df899a JM |
3656 | in some cases (for example, when @code{alloca} is used). |
3657 | ||
4977bab6 ZW |
3658 | @html |
3659 | <hr /> | |
3660 | @end html | |
3661 | @heading @anchor{*-*-vxworks*}*-*-vxworks* | |
3662 | Support for VxWorks is in flux. At present GCC supports @emph{only} the | |
3663 | very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC. | |
3664 | We welcome patches for other architectures supported by VxWorks 5.5. | |
3665 | Support for VxWorks AE would also be welcome; we believe this is merely | |
3666 | a matter of writing an appropriate ``configlette'' (see below). We are | |
3667 | not interested in supporting older, a.out or COFF-based, versions of | |
3668 | VxWorks in GCC 3. | |
3669 | ||
3670 | VxWorks comes with an older version of GCC installed in | |
3671 | @file{@var{$WIND_BASE}/host}; we recommend you do not overwrite it. | |
3672 | Choose an installation @var{prefix} entirely outside @var{$WIND_BASE}. | |
3673 | Before running @command{configure}, create the directories @file{@var{prefix}} | |
3674 | and @file{@var{prefix}/bin}. Link or copy the appropriate assembler, | |
3675 | linker, etc. into @file{@var{prefix}/bin}, and set your @var{PATH} to | |
3676 | include that directory while running both @command{configure} and | |
3677 | @command{make}. | |
3678 | ||
3679 | You must give @command{configure} the | |
3680 | @option{--with-headers=@var{$WIND_BASE}/target/h} switch so that it can | |
3681 | find the VxWorks system headers. Since VxWorks is a cross compilation | |
3682 | target only, you must also specify @option{--target=@var{target}}. | |
3683 | @command{configure} will attempt to create the directory | |
3684 | @file{@var{prefix}/@var{target}/sys-include} and copy files into it; | |
3685 | make sure the user running @command{configure} has sufficient privilege | |
3686 | to do so. | |
3687 | ||
3688 | GCC's exception handling runtime requires a special ``configlette'' | |
3689 | module, @file{contrib/gthr_supp_vxw_5x.c}. Follow the instructions in | |
3690 | that file to add the module to your kernel build. (Future versions of | |
daf2f129 | 3691 | VxWorks will incorporate this module.) |
4977bab6 | 3692 | |
7e081a0c AJ |
3693 | @html |
3694 | <hr /> | |
3695 | @end html | |
3696 | @heading @anchor{x86_64-*-*}x86_64-*-*, amd64-*-* | |
3697 | ||
3698 | GCC supports the x86-64 architecture implemented by the AMD64 processor | |
3699 | (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD. | |
3700 | On GNU/Linux the default is a bi-arch compiler which is able to generate | |
3701 | both 64-bit x86-64 and 32-bit x86 code (via the @option{-m32} switch). | |
3702 | ||
fd29f6ea | 3703 | @html |
b8db17af | 3704 | <hr /> |
fd29f6ea BW |
3705 | @end html |
3706 | @heading @anchor{xtensa-*-elf}xtensa-*-elf | |
3707 | ||
3708 | This target is intended for embedded Xtensa systems using the | |
3709 | @samp{newlib} C library. It uses ELF but does not support shared | |
3710 | objects. Designed-defined instructions specified via the | |
3711 | Tensilica Instruction Extension (TIE) language are only supported | |
3712 | through inline assembly. | |
3713 | ||
3714 | The Xtensa configuration information must be specified prior to | |
e677f70c | 3715 | building GCC@. The @file{include/xtensa-config.h} header |
fd29f6ea BW |
3716 | file contains the configuration information. If you created your |
3717 | own Xtensa configuration with the Xtensa Processor Generator, the | |
3718 | downloaded files include a customized copy of this header file, | |
3719 | which you can use to replace the default header file. | |
3720 | ||
3721 | @html | |
b8db17af | 3722 | <hr /> |
fd29f6ea BW |
3723 | @end html |
3724 | @heading @anchor{xtensa-*-linux*}xtensa-*-linux* | |
3725 | ||
3726 | This target is for Xtensa systems running GNU/Linux. It supports ELF | |
3727 | shared objects and the GNU C library (glibc). It also generates | |
3728 | position-independent code (PIC) regardless of whether the | |
3729 | @option{-fpic} or @option{-fPIC} options are used. In other | |
f282ffb3 | 3730 | respects, this target is the same as the |
fd29f6ea BW |
3731 | @uref{#xtensa-*-elf,,@samp{xtensa-*-elf}} target. |
3732 | ||
f42974dc | 3733 | @html |
b8db17af | 3734 | <hr /> |
f42974dc | 3735 | @end html |
57694e40 | 3736 | @heading @anchor{windows}Microsoft Windows (32-bit) |
f42974dc | 3737 | |
ccc1ce6e | 3738 | A port of GCC 2.95.2 and 3.x is included with the |
f42974dc DW |
3739 | @uref{http://www.cygwin.com/,,Cygwin environment}. |
3740 | ||
3741 | Current (as of early 2001) snapshots of GCC will build under Cygwin | |
3742 | without modification. | |
3743 | ||
ccc1ce6e CF |
3744 | GCC does not currently build with Microsoft's C++ compiler and there |
3745 | are no plans to make it do so. | |
3746 | ||
f42974dc | 3747 | @html |
b8db17af | 3748 | <hr /> |
f42974dc | 3749 | @end html |
ef88b07d | 3750 | @heading @anchor{os2}OS/2 |
f42974dc DW |
3751 | |
3752 | GCC does not currently support OS/2. However, Andrew Zabolotny has been | |
14976c58 | 3753 | working on a generic OS/2 port with pgcc. The current code can be found |
f42974dc DW |
3754 | at @uref{http://www.goof.com/pcg/os2/,,http://www.goof.com/pcg/os2/}. |
3755 | ||
f9047ed3 | 3756 | An older copy of GCC 2.8.1 is included with the EMX tools available at |
f42974dc DW |
3757 | @uref{ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/,, |
3758 | ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/}. | |
3759 | ||
3760 | @html | |
b8db17af | 3761 | <hr /> |
f42974dc | 3762 | @end html |
ef88b07d | 3763 | @heading @anchor{older}Older systems |
f9047ed3 JM |
3764 | |
3765 | GCC contains support files for many older (1980s and early | |
3766 | 1990s) Unix variants. For the most part, support for these systems | |
3767 | has not been deliberately removed, but it has not been maintained for | |
c7bdf0a6 | 3768 | several years and may suffer from bitrot. |
f9047ed3 | 3769 | |
c7bdf0a6 | 3770 | Starting with GCC 3.1, each release has a list of ``obsoleted'' systems. |
9340544b ZW |
3771 | Support for these systems is still present in that release, but |
3772 | @command{configure} will fail unless the @option{--enable-obsolete} | |
c7bdf0a6 ZW |
3773 | option is given. Unless a maintainer steps forward, support for these |
3774 | systems will be removed from the next release of GCC@. | |
f9047ed3 JM |
3775 | |
3776 | Support for old systems as hosts for GCC can cause problems if the | |
3777 | workarounds for compiler, library and operating system bugs affect the | |
161d7b59 | 3778 | cleanliness or maintainability of the rest of GCC@. In some cases, to |
f9047ed3 JM |
3779 | bring GCC up on such a system, if still possible with current GCC, may |
3780 | require first installing an old version of GCC which did work on that | |
c7bdf0a6 ZW |
3781 | system, and using it to compile a more recent GCC, to avoid bugs in the |
3782 | vendor compiler. Old releases of GCC 1 and GCC 2 are available in the | |
3783 | @file{old-releases} directory on the @uref{../mirrors.html,,GCC mirror | |
3784 | sites}. Header bugs may generally be avoided using | |
3785 | @command{fixincludes}, but bugs or deficiencies in libraries and the | |
3786 | operating system may still cause problems. | |
3787 | ||
3788 | Support for older systems as targets for cross-compilation is less | |
3789 | problematic than support for them as hosts for GCC; if an enthusiast | |
3790 | wishes to make such a target work again (including resurrecting any of | |
3791 | the targets that never worked with GCC 2, starting from the last CVS | |
3792 | version before they were removed), patches | |
3793 | @uref{../contribute.html,,following the usual requirements} would be | |
3794 | likely to be accepted, since they should not affect the support for more | |
3795 | modern targets. | |
f9047ed3 JM |
3796 | |
3797 | For some systems, old versions of GNU binutils may also be useful, | |
021c4bfd | 3798 | and are available from @file{pub/binutils/old-releases} on |
f42974dc | 3799 | @uref{http://sources.redhat.com/mirrors.html,,sources.redhat.com mirror sites}. |
f9047ed3 JM |
3800 | |
3801 | Some of the information on specific systems above relates to | |
3802 | such older systems, but much of the information | |
3803 | about GCC on such systems (which may no longer be applicable to | |
f42974dc | 3804 | current GCC) is to be found in the GCC texinfo manual. |
f9047ed3 | 3805 | |
f42974dc | 3806 | @html |
b8db17af | 3807 | <hr /> |
f42974dc | 3808 | @end html |
250d5688 | 3809 | @heading @anchor{elf_targets}all ELF targets (SVR4, Solaris 2, etc.) |
f42974dc | 3810 | |
38209993 LG |
3811 | C++ support is significantly better on ELF targets if you use the |
3812 | @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of | |
3813 | inlines, vtables and template instantiations will be discarded | |
3814 | automatically. | |
f42974dc DW |
3815 | |
3816 | ||
3817 | @html | |
b8db17af | 3818 | <hr /> |
f42974dc DW |
3819 | <p> |
3820 | @end html | |
3821 | @ifhtml | |
3822 | @uref{./index.html,,Return to the GCC Installation page} | |
3823 | @end ifhtml | |
3824 | @end ifset | |
3825 | ||
73e2155a JM |
3826 | @c ***Old documentation****************************************************** |
3827 | @ifset oldhtml | |
3828 | @include install-old.texi | |
3829 | @html | |
b8db17af | 3830 | <hr /> |
73e2155a JM |
3831 | <p> |
3832 | @end html | |
3833 | @ifhtml | |
3834 | @uref{./index.html,,Return to the GCC Installation page} | |
3835 | @end ifhtml | |
3836 | @end ifset | |
3837 | ||
aed5964b JM |
3838 | @c ***GFDL******************************************************************** |
3839 | @ifset gfdlhtml | |
3840 | @include fdl.texi | |
3841 | @html | |
b8db17af | 3842 | <hr /> |
aed5964b JM |
3843 | <p> |
3844 | @end html | |
3845 | @ifhtml | |
3846 | @uref{./index.html,,Return to the GCC Installation page} | |
3847 | @end ifhtml | |
3848 | @end ifset | |
3849 | ||
f42974dc DW |
3850 | @c *************************************************************************** |
3851 | @c Part 6 The End of the Document | |
3852 | @ifinfo | |
3853 | @comment node-name, next, previous, up | |
aed5964b | 3854 | @node Concept Index, , GNU Free Documentation License, Top |
f42974dc DW |
3855 | @end ifinfo |
3856 | ||
3857 | @ifinfo | |
3858 | @unnumbered Concept Index | |
3859 | ||
3860 | @printindex cp | |
3861 | ||
3862 | @contents | |
3863 | @end ifinfo | |
3864 | @bye |