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