]>
Commit | Line | Data |
---|---|---|
1 | \input texinfo.tex @c -*-texinfo-*- | |
2 | @c @ifnothtml | |
3 | @c %**start of header | |
4 | @setfilename gccinstall.info | |
5 | @settitle Installing GCC | |
6 | @setchapternewpage odd | |
7 | @c %**end of header | |
8 | @c @end ifnothtml | |
9 | ||
10 | @include gcc-common.texi | |
11 | ||
12 | @c Specify title for specific html page | |
13 | @ifset indexhtml | |
14 | @settitle Installing GCC | |
15 | @end ifset | |
16 | @ifset specifichtml | |
17 | @settitle Host/Target specific installation notes for GCC | |
18 | @end ifset | |
19 | @ifset prerequisiteshtml | |
20 | @settitle Prerequisites for GCC | |
21 | @end ifset | |
22 | @ifset downloadhtml | |
23 | @settitle Downloading GCC | |
24 | @end ifset | |
25 | @ifset configurehtml | |
26 | @settitle Installing GCC: Configuration | |
27 | @end ifset | |
28 | @ifset buildhtml | |
29 | @settitle Installing GCC: Building | |
30 | @end ifset | |
31 | @ifset testhtml | |
32 | @settitle Installing GCC: Testing | |
33 | @end ifset | |
34 | @ifset finalinstallhtml | |
35 | @settitle Installing GCC: Final installation | |
36 | @end ifset | |
37 | @ifset binarieshtml | |
38 | @settitle Installing GCC: Binaries | |
39 | @end ifset | |
40 | @ifset oldhtml | |
41 | @settitle Installing GCC: Old documentation | |
42 | @end ifset | |
43 | @ifset gfdlhtml | |
44 | @settitle Installing GCC: GNU Free Documentation License | |
45 | @end ifset | |
46 | ||
47 | @c Copyright (C) 1988-2014 Free Software Foundation, Inc. | |
48 | @c *** Converted to texinfo by Dean Wakerley, dean@wakerley.com | |
49 | ||
50 | @c IMPORTANT: whenever you modify this file, run `install.texi2html' to | |
51 | @c test the generation of HTML documents for the gcc.gnu.org web pages. | |
52 | @c | |
53 | @c Do not use @footnote{} in this file as it breaks install.texi2html! | |
54 | ||
55 | @c Include everything if we're not making html | |
56 | @ifnothtml | |
57 | @set indexhtml | |
58 | @set specifichtml | |
59 | @set prerequisiteshtml | |
60 | @set downloadhtml | |
61 | @set configurehtml | |
62 | @set buildhtml | |
63 | @set testhtml | |
64 | @set finalinstallhtml | |
65 | @set binarieshtml | |
66 | @set oldhtml | |
67 | @set gfdlhtml | |
68 | @end ifnothtml | |
69 | ||
70 | @c Part 2 Summary Description and Copyright | |
71 | @copying | |
72 | Copyright @copyright{} 1988-2014 Free Software Foundation, Inc. | |
73 | @sp 1 | |
74 | Permission is granted to copy, distribute and/or modify this document | |
75 | under the terms of the GNU Free Documentation License, Version 1.3 or | |
76 | any later version published by the Free Software Foundation; with no | |
77 | Invariant Sections, the Front-Cover texts being (a) (see below), and | |
78 | with the Back-Cover Texts being (b) (see below). A copy of the | |
79 | license is included in the section entitled ``@uref{./gfdl.html,,GNU | |
80 | Free Documentation License}''. | |
81 | ||
82 | (a) The FSF's Front-Cover Text is: | |
83 | ||
84 | A GNU Manual | |
85 | ||
86 | (b) The FSF's Back-Cover Text is: | |
87 | ||
88 | You have freedom to copy and modify this GNU Manual, like GNU | |
89 | software. Copies published by the Free Software Foundation raise | |
90 | funds for GNU development. | |
91 | @end copying | |
92 | @ifinfo | |
93 | @insertcopying | |
94 | @end ifinfo | |
95 | @dircategory Software development | |
96 | @direntry | |
97 | * gccinstall: (gccinstall). Installing the GNU Compiler Collection. | |
98 | @end direntry | |
99 | ||
100 | @c Part 3 Titlepage and Copyright | |
101 | @titlepage | |
102 | @title Installing GCC | |
103 | @versionsubtitle | |
104 | ||
105 | @c The following two commands start the copyright page. | |
106 | @page | |
107 | @vskip 0pt plus 1filll | |
108 | @insertcopying | |
109 | @end titlepage | |
110 | ||
111 | @c Part 4 Top node, Master Menu, and/or Table of Contents | |
112 | @ifinfo | |
113 | @node Top, , , (dir) | |
114 | @comment node-name, next, Previous, up | |
115 | ||
116 | @menu | |
117 | * Installing GCC:: This document describes the generic installation | |
118 | procedure for GCC as well as detailing some target | |
119 | specific installation instructions. | |
120 | ||
121 | * Specific:: Host/target specific installation notes for GCC. | |
122 | * Binaries:: Where to get pre-compiled binaries. | |
123 | ||
124 | * Old:: Old installation documentation. | |
125 | ||
126 | * GNU Free Documentation License:: How you can copy and share this manual. | |
127 | * Concept Index:: This index has two entries. | |
128 | @end menu | |
129 | @end ifinfo | |
130 | ||
131 | @iftex | |
132 | @contents | |
133 | @end iftex | |
134 | ||
135 | @c Part 5 The Body of the Document | |
136 | @c ***Installing GCC********************************************************** | |
137 | @ifnothtml | |
138 | @comment node-name, next, previous, up | |
139 | @node Installing GCC, Binaries, , Top | |
140 | @end ifnothtml | |
141 | @ifset indexhtml | |
142 | @ifnothtml | |
143 | @chapter Installing GCC | |
144 | @end ifnothtml | |
145 | ||
146 | The latest version of this document is always available at | |
147 | @uref{http://gcc.gnu.org/install/,,http://gcc.gnu.org/install/}. | |
148 | It refers to the current development sources, instructions for | |
149 | specific released versions are included with the sources. | |
150 | ||
151 | This document describes the generic installation procedure for GCC as well | |
152 | as detailing some target specific installation instructions. | |
153 | ||
154 | GCC includes several components that previously were separate distributions | |
155 | with their own installation instructions. This document supersedes all | |
156 | package-specific installation instructions. | |
157 | ||
158 | @emph{Before} starting the build/install procedure please check the | |
159 | @ifnothtml | |
160 | @ref{Specific, host/target specific installation notes}. | |
161 | @end ifnothtml | |
162 | @ifhtml | |
163 | @uref{specific.html,,host/target specific installation notes}. | |
164 | @end ifhtml | |
165 | We recommend you browse the entire generic installation instructions before | |
166 | you proceed. | |
167 | ||
168 | Lists of successful builds for released versions of GCC are | |
169 | available at @uref{http://gcc.gnu.org/buildstat.html}. | |
170 | These lists are updated as new information becomes available. | |
171 | ||
172 | The installation procedure itself is broken into five steps. | |
173 | ||
174 | @ifinfo | |
175 | @menu | |
176 | * Prerequisites:: | |
177 | * Downloading the source:: | |
178 | * Configuration:: | |
179 | * Building:: | |
180 | * Testing:: (optional) | |
181 | * Final install:: | |
182 | @end menu | |
183 | @end ifinfo | |
184 | @ifhtml | |
185 | @enumerate | |
186 | @item | |
187 | @uref{prerequisites.html,,Prerequisites} | |
188 | @item | |
189 | @uref{download.html,,Downloading the source} | |
190 | @item | |
191 | @uref{configure.html,,Configuration} | |
192 | @item | |
193 | @uref{build.html,,Building} | |
194 | @item | |
195 | @uref{test.html,,Testing} (optional) | |
196 | @item | |
197 | @uref{finalinstall.html,,Final install} | |
198 | @end enumerate | |
199 | @end ifhtml | |
200 | ||
201 | Please note that GCC does not support @samp{make uninstall} and probably | |
202 | won't do so in the near future as this would open a can of worms. Instead, | |
203 | we suggest that you install GCC into a directory of its own and simply | |
204 | remove that directory when you do not need that specific version of GCC | |
205 | any longer, and, if shared libraries are installed there as well, no | |
206 | more binaries exist that use them. | |
207 | ||
208 | @ifhtml | |
209 | There are also some @uref{old.html,,old installation instructions}, | |
210 | which are mostly obsolete but still contain some information which has | |
211 | not yet been merged into the main part of this manual. | |
212 | @end ifhtml | |
213 | ||
214 | @html | |
215 | <hr /> | |
216 | <p> | |
217 | @end html | |
218 | @ifhtml | |
219 | @uref{./index.html,,Return to the GCC Installation page} | |
220 | ||
221 | @insertcopying | |
222 | @end ifhtml | |
223 | @end ifset | |
224 | ||
225 | @c ***Prerequisites************************************************** | |
226 | @ifnothtml | |
227 | @comment node-name, next, previous, up | |
228 | @node Prerequisites, Downloading the source, , Installing GCC | |
229 | @end ifnothtml | |
230 | @ifset prerequisiteshtml | |
231 | @ifnothtml | |
232 | @chapter Prerequisites | |
233 | @end ifnothtml | |
234 | @cindex Prerequisites | |
235 | ||
236 | GCC requires that various tools and packages be available for use in the | |
237 | build procedure. Modifying GCC sources requires additional tools | |
238 | described below. | |
239 | ||
240 | @heading Tools/packages necessary for building GCC | |
241 | @table @asis | |
242 | @item ISO C++98 compiler | |
243 | Necessary to bootstrap GCC, although versions of GCC prior | |
244 | to 4.8 also allow bootstrapping with a ISO C89 compiler and versions | |
245 | of GCC prior to 3.4 also allow bootstrapping with a traditional | |
246 | (K&R) C compiler. | |
247 | ||
248 | To build all languages in a cross-compiler or other configuration where | |
249 | 3-stage bootstrap is not performed, you need to start with an existing | |
250 | GCC binary (version 3.4 or later) because source code for language | |
251 | frontends other than C might use GCC extensions. | |
252 | ||
253 | Note that to bootstrap GCC with versions of GCC earlier than 3.4, you | |
254 | may need to use @option{--disable-stage1-checking}, though | |
255 | bootstrapping the compiler with such earlier compilers is strongly | |
256 | discouraged. | |
257 | ||
258 | @item C standard library and headers | |
259 | ||
260 | In order to build GCC, the C standard library and headers must be present | |
261 | for all target variants for which target libraries will be built (and not | |
262 | only the variant of the host C++ compiler). | |
263 | ||
264 | This affects the popular @samp{x86_64-unknown-linux-gnu} platform (among | |
265 | other multilib targets), for which 64-bit (@samp{x86_64}) and 32-bit | |
266 | (@samp{i386}) libc headers are usually packaged separately. If you do a | |
267 | build of a native compiler on @samp{x86_64-unknown-linux-gnu}, make sure you | |
268 | either have the 32-bit libc developer package properly installed (the exact | |
269 | name of the package depends on your distro) or you must build GCC as a | |
270 | 64-bit only compiler by configuring with the option | |
271 | @option{--disable-multilib}. Otherwise, you may encounter an error such as | |
272 | @samp{fatal error: gnu/stubs-32.h: No such file} | |
273 | ||
274 | @item GNAT | |
275 | ||
276 | In order to build the Ada compiler (GNAT) you must already have GNAT | |
277 | installed because portions of the Ada frontend are written in Ada (with | |
278 | GNAT extensions.) Refer to the Ada installation instructions for more | |
279 | specific information. | |
280 | ||
281 | @item A ``working'' POSIX compatible shell, or GNU bash | |
282 | ||
283 | Necessary when running @command{configure} because some | |
284 | @command{/bin/sh} shells have bugs and may crash when configuring the | |
285 | target libraries. In other cases, @command{/bin/sh} or @command{ksh} | |
286 | have disastrous corner-case performance problems. This | |
287 | can cause target @command{configure} runs to literally take days to | |
288 | complete in some cases. | |
289 | ||
290 | So on some platforms @command{/bin/ksh} is sufficient, on others it | |
291 | isn't. See the host/target specific instructions for your platform, or | |
292 | use @command{bash} to be sure. Then set @env{CONFIG_SHELL} in your | |
293 | environment to your ``good'' shell prior to running | |
294 | @command{configure}/@command{make}. | |
295 | ||
296 | @command{zsh} is not a fully compliant POSIX shell and will not | |
297 | work when configuring GCC@. | |
298 | ||
299 | @item A POSIX or SVR4 awk | |
300 | ||
301 | Necessary for creating some of the generated source files for GCC@. | |
302 | If in doubt, use a recent GNU awk version, as some of the older ones | |
303 | are broken. GNU awk version 3.1.5 is known to work. | |
304 | ||
305 | @item GNU binutils | |
306 | ||
307 | Necessary in some circumstances, optional in others. See the | |
308 | host/target specific instructions for your platform for the exact | |
309 | requirements. | |
310 | ||
311 | @item gzip version 1.2.4 (or later) or | |
312 | @itemx bzip2 version 1.0.2 (or later) | |
313 | ||
314 | Necessary to uncompress GCC @command{tar} files when source code is | |
315 | obtained via FTP mirror sites. | |
316 | ||
317 | @item GNU make version 3.80 (or later) | |
318 | ||
319 | You must have GNU make installed to build GCC@. | |
320 | ||
321 | @item GNU tar version 1.14 (or later) | |
322 | ||
323 | Necessary (only on some platforms) to untar the source code. Many | |
324 | systems' @command{tar} programs will also work, only try GNU | |
325 | @command{tar} if you have problems. | |
326 | ||
327 | @item Perl version 5.6.1 (or later) | |
328 | ||
329 | Necessary when targeting Darwin, building @samp{libstdc++}, | |
330 | and not using @option{--disable-symvers}. | |
331 | Necessary when targeting Solaris 2 with Sun @command{ld} and not using | |
332 | @option{--disable-symvers}. The bundled @command{perl} in Solaris@tie{}8 | |
333 | and up works. | |
334 | ||
335 | Necessary when regenerating @file{Makefile} dependencies in libiberty. | |
336 | Necessary when regenerating @file{libiberty/functions.texi}. | |
337 | Necessary when generating manpages from Texinfo manuals. | |
338 | Used by various scripts to generate some files included in SVN (mainly | |
339 | Unicode-related and rarely changing) from source tables. | |
340 | ||
341 | @item @command{jar}, or InfoZIP (@command{zip} and @command{unzip}) | |
342 | ||
343 | Necessary to build libgcj, the GCJ runtime. | |
344 | ||
345 | @end table | |
346 | ||
347 | Several support libraries are necessary to build GCC, some are required, | |
348 | others optional. While any sufficiently new version of required tools | |
349 | usually work, library requirements are generally stricter. Newer | |
350 | versions may work in some cases, but it's safer to use the exact | |
351 | versions documented. We appreciate bug reports about problems with | |
352 | newer versions, though. If your OS vendor provides packages for the | |
353 | support libraries then using those packages may be the simplest way to | |
354 | install the libraries. | |
355 | ||
356 | @table @asis | |
357 | @item GNU Multiple Precision Library (GMP) version 4.3.2 (or later) | |
358 | ||
359 | Necessary to build GCC@. If a GMP source distribution is found in a | |
360 | subdirectory of your GCC sources named @file{gmp}, it will be built | |
361 | together with GCC. Alternatively, if GMP is already installed but it | |
362 | is not in your library search path, you will have to configure with the | |
363 | @option{--with-gmp} configure option. See also @option{--with-gmp-lib} | |
364 | and @option{--with-gmp-include}. | |
365 | ||
366 | @item MPFR Library version 2.4.2 (or later) | |
367 | ||
368 | Necessary to build GCC@. It can be downloaded from | |
369 | @uref{http://www.mpfr.org/}. If an MPFR source distribution is found | |
370 | in a subdirectory of your GCC sources named @file{mpfr}, it will be | |
371 | built together with GCC. Alternatively, if MPFR is already installed | |
372 | but it is not in your default library search path, the | |
373 | @option{--with-mpfr} configure option should be used. See also | |
374 | @option{--with-mpfr-lib} and @option{--with-mpfr-include}. | |
375 | ||
376 | @item MPC Library version 0.8.1 (or later) | |
377 | ||
378 | Necessary to build GCC@. It can be downloaded from | |
379 | @uref{http://www.multiprecision.org/}. If an MPC source distribution | |
380 | is found in a subdirectory of your GCC sources named @file{mpc}, it | |
381 | will be built together with GCC. Alternatively, if MPC is already | |
382 | installed but it is not in your default library search path, the | |
383 | @option{--with-mpc} configure option should be used. See also | |
384 | @option{--with-mpc-lib} and @option{--with-mpc-include}. | |
385 | ||
386 | @item ISL Library version 0.12.2 | |
387 | ||
388 | Necessary to build GCC with the Graphite loop optimizations. | |
389 | It can be downloaded from @uref{ftp://gcc.gnu.org/pub/gcc/infrastructure/} | |
390 | as @file{isl-0.12.2.tar.bz2}. If an ISL source distribution is found | |
391 | in a subdirectory of your GCC sources named @file{isl}, it will be | |
392 | built together with GCC. Alternatively, the @option{--with-isl} configure | |
393 | option should be used if ISL is not installed in your default library | |
394 | search path. | |
395 | ||
396 | @item CLooG 0.18.1 | |
397 | ||
398 | Necessary to build GCC with the Graphite loop optimizations. It can be | |
399 | downloaded from @uref{ftp://gcc.gnu.org/pub/gcc/infrastructure/} as | |
400 | @file{cloog-0.18.1.tar.gz}. If a CLooG source distribution is found | |
401 | in a subdirectory of your GCC sources named @file{cloog}, it will be | |
402 | built together with GCC. Alternatively, the @option{--with-cloog} configure | |
403 | option should be used if CLooG is not installed in your default library search | |
404 | path. | |
405 | ||
406 | If you want to install CLooG separately it needs to be built against | |
407 | ISL 0.12.2 by using the @option{--with-isl=system} to direct CLooG to pick | |
408 | up an already installed ISL. Using the ISL library as bundled with CLooG | |
409 | is not supported. | |
410 | ||
411 | @end table | |
412 | ||
413 | @heading Tools/packages necessary for modifying GCC | |
414 | @table @asis | |
415 | @item autoconf version 2.64 | |
416 | @itemx GNU m4 version 1.4.6 (or later) | |
417 | ||
418 | Necessary when modifying @file{configure.ac}, @file{aclocal.m4}, etc.@: | |
419 | to regenerate @file{configure} and @file{config.in} files. | |
420 | ||
421 | @item automake version 1.11.1 | |
422 | ||
423 | Necessary when modifying a @file{Makefile.am} file to regenerate its | |
424 | associated @file{Makefile.in}. | |
425 | ||
426 | Much of GCC does not use automake, so directly edit the @file{Makefile.in} | |
427 | file. Specifically this applies to the @file{gcc}, @file{intl}, | |
428 | @file{libcpp}, @file{libiberty}, @file{libobjc} directories as well | |
429 | as any of their subdirectories. | |
430 | ||
431 | For directories that use automake, GCC requires the latest release in | |
432 | the 1.11 series, which is currently 1.11.1. When regenerating a directory | |
433 | to a newer version, please update all the directories using an older 1.11 | |
434 | to the latest released version. | |
435 | ||
436 | @item gettext version 0.14.5 (or later) | |
437 | ||
438 | Needed to regenerate @file{gcc.pot}. | |
439 | ||
440 | @item gperf version 2.7.2 (or later) | |
441 | ||
442 | Necessary when modifying @command{gperf} input files, e.g.@: | |
443 | @file{gcc/cp/cfns.gperf} to regenerate its associated header file, e.g.@: | |
444 | @file{gcc/cp/cfns.h}. | |
445 | ||
446 | @item DejaGnu 1.4.4 | |
447 | @itemx Expect | |
448 | @itemx Tcl | |
449 | ||
450 | Necessary to run the GCC testsuite; see the section on testing for | |
451 | details. Tcl 8.6 has a known regression in RE pattern handling that | |
452 | make parts of the testsuite fail. See | |
453 | @uref{http://core.tcl.tk/tcl/tktview/267b7e2334ee2e9de34c4b00d6e72e2f1997085f} | |
454 | for more information. | |
455 | ||
456 | @item autogen version 5.5.4 (or later) and | |
457 | @itemx guile version 1.4.1 (or later) | |
458 | ||
459 | Necessary to regenerate @file{fixinc/fixincl.x} from | |
460 | @file{fixinc/inclhack.def} and @file{fixinc/*.tpl}. | |
461 | ||
462 | Necessary to run @samp{make check} for @file{fixinc}. | |
463 | ||
464 | Necessary to regenerate the top level @file{Makefile.in} file from | |
465 | @file{Makefile.tpl} and @file{Makefile.def}. | |
466 | ||
467 | @item Flex version 2.5.4 (or later) | |
468 | ||
469 | Necessary when modifying @file{*.l} files. | |
470 | ||
471 | Necessary to build GCC during development because the generated output | |
472 | files are not included in the SVN repository. They are included in | |
473 | releases. | |
474 | ||
475 | @item Texinfo version 4.7 (or later) | |
476 | ||
477 | Necessary for running @command{makeinfo} when modifying @file{*.texi} | |
478 | files to test your changes. | |
479 | ||
480 | Necessary for running @command{make dvi} or @command{make pdf} to | |
481 | create printable documentation in DVI or PDF format. Texinfo version | |
482 | 4.8 or later is required for @command{make pdf}. | |
483 | ||
484 | Necessary to build GCC documentation during development because the | |
485 | generated output files are not included in the SVN repository. They are | |
486 | included in releases. | |
487 | ||
488 | @item @TeX{} (any working version) | |
489 | ||
490 | Necessary for running @command{texi2dvi} and @command{texi2pdf}, which | |
491 | are used when running @command{make dvi} or @command{make pdf} to create | |
492 | DVI or PDF files, respectively. | |
493 | ||
494 | @item SVN (any version) | |
495 | @itemx SSH (any version) | |
496 | ||
497 | Necessary to access the SVN repository. Public releases and weekly | |
498 | snapshots of the development sources are also available via FTP@. | |
499 | ||
500 | @item GNU diffutils version 2.7 (or later) | |
501 | ||
502 | Useful when submitting patches for the GCC source code. | |
503 | ||
504 | @item patch version 2.5.4 (or later) | |
505 | ||
506 | Necessary when applying patches, created with @command{diff}, to one's | |
507 | own sources. | |
508 | ||
509 | @item ecj1 | |
510 | @itemx gjavah | |
511 | ||
512 | If you wish to modify @file{.java} files in libjava, you will need to | |
513 | configure with @option{--enable-java-maintainer-mode}, and you will need | |
514 | to have executables named @command{ecj1} and @command{gjavah} in your path. | |
515 | The @command{ecj1} executable should run the Eclipse Java compiler via | |
516 | the GCC-specific entry point. You can download a suitable jar from | |
517 | @uref{ftp://sourceware.org/pub/java/}, or by running the script | |
518 | @command{contrib/download_ecj}. | |
519 | ||
520 | @item antlr.jar version 2.7.1 (or later) | |
521 | @itemx antlr binary | |
522 | ||
523 | If you wish to build the @command{gjdoc} binary in libjava, you will | |
524 | need to have an @file{antlr.jar} library available. The library is | |
525 | searched for in system locations but can be specified with | |
526 | @option{--with-antlr-jar=} instead. When configuring with | |
527 | @option{--enable-java-maintainer-mode}, you will need to have one of | |
528 | the executables named @command{cantlr}, @command{runantlr} or | |
529 | @command{antlr} in your path. | |
530 | ||
531 | @end table | |
532 | ||
533 | @html | |
534 | <hr /> | |
535 | <p> | |
536 | @end html | |
537 | @ifhtml | |
538 | @uref{./index.html,,Return to the GCC Installation page} | |
539 | @end ifhtml | |
540 | @end ifset | |
541 | ||
542 | @c ***Downloading the source************************************************** | |
543 | @ifnothtml | |
544 | @comment node-name, next, previous, up | |
545 | @node Downloading the source, Configuration, Prerequisites, Installing GCC | |
546 | @end ifnothtml | |
547 | @ifset downloadhtml | |
548 | @ifnothtml | |
549 | @chapter Downloading GCC | |
550 | @end ifnothtml | |
551 | @cindex Downloading GCC | |
552 | @cindex Downloading the Source | |
553 | ||
554 | GCC is distributed via @uref{http://gcc.gnu.org/svn.html,,SVN} and FTP | |
555 | tarballs compressed with @command{gzip} or | |
556 | @command{bzip2}. | |
557 | ||
558 | Please refer to the @uref{http://gcc.gnu.org/releases.html,,releases web page} | |
559 | for information on how to obtain GCC@. | |
560 | ||
561 | The source distribution includes the C, C++, Objective-C, Fortran, Java, | |
562 | and Ada (in the case of GCC 3.1 and later) compilers, as well as | |
563 | runtime libraries for C++, Objective-C, Fortran, and Java. | |
564 | For previous versions these were downloadable as separate components such | |
565 | as the core GCC distribution, which included the C language front end and | |
566 | shared components, and language-specific distributions including the | |
567 | language front end and the language runtime (where appropriate). | |
568 | ||
569 | If you also intend to build binutils (either to upgrade an existing | |
570 | installation or for use in place of the corresponding tools of your | |
571 | OS), unpack the binutils distribution either in the same directory or | |
572 | a separate one. In the latter case, add symbolic links to any | |
573 | components of the binutils you intend to build alongside the compiler | |
574 | (@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld}, | |
575 | @file{opcodes}, @dots{}) to the directory containing the GCC sources. | |
576 | ||
577 | Likewise the GMP, MPFR and MPC libraries can be automatically built | |
578 | together with GCC. Unpack the GMP, MPFR and/or MPC source | |
579 | distributions in the directory containing the GCC sources and rename | |
580 | their directories to @file{gmp}, @file{mpfr} and @file{mpc}, | |
581 | respectively (or use symbolic links with the same name). | |
582 | ||
583 | @html | |
584 | <hr /> | |
585 | <p> | |
586 | @end html | |
587 | @ifhtml | |
588 | @uref{./index.html,,Return to the GCC Installation page} | |
589 | @end ifhtml | |
590 | @end ifset | |
591 | ||
592 | @c ***Configuration*********************************************************** | |
593 | @ifnothtml | |
594 | @comment node-name, next, previous, up | |
595 | @node Configuration, Building, Downloading the source, Installing GCC | |
596 | @end ifnothtml | |
597 | @ifset configurehtml | |
598 | @ifnothtml | |
599 | @chapter Installing GCC: Configuration | |
600 | @end ifnothtml | |
601 | @cindex Configuration | |
602 | @cindex Installing GCC: Configuration | |
603 | ||
604 | Like most GNU software, GCC must be configured before it can be built. | |
605 | This document describes the recommended configuration procedure | |
606 | for both native and cross targets. | |
607 | ||
608 | We use @var{srcdir} to refer to the toplevel source directory for | |
609 | GCC; we use @var{objdir} to refer to the toplevel build/object directory. | |
610 | ||
611 | If you obtained the sources via SVN, @var{srcdir} must refer to the top | |
612 | @file{gcc} directory, the one where the @file{MAINTAINERS} file can be | |
613 | found, and not its @file{gcc} subdirectory, otherwise the build will fail. | |
614 | ||
615 | If either @var{srcdir} or @var{objdir} is located on an automounted NFS | |
616 | file system, the shell's built-in @command{pwd} command will return | |
617 | temporary pathnames. Using these can lead to various sorts of build | |
618 | problems. To avoid this issue, set the @env{PWDCMD} environment | |
619 | variable to an automounter-aware @command{pwd} command, e.g., | |
620 | @command{pawd} or @samp{amq -w}, during the configuration and build | |
621 | phases. | |
622 | ||
623 | First, we @strong{highly} recommend that GCC be built into a | |
624 | separate directory from the sources which does @strong{not} reside | |
625 | within the source tree. This is how we generally build GCC; building | |
626 | where @var{srcdir} == @var{objdir} should still work, but doesn't | |
627 | get extensive testing; building where @var{objdir} is a subdirectory | |
628 | of @var{srcdir} is unsupported. | |
629 | ||
630 | If you have previously built GCC in the same directory for a | |
631 | different target machine, do @samp{make distclean} to delete all files | |
632 | that might be invalid. One of the files this deletes is @file{Makefile}; | |
633 | if @samp{make distclean} complains that @file{Makefile} does not exist | |
634 | or issues a message like ``don't know how to make distclean'' it probably | |
635 | means that the directory is already suitably clean. However, with the | |
636 | recommended method of building in a separate @var{objdir}, you should | |
637 | simply use a different @var{objdir} for each target. | |
638 | ||
639 | Second, when configuring a native system, either @command{cc} or | |
640 | @command{gcc} must be in your path or you must set @env{CC} in | |
641 | your environment before running configure. Otherwise the configuration | |
642 | scripts may fail. | |
643 | ||
644 | @ignore | |
645 | Note that the bootstrap compiler and the resulting GCC must be link | |
646 | compatible, else the bootstrap will fail with linker errors about | |
647 | incompatible object file formats. Several multilibed targets are | |
648 | affected by this requirement, see | |
649 | @ifnothtml | |
650 | @ref{Specific, host/target specific installation notes}. | |
651 | @end ifnothtml | |
652 | @ifhtml | |
653 | @uref{specific.html,,host/target specific installation notes}. | |
654 | @end ifhtml | |
655 | @end ignore | |
656 | ||
657 | To configure GCC: | |
658 | ||
659 | @smallexample | |
660 | % mkdir @var{objdir} | |
661 | % cd @var{objdir} | |
662 | % @var{srcdir}/configure [@var{options}] [@var{target}] | |
663 | @end smallexample | |
664 | ||
665 | @heading Distributor options | |
666 | ||
667 | If you will be distributing binary versions of GCC, with modifications | |
668 | to the source code, you should use the options described in this | |
669 | section to make clear that your version contains modifications. | |
670 | ||
671 | @table @code | |
672 | @item --with-pkgversion=@var{version} | |
673 | Specify a string that identifies your package. You may wish | |
674 | to include a build number or build date. This version string will be | |
675 | included in the output of @command{gcc --version}. This suffix does | |
676 | not replace the default version string, only the @samp{GCC} part. | |
677 | ||
678 | The default value is @samp{GCC}. | |
679 | ||
680 | @item --with-bugurl=@var{url} | |
681 | Specify the URL that users should visit if they wish to report a bug. | |
682 | You are of course welcome to forward bugs reported to you to the FSF, | |
683 | if you determine that they are not bugs in your modifications. | |
684 | ||
685 | The default value refers to the FSF's GCC bug tracker. | |
686 | ||
687 | @end table | |
688 | ||
689 | @heading Target specification | |
690 | @itemize @bullet | |
691 | @item | |
692 | GCC has code to correctly determine the correct value for @var{target} | |
693 | for nearly all native systems. Therefore, we highly recommend you do | |
694 | not provide a configure target when configuring a native compiler. | |
695 | ||
696 | @item | |
697 | @var{target} must be specified as @option{--target=@var{target}} | |
698 | when configuring a cross compiler; examples of valid targets would be | |
699 | m68k-elf, sh-elf, etc. | |
700 | ||
701 | @item | |
702 | Specifying just @var{target} instead of @option{--target=@var{target}} | |
703 | implies that the host defaults to @var{target}. | |
704 | @end itemize | |
705 | ||
706 | ||
707 | @heading Options specification | |
708 | ||
709 | Use @var{options} to override several configure time options for | |
710 | GCC@. A list of supported @var{options} follows; @samp{configure | |
711 | --help} may list other options, but those not listed below may not | |
712 | work and should not normally be used. | |
713 | ||
714 | Note that each @option{--enable} option has a corresponding | |
715 | @option{--disable} option and that each @option{--with} option has a | |
716 | corresponding @option{--without} option. | |
717 | ||
718 | @table @code | |
719 | @item --prefix=@var{dirname} | |
720 | Specify the toplevel installation | |
721 | directory. This is the recommended way to install the tools into a directory | |
722 | other than the default. The toplevel installation directory defaults to | |
723 | @file{/usr/local}. | |
724 | ||
725 | We @strong{highly} recommend against @var{dirname} being the same or a | |
726 | subdirectory of @var{objdir} or vice versa. If specifying a directory | |
727 | beneath a user's home directory tree, some shells will not expand | |
728 | @var{dirname} correctly if it contains the @samp{~} metacharacter; use | |
729 | @env{$HOME} instead. | |
730 | ||
731 | The following standard @command{autoconf} options are supported. Normally you | |
732 | should not need to use these options. | |
733 | @table @code | |
734 | @item --exec-prefix=@var{dirname} | |
735 | Specify the toplevel installation directory for architecture-dependent | |
736 | files. The default is @file{@var{prefix}}. | |
737 | ||
738 | @item --bindir=@var{dirname} | |
739 | Specify the installation directory for the executables called by users | |
740 | (such as @command{gcc} and @command{g++}). The default is | |
741 | @file{@var{exec-prefix}/bin}. | |
742 | ||
743 | @item --libdir=@var{dirname} | |
744 | Specify the installation directory for object code libraries and | |
745 | internal data files of GCC@. The default is @file{@var{exec-prefix}/lib}. | |
746 | ||
747 | @item --libexecdir=@var{dirname} | |
748 | Specify the installation directory for internal executables of GCC@. | |
749 | The default is @file{@var{exec-prefix}/libexec}. | |
750 | ||
751 | @item --with-slibdir=@var{dirname} | |
752 | Specify the installation directory for the shared libgcc library. The | |
753 | default is @file{@var{libdir}}. | |
754 | ||
755 | @item --datarootdir=@var{dirname} | |
756 | Specify the root of the directory tree for read-only architecture-independent | |
757 | data files referenced by GCC@. The default is @file{@var{prefix}/share}. | |
758 | ||
759 | @item --infodir=@var{dirname} | |
760 | Specify the installation directory for documentation in info format. | |
761 | The default is @file{@var{datarootdir}/info}. | |
762 | ||
763 | @item --datadir=@var{dirname} | |
764 | Specify the installation directory for some architecture-independent | |
765 | data files referenced by GCC@. The default is @file{@var{datarootdir}}. | |
766 | ||
767 | @item --docdir=@var{dirname} | |
768 | Specify the installation directory for documentation files (other | |
769 | than Info) for GCC@. The default is @file{@var{datarootdir}/doc}. | |
770 | ||
771 | @item --htmldir=@var{dirname} | |
772 | Specify the installation directory for HTML documentation files. | |
773 | The default is @file{@var{docdir}}. | |
774 | ||
775 | @item --pdfdir=@var{dirname} | |
776 | Specify the installation directory for PDF documentation files. | |
777 | The default is @file{@var{docdir}}. | |
778 | ||
779 | @item --mandir=@var{dirname} | |
780 | Specify the installation directory for manual pages. The default is | |
781 | @file{@var{datarootdir}/man}. (Note that the manual pages are only extracts | |
782 | from the full GCC manuals, which are provided in Texinfo format. The manpages | |
783 | are derived by an automatic conversion process from parts of the full | |
784 | manual.) | |
785 | ||
786 | @item --with-gxx-include-dir=@var{dirname} | |
787 | Specify | |
788 | the installation directory for G++ header files. The default depends | |
789 | on other configuration options, and differs between cross and native | |
790 | configurations. | |
791 | ||
792 | @item --with-specs=@var{specs} | |
793 | Specify additional command line driver SPECS. | |
794 | This can be useful if you need to turn on a non-standard feature by | |
795 | default without modifying the compiler's source code, for instance | |
796 | @option{--with-specs=%@{!fcommon:%@{!fno-common:-fno-common@}@}}. | |
797 | @ifnothtml | |
798 | @xref{Spec Files,, Specifying subprocesses and the switches to pass to them, | |
799 | gcc, Using the GNU Compiler Collection (GCC)}, | |
800 | @end ifnothtml | |
801 | @ifhtml | |
802 | See ``Spec Files'' in the main manual | |
803 | @end ifhtml | |
804 | ||
805 | @end table | |
806 | ||
807 | @item --program-prefix=@var{prefix} | |
808 | GCC supports some transformations of the names of its programs when | |
809 | installing them. This option prepends @var{prefix} to the names of | |
810 | programs to install in @var{bindir} (see above). For example, specifying | |
811 | @option{--program-prefix=foo-} would result in @samp{gcc} | |
812 | being installed as @file{/usr/local/bin/foo-gcc}. | |
813 | ||
814 | @item --program-suffix=@var{suffix} | |
815 | Appends @var{suffix} to the names of programs to install in @var{bindir} | |
816 | (see above). For example, specifying @option{--program-suffix=-3.1} | |
817 | would result in @samp{gcc} being installed as | |
818 | @file{/usr/local/bin/gcc-3.1}. | |
819 | ||
820 | @item --program-transform-name=@var{pattern} | |
821 | Applies the @samp{sed} script @var{pattern} to be applied to the names | |
822 | of programs to install in @var{bindir} (see above). @var{pattern} has to | |
823 | consist of one or more basic @samp{sed} editing commands, separated by | |
824 | semicolons. For example, if you want the @samp{gcc} program name to be | |
825 | transformed to the installed program @file{/usr/local/bin/myowngcc} and | |
826 | the @samp{g++} program name to be transformed to | |
827 | @file{/usr/local/bin/gspecial++} without changing other program names, | |
828 | you could use the pattern | |
829 | @option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'} | |
830 | to achieve this effect. | |
831 | ||
832 | All three options can be combined and used together, resulting in more | |
833 | complex conversion patterns. As a basic rule, @var{prefix} (and | |
834 | @var{suffix}) are prepended (appended) before further transformations | |
835 | can happen with a special transformation script @var{pattern}. | |
836 | ||
837 | As currently implemented, this option only takes effect for native | |
838 | builds; cross compiler binaries' names are not transformed even when a | |
839 | transformation is explicitly asked for by one of these options. | |
840 | ||
841 | For native builds, some of the installed programs are also installed | |
842 | with the target alias in front of their name, as in | |
843 | @samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen | |
844 | before the target alias is prepended to the name---so, specifying | |
845 | @option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the | |
846 | resulting binary would be installed as | |
847 | @file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}. | |
848 | ||
849 | As a last shortcoming, none of the installed Ada programs are | |
850 | transformed yet, which will be fixed in some time. | |
851 | ||
852 | @item --with-local-prefix=@var{dirname} | |
853 | Specify the | |
854 | installation directory for local include files. The default is | |
855 | @file{/usr/local}. Specify this option if you want the compiler to | |
856 | search directory @file{@var{dirname}/include} for locally installed | |
857 | header files @emph{instead} of @file{/usr/local/include}. | |
858 | ||
859 | You should specify @option{--with-local-prefix} @strong{only} if your | |
860 | site has a different convention (not @file{/usr/local}) for where to put | |
861 | site-specific files. | |
862 | ||
863 | The default value for @option{--with-local-prefix} is @file{/usr/local} | |
864 | regardless of the value of @option{--prefix}. Specifying | |
865 | @option{--prefix} has no effect on which directory GCC searches for | |
866 | local header files. This may seem counterintuitive, but actually it is | |
867 | logical. | |
868 | ||
869 | The purpose of @option{--prefix} is to specify where to @emph{install | |
870 | GCC}. The local header files in @file{/usr/local/include}---if you put | |
871 | any in that directory---are not part of GCC@. They are part of other | |
872 | programs---perhaps many others. (GCC installs its own header files in | |
873 | another directory which is based on the @option{--prefix} value.) | |
874 | ||
875 | Both the local-prefix include directory and the GCC-prefix include | |
876 | directory are part of GCC's ``system include'' directories. Although these | |
877 | two directories are not fixed, they need to be searched in the proper | |
878 | order for the correct processing of the include_next directive. The | |
879 | local-prefix include directory is searched before the GCC-prefix | |
880 | include directory. Another characteristic of system include directories | |
881 | is that pedantic warnings are turned off for headers in these directories. | |
882 | ||
883 | Some autoconf macros add @option{-I @var{directory}} options to the | |
884 | compiler command line, to ensure that directories containing installed | |
885 | packages' headers are searched. When @var{directory} is one of GCC's | |
886 | system include directories, GCC will ignore the option so that system | |
887 | directories continue to be processed in the correct order. This | |
888 | may result in a search order different from what was specified but the | |
889 | directory will still be searched. | |
890 | ||
891 | GCC automatically searches for ordinary libraries using | |
892 | @env{GCC_EXEC_PREFIX}. Thus, when the same installation prefix is | |
893 | used for both GCC and packages, GCC will automatically search for | |
894 | both headers and libraries. This provides a configuration that is | |
895 | easy to use. GCC behaves in a manner similar to that when it is | |
896 | installed as a system compiler in @file{/usr}. | |
897 | ||
898 | Sites that need to install multiple versions of GCC may not want to | |
899 | use the above simple configuration. It is possible to use the | |
900 | @option{--program-prefix}, @option{--program-suffix} and | |
901 | @option{--program-transform-name} options to install multiple versions | |
902 | into a single directory, but it may be simpler to use different prefixes | |
903 | and the @option{--with-local-prefix} option to specify the location of the | |
904 | site-specific files for each version. It will then be necessary for | |
905 | users to specify explicitly the location of local site libraries | |
906 | (e.g., with @env{LIBRARY_PATH}). | |
907 | ||
908 | The same value can be used for both @option{--with-local-prefix} and | |
909 | @option{--prefix} provided it is not @file{/usr}. This can be used | |
910 | to avoid the default search of @file{/usr/local/include}. | |
911 | ||
912 | @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}! | |
913 | The directory you use for @option{--with-local-prefix} @strong{must not} | |
914 | contain any of the system's standard header files. If it did contain | |
915 | them, certain programs would be miscompiled (including GNU Emacs, on | |
916 | certain targets), because this would override and nullify the header | |
917 | file corrections made by the @command{fixincludes} script. | |
918 | ||
919 | Indications are that people who use this option use it based on mistaken | |
920 | ideas of what it is for. People use it as if it specified where to | |
921 | install part of GCC@. Perhaps they make this assumption because | |
922 | installing GCC creates the directory. | |
923 | ||
924 | @item --with-native-system-header-dir=@var{dirname} | |
925 | Specifies that @var{dirname} is the directory that contains native system | |
926 | header files, rather than @file{/usr/include}. This option is most useful | |
927 | if you are creating a compiler that should be isolated from the system | |
928 | as much as possible. It is most commonly used with the | |
929 | @option{--with-sysroot} option and will cause GCC to search | |
930 | @var{dirname} inside the system root specified by that option. | |
931 | ||
932 | @item --enable-shared[=@var{package}[,@dots{}]] | |
933 | Build shared versions of libraries, if shared libraries are supported on | |
934 | the target platform. Unlike GCC 2.95.x and earlier, shared libraries | |
935 | are enabled by default on all platforms that support shared libraries. | |
936 | ||
937 | If a list of packages is given as an argument, build shared libraries | |
938 | only for the listed packages. For other packages, only static libraries | |
939 | will be built. Package names currently recognized in the GCC tree are | |
940 | @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not | |
941 | @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc}, | |
942 | @samp{ada}, @samp{libada}, @samp{libjava}, @samp{libgo}, and @samp{libobjc}. | |
943 | Note @samp{libiberty} does not support shared libraries at all. | |
944 | ||
945 | Use @option{--disable-shared} to build only static libraries. Note that | |
946 | @option{--disable-shared} does not accept a list of package names as | |
947 | argument, only @option{--enable-shared} does. | |
948 | ||
949 | Contrast with @option{--enable-host-shared}, which affects @emph{host} | |
950 | code. | |
951 | ||
952 | @item --enable-host-shared | |
953 | Specify that the @emph{host} code should be built into position-independent | |
954 | machine code (with -fPIC), allowing it to be used within shared libraries, | |
955 | but yielding a slightly slower compiler. | |
956 | ||
957 | Currently this option is only of use to people developing GCC itself. | |
958 | ||
959 | Contrast with @option{--enable-shared}, which affects @emph{target} | |
960 | libraries. | |
961 | ||
962 | @item @anchor{with-gnu-as}--with-gnu-as | |
963 | Specify that the compiler should assume that the | |
964 | assembler it finds is the GNU assembler. However, this does not modify | |
965 | the rules to find an assembler and will result in confusion if the | |
966 | assembler found is not actually the GNU assembler. (Confusion may also | |
967 | result if the compiler finds the GNU assembler but has not been | |
968 | configured with @option{--with-gnu-as}.) If you have more than one | |
969 | assembler installed on your system, you may want to use this option in | |
970 | connection with @option{--with-as=@var{pathname}} or | |
971 | @option{--with-build-time-tools=@var{pathname}}. | |
972 | ||
973 | The following systems are the only ones where it makes a difference | |
974 | whether you use the GNU assembler. On any other system, | |
975 | @option{--with-gnu-as} has no effect. | |
976 | ||
977 | @itemize @bullet | |
978 | @item @samp{hppa1.0-@var{any}-@var{any}} | |
979 | @item @samp{hppa1.1-@var{any}-@var{any}} | |
980 | @item @samp{sparc-sun-solaris2.@var{any}} | |
981 | @item @samp{sparc64-@var{any}-solaris2.@var{any}} | |
982 | @end itemize | |
983 | ||
984 | @item @anchor{with-as}--with-as=@var{pathname} | |
985 | Specify that the compiler should use the assembler pointed to by | |
986 | @var{pathname}, rather than the one found by the standard rules to find | |
987 | an assembler, which are: | |
988 | @itemize @bullet | |
989 | @item | |
990 | Unless GCC is being built with a cross compiler, check the | |
991 | @file{@var{libexec}/gcc/@var{target}/@var{version}} directory. | |
992 | @var{libexec} defaults to @file{@var{exec-prefix}/libexec}; | |
993 | @var{exec-prefix} defaults to @var{prefix}, which | |
994 | defaults to @file{/usr/local} unless overridden by the | |
995 | @option{--prefix=@var{pathname}} switch described above. @var{target} | |
996 | is the target system triple, such as @samp{sparc-sun-solaris2.7}, and | |
997 | @var{version} denotes the GCC version, such as 3.0. | |
998 | ||
999 | @item | |
1000 | If the target system is the same that you are building on, check | |
1001 | operating system specific directories (e.g.@: @file{/usr/ccs/bin} on | |
1002 | Sun Solaris 2). | |
1003 | ||
1004 | @item | |
1005 | Check in the @env{PATH} for a tool whose name is prefixed by the | |
1006 | target system triple. | |
1007 | ||
1008 | @item | |
1009 | Check in the @env{PATH} for a tool whose name is not prefixed by the | |
1010 | target system triple, if the host and target system triple are | |
1011 | the same (in other words, we use a host tool if it can be used for | |
1012 | the target as well). | |
1013 | @end itemize | |
1014 | ||
1015 | You may want to use @option{--with-as} if no assembler | |
1016 | is installed in the directories listed above, or if you have multiple | |
1017 | assemblers installed and want to choose one that is not found by the | |
1018 | above rules. | |
1019 | ||
1020 | @item @anchor{with-gnu-ld}--with-gnu-ld | |
1021 | Same as @uref{#with-gnu-as,,@option{--with-gnu-as}} | |
1022 | but for the linker. | |
1023 | ||
1024 | @item --with-ld=@var{pathname} | |
1025 | Same as @uref{#with-as,,@option{--with-as}} | |
1026 | but for the linker. | |
1027 | ||
1028 | @item --with-stabs | |
1029 | Specify that stabs debugging | |
1030 | information should be used instead of whatever format the host normally | |
1031 | uses. Normally GCC uses the same debug format as the host system. | |
1032 | ||
1033 | On MIPS based systems and on Alphas, you must specify whether you want | |
1034 | GCC to create the normal ECOFF debugging format, or to use BSD-style | |
1035 | stabs passed through the ECOFF symbol table. The normal ECOFF debug | |
1036 | format cannot fully handle languages other than C@. BSD stabs format can | |
1037 | handle other languages, but it only works with the GNU debugger GDB@. | |
1038 | ||
1039 | Normally, GCC uses the ECOFF debugging format by default; if you | |
1040 | prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@. | |
1041 | ||
1042 | No matter which default you choose when you configure GCC, the user | |
1043 | can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly | |
1044 | the debug format for a particular compilation. | |
1045 | ||
1046 | @option{--with-stabs} is meaningful on the ISC system on the 386, also, if | |
1047 | @option{--with-gas} is used. It selects use of stabs debugging | |
1048 | information embedded in COFF output. This kind of debugging information | |
1049 | supports C++ well; ordinary COFF debugging information does not. | |
1050 | ||
1051 | @option{--with-stabs} is also meaningful on 386 systems running SVR4. It | |
1052 | selects use of stabs debugging information embedded in ELF output. The | |
1053 | C++ compiler currently (2.6.0) does not support the DWARF debugging | |
1054 | information normally used on 386 SVR4 platforms; stabs provide a | |
1055 | workable alternative. This requires gas and gdb, as the normal SVR4 | |
1056 | tools can not generate or interpret stabs. | |
1057 | ||
1058 | @item --with-tls=@var{dialect} | |
1059 | Specify the default TLS dialect, for systems were there is a choice. | |
1060 | For ARM targets, possible values for @var{dialect} are @code{gnu} or | |
1061 | @code{gnu2}, which select between the original GNU dialect and the GNU TLS | |
1062 | descriptor-based dialect. | |
1063 | ||
1064 | @item --enable-multiarch | |
1065 | Specify whether to enable or disable multiarch support. The default is | |
1066 | to check for glibc start files in a multiarch location, and enable it | |
1067 | if the files are found. The auto detection is enabled for native builds, | |
1068 | and for cross builds configured with @option{--with-sysroot}, and without | |
1069 | @option{--with-native-system-header-dir}. | |
1070 | More documentation about multiarch can be found at | |
1071 | @uref{http://wiki.debian.org/Multiarch}. | |
1072 | ||
1073 | @item --enable-vtable-verify | |
1074 | Specify whether to enable or disable the vtable verification feature. | |
1075 | Enabling this feature causes libstdc++ to be built with its virtual calls | |
1076 | in verifiable mode. This means that, when linked with libvtv, every | |
1077 | virtual call in libstdc++ will verify the vtable pointer through which the | |
1078 | call will be made before actually making the call. If not linked with libvtv, | |
1079 | the verifier will call stub functions (in libstdc++ itself) and do nothing. | |
1080 | If vtable verification is disabled, then libstdc++ is not built with its | |
1081 | virtual calls in verifiable mode at all. However the libvtv library will | |
1082 | still be built (see @option{--disable-libvtv} to turn off building libvtv). | |
1083 | @option{--disable-vtable-verify} is the default. | |
1084 | ||
1085 | @item --disable-multilib | |
1086 | Specify that multiple target | |
1087 | libraries to support different target variants, calling | |
1088 | conventions, etc.@: should not be built. The default is to build a | |
1089 | predefined set of them. | |
1090 | ||
1091 | Some targets provide finer-grained control over which multilibs are built | |
1092 | (e.g., @option{--disable-softfloat}): | |
1093 | @table @code | |
1094 | @item arm-*-* | |
1095 | fpu, 26bit, underscore, interwork, biendian, nofmult. | |
1096 | ||
1097 | @item m68*-*-* | |
1098 | softfloat, m68881, m68000, m68020. | |
1099 | ||
1100 | @item mips*-*-* | |
1101 | single-float, biendian, softfloat. | |
1102 | ||
1103 | @item powerpc*-*-*, rs6000*-*-* | |
1104 | aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian, | |
1105 | sysv, aix. | |
1106 | ||
1107 | @end table | |
1108 | ||
1109 | @item --with-multilib-list=@var{list} | |
1110 | @itemx --without-multilib-list | |
1111 | Specify what multilibs to build. | |
1112 | Currently only implemented for sh*-*-* and x86-64-*-linux*. | |
1113 | ||
1114 | @table @code | |
1115 | @item sh*-*-* | |
1116 | @var{list} is a comma separated list of CPU names. These must be of the | |
1117 | form @code{sh*} or @code{m*} (in which case they match the compiler option | |
1118 | for that processor). The list should not contain any endian options - | |
1119 | these are handled by @option{--with-endian}. | |
1120 | ||
1121 | If @var{list} is empty, then there will be no multilibs for extra | |
1122 | processors. The multilib for the secondary endian remains enabled. | |
1123 | ||
1124 | As a special case, if an entry in the list starts with a @code{!} | |
1125 | (exclamation point), then it is added to the list of excluded multilibs. | |
1126 | Entries of this sort should be compatible with @samp{MULTILIB_EXCLUDES} | |
1127 | (once the leading @code{!} has been stripped). | |
1128 | ||
1129 | If @option{--with-multilib-list} is not given, then a default set of | |
1130 | multilibs is selected based on the value of @option{--target}. This is | |
1131 | usually the complete set of libraries, but some targets imply a more | |
1132 | specialized subset. | |
1133 | ||
1134 | Example 1: to configure a compiler for SH4A only, but supporting both | |
1135 | endians, with little endian being the default: | |
1136 | @smallexample | |
1137 | --with-cpu=sh4a --with-endian=little,big --with-multilib-list= | |
1138 | @end smallexample | |
1139 | ||
1140 | Example 2: to configure a compiler for both SH4A and SH4AL-DSP, but with | |
1141 | only little endian SH4AL: | |
1142 | @smallexample | |
1143 | --with-cpu=sh4a --with-endian=little,big \ | |
1144 | --with-multilib-list=sh4al,!mb/m4al | |
1145 | @end smallexample | |
1146 | ||
1147 | @item x86-64-*-linux* | |
1148 | @var{list} is a comma separated list of @code{m32}, @code{m64} and | |
1149 | @code{mx32} to enable 32-bit, 64-bit and x32 run-time libraries, | |
1150 | respectively. If @var{list} is empty, then there will be no multilibs | |
1151 | and only the default run-time library will be enabled. | |
1152 | ||
1153 | If @option{--with-multilib-list} is not given, then only 32-bit and | |
1154 | 64-bit run-time libraries will be enabled. | |
1155 | @end table | |
1156 | ||
1157 | @item --with-endian=@var{endians} | |
1158 | Specify what endians to use. | |
1159 | Currently only implemented for sh*-*-*. | |
1160 | ||
1161 | @var{endians} may be one of the following: | |
1162 | @table @code | |
1163 | @item big | |
1164 | Use big endian exclusively. | |
1165 | @item little | |
1166 | Use little endian exclusively. | |
1167 | @item big,little | |
1168 | Use big endian by default. Provide a multilib for little endian. | |
1169 | @item little,big | |
1170 | Use little endian by default. Provide a multilib for big endian. | |
1171 | @end table | |
1172 | ||
1173 | @item --enable-threads | |
1174 | Specify that the target | |
1175 | supports threads. This affects the Objective-C compiler and runtime | |
1176 | library, and exception handling for other languages like C++ and Java. | |
1177 | On some systems, this is the default. | |
1178 | ||
1179 | In general, the best (and, in many cases, the only known) threading | |
1180 | model available will be configured for use. Beware that on some | |
1181 | systems, GCC has not been taught what threading models are generally | |
1182 | available for the system. In this case, @option{--enable-threads} is an | |
1183 | alias for @option{--enable-threads=single}. | |
1184 | ||
1185 | @item --disable-threads | |
1186 | Specify that threading support should be disabled for the system. | |
1187 | This is an alias for @option{--enable-threads=single}. | |
1188 | ||
1189 | @item --enable-threads=@var{lib} | |
1190 | Specify that | |
1191 | @var{lib} is the thread support library. This affects the Objective-C | |
1192 | compiler and runtime library, and exception handling for other languages | |
1193 | like C++ and Java. The possibilities for @var{lib} are: | |
1194 | ||
1195 | @table @code | |
1196 | @item aix | |
1197 | AIX thread support. | |
1198 | @item dce | |
1199 | DCE thread support. | |
1200 | @item lynx | |
1201 | LynxOS thread support. | |
1202 | @item mipssde | |
1203 | MIPS SDE thread support. | |
1204 | @item no | |
1205 | This is an alias for @samp{single}. | |
1206 | @item posix | |
1207 | Generic POSIX/Unix98 thread support. | |
1208 | @item rtems | |
1209 | RTEMS thread support. | |
1210 | @item single | |
1211 | Disable thread support, should work for all platforms. | |
1212 | @item tpf | |
1213 | TPF thread support. | |
1214 | @item vxworks | |
1215 | VxWorks thread support. | |
1216 | @item win32 | |
1217 | Microsoft Win32 API thread support. | |
1218 | @end table | |
1219 | ||
1220 | @item --enable-tls | |
1221 | Specify that the target supports TLS (Thread Local Storage). Usually | |
1222 | configure can correctly determine if TLS is supported. In cases where | |
1223 | it guesses incorrectly, TLS can be explicitly enabled or disabled with | |
1224 | @option{--enable-tls} or @option{--disable-tls}. This can happen if | |
1225 | the assembler supports TLS but the C library does not, or if the | |
1226 | assumptions made by the configure test are incorrect. | |
1227 | ||
1228 | @item --disable-tls | |
1229 | Specify that the target does not support TLS. | |
1230 | This is an alias for @option{--enable-tls=no}. | |
1231 | ||
1232 | @item --with-cpu=@var{cpu} | |
1233 | @itemx --with-cpu-32=@var{cpu} | |
1234 | @itemx --with-cpu-64=@var{cpu} | |
1235 | Specify which cpu variant the compiler should generate code for by default. | |
1236 | @var{cpu} will be used as the default value of the @option{-mcpu=} switch. | |
1237 | This option is only supported on some targets, including ARC, ARM, i386, M68k, | |
1238 | PowerPC, and SPARC@. It is mandatory for ARC@. The @option{--with-cpu-32} and | |
1239 | @option{--with-cpu-64} options specify separate default CPUs for | |
1240 | 32-bit and 64-bit modes; these options are only supported for i386, | |
1241 | x86-64 and PowerPC. | |
1242 | ||
1243 | @item --with-schedule=@var{cpu} | |
1244 | @itemx --with-arch=@var{cpu} | |
1245 | @itemx --with-arch-32=@var{cpu} | |
1246 | @itemx --with-arch-64=@var{cpu} | |
1247 | @itemx --with-tune=@var{cpu} | |
1248 | @itemx --with-tune-32=@var{cpu} | |
1249 | @itemx --with-tune-64=@var{cpu} | |
1250 | @itemx --with-abi=@var{abi} | |
1251 | @itemx --with-fpu=@var{type} | |
1252 | @itemx --with-float=@var{type} | |
1253 | These configure options provide default values for the @option{-mschedule=}, | |
1254 | @option{-march=}, @option{-mtune=}, @option{-mabi=}, and @option{-mfpu=} | |
1255 | options and for @option{-mhard-float} or @option{-msoft-float}. As with | |
1256 | @option{--with-cpu}, which switches will be accepted and acceptable values | |
1257 | of the arguments depend on the target. | |
1258 | ||
1259 | @item --with-mode=@var{mode} | |
1260 | Specify if the compiler should default to @option{-marm} or @option{-mthumb}. | |
1261 | This option is only supported on ARM targets. | |
1262 | ||
1263 | @item --with-stack-offset=@var{num} | |
1264 | This option sets the default for the -mstack-offset=@var{num} option, | |
1265 | and will thus generally also control the setting of this option for | |
1266 | libraries. This option is only supported on Epiphany targets. | |
1267 | ||
1268 | @item --with-fpmath=@var{isa} | |
1269 | This options sets @option{-mfpmath=sse} by default and specifies the default | |
1270 | ISA for floating-point arithmetics. You can select either @samp{sse} which | |
1271 | enables @option{-msse2} or @samp{avx} which enables @option{-mavx} by default. | |
1272 | This option is only supported on i386 and x86-64 targets. | |
1273 | ||
1274 | @item --with-nan=@var{encoding} | |
1275 | On MIPS targets, set the default encoding convention to use for the | |
1276 | special not-a-number (NaN) IEEE 754 floating-point data. The | |
1277 | possibilities for @var{encoding} are: | |
1278 | @table @code | |
1279 | @item legacy | |
1280 | Use the legacy encoding, as with the @option{-mnan=legacy} command-line | |
1281 | option. | |
1282 | @item 2008 | |
1283 | Use the 754-2008 encoding, as with the @option{-mnan=2008} command-line | |
1284 | option. | |
1285 | @end table | |
1286 | To use this configuration option you must have an assembler version | |
1287 | installed that supports the @option{-mnan=} command-line option too. | |
1288 | In the absence of this configuration option the default convention is | |
1289 | the legacy encoding, as when neither of the @option{-mnan=2008} and | |
1290 | @option{-mnan=legacy} command-line options has been used. | |
1291 | ||
1292 | @item --with-divide=@var{type} | |
1293 | Specify how the compiler should generate code for checking for | |
1294 | division by zero. This option is only supported on the MIPS target. | |
1295 | The possibilities for @var{type} are: | |
1296 | @table @code | |
1297 | @item traps | |
1298 | Division by zero checks use conditional traps (this is the default on | |
1299 | systems that support conditional traps). | |
1300 | @item breaks | |
1301 | Division by zero checks use the break instruction. | |
1302 | @end table | |
1303 | ||
1304 | @c If you make --with-llsc the default for additional targets, | |
1305 | @c update the --with-llsc description in the MIPS section below. | |
1306 | ||
1307 | @item --with-llsc | |
1308 | On MIPS targets, make @option{-mllsc} the default when no | |
1309 | @option{-mno-llsc} option is passed. This is the default for | |
1310 | Linux-based targets, as the kernel will emulate them if the ISA does | |
1311 | not provide them. | |
1312 | ||
1313 | @item --without-llsc | |
1314 | On MIPS targets, make @option{-mno-llsc} the default when no | |
1315 | @option{-mllsc} option is passed. | |
1316 | ||
1317 | @item --with-synci | |
1318 | On MIPS targets, make @option{-msynci} the default when no | |
1319 | @option{-mno-synci} option is passed. | |
1320 | ||
1321 | @item --without-synci | |
1322 | On MIPS targets, make @option{-mno-synci} the default when no | |
1323 | @option{-msynci} option is passed. This is the default. | |
1324 | ||
1325 | @item --with-mips-plt | |
1326 | On MIPS targets, make use of copy relocations and PLTs. | |
1327 | These features are extensions to the traditional | |
1328 | SVR4-based MIPS ABIs and require support from GNU binutils | |
1329 | and the runtime C library. | |
1330 | ||
1331 | @item --enable-__cxa_atexit | |
1332 | Define if you want to use __cxa_atexit, rather than atexit, to | |
1333 | register C++ destructors for local statics and global objects. | |
1334 | This is essential for fully standards-compliant handling of | |
1335 | destructors, but requires __cxa_atexit in libc. This option is currently | |
1336 | only available on systems with GNU libc. When enabled, this will cause | |
1337 | @option{-fuse-cxa-atexit} to be passed by default. | |
1338 | ||
1339 | @item --enable-gnu-indirect-function | |
1340 | Define if you want to enable the @code{ifunc} attribute. This option is | |
1341 | currently only available on systems with GNU libc on certain targets. | |
1342 | ||
1343 | @item --enable-target-optspace | |
1344 | Specify that target | |
1345 | libraries should be optimized for code space instead of code speed. | |
1346 | This is the default for the m32r platform. | |
1347 | ||
1348 | @item --with-cpp-install-dir=@var{dirname} | |
1349 | Specify that the user visible @command{cpp} program should be installed | |
1350 | in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}. | |
1351 | ||
1352 | @item --enable-comdat | |
1353 | Enable COMDAT group support. This is primarily used to override the | |
1354 | automatically detected value. | |
1355 | ||
1356 | @item --enable-initfini-array | |
1357 | Force the use of sections @code{.init_array} and @code{.fini_array} | |
1358 | (instead of @code{.init} and @code{.fini}) for constructors and | |
1359 | destructors. Option @option{--disable-initfini-array} has the | |
1360 | opposite effect. If neither option is specified, the configure script | |
1361 | will try to guess whether the @code{.init_array} and | |
1362 | @code{.fini_array} sections are supported and, if they are, use them. | |
1363 | ||
1364 | @item --enable-link-mutex | |
1365 | When building GCC, use a mutex to avoid linking the compilers for | |
1366 | multiple languages at the same time, to avoid thrashing on build | |
1367 | systems with limited free memory. The default is not to use such a mutex. | |
1368 | ||
1369 | @item --enable-maintainer-mode | |
1370 | The build rules that regenerate the Autoconf and Automake output files as | |
1371 | well as the GCC master message catalog @file{gcc.pot} are normally | |
1372 | disabled. This is because it can only be rebuilt if the complete source | |
1373 | tree is present. If you have changed the sources and want to rebuild the | |
1374 | catalog, configuring with @option{--enable-maintainer-mode} will enable | |
1375 | this. Note that you need a recent version of the @code{gettext} tools | |
1376 | to do so. | |
1377 | ||
1378 | @item --disable-bootstrap | |
1379 | For a native build, the default configuration is to perform | |
1380 | a 3-stage bootstrap of the compiler when @samp{make} is invoked, | |
1381 | testing that GCC can compile itself correctly. If you want to disable | |
1382 | this process, you can configure with @option{--disable-bootstrap}. | |
1383 | ||
1384 | @item --enable-bootstrap | |
1385 | In special cases, you may want to perform a 3-stage build | |
1386 | even if the target and host triplets are different. | |
1387 | This is possible when the host can run code compiled for | |
1388 | the target (e.g.@: host is i686-linux, target is i486-linux). | |
1389 | Starting from GCC 4.2, to do this you have to configure explicitly | |
1390 | with @option{--enable-bootstrap}. | |
1391 | ||
1392 | @item --enable-generated-files-in-srcdir | |
1393 | Neither the .c and .h files that are generated from Bison and flex nor the | |
1394 | info manuals and man pages that are built from the .texi files are present | |
1395 | in the SVN development tree. When building GCC from that development tree, | |
1396 | or from one of our snapshots, those generated files are placed in your | |
1397 | build directory, which allows for the source to be in a readonly | |
1398 | directory. | |
1399 | ||
1400 | If you configure with @option{--enable-generated-files-in-srcdir} then those | |
1401 | generated files will go into the source directory. This is mainly intended | |
1402 | for generating release or prerelease tarballs of the GCC sources, since it | |
1403 | is not a requirement that the users of source releases to have flex, Bison, | |
1404 | or makeinfo. | |
1405 | ||
1406 | @item --enable-version-specific-runtime-libs | |
1407 | Specify | |
1408 | that runtime libraries should be installed in the compiler specific | |
1409 | subdirectory (@file{@var{libdir}/gcc}) rather than the usual places. In | |
1410 | addition, @samp{libstdc++}'s include files will be installed into | |
1411 | @file{@var{libdir}} unless you overruled it by using | |
1412 | @option{--with-gxx-include-dir=@var{dirname}}. Using this option is | |
1413 | particularly useful if you intend to use several versions of GCC in | |
1414 | parallel. This is currently supported by @samp{libgfortran}, | |
1415 | @samp{libjava}, @samp{libstdc++}, and @samp{libobjc}. | |
1416 | ||
1417 | @item --enable-languages=@var{lang1},@var{lang2},@dots{} | |
1418 | Specify that only a particular subset of compilers and | |
1419 | their runtime libraries should be built. For a list of valid values for | |
1420 | @var{langN} you can issue the following command in the | |
1421 | @file{gcc} directory of your GCC source tree:@* | |
1422 | @smallexample | |
1423 | grep language= */config-lang.in | |
1424 | @end smallexample | |
1425 | Currently, you can use any of the following: | |
1426 | @code{all}, @code{ada}, @code{c}, @code{c++}, @code{fortran}, | |
1427 | @code{go}, @code{java}, @code{objc}, @code{obj-c++}. | |
1428 | Building the Ada compiler has special requirements, see below. | |
1429 | If you do not pass this flag, or specify the option @code{all}, then all | |
1430 | default languages available in the @file{gcc} sub-tree will be configured. | |
1431 | Ada, Go and Objective-C++ are not default languages; the rest are. | |
1432 | ||
1433 | @item --enable-stage1-languages=@var{lang1},@var{lang2},@dots{} | |
1434 | Specify that a particular subset of compilers and their runtime | |
1435 | libraries should be built with the system C compiler during stage 1 of | |
1436 | the bootstrap process, rather than only in later stages with the | |
1437 | bootstrapped C compiler. The list of valid values is the same as for | |
1438 | @option{--enable-languages}, and the option @code{all} will select all | |
1439 | of the languages enabled by @option{--enable-languages}. This option is | |
1440 | primarily useful for GCC development; for instance, when a development | |
1441 | version of the compiler cannot bootstrap due to compiler bugs, or when | |
1442 | one is debugging front ends other than the C front end. When this | |
1443 | option is used, one can then build the target libraries for the | |
1444 | specified languages with the stage-1 compiler by using @command{make | |
1445 | stage1-bubble all-target}, or run the testsuite on the stage-1 compiler | |
1446 | for the specified languages using @command{make stage1-start check-gcc}. | |
1447 | ||
1448 | @item --disable-libada | |
1449 | Specify that the run-time libraries and tools used by GNAT should not | |
1450 | be built. This can be useful for debugging, or for compatibility with | |
1451 | previous Ada build procedures, when it was required to explicitly | |
1452 | do a @samp{make -C gcc gnatlib_and_tools}. | |
1453 | ||
1454 | @item --disable-libssp | |
1455 | Specify that the run-time libraries for stack smashing protection | |
1456 | should not be built. | |
1457 | ||
1458 | @item --disable-libquadmath | |
1459 | Specify that the GCC quad-precision math library should not be built. | |
1460 | On some systems, the library is required to be linkable when building | |
1461 | the Fortran front end, unless @option{--disable-libquadmath-support} | |
1462 | is used. | |
1463 | ||
1464 | @item --disable-libquadmath-support | |
1465 | Specify that the Fortran front end and @code{libgfortran} do not add | |
1466 | support for @code{libquadmath} on systems supporting it. | |
1467 | ||
1468 | @item --disable-libgomp | |
1469 | Specify that the run-time libraries used by GOMP should not be built. | |
1470 | ||
1471 | @item --disable-libvtv | |
1472 | Specify that the run-time libraries used by vtable verification | |
1473 | should not be built. | |
1474 | ||
1475 | @item --with-dwarf2 | |
1476 | Specify that the compiler should | |
1477 | use DWARF 2 debugging information as the default. | |
1478 | ||
1479 | @item --enable-targets=all | |
1480 | @itemx --enable-targets=@var{target_list} | |
1481 | Some GCC targets, e.g.@: powerpc64-linux, build bi-arch compilers. | |
1482 | These are compilers that are able to generate either 64-bit or 32-bit | |
1483 | code. Typically, the corresponding 32-bit target, e.g.@: | |
1484 | powerpc-linux for powerpc64-linux, only generates 32-bit code. This | |
1485 | option enables the 32-bit target to be a bi-arch compiler, which is | |
1486 | useful when you want a bi-arch compiler that defaults to 32-bit, and | |
1487 | you are building a bi-arch or multi-arch binutils in a combined tree. | |
1488 | On mips-linux, this will build a tri-arch compiler (ABI o32/n32/64), | |
1489 | defaulted to o32. | |
1490 | Currently, this option only affects sparc-linux, powerpc-linux, x86-linux, | |
1491 | mips-linux and s390-linux. | |
1492 | ||
1493 | @item --enable-secureplt | |
1494 | This option enables @option{-msecure-plt} by default for powerpc-linux. | |
1495 | @ifnothtml | |
1496 | @xref{RS/6000 and PowerPC Options,, RS/6000 and PowerPC Options, gcc, | |
1497 | Using the GNU Compiler Collection (GCC)}, | |
1498 | @end ifnothtml | |
1499 | @ifhtml | |
1500 | See ``RS/6000 and PowerPC Options'' in the main manual | |
1501 | @end ifhtml | |
1502 | ||
1503 | @item --enable-cld | |
1504 | This option enables @option{-mcld} by default for 32-bit x86 targets. | |
1505 | @ifnothtml | |
1506 | @xref{i386 and x86-64 Options,, i386 and x86-64 Options, gcc, | |
1507 | Using the GNU Compiler Collection (GCC)}, | |
1508 | @end ifnothtml | |
1509 | @ifhtml | |
1510 | See ``i386 and x86-64 Options'' in the main manual | |
1511 | @end ifhtml | |
1512 | ||
1513 | @item --enable-win32-registry | |
1514 | @itemx --enable-win32-registry=@var{key} | |
1515 | @itemx --disable-win32-registry | |
1516 | The @option{--enable-win32-registry} option enables Microsoft Windows-hosted GCC | |
1517 | to look up installations paths in the registry using the following key: | |
1518 | ||
1519 | @smallexample | |
1520 | @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}} | |
1521 | @end smallexample | |
1522 | ||
1523 | @var{key} defaults to GCC version number, and can be overridden by the | |
1524 | @option{--enable-win32-registry=@var{key}} option. Vendors and distributors | |
1525 | who use custom installers are encouraged to provide a different key, | |
1526 | perhaps one comprised of vendor name and GCC version number, to | |
1527 | avoid conflict with existing installations. This feature is enabled | |
1528 | by default, and can be disabled by @option{--disable-win32-registry} | |
1529 | option. This option has no effect on the other hosts. | |
1530 | ||
1531 | @item --nfp | |
1532 | Specify that the machine does not have a floating point unit. This | |
1533 | option only applies to @samp{m68k-sun-sunos@var{n}}. On any other | |
1534 | system, @option{--nfp} has no effect. | |
1535 | ||
1536 | @item --enable-werror | |
1537 | @itemx --disable-werror | |
1538 | @itemx --enable-werror=yes | |
1539 | @itemx --enable-werror=no | |
1540 | When you specify this option, it controls whether certain files in the | |
1541 | compiler are built with @option{-Werror} in bootstrap stage2 and later. | |
1542 | If you don't specify it, @option{-Werror} is turned on for the main | |
1543 | development trunk. However it defaults to off for release branches and | |
1544 | final releases. The specific files which get @option{-Werror} are | |
1545 | controlled by the Makefiles. | |
1546 | ||
1547 | @item --enable-checking | |
1548 | @itemx --enable-checking=@var{list} | |
1549 | When you specify this option, the compiler is built to perform internal | |
1550 | consistency checks of the requested complexity. This does not change the | |
1551 | generated code, but adds error checking within the compiler. This will | |
1552 | slow down the compiler and may only work properly if you are building | |
1553 | the compiler with GCC@. This is @samp{yes} by default when building | |
1554 | from SVN or snapshots, but @samp{release} for releases. The default | |
1555 | for building the stage1 compiler is @samp{yes}. More control | |
1556 | over the checks may be had by specifying @var{list}. The categories of | |
1557 | checks available are @samp{yes} (most common checks | |
1558 | @samp{assert,misc,tree,gc,rtlflag,runtime}), @samp{no} (no checks at | |
1559 | all), @samp{all} (all but @samp{valgrind}), @samp{release} (cheapest | |
1560 | checks @samp{assert,runtime}) or @samp{none} (same as @samp{no}). | |
1561 | Individual checks can be enabled with these flags @samp{assert}, | |
1562 | @samp{df}, @samp{fold}, @samp{gc}, @samp{gcac} @samp{misc}, @samp{rtl}, | |
1563 | @samp{rtlflag}, @samp{runtime}, @samp{tree}, and @samp{valgrind}. | |
1564 | ||
1565 | The @samp{valgrind} check requires the external @command{valgrind} | |
1566 | simulator, available from @uref{http://valgrind.org/}. The | |
1567 | @samp{df}, @samp{rtl}, @samp{gcac} and @samp{valgrind} checks are very expensive. | |
1568 | To disable all checking, @samp{--disable-checking} or | |
1569 | @samp{--enable-checking=none} must be explicitly requested. Disabling | |
1570 | assertions will make the compiler and runtime slightly faster but | |
1571 | increase the risk of undetected internal errors causing wrong code to be | |
1572 | generated. | |
1573 | ||
1574 | @item --disable-stage1-checking | |
1575 | @itemx --enable-stage1-checking | |
1576 | @itemx --enable-stage1-checking=@var{list} | |
1577 | If no @option{--enable-checking} option is specified the stage1 | |
1578 | compiler will be built with @samp{yes} checking enabled, otherwise | |
1579 | the stage1 checking flags are the same as specified by | |
1580 | @option{--enable-checking}. To build the stage1 compiler with | |
1581 | different checking options use @option{--enable-stage1-checking}. | |
1582 | The list of checking options is the same as for @option{--enable-checking}. | |
1583 | If your system is too slow or too small to bootstrap a released compiler | |
1584 | with checking for stage1 enabled, you can use @samp{--disable-stage1-checking} | |
1585 | to disable checking for the stage1 compiler. | |
1586 | ||
1587 | @item --enable-coverage | |
1588 | @itemx --enable-coverage=@var{level} | |
1589 | With this option, the compiler is built to collect self coverage | |
1590 | information, every time it is run. This is for internal development | |
1591 | purposes, and only works when the compiler is being built with gcc. The | |
1592 | @var{level} argument controls whether the compiler is built optimized or | |
1593 | not, values are @samp{opt} and @samp{noopt}. For coverage analysis you | |
1594 | want to disable optimization, for performance analysis you want to | |
1595 | enable optimization. When coverage is enabled, the default level is | |
1596 | without optimization. | |
1597 | ||
1598 | @item --enable-gather-detailed-mem-stats | |
1599 | When this option is specified more detailed information on memory | |
1600 | allocation is gathered. This information is printed when using | |
1601 | @option{-fmem-report}. | |
1602 | ||
1603 | @item --enable-nls | |
1604 | @itemx --disable-nls | |
1605 | The @option{--enable-nls} option enables Native Language Support (NLS), | |
1606 | which lets GCC output diagnostics in languages other than American | |
1607 | English. Native Language Support is enabled by default if not doing a | |
1608 | canadian cross build. The @option{--disable-nls} option disables NLS@. | |
1609 | ||
1610 | @item --with-included-gettext | |
1611 | If NLS is enabled, the @option{--with-included-gettext} option causes the build | |
1612 | procedure to prefer its copy of GNU @command{gettext}. | |
1613 | ||
1614 | @item --with-catgets | |
1615 | If NLS is enabled, and if the host lacks @code{gettext} but has the | |
1616 | inferior @code{catgets} interface, the GCC build procedure normally | |
1617 | ignores @code{catgets} and instead uses GCC's copy of the GNU | |
1618 | @code{gettext} library. The @option{--with-catgets} option causes the | |
1619 | build procedure to use the host's @code{catgets} in this situation. | |
1620 | ||
1621 | @item --with-libiconv-prefix=@var{dir} | |
1622 | Search for libiconv header files in @file{@var{dir}/include} and | |
1623 | libiconv library files in @file{@var{dir}/lib}. | |
1624 | ||
1625 | @item --enable-obsolete | |
1626 | Enable configuration for an obsoleted system. If you attempt to | |
1627 | configure GCC for a system (build, host, or target) which has been | |
1628 | obsoleted, and you do not specify this flag, configure will halt with an | |
1629 | error message. | |
1630 | ||
1631 | All support for systems which have been obsoleted in one release of GCC | |
1632 | is removed entirely in the next major release, unless someone steps | |
1633 | forward to maintain the port. | |
1634 | ||
1635 | @item --enable-decimal-float | |
1636 | @itemx --enable-decimal-float=yes | |
1637 | @itemx --enable-decimal-float=no | |
1638 | @itemx --enable-decimal-float=bid | |
1639 | @itemx --enable-decimal-float=dpd | |
1640 | @itemx --disable-decimal-float | |
1641 | Enable (or disable) support for the C decimal floating point extension | |
1642 | that is in the IEEE 754-2008 standard. This is enabled by default only | |
1643 | on PowerPC, i386, and x86_64 GNU/Linux systems. Other systems may also | |
1644 | support it, but require the user to specifically enable it. You can | |
1645 | optionally control which decimal floating point format is used (either | |
1646 | @samp{bid} or @samp{dpd}). The @samp{bid} (binary integer decimal) | |
1647 | format is default on i386 and x86_64 systems, and the @samp{dpd} | |
1648 | (densely packed decimal) format is default on PowerPC systems. | |
1649 | ||
1650 | @item --enable-fixed-point | |
1651 | @itemx --disable-fixed-point | |
1652 | Enable (or disable) support for C fixed-point arithmetic. | |
1653 | This option is enabled by default for some targets (such as MIPS) which | |
1654 | have hardware-support for fixed-point operations. On other targets, you | |
1655 | may enable this option manually. | |
1656 | ||
1657 | @item --with-long-double-128 | |
1658 | Specify if @code{long double} type should be 128-bit by default on selected | |
1659 | GNU/Linux architectures. If using @code{--without-long-double-128}, | |
1660 | @code{long double} will be by default 64-bit, the same as @code{double} type. | |
1661 | When neither of these configure options are used, the default will be | |
1662 | 128-bit @code{long double} when built against GNU C Library 2.4 and later, | |
1663 | 64-bit @code{long double} otherwise. | |
1664 | ||
1665 | @item --with-gmp=@var{pathname} | |
1666 | @itemx --with-gmp-include=@var{pathname} | |
1667 | @itemx --with-gmp-lib=@var{pathname} | |
1668 | @itemx --with-mpfr=@var{pathname} | |
1669 | @itemx --with-mpfr-include=@var{pathname} | |
1670 | @itemx --with-mpfr-lib=@var{pathname} | |
1671 | @itemx --with-mpc=@var{pathname} | |
1672 | @itemx --with-mpc-include=@var{pathname} | |
1673 | @itemx --with-mpc-lib=@var{pathname} | |
1674 | If you want to build GCC but do not have the GMP library, the MPFR | |
1675 | library and/or the MPC library installed in a standard location and | |
1676 | do not have their sources present in the GCC source tree then you | |
1677 | can explicitly specify the directory where they are installed | |
1678 | (@samp{--with-gmp=@var{gmpinstalldir}}, | |
1679 | @samp{--with-mpfr=@/@var{mpfrinstalldir}}, | |
1680 | @samp{--with-mpc=@/@var{mpcinstalldir}}). The | |
1681 | @option{--with-gmp=@/@var{gmpinstalldir}} option is shorthand for | |
1682 | @option{--with-gmp-lib=@/@var{gmpinstalldir}/lib} and | |
1683 | @option{--with-gmp-include=@/@var{gmpinstalldir}/include}. Likewise the | |
1684 | @option{--with-mpfr=@/@var{mpfrinstalldir}} option is shorthand for | |
1685 | @option{--with-mpfr-lib=@/@var{mpfrinstalldir}/lib} and | |
1686 | @option{--with-mpfr-include=@/@var{mpfrinstalldir}/include}, also the | |
1687 | @option{--with-mpc=@/@var{mpcinstalldir}} option is shorthand for | |
1688 | @option{--with-mpc-lib=@/@var{mpcinstalldir}/lib} and | |
1689 | @option{--with-mpc-include=@/@var{mpcinstalldir}/include}. If these | |
1690 | shorthand assumptions are not correct, you can use the explicit | |
1691 | include and lib options directly. You might also need to ensure the | |
1692 | shared libraries can be found by the dynamic linker when building and | |
1693 | using GCC, for example by setting the runtime shared library path | |
1694 | variable (@env{LD_LIBRARY_PATH} on GNU/Linux and Solaris systems). | |
1695 | ||
1696 | These flags are applicable to the host platform only. When building | |
1697 | a cross compiler, they will not be used to configure target libraries. | |
1698 | ||
1699 | @item --with-isl=@var{pathname} | |
1700 | @itemx --with-isl-include=@var{pathname} | |
1701 | @itemx --with-isl-lib=@var{pathname} | |
1702 | @itemx --with-cloog=@var{pathname} | |
1703 | @itemx --with-cloog-include=@var{pathname} | |
1704 | @itemx --with-cloog-lib=@var{pathname} | |
1705 | If you do not have ISL and the CLooG | |
1706 | libraries installed in a standard location and you want to build GCC, | |
1707 | you can explicitly specify the directory where they are installed | |
1708 | (@samp{--with-isl=@/@var{islinstalldir}}, | |
1709 | @samp{--with-cloog=@/@var{clooginstalldir}}). The | |
1710 | @option{--with-isl=@/@var{islinstalldir}} option is shorthand for | |
1711 | @option{--with-isl-lib=@/@var{islinstalldir}/lib} and | |
1712 | @option{--with-isl-include=@/@var{islinstalldir}/include}. Likewise the | |
1713 | @option{--with-cloog=@/@var{clooginstalldir}} option is shorthand for | |
1714 | @option{--with-cloog-lib=@/@var{clooginstalldir}/lib} and | |
1715 | @option{--with-cloog-include=@/@var{clooginstalldir}/include}. If these | |
1716 | shorthand assumptions are not correct, you can use the explicit | |
1717 | include and lib options directly. | |
1718 | ||
1719 | These flags are applicable to the host platform only. When building | |
1720 | a cross compiler, they will not be used to configure target libraries. | |
1721 | ||
1722 | @item --with-host-libstdcxx=@var{linker-args} | |
1723 | If you are linking with a static copy of PPL, you can use this option | |
1724 | to specify how the linker should find the standard C++ library used | |
1725 | internally by PPL. Typical values of @var{linker-args} might be | |
1726 | @samp{-lstdc++} or @samp{-Wl,-Bstatic,-lstdc++,-Bdynamic -lm}. If you are | |
1727 | linking with a shared copy of PPL, you probably do not need this | |
1728 | option; shared library dependencies will cause the linker to search | |
1729 | for the standard C++ library automatically. | |
1730 | ||
1731 | @item --with-stage1-ldflags=@var{flags} | |
1732 | This option may be used to set linker flags to be used when linking | |
1733 | stage 1 of GCC. These are also used when linking GCC if configured with | |
1734 | @option{--disable-bootstrap}. By default no special flags are used. | |
1735 | ||
1736 | @item --with-stage1-libs=@var{libs} | |
1737 | This option may be used to set libraries to be used when linking stage 1 | |
1738 | of GCC. These are also used when linking GCC if configured with | |
1739 | @option{--disable-bootstrap}. The default is the argument to | |
1740 | @option{--with-host-libstdcxx}, if specified. | |
1741 | ||
1742 | @item --with-boot-ldflags=@var{flags} | |
1743 | This option may be used to set linker flags to be used when linking | |
1744 | stage 2 and later when bootstrapping GCC. If neither --with-boot-libs | |
1745 | nor --with-host-libstdcxx is set to a value, then the default is | |
1746 | @samp{-static-libstdc++ -static-libgcc}. | |
1747 | ||
1748 | @item --with-boot-libs=@var{libs} | |
1749 | This option may be used to set libraries to be used when linking stage 2 | |
1750 | and later when bootstrapping GCC. The default is the argument to | |
1751 | @option{--with-host-libstdcxx}, if specified. | |
1752 | ||
1753 | @item --with-debug-prefix-map=@var{map} | |
1754 | Convert source directory names using @option{-fdebug-prefix-map} when | |
1755 | building runtime libraries. @samp{@var{map}} is a space-separated | |
1756 | list of maps of the form @samp{@var{old}=@var{new}}. | |
1757 | ||
1758 | @item --enable-linker-build-id | |
1759 | Tells GCC to pass @option{--build-id} option to the linker for all final | |
1760 | links (links performed without the @option{-r} or @option{--relocatable} | |
1761 | option), if the linker supports it. If you specify | |
1762 | @option{--enable-linker-build-id}, but your linker does not | |
1763 | support @option{--build-id} option, a warning is issued and the | |
1764 | @option{--enable-linker-build-id} option is ignored. The default is off. | |
1765 | ||
1766 | @item --with-linker-hash-style=@var{choice} | |
1767 | Tells GCC to pass @option{--hash-style=@var{choice}} option to the | |
1768 | linker for all final links. @var{choice} can be one of | |
1769 | @samp{sysv}, @samp{gnu}, and @samp{both} where @samp{sysv} is the default. | |
1770 | ||
1771 | @item --enable-gnu-unique-object | |
1772 | @itemx --disable-gnu-unique-object | |
1773 | Tells GCC to use the gnu_unique_object relocation for C++ template | |
1774 | static data members and inline function local statics. Enabled by | |
1775 | default for a toolchain with an assembler that accepts it and | |
1776 | GLIBC 2.11 or above, otherwise disabled. | |
1777 | ||
1778 | @item --enable-lto | |
1779 | @itemx --disable-lto | |
1780 | Enable support for link-time optimization (LTO). This is enabled by | |
1781 | default, and may be disabled using @option{--disable-lto}. | |
1782 | ||
1783 | @item --with-plugin-ld=@var{pathname} | |
1784 | Enable an alternate linker to be used at link-time optimization (LTO) | |
1785 | link time when @option{-fuse-linker-plugin} is enabled. | |
1786 | This linker should have plugin support such as gold starting with | |
1787 | version 2.20 or GNU ld starting with version 2.21. | |
1788 | See @option{-fuse-linker-plugin} for details. | |
1789 | ||
1790 | @item --enable-canonical-system-headers | |
1791 | @itemx --disable-canonical-system-headers | |
1792 | Enable system header path canonicalization for @file{libcpp}. This can | |
1793 | produce shorter header file paths in diagnostics and dependency output | |
1794 | files, but these changed header paths may conflict with some compilation | |
1795 | environments. Enabled by default, and may be disabled using | |
1796 | @option{--disable-canonical-system-headers}. | |
1797 | ||
1798 | @item --with-glibc-version=@var{major}.@var{minor} | |
1799 | Tell GCC that when the GNU C Library (glibc) is used on the target it | |
1800 | will be version @var{major}.@var{minor} or later. Normally this can | |
1801 | be detected from the C library's header files, but this option may be | |
1802 | needed when bootstrapping a cross toolchain without the header files | |
1803 | available for building the initial bootstrap compiler. | |
1804 | ||
1805 | If GCC is configured with some multilibs that use glibc and some that | |
1806 | do not, this option applies only to the multilibs that use glibc. | |
1807 | However, such configurations may not work well as not all the relevant | |
1808 | configuration in GCC is on a per-multilib basis. | |
1809 | @end table | |
1810 | ||
1811 | @subheading Cross-Compiler-Specific Options | |
1812 | The following options only apply to building cross compilers. | |
1813 | ||
1814 | @table @code | |
1815 | @item --with-sysroot | |
1816 | @itemx --with-sysroot=@var{dir} | |
1817 | Tells GCC to consider @var{dir} as the root of a tree that contains | |
1818 | (a subset of) the root filesystem of the target operating system. | |
1819 | Target system headers, libraries and run-time object files will be | |
1820 | searched for in there. More specifically, this acts as if | |
1821 | @option{--sysroot=@var{dir}} was added to the default options of the built | |
1822 | compiler. The specified directory is not copied into the | |
1823 | install tree, unlike the options @option{--with-headers} and | |
1824 | @option{--with-libs} that this option obsoletes. The default value, | |
1825 | in case @option{--with-sysroot} is not given an argument, is | |
1826 | @option{$@{gcc_tooldir@}/sys-root}. If the specified directory is a | |
1827 | subdirectory of @option{$@{exec_prefix@}}, then it will be found relative to | |
1828 | the GCC binaries if the installation tree is moved. | |
1829 | ||
1830 | This option affects the system root for the compiler used to build | |
1831 | target libraries (which runs on the build system) and the compiler newly | |
1832 | installed with @code{make install}; it does not affect the compiler which is | |
1833 | used to build GCC itself. | |
1834 | ||
1835 | If you specify the @option{--with-native-system-header-dir=@var{dirname}} | |
1836 | option then the compiler will search that directory within @var{dirname} for | |
1837 | native system headers rather than the default @file{/usr/include}. | |
1838 | ||
1839 | @item --with-build-sysroot | |
1840 | @itemx --with-build-sysroot=@var{dir} | |
1841 | Tells GCC to consider @var{dir} as the system root (see | |
1842 | @option{--with-sysroot}) while building target libraries, instead of | |
1843 | the directory specified with @option{--with-sysroot}. This option is | |
1844 | only useful when you are already using @option{--with-sysroot}. You | |
1845 | can use @option{--with-build-sysroot} when you are configuring with | |
1846 | @option{--prefix} set to a directory that is different from the one in | |
1847 | which you are installing GCC and your target libraries. | |
1848 | ||
1849 | This option affects the system root for the compiler used to build | |
1850 | target libraries (which runs on the build system); it does not affect | |
1851 | the compiler which is used to build GCC itself. | |
1852 | ||
1853 | If you specify the @option{--with-native-system-header-dir=@var{dirname}} | |
1854 | option then the compiler will search that directory within @var{dirname} for | |
1855 | native system headers rather than the default @file{/usr/include}. | |
1856 | ||
1857 | @item --with-headers | |
1858 | @itemx --with-headers=@var{dir} | |
1859 | Deprecated in favor of @option{--with-sysroot}. | |
1860 | Specifies that target headers are available when building a cross compiler. | |
1861 | The @var{dir} argument specifies a directory which has the target include | |
1862 | files. These include files will be copied into the @file{gcc} install | |
1863 | directory. @emph{This option with the @var{dir} argument is required} when | |
1864 | building a cross compiler, if @file{@var{prefix}/@var{target}/sys-include} | |
1865 | doesn't pre-exist. If @file{@var{prefix}/@var{target}/sys-include} does | |
1866 | pre-exist, the @var{dir} argument may be omitted. @command{fixincludes} | |
1867 | will be run on these files to make them compatible with GCC@. | |
1868 | ||
1869 | @item --without-headers | |
1870 | Tells GCC not use any target headers from a libc when building a cross | |
1871 | compiler. When crossing to GNU/Linux, you need the headers so GCC | |
1872 | can build the exception handling for libgcc. | |
1873 | ||
1874 | @item --with-libs | |
1875 | @itemx --with-libs="@var{dir1} @var{dir2} @dots{} @var{dirN}" | |
1876 | Deprecated in favor of @option{--with-sysroot}. | |
1877 | Specifies a list of directories which contain the target runtime | |
1878 | libraries. These libraries will be copied into the @file{gcc} install | |
1879 | directory. If the directory list is omitted, this option has no | |
1880 | effect. | |
1881 | ||
1882 | @item --with-newlib | |
1883 | Specifies that @samp{newlib} is | |
1884 | being used as the target C library. This causes @code{__eprintf} to be | |
1885 | omitted from @file{libgcc.a} on the assumption that it will be provided by | |
1886 | @samp{newlib}. | |
1887 | ||
1888 | @item --with-avrlibc | |
1889 | Specifies that @samp{AVR-Libc} is | |
1890 | being used as the target C library. This causes float support | |
1891 | functions like @code{__addsf3} to be omitted from @file{libgcc.a} on | |
1892 | the assumption that it will be provided by @file{libm.a}. For more | |
1893 | technical details, cf. @uref{http://gcc.gnu.org/PR54461,,PR54461}. | |
1894 | This option is only supported for the AVR target. It is not supported for | |
1895 | RTEMS configurations, which currently use newlib. The option is | |
1896 | supported since version 4.7.2 and is the default in 4.8.0 and newer. | |
1897 | ||
1898 | @item --with-nds32-lib=@var{library} | |
1899 | Specifies that @var{library} setting is used for building @file{libgcc.a}. | |
1900 | Currently, the valid @var{library} is @samp{newlib} or @samp{mculib}. | |
1901 | This option is only supported for the NDS32 target. | |
1902 | ||
1903 | @item --with-build-time-tools=@var{dir} | |
1904 | Specifies where to find the set of target tools (assembler, linker, etc.) | |
1905 | that will be used while building GCC itself. This option can be useful | |
1906 | if the directory layouts are different between the system you are building | |
1907 | GCC on, and the system where you will deploy it. | |
1908 | ||
1909 | For example, on an @samp{ia64-hp-hpux} system, you may have the GNU | |
1910 | assembler and linker in @file{/usr/bin}, and the native tools in a | |
1911 | different path, and build a toolchain that expects to find the | |
1912 | native tools in @file{/usr/bin}. | |
1913 | ||
1914 | When you use this option, you should ensure that @var{dir} includes | |
1915 | @command{ar}, @command{as}, @command{ld}, @command{nm}, | |
1916 | @command{ranlib} and @command{strip} if necessary, and possibly | |
1917 | @command{objdump}. Otherwise, GCC may use an inconsistent set of | |
1918 | tools. | |
1919 | @end table | |
1920 | ||
1921 | @subheading Java-Specific Options | |
1922 | ||
1923 | The following option applies to the build of the Java front end. | |
1924 | ||
1925 | @table @code | |
1926 | @item --disable-libgcj | |
1927 | Specify that the run-time libraries | |
1928 | used by GCJ should not be built. This is useful in case you intend | |
1929 | to use GCJ with some other run-time, or you're going to install it | |
1930 | separately, or it just happens not to build on your particular | |
1931 | machine. In general, if the Java front end is enabled, the GCJ | |
1932 | libraries will be enabled too, unless they're known to not work on | |
1933 | the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you | |
1934 | may need to port it; in this case, before modifying the top-level | |
1935 | @file{configure.in} so that @samp{libgcj} is enabled by default on this platform, | |
1936 | you may use @option{--enable-libgcj} to override the default. | |
1937 | ||
1938 | @end table | |
1939 | ||
1940 | The following options apply to building @samp{libgcj}. | |
1941 | ||
1942 | @subsubheading General Options | |
1943 | ||
1944 | @table @code | |
1945 | @item --enable-java-maintainer-mode | |
1946 | By default the @samp{libjava} build will not attempt to compile the | |
1947 | @file{.java} source files to @file{.class}. Instead, it will use the | |
1948 | @file{.class} files from the source tree. If you use this option you | |
1949 | must have executables named @command{ecj1} and @command{gjavah} in your path | |
1950 | for use by the build. You must use this option if you intend to | |
1951 | modify any @file{.java} files in @file{libjava}. | |
1952 | ||
1953 | @item --with-java-home=@var{dirname} | |
1954 | This @samp{libjava} option overrides the default value of the | |
1955 | @samp{java.home} system property. It is also used to set | |
1956 | @samp{sun.boot.class.path} to @file{@var{dirname}/lib/rt.jar}. By | |
1957 | default @samp{java.home} is set to @file{@var{prefix}} and | |
1958 | @samp{sun.boot.class.path} to | |
1959 | @file{@var{datadir}/java/libgcj-@var{version}.jar}. | |
1960 | ||
1961 | @item --with-ecj-jar=@var{filename} | |
1962 | This option can be used to specify the location of an external jar | |
1963 | file containing the Eclipse Java compiler. A specially modified | |
1964 | version of this compiler is used by @command{gcj} to parse | |
1965 | @file{.java} source files. If this option is given, the | |
1966 | @samp{libjava} build will create and install an @file{ecj1} executable | |
1967 | which uses this jar file at runtime. | |
1968 | ||
1969 | If this option is not given, but an @file{ecj.jar} file is found in | |
1970 | the topmost source tree at configure time, then the @samp{libgcj} | |
1971 | build will create and install @file{ecj1}, and will also install the | |
1972 | discovered @file{ecj.jar} into a suitable place in the install tree. | |
1973 | ||
1974 | If @file{ecj1} is not installed, then the user will have to supply one | |
1975 | on his path in order for @command{gcj} to properly parse @file{.java} | |
1976 | source files. A suitable jar is available from | |
1977 | @uref{ftp://sourceware.org/pub/java/}. | |
1978 | ||
1979 | @item --disable-getenv-properties | |
1980 | Don't set system properties from @env{GCJ_PROPERTIES}. | |
1981 | ||
1982 | @item --enable-hash-synchronization | |
1983 | Use a global hash table for monitor locks. Ordinarily, | |
1984 | @samp{libgcj}'s @samp{configure} script automatically makes | |
1985 | the correct choice for this option for your platform. Only use | |
1986 | this if you know you need the library to be configured differently. | |
1987 | ||
1988 | @item --enable-interpreter | |
1989 | Enable the Java interpreter. The interpreter is automatically | |
1990 | enabled by default on all platforms that support it. This option | |
1991 | is really only useful if you want to disable the interpreter | |
1992 | (using @option{--disable-interpreter}). | |
1993 | ||
1994 | @item --disable-java-net | |
1995 | Disable java.net. This disables the native part of java.net only, | |
1996 | using non-functional stubs for native method implementations. | |
1997 | ||
1998 | @item --disable-jvmpi | |
1999 | Disable JVMPI support. | |
2000 | ||
2001 | @item --disable-libgcj-bc | |
2002 | Disable BC ABI compilation of certain parts of libgcj. By default, | |
2003 | some portions of libgcj are compiled with @option{-findirect-dispatch} | |
2004 | and @option{-fno-indirect-classes}, allowing them to be overridden at | |
2005 | run-time. | |
2006 | ||
2007 | If @option{--disable-libgcj-bc} is specified, libgcj is built without | |
2008 | these options. This allows the compile-time linker to resolve | |
2009 | dependencies when statically linking to libgcj. However it makes it | |
2010 | impossible to override the affected portions of libgcj at run-time. | |
2011 | ||
2012 | @item --enable-reduced-reflection | |
2013 | Build most of libgcj with @option{-freduced-reflection}. This reduces | |
2014 | the size of libgcj at the expense of not being able to do accurate | |
2015 | reflection on the classes it contains. This option is safe if you | |
2016 | know that code using libgcj will never use reflection on the standard | |
2017 | runtime classes in libgcj (including using serialization, RMI or CORBA). | |
2018 | ||
2019 | @item --with-ecos | |
2020 | Enable runtime eCos target support. | |
2021 | ||
2022 | @item --without-libffi | |
2023 | Don't use @samp{libffi}. This will disable the interpreter and JNI | |
2024 | support as well, as these require @samp{libffi} to work. | |
2025 | ||
2026 | @item --enable-libgcj-debug | |
2027 | Enable runtime debugging code. | |
2028 | ||
2029 | @item --enable-libgcj-multifile | |
2030 | If specified, causes all @file{.java} source files to be | |
2031 | compiled into @file{.class} files in one invocation of | |
2032 | @samp{gcj}. This can speed up build time, but is more | |
2033 | resource-intensive. If this option is unspecified or | |
2034 | disabled, @samp{gcj} is invoked once for each @file{.java} | |
2035 | file to compile into a @file{.class} file. | |
2036 | ||
2037 | @item --with-libiconv-prefix=DIR | |
2038 | Search for libiconv in @file{DIR/include} and @file{DIR/lib}. | |
2039 | ||
2040 | @item --enable-sjlj-exceptions | |
2041 | Force use of the @code{setjmp}/@code{longjmp}-based scheme for exceptions. | |
2042 | @samp{configure} ordinarily picks the correct value based on the platform. | |
2043 | Only use this option if you are sure you need a different setting. | |
2044 | ||
2045 | @item --with-system-zlib | |
2046 | Use installed @samp{zlib} rather than that included with GCC@. | |
2047 | ||
2048 | @item --with-win32-nlsapi=ansi, unicows or unicode | |
2049 | Indicates how MinGW @samp{libgcj} translates between UNICODE | |
2050 | characters and the Win32 API@. | |
2051 | ||
2052 | @item --enable-java-home | |
2053 | If enabled, this creates a JPackage compatible SDK environment during install. | |
2054 | Note that if --enable-java-home is used, --with-arch-directory=ARCH must also | |
2055 | be specified. | |
2056 | ||
2057 | @item --with-arch-directory=ARCH | |
2058 | Specifies the name to use for the @file{jre/lib/ARCH} directory in the SDK | |
2059 | environment created when --enable-java-home is passed. Typical names for this | |
2060 | directory include i386, amd64, ia64, etc. | |
2061 | ||
2062 | @item --with-os-directory=DIR | |
2063 | Specifies the OS directory for the SDK include directory. This is set to auto | |
2064 | detect, and is typically 'linux'. | |
2065 | ||
2066 | @item --with-origin-name=NAME | |
2067 | Specifies the JPackage origin name. This defaults to the 'gcj' in | |
2068 | java-1.5.0-gcj. | |
2069 | ||
2070 | @item --with-arch-suffix=SUFFIX | |
2071 | Specifies the suffix for the sdk directory. Defaults to the empty string. | |
2072 | Examples include '.x86_64' in 'java-1.5.0-gcj-1.5.0.0.x86_64'. | |
2073 | ||
2074 | @item --with-jvm-root-dir=DIR | |
2075 | Specifies where to install the SDK. Default is $(prefix)/lib/jvm. | |
2076 | ||
2077 | @item --with-jvm-jar-dir=DIR | |
2078 | Specifies where to install jars. Default is $(prefix)/lib/jvm-exports. | |
2079 | ||
2080 | @item --with-python-dir=DIR | |
2081 | Specifies where to install the Python modules used for aot-compile. DIR should | |
2082 | not include the prefix used in installation. For example, if the Python modules | |
2083 | are to be installed in /usr/lib/python2.5/site-packages, then | |
2084 | --with-python-dir=/lib/python2.5/site-packages should be passed. If this is | |
2085 | not specified, then the Python modules are installed in $(prefix)/share/python. | |
2086 | ||
2087 | @item --enable-aot-compile-rpm | |
2088 | Adds aot-compile-rpm to the list of installed scripts. | |
2089 | ||
2090 | @item --enable-browser-plugin | |
2091 | Build the gcjwebplugin web browser plugin. | |
2092 | ||
2093 | @item --enable-static-libjava | |
2094 | Build static libraries in libjava. The default is to only build shared | |
2095 | libraries. | |
2096 | ||
2097 | @table @code | |
2098 | @item ansi | |
2099 | Use the single-byte @code{char} and the Win32 A functions natively, | |
2100 | translating to and from UNICODE when using these functions. If | |
2101 | unspecified, this is the default. | |
2102 | ||
2103 | @item unicows | |
2104 | Use the @code{WCHAR} and Win32 W functions natively. Adds | |
2105 | @code{-lunicows} to @file{libgcj.spec} to link with @samp{libunicows}. | |
2106 | @file{unicows.dll} needs to be deployed on Microsoft Windows 9X machines | |
2107 | running built executables. @file{libunicows.a}, an open-source | |
2108 | import library around Microsoft's @code{unicows.dll}, is obtained from | |
2109 | @uref{http://libunicows.sourceforge.net/}, which also gives details | |
2110 | on getting @file{unicows.dll} from Microsoft. | |
2111 | ||
2112 | @item unicode | |
2113 | Use the @code{WCHAR} and Win32 W functions natively. Does @emph{not} | |
2114 | add @code{-lunicows} to @file{libgcj.spec}. The built executables will | |
2115 | only run on Microsoft Windows NT and above. | |
2116 | @end table | |
2117 | @end table | |
2118 | ||
2119 | @subsubheading AWT-Specific Options | |
2120 | ||
2121 | @table @code | |
2122 | @item --with-x | |
2123 | Use the X Window System. | |
2124 | ||
2125 | @item --enable-java-awt=PEER(S) | |
2126 | Specifies the AWT peer library or libraries to build alongside | |
2127 | @samp{libgcj}. If this option is unspecified or disabled, AWT | |
2128 | will be non-functional. Current valid values are @option{gtk} and | |
2129 | @option{xlib}. Multiple libraries should be separated by a | |
2130 | comma (i.e.@: @option{--enable-java-awt=gtk,xlib}). | |
2131 | ||
2132 | @item --enable-gtk-cairo | |
2133 | Build the cairo Graphics2D implementation on GTK@. | |
2134 | ||
2135 | @item --enable-java-gc=TYPE | |
2136 | Choose garbage collector. Defaults to @option{boehm} if unspecified. | |
2137 | ||
2138 | @item --disable-gtktest | |
2139 | Do not try to compile and run a test GTK+ program. | |
2140 | ||
2141 | @item --disable-glibtest | |
2142 | Do not try to compile and run a test GLIB program. | |
2143 | ||
2144 | @item --with-libart-prefix=PFX | |
2145 | Prefix where libart is installed (optional). | |
2146 | ||
2147 | @item --with-libart-exec-prefix=PFX | |
2148 | Exec prefix where libart is installed (optional). | |
2149 | ||
2150 | @item --disable-libarttest | |
2151 | Do not try to compile and run a test libart program. | |
2152 | ||
2153 | @end table | |
2154 | ||
2155 | @subsubheading Overriding @command{configure} test results | |
2156 | ||
2157 | Sometimes, it might be necessary to override the result of some | |
2158 | @command{configure} test, for example in order to ease porting to a new | |
2159 | system or work around a bug in a test. The toplevel @command{configure} | |
2160 | script provides three variables for this: | |
2161 | ||
2162 | @table @code | |
2163 | ||
2164 | @item build_configargs | |
2165 | @cindex @code{build_configargs} | |
2166 | The contents of this variable is passed to all build @command{configure} | |
2167 | scripts. | |
2168 | ||
2169 | @item host_configargs | |
2170 | @cindex @code{host_configargs} | |
2171 | The contents of this variable is passed to all host @command{configure} | |
2172 | scripts. | |
2173 | ||
2174 | @item target_configargs | |
2175 | @cindex @code{target_configargs} | |
2176 | The contents of this variable is passed to all target @command{configure} | |
2177 | scripts. | |
2178 | ||
2179 | @end table | |
2180 | ||
2181 | In order to avoid shell and @command{make} quoting issues for complex | |
2182 | overrides, you can pass a setting for @env{CONFIG_SITE} and set | |
2183 | variables in the site file. | |
2184 | ||
2185 | @html | |
2186 | <hr /> | |
2187 | <p> | |
2188 | @end html | |
2189 | @ifhtml | |
2190 | @uref{./index.html,,Return to the GCC Installation page} | |
2191 | @end ifhtml | |
2192 | @end ifset | |
2193 | ||
2194 | @c ***Building**************************************************************** | |
2195 | @ifnothtml | |
2196 | @comment node-name, next, previous, up | |
2197 | @node Building, Testing, Configuration, Installing GCC | |
2198 | @end ifnothtml | |
2199 | @ifset buildhtml | |
2200 | @ifnothtml | |
2201 | @chapter Building | |
2202 | @end ifnothtml | |
2203 | @cindex Installing GCC: Building | |
2204 | ||
2205 | Now that GCC is configured, you are ready to build the compiler and | |
2206 | runtime libraries. | |
2207 | ||
2208 | Some commands executed when making the compiler may fail (return a | |
2209 | nonzero status) and be ignored by @command{make}. These failures, which | |
2210 | are often due to files that were not found, are expected, and can safely | |
2211 | be ignored. | |
2212 | ||
2213 | It is normal to have compiler warnings when compiling certain files. | |
2214 | Unless you are a GCC developer, you can generally ignore these warnings | |
2215 | unless they cause compilation to fail. Developers should attempt to fix | |
2216 | any warnings encountered, however they can temporarily continue past | |
2217 | warnings-as-errors by specifying the configure flag | |
2218 | @option{--disable-werror}. | |
2219 | ||
2220 | On certain old systems, defining certain environment variables such as | |
2221 | @env{CC} can interfere with the functioning of @command{make}. | |
2222 | ||
2223 | If you encounter seemingly strange errors when trying to build the | |
2224 | compiler in a directory other than the source directory, it could be | |
2225 | because you have previously configured the compiler in the source | |
2226 | directory. Make sure you have done all the necessary preparations. | |
2227 | ||
2228 | If you build GCC on a BSD system using a directory stored in an old System | |
2229 | V file system, problems may occur in running @command{fixincludes} if the | |
2230 | System V file system doesn't support symbolic links. These problems | |
2231 | result in a failure to fix the declaration of @code{size_t} in | |
2232 | @file{sys/types.h}. If you find that @code{size_t} is a signed type and | |
2233 | that type mismatches occur, this could be the cause. | |
2234 | ||
2235 | The solution is not to use such a directory for building GCC@. | |
2236 | ||
2237 | Similarly, when building from SVN or snapshots, or if you modify | |
2238 | @file{*.l} files, you need the Flex lexical analyzer generator | |
2239 | installed. If you do not modify @file{*.l} files, releases contain | |
2240 | the Flex-generated files and you do not need Flex installed to build | |
2241 | them. There is still one Flex-based lexical analyzer (part of the | |
2242 | build machinery, not of GCC itself) that is used even if you only | |
2243 | build the C front end. | |
2244 | ||
2245 | When building from SVN or snapshots, or if you modify Texinfo | |
2246 | documentation, you need version 4.7 or later of Texinfo installed if you | |
2247 | want Info documentation to be regenerated. Releases contain Info | |
2248 | documentation pre-built for the unmodified documentation in the release. | |
2249 | ||
2250 | @section Building a native compiler | |
2251 | ||
2252 | For a native build, the default configuration is to perform | |
2253 | a 3-stage bootstrap of the compiler when @samp{make} is invoked. | |
2254 | This will build the entire GCC system and ensure that it compiles | |
2255 | itself correctly. It can be disabled with the @option{--disable-bootstrap} | |
2256 | parameter to @samp{configure}, but bootstrapping is suggested because | |
2257 | the compiler will be tested more completely and could also have | |
2258 | better performance. | |
2259 | ||
2260 | The bootstrapping process will complete the following steps: | |
2261 | ||
2262 | @itemize @bullet | |
2263 | @item | |
2264 | Build tools necessary to build the compiler. | |
2265 | ||
2266 | @item | |
2267 | Perform a 3-stage bootstrap of the compiler. This includes building | |
2268 | three times the target tools for use by the compiler such as binutils | |
2269 | (bfd, binutils, gas, gprof, ld, and opcodes) if they have been | |
2270 | individually linked or moved into the top level GCC source tree before | |
2271 | configuring. | |
2272 | ||
2273 | @item | |
2274 | Perform a comparison test of the stage2 and stage3 compilers. | |
2275 | ||
2276 | @item | |
2277 | Build runtime libraries using the stage3 compiler from the previous step. | |
2278 | ||
2279 | @end itemize | |
2280 | ||
2281 | If you are short on disk space you might consider @samp{make | |
2282 | bootstrap-lean} instead. The sequence of compilation is the | |
2283 | same described above, but object files from the stage1 and | |
2284 | stage2 of the 3-stage bootstrap of the compiler are deleted as | |
2285 | soon as they are no longer needed. | |
2286 | ||
2287 | If you wish to use non-default GCC flags when compiling the stage2 | |
2288 | and stage3 compilers, set @code{BOOT_CFLAGS} on the command line when | |
2289 | doing @samp{make}. For example, if you want to save additional space | |
2290 | during the bootstrap and in the final installation as well, you can | |
2291 | build the compiler binaries without debugging information as in the | |
2292 | following example. This will save roughly 40% of disk space both for | |
2293 | the bootstrap and the final installation. (Libraries will still contain | |
2294 | debugging information.) | |
2295 | ||
2296 | @smallexample | |
2297 | make BOOT_CFLAGS='-O' bootstrap | |
2298 | @end smallexample | |
2299 | ||
2300 | You can place non-default optimization flags into @code{BOOT_CFLAGS}; they | |
2301 | are less well tested here than the default of @samp{-g -O2}, but should | |
2302 | still work. In a few cases, you may find that you need to specify special | |
2303 | flags such as @option{-msoft-float} here to complete the bootstrap; or, | |
2304 | if the native compiler miscompiles the stage1 compiler, you may need | |
2305 | to work around this, by choosing @code{BOOT_CFLAGS} to avoid the parts | |
2306 | of the stage1 compiler that were miscompiled, or by using @samp{make | |
2307 | bootstrap4} to increase the number of stages of bootstrap. | |
2308 | ||
2309 | @code{BOOT_CFLAGS} does not apply to bootstrapped target libraries. | |
2310 | Since these are always compiled with the compiler currently being | |
2311 | bootstrapped, you can use @code{CFLAGS_FOR_TARGET} to modify their | |
2312 | compilation flags, as for non-bootstrapped target libraries. | |
2313 | Again, if the native compiler miscompiles the stage1 compiler, you may | |
2314 | need to work around this by avoiding non-working parts of the stage1 | |
2315 | compiler. Use @code{STAGE1_TFLAGS} to this end. | |
2316 | ||
2317 | If you used the flag @option{--enable-languages=@dots{}} to restrict | |
2318 | the compilers to be built, only those you've actually enabled will be | |
2319 | built. This will of course only build those runtime libraries, for | |
2320 | which the particular compiler has been built. Please note, | |
2321 | that re-defining @env{LANGUAGES} when calling @samp{make} | |
2322 | @strong{does not} work anymore! | |
2323 | ||
2324 | If the comparison of stage2 and stage3 fails, this normally indicates | |
2325 | that the stage2 compiler has compiled GCC incorrectly, and is therefore | |
2326 | a potentially serious bug which you should investigate and report. (On | |
2327 | a few systems, meaningful comparison of object files is impossible; they | |
2328 | always appear ``different''. If you encounter this problem, you will | |
2329 | need to disable comparison in the @file{Makefile}.) | |
2330 | ||
2331 | If you do not want to bootstrap your compiler, you can configure with | |
2332 | @option{--disable-bootstrap}. In particular cases, you may want to | |
2333 | bootstrap your compiler even if the target system is not the same as | |
2334 | the one you are building on: for example, you could build a | |
2335 | @code{powerpc-unknown-linux-gnu} toolchain on a | |
2336 | @code{powerpc64-unknown-linux-gnu} host. In this case, pass | |
2337 | @option{--enable-bootstrap} to the configure script. | |
2338 | ||
2339 | @code{BUILD_CONFIG} can be used to bring in additional customization | |
2340 | to the build. It can be set to a whitespace-separated list of names. | |
2341 | For each such @code{NAME}, top-level @file{config/@code{NAME}.mk} will | |
2342 | be included by the top-level @file{Makefile}, bringing in any settings | |
2343 | it contains. The default @code{BUILD_CONFIG} can be set using the | |
2344 | configure option @option{--with-build-config=@code{NAME}...}. Some | |
2345 | examples of supported build configurations are: | |
2346 | ||
2347 | @table @asis | |
2348 | @item @samp{bootstrap-O1} | |
2349 | Removes any @option{-O}-started option from @code{BOOT_CFLAGS}, and adds | |
2350 | @option{-O1} to it. @samp{BUILD_CONFIG=bootstrap-O1} is equivalent to | |
2351 | @samp{BOOT_CFLAGS='-g -O1'}. | |
2352 | ||
2353 | @item @samp{bootstrap-O3} | |
2354 | Analogous to @code{bootstrap-O1}. | |
2355 | ||
2356 | @item @samp{bootstrap-lto} | |
2357 | Enables Link-Time Optimization for host tools during bootstrapping. | |
2358 | @samp{BUILD_CONFIG=bootstrap-lto} is equivalent to adding | |
2359 | @option{-flto} to @samp{BOOT_CFLAGS}. | |
2360 | ||
2361 | @item @samp{bootstrap-debug} | |
2362 | Verifies that the compiler generates the same executable code, whether | |
2363 | or not it is asked to emit debug information. To this end, this | |
2364 | option builds stage2 host programs without debug information, and uses | |
2365 | @file{contrib/compare-debug} to compare them with the stripped stage3 | |
2366 | object files. If @code{BOOT_CFLAGS} is overridden so as to not enable | |
2367 | debug information, stage2 will have it, and stage3 won't. This option | |
2368 | is enabled by default when GCC bootstrapping is enabled, if | |
2369 | @code{strip} can turn object files compiled with and without debug | |
2370 | info into identical object files. In addition to better test | |
2371 | coverage, this option makes default bootstraps faster and leaner. | |
2372 | ||
2373 | @item @samp{bootstrap-debug-big} | |
2374 | Rather than comparing stripped object files, as in | |
2375 | @code{bootstrap-debug}, this option saves internal compiler dumps | |
2376 | during stage2 and stage3 and compares them as well, which helps catch | |
2377 | additional potential problems, but at a great cost in terms of disk | |
2378 | space. It can be specified in addition to @samp{bootstrap-debug}. | |
2379 | ||
2380 | @item @samp{bootstrap-debug-lean} | |
2381 | This option saves disk space compared with @code{bootstrap-debug-big}, | |
2382 | but at the expense of some recompilation. Instead of saving the dumps | |
2383 | of stage2 and stage3 until the final compare, it uses | |
2384 | @option{-fcompare-debug} to generate, compare and remove the dumps | |
2385 | during stage3, repeating the compilation that already took place in | |
2386 | stage2, whose dumps were not saved. | |
2387 | ||
2388 | @item @samp{bootstrap-debug-lib} | |
2389 | This option tests executable code invariance over debug information | |
2390 | generation on target libraries, just like @code{bootstrap-debug-lean} | |
2391 | tests it on host programs. It builds stage3 libraries with | |
2392 | @option{-fcompare-debug}, and it can be used along with any of the | |
2393 | @code{bootstrap-debug} options above. | |
2394 | ||
2395 | There aren't @code{-lean} or @code{-big} counterparts to this option | |
2396 | because most libraries are only build in stage3, so bootstrap compares | |
2397 | would not get significant coverage. Moreover, the few libraries built | |
2398 | in stage2 are used in stage3 host programs, so we wouldn't want to | |
2399 | compile stage2 libraries with different options for comparison purposes. | |
2400 | ||
2401 | @item @samp{bootstrap-debug-ckovw} | |
2402 | Arranges for error messages to be issued if the compiler built on any | |
2403 | stage is run without the option @option{-fcompare-debug}. This is | |
2404 | useful to verify the full @option{-fcompare-debug} testing coverage. It | |
2405 | must be used along with @code{bootstrap-debug-lean} and | |
2406 | @code{bootstrap-debug-lib}. | |
2407 | ||
2408 | @item @samp{bootstrap-time} | |
2409 | Arranges for the run time of each program started by the GCC driver, | |
2410 | built in any stage, to be logged to @file{time.log}, in the top level of | |
2411 | the build tree. | |
2412 | ||
2413 | @end table | |
2414 | ||
2415 | @section Building a cross compiler | |
2416 | ||
2417 | When building a cross compiler, it is not generally possible to do a | |
2418 | 3-stage bootstrap of the compiler. This makes for an interesting problem | |
2419 | as parts of GCC can only be built with GCC@. | |
2420 | ||
2421 | To build a cross compiler, we recommend first building and installing a | |
2422 | native compiler. You can then use the native GCC compiler to build the | |
2423 | cross compiler. The installed native compiler needs to be GCC version | |
2424 | 2.95 or later. | |
2425 | ||
2426 | If the cross compiler is to be built with support for the Java | |
2427 | programming language and the ability to compile .java source files is | |
2428 | desired, the installed native compiler used to build the cross | |
2429 | compiler needs to be the same GCC version as the cross compiler. In | |
2430 | addition the cross compiler needs to be configured with | |
2431 | @option{--with-ecj-jar=@dots{}}. | |
2432 | ||
2433 | Assuming you have already installed a native copy of GCC and configured | |
2434 | your cross compiler, issue the command @command{make}, which performs the | |
2435 | following steps: | |
2436 | ||
2437 | @itemize @bullet | |
2438 | @item | |
2439 | Build host tools necessary to build the compiler. | |
2440 | ||
2441 | @item | |
2442 | Build target tools for use by the compiler such as binutils (bfd, | |
2443 | binutils, gas, gprof, ld, and opcodes) | |
2444 | if they have been individually linked or moved into the top level GCC source | |
2445 | tree before configuring. | |
2446 | ||
2447 | @item | |
2448 | Build the compiler (single stage only). | |
2449 | ||
2450 | @item | |
2451 | Build runtime libraries using the compiler from the previous step. | |
2452 | @end itemize | |
2453 | ||
2454 | Note that if an error occurs in any step the make process will exit. | |
2455 | ||
2456 | If you are not building GNU binutils in the same source tree as GCC, | |
2457 | you will need a cross-assembler and cross-linker installed before | |
2458 | configuring GCC@. Put them in the directory | |
2459 | @file{@var{prefix}/@var{target}/bin}. Here is a table of the tools | |
2460 | you should put in this directory: | |
2461 | ||
2462 | @table @file | |
2463 | @item as | |
2464 | This should be the cross-assembler. | |
2465 | ||
2466 | @item ld | |
2467 | This should be the cross-linker. | |
2468 | ||
2469 | @item ar | |
2470 | This should be the cross-archiver: a program which can manipulate | |
2471 | archive files (linker libraries) in the target machine's format. | |
2472 | ||
2473 | @item ranlib | |
2474 | This should be a program to construct a symbol table in an archive file. | |
2475 | @end table | |
2476 | ||
2477 | The installation of GCC will find these programs in that directory, | |
2478 | and copy or link them to the proper place to for the cross-compiler to | |
2479 | find them when run later. | |
2480 | ||
2481 | The easiest way to provide these files is to build the Binutils package. | |
2482 | Configure it with the same @option{--host} and @option{--target} | |
2483 | options that you use for configuring GCC, then build and install | |
2484 | them. They install their executables automatically into the proper | |
2485 | directory. Alas, they do not support all the targets that GCC | |
2486 | supports. | |
2487 | ||
2488 | If you are not building a C library in the same source tree as GCC, | |
2489 | you should also provide the target libraries and headers before | |
2490 | configuring GCC, specifying the directories with | |
2491 | @option{--with-sysroot} or @option{--with-headers} and | |
2492 | @option{--with-libs}. Many targets also require ``start files'' such | |
2493 | as @file{crt0.o} and | |
2494 | @file{crtn.o} which are linked into each executable. There may be several | |
2495 | alternatives for @file{crt0.o}, for use with profiling or other | |
2496 | compilation options. Check your target's definition of | |
2497 | @code{STARTFILE_SPEC} to find out what start files it uses. | |
2498 | ||
2499 | @section Building in parallel | |
2500 | ||
2501 | GNU Make 3.80 and above, which is necessary to build GCC, support | |
2502 | building in parallel. To activate this, you can use @samp{make -j 2} | |
2503 | instead of @samp{make}. You can also specify a bigger number, and | |
2504 | in most cases using a value greater than the number of processors in | |
2505 | your machine will result in fewer and shorter I/O latency hits, thus | |
2506 | improving overall throughput; this is especially true for slow drives | |
2507 | and network filesystems. | |
2508 | ||
2509 | @section Building the Ada compiler | |
2510 | ||
2511 | In order to build GNAT, the Ada compiler, you need a working GNAT | |
2512 | compiler (GCC version 4.0 or later). | |
2513 | This includes GNAT tools such as @command{gnatmake} and | |
2514 | @command{gnatlink}, since the Ada front end is written in Ada and | |
2515 | uses some GNAT-specific extensions. | |
2516 | ||
2517 | In order to build a cross compiler, it is suggested to install | |
2518 | the new compiler as native first, and then use it to build the cross | |
2519 | compiler. | |
2520 | ||
2521 | @command{configure} does not test whether the GNAT installation works | |
2522 | and has a sufficiently recent version; if too old a GNAT version is | |
2523 | installed, the build will fail unless @option{--enable-languages} is | |
2524 | used to disable building the Ada front end. | |
2525 | ||
2526 | @env{ADA_INCLUDE_PATH} and @env{ADA_OBJECT_PATH} environment variables | |
2527 | must not be set when building the Ada compiler, the Ada tools, or the | |
2528 | Ada runtime libraries. You can check that your build environment is clean | |
2529 | by verifying that @samp{gnatls -v} lists only one explicit path in each | |
2530 | section. | |
2531 | ||
2532 | @section Building with profile feedback | |
2533 | ||
2534 | It is possible to use profile feedback to optimize the compiler itself. This | |
2535 | should result in a faster compiler binary. Experiments done on x86 using gcc | |
2536 | 3.3 showed approximately 7 percent speedup on compiling C programs. To | |
2537 | bootstrap the compiler with profile feedback, use @code{make profiledbootstrap}. | |
2538 | ||
2539 | When @samp{make profiledbootstrap} is run, it will first build a @code{stage1} | |
2540 | compiler. This compiler is used to build a @code{stageprofile} compiler | |
2541 | instrumented to collect execution counts of instruction and branch | |
2542 | probabilities. Then runtime libraries are compiled with profile collected. | |
2543 | Finally a @code{stagefeedback} compiler is built using the information collected. | |
2544 | ||
2545 | Unlike standard bootstrap, several additional restrictions apply. The | |
2546 | compiler used to build @code{stage1} needs to support a 64-bit integral type. | |
2547 | It is recommended to only use GCC for this. Also parallel make is currently | |
2548 | not supported since collisions in profile collecting may occur. | |
2549 | ||
2550 | @html | |
2551 | <hr /> | |
2552 | <p> | |
2553 | @end html | |
2554 | @ifhtml | |
2555 | @uref{./index.html,,Return to the GCC Installation page} | |
2556 | @end ifhtml | |
2557 | @end ifset | |
2558 | ||
2559 | @c ***Testing***************************************************************** | |
2560 | @ifnothtml | |
2561 | @comment node-name, next, previous, up | |
2562 | @node Testing, Final install, Building, Installing GCC | |
2563 | @end ifnothtml | |
2564 | @ifset testhtml | |
2565 | @ifnothtml | |
2566 | @chapter Installing GCC: Testing | |
2567 | @end ifnothtml | |
2568 | @cindex Testing | |
2569 | @cindex Installing GCC: Testing | |
2570 | @cindex Testsuite | |
2571 | ||
2572 | Before you install GCC, we encourage you to run the testsuites and to | |
2573 | compare your results with results from a similar configuration that have | |
2574 | been submitted to the | |
2575 | @uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}. | |
2576 | Some of these archived results are linked from the build status lists | |
2577 | at @uref{http://gcc.gnu.org/buildstat.html}, although not everyone who | |
2578 | reports a successful build runs the testsuites and submits the results. | |
2579 | This step is optional and may require you to download additional software, | |
2580 | but it can give you confidence in your new GCC installation or point out | |
2581 | problems before you install and start using your new GCC@. | |
2582 | ||
2583 | First, you must have @uref{download.html,,downloaded the testsuites}. | |
2584 | These are part of the full distribution, but if you downloaded the | |
2585 | ``core'' compiler plus any front ends, you must download the testsuites | |
2586 | separately. | |
2587 | ||
2588 | Second, you must have the testing tools installed. This includes | |
2589 | @uref{http://www.gnu.org/software/dejagnu/,,DejaGnu}, Tcl, and Expect; | |
2590 | the DejaGnu site has links to these. | |
2591 | ||
2592 | If the directories where @command{runtest} and @command{expect} were | |
2593 | installed are not in the @env{PATH}, you may need to set the following | |
2594 | environment variables appropriately, as in the following example (which | |
2595 | assumes that DejaGnu has been installed under @file{/usr/local}): | |
2596 | ||
2597 | @smallexample | |
2598 | TCL_LIBRARY = /usr/local/share/tcl8.0 | |
2599 | DEJAGNULIBS = /usr/local/share/dejagnu | |
2600 | @end smallexample | |
2601 | ||
2602 | (On systems such as Cygwin, these paths are required to be actual | |
2603 | paths, not mounts or links; presumably this is due to some lack of | |
2604 | portability in the DejaGnu code.) | |
2605 | ||
2606 | ||
2607 | Finally, you can run the testsuite (which may take a long time): | |
2608 | @smallexample | |
2609 | cd @var{objdir}; make -k check | |
2610 | @end smallexample | |
2611 | ||
2612 | This will test various components of GCC, such as compiler | |
2613 | front ends and runtime libraries. While running the testsuite, DejaGnu | |
2614 | might emit some harmless messages resembling | |
2615 | @samp{WARNING: Couldn't find the global config file.} or | |
2616 | @samp{WARNING: Couldn't find tool init file} that can be ignored. | |
2617 | ||
2618 | If you are testing a cross-compiler, you may want to run the testsuite | |
2619 | on a simulator as described at @uref{http://gcc.gnu.org/simtest-howto.html}. | |
2620 | ||
2621 | @section How can you run the testsuite on selected tests? | |
2622 | ||
2623 | In order to run sets of tests selectively, there are targets | |
2624 | @samp{make check-gcc} and language specific @samp{make check-c}, | |
2625 | @samp{make check-c++}, @samp{make check-fortran}, @samp{make check-java}, | |
2626 | @samp{make check-ada}, @samp{make check-objc}, @samp{make check-obj-c++}, | |
2627 | @samp{make check-lto} | |
2628 | in the @file{gcc} subdirectory of the object directory. You can also | |
2629 | just run @samp{make check} in a subdirectory of the object directory. | |
2630 | ||
2631 | ||
2632 | A more selective way to just run all @command{gcc} execute tests in the | |
2633 | testsuite is to use | |
2634 | ||
2635 | @smallexample | |
2636 | make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}" | |
2637 | @end smallexample | |
2638 | ||
2639 | Likewise, in order to run only the @command{g++} ``old-deja'' tests in | |
2640 | the testsuite with filenames matching @samp{9805*}, you would use | |
2641 | ||
2642 | @smallexample | |
2643 | make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}" | |
2644 | @end smallexample | |
2645 | ||
2646 | The @file{*.exp} files are located in the testsuite directories of the GCC | |
2647 | source, the most important ones being @file{compile.exp}, | |
2648 | @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}. | |
2649 | To get a list of the possible @file{*.exp} files, pipe the | |
2650 | output of @samp{make check} into a file and look at the | |
2651 | @samp{Running @dots{} .exp} lines. | |
2652 | ||
2653 | @section Passing options and running multiple testsuites | |
2654 | ||
2655 | You can pass multiple options to the testsuite using the | |
2656 | @samp{--target_board} option of DejaGNU, either passed as part of | |
2657 | @samp{RUNTESTFLAGS}, or directly to @command{runtest} if you prefer to | |
2658 | work outside the makefiles. For example, | |
2659 | ||
2660 | @smallexample | |
2661 | make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fmerge-constants" | |
2662 | @end smallexample | |
2663 | ||
2664 | will run the standard @command{g++} testsuites (``unix'' is the target name | |
2665 | for a standard native testsuite situation), passing | |
2666 | @samp{-O3 -fmerge-constants} to the compiler on every test, i.e., | |
2667 | slashes separate options. | |
2668 | ||
2669 | You can run the testsuites multiple times using combinations of options | |
2670 | with a syntax similar to the brace expansion of popular shells: | |
2671 | ||
2672 | @smallexample | |
2673 | @dots{}"--target_board=arm-sim\@{-mhard-float,-msoft-float\@}\@{-O1,-O2,-O3,\@}" | |
2674 | @end smallexample | |
2675 | ||
2676 | (Note the empty option caused by the trailing comma in the final group.) | |
2677 | The following will run each testsuite eight times using the @samp{arm-sim} | |
2678 | target, as if you had specified all possible combinations yourself: | |
2679 | ||
2680 | @smallexample | |
2681 | --target_board='arm-sim/-mhard-float/-O1 \ | |
2682 | arm-sim/-mhard-float/-O2 \ | |
2683 | arm-sim/-mhard-float/-O3 \ | |
2684 | arm-sim/-mhard-float \ | |
2685 | arm-sim/-msoft-float/-O1 \ | |
2686 | arm-sim/-msoft-float/-O2 \ | |
2687 | arm-sim/-msoft-float/-O3 \ | |
2688 | arm-sim/-msoft-float' | |
2689 | @end smallexample | |
2690 | ||
2691 | They can be combined as many times as you wish, in arbitrary ways. This | |
2692 | list: | |
2693 | ||
2694 | @smallexample | |
2695 | @dots{}"--target_board=unix/-Wextra\@{-O3,-fno-strength\@}\@{-fomit-frame,\@}" | |
2696 | @end smallexample | |
2697 | ||
2698 | will generate four combinations, all involving @samp{-Wextra}. | |
2699 | ||
2700 | The disadvantage to this method is that the testsuites are run in serial, | |
2701 | which is a waste on multiprocessor systems. For users with GNU Make and | |
2702 | a shell which performs brace expansion, you can run the testsuites in | |
2703 | parallel by having the shell perform the combinations and @command{make} | |
2704 | do the parallel runs. Instead of using @samp{--target_board}, use a | |
2705 | special makefile target: | |
2706 | ||
2707 | @smallexample | |
2708 | make -j@var{N} check-@var{testsuite}//@var{test-target}/@var{option1}/@var{option2}/@dots{} | |
2709 | @end smallexample | |
2710 | ||
2711 | For example, | |
2712 | ||
2713 | @smallexample | |
2714 | make -j3 check-gcc//sh-hms-sim/@{-m1,-m2,-m3,-m3e,-m4@}/@{,-nofpu@} | |
2715 | @end smallexample | |
2716 | ||
2717 | will run three concurrent ``make-gcc'' testsuites, eventually testing all | |
2718 | ten combinations as described above. Note that this is currently only | |
2719 | supported in the @file{gcc} subdirectory. (To see how this works, try | |
2720 | typing @command{echo} before the example given here.) | |
2721 | ||
2722 | ||
2723 | @section Additional testing for Java Class Libraries | |
2724 | ||
2725 | The Java runtime tests can be executed via @samp{make check} | |
2726 | in the @file{@var{target}/libjava/testsuite} directory in | |
2727 | the build tree. | |
2728 | ||
2729 | The @uref{http://sourceware.org/mauve/,,Mauve Project} provides | |
2730 | a suite of tests for the Java Class Libraries. This suite can be run | |
2731 | as part of libgcj testing by placing the Mauve tree within the libjava | |
2732 | testsuite at @file{libjava/testsuite/libjava.mauve/mauve}, or by | |
2733 | specifying the location of that tree when invoking @samp{make}, as in | |
2734 | @samp{make MAUVEDIR=~/mauve check}. | |
2735 | ||
2736 | @section How to interpret test results | |
2737 | ||
2738 | The result of running the testsuite are various @file{*.sum} and @file{*.log} | |
2739 | files in the testsuite subdirectories. The @file{*.log} files contain a | |
2740 | detailed log of the compiler invocations and the corresponding | |
2741 | results, the @file{*.sum} files summarize the results. These summaries | |
2742 | contain status codes for all tests: | |
2743 | ||
2744 | @itemize @bullet | |
2745 | @item | |
2746 | PASS: the test passed as expected | |
2747 | @item | |
2748 | XPASS: the test unexpectedly passed | |
2749 | @item | |
2750 | FAIL: the test unexpectedly failed | |
2751 | @item | |
2752 | XFAIL: the test failed as expected | |
2753 | @item | |
2754 | UNSUPPORTED: the test is not supported on this platform | |
2755 | @item | |
2756 | ERROR: the testsuite detected an error | |
2757 | @item | |
2758 | WARNING: the testsuite detected a possible problem | |
2759 | @end itemize | |
2760 | ||
2761 | It is normal for some tests to report unexpected failures. At the | |
2762 | current time the testing harness does not allow fine grained control | |
2763 | over whether or not a test is expected to fail. This problem should | |
2764 | be fixed in future releases. | |
2765 | ||
2766 | ||
2767 | @section Submitting test results | |
2768 | ||
2769 | If you want to report the results to the GCC project, use the | |
2770 | @file{contrib/test_summary} shell script. Start it in the @var{objdir} with | |
2771 | ||
2772 | @smallexample | |
2773 | @var{srcdir}/contrib/test_summary -p your_commentary.txt \ | |
2774 | -m gcc-testresults@@gcc.gnu.org |sh | |
2775 | @end smallexample | |
2776 | ||
2777 | This script uses the @command{Mail} program to send the results, so | |
2778 | make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is | |
2779 | prepended to the testsuite summary and should contain any special | |
2780 | remarks you have on your results or your build environment. Please | |
2781 | do not edit the testsuite result block or the subject line, as these | |
2782 | messages may be automatically processed. | |
2783 | ||
2784 | @html | |
2785 | <hr /> | |
2786 | <p> | |
2787 | @end html | |
2788 | @ifhtml | |
2789 | @uref{./index.html,,Return to the GCC Installation page} | |
2790 | @end ifhtml | |
2791 | @end ifset | |
2792 | ||
2793 | @c ***Final install*********************************************************** | |
2794 | @ifnothtml | |
2795 | @comment node-name, next, previous, up | |
2796 | @node Final install, , Testing, Installing GCC | |
2797 | @end ifnothtml | |
2798 | @ifset finalinstallhtml | |
2799 | @ifnothtml | |
2800 | @chapter Installing GCC: Final installation | |
2801 | @end ifnothtml | |
2802 | ||
2803 | Now that GCC has been built (and optionally tested), you can install it with | |
2804 | @smallexample | |
2805 | cd @var{objdir} && make install | |
2806 | @end smallexample | |
2807 | ||
2808 | We strongly recommend to install into a target directory where there is | |
2809 | no previous version of GCC present. Also, the GNAT runtime should not | |
2810 | be stripped, as this would break certain features of the debugger that | |
2811 | depend on this debugging information (catching Ada exceptions for | |
2812 | instance). | |
2813 | ||
2814 | That step completes the installation of GCC; user level binaries can | |
2815 | be found in @file{@var{prefix}/bin} where @var{prefix} is the value | |
2816 | you specified with the @option{--prefix} to configure (or | |
2817 | @file{/usr/local} by default). (If you specified @option{--bindir}, | |
2818 | that directory will be used instead; otherwise, if you specified | |
2819 | @option{--exec-prefix}, @file{@var{exec-prefix}/bin} will be used.) | |
2820 | Headers for the C++ and Java libraries are installed in | |
2821 | @file{@var{prefix}/include}; libraries in @file{@var{libdir}} | |
2822 | (normally @file{@var{prefix}/lib}); internal parts of the compiler in | |
2823 | @file{@var{libdir}/gcc} and @file{@var{libexecdir}/gcc}; documentation | |
2824 | in info format in @file{@var{infodir}} (normally | |
2825 | @file{@var{prefix}/info}). | |
2826 | ||
2827 | When installing cross-compilers, GCC's executables | |
2828 | are not only installed into @file{@var{bindir}}, that | |
2829 | is, @file{@var{exec-prefix}/bin}, but additionally into | |
2830 | @file{@var{exec-prefix}/@var{target-alias}/bin}, if that directory | |
2831 | exists. Typically, such @dfn{tooldirs} hold target-specific | |
2832 | binutils, including assembler and linker. | |
2833 | ||
2834 | Installation into a temporary staging area or into a @command{chroot} | |
2835 | jail can be achieved with the command | |
2836 | ||
2837 | @smallexample | |
2838 | make DESTDIR=@var{path-to-rootdir} install | |
2839 | @end smallexample | |
2840 | ||
2841 | @noindent | |
2842 | where @var{path-to-rootdir} is the absolute path of | |
2843 | a directory relative to which all installation paths will be | |
2844 | interpreted. Note that the directory specified by @code{DESTDIR} | |
2845 | need not exist yet; it will be created if necessary. | |
2846 | ||
2847 | There is a subtle point with tooldirs and @code{DESTDIR}: | |
2848 | If you relocate a cross-compiler installation with | |
2849 | e.g.@: @samp{DESTDIR=@var{rootdir}}, then the directory | |
2850 | @file{@var{rootdir}/@var{exec-prefix}/@var{target-alias}/bin} will | |
2851 | be filled with duplicated GCC executables only if it already exists, | |
2852 | it will not be created otherwise. This is regarded as a feature, | |
2853 | not as a bug, because it gives slightly more control to the packagers | |
2854 | using the @code{DESTDIR} feature. | |
2855 | ||
2856 | You can install stripped programs and libraries with | |
2857 | ||
2858 | @smallexample | |
2859 | make install-strip | |
2860 | @end smallexample | |
2861 | ||
2862 | If you are bootstrapping a released version of GCC then please | |
2863 | quickly review the build status page for your release, available from | |
2864 | @uref{http://gcc.gnu.org/buildstat.html}. | |
2865 | If your system is not listed for the version of GCC that you built, | |
2866 | send a note to | |
2867 | @email{gcc@@gcc.gnu.org} indicating | |
2868 | that you successfully built and installed GCC@. | |
2869 | Include the following information: | |
2870 | ||
2871 | @itemize @bullet | |
2872 | @item | |
2873 | Output from running @file{@var{srcdir}/config.guess}. Do not send | |
2874 | that file itself, just the one-line output from running it. | |
2875 | ||
2876 | @item | |
2877 | The output of @samp{gcc -v} for your newly installed @command{gcc}. | |
2878 | This tells us which version of GCC you built and the options you passed to | |
2879 | configure. | |
2880 | ||
2881 | @item | |
2882 | Whether you enabled all languages or a subset of them. If you used a | |
2883 | full distribution then this information is part of the configure | |
2884 | options in the output of @samp{gcc -v}, but if you downloaded the | |
2885 | ``core'' compiler plus additional front ends then it isn't apparent | |
2886 | which ones you built unless you tell us about it. | |
2887 | ||
2888 | @item | |
2889 | If the build was for GNU/Linux, also include: | |
2890 | @itemize @bullet | |
2891 | @item | |
2892 | The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3); | |
2893 | this information should be available from @file{/etc/issue}. | |
2894 | ||
2895 | @item | |
2896 | The version of the Linux kernel, available from @samp{uname --version} | |
2897 | or @samp{uname -a}. | |
2898 | ||
2899 | @item | |
2900 | The version of glibc you used; for RPM-based systems like Red Hat, | |
2901 | Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version, | |
2902 | and on systems like Debian and Progeny use @samp{dpkg -l libc6}. | |
2903 | @end itemize | |
2904 | For other systems, you can include similar information if you think it is | |
2905 | relevant. | |
2906 | ||
2907 | @item | |
2908 | Any other information that you think would be useful to people building | |
2909 | GCC on the same configuration. The new entry in the build status list | |
2910 | will include a link to the archived copy of your message. | |
2911 | @end itemize | |
2912 | ||
2913 | We'd also like to know if the | |
2914 | @ifnothtml | |
2915 | @ref{Specific, host/target specific installation notes} | |
2916 | @end ifnothtml | |
2917 | @ifhtml | |
2918 | @uref{specific.html,,host/target specific installation notes} | |
2919 | @end ifhtml | |
2920 | didn't include your host/target information or if that information is | |
2921 | incomplete or out of date. Send a note to | |
2922 | @email{gcc@@gcc.gnu.org} detailing how the information should be changed. | |
2923 | ||
2924 | If you find a bug, please report it following the | |
2925 | @uref{../bugs/,,bug reporting guidelines}. | |
2926 | ||
2927 | If you want to print the GCC manuals, do @samp{cd @var{objdir}; make | |
2928 | dvi}. You will need to have @command{texi2dvi} (version at least 4.7) | |
2929 | and @TeX{} installed. This creates a number of @file{.dvi} files in | |
2930 | subdirectories of @file{@var{objdir}}; these may be converted for | |
2931 | printing with programs such as @command{dvips}. Alternately, by using | |
2932 | @samp{make pdf} in place of @samp{make dvi}, you can create documentation | |
2933 | in the form of @file{.pdf} files; this requires @command{texi2pdf}, which | |
2934 | is included with Texinfo version 4.8 and later. You can also | |
2935 | @uref{http://shop.fsf.org/,,buy printed manuals from the | |
2936 | Free Software Foundation}, though such manuals may not be for the most | |
2937 | recent version of GCC@. | |
2938 | ||
2939 | If you would like to generate online HTML documentation, do @samp{cd | |
2940 | @var{objdir}; make html} and HTML will be generated for the gcc manuals in | |
2941 | @file{@var{objdir}/gcc/HTML}. | |
2942 | ||
2943 | @html | |
2944 | <hr /> | |
2945 | <p> | |
2946 | @end html | |
2947 | @ifhtml | |
2948 | @uref{./index.html,,Return to the GCC Installation page} | |
2949 | @end ifhtml | |
2950 | @end ifset | |
2951 | ||
2952 | @c ***Binaries**************************************************************** | |
2953 | @ifnothtml | |
2954 | @comment node-name, next, previous, up | |
2955 | @node Binaries, Specific, Installing GCC, Top | |
2956 | @end ifnothtml | |
2957 | @ifset binarieshtml | |
2958 | @ifnothtml | |
2959 | @chapter Installing GCC: Binaries | |
2960 | @end ifnothtml | |
2961 | @cindex Binaries | |
2962 | @cindex Installing GCC: Binaries | |
2963 | ||
2964 | We are often asked about pre-compiled versions of GCC@. While we cannot | |
2965 | provide these for all platforms, below you'll find links to binaries for | |
2966 | various platforms where creating them by yourself is not easy due to various | |
2967 | reasons. | |
2968 | ||
2969 | Please note that we did not create these binaries, nor do we | |
2970 | support them. If you have any problems installing them, please | |
2971 | contact their makers. | |
2972 | ||
2973 | @itemize | |
2974 | @item | |
2975 | AIX: | |
2976 | @itemize | |
2977 | @item | |
2978 | @uref{http://www.bullfreeware.com,,Bull's Freeware and Shareware Archive for AIX}; | |
2979 | ||
2980 | @item | |
2981 | @uref{http://pware.hvcc.edu,,Hudson Valley Community College Open Source Software for IBM System p}; | |
2982 | ||
2983 | @item | |
2984 | @uref{http://www.perzl.org/aix/,,AIX 5L and 6 Open Source Packages}. | |
2985 | @end itemize | |
2986 | ||
2987 | @item | |
2988 | DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}. | |
2989 | ||
2990 | @item | |
2991 | Renesas H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU | |
2992 | Development Tools for the Renesas H8/300[HS] Series}. | |
2993 | ||
2994 | @item | |
2995 | HP-UX: | |
2996 | @itemize | |
2997 | @item | |
2998 | @uref{http://hpux.connect.org.uk/,,HP-UX Porting Center}; | |
2999 | ||
3000 | @item | |
3001 | @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}. | |
3002 | @end itemize | |
3003 | ||
3004 | @item | |
3005 | @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO | |
3006 | OpenServer/Unixware}. | |
3007 | ||
3008 | @item | |
3009 | Solaris 2 (SPARC, Intel): | |
3010 | @itemize | |
3011 | @item | |
3012 | @uref{http://www.sunfreeware.com/,,Sunfreeware} | |
3013 | ||
3014 | @item | |
3015 | @uref{http://www.blastwave.org/,,Blastwave} | |
3016 | ||
3017 | @item | |
3018 | @uref{http://www.opencsw.org/,,OpenCSW} | |
3019 | ||
3020 | @item | |
3021 | @uref{http://jupiterrise.com/tgcware/,,TGCware} | |
3022 | @end itemize | |
3023 | ||
3024 | @item | |
3025 | Microsoft Windows: | |
3026 | @itemize | |
3027 | @item | |
3028 | The @uref{http://sourceware.org/cygwin/,,Cygwin} project; | |
3029 | @item | |
3030 | The @uref{http://www.mingw.org/,,MinGW} project. | |
3031 | @end itemize | |
3032 | ||
3033 | @item | |
3034 | @uref{ftp://ftp.thewrittenword.com/packages/by-name/,,The | |
3035 | Written Word} offers binaries for | |
3036 | AIX 4.3.3, 5.1 and 5.2, | |
3037 | GNU/Linux (i386), | |
3038 | HP-UX 10.20, 11.00, and 11.11, and | |
3039 | Solaris/SPARC 2.5.1, 2.6, 7, 8, 9 and 10. | |
3040 | ||
3041 | @item | |
3042 | @uref{http://www.openpkg.org/,,OpenPKG} offers binaries for quite a | |
3043 | number of platforms. | |
3044 | ||
3045 | @item | |
3046 | The @uref{http://gcc.gnu.org/wiki/GFortranBinaries,,GFortran Wiki} has | |
3047 | links to GNU Fortran binaries for several platforms. | |
3048 | @end itemize | |
3049 | ||
3050 | @html | |
3051 | <hr /> | |
3052 | <p> | |
3053 | @end html | |
3054 | @ifhtml | |
3055 | @uref{./index.html,,Return to the GCC Installation page} | |
3056 | @end ifhtml | |
3057 | @end ifset | |
3058 | ||
3059 | @c ***Specific**************************************************************** | |
3060 | @ifnothtml | |
3061 | @comment node-name, next, previous, up | |
3062 | @node Specific, Old, Binaries, Top | |
3063 | @end ifnothtml | |
3064 | @ifset specifichtml | |
3065 | @ifnothtml | |
3066 | @chapter Host/target specific installation notes for GCC | |
3067 | @end ifnothtml | |
3068 | @cindex Specific | |
3069 | @cindex Specific installation notes | |
3070 | @cindex Target specific installation | |
3071 | @cindex Host specific installation | |
3072 | @cindex Target specific installation notes | |
3073 | ||
3074 | Please read this document carefully @emph{before} installing the | |
3075 | GNU Compiler Collection on your machine. | |
3076 | ||
3077 | Note that this list of install notes is @emph{not} a list of supported | |
3078 | hosts or targets. Not all supported hosts and targets are listed | |
3079 | here, only the ones that require host-specific or target-specific | |
3080 | information have to. | |
3081 | ||
3082 | @ifhtml | |
3083 | @itemize | |
3084 | @item | |
3085 | @uref{#alpha-x-x,,alpha*-*-*} | |
3086 | @item | |
3087 | @uref{#alpha-dec-osf51,,alpha*-dec-osf5.1} | |
3088 | @item | |
3089 | @uref{#amd64-x-solaris210,,amd64-*-solaris2.10} | |
3090 | @item | |
3091 | @uref{#arm-x-eabi,,arm-*-eabi} | |
3092 | @item | |
3093 | @uref{#avr,,avr} | |
3094 | @item | |
3095 | @uref{#bfin,,Blackfin} | |
3096 | @item | |
3097 | @uref{#dos,,DOS} | |
3098 | @item | |
3099 | @uref{#x-x-freebsd,,*-*-freebsd*} | |
3100 | @item | |
3101 | @uref{#h8300-hms,,h8300-hms} | |
3102 | @item | |
3103 | @uref{#hppa-hp-hpux,,hppa*-hp-hpux*} | |
3104 | @item | |
3105 | @uref{#hppa-hp-hpux10,,hppa*-hp-hpux10} | |
3106 | @item | |
3107 | @uref{#hppa-hp-hpux11,,hppa*-hp-hpux11} | |
3108 | @item | |
3109 | @uref{#x-x-linux-gnu,,*-*-linux-gnu} | |
3110 | @item | |
3111 | @uref{#ix86-x-linux,,i?86-*-linux*} | |
3112 | @item | |
3113 | @uref{#ix86-x-solaris289,,i?86-*-solaris2.9} | |
3114 | @item | |
3115 | @uref{#ix86-x-solaris210,,i?86-*-solaris2.10} | |
3116 | @item | |
3117 | @uref{#ia64-x-linux,,ia64-*-linux} | |
3118 | @item | |
3119 | @uref{#ia64-x-hpux,,ia64-*-hpux*} | |
3120 | @item | |
3121 | @uref{#x-ibm-aix,,*-ibm-aix*} | |
3122 | @item | |
3123 | @uref{#iq2000-x-elf,,iq2000-*-elf} | |
3124 | @item | |
3125 | @uref{#lm32-x-elf,,lm32-*-elf} | |
3126 | @item | |
3127 | @uref{#lm32-x-uclinux,,lm32-*-uclinux} | |
3128 | @item | |
3129 | @uref{#m32c-x-elf,,m32c-*-elf} | |
3130 | @item | |
3131 | @uref{#m32r-x-elf,,m32r-*-elf} | |
3132 | @item | |
3133 | @uref{#m68k-x-x,,m68k-*-*} | |
3134 | @item | |
3135 | @uref{#m68k-uclinux,,m68k-uclinux} | |
3136 | @item | |
3137 | @uref{#mep-x-elf,,mep-*-elf} | |
3138 | @item | |
3139 | @uref{#microblaze-x-elf,,microblaze-*-elf} | |
3140 | @item | |
3141 | @uref{#mips-x-x,,mips-*-*} | |
3142 | @item | |
3143 | @uref{#mips-sgi-irix5,,mips-sgi-irix5} | |
3144 | @item | |
3145 | @uref{#mips-sgi-irix6,,mips-sgi-irix6} | |
3146 | @item | |
3147 | @uref{#powerpc-x-x,,powerpc*-*-*} | |
3148 | @item | |
3149 | @uref{#powerpc-x-darwin,,powerpc-*-darwin*} | |
3150 | @item | |
3151 | @uref{#powerpc-x-elf,,powerpc-*-elf} | |
3152 | @item | |
3153 | @uref{#powerpc-x-linux-gnu,,powerpc*-*-linux-gnu*} | |
3154 | @item | |
3155 | @uref{#powerpc-x-netbsd,,powerpc-*-netbsd*} | |
3156 | @item | |
3157 | @uref{#powerpc-x-eabisim,,powerpc-*-eabisim} | |
3158 | @item | |
3159 | @uref{#powerpc-x-eabi,,powerpc-*-eabi} | |
3160 | @item | |
3161 | @uref{#powerpcle-x-elf,,powerpcle-*-elf} | |
3162 | @item | |
3163 | @uref{#powerpcle-x-eabisim,,powerpcle-*-eabisim} | |
3164 | @item | |
3165 | @uref{#powerpcle-x-eabi,,powerpcle-*-eabi} | |
3166 | @item | |
3167 | @uref{#s390-x-linux,,s390-*-linux*} | |
3168 | @item | |
3169 | @uref{#s390x-x-linux,,s390x-*-linux*} | |
3170 | @item | |
3171 | @uref{#s390x-ibm-tpf,,s390x-ibm-tpf*} | |
3172 | @item | |
3173 | @uref{#x-x-solaris2,,*-*-solaris2*} | |
3174 | @item | |
3175 | @uref{#sparc-x-x,,sparc*-*-*} | |
3176 | @item | |
3177 | @uref{#sparc-sun-solaris2,,sparc-sun-solaris2*} | |
3178 | @item | |
3179 | @uref{#sparc-sun-solaris210,,sparc-sun-solaris2.10} | |
3180 | @item | |
3181 | @uref{#sparc-x-linux,,sparc-*-linux*} | |
3182 | @item | |
3183 | @uref{#sparc64-x-solaris2,,sparc64-*-solaris2*} | |
3184 | @item | |
3185 | @uref{#sparcv9-x-solaris2,,sparcv9-*-solaris2*} | |
3186 | @item | |
3187 | @uref{#c6x-x-x,,c6x-*-*} | |
3188 | @item | |
3189 | @uref{#tilegx-x-linux,,tilegx-*-linux*} | |
3190 | @item | |
3191 | @uref{#tilegxbe-x-linux,,tilegxbe-*-linux*} | |
3192 | @item | |
3193 | @uref{#tilepro-x-linux,,tilepro-*-linux*} | |
3194 | @item | |
3195 | @uref{#x-x-vxworks,,*-*-vxworks*} | |
3196 | @item | |
3197 | @uref{#x86-64-x-x,,x86_64-*-*, amd64-*-*} | |
3198 | @item | |
3199 | @uref{#x86-64-x-solaris210,,x86_64-*-solaris2.1[0-9]*} | |
3200 | @item | |
3201 | @uref{#xtensa-x-elf,,xtensa*-*-elf} | |
3202 | @item | |
3203 | @uref{#xtensa-x-linux,,xtensa*-*-linux*} | |
3204 | @item | |
3205 | @uref{#windows,,Microsoft Windows} | |
3206 | @item | |
3207 | @uref{#x-x-cygwin,,*-*-cygwin} | |
3208 | @item | |
3209 | @uref{#x-x-interix,,*-*-interix} | |
3210 | @item | |
3211 | @uref{#x-x-mingw32,,*-*-mingw32} | |
3212 | @item | |
3213 | @uref{#os2,,OS/2} | |
3214 | @item | |
3215 | @uref{#older,,Older systems} | |
3216 | @end itemize | |
3217 | ||
3218 | @itemize | |
3219 | @item | |
3220 | @uref{#elf,,all ELF targets} (SVR4, Solaris 2, etc.) | |
3221 | @end itemize | |
3222 | @end ifhtml | |
3223 | ||
3224 | ||
3225 | @html | |
3226 | <!-- -------- host/target specific issues start here ---------------- --> | |
3227 | <hr /> | |
3228 | @end html | |
3229 | @anchor{alpha-x-x} | |
3230 | @heading alpha*-*-* | |
3231 | This section contains general configuration information for all | |
3232 | alpha-based platforms using ELF (in particular, ignore this section for | |
3233 | DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this | |
3234 | section, please read all other sections that match your target. | |
3235 | ||
3236 | We require binutils 2.11.2 or newer. | |
3237 | Previous binutils releases had a number of problems with DWARF 2 | |
3238 | debugging information, not the least of which is incorrect linking of | |
3239 | shared libraries. | |
3240 | ||
3241 | @html | |
3242 | <hr /> | |
3243 | @end html | |
3244 | @anchor{alpha-dec-osf51} | |
3245 | @heading alpha*-dec-osf5.1 | |
3246 | Systems using processors that implement the DEC Alpha architecture and | |
3247 | are running the DEC/Compaq/HP Unix (DEC OSF/1, Digital UNIX, or Compaq/HP | |
3248 | Tru64 UNIX) operating system, for example the DEC Alpha AXP systems. | |
3249 | ||
3250 | Support for Tru64 UNIX V5.1 has been removed in GCC 4.8. As of GCC 4.6, | |
3251 | support for Tru64 UNIX V4.0 and V5.0 has been removed. As of GCC 3.2, | |
3252 | versions before @code{alpha*-dec-osf4} are no longer supported. (These | |
3253 | are the versions which identify themselves as DEC OSF/1.) | |
3254 | ||
3255 | @html | |
3256 | <hr /> | |
3257 | @end html | |
3258 | @anchor{amd64-x-solaris210} | |
3259 | @heading amd64-*-solaris2.1[0-9]* | |
3260 | This is a synonym for @samp{x86_64-*-solaris2.1[0-9]*}. | |
3261 | ||
3262 | @html | |
3263 | <hr /> | |
3264 | @end html | |
3265 | @anchor{arc-x-elf32} | |
3266 | @heading arc-*-elf32 | |
3267 | ||
3268 | Use @samp{configure --target=arc-elf32 --with-cpu=@var{cpu} --enable-languages="c,c++"} | |
3269 | to configure GCC, with @var{cpu} being one of @samp{arc600}, @samp{arc601}, | |
3270 | or @samp{arc700}@. | |
3271 | ||
3272 | @html | |
3273 | <hr /> | |
3274 | @end html | |
3275 | @anchor{arc-linux-uclibc} | |
3276 | @heading arc-linux-uclibc | |
3277 | ||
3278 | Use @samp{configure --target=arc-linux-uclibc --with-cpu=arc700 --enable-languages="c,c++"} to configure GCC@. | |
3279 | ||
3280 | @html | |
3281 | <hr /> | |
3282 | @end html | |
3283 | @anchor{arm-x-eabi} | |
3284 | @heading arm-*-eabi | |
3285 | ARM-family processors. Subtargets that use the ELF object format | |
3286 | require GNU binutils 2.13 or newer. Such subtargets include: | |
3287 | @code{arm-*-netbsdelf}, @code{arm-*-*linux-*} | |
3288 | and @code{arm-*-rtemseabi}. | |
3289 | ||
3290 | @html | |
3291 | <hr /> | |
3292 | @end html | |
3293 | @anchor{avr} | |
3294 | @heading avr | |
3295 | ATMEL AVR-family micro controllers. These are used in embedded | |
3296 | applications. There are no standard Unix configurations. | |
3297 | @ifnothtml | |
3298 | @xref{AVR Options,, AVR Options, gcc, Using the GNU Compiler | |
3299 | Collection (GCC)}, | |
3300 | @end ifnothtml | |
3301 | @ifhtml | |
3302 | See ``AVR Options'' in the main manual | |
3303 | @end ifhtml | |
3304 | for the list of supported MCU types. | |
3305 | ||
3306 | Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@. | |
3307 | ||
3308 | Further installation notes and other useful information about AVR tools | |
3309 | can also be obtained from: | |
3310 | ||
3311 | @itemize @bullet | |
3312 | @item | |
3313 | @uref{http://www.nongnu.org/avr/,,http://www.nongnu.org/avr/} | |
3314 | @item | |
3315 | @uref{http://www.amelek.gda.pl/avr/,,http://www.amelek.gda.pl/avr/} | |
3316 | @end itemize | |
3317 | ||
3318 | We @emph{strongly} recommend using binutils 2.13 or newer. | |
3319 | ||
3320 | The following error: | |
3321 | @smallexample | |
3322 | Error: register required | |
3323 | @end smallexample | |
3324 | ||
3325 | indicates that you should upgrade to a newer version of the binutils. | |
3326 | ||
3327 | @html | |
3328 | <hr /> | |
3329 | @end html | |
3330 | @anchor{bfin} | |
3331 | @heading Blackfin | |
3332 | The Blackfin processor, an Analog Devices DSP. | |
3333 | @ifnothtml | |
3334 | @xref{Blackfin Options,, Blackfin Options, gcc, Using the GNU Compiler | |
3335 | Collection (GCC)}, | |
3336 | @end ifnothtml | |
3337 | @ifhtml | |
3338 | See ``Blackfin Options'' in the main manual | |
3339 | @end ifhtml | |
3340 | ||
3341 | More information, and a version of binutils with support for this processor, | |
3342 | is available at @uref{http://blackfin.uclinux.org} | |
3343 | ||
3344 | @html | |
3345 | <hr /> | |
3346 | @end html | |
3347 | @anchor{cr16} | |
3348 | @heading CR16 | |
3349 | The CR16 CompactRISC architecture is a 16-bit architecture. This | |
3350 | architecture is used in embedded applications. | |
3351 | ||
3352 | @ifnothtml | |
3353 | @xref{CR16 Options,, CR16 Options, gcc, Using and Porting the GNU Compiler | |
3354 | Collection (GCC)}, | |
3355 | @end ifnothtml | |
3356 | ||
3357 | @ifhtml | |
3358 | See ``CR16 Options'' in the main manual for a list of CR16-specific options. | |
3359 | @end ifhtml | |
3360 | ||
3361 | Use @samp{configure --target=cr16-elf --enable-languages=c,c++} to configure | |
3362 | GCC@ for building a CR16 elf cross-compiler. | |
3363 | ||
3364 | Use @samp{configure --target=cr16-uclinux --enable-languages=c,c++} to | |
3365 | configure GCC@ for building a CR16 uclinux cross-compiler. | |
3366 | ||
3367 | @html | |
3368 | <hr /> | |
3369 | @end html | |
3370 | @anchor{cris} | |
3371 | @heading CRIS | |
3372 | CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip | |
3373 | series. These are used in embedded applications. | |
3374 | ||
3375 | @ifnothtml | |
3376 | @xref{CRIS Options,, CRIS Options, gcc, Using the GNU Compiler | |
3377 | Collection (GCC)}, | |
3378 | @end ifnothtml | |
3379 | @ifhtml | |
3380 | See ``CRIS Options'' in the main manual | |
3381 | @end ifhtml | |
3382 | for a list of CRIS-specific options. | |
3383 | ||
3384 | There are a few different CRIS targets: | |
3385 | @table @code | |
3386 | @item cris-axis-elf | |
3387 | Mainly for monolithic embedded systems. Includes a multilib for the | |
3388 | @samp{v10} core used in @samp{ETRAX 100 LX}. | |
3389 | @item cris-axis-linux-gnu | |
3390 | A GNU/Linux port for the CRIS architecture, currently targeting | |
3391 | @samp{ETRAX 100 LX} by default. | |
3392 | @end table | |
3393 | ||
3394 | For @code{cris-axis-elf} you need binutils 2.11 | |
3395 | or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer. | |
3396 | ||
3397 | Pre-packaged tools can be obtained from | |
3398 | @uref{ftp://ftp.axis.com/@/pub/@/axis/@/tools/@/cris/@/compiler-kit/}. More | |
3399 | information about this platform is available at | |
3400 | @uref{http://developer.axis.com/}. | |
3401 | ||
3402 | @html | |
3403 | <hr /> | |
3404 | @end html | |
3405 | @anchor{dos} | |
3406 | @heading DOS | |
3407 | Please have a look at the @uref{binaries.html,,binaries page}. | |
3408 | ||
3409 | You cannot install GCC by itself on MSDOS; it will not compile under | |
3410 | any MSDOS compiler except itself. You need to get the complete | |
3411 | compilation package DJGPP, which includes binaries as well as sources, | |
3412 | and includes all the necessary compilation tools and libraries. | |
3413 | ||
3414 | @html | |
3415 | <hr /> | |
3416 | @end html | |
3417 | @anchor{epiphany-x-elf} | |
3418 | @heading epiphany-*-elf | |
3419 | Adapteva Epiphany. | |
3420 | This configuration is intended for embedded systems. | |
3421 | ||
3422 | @html | |
3423 | <hr /> | |
3424 | @end html | |
3425 | @anchor{x-x-freebsd} | |
3426 | @heading *-*-freebsd* | |
3427 | Support for FreeBSD 1 was discontinued in GCC 3.2. Support for | |
3428 | FreeBSD 2 (and any mutant a.out variants of FreeBSD 3) was | |
3429 | discontinued in GCC 4.0. | |
3430 | ||
3431 | In order to better utilize FreeBSD base system functionality and match | |
3432 | the configuration of the system compiler, GCC 4.5 and above as well as | |
3433 | GCC 4.4 past 2010-06-20 leverage SSP support in libc (which is present | |
3434 | on FreeBSD 7 or later) and the use of @code{__cxa_atexit} by default | |
3435 | (on FreeBSD 6 or later). The use of @code{dl_iterate_phdr} inside | |
3436 | @file{libgcc_s.so.1} and boehm-gc (on FreeBSD 7 or later) is enabled | |
3437 | by GCC 4.5 and above. | |
3438 | ||
3439 | We support FreeBSD using the ELF file format with DWARF 2 debugging | |
3440 | for all CPU architectures. You may use @option{-gstabs} instead of | |
3441 | @option{-g}, if you really want the old debugging format. There are | |
3442 | no known issues with mixing object files and libraries with different | |
3443 | debugging formats. Otherwise, this release of GCC should now match | |
3444 | more of the configuration used in the stock FreeBSD configuration of | |
3445 | GCC@. In particular, @option{--enable-threads} is now configured by | |
3446 | default. However, as a general user, do not attempt to replace the | |
3447 | system compiler with this release. Known to bootstrap and check with | |
3448 | good results on FreeBSD 7.2-STABLE@. In the past, known to bootstrap | |
3449 | and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4, | |
3450 | 4.5, 4.8, 4.9 and 5-CURRENT@. | |
3451 | ||
3452 | The version of binutils installed in @file{/usr/bin} probably works | |
3453 | with this release of GCC@. Bootstrapping against the latest GNU | |
3454 | binutils and/or the version found in @file{/usr/ports/devel/binutils} has | |
3455 | been known to enable additional features and improve overall testsuite | |
3456 | results. However, it is currently known that boehm-gc (which itself | |
3457 | is required for java) may not configure properly on FreeBSD prior to | |
3458 | the FreeBSD 7.0 release with GNU binutils after 2.16.1. | |
3459 | ||
3460 | @html | |
3461 | <hr /> | |
3462 | @end html | |
3463 | @anchor{h8300-hms} | |
3464 | @heading h8300-hms | |
3465 | Renesas H8/300 series of processors. | |
3466 | ||
3467 | Please have a look at the @uref{binaries.html,,binaries page}. | |
3468 | ||
3469 | The calling convention and structure layout has changed in release 2.6. | |
3470 | All code must be recompiled. The calling convention now passes the | |
3471 | first three arguments in function calls in registers. Structures are no | |
3472 | longer a multiple of 2 bytes. | |
3473 | ||
3474 | @html | |
3475 | <hr /> | |
3476 | @end html | |
3477 | @anchor{hppa-hp-hpux} | |
3478 | @heading hppa*-hp-hpux* | |
3479 | Support for HP-UX version 9 and older was discontinued in GCC 3.4. | |
3480 | ||
3481 | We require using gas/binutils on all hppa platforms. Version 2.19 or | |
3482 | later is recommended. | |
3483 | ||
3484 | It may be helpful to configure GCC with the | |
3485 | @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and | |
3486 | @option{--with-as=@dots{}} options to ensure that GCC can find GAS@. | |
3487 | ||
3488 | The HP assembler should not be used with GCC. It is rarely tested and may | |
3489 | not work. It shouldn't be used with any languages other than C due to its | |
3490 | many limitations. | |
3491 | ||
3492 | Specifically, @option{-g} does not work (HP-UX uses a peculiar debugging | |
3493 | format which GCC does not know about). It also inserts timestamps | |
3494 | into each object file it creates, causing the 3-stage comparison test to | |
3495 | fail during a bootstrap. You should be able to continue by saying | |
3496 | @samp{make all-host all-target} after getting the failure from @samp{make}. | |
3497 | ||
3498 | Various GCC features are not supported. For example, it does not support weak | |
3499 | symbols or alias definitions. As a result, explicit template instantiations | |
3500 | are required when using C++. This makes it difficult if not impossible to | |
3501 | build many C++ applications. | |
3502 | ||
3503 | There are two default scheduling models for instructions. These are | |
3504 | PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc | |
3505 | architecture specified for the target machine when configuring. | |
3506 | PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when | |
3507 | the target is a @samp{hppa1*} machine. | |
3508 | ||
3509 | The PROCESSOR_8000 model is not well suited to older processors. Thus, | |
3510 | it is important to completely specify the machine architecture when | |
3511 | configuring if you want a model other than PROCESSOR_8000. The macro | |
3512 | TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different | |
3513 | default scheduling model is desired. | |
3514 | ||
3515 | As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10 | |
3516 | through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later. | |
3517 | This namespace change might cause problems when bootstrapping with | |
3518 | an earlier version of GCC or the HP compiler as essentially the same | |
3519 | namespace is required for an entire build. This problem can be avoided | |
3520 | in a number of ways. With HP cc, @env{UNIX_STD} can be set to @samp{95} | |
3521 | or @samp{98}. Another way is to add an appropriate set of predefines | |
3522 | to @env{CC}. The description for the @option{munix=} option contains | |
3523 | a list of the predefines used with each standard. | |
3524 | ||
3525 | More specific information to @samp{hppa*-hp-hpux*} targets follows. | |
3526 | ||
3527 | @html | |
3528 | <hr /> | |
3529 | @end html | |
3530 | @anchor{hppa-hp-hpux10} | |
3531 | @heading hppa*-hp-hpux10 | |
3532 | For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch | |
3533 | @code{PHCO_19798} from HP@. | |
3534 | ||
3535 | The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces are | |
3536 | used for one-only code and data. This resolves many of the previous | |
3537 | problems in using C++ on this target. However, the ABI is not compatible | |
3538 | with the one implemented under HP-UX 11 using secondary definitions. | |
3539 | ||
3540 | @html | |
3541 | <hr /> | |
3542 | @end html | |
3543 | @anchor{hppa-hp-hpux11} | |
3544 | @heading hppa*-hp-hpux11 | |
3545 | GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot | |
3546 | be used to compile GCC 3.0 and up. | |
3547 | ||
3548 | The libffi and libjava libraries haven't been ported to 64-bit HP-UX@ | |
3549 | and don't build. | |
3550 | ||
3551 | Refer to @uref{binaries.html,,binaries} for information about obtaining | |
3552 | precompiled GCC binaries for HP-UX@. Precompiled binaries must be obtained | |
3553 | to build the Ada language as it can't be bootstrapped using C@. Ada is | |
3554 | only available for the 32-bit PA-RISC runtime. | |
3555 | ||
3556 | Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The | |
3557 | bundled compiler supports only traditional C; you will need either HP's | |
3558 | unbundled compiler, or a binary distribution of GCC@. | |
3559 | ||
3560 | It is possible to build GCC 3.3 starting with the bundled HP compiler, | |
3561 | but the process requires several steps. GCC 3.3 can then be used to | |
3562 | build later versions. The fastjar program contains ISO C code and | |
3563 | can't be built with the HP bundled compiler. This problem can be | |
3564 | avoided by not building the Java language. For example, use the | |
3565 | @option{--enable-languages="c,c++,f77,objc"} option in your configure | |
3566 | command. | |
3567 | ||
3568 | There are several possible approaches to building the distribution. | |
3569 | Binutils can be built first using the HP tools. Then, the GCC | |
3570 | distribution can be built. The second approach is to build GCC | |
3571 | first using the HP tools, then build binutils, then rebuild GCC@. | |
3572 | There have been problems with various binary distributions, so it | |
3573 | is best not to start from a binary distribution. | |
3574 | ||
3575 | On 64-bit capable systems, there are two distinct targets. Different | |
3576 | installation prefixes must be used if both are to be installed on | |
3577 | the same system. The @samp{hppa[1-2]*-hp-hpux11*} target generates code | |
3578 | for the 32-bit PA-RISC runtime architecture and uses the HP linker. | |
3579 | The @samp{hppa64-hp-hpux11*} target generates 64-bit code for the | |
3580 | PA-RISC 2.0 architecture. | |
3581 | ||
3582 | The script config.guess now selects the target type based on the compiler | |
3583 | detected during configuration. You must define @env{PATH} or @env{CC} so | |
3584 | that configure finds an appropriate compiler for the initial bootstrap. | |
3585 | When @env{CC} is used, the definition should contain the options that are | |
3586 | needed whenever @env{CC} is used. | |
3587 | ||
3588 | Specifically, options that determine the runtime architecture must be | |
3589 | in @env{CC} to correctly select the target for the build. It is also | |
3590 | convenient to place many other compiler options in @env{CC}. For example, | |
3591 | @env{CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"} | |
3592 | can be used to bootstrap the GCC 3.3 branch with the HP compiler in | |
3593 | 64-bit K&R/bundled mode. The @option{+DA2.0W} option will result in | |
3594 | the automatic selection of the @samp{hppa64-hp-hpux11*} target. The | |
3595 | macro definition table of cpp needs to be increased for a successful | |
3596 | build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to | |
3597 | be defined when building with the bundled compiler, or when using the | |
3598 | @option{-Ac} option. These defines aren't necessary with @option{-Ae}. | |
3599 | ||
3600 | It is best to explicitly configure the @samp{hppa64-hp-hpux11*} target | |
3601 | with the @option{--with-ld=@dots{}} option. This overrides the standard | |
3602 | search for ld. The two linkers supported on this target require different | |
3603 | commands. The default linker is determined during configuration. As a | |
3604 | result, it's not possible to switch linkers in the middle of a GCC build. | |
3605 | This has been reported to sometimes occur in unified builds of binutils | |
3606 | and GCC@. | |
3607 | ||
3608 | A recent linker patch must be installed for the correct operation of | |
3609 | GCC 3.3 and later. @code{PHSS_26559} and @code{PHSS_24304} are the | |
3610 | oldest linker patches that are known to work. They are for HP-UX | |
3611 | 11.00 and 11.11, respectively. @code{PHSS_24303}, the companion to | |
3612 | @code{PHSS_24304}, might be usable but it hasn't been tested. These | |
3613 | patches have been superseded. Consult the HP patch database to obtain | |
3614 | the currently recommended linker patch for your system. | |
3615 | ||
3616 | The patches are necessary for the support of weak symbols on the | |
3617 | 32-bit port, and for the running of initializers and finalizers. Weak | |
3618 | symbols are implemented using SOM secondary definition symbols. Prior | |
3619 | to HP-UX 11, there are bugs in the linker support for secondary symbols. | |
3620 | The patches correct a problem of linker core dumps creating shared | |
3621 | libraries containing secondary symbols, as well as various other | |
3622 | linking issues involving secondary symbols. | |
3623 | ||
3624 | GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to | |
3625 | run initializers and finalizers on the 64-bit port. The 32-bit port | |
3626 | uses the linker @option{+init} and @option{+fini} options for the same | |
3627 | purpose. The patches correct various problems with the +init/+fini | |
3628 | options, including program core dumps. Binutils 2.14 corrects a | |
3629 | problem on the 64-bit port resulting from HP's non-standard use of | |
3630 | the .init and .fini sections for array initializers and finalizers. | |
3631 | ||
3632 | Although the HP and GNU linkers are both supported for the | |
3633 | @samp{hppa64-hp-hpux11*} target, it is strongly recommended that the | |
3634 | HP linker be used for link editing on this target. | |
3635 | ||
3636 | At this time, the GNU linker does not support the creation of long | |
3637 | branch stubs. As a result, it can't successfully link binaries | |
3638 | containing branch offsets larger than 8 megabytes. In addition, | |
3639 | there are problems linking shared libraries, linking executables | |
3640 | with @option{-static}, and with dwarf2 unwind and exception support. | |
3641 | It also doesn't provide stubs for internal calls to global functions | |
3642 | in shared libraries, so these calls can't be overloaded. | |
3643 | ||
3644 | The HP dynamic loader does not support GNU symbol versioning, so symbol | |
3645 | versioning is not supported. It may be necessary to disable symbol | |
3646 | versioning with @option{--disable-symvers} when using GNU ld. | |
3647 | ||
3648 | POSIX threads are the default. The optional DCE thread library is not | |
3649 | supported, so @option{--enable-threads=dce} does not work. | |
3650 | ||
3651 | @html | |
3652 | <hr /> | |
3653 | @end html | |
3654 | @anchor{x-x-linux-gnu} | |
3655 | @heading *-*-linux-gnu | |
3656 | Versions of libstdc++-v3 starting with 3.2.1 require bug fixes present | |
3657 | in glibc 2.2.5 and later. More information is available in the | |
3658 | libstdc++-v3 documentation. | |
3659 | ||
3660 | @html | |
3661 | <hr /> | |
3662 | @end html | |
3663 | @anchor{ix86-x-linux} | |
3664 | @heading i?86-*-linux* | |
3665 | As of GCC 3.3, binutils 2.13.1 or later is required for this platform. | |
3666 | See @uref{http://gcc.gnu.org/PR10877,,bug 10877} for more information. | |
3667 | ||
3668 | If you receive Signal 11 errors when building on GNU/Linux, then it is | |
3669 | possible you have a hardware problem. Further information on this can be | |
3670 | found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}. | |
3671 | ||
3672 | @html | |
3673 | <hr /> | |
3674 | @end html | |
3675 | @anchor{ix86-x-solaris29} | |
3676 | @heading i?86-*-solaris2.9 | |
3677 | The Sun assembler in Solaris 9 has several bugs and limitations. | |
3678 | While GCC works around them, several features are missing, so it is | |
3679 | @c FIXME: which ones? | |
3680 | recommended to use the GNU assembler instead. There is no bundled | |
3681 | version, but the current version, from GNU binutils 2.22, is known to | |
3682 | work. | |
3683 | ||
3684 | Solaris@tie{}2/x86 doesn't support the execution of SSE/SSE2 instructions | |
3685 | before Solaris@tie{}9 4/04, even if the CPU supports them. Programs will | |
3686 | receive @code{SIGILL} if they try. The fix is available both in | |
3687 | Solaris@tie{}9 Update@tie{}6 and kernel patch 112234-12 or newer. To | |
3688 | avoid this problem, | |
3689 | @option{-march} defaults to @samp{pentiumpro} on Solaris 9. If | |
3690 | you have the patch installed, you can configure GCC with an appropriate | |
3691 | @option{--with-arch} option, but need GNU @command{as} for SSE2 support. | |
3692 | ||
3693 | @html | |
3694 | <hr /> | |
3695 | @end html | |
3696 | @anchor{ix86-x-solaris210} | |
3697 | @heading i?86-*-solaris2.10 | |
3698 | Use this for Solaris 10 or later on x86 and x86-64 systems. Starting | |
3699 | with GCC 4.7, there is also a 64-bit @samp{amd64-*-solaris2.1[0-9]*} or | |
3700 | @samp{x86_64-*-solaris2.1[0-9]*} configuration that corresponds to | |
3701 | @samp{sparcv9-sun-solaris2*}. | |
3702 | ||
3703 | It is recommended that you configure GCC to use the GNU assembler, in | |
3704 | @file{/usr/sfw/bin/gas}. The versions included in Solaris 10, from GNU | |
3705 | binutils 2.15, and Solaris 11, from GNU binutils 2.19, work fine, | |
3706 | although the current version, from GNU binutils | |
3707 | 2.22, is known to work, too. Recent versions of the Sun assembler in | |
3708 | @file{/usr/ccs/bin/as} work almost as well, though. | |
3709 | @c FIXME: as patch requirements? | |
3710 | ||
3711 | For linking, the Sun linker, is preferred. If you want to use the GNU | |
3712 | linker instead, which is available in @file{/usr/sfw/bin/gld}, note that | |
3713 | due to a packaging bug the version in Solaris 10, from GNU binutils | |
3714 | 2.15, cannot be used, while the version in Solaris 11, from GNU binutils | |
3715 | 2.19, works, as does the latest version, from GNU binutils 2.22. | |
3716 | ||
3717 | To use GNU @command{as}, configure with the options | |
3718 | @option{--with-gnu-as --with-as=@//usr/@/sfw/@/bin/@/gas}. It may be necessary | |
3719 | to configure with @option{--without-gnu-ld --with-ld=@//usr/@/ccs/@/bin/@/ld} to | |
3720 | guarantee use of Sun @command{ld}. | |
3721 | @c FIXME: why --without-gnu-ld --with-ld? | |
3722 | ||
3723 | @html | |
3724 | <hr /> | |
3725 | @end html | |
3726 | @anchor{ia64-x-linux} | |
3727 | @heading ia64-*-linux | |
3728 | IA-64 processor (also known as IPF, or Itanium Processor Family) | |
3729 | running GNU/Linux. | |
3730 | ||
3731 | If you are using the installed system libunwind library with | |
3732 | @option{--with-system-libunwind}, then you must use libunwind 0.98 or | |
3733 | later. | |
3734 | ||
3735 | None of the following versions of GCC has an ABI that is compatible | |
3736 | with any of the other versions in this list, with the exception that | |
3737 | Red Hat 2.96 and Trillian 000171 are compatible with each other: | |
3738 | 3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717. | |
3739 | This primarily affects C++ programs and programs that create shared libraries. | |
3740 | GCC 3.1 or later is recommended for compiling linux, the kernel. | |
3741 | As of version 3.1 GCC is believed to be fully ABI compliant, and hence no | |
3742 | more major ABI changes are expected. | |
3743 | ||
3744 | @html | |
3745 | <hr /> | |
3746 | @end html | |
3747 | @anchor{ia64-x-hpux} | |
3748 | @heading ia64-*-hpux* | |
3749 | Building GCC on this target requires the GNU Assembler. The bundled HP | |
3750 | assembler will not work. To prevent GCC from using the wrong assembler, | |
3751 | the option @option{--with-gnu-as} may be necessary. | |
3752 | ||
3753 | The GCC libunwind library has not been ported to HPUX@. This means that for | |
3754 | GCC versions 3.2.3 and earlier, @option{--enable-libunwind-exceptions} | |
3755 | is required to build GCC@. For GCC 3.3 and later, this is the default. | |
3756 | For gcc 3.4.3 and later, @option{--enable-libunwind-exceptions} is | |
3757 | removed and the system libunwind library will always be used. | |
3758 | ||
3759 | @html | |
3760 | <hr /> | |
3761 | @end html | |
3762 | @anchor{aarch64-x-x} | |
3763 | @heading aarch64*-*-* | |
3764 | Pre 2.24 binutils does not have support for selecting -mabi and does not | |
3765 | support ILP32. If GCC 4.9 or later is built with pre 2.24, GCC will not | |
3766 | support option -mabi=ilp32. | |
3767 | ||
3768 | @html | |
3769 | <hr /> | |
3770 | <!-- rs6000-ibm-aix*, powerpc-ibm-aix* --> | |
3771 | @end html | |
3772 | @anchor{x-ibm-aix} | |
3773 | @heading *-ibm-aix* | |
3774 | Support for AIX version 3 and older was discontinued in GCC 3.4. | |
3775 | Support for AIX version 4.2 and older was discontinued in GCC 4.5. | |
3776 | ||
3777 | ``out of memory'' bootstrap failures may indicate a problem with | |
3778 | process resource limits (ulimit). Hard limits are configured in the | |
3779 | @file{/etc/security/limits} system configuration file. | |
3780 | ||
3781 | GCC can bootstrap with recent versions of IBM XLC, but bootstrapping | |
3782 | with an earlier release of GCC is recommended. Bootstrapping with XLC | |
3783 | requires a larger data segment, which can be enabled through the | |
3784 | @var{LDR_CNTRL} environment variable, e.g., | |
3785 | ||
3786 | @smallexample | |
3787 | % LDR_CNTRL=MAXDATA=0x50000000 | |
3788 | % export LDR_CNTRL | |
3789 | @end smallexample | |
3790 | ||
3791 | One can start with a pre-compiled version of GCC to build from | |
3792 | sources. One may delete GCC's ``fixed'' header files when starting | |
3793 | with a version of GCC built for an earlier release of AIX. | |
3794 | ||
3795 | To speed up the configuration phases of bootstrapping and installing GCC, | |
3796 | one may use GNU Bash instead of AIX @command{/bin/sh}, e.g., | |
3797 | ||
3798 | @smallexample | |
3799 | % CONFIG_SHELL=/opt/freeware/bin/bash | |
3800 | % export CONFIG_SHELL | |
3801 | @end smallexample | |
3802 | ||
3803 | and then proceed as described in @uref{build.html,,the build | |
3804 | instructions}, where we strongly recommend specifying an absolute path | |
3805 | to invoke @var{srcdir}/configure. | |
3806 | ||
3807 | Because GCC on AIX is built as a 32-bit executable by default, | |
3808 | (although it can generate 64-bit programs) the GMP and MPFR libraries | |
3809 | required by gfortran must be 32-bit libraries. Building GMP and MPFR | |
3810 | as static archive libraries works better than shared libraries. | |
3811 | ||
3812 | Errors involving @code{alloca} when building GCC generally are due | |
3813 | to an incorrect definition of @code{CC} in the Makefile or mixing files | |
3814 | compiled with the native C compiler and GCC@. During the stage1 phase of | |
3815 | the build, the native AIX compiler @strong{must} be invoked as @command{cc} | |
3816 | (not @command{xlc}). Once @command{configure} has been informed of | |
3817 | @command{xlc}, one needs to use @samp{make distclean} to remove the | |
3818 | configure cache files and ensure that @env{CC} environment variable | |
3819 | does not provide a definition that will confuse @command{configure}. | |
3820 | If this error occurs during stage2 or later, then the problem most likely | |
3821 | is the version of Make (see above). | |
3822 | ||
3823 | The native @command{as} and @command{ld} are recommended for | |
3824 | bootstrapping on AIX@. The GNU Assembler, GNU Linker, and GNU | |
3825 | Binutils version 2.20 is the minimum level that supports bootstrap on | |
3826 | AIX 5@. The GNU Assembler has not been updated to support AIX 6@ or | |
3827 | AIX 7. The native AIX tools do interoperate with GCC@. | |
3828 | ||
3829 | AIX 5.3 TL10, AIX 6.1 TL05 and AIX 7.1 TL00 introduced an AIX | |
3830 | assembler change that sometimes produces corrupt assembly files | |
3831 | causing AIX linker errors. The bug breaks GCC bootstrap on AIX and | |
3832 | can cause compilation failures with existing GCC installations. An | |
3833 | AIX iFix for AIX 5.3 is available (APAR IZ98385 for AIX 5.3 TL10, APAR | |
3834 | IZ98477 for AIX 5.3 TL11 and IZ98134 for AIX 5.3 TL12). AIX 5.3 TL11 SP8, | |
3835 | AIX 5.3 TL12 SP5, AIX 6.1 TL04 SP11, AIX 6.1 TL05 SP7, AIX 6.1 TL06 SP6, | |
3836 | AIX 6.1 TL07 and AIX 7.1 TL01 should include the fix. | |
3837 | ||
3838 | Building @file{libstdc++.a} requires a fix for an AIX Assembler bug | |
3839 | APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a | |
3840 | fix for another AIX Assembler bug and a co-dependent AIX Archiver fix | |
3841 | referenced as APAR IY53606 (AIX 5.2) or as APAR IY54774 (AIX 5.1) | |
3842 | ||
3843 | @samp{libstdc++} in GCC 3.4 increments the major version number of the | |
3844 | shared object and GCC installation places the @file{libstdc++.a} | |
3845 | shared library in a common location which will overwrite the and GCC | |
3846 | 3.3 version of the shared library. Applications either need to be | |
3847 | re-linked against the new shared library or the GCC 3.1 and GCC 3.3 | |
3848 | versions of the @samp{libstdc++} shared object needs to be available | |
3849 | to the AIX runtime loader. The GCC 3.1 @samp{libstdc++.so.4}, if | |
3850 | present, and GCC 3.3 @samp{libstdc++.so.5} shared objects can be | |
3851 | installed for runtime dynamic loading using the following steps to set | |
3852 | the @samp{F_LOADONLY} flag in the shared object for @emph{each} | |
3853 | multilib @file{libstdc++.a} installed: | |
3854 | ||
3855 | Extract the shared objects from the currently installed | |
3856 | @file{libstdc++.a} archive: | |
3857 | @smallexample | |
3858 | % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5 | |
3859 | @end smallexample | |
3860 | ||
3861 | Enable the @samp{F_LOADONLY} flag so that the shared object will be | |
3862 | available for runtime dynamic loading, but not linking: | |
3863 | @smallexample | |
3864 | % strip -e libstdc++.so.4 libstdc++.so.5 | |
3865 | @end smallexample | |
3866 | ||
3867 | Archive the runtime-only shared object in the GCC 3.4 | |
3868 | @file{libstdc++.a} archive: | |
3869 | @smallexample | |
3870 | % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5 | |
3871 | @end smallexample | |
3872 | ||
3873 | Linking executables and shared libraries may produce warnings of | |
3874 | duplicate symbols. The assembly files generated by GCC for AIX always | |
3875 | have included multiple symbol definitions for certain global variable | |
3876 | and function declarations in the original program. The warnings should | |
3877 | not prevent the linker from producing a correct library or runnable | |
3878 | executable. | |
3879 | ||
3880 | AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and | |
3881 | 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1 | |
3882 | to parse archive libraries did not handle the new format correctly. | |
3883 | These routines are used by GCC and result in error messages during | |
3884 | linking such as ``not a COFF file''. The version of the routines shipped | |
3885 | with AIX 4.3.1 should work for a 32-bit environment. The @option{-g} | |
3886 | option of the archive command may be used to create archives of 32-bit | |
3887 | objects using the original ``small format''. A correct version of the | |
3888 | routines is shipped with AIX 4.3.2 and above. | |
3889 | ||
3890 | Some versions of the AIX binder (linker) can fail with a relocation | |
3891 | overflow severe error when the @option{-bbigtoc} option is used to link | |
3892 | GCC-produced object files into an executable that overflows the TOC@. A fix | |
3893 | for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is | |
3894 | available from IBM Customer Support and from its | |
3895 | @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com} | |
3896 | website as PTF U455193. | |
3897 | ||
3898 | The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core | |
3899 | with a segmentation fault when invoked by any version of GCC@. A fix for | |
3900 | APAR IX87327 is available from IBM Customer Support and from its | |
3901 | @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com} | |
3902 | website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above. | |
3903 | ||
3904 | The initial assembler shipped with AIX 4.3.0 generates incorrect object | |
3905 | files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS | |
3906 | TO ASSEMBLE/BIND) is available from IBM Customer Support and from its | |
3907 | @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com} | |
3908 | website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above. | |
3909 | ||
3910 | AIX provides National Language Support (NLS)@. Compilers and assemblers | |
3911 | use NLS to support locale-specific representations of various data | |
3912 | formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for | |
3913 | separating decimal fractions). There have been problems reported where | |
3914 | GCC does not produce the same floating-point formats that the assembler | |
3915 | expects. If one encounters this problem, set the @env{LANG} | |
3916 | environment variable to @samp{C} or @samp{En_US}. | |
3917 | ||
3918 | A default can be specified with the @option{-mcpu=@var{cpu_type}} | |
3919 | switch and using the configure option @option{--with-cpu-@var{cpu_type}}. | |
3920 | ||
3921 | @html | |
3922 | <hr /> | |
3923 | @end html | |
3924 | @anchor{iq2000-x-elf} | |
3925 | @heading iq2000-*-elf | |
3926 | Vitesse IQ2000 processors. These are used in embedded | |
3927 | applications. There are no standard Unix configurations. | |
3928 | ||
3929 | @html | |
3930 | <hr /> | |
3931 | @end html | |
3932 | @anchor{lm32-x-elf} | |
3933 | @heading lm32-*-elf | |
3934 | Lattice Mico32 processor. | |
3935 | This configuration is intended for embedded systems. | |
3936 | ||
3937 | @html | |
3938 | <hr /> | |
3939 | @end html | |
3940 | @anchor{lm32-x-uclinux} | |
3941 | @heading lm32-*-uclinux | |
3942 | Lattice Mico32 processor. | |
3943 | This configuration is intended for embedded systems running uClinux. | |
3944 | ||
3945 | @html | |
3946 | <hr /> | |
3947 | @end html | |
3948 | @anchor{m32c-x-elf} | |
3949 | @heading m32c-*-elf | |
3950 | Renesas M32C processor. | |
3951 | This configuration is intended for embedded systems. | |
3952 | ||
3953 | @html | |
3954 | <hr /> | |
3955 | @end html | |
3956 | @anchor{m32r-x-elf} | |
3957 | @heading m32r-*-elf | |
3958 | Renesas M32R processor. | |
3959 | This configuration is intended for embedded systems. | |
3960 | ||
3961 | @html | |
3962 | <hr /> | |
3963 | @end html | |
3964 | @anchor{m68k-x-x} | |
3965 | @heading m68k-*-* | |
3966 | By default, | |
3967 | @samp{m68k-*-elf*}, @samp{m68k-*-rtems}, @samp{m68k-*-uclinux} and | |
3968 | @samp{m68k-*-linux} | |
3969 | build libraries for both M680x0 and ColdFire processors. If you only | |
3970 | need the M680x0 libraries, you can omit the ColdFire ones by passing | |
3971 | @option{--with-arch=m68k} to @command{configure}. Alternatively, you | |
3972 | can omit the M680x0 libraries by passing @option{--with-arch=cf} to | |
3973 | @command{configure}. These targets default to 5206 or 5475 code as | |
3974 | appropriate for the target system when | |
3975 | configured with @option{--with-arch=cf} and 68020 code otherwise. | |
3976 | ||
3977 | The @samp{m68k-*-netbsd} and | |
3978 | @samp{m68k-*-openbsd} targets also support the @option{--with-arch} | |
3979 | option. They will generate ColdFire CFV4e code when configured with | |
3980 | @option{--with-arch=cf} and 68020 code otherwise. | |
3981 | ||
3982 | You can override the default processors listed above by configuring | |
3983 | with @option{--with-cpu=@var{target}}. This @var{target} can either | |
3984 | be a @option{-mcpu} argument or one of the following values: | |
3985 | @samp{m68000}, @samp{m68010}, @samp{m68020}, @samp{m68030}, | |
3986 | @samp{m68040}, @samp{m68060}, @samp{m68020-40} and @samp{m68020-60}. | |
3987 | ||
3988 | GCC requires at least binutils version 2.17 on these targets. | |
3989 | ||
3990 | @html | |
3991 | <hr /> | |
3992 | @end html | |
3993 | @anchor{m68k-x-uclinux} | |
3994 | @heading m68k-*-uclinux | |
3995 | GCC 4.3 changed the uClinux configuration so that it uses the | |
3996 | @samp{m68k-linux-gnu} ABI rather than the @samp{m68k-elf} ABI. | |
3997 | It also added improved support for C++ and flat shared libraries, | |
3998 | both of which were ABI changes. | |
3999 | ||
4000 | @html | |
4001 | <hr /> | |
4002 | @end html | |
4003 | @anchor{mep-x-elf} | |
4004 | @heading mep-*-elf | |
4005 | Toshiba Media embedded Processor. | |
4006 | This configuration is intended for embedded systems. | |
4007 | ||
4008 | @html | |
4009 | <hr /> | |
4010 | @end html | |
4011 | @anchor{microblaze-x-elf} | |
4012 | @heading microblaze-*-elf | |
4013 | Xilinx MicroBlaze processor. | |
4014 | This configuration is intended for embedded systems. | |
4015 | ||
4016 | @html | |
4017 | <hr /> | |
4018 | @end html | |
4019 | @anchor{mips-x-x} | |
4020 | @heading mips-*-* | |
4021 | If on a MIPS system you get an error message saying ``does not have gp | |
4022 | sections for all it's [sic] sectons [sic]'', don't worry about it. This | |
4023 | happens whenever you use GAS with the MIPS linker, but there is not | |
4024 | really anything wrong, and it is okay to use the output file. You can | |
4025 | stop such warnings by installing the GNU linker. | |
4026 | ||
4027 | It would be nice to extend GAS to produce the gp tables, but they are | |
4028 | optional, and there should not be a warning about their absence. | |
4029 | ||
4030 | The libstdc++ atomic locking routines for MIPS targets requires MIPS II | |
4031 | and later. A patch went in just after the GCC 3.3 release to | |
4032 | make @samp{mips*-*-*} use the generic implementation instead. You can also | |
4033 | configure for @samp{mipsel-elf} as a workaround. The | |
4034 | @samp{mips*-*-linux*} target continues to use the MIPS II routines. More | |
4035 | work on this is expected in future releases. | |
4036 | ||
4037 | @c If you make --with-llsc the default for another target, please also | |
4038 | @c update the description of the --with-llsc option. | |
4039 | ||
4040 | The built-in @code{__sync_*} functions are available on MIPS II and | |
4041 | later systems and others that support the @samp{ll}, @samp{sc} and | |
4042 | @samp{sync} instructions. This can be overridden by passing | |
4043 | @option{--with-llsc} or @option{--without-llsc} when configuring GCC. | |
4044 | Since the Linux kernel emulates these instructions if they are | |
4045 | missing, the default for @samp{mips*-*-linux*} targets is | |
4046 | @option{--with-llsc}. The @option{--with-llsc} and | |
4047 | @option{--without-llsc} configure options may be overridden at compile | |
4048 | time by passing the @option{-mllsc} or @option{-mno-llsc} options to | |
4049 | the compiler. | |
4050 | ||
4051 | MIPS systems check for division by zero (unless | |
4052 | @option{-mno-check-zero-division} is passed to the compiler) by | |
4053 | generating either a conditional trap or a break instruction. Using | |
4054 | trap results in smaller code, but is only supported on MIPS II and | |
4055 | later. Also, some versions of the Linux kernel have a bug that | |
4056 | prevents trap from generating the proper signal (@code{SIGFPE}). To enable | |
4057 | the use of break, use the @option{--with-divide=breaks} | |
4058 | @command{configure} option when configuring GCC@. The default is to | |
4059 | use traps on systems that support them. | |
4060 | ||
4061 | The assembler from GNU binutils 2.17 and earlier has a bug in the way | |
4062 | it sorts relocations for REL targets (o32, o64, EABI). This can cause | |
4063 | bad code to be generated for simple C++ programs. Also the linker | |
4064 | from GNU binutils versions prior to 2.17 has a bug which causes the | |
4065 | runtime linker stubs in very large programs, like @file{libgcj.so}, to | |
4066 | be incorrectly generated. GNU Binutils 2.18 and later (and snapshots | |
4067 | made after Nov. 9, 2006) should be free from both of these problems. | |
4068 | ||
4069 | @html | |
4070 | <hr /> | |
4071 | @end html | |
4072 | @anchor{mips-sgi-irix5} | |
4073 | @heading mips-sgi-irix5 | |
4074 | Support for IRIX 5 has been removed in GCC 4.6. | |
4075 | ||
4076 | @html | |
4077 | <hr /> | |
4078 | @end html | |
4079 | @anchor{mips-sgi-irix6} | |
4080 | @heading mips-sgi-irix6 | |
4081 | Support for IRIX 6.5 has been removed in GCC 4.8. Support for IRIX 6 | |
4082 | releases before 6.5 has been removed in GCC 4.6, as well as support for | |
4083 | the O32 ABI. | |
4084 | ||
4085 | @html | |
4086 | <hr /> | |
4087 | @end html | |
4088 | @anchor{moxie-x-elf} | |
4089 | @heading moxie-*-elf | |
4090 | The moxie processor. | |
4091 | ||
4092 | @html | |
4093 | <hr /> | |
4094 | @end html | |
4095 | @anchor{msp430-x-elf} | |
4096 | @heading msp430-*-elf | |
4097 | TI MSP430 processor. | |
4098 | This configuration is intended for embedded systems. | |
4099 | ||
4100 | @html | |
4101 | <hr /> | |
4102 | @end html | |
4103 | @anchor{powerpc-x-x} | |
4104 | @heading powerpc-*-* | |
4105 | You can specify a default version for the @option{-mcpu=@var{cpu_type}} | |
4106 | switch by using the configure option @option{--with-cpu-@var{cpu_type}}. | |
4107 | ||
4108 | You will need | |
4109 | @uref{ftp://ftp.kernel.org/pub/linux/devel/binutils,,binutils 2.15} | |
4110 | or newer for a working GCC@. | |
4111 | ||
4112 | @html | |
4113 | <hr /> | |
4114 | @end html | |
4115 | @anchor{powerpc-x-darwin} | |
4116 | @heading powerpc-*-darwin* | |
4117 | PowerPC running Darwin (Mac OS X kernel). | |
4118 | ||
4119 | Pre-installed versions of Mac OS X may not include any developer tools, | |
4120 | meaning that you will not be able to build GCC from source. Tool | |
4121 | binaries are available at | |
4122 | @uref{http://opensource.apple.com/}. | |
4123 | ||
4124 | This version of GCC requires at least cctools-590.36. The | |
4125 | cctools-590.36 package referenced from | |
4126 | @uref{http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html} will not work | |
4127 | on systems older than 10.3.9 (aka darwin7.9.0). | |
4128 | ||
4129 | @html | |
4130 | <hr /> | |
4131 | @end html | |
4132 | @anchor{powerpc-x-elf} | |
4133 | @heading powerpc-*-elf | |
4134 | PowerPC system in big endian mode, running System V.4. | |
4135 | ||
4136 | @html | |
4137 | <hr /> | |
4138 | @end html | |
4139 | @anchor{powerpc-x-linux-gnu} | |
4140 | @heading powerpc*-*-linux-gnu* | |
4141 | PowerPC system in big endian mode running Linux. | |
4142 | ||
4143 | @html | |
4144 | <hr /> | |
4145 | @end html | |
4146 | @anchor{powerpc-x-netbsd} | |
4147 | @heading powerpc-*-netbsd* | |
4148 | PowerPC system in big endian mode running NetBSD@. | |
4149 | ||
4150 | @html | |
4151 | <hr /> | |
4152 | @end html | |
4153 | @anchor{powerpc-x-eabisim} | |
4154 | @heading powerpc-*-eabisim | |
4155 | Embedded PowerPC system in big endian mode for use in running under the | |
4156 | PSIM simulator. | |
4157 | ||
4158 | @html | |
4159 | <hr /> | |
4160 | @end html | |
4161 | @anchor{powerpc-x-eabi} | |
4162 | @heading powerpc-*-eabi | |
4163 | Embedded PowerPC system in big endian mode. | |
4164 | ||
4165 | @html | |
4166 | <hr /> | |
4167 | @end html | |
4168 | @anchor{powerpcle-x-elf} | |
4169 | @heading powerpcle-*-elf | |
4170 | PowerPC system in little endian mode, running System V.4. | |
4171 | ||
4172 | @html | |
4173 | <hr /> | |
4174 | @end html | |
4175 | @anchor{powerpcle-x-eabisim} | |
4176 | @heading powerpcle-*-eabisim | |
4177 | Embedded PowerPC system in little endian mode for use in running under | |
4178 | the PSIM simulator. | |
4179 | ||
4180 | @html | |
4181 | <hr /> | |
4182 | @end html | |
4183 | @anchor{powerpcle-x-eabi} | |
4184 | @heading powerpcle-*-eabi | |
4185 | Embedded PowerPC system in little endian mode. | |
4186 | ||
4187 | @html | |
4188 | <hr /> | |
4189 | @end html | |
4190 | @anchor{rl78-x-elf} | |
4191 | @heading rl78-*-elf | |
4192 | The Renesas RL78 processor. | |
4193 | This configuration is intended for embedded systems. | |
4194 | ||
4195 | @html | |
4196 | <hr /> | |
4197 | @end html | |
4198 | @anchor{rx-x-elf} | |
4199 | @heading rx-*-elf | |
4200 | The Renesas RX processor. See | |
4201 | @uref{http://eu.renesas.com/fmwk.jsp?cnt=rx600_series_landing.jsp&fp=/products/mpumcu/rx_family/rx600_series} | |
4202 | for more information about this processor. | |
4203 | ||
4204 | @html | |
4205 | <hr /> | |
4206 | @end html | |
4207 | @anchor{s390-x-linux} | |
4208 | @heading s390-*-linux* | |
4209 | S/390 system running GNU/Linux for S/390@. | |
4210 | ||
4211 | @html | |
4212 | <hr /> | |
4213 | @end html | |
4214 | @anchor{s390x-x-linux} | |
4215 | @heading s390x-*-linux* | |
4216 | zSeries system (64-bit) running GNU/Linux for zSeries@. | |
4217 | ||
4218 | @html | |
4219 | <hr /> | |
4220 | @end html | |
4221 | @anchor{s390x-ibm-tpf} | |
4222 | @heading s390x-ibm-tpf* | |
4223 | zSeries system (64-bit) running TPF@. This platform is | |
4224 | supported as cross-compilation target only. | |
4225 | ||
4226 | @html | |
4227 | <hr /> | |
4228 | @end html | |
4229 | @c Please use Solaris 2 to refer to all release of Solaris, starting | |
4230 | @c with 2.0 until 2.6, 7, 8, etc. Solaris 1 was a marketing name for | |
4231 | @c SunOS 4 releases which we don't use to avoid confusion. Solaris | |
4232 | @c alone is too unspecific and must be avoided. | |
4233 | @anchor{x-x-solaris2} | |
4234 | @heading *-*-solaris2* | |
4235 | Support for Solaris 9 has been obsoleted in GCC 4.9, but can still be | |
4236 | enabled by configuring with @option{--enable-obsolete}. Support will be | |
4237 | removed in GCC 4.10. Support for Solaris 8 has removed in GCC 4.8. | |
4238 | Support for Solaris 7 has been removed in GCC 4.6. | |
4239 | ||
4240 | Sun does not ship a C compiler with Solaris 2 before Solaris 10, though | |
4241 | you can download the Sun Studio compilers for free. In Solaris 10 and | |
4242 | 11, GCC 3.4.3 is available as @command{/usr/sfw/bin/gcc}. Solaris 11 | |
4243 | also provides GCC 4.5.2 as @command{/usr/gcc/4.5/bin/gcc}. Alternatively, | |
4244 | you can install a pre-built GCC to bootstrap and install GCC. See the | |
4245 | @uref{binaries.html,,binaries page} for details. | |
4246 | ||
4247 | The Solaris 2 @command{/bin/sh} will often fail to configure | |
4248 | @samp{libstdc++-v3}, @samp{boehm-gc} or @samp{libjava}. We therefore | |
4249 | recommend using the following initial sequence of commands | |
4250 | ||
4251 | @smallexample | |
4252 | % CONFIG_SHELL=/bin/ksh | |
4253 | % export CONFIG_SHELL | |
4254 | @end smallexample | |
4255 | ||
4256 | @noindent | |
4257 | and proceed as described in @uref{configure.html,,the configure instructions}. | |
4258 | In addition we strongly recommend specifying an absolute path to invoke | |
4259 | @command{@var{srcdir}/configure}. | |
4260 | ||
4261 | Solaris 2 comes with a number of optional OS packages. Some of these | |
4262 | are needed to use GCC fully, namely @code{SUNWarc}, | |
4263 | @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm}, | |
4264 | @code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all | |
4265 | optional packages when installing Solaris 2, you will need to verify that | |
4266 | the packages that GCC needs are installed. | |
4267 | ||
4268 | To check whether an optional package is installed, use | |
4269 | the @command{pkginfo} command. To add an optional package, use the | |
4270 | @command{pkgadd} command. For further details, see the Solaris 2 | |
4271 | documentation. | |
4272 | ||
4273 | Trying to use the linker and other tools in | |
4274 | @file{/usr/ucb} to install GCC has been observed to cause trouble. | |
4275 | For example, the linker may hang indefinitely. The fix is to remove | |
4276 | @file{/usr/ucb} from your @env{PATH}. | |
4277 | ||
4278 | The build process works more smoothly with the legacy Sun tools so, if you | |
4279 | have @file{/usr/xpg4/bin} in your @env{PATH}, we recommend that you place | |
4280 | @file{/usr/bin} before @file{/usr/xpg4/bin} for the duration of the build. | |
4281 | ||
4282 | We recommend the use of the Sun assembler or the GNU assembler, in | |
4283 | conjunction with the Sun linker. The GNU @command{as} | |
4284 | versions included in Solaris 10, from GNU binutils 2.15, and Solaris 11, | |
4285 | from GNU binutils 2.19, are known to work. They can be found in | |
4286 | @file{/usr/sfw/bin/gas}. Current versions of GNU binutils (2.22) | |
4287 | are known to work as well. Note that your mileage may vary | |
4288 | if you use a combination of the GNU tools and the Sun tools: while the | |
4289 | combination GNU @command{as} + Sun @command{ld} should reasonably work, | |
4290 | the reverse combination Sun @command{as} + GNU @command{ld} may fail to | |
4291 | build or cause memory corruption at runtime in some cases for C++ programs. | |
4292 | @c FIXME: still? | |
4293 | GNU @command{ld} usually works as well, although the version included in | |
4294 | Solaris 10 cannot be used due to several bugs. Again, the current | |
4295 | version (2.22) is known to work, but generally lacks platform specific | |
4296 | features, so better stay with Sun @command{ld}. To use the LTO linker | |
4297 | plugin (@option{-fuse-linker-plugin}) with GNU @command{ld}, GNU | |
4298 | binutils @emph{must} be configured with @option{--enable-largefile}. | |
4299 | ||
4300 | To enable symbol versioning in @samp{libstdc++} with Sun @command{ld}, | |
4301 | you need to have any version of GNU @command{c++filt}, which is part of | |
4302 | GNU binutils. @samp{libstdc++} symbol versioning will be disabled if no | |
4303 | appropriate version is found. Sun @command{c++filt} from the Sun Studio | |
4304 | compilers does @emph{not} work. | |
4305 | ||
4306 | Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or | |
4307 | newer: @command{g++} will complain that types are missing. These headers | |
4308 | assume that omitting the type means @code{int}; this assumption worked for | |
4309 | C90 but is wrong for C++, and is now wrong for C99 also. | |
4310 | ||
4311 | Sun bug 4927647 sometimes causes random spurious testsuite failures | |
4312 | related to missing diagnostic output. This bug doesn't affect GCC | |
4313 | itself, rather it is a kernel bug triggered by the @command{expect} | |
4314 | program which is used only by the GCC testsuite driver. When the bug | |
4315 | causes the @command{expect} program to miss anticipated output, extra | |
4316 | testsuite failures appear. | |
4317 | ||
4318 | There are patches for Solaris 9 (117171-11 or newer for | |
4319 | SPARC, 117172-11 or newer for Intel) that address this problem. | |
4320 | ||
4321 | Thread-local storage (TLS) is supported in Solaris@tie{}9, but requires | |
4322 | some patches. The @samp{libthread} patches provide the | |
4323 | @code{__tls_get_addr} (SPARC, 64-bit x86) resp.@ @code{___tls_get_addr} | |
4324 | (32-bit x86) functions. On Solaris@tie{}9, the necessary support | |
4325 | on SPARC is present since FCS, while 114432-05 or newer is required on | |
4326 | Intel. Additionally, on Solaris@tie{}9/x86, patch 113986-02 or newer is | |
4327 | required for the Sun @command{ld} and runtime linker (@command{ld.so.1}) | |
4328 | support, while Solaris@tie{}9/SPARC works since FCS. The linker | |
4329 | patches must be installed even if GNU @command{ld} is used. Sun | |
4330 | @command{as} in Solaris@tie{}9 doesn't support the necessary | |
4331 | relocations, so GNU @command{as} must be used. The @command{configure} | |
4332 | script checks for those prerequisites and automatically enables TLS | |
4333 | support if they are met. Although those minimal patch versions should | |
4334 | work, it is recommended to use the latest patch versions which include | |
4335 | additional bug fixes. | |
4336 | ||
4337 | @html | |
4338 | <hr /> | |
4339 | @end html | |
4340 | @anchor{sparc-x-x} | |
4341 | @heading sparc*-*-* | |
4342 | This section contains general configuration information for all | |
4343 | SPARC-based platforms. In addition to reading this section, please | |
4344 | read all other sections that match your target. | |
4345 | ||
4346 | Newer versions of the GNU Multiple Precision Library (GMP), the MPFR | |
4347 | library and the MPC library are known to be miscompiled by earlier | |
4348 | versions of GCC on these platforms. We therefore recommend the use | |
4349 | of the exact versions of these libraries listed as minimal versions | |
4350 | in @uref{prerequisites.html,,the prerequisites}. | |
4351 | ||
4352 | @html | |
4353 | <hr /> | |
4354 | @end html | |
4355 | @anchor{sparc-sun-solaris2} | |
4356 | @heading sparc-sun-solaris2* | |
4357 | When GCC is configured to use GNU binutils 2.14 or later, the binaries | |
4358 | produced are smaller than the ones produced using Sun's native tools; | |
4359 | this difference is quite significant for binaries containing debugging | |
4360 | information. | |
4361 | ||
4362 | Starting with Solaris 7, the operating system is capable of executing | |
4363 | 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports | |
4364 | this; the @option{-m64} option enables 64-bit code generation. | |
4365 | However, if all you want is code tuned for the UltraSPARC CPU, you | |
4366 | should try the @option{-mtune=ultrasparc} option instead, which produces | |
4367 | code that, unlike full 64-bit code, can still run on non-UltraSPARC | |
4368 | machines. | |
4369 | ||
4370 | When configuring on a Solaris 7 or later system that is running a kernel | |
4371 | that supports only 32-bit binaries, one must configure with | |
4372 | @option{--disable-multilib}, since we will not be able to build the | |
4373 | 64-bit target libraries. | |
4374 | ||
4375 | GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of | |
4376 | the GNU compiler (especially GCC 3.0.x versions), which lead to the | |
4377 | miscompilation of the stage1 compiler and the subsequent failure of the | |
4378 | bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary | |
4379 | stage, i.e.@: to bootstrap that compiler with the base compiler and then | |
4380 | use it to bootstrap the final compiler. | |
4381 | ||
4382 | GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE Studio 7) | |
4383 | and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a bootstrap | |
4384 | failure in form of a miscompilation of the stage1 compiler by the Sun | |
4385 | compiler. This is Sun bug 4974440. This is fixed with patch 112760-07. | |
4386 | ||
4387 | GCC 3.4 changed the default debugging format from Stabs to DWARF-2 for | |
4388 | 32-bit code on Solaris 7 and later. If you use the Sun assembler, this | |
4389 | change apparently runs afoul of Sun bug 4910101 (which is referenced as | |
4390 | an x86-only problem by Sun, probably because they do not use DWARF-2). | |
4391 | A symptom of the problem is that you cannot compile C++ programs like | |
4392 | @command{groff} 1.19.1 without getting messages similar to the following: | |
4393 | ||
4394 | @smallexample | |
4395 | ld: warning: relocation error: R_SPARC_UA32: @dots{} | |
4396 | external symbolic relocation against non-allocatable section | |
4397 | .debug_info cannot be processed at runtime: relocation ignored. | |
4398 | @end smallexample | |
4399 | ||
4400 | @noindent | |
4401 | To work around this problem, compile with @option{-gstabs+} instead of | |
4402 | plain @option{-g}. | |
4403 | ||
4404 | When configuring the GNU Multiple Precision Library (GMP), the MPFR | |
4405 | library or the MPC library on a Solaris 7 or later system, the canonical | |
4406 | target triplet must be specified as the @command{build} parameter on the | |
4407 | configure line. This target triplet can be obtained by invoking @command{./config.guess} in the toplevel source directory of GCC (and | |
4408 | not that of GMP or MPFR or MPC). For example on a Solaris 9 system: | |
4409 | ||
4410 | @smallexample | |
4411 | % ./configure --build=sparc-sun-solaris2.9 --prefix=xxx | |
4412 | @end smallexample | |
4413 | ||
4414 | @html | |
4415 | <hr /> | |
4416 | @end html | |
4417 | @anchor{sparc-sun-solaris210} | |
4418 | @heading sparc-sun-solaris2.10 | |
4419 | There is a bug in older versions of the Sun assembler which breaks | |
4420 | thread-local storage (TLS). A typical error message is | |
4421 | ||
4422 | @smallexample | |
4423 | ld: fatal: relocation error: R_SPARC_TLS_LE_HIX22: file /var/tmp//ccamPA1v.o: | |
4424 | symbol <unknown>: bad symbol type SECT: symbol type must be TLS | |
4425 | @end smallexample | |
4426 | ||
4427 | @noindent | |
4428 | This bug is fixed in Sun patch 118683-03 or later. | |
4429 | ||
4430 | @html | |
4431 | <hr /> | |
4432 | @end html | |
4433 | @anchor{sparc-x-linux} | |
4434 | @heading sparc-*-linux* | |
4435 | ||
4436 | GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4 | |
4437 | or newer on this platform. All earlier binutils and glibc | |
4438 | releases mishandled unaligned relocations on @code{sparc-*-*} targets. | |
4439 | ||
4440 | ||
4441 | @html | |
4442 | <hr /> | |
4443 | @end html | |
4444 | @anchor{sparc64-x-solaris2} | |
4445 | @heading sparc64-*-solaris2* | |
4446 | When configuring the GNU Multiple Precision Library (GMP), the MPFR | |
4447 | library or the MPC library, the canonical target triplet must be specified | |
4448 | as the @command{build} parameter on the configure line. For example | |
4449 | on a Solaris 9 system: | |
4450 | ||
4451 | @smallexample | |
4452 | % ./configure --build=sparc64-sun-solaris2.9 --prefix=xxx | |
4453 | @end smallexample | |
4454 | ||
4455 | The following compiler flags must be specified in the configure | |
4456 | step in order to bootstrap this target with the Sun compiler: | |
4457 | ||
4458 | @smallexample | |
4459 | % CC="cc -xarch=v9 -xildoff" @var{srcdir}/configure [@var{options}] [@var{target}] | |
4460 | @end smallexample | |
4461 | ||
4462 | @noindent | |
4463 | @option{-xarch=v9} specifies the SPARC-V9 architecture to the Sun toolchain | |
4464 | and @option{-xildoff} turns off the incremental linker. | |
4465 | ||
4466 | @html | |
4467 | <hr /> | |
4468 | @end html | |
4469 | @anchor{sparcv9-x-solaris2} | |
4470 | @heading sparcv9-*-solaris2* | |
4471 | This is a synonym for @samp{sparc64-*-solaris2*}. | |
4472 | ||
4473 | @html | |
4474 | <hr /> | |
4475 | @end html | |
4476 | @anchor{c6x-x-x} | |
4477 | @heading c6x-*-* | |
4478 | The C6X family of processors. This port requires binutils-2.22 or newer. | |
4479 | ||
4480 | @html | |
4481 | <hr /> | |
4482 | @end html | |
4483 | @anchor{tilegx-*-linux} | |
4484 | @heading tilegx-*-linux* | |
4485 | The TILE-Gx processor in little endian mode, running GNU/Linux. This | |
4486 | port requires binutils-2.22 or newer. | |
4487 | ||
4488 | @html | |
4489 | <hr /> | |
4490 | @end html | |
4491 | @anchor{tilegxbe-*-linux} | |
4492 | @heading tilegxbe-*-linux* | |
4493 | The TILE-Gx processor in big endian mode, running GNU/Linux. This | |
4494 | port requires binutils-2.23 or newer. | |
4495 | ||
4496 | @html | |
4497 | <hr /> | |
4498 | @end html | |
4499 | @anchor{tilepro-*-linux} | |
4500 | @heading tilepro-*-linux* | |
4501 | The TILEPro processor running GNU/Linux. This port requires | |
4502 | binutils-2.22 or newer. | |
4503 | ||
4504 | @html | |
4505 | <hr /> | |
4506 | @end html | |
4507 | @anchor{x-x-vxworks} | |
4508 | @heading *-*-vxworks* | |
4509 | Support for VxWorks is in flux. At present GCC supports @emph{only} the | |
4510 | very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC@. | |
4511 | We welcome patches for other architectures supported by VxWorks 5.5. | |
4512 | Support for VxWorks AE would also be welcome; we believe this is merely | |
4513 | a matter of writing an appropriate ``configlette'' (see below). We are | |
4514 | not interested in supporting older, a.out or COFF-based, versions of | |
4515 | VxWorks in GCC 3. | |
4516 | ||
4517 | VxWorks comes with an older version of GCC installed in | |
4518 | @file{@var{$WIND_BASE}/host}; we recommend you do not overwrite it. | |
4519 | Choose an installation @var{prefix} entirely outside @var{$WIND_BASE}. | |
4520 | Before running @command{configure}, create the directories @file{@var{prefix}} | |
4521 | and @file{@var{prefix}/bin}. Link or copy the appropriate assembler, | |
4522 | linker, etc.@: into @file{@var{prefix}/bin}, and set your @var{PATH} to | |
4523 | include that directory while running both @command{configure} and | |
4524 | @command{make}. | |
4525 | ||
4526 | You must give @command{configure} the | |
4527 | @option{--with-headers=@var{$WIND_BASE}/target/h} switch so that it can | |
4528 | find the VxWorks system headers. Since VxWorks is a cross compilation | |
4529 | target only, you must also specify @option{--target=@var{target}}. | |
4530 | @command{configure} will attempt to create the directory | |
4531 | @file{@var{prefix}/@var{target}/sys-include} and copy files into it; | |
4532 | make sure the user running @command{configure} has sufficient privilege | |
4533 | to do so. | |
4534 | ||
4535 | GCC's exception handling runtime requires a special ``configlette'' | |
4536 | module, @file{contrib/gthr_supp_vxw_5x.c}. Follow the instructions in | |
4537 | that file to add the module to your kernel build. (Future versions of | |
4538 | VxWorks will incorporate this module.) | |
4539 | ||
4540 | @html | |
4541 | <hr /> | |
4542 | @end html | |
4543 | @anchor{x86-64-x-x} | |
4544 | @heading x86_64-*-*, amd64-*-* | |
4545 | GCC supports the x86-64 architecture implemented by the AMD64 processor | |
4546 | (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD@. | |
4547 | On GNU/Linux the default is a bi-arch compiler which is able to generate | |
4548 | both 64-bit x86-64 and 32-bit x86 code (via the @option{-m32} switch). | |
4549 | ||
4550 | @html | |
4551 | <hr /> | |
4552 | @end html | |
4553 | @anchor{x86-64-x-solaris210} | |
4554 | @heading x86_64-*-solaris2.1[0-9]* | |
4555 | GCC also supports the x86-64 architecture implemented by the AMD64 | |
4556 | processor (@samp{amd64-*-*} is an alias for @samp{x86_64-*-*}) on | |
4557 | Solaris 10 or later. Unlike other systems, without special options a | |
4558 | bi-arch compiler is built which generates 32-bit code by default, but | |
4559 | can generate 64-bit x86-64 code with the @option{-m64} switch. Since | |
4560 | GCC 4.7, there is also configuration that defaults to 64-bit code, but | |
4561 | can generate 32-bit code with @option{-m32}. To configure and build | |
4562 | this way, you have to provide all support libraries like @file{libgmp} | |
4563 | as 64-bit code, configure with @option{--target=x86_64-pc-solaris2.1x} | |
4564 | and @samp{CC=gcc -m64}. | |
4565 | ||
4566 | @html | |
4567 | <hr /> | |
4568 | @end html | |
4569 | @anchor{xtensa-x-elf} | |
4570 | @heading xtensa*-*-elf | |
4571 | This target is intended for embedded Xtensa systems using the | |
4572 | @samp{newlib} C library. It uses ELF but does not support shared | |
4573 | objects. Designed-defined instructions specified via the | |
4574 | Tensilica Instruction Extension (TIE) language are only supported | |
4575 | through inline assembly. | |
4576 | ||
4577 | The Xtensa configuration information must be specified prior to | |
4578 | building GCC@. The @file{include/xtensa-config.h} header | |
4579 | file contains the configuration information. If you created your | |
4580 | own Xtensa configuration with the Xtensa Processor Generator, the | |
4581 | downloaded files include a customized copy of this header file, | |
4582 | which you can use to replace the default header file. | |
4583 | ||
4584 | @html | |
4585 | <hr /> | |
4586 | @end html | |
4587 | @anchor{xtensa-x-linux} | |
4588 | @heading xtensa*-*-linux* | |
4589 | This target is for Xtensa systems running GNU/Linux. It supports ELF | |
4590 | shared objects and the GNU C library (glibc). It also generates | |
4591 | position-independent code (PIC) regardless of whether the | |
4592 | @option{-fpic} or @option{-fPIC} options are used. In other | |
4593 | respects, this target is the same as the | |
4594 | @uref{#xtensa*-*-elf,,@samp{xtensa*-*-elf}} target. | |
4595 | ||
4596 | @html | |
4597 | <hr /> | |
4598 | @end html | |
4599 | @anchor{windows} | |
4600 | @heading Microsoft Windows | |
4601 | ||
4602 | @subheading Intel 16-bit versions | |
4603 | The 16-bit versions of Microsoft Windows, such as Windows 3.1, are not | |
4604 | supported. | |
4605 | ||
4606 | However, the 32-bit port has limited support for Microsoft | |
4607 | Windows 3.11 in the Win32s environment, as a target only. See below. | |
4608 | ||
4609 | @subheading Intel 32-bit versions | |
4610 | The 32-bit versions of Windows, including Windows 95, Windows NT, Windows | |
4611 | XP, and Windows Vista, are supported by several different target | |
4612 | platforms. These targets differ in which Windows subsystem they target | |
4613 | and which C libraries are used. | |
4614 | ||
4615 | @itemize | |
4616 | @item Cygwin @uref{#x-x-cygwin,,*-*-cygwin}: Cygwin provides a user-space | |
4617 | Linux API emulation layer in the Win32 subsystem. | |
4618 | @item Interix @uref{#x-x-interix,,*-*-interix}: The Interix subsystem | |
4619 | provides native support for POSIX. | |
4620 | @item MinGW @uref{#x-x-mingw32,,*-*-mingw32}: MinGW is a native GCC port for | |
4621 | the Win32 subsystem that provides a subset of POSIX. | |
4622 | @item MKS i386-pc-mks: NuTCracker from MKS. See | |
4623 | @uref{http://www.mkssoftware.com/} for more information. | |
4624 | @end itemize | |
4625 | ||
4626 | @subheading Intel 64-bit versions | |
4627 | GCC contains support for x86-64 using the mingw-w64 | |
4628 | runtime library, available from @uref{http://mingw-w64.sourceforge.net/}. | |
4629 | This library should be used with the target triple x86_64-pc-mingw32. | |
4630 | ||
4631 | Presently Windows for Itanium is not supported. | |
4632 | ||
4633 | @subheading Windows CE | |
4634 | Windows CE is supported as a target only on Hitachi | |
4635 | SuperH (sh-wince-pe), and MIPS (mips-wince-pe). | |
4636 | ||
4637 | @subheading Other Windows Platforms | |
4638 | GCC no longer supports Windows NT on the Alpha or PowerPC. | |
4639 | ||
4640 | GCC no longer supports the Windows POSIX subsystem. However, it does | |
4641 | support the Interix subsystem. See above. | |
4642 | ||
4643 | Old target names including *-*-winnt and *-*-windowsnt are no longer used. | |
4644 | ||
4645 | PW32 (i386-pc-pw32) support was never completed, and the project seems to | |
4646 | be inactive. See @uref{http://pw32.sourceforge.net/} for more information. | |
4647 | ||
4648 | UWIN support has been removed due to a lack of maintenance. | |
4649 | ||
4650 | @html | |
4651 | <hr /> | |
4652 | @end html | |
4653 | @anchor{x-x-cygwin} | |
4654 | @heading *-*-cygwin | |
4655 | Ports of GCC are included with the | |
4656 | @uref{http://www.cygwin.com/,,Cygwin environment}. | |
4657 | ||
4658 | GCC will build under Cygwin without modification; it does not build | |
4659 | with Microsoft's C++ compiler and there are no plans to make it do so. | |
4660 | ||
4661 | The Cygwin native compiler can be configured to target any 32-bit x86 | |
4662 | cpu architecture desired; the default is i686-pc-cygwin. It should be | |
4663 | used with as up-to-date a version of binutils as possible; use either | |
4664 | the latest official GNU binutils release in the Cygwin distribution, | |
4665 | or version 2.20 or above if building your own. | |
4666 | ||
4667 | @html | |
4668 | <hr /> | |
4669 | @end html | |
4670 | @anchor{x-x-interix} | |
4671 | @heading *-*-interix | |
4672 | The Interix target is used by OpenNT, Interix, Services For UNIX (SFU), | |
4673 | and Subsystem for UNIX-based Applications (SUA). Applications compiled | |
4674 | with this target run in the Interix subsystem, which is separate from | |
4675 | the Win32 subsystem. This target was last known to work in GCC 3.3. | |
4676 | ||
4677 | @html | |
4678 | <hr /> | |
4679 | @end html | |
4680 | @anchor{x-x-mingw32} | |
4681 | @heading *-*-mingw32 | |
4682 | GCC will build with and support only MinGW runtime 3.12 and later. | |
4683 | Earlier versions of headers are incompatible with the new default semantics | |
4684 | of @code{extern inline} in @code{-std=c99} and @code{-std=gnu99} modes. | |
4685 | ||
4686 | @html | |
4687 | <hr /> | |
4688 | @end html | |
4689 | @anchor{older} | |
4690 | @heading Older systems | |
4691 | GCC contains support files for many older (1980s and early | |
4692 | 1990s) Unix variants. For the most part, support for these systems | |
4693 | has not been deliberately removed, but it has not been maintained for | |
4694 | several years and may suffer from bitrot. | |
4695 | ||
4696 | Starting with GCC 3.1, each release has a list of ``obsoleted'' systems. | |
4697 | Support for these systems is still present in that release, but | |
4698 | @command{configure} will fail unless the @option{--enable-obsolete} | |
4699 | option is given. Unless a maintainer steps forward, support for these | |
4700 | systems will be removed from the next release of GCC@. | |
4701 | ||
4702 | Support for old systems as hosts for GCC can cause problems if the | |
4703 | workarounds for compiler, library and operating system bugs affect the | |
4704 | cleanliness or maintainability of the rest of GCC@. In some cases, to | |
4705 | bring GCC up on such a system, if still possible with current GCC, may | |
4706 | require first installing an old version of GCC which did work on that | |
4707 | system, and using it to compile a more recent GCC, to avoid bugs in the | |
4708 | vendor compiler. Old releases of GCC 1 and GCC 2 are available in the | |
4709 | @file{old-releases} directory on the @uref{../mirrors.html,,GCC mirror | |
4710 | sites}. Header bugs may generally be avoided using | |
4711 | @command{fixincludes}, but bugs or deficiencies in libraries and the | |
4712 | operating system may still cause problems. | |
4713 | ||
4714 | Support for older systems as targets for cross-compilation is less | |
4715 | problematic than support for them as hosts for GCC; if an enthusiast | |
4716 | wishes to make such a target work again (including resurrecting any of | |
4717 | the targets that never worked with GCC 2, starting from the last | |
4718 | version before they were removed), patches | |
4719 | @uref{../contribute.html,,following the usual requirements} would be | |
4720 | likely to be accepted, since they should not affect the support for more | |
4721 | modern targets. | |
4722 | ||
4723 | For some systems, old versions of GNU binutils may also be useful, | |
4724 | and are available from @file{pub/binutils/old-releases} on | |
4725 | @uref{http://sourceware.org/mirrors.html,,sourceware.org mirror sites}. | |
4726 | ||
4727 | Some of the information on specific systems above relates to | |
4728 | such older systems, but much of the information | |
4729 | about GCC on such systems (which may no longer be applicable to | |
4730 | current GCC) is to be found in the GCC texinfo manual. | |
4731 | ||
4732 | @html | |
4733 | <hr /> | |
4734 | @end html | |
4735 | @anchor{elf} | |
4736 | @heading all ELF targets (SVR4, Solaris 2, etc.) | |
4737 | C++ support is significantly better on ELF targets if you use the | |
4738 | @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of | |
4739 | inlines, vtables and template instantiations will be discarded | |
4740 | automatically. | |
4741 | ||
4742 | ||
4743 | @html | |
4744 | <hr /> | |
4745 | <p> | |
4746 | @end html | |
4747 | @ifhtml | |
4748 | @uref{./index.html,,Return to the GCC Installation page} | |
4749 | @end ifhtml | |
4750 | @end ifset | |
4751 | ||
4752 | @c ***Old documentation****************************************************** | |
4753 | @ifset oldhtml | |
4754 | @include install-old.texi | |
4755 | @html | |
4756 | <hr /> | |
4757 | <p> | |
4758 | @end html | |
4759 | @ifhtml | |
4760 | @uref{./index.html,,Return to the GCC Installation page} | |
4761 | @end ifhtml | |
4762 | @end ifset | |
4763 | ||
4764 | @c ***GFDL******************************************************************** | |
4765 | @ifset gfdlhtml | |
4766 | @include fdl.texi | |
4767 | @html | |
4768 | <hr /> | |
4769 | <p> | |
4770 | @end html | |
4771 | @ifhtml | |
4772 | @uref{./index.html,,Return to the GCC Installation page} | |
4773 | @end ifhtml | |
4774 | @end ifset | |
4775 | ||
4776 | @c *************************************************************************** | |
4777 | @c Part 6 The End of the Document | |
4778 | @ifinfo | |
4779 | @comment node-name, next, previous, up | |
4780 | @node Concept Index, , GNU Free Documentation License, Top | |
4781 | @end ifinfo | |
4782 | ||
4783 | @ifinfo | |
4784 | @unnumbered Concept Index | |
4785 | ||
4786 | @printindex cp | |
4787 | ||
4788 | @contents | |
4789 | @end ifinfo | |
4790 | @bye |