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