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