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