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