Skip to content
Browse files

Rebase to HEAD as of a few days ago.

  • Loading branch information...
1 parent 861c7b4 commit 5d5ec9adca1e85cf9794ca71c025861c71c687f2 tls committed Aug 19, 2014
Showing with 155,954 additions and 0 deletions.
  1. +5 −0 external/gpl3/gcc.old/Makefile
  2. +16 −0 external/gpl3/gcc.old/Makefile.gcc_path
  3. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/ABOUT-NLS
  4. 0 {gnu/dist/gcc4/libstdc++-v3/docs/html/17_intro → external/gpl3/gcc.old/dist}/COPYING
  5. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/COPYING.LIB
  6. +73 −0 external/gpl3/gcc.old/dist/COPYING.RUNTIME
  7. +674 −0 external/gpl3/gcc.old/dist/COPYING3
  8. +165 −0 external/gpl3/gcc.old/dist/COPYING3.LIB
  9. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/INSTALL/README
  10. +112 −0 external/gpl3/gcc.old/dist/INSTALL/binaries.html
  11. +376 −0 external/gpl3/gcc.old/dist/INSTALL/build.html
  12. +1,209 −0 external/gpl3/gcc.old/dist/INSTALL/configure.html
  13. +97 −0 external/gpl3/gcc.old/dist/INSTALL/download.html
  14. +170 −0 external/gpl3/gcc.old/dist/INSTALL/finalinstall.html
  15. +463 −0 external/gpl3/gcc.old/dist/INSTALL/gfdl.html
  16. +125 −0 external/gpl3/gcc.old/dist/INSTALL/index.html
  17. +213 −0 external/gpl3/gcc.old/dist/INSTALL/old.html
  18. +284 −0 external/gpl3/gcc.old/dist/INSTALL/prerequisites.html
  19. +1,609 −0 external/gpl3/gcc.old/dist/INSTALL/specific.html
  20. +233 −0 external/gpl3/gcc.old/dist/INSTALL/test.html
  21. +1 −0 external/gpl3/gcc.old/dist/LAST_UPDATED
  22. +495 −0 external/gpl3/gcc.old/dist/MAINTAINERS
  23. +66,220 −0 external/gpl3/gcc.old/dist/MD5SUMS
  24. +594 −0 external/gpl3/gcc.old/dist/Makefile.def
  25. +58,095 −0 external/gpl3/gcc.old/dist/
  26. +1,802 −0 external/gpl3/gcc.old/dist/Makefile.tpl
  27. +11,220 −0 external/gpl3/gcc.old/dist/NEWS
  28. +17 −0 external/gpl3/gcc.old/dist/README
  29. +143 −0 external/gpl3/gcc.old/dist/compile
  30. +876 −0 external/gpl3/gcc.old/dist/
  31. +1,519 −0 external/gpl3/gcc.old/dist/config.guess
  32. +548 −0 external/gpl3/gcc.old/dist/config.rpath
  33. +1,732 −0 external/gpl3/gcc.old/dist/config.sub
  34. +746 −0 external/gpl3/gcc.old/dist/config/acinclude.m4
  35. +621 −0 external/gpl3/gcc.old/dist/config/acx.m4
  36. +1 −0 external/gpl3/gcc.old/dist/config/
  37. +1 −0 external/gpl3/gcc.old/dist/config/
  38. +8 −0 external/gpl3/gcc.old/dist/config/
  39. +16 −0 external/gpl3/gcc.old/dist/config/
  40. +11 −0 external/gpl3/gcc.old/dist/config/
  41. +12 −0 external/gpl3/gcc.old/dist/config/
  42. +12 −0 external/gpl3/gcc.old/dist/config/
  43. +2 −0 external/gpl3/gcc.old/dist/config/
  44. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/codeset.m4
  45. +137 −0 external/gpl3/gcc.old/dist/config/depstand.m4
  46. +27 −0 external/gpl3/gcc.old/dist/config/elf.m4
  47. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/enable.m4
  48. +79 −0 external/gpl3/gcc.old/dist/config/extensions.m4
  49. +64 −0 external/gpl3/gcc.old/dist/config/futex.m4
  50. +80 −0 external/gpl3/gcc.old/dist/config/gettext-sister.m4
  51. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/gettext.m4
  52. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/glibc21.m4
  53. +32 −0 external/gpl3/gcc.old/dist/config/gxx-include-dir.m4
  54. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/iconv.m4
  55. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/intdiv0.m4
  56. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/inttypes-pri.m4
  57. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/inttypes.m4
  58. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/inttypes_h.m4
  59. +34 −0 external/gpl3/gcc.old/dist/config/largefile.m4
  60. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/lcmessage.m4
  61. +45 −0 external/gpl3/gcc.old/dist/config/ld-symbolic.m4
  62. +31 −0 external/gpl3/gcc.old/dist/config/lead-dot.m4
  63. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/lib-ld.m4
  64. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/lib-link.m4
  65. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/lib-prefix.m4
  66. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/mh-cxux
  67. +9 −0 external/gpl3/gcc.old/dist/config/mh-cygwin
  68. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/mh-decstation
  69. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/mh-dgux386
  70. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/mh-djgpp
  71. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/mh-interix
  72. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/mh-lynxrs6k
  73. +6 −0 external/gpl3/gcc.old/dist/config/mh-mingw
  74. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/mh-ncr3000
  75. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/mh-necv4
  76. +4 −0 external/gpl3/gcc.old/dist/config/mh-pa
  77. +4 −0 external/gpl3/gcc.old/dist/config/mh-pa-hpux10
  78. +8 −0 external/gpl3/gcc.old/dist/config/mh-ppc-aix
  79. +5 −0 external/gpl3/gcc.old/dist/config/mh-ppc-darwin
  80. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/mh-sco
  81. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/mh-solaris
  82. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/mh-sysv4
  83. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/mh-sysv5
  84. +2 −0 external/gpl3/gcc.old/dist/config/mh-x86-darwin
  85. +2 −0 external/gpl3/gcc.old/dist/config/mh-x86omitfp
  86. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/mt-alphaieee
  87. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/mt-d30v
  88. +1 −0 external/gpl3/gcc.old/dist/config/mt-gnu
  89. +8 −0 external/gpl3/gcc.old/dist/config/mt-mep
  90. +1 −0 external/gpl3/gcc.old/dist/config/mt-mips-elfoabi
  91. +2 −0 external/gpl3/gcc.old/dist/config/mt-mips-gnu
  92. +5 −0 external/gpl3/gcc.old/dist/config/mt-mips16-compat
  93. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/mt-netware
  94. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/mt-ospace
  95. +10 −0 external/gpl3/gcc.old/dist/config/mt-sde
  96. +2 −0 external/gpl3/gcc.old/dist/config/mt-spu
  97. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/mt-v810
  98. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/mt-wince
  99. +68 −0 external/gpl3/gcc.old/dist/config/multi.m4
  100. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/nls.m4
  101. +69 −0 external/gpl3/gcc.old/dist/config/no-executables.m4
  102. +274 −0 external/gpl3/gcc.old/dist/config/override.m4
  103. +11 −0 external/gpl3/gcc.old/dist/config/plugins.m4
  104. +197 −0 external/gpl3/gcc.old/dist/config/po.m4
  105. +98 −0 external/gpl3/gcc.old/dist/config/proginstall.m4
  106. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/progtest.m4
  107. +586 −0 external/gpl3/gcc.old/dist/config/stdint.m4
  108. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/stdint_h.m4
  109. +3,246 −0 external/gpl3/gcc.old/dist/config/tcl.m4
  110. +129 −0 external/gpl3/gcc.old/dist/config/tls.m4
  111. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/uintmax_t.m4
  112. 0 {gnu/dist/gcc4 → external/gpl3/gcc.old/dist}/config/ulonglong.m4
  113. +37 −0 external/gpl3/gcc.old/dist/config/unwind_ipinfo.m4
  114. +107 −0 external/gpl3/gcc.old/dist/config/warnings.m4
  115. +18 −0 external/gpl3/gcc.old/dist/config/zlib.m4
Sorry, we could not display the entire diff because too many files (53,502) changed.
5 external/gpl3/gcc.old/Makefile
@@ -0,0 +1,5 @@
+# $NetBSD: Makefile,v 2014/08/19 23:57:05 tls Exp $
+SUBDIR+= lib .WAIT usr.bin
+.include <>
16 external/gpl3/gcc.old/Makefile.gcc_path
@@ -0,0 +1,16 @@
+# $NetBSD: Makefile.gcc_path,v 2014/08/19 23:57:05 tls Exp $
+# Define some commom paths
+.include <>
+#.if exists(${GCC_SUBDIR}/dist)
0 gnu/dist/gcc4/ABOUT-NLS → external/gpl3/gcc.old/dist/ABOUT-NLS
File renamed without changes.
0 ...4/libstdc++-v3/docs/html/17_intro/COPYING → external/gpl3/gcc.old/dist/COPYING
File renamed without changes.
0 gnu/dist/gcc4/COPYING.LIB → external/gpl3/gcc.old/dist/COPYING.LIB
File renamed without changes.
73 external/gpl3/gcc.old/dist/COPYING.RUNTIME
@@ -0,0 +1,73 @@
+Version 3.1, 31 March 2009
+Copyright (C) 2009 Free Software Foundation, Inc. <>
+Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.
+This GCC Runtime Library Exception ("Exception") is an additional
+permission under section 7 of the GNU General Public License, version
+3 ("GPLv3"). It applies to a given file (the "Runtime Library") that
+bears a notice placed by the copyright holder of the file stating that
+the file is governed by GPLv3 along with this Exception.
+When you use GCC to compile a program, GCC may combine portions of
+certain GCC header files and runtime libraries with the compiled
+program. The purpose of this Exception is to allow compilation of
+non-GPL (including proprietary) programs to use, in this way, the
+header files and runtime libraries covered by this Exception.
+0. Definitions.
+A file is an "Independent Module" if it either requires the Runtime
+Library for execution after a Compilation Process, or makes use of an
+interface provided by the Runtime Library, but is not otherwise based
+on the Runtime Library.
+"GCC" means a version of the GNU Compiler Collection, with or without
+modifications, governed by version 3 (or a specified later version) of
+the GNU General Public License (GPL) with the option of using any
+subsequent versions published by the FSF.
+"GPL-compatible Software" is software whose conditions of propagation,
+modification and use would permit combination with GCC in accord with
+the license of GCC.
+"Target Code" refers to output from any compiler for a real or virtual
+target processor architecture, in executable form or suitable for
+input to an assembler, loader, linker and/or execution
+phase. Notwithstanding that, Target Code does not include data in any
+format that is used as a compiler intermediate representation, or used
+for producing a compiler intermediate representation.
+The "Compilation Process" transforms code entirely represented in
+non-intermediate languages designed for human-written code, and/or in
+Java Virtual Machine byte code, into Target Code. Thus, for example,
+use of source code generators and preprocessors need not be considered
+part of the Compilation Process, since the Compilation Process can be
+understood as starting with the output of the generators or
+A Compilation Process is "Eligible" if it is done using GCC, alone or
+with other GPL-compatible software, or if it is done without using any
+work based on GCC. For example, using non-GPL-compatible Software to
+optimize any GCC intermediate representations would not qualify as an
+Eligible Compilation Process.
+1. Grant of Additional Permission.
+You have permission to propagate a work of Target Code formed by
+combining the Runtime Library with Independent Modules, even if such
+propagation would otherwise violate the terms of GPLv3, provided that
+all Target Code was generated by Eligible Compilation Processes. You
+may then convey such a combination under terms of your choice,
+consistent with the licensing of the Independent Modules.
+2. No Weakening of GCC Copyleft.
+The availability of this Exception does not imply any general
+presumption that third-party software is unaffected by the copyleft
+requirements of the license of GCC.
674 external/gpl3/gcc.old/dist/COPYING3
@@ -0,0 +1,674 @@
+ Version 3, 29 June 2007
+ Copyright (C) 2007 Free Software Foundation, Inc. <>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+ Preamble
+ The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+ The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works. By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users. We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors. You can apply it to
+your programs, too.
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+ To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights. Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received. You must make sure that they, too, receive
+or can get the source code. And you must show them these terms so they
+know their rights.
+ Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+ For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software. For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+ Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so. This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software. The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable. Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products. If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+ Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary. To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+ The precise terms and conditions for copying, distribution and
+modification follow.
+ 0. Definitions.
+ "This License" refers to version 3 of the GNU General Public License.
+ "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+ "The Program" refers to any copyrightable work licensed under this
+License. Each licensee is addressed as "you". "Licensees" and
+"recipients" may be individuals or organizations.
+ To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy. The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+ A "covered work" means either the unmodified Program or a work based
+on the Program.
+ To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy. Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+ To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies. Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+ An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License. If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+ 1. Source Code.
+ The "source code" for a work means the preferred form of the work
+for making modifications to it. "Object code" means any non-source
+form of a work.
+ A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+ The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form. A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+ The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities. However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work. For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+ The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+ The Corresponding Source for a work in source code form is that
+same work.
+ 2. Basic Permissions.
+ All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met. This License explicitly affirms your unlimited
+permission to run the unmodified Program. The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work. This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+ You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force. You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright. Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+ Conveying under any other circumstances is permitted solely under
+the conditions stated below. Sublicensing is not allowed; section 10
+makes it unnecessary.
+ 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+ No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+ When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+ 4. Conveying Verbatim Copies.
+ You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+ You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+ 5. Conveying Modified Source Versions.
+ You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+ a) The work must carry prominent notices stating that you modified
+ it, and giving a relevant date.
+ b) The work must carry prominent notices stating that it is
+ released under this License and any conditions added under section
+ 7. This requirement modifies the requirement in section 4 to
+ "keep intact all notices".
+ c) You must license the entire work, as a whole, under this
+ License to anyone who comes into possession of a copy. This
+ License will therefore apply, along with any applicable section 7
+ additional terms, to the whole of the work, and all its parts,
+ regardless of how they are packaged. This License gives no
+ permission to license the work in any other way, but it does not
+ invalidate such permission if you have separately received it.
+ d) If the work has interactive user interfaces, each must display
+ Appropriate Legal Notices; however, if the Program has interactive
+ interfaces that do not display Appropriate Legal Notices, your
+ work need not make them do so.
+ A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit. Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+ 6. Conveying Non-Source Forms.
+ You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+ a) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by the
+ Corresponding Source fixed on a durable physical medium
+ customarily used for software interchange.
+ b) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by a
+ written offer, valid for at least three years and valid for as
+ long as you offer spare parts or customer support for that product
+ model, to give anyone who possesses the object code either (1) a
+ copy of the Corresponding Source for all the software in the
+ product that is covered by this License, on a durable physical
+ medium customarily used for software interchange, for a price no
+ more than your reasonable cost of physically performing this
+ conveying of source, or (2) access to copy the
+ Corresponding Source from a network server at no charge.
+ c) Convey individual copies of the object code with a copy of the
+ written offer to provide the Corresponding Source. This
+ alternative is allowed only occasionally and noncommercially, and
+ only if you received the object code with such an offer, in accord
+ with subsection 6b.
+ d) Convey the object code by offering access from a designated
+ place (gratis or for a charge), and offer equivalent access to the
+ Corresponding Source in the same way through the same place at no
+ further charge. You need not require recipients to copy the
+ Corresponding Source along with the object code. If the place to
+ copy the object code is a network server, the Corresponding Source
+ may be on a different server (operated by you or a third party)
+ that supports equivalent copying facilities, provided you maintain
+ clear directions next to the object code saying where to find the
+ Corresponding Source. Regardless of what server hosts the
+ Corresponding Source, you remain obligated to ensure that it is
+ available for as long as needed to satisfy these requirements.
+ e) Convey the object code using peer-to-peer transmission, provided
+ you inform other peers where the object code and Corresponding
+ Source of the work are being offered to the general public at no
+ charge under subsection 6d.
+ A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+ A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling. In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage. For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product. A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+ "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source. The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+ If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information. But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+ The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed. Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+ Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+ 7. Additional Terms.
+ "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law. If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+ When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it. (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.) You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+ Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+ a) Disclaiming warranty or limiting liability differently from the
+ terms of sections 15 and 16 of this License; or
+ b) Requiring preservation of specified reasonable legal notices or
+ author attributions in that material or in the Appropriate Legal
+ Notices displayed by works containing it; or
+ c) Prohibiting misrepresentation of the origin of that material, or
+ requiring that modified versions of such material be marked in
+ reasonable ways as different from the original version; or
+ d) Limiting the use for publicity purposes of names of licensors or
+ authors of the material; or
+ e) Declining to grant rights under trademark law for use of some
+ trade names, trademarks, or service marks; or
+ f) Requiring indemnification of licensors and authors of that
+ material by anyone who conveys the material (or modified versions of
+ it) with contractual assumptions of liability to the recipient, for
+ any liability that these contractual assumptions directly impose on
+ those licensors and authors.
+ All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10. If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term. If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+ If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+ Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+ 8. Termination.
+ You may not propagate or modify a covered work except as expressly
+provided under this License. Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+ However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+ Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+ Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License. If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+ 9. Acceptance Not Required for Having Copies.
+ You are not required to accept this License in order to receive or
+run a copy of the Program. Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance. However,
+nothing other than this License grants you permission to propagate or
+modify any covered work. These actions infringe copyright if you do
+not accept this License. Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+ 10. Automatic Licensing of Downstream Recipients.
+ Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License. You are not responsible
+for enforcing compliance by third parties with this License.
+ An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations. If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+ You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License. For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+ 11. Patents.
+ A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based. The
+work thus licensed is called the contributor's "contributor version".
+ A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version. For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+ Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+ In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement). To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+ If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients. "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+ If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+ A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License. You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+ Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+ 12. No Surrender of Others' Freedom.
+ If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all. For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+ 13. Use with the GNU Affero General Public License.
+ Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work. The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+ 14. Revised Versions of this License.
+ The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+ Each version is given a distinguishing version number. If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation. If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+ If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+ Later license versions may give you additional or different
+permissions. However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+ 15. Disclaimer of Warranty.
+ 16. Limitation of Liability.
+ 17. Interpretation of Sections 15 and 16.
+ If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+ How to Apply These Terms to Your New Programs
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+ <one line to give the program's name and a brief idea of what it does.>
+ Copyright (C) <year> <name of author>
+ This program is free software: you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation, either version 3 of the License, or
+ (at your option) any later version.
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ GNU General Public License for more details.
+ You should have received a copy of the GNU General Public License
+ along with this program. If not, see <>.
+Also add information on how to contact you by electronic and paper mail.
+ If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+ <program> Copyright (C) <year> <name of author>
+ This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+ You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+ The GNU General Public License does not permit incorporating your program
+into proprietary programs. If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library. If this is what you want to do, use the GNU Lesser General
+Public License instead of this License. But first, please read
165 external/gpl3/gcc.old/dist/COPYING3.LIB
@@ -0,0 +1,165 @@
+ Version 3, 29 June 2007
+ Copyright (C) 2007 Free Software Foundation, Inc. <>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+ This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+ 0. Additional Definitions.
+ As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+ "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+ An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+ A "Combined Work" is a work produced by combining or linking an
+Application with the Library. The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+ The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+ The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+ 1. Exception to Section 3 of the GNU GPL.
+ You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+ 2. Conveying Modified Versions.
+ If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+ a) under this License, provided that you make a good faith effort to
+ ensure that, in the event an Application does not supply the
+ function or data, the facility still operates, and performs
+ whatever part of its purpose remains meaningful, or
+ b) under the GNU GPL, with none of the additional permissions of
+ this License applicable to that copy.
+ 3. Object Code Incorporating Material from Library Header Files.
+ The object code form of an Application may incorporate material from
+a header file that is part of the Library. You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+ a) Give prominent notice with each copy of the object code that the
+ Library is used in it and that the Library and its use are
+ covered by this License.
+ b) Accompany the object code with a copy of the GNU GPL and this license
+ document.
+ 4. Combined Works.
+ You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+ a) Give prominent notice with each copy of the Combined Work that
+ the Library is used in it and that the Library and its use are
+ covered by this License.
+ b) Accompany the Combined Work with a copy of the GNU GPL and this license
+ document.
+ c) For a Combined Work that displays copyright notices during
+ execution, include the copyright notice for the Library among
+ these notices, as well as a reference directing the user to the
+ copies of the GNU GPL and this license document.
+ d) Do one of the following:
+ 0) Convey the Minimal Corresponding Source under the terms of this
+ License, and the Corresponding Application Code in a form
+ suitable for, and under terms that permit, the user to
+ recombine or relink the Application with a modified version of
+ the Linked Version to produce a modified Combined Work, in the
+ manner specified by section 6 of the GNU GPL for conveying
+ Corresponding Source.
+ 1) Use a suitable shared library mechanism for linking with the
+ Library. A suitable mechanism is one that (a) uses at run time
+ a copy of the Library already present on the user's computer
+ system, and (b) will operate properly with a modified version
+ of the Library that is interface-compatible with the Linked
+ Version.
+ e) Provide Installation Information, but only if you would otherwise
+ be required to provide such information under section 6 of the
+ GNU GPL, and only to the extent that such information is
+ necessary to install and execute a modified version of the
+ Combined Work produced by recombining or relinking the
+ Application with a modified version of the Linked Version. (If
+ you use option 4d0, the Installation Information must accompany
+ the Minimal Corresponding Source and Corresponding Application
+ Code. If you use option 4d1, you must provide the Installation
+ Information in the manner specified by section 6 of the GNU GPL
+ for conveying Corresponding Source.)
+ 5. Combined Libraries.
+ You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+ a) Accompany the combined library with a copy of the same work based
+ on the Library, uncombined with any other library facilities,
+ conveyed under the terms of this License.
+ b) Give prominent notice with the combined library that part of it
+ is a work based on the Library, and explaining where to find the
+ accompanying uncombined form of the same work.
+ 6. Revised Versions of the GNU Lesser General Public License.
+ The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+ Each version is given a distinguishing version number. If the
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+ If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
0 gnu/dist/gcc4/INSTALL/README → external/gpl3/gcc.old/dist/INSTALL/README
File renamed without changes.
112 external/gpl3/gcc.old/dist/INSTALL/binaries.html
@@ -0,0 +1,112 @@
+<html lang="en">
+<title>Installing GCC: Binaries</title>
+<meta http-equiv="Content-Type" content="text/html">
+<meta name="description" content="Installing GCC: Binaries">
+<meta name="generator" content="makeinfo 4.12">
+<link title="Top" rel="top" href="#Top">
+<link href="" rel="generator-home" title="Texinfo Homepage">
+Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
+1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008,
+2009, 2010, 2011 Free Software Foundation, Inc.
+ Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.2 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, the Front-Cover texts being (a) (see below), and
+with the Back-Cover Texts being (b) (see below). A copy of the
+license is included in the section entitled "GNU Free Documentation License".
+(a) The FSF's Front-Cover Text is:
+ A GNU Manual
+(b) The FSF's Back-Cover Text is:
+ You have freedom to copy and modify this GNU Manual, like GNU
+ software. Copies published by the Free Software Foundation raise
+ funds for GNU development.-->
+<meta http-equiv="Content-Style-Type" content="text/css">
+<style type="text/css"><!--
+ pre.display { font-family:inherit }
+ pre.format { font-family:inherit }
+ pre.smalldisplay { font-family:inherit; font-size:smaller }
+ pre.smallformat { font-family:inherit; font-size:smaller }
+ pre.smallexample { font-size:smaller }
+ pre.smalllisp { font-size:smaller }
+ { font-variant:small-caps }
+ span.roman { font-family:serif; font-weight:normal; }
+ span.sansserif { font-family:sans-serif; font-weight:normal; }
+<h1 class="settitle">Installing GCC: Binaries</h1>
+<a name="index-Binaries-1"></a><a name="index-Installing-GCC_003a-Binaries-2"></a>
+We are often asked about pre-compiled versions of GCC. While we cannot
+provide these for all platforms, below you'll find links to binaries for
+various platforms where creating them by yourself is not easy due to various
+ <p>Please note that we did not create these binaries, nor do we
+support them. If you have any problems installing them, please
+contact their makers.
+ <ul>
+ <ul>
+<li><a href="">Bull's Freeware and Shareware Archive for AIX</a>;
+ <li><a href="">Hudson Valley Community College Open Source Software for IBM System p</a>;
+ <li><a href="">AIX 5L and 6 Open Source Packages</a>.
+ <li>DOS&mdash;<a href="">DJGPP</a>.
+ <li>Renesas H8/300[HS]&mdash;<a href="">GNU Development Tools for the Renesas H8/300[HS] Series</a>.
+ <li>HP-UX:
+ <ul>
+<li><a href="">HP-UX Porting Center</a>;
+ <li><a href="">Binaries for HP-UX 11.00 at Aachen University of Technology</a>.
+ <li><a href="">SCO OpenServer/Unixware</a>.
+ <li>Solaris 2 (SPARC, Intel)&mdash;<a href="">Sunfreeware</a>.
+ <li>SGI&mdash;<a href="">SGI Freeware</a>.
+ <li>Microsoft Windows:
+ <ul>
+<li>The <a href="">Cygwin</a> project;
+<li>The <a href="">MinGW</a> project.
+ <li><a href="">The Written Word</a> offers binaries for
+AIX 4.3.3, 5.1 and 5.2,
+IRIX 6.5,
+Tru64 UNIX 4.0D and 5.1,
+GNU/Linux (i386),
+HP-UX 10.20, 11.00, and 11.11, and
+Solaris/SPARC 2.5.1, 2.6, 7, 8, 9 and 10.
+ <li><a href="">OpenPKG</a> offers binaries for quite a
+number of platforms.
+ <li>The <a href="">GFortran Wiki</a> has
+links to GNU Fortran binaries for several platforms.
+ <p><hr />
+<p><a href="./index.html">Return to the GCC Installation page</a>
+<!-- ***Specific**************************************************************** -->
+<!-- ***Old documentation****************************************************** -->
+<!-- ***GFDL******************************************************************** -->
+<!-- *************************************************************************** -->
+<!-- Part 6 The End of the Document -->
376 external/gpl3/gcc.old/dist/INSTALL/build.html
@@ -0,0 +1,376 @@
+<html lang="en">
+<title>Installing GCC: Building</title>
+<meta http-equiv="Content-Type" content="text/html">
+<meta name="description" content="Installing GCC: Building">
+<meta name="generator" content="makeinfo 4.12">
+<link title="Top" rel="top" href="#Top">
+<link href="" rel="generator-home" title="Texinfo Homepage">
+Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
+1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008,
+2009, 2010, 2011 Free Software Foundation, Inc.
+ Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.2 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, the Front-Cover texts being (a) (see below), and
+with the Back-Cover Texts being (b) (see below). A copy of the
+license is included in the section entitled "GNU Free Documentation License".
+(a) The FSF's Front-Cover Text is:
+ A GNU Manual
+(b) The FSF's Back-Cover Text is:
+ You have freedom to copy and modify this GNU Manual, like GNU
+ software. Copies published by the Free Software Foundation raise
+ funds for GNU development.-->
+<meta http-equiv="Content-Style-Type" content="text/css">
+<style type="text/css"><!--
+ pre.display { font-family:inherit }
+ pre.format { font-family:inherit }
+ pre.smalldisplay { font-family:inherit; font-size:smaller }
+ pre.smallformat { font-family:inherit; font-size:smaller }
+ pre.smallexample { font-size:smaller }
+ pre.smalllisp { font-size:smaller }
+ { font-variant:small-caps }
+ span.roman { font-family:serif; font-weight:normal; }
+ span.sansserif { font-family:sans-serif; font-weight:normal; }
+<h1 class="settitle">Installing GCC: Building</h1>
+<a name="index-Installing-GCC_003a-Building-1"></a>
+Now that GCC is configured, you are ready to build the compiler and
+runtime libraries.
+ <p>Some commands executed when making the compiler may fail (return a
+nonzero status) and be ignored by <samp><span class="command">make</span></samp>. These failures, which
+are often due to files that were not found, are expected, and can safely
+be ignored.
+ <p>It is normal to have compiler warnings when compiling certain files.
+Unless you are a GCC developer, you can generally ignore these warnings
+unless they cause compilation to fail. Developers should attempt to fix
+any warnings encountered, however they can temporarily continue past
+warnings-as-errors by specifying the configure flag
+<samp><span class="option">--disable-werror</span></samp>.
+ <p>On certain old systems, defining certain environment variables such as
+<samp><span class="env">CC</span></samp> can interfere with the functioning of <samp><span class="command">make</span></samp>.
+ <p>If you encounter seemingly strange errors when trying to build the
+compiler in a directory other than the source directory, it could be
+because you have previously configured the compiler in the source
+directory. Make sure you have done all the necessary preparations.
+ <p>If you build GCC on a BSD system using a directory stored in an old System
+V file system, problems may occur in running <samp><span class="command">fixincludes</span></samp> if the
+System V file system doesn't support symbolic links. These problems
+result in a failure to fix the declaration of <code>size_t</code> in
+<samp><span class="file">sys/types.h</span></samp>. If you find that <code>size_t</code> is a signed type and
+that type mismatches occur, this could be the cause.
+ <p>The solution is not to use such a directory for building GCC.
+ <p>Similarly, when building from SVN or snapshots, or if you modify
+<samp><span class="file">*.l</span></samp> files, you need the Flex lexical analyzer generator
+installed. If you do not modify <samp><span class="file">*.l</span></samp> files, releases contain
+the Flex-generated files and you do not need Flex installed to build
+them. There is still one Flex-based lexical analyzer (part of the
+build machinery, not of GCC itself) that is used even if you only
+build the C front end.
+ <p>When building from SVN or snapshots, or if you modify Texinfo
+documentation, you need version 4.7 or later of Texinfo installed if you
+want Info documentation to be regenerated. Releases contain Info
+documentation pre-built for the unmodified documentation in the release.
+<h3 class="section"><a name="TOC0"></a>Building a native compiler</h3>
+<p>For a native build, the default configuration is to perform
+a 3-stage bootstrap of the compiler when &lsquo;<samp><span class="samp">make</span></samp>&rsquo; is invoked.
+This will build the entire GCC system and ensure that it compiles
+itself correctly. It can be disabled with the <samp><span class="option">--disable-bootstrap</span></samp>
+parameter to &lsquo;<samp><span class="samp">configure</span></samp>&rsquo;, but bootstrapping is suggested because
+the compiler will be tested more completely and could also have
+better performance.
+ <p>The bootstrapping process will complete the following steps:
+ <ul>
+<li>Build tools necessary to build the compiler.
+ <li>Perform a 3-stage bootstrap of the compiler. This includes building
+three times the target tools for use by the compiler such as binutils
+(bfd, binutils, gas, gprof, ld, and opcodes) if they have been
+individually linked or moved into the top level GCC source tree before
+ <li>Perform a comparison test of the stage2 and stage3 compilers.
+ <li>Build runtime libraries using the stage3 compiler from the previous step.
+ </ul>
+ <p>If you are short on disk space you might consider &lsquo;<samp><span class="samp">make
+bootstrap-lean</span></samp>&rsquo; instead. The sequence of compilation is the
+same described above, but object files from the stage1 and
+stage2 of the 3-stage bootstrap of the compiler are deleted as
+soon as they are no longer needed.
+ <p>If you wish to use non-default GCC flags when compiling the stage2
+and stage3 compilers, set <code>BOOT_CFLAGS</code> on the command line when
+doing &lsquo;<samp><span class="samp">make</span></samp>&rsquo;. For example, if you want to save additional space
+during the bootstrap and in the final installation as well, you can
+build the compiler binaries without debugging information as in the
+following example. This will save roughly 40% of disk space both for
+the bootstrap and the final installation. (Libraries will still contain
+debugging information.)
+<pre class="smallexample"> make BOOT_CFLAGS='-O' bootstrap
+ <p>You can place non-default optimization flags into <code>BOOT_CFLAGS</code>; they
+are less well tested here than the default of &lsquo;<samp><span class="samp">-g -O2</span></samp>&rsquo;, but should
+still work. In a few cases, you may find that you need to specify special
+flags such as <samp><span class="option">-msoft-float</span></samp> here to complete the bootstrap; or,
+if the native compiler miscompiles the stage1 compiler, you may need
+to work around this, by choosing <code>BOOT_CFLAGS</code> to avoid the parts
+of the stage1 compiler that were miscompiled, or by using &lsquo;<samp><span class="samp">make
+bootstrap4</span></samp>&rsquo; to increase the number of stages of bootstrap.
+ <p><code>BOOT_CFLAGS</code> does not apply to bootstrapped target libraries.
+Since these are always compiled with the compiler currently being
+bootstrapped, you can use <code>CFLAGS_FOR_TARGET</code> to modify their
+compilation flags, as for non-bootstrapped target libraries.
+Again, if the native compiler miscompiles the stage1 compiler, you may
+need to work around this by avoiding non-working parts of the stage1
+compiler. Use <code>STAGE1_TFLAGS</code> to this end.
+ <p>If you used the flag <samp><span class="option">--enable-languages=...</span></samp> to restrict
+the compilers to be built, only those you've actually enabled will be
+built. This will of course only build those runtime libraries, for
+which the particular compiler has been built. Please note,
+that re-defining <samp><span class="env">LANGUAGES</span></samp> when calling &lsquo;<samp><span class="samp">make</span></samp>&rsquo;
+<strong>does not</strong> work anymore!
+ <p>If the comparison of stage2 and stage3 fails, this normally indicates
+that the stage2 compiler has compiled GCC incorrectly, and is therefore
+a potentially serious bug which you should investigate and report. (On
+a few systems, meaningful comparison of object files is impossible; they
+always appear &ldquo;different&rdquo;. If you encounter this problem, you will
+need to disable comparison in the <samp><span class="file">Makefile</span></samp>.)
+ <p>If you do not want to bootstrap your compiler, you can configure with
+<samp><span class="option">--disable-bootstrap</span></samp>. In particular cases, you may want to
+bootstrap your compiler even if the target system is not the same as
+the one you are building on: for example, you could build a
+<code>powerpc-unknown-linux-gnu</code> toolchain on a
+<code>powerpc64-unknown-linux-gnu</code> host. In this case, pass
+<samp><span class="option">--enable-bootstrap</span></samp> to the configure script.
+ <p><code>BUILD_CONFIG</code> can be used to bring in additional customization
+to the build. It can be set to a whitespace-separated list of names.
+For each such <code>NAME</code>, top-level <samp><span class="file">config/</span><code>NAME</code><span class="file">.mk</span></samp> will
+be included by the top-level <samp><span class="file">Makefile</span></samp>, bringing in any settings
+it contains. The default <code>BUILD_CONFIG</code> can be set using the
+configure option <samp><span class="option">--with-build-config=</span><code>NAME</code><span class="option">...</span></samp>. Some
+examples of supported build configurations are:
+ <dl>
+<dt>&lsquo;<samp><span class="samp">bootstrap-O1</span></samp>&rsquo;<dd>Removes any <samp><span class="option">-O</span></samp>-started option from <code>BOOT_CFLAGS</code>, and adds
+<samp><span class="option">-O1</span></samp> to it. &lsquo;<samp><span class="samp">BUILD_CONFIG=bootstrap-O1</span></samp>&rsquo; is equivalent to
+&lsquo;<samp><span class="samp">BOOT_CFLAGS='-g -O1'</span></samp>&rsquo;.
+ <br><dt>&lsquo;<samp><span class="samp">bootstrap-O3</span></samp>&rsquo;<dd>Analogous to <code>bootstrap-O1</code>.
+ <br><dt>&lsquo;<samp><span class="samp">bootstrap-debug</span></samp>&rsquo;<dd>Verifies that the compiler generates the same executable code, whether
+or not it is asked to emit debug information. To this end, this
+option builds stage2 host programs without debug information, and uses
+<samp><span class="file">contrib/compare-debug</span></samp> to compare them with the stripped stage3
+object files. If <code>BOOT_CFLAGS</code> is overridden so as to not enable
+debug information, stage2 will have it, and stage3 won't. This option
+is enabled by default when GCC bootstrapping is enabled, if
+<code>strip</code> can turn object files compiled with and without debug
+info into identical object files. In addition to better test
+coverage, this option makes default bootstraps faster and leaner.
+ <br><dt>&lsquo;<samp><span class="samp">bootstrap-debug-big</span></samp>&rsquo;<dd>Rather than comparing stripped object files, as in
+<code>bootstrap-debug</code>, this option saves internal compiler dumps
+during stage2 and stage3 and compares them as well, which helps catch
+additional potential problems, but at a great cost in terms of disk
+space. It can be specified in addition to &lsquo;<samp><span class="samp">bootstrap-debug</span></samp>&rsquo;.
+ <br><dt>&lsquo;<samp><span class="samp">bootstrap-debug-lean</span></samp>&rsquo;<dd>This option saves disk space compared with <code>bootstrap-debug-big</code>,
+but at the expense of some recompilation. Instead of saving the dumps
+of stage2 and stage3 until the final compare, it uses
+<samp><span class="option">-fcompare-debug</span></samp> to generate, compare and remove the dumps
+during stage3, repeating the compilation that already took place in
+stage2, whose dumps were not saved.
+ <br><dt>&lsquo;<samp><span class="samp">bootstrap-debug-lib</span></samp>&rsquo;<dd>This option tests executable code invariance over debug information
+generation on target libraries, just like <code>bootstrap-debug-lean</code>
+tests it on host programs. It builds stage3 libraries with
+<samp><span class="option">-fcompare-debug</span></samp>, and it can be used along with any of the
+<code>bootstrap-debug</code> options above.
+ <p>There aren't <code>-lean</code> or <code>-big</code> counterparts to this option
+because most libraries are only build in stage3, so bootstrap compares
+would not get significant coverage. Moreover, the few libraries built
+in stage2 are used in stage3 host programs, so we wouldn't want to
+compile stage2 libraries with different options for comparison purposes.
+ <br><dt>&lsquo;<samp><span class="samp">bootstrap-debug-ckovw</span></samp>&rsquo;<dd>Arranges for error messages to be issued if the compiler built on any
+stage is run without the option <samp><span class="option">-fcompare-debug</span></samp>. This is
+useful to verify the full <samp><span class="option">-fcompare-debug</span></samp> testing coverage. It
+must be used along with <code>bootstrap-debug-lean</code> and
+ <br><dt>&lsquo;<samp><span class="samp">bootstrap-time</span></samp>&rsquo;<dd>Arranges for the run time of each program started by the GCC driver,
+built in any stage, to be logged to <samp><span class="file">time.log</span></samp>, in the top level of
+the build tree.
+ </dl>
+<h3 class="section"><a name="TOC1"></a>Building a cross compiler</h3>
+<p>When building a cross compiler, it is not generally possible to do a
+3-stage bootstrap of the compiler. This makes for an interesting problem
+as parts of GCC can only be built with GCC.
+ <p>To build a cross compiler, we recommend first building and installing a
+native compiler. You can then use the native GCC compiler to build the
+cross compiler. The installed native compiler needs to be GCC version
+2.95 or later.
+ <p>If the cross compiler is to be built with support for the Java
+programming language and the ability to compile .java source files is
+desired, the installed native compiler used to build the cross
+compiler needs to be the same GCC version as the cross compiler. In
+addition the cross compiler needs to be configured with
+<samp><span class="option">--with-ecj-jar=...</span></samp>.
+ <p>Assuming you have already installed a native copy of GCC and configured
+your cross compiler, issue the command <samp><span class="command">make</span></samp>, which performs the
+following steps:
+ <ul>
+<li>Build host tools necessary to build the compiler.
+ <li>Build target tools for use by the compiler such as binutils (bfd,
+binutils, gas, gprof, ld, and opcodes)
+if they have been individually linked or moved into the top level GCC source
+tree before configuring.
+ <li>Build the compiler (single stage only).
+ <li>Build runtime libraries using the compiler from the previous step.
+ <p>Note that if an error occurs in any step the make process will exit.
+ <p>If you are not building GNU binutils in the same source tree as GCC,
+you will need a cross-assembler and cross-linker installed before
+configuring GCC. Put them in the directory
+<samp><var>prefix</var><span class="file">/</span><var>target</var><span class="file">/bin</span></samp>. Here is a table of the tools
+you should put in this directory:
+ <dl>
+<dt><samp><span class="file">as</span></samp><dd>This should be the cross-assembler.
+ <br><dt><samp><span class="file">ld</span></samp><dd>This should be the cross-linker.
+ <br><dt><samp><span class="file">ar</span></samp><dd>This should be the cross-archiver: a program which can manipulate
+archive files (linker libraries) in the target machine's format.
+ <br><dt><samp><span class="file">ranlib</span></samp><dd>This should be a program to construct a symbol table in an archive file.
+ <p>The installation of GCC will find these programs in that directory,
+and copy or link them to the proper place to for the cross-compiler to
+find them when run later.
+ <p>The easiest way to provide these files is to build the Binutils package.
+Configure it with the same <samp><span class="option">--host</span></samp> and <samp><span class="option">--target</span></samp>
+options that you use for configuring GCC, then build and install
+them. They install their executables automatically into the proper
+directory. Alas, they do not support all the targets that GCC
+ <p>If you are not building a C library in the same source tree as GCC,
+you should also provide the target libraries and headers before
+configuring GCC, specifying the directories with
+<samp><span class="option">--with-sysroot</span></samp> or <samp><span class="option">--with-headers</span></samp> and
+<samp><span class="option">--with-libs</span></samp>. Many targets also require &ldquo;start files&rdquo; such
+as <samp><span class="file">crt0.o</span></samp> and
+<samp><span class="file">crtn.o</span></samp> which are linked into each executable. There may be several
+alternatives for <samp><span class="file">crt0.o</span></samp>, for use with profiling or other
+compilation options. Check your target's definition of
+<code>STARTFILE_SPEC</code> to find out what start files it uses.
+<h3 class="section"><a name="TOC2"></a>Building in parallel</h3>
+<p>GNU Make 3.80 and above, which is necessary to build GCC, support
+building in parallel. To activate this, you can use &lsquo;<samp><span class="samp">make -j 2</span></samp>&rsquo;
+instead of &lsquo;<samp><span class="samp">make</span></samp>&rsquo;. You can also specify a bigger number, and
+in most cases using a value greater than the number of processors in
+your machine will result in fewer and shorter I/O latency hits, thus
+improving overall throughput; this is especially true for slow drives
+and network filesystems.
+<h3 class="section"><a name="TOC3"></a>Building the Ada compiler</h3>
+<p>In order to build GNAT, the Ada compiler, you need a working GNAT
+compiler (GCC version 3.4 or later).
+This includes GNAT tools such as <samp><span class="command">gnatmake</span></samp> and
+<samp><span class="command">gnatlink</span></samp>, since the Ada front end is written in Ada and
+uses some GNAT-specific extensions.
+ <p>In order to build a cross compiler, it is suggested to install
+the new compiler as native first, and then use it to build the cross
+ <p><samp><span class="command">configure</span></samp> does not test whether the GNAT installation works
+and has a sufficiently recent version; if too old a GNAT version is
+installed, the build will fail unless <samp><span class="option">--enable-languages</span></samp> is
+used to disable building the Ada front end.
+ <p><samp><span class="env">ADA_INCLUDE_PATH</span></samp> and <samp><span class="env">ADA_OBJECT_PATH</span></samp> environment variables
+must not be set when building the Ada compiler, the Ada tools, or the
+Ada runtime libraries. You can check that your build environment is clean
+by verifying that &lsquo;<samp><span class="samp">gnatls -v</span></samp>&rsquo; lists only one explicit path in each
+<h3 class="section"><a name="TOC4"></a>Building with profile feedback</h3>
+<p>It is possible to use profile feedback to optimize the compiler itself. This
+should result in a faster compiler binary. Experiments done on x86 using gcc
+3.3 showed approximately 7 percent speedup on compiling C programs. To
+bootstrap the compiler with profile feedback, use <code>make profiledbootstrap</code>.
+ <p>When &lsquo;<samp><span class="samp">make profiledbootstrap</span></samp>&rsquo; is run, it will first build a <code>stage1</code>
+compiler. This compiler is used to build a <code>stageprofile</code> compiler
+instrumented to collect execution counts of instruction and branch
+probabilities. Then runtime libraries are compiled with profile collected.
+Finally a <code>stagefeedback</code> compiler is built using the information collected.
+ <p>Unlike standard bootstrap, several additional restrictions apply. The
+compiler used to build <code>stage1</code> needs to support a 64-bit integral type.
+It is recommended to only use GCC for this. Also parallel make is currently
+not supported since collisions in profile collecting may occur.
+ <p><hr />
+<p><a href="./index.html">Return to the GCC Installation page</a>
+<!-- ***Testing***************************************************************** -->
+<!-- ***Final install*********************************************************** -->
+<!-- ***Binaries**************************************************************** -->
+<!-- ***Specific**************************************************************** -->
+<!-- ***Old documentation****************************************************** -->
+<!-- ***GFDL******************************************************************** -->
+<!-- *************************************************************************** -->
+<!-- Part 6 The End of the Document -->
1,209 external/gpl3/gcc.old/dist/INSTALL/configure.html
@@ -0,0 +1,1209 @@
+<html lang="en">
+<title>Installing GCC: Configuration</title>
+<meta http-equiv="Content-Type" content="text/html">
+<meta name="description" content="Installing GCC: Configuration">
+<meta name="generator" content="makeinfo 4.12">
+<link title="Top" rel="top" href="#Top">
+<link href="" rel="generator-home" title="Texinfo Homepage">
+Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
+1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008,
+2009, 2010, 2011 Free Software Foundation, Inc.
+ Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.2 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, the Front-Cover texts being (a) (see below), and
+with the Back-Cover Texts being (b) (see below). A copy of the
+license is included in the section entitled "GNU Free Documentation License".
+(a) The FSF's Front-Cover Text is:
+ A GNU Manual
+(b) The FSF's Back-Cover Text is:
+ You have freedom to copy and modify this GNU Manual, like GNU
+ software. Copies published by the Free Software Foundation raise
+ funds for GNU development.-->
+<meta http-equiv="Content-Style-Type" content="text/css">
+<style type="text/css"><!--
+ pre.display { font-family:inherit }
+ pre.format { font-family:inherit }
+ pre.smalldisplay { font-family:inherit; font-size:smaller }
+ pre.smallformat { font-family:inherit; font-size:smaller }
+ pre.smallexample { font-size:smaller }
+ pre.smalllisp { font-size:smaller }
+ { font-variant:small-caps }
+ span.roman { font-family:serif; font-weight:normal; }
+ span.sansserif { font-family:sans-serif; font-weight:normal; }
+<h1 class="settitle">Installing GCC: Configuration</h1>
+<a name="index-Configuration-1"></a><a name="index-Installing-GCC_003a-Configuration-2"></a>
+Like most GNU software, GCC must be configured before it can be built.
+This document describes the recommended configuration procedure
+for both native and cross targets.
+ <p>We use <var>srcdir</var> to refer to the toplevel source directory for
+GCC; we use <var>objdir</var> to refer to the toplevel build/object directory.
+ <p>If you obtained the sources via SVN, <var>srcdir</var> must refer to the top
+<samp><span class="file">gcc</span></samp> directory, the one where the <samp><span class="file">MAINTAINERS</span></samp> file can be
+found, and not its <samp><span class="file">gcc</span></samp> subdirectory, otherwise the build will fail.
+ <p>If either <var>srcdir</var> or <var>objdir</var> is located on an automounted NFS
+file system, the shell's built-in <samp><span class="command">pwd</span></samp> command will return
+temporary pathnames. Using these can lead to various sorts of build
+problems. To avoid this issue, set the <samp><span class="env">PWDCMD</span></samp> environment
+variable to an automounter-aware <samp><span class="command">pwd</span></samp> command, e.g.,
+<samp><span class="command">pawd</span></samp> or &lsquo;<samp><span class="samp">amq -w</span></samp>&rsquo;, during the configuration and build
+ <p>First, we <strong>highly</strong> recommend that GCC be built into a
+separate directory from the sources which does <strong>not</strong> reside
+within the source tree. This is how we generally build GCC; building
+where <var>srcdir</var> == <var>objdir</var> should still work, but doesn't
+get extensive testing; building where <var>objdir</var> is a subdirectory
+of <var>srcdir</var> is unsupported.
+ <p>If you have previously built GCC in the same directory for a
+different target machine, do &lsquo;<samp><span class="samp">make distclean</span></samp>&rsquo; to delete all files
+that might be invalid. One of the files this deletes is <samp><span class="file">Makefile</span></samp>;
+if &lsquo;<samp><span class="samp">make distclean</span></samp>&rsquo; complains that <samp><span class="file">Makefile</span></samp> does not exist
+or issues a message like &ldquo;don't know how to make distclean&rdquo; it probably
+means that the directory is already suitably clean. However, with the
+recommended method of building in a separate <var>objdir</var>, you should
+simply use a different <var>objdir</var> for each target.
+ <p>Second, when configuring a native system, either <samp><span class="command">cc</span></samp> or
+<samp><span class="command">gcc</span></samp> must be in your path or you must set <samp><span class="env">CC</span></samp> in
+your environment before running configure. Otherwise the configuration
+scripts may fail.
+ <p>To configure GCC:
+<pre class="smallexample"> % mkdir <var>objdir</var>
+ % cd <var>objdir</var>
+ % <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>]
+ <h3 class="heading"><a name="TOC0"></a>Distributor options</h3>
+<p>If you will be distributing binary versions of GCC, with modifications
+to the source code, you should use the options described in this
+section to make clear that your version contains modifications.
+ <dl>
+<dt><code>--with-pkgversion=</code><var>version</var><dd>Specify a string that identifies your package. You may wish
+to include a build number or build date. This version string will be
+included in the output of <samp><span class="command">gcc --version</span></samp>. This suffix does
+not replace the default version string, only the &lsquo;<samp><span class="samp">GCC</span></samp>&rsquo; part.
+ <p>The default value is &lsquo;<samp><span class="samp">GCC</span></samp>&rsquo;.
+ <br><dt><code>--with-bugurl=</code><var>url</var><dd>Specify the URL that users should visit if they wish to report a bug.
+You are of course welcome to forward bugs reported to you to the FSF,
+if you determine that they are not bugs in your modifications.
+ <p>The default value refers to the FSF's GCC bug tracker.
+ </dl>
+<h3 class="heading"><a name="TOC1"></a>Target specification</h3>
+ <ul>
+<li>GCC has code to correctly determine the correct value for <var>target</var>
+for nearly all native systems. Therefore, we highly recommend you do
+not provide a configure target when configuring a native compiler.
+ <li><var>target</var> must be specified as <samp><span class="option">--target=</span><var>target</var></samp>
+when configuring a cross compiler; examples of valid targets would be
+m68k-elf, sh-elf, etc.
+ <li>Specifying just <var>target</var> instead of <samp><span class="option">--target=</span><var>target</var></samp>
+implies that the host defaults to <var>target</var>.
+<h3 class="heading"><a name="TOC2"></a>Options specification</h3>
+<p>Use <var>options</var> to override several configure time options for
+GCC. A list of supported <var>options</var> follows; &lsquo;<samp><span class="samp">configure
+--help</span></samp>&rsquo; may list other options, but those not listed below may not
+work and should not normally be used.
+ <p>Note that each <samp><span class="option">--enable</span></samp> option has a corresponding
+<samp><span class="option">--disable</span></samp> option and that each <samp><span class="option">--with</span></samp> option has a
+corresponding <samp><span class="option">--without</span></samp> option.
+ <dl>
+<dt><code>--prefix=</code><var>dirname</var><dd>Specify the toplevel installation
+directory. This is the recommended way to install the tools into a directory
+other than the default. The toplevel installation directory defaults to
+<samp><span class="file">/usr/local</span></samp>.
+ <p>We <strong>highly</strong> recommend against <var>dirname</var> being the same or a
+subdirectory of <var>objdir</var> or vice versa. If specifying a directory
+beneath a user's home directory tree, some shells will not expand
+<var>dirname</var> correctly if it contains the &lsquo;<samp><span class="samp">~</span></samp>&rsquo; metacharacter; use
+<samp><span class="env">$HOME</span></samp> instead.
+ <p>The following standard <samp><span class="command">autoconf</span></samp> options are supported. Normally you
+should not need to use these options.
+ <dl>
+<dt><code>--exec-prefix=</code><var>dirname</var><dd>Specify the toplevel installation directory for architecture-dependent
+files. The default is <samp><var>prefix</var></samp>.
+ <br><dt><code>--bindir=</code><var>dirname</var><dd>Specify the installation directory for the executables called by users
+(such as <samp><span class="command">gcc</span></samp> and <samp><span class="command">g++</span></samp>). The default is
+<samp><var>exec-prefix</var><span class="file">/bin</span></samp>.
+ <br><dt><code>--libdir=</code><var>dirname</var><dd>Specify the installation directory for object code libraries and
+internal data files of GCC. The default is <samp><var>exec-prefix</var><span class="file">/lib</span></samp>.
+ <br><dt><code>--libexecdir=</code><var>dirname</var><dd>Specify the installation directory for internal executables of GCC.
+The default is <samp><var>exec-prefix</var><span class="file">/libexec</span></samp>.
+ <br><dt><code>--with-slibdir=</code><var>dirname</var><dd>Specify the installation directory for the shared libgcc library. The
+default is <samp><var>libdir</var></samp>.
+ <br><dt><code>--datarootdir=</code><var>dirname</var><dd>Specify the root of the directory tree for read-only architecture-independent
+data files referenced by GCC. The default is <samp><var>prefix</var><span class="file">/share</span></samp>.
+ <br><dt><code>--infodir=</code><var>dirname</var><dd>Specify the installation directory for documentation in info format.
+The default is <samp><var>datarootdir</var><span class="file">/info</span></samp>.
+ <br><dt><code>--datadir=</code><var>dirname</var><dd>Specify the installation directory for some architecture-independent
+data files referenced by GCC. The default is <samp><var>datarootdir</var></samp>.
+ <br><dt><code>--docdir=</code><var>dirname</var><dd>Specify the installation directory for documentation files (other
+than Info) for GCC. The default is <samp><var>datarootdir</var><span class="file">/doc</span></samp>.
+ <br><dt><code>--htmldir=</code><var>dirname</var><dd>Specify the installation directory for HTML documentation files.
+The default is <samp><var>docdir</var></samp>.
+ <br><dt><code>--pdfdir=</code><var>dirname</var><dd>Specify the installation directory for PDF documentation files.
+The default is <samp><var>docdir</var></samp>.
+ <br><dt><code>--mandir=</code><var>dirname</var><dd>Specify the installation directory for manual pages. The default is
+<samp><var>datarootdir</var><span class="file">/man</span></samp>. (Note that the manual pages are only extracts
+from the full GCC manuals, which are provided in Texinfo format. The manpages
+are derived by an automatic conversion process from parts of the full
+ <br><dt><code>--with-gxx-include-dir=</code><var>dirname</var><dd>Specify
+the installation directory for G++ header files. The default depends
+on other configuration options, and differs between cross and native
+ </dl>
+ <br><dt><code>--program-prefix=</code><var>prefix</var><dd>GCC supports some transformations of the names of its programs when
+installing them. This option prepends <var>prefix</var> to the names of
+programs to install in <var>bindir</var> (see above). For example, specifying
+<samp><span class="option">--program-prefix=foo-</span></samp> would result in &lsquo;<samp><span class="samp">gcc</span></samp>&rsquo;
+being installed as <samp><span class="file">/usr/local/bin/foo-gcc</span></samp>.
+ <br><dt><code>--program-suffix=</code><var>suffix</var><dd>Appends <var>suffix</var> to the names of programs to install in <var>bindir</var>
+(see above). For example, specifying <samp><span class="option">--program-suffix=-3.1</span></samp>
+would result in &lsquo;<samp><span class="samp">gcc</span></samp>&rsquo; being installed as
+<samp><span class="file">/usr/local/bin/gcc-3.1</span></samp>.
+ <br><dt><code>--program-transform-name=</code><var>pattern</var><dd>Applies the &lsquo;<samp><span class="samp">sed</span></samp>&rsquo; script <var>pattern</var> to be applied to the names
+of programs to install in <var>bindir</var> (see above). <var>pattern</var> has to
+consist of one or more basic &lsquo;<samp><span class="samp">sed</span></samp>&rsquo; editing commands, separated by
+semicolons. For example, if you want the &lsquo;<samp><span class="samp">gcc</span></samp>&rsquo; program name to be
+transformed to the installed program <samp><span class="file">/usr/local/bin/myowngcc</span></samp> and
+the &lsquo;<samp><span class="samp">g++</span></samp>&rsquo; program name to be transformed to
+<samp><span class="file">/usr/local/bin/gspecial++</span></samp> without changing other program names,
+you could use the pattern
+<samp><span class="option">--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'</span></samp>
+to achieve this effect.
+ <p>All three options can be combined and used together, resulting in more
+complex conversion patterns. As a basic rule, <var>prefix</var> (and
+<var>suffix</var>) are prepended (appended) before further transformations
+can happen with a special transformation script <var>pattern</var>.
+ <p>As currently implemented, this option only takes effect for native
+builds; cross compiler binaries' names are not transformed even when a
+transformation is explicitly asked for by one of these options.
+ <p>For native builds, some of the installed programs are also installed
+with the target alias in front of their name, as in
+&lsquo;<samp><span class="samp">i686-pc-linux-gnu-gcc</span></samp>&rsquo;. All of the above transformations happen
+before the target alias is prepended to the name&mdash;so, specifying
+<samp><span class="option">--program-prefix=foo-</span></samp> and <samp><span class="option">program-suffix=-3.1</span></samp>, the
+resulting binary would be installed as
+<samp><span class="file">/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1</span></samp>.
+ <p>As a last shortcoming, none of the installed Ada programs are
+transformed yet, which will be fixed in some time.
+ <br><dt><code>--with-local-prefix=</code><var>dirname</var><dd>Specify the
+installation directory for local include files. The default is
+<samp><span class="file">/usr/local</span></samp>. Specify this option if you want the compiler to
+search directory <samp><var>dirname</var><span class="file">/include</span></samp> for locally installed
+header files <em>instead</em> of <samp><span class="file">/usr/local/include</span></samp>.
+ <p>You should specify <samp><span class="option">--with-local-prefix</span></samp> <strong>only</strong> if your
+site has a different convention (not <samp><span class="file">/usr/local</span></samp>) for where to put
+site-specific files.
+ <p>The default value for <samp><span class="option">--with-local-prefix</span></samp> is <samp><span class="file">/usr/local</span></samp>
+regardless of the value of <samp><span class="option">--prefix</span></samp>. Specifying
+<samp><span class="option">--prefix</span></samp> has no effect on which directory GCC searches for
+local header files. This may seem counterintuitive, but actually it is
+ <p>The purpose of <samp><span class="option">--prefix</span></samp> is to specify where to <em>install
+GCC</em>. The local header files in <samp><span class="file">/usr/local/include</span></samp>&mdash;if you put
+any in that directory&mdash;are not part of GCC. They are part of other
+programs&mdash;perhaps many others. (GCC installs its own header files in
+another directory which is based on the <samp><span class="option">--prefix</span></samp> value.)
+ <p>Both the local-prefix include directory and the GCC-prefix include
+directory are part of GCC's &ldquo;system include&rdquo; directories. Although these
+two directories are not fixed, they need to be searched in the proper
+order for the correct processing of the include_next directive. The
+local-prefix include directory is searched before the GCC-prefix
+include directory. Another characteristic of system include directories
+is that pedantic warnings are turned off for headers in these directories.
+ <p>Some autoconf macros add <samp><span class="option">-I </span><var>directory</var></samp> options to the
+compiler command line, to ensure that directories containing installed
+packages' headers are searched. When <var>directory</var> is one of GCC's
+system include directories, GCC will ignore the option so that system
+directories continue to be processed in the correct order. This
+may result in a search order different from what was specified but the
+directory will still be searched.
+ <p>GCC automatically searches for ordinary libraries using
+<samp><span class="env">GCC_EXEC_PREFIX</span></samp>. Thus, when the same installation prefix is
+used for both GCC and packages, GCC will automatically search for
+both headers and libraries. This provides a configuration that is
+easy to use. GCC behaves in a manner similar to that when it is
+installed as a system compiler in <samp><span class="file">/usr</span></samp>.
+ <p>Sites that need to install multiple versions of GCC may not want to
+use the above simple configuration. It is possible to use the
+<samp><span class="option">--program-prefix</span></samp>, <samp><span class="option">--program-suffix</span></samp> and
+<samp><span class="option">--program-transform-name</span></samp> options to install multiple versions
+into a single directory, but it may be simpler to use different prefixes
+and the <samp><span class="option">--with-local-prefix</span></samp> option to specify the location of the
+site-specific files for each version. It will then be necessary for
+users to specify explicitly the location of local site libraries
+(e.g., with <samp><span class="env">LIBRARY_PATH</span></samp>).
+ <p>The same value can be used for both <samp><span class="option">--with-local-prefix</span></samp> and
+<samp><span class="option">--prefix</span></samp> provided it is not <samp><span class="file">/usr</span></samp>. This can be used
+to avoid the default search of <samp><span class="file">/usr/local/include</span></samp>.
+ <p><strong>Do not</strong> specify <samp><span class="file">/usr</span></samp> as the <samp><span class="option">--with-local-prefix</span></samp>!
+The directory you use for <samp><span class="option">--with-local-prefix</span></samp> <strong>must not</strong>
+contain any of the system's standard header files. If it did contain
+them, certain programs would be miscompiled (including GNU Emacs, on
+certain targets), because this would override and nullify the header
+file corrections made by the <samp><span class="command">fixincludes</span></samp> script.
+ <p>Indications are that people who use this option use it based on mistaken
+ideas of what it is for. People use it as if it specified where to
+install part of GCC. Perhaps they make this assumption because
+installing GCC creates the directory.
+ <br><dt><code>--enable-shared[=</code><var>package</var><code>[,...]]</code><dd>Build shared versions of libraries, if shared libraries are supported on
+the target platform. Unlike GCC 2.95.x and earlier, shared libraries
+are enabled by default on all platforms that support shared libraries.
+ <p>If a list of packages is given as an argument, build shared libraries
+only for the listed packages. For other packages, only static libraries
+will be built. Package names currently recognized in the GCC tree are
+&lsquo;<samp><span class="samp">libgcc</span></samp>&rsquo; (also known as &lsquo;<samp><span class="samp">gcc</span></samp>&rsquo;), &lsquo;<samp><span class="samp">libstdc++</span></samp>&rsquo; (not
+&lsquo;<samp><span class="samp">libstdc++-v3</span></samp>&rsquo;), &lsquo;<samp><span class="samp">libffi</span></samp>&rsquo;, &lsquo;<samp><span class="samp">zlib</span></samp>&rsquo;, &lsquo;<samp><span class="samp">boehm-gc</span></samp>&rsquo;,
+&lsquo;<samp><span class="samp">ada</span></samp>&rsquo;, &lsquo;<samp><span class="samp">libada</span></samp>&rsquo;, &lsquo;<samp><span class="samp">libjava</span></samp>&rsquo; and &lsquo;<samp><span class="samp">libobjc</span></samp>&rsquo;.
+Note &lsquo;<samp><span class="samp">libiberty</span></samp>&rsquo; does not support shared libraries at all.
+ <p>Use <samp><span class="option">--disable-shared</span></samp> to build only static libraries. Note that
+<samp><span class="option">--disable-shared</span></samp> does not accept a list of package names as
+argument, only <samp><span class="option">--enable-shared</span></samp> does.
+ <br><dt><code><a name="with_002dgnu_002das"></a>--with-gnu-as</code><dd>Specify that the compiler should assume that the
+assembler it finds is the GNU assembler. However, this does not modify
+the rules to find an assembler and will result in confusion if the
+assembler found is not actually the GNU assembler. (Confusion may also
+result if the compiler finds the GNU assembler but has not been
+configured with <samp><span class="option">--with-gnu-as</span></samp>.) If you have more than one
+assembler installed on your system, you may want to use this option in
+connection with <samp><span class="option">--with-as=</span><var>pathname</var></samp> or
+<samp><span class="option">--with-build-time-tools=</span><var>pathname</var></samp>.
+ <p>The following systems are the only ones where it makes a difference
+whether you use the GNU assembler. On any other system,
+<samp><span class="option">--with-gnu-as</span></samp> has no effect.
+ <ul>
+<li>&lsquo;<samp><span class="samp">hppa1.0-</span><var>any</var><span class="samp">-</span><var>any</var></samp>&rsquo;
+<li>&lsquo;<samp><span class="samp">hppa1.1-</span><var>any</var><span class="samp">-</span><var>any</var></samp>&rsquo;
+<li>&lsquo;<samp><span class="samp">sparc-sun-solaris2.</span><var>any</var></samp>&rsquo;
+<li>&lsquo;<samp><span class="samp">sparc64-</span><var>any</var><span class="samp">-solaris2.</span><var>any</var></samp>&rsquo;
+ <br><dt><code><a name="with_002das"></a>--with-as=</code><var>pathname</var><dd>Specify that the compiler should use the assembler pointed to by
+<var>pathname</var>, rather than the one found by the standard rules to find
+an assembler, which are:
+ <ul>
+<li>Unless GCC is being built with a cross compiler, check the
+<samp><var>libexec</var><span class="file">/gcc/</span><var>target</var><span class="file">/</span><var>version</var></samp> directory.
+<var>libexec</var> defaults to <samp><var>exec-prefix</var><span class="file">/libexec</span></samp>;
+<var>exec-prefix</var> defaults to <var>prefix</var>, which
+defaults to <samp><span class="file">/usr/local</span></samp> unless overridden by the
+<samp><span class="option">--prefix=</span><var>pathname</var></samp> switch described above. <var>target</var>
+is the target system triple, such as &lsquo;<samp><span class="samp">sparc-sun-solaris2.7</span></samp>&rsquo;, and
+<var>version</var> denotes the GCC version, such as 3.0.
+ <li>If the target system is the same that you are building on, check
+operating system specific directories (e.g. <samp><span class="file">/usr/ccs/bin</span></samp> on
+Sun Solaris 2).
+ <li>Check in the <samp><span class="env">PATH</span></samp> for a tool whose name is prefixed by the
+target system triple.
+ <li>Check in the <samp><span class="env">PATH</span></samp> for a tool whose name is not prefixed by the
+target system triple, if the host and target system triple are
+the same (in other words, we use a host tool if it can be used for
+the target as well).
+ <p>You may want to use <samp><span class="option">--with-as</span></samp> if no assembler
+is installed in the directories listed above, or if you have multiple
+assemblers installed and want to choose one that is not found by the
+above rules.
+ <br><dt><code><a name="with_002dgnu_002dld"></a>--with-gnu-ld</code><dd>Same as <a href="#with-gnu-as"><samp><span class="option">--with-gnu-as</span></samp></a>
+but for the linker.
+ <br><dt><code>--with-ld=</code><var>pathname</var><dd>Same as <a href="#with-as"><samp><span class="option">--with-as</span></samp></a>
+but for the linker.
+ <br><dt><code>--with-stabs</code><dd>Specify that stabs debugging
+information should be used instead of whatever format the host normally
+uses. Normally GCC uses the same debug format as the host system.
+ <p>On MIPS based systems and on Alphas, you must specify whether you want
+GCC to create the normal ECOFF debugging format, or to use BSD-style
+stabs passed through the ECOFF symbol table. The normal ECOFF debug
+format cannot fully handle languages other than C. BSD stabs format can
+handle other languages, but it only works with the GNU debugger GDB.
+ <p>Normally, GCC uses the ECOFF debugging format by default; if you
+prefer BSD stabs, specify <samp><span class="option">--with-stabs</span></samp> when you configure GCC.
+ <p>No matter which default you choose when you configure GCC, the user
+can use the <samp><span class="option">-gcoff</span></samp> and <samp><span class="option">-gstabs+</span></samp> options to specify explicitly
+the debug format for a particular compilation.
+ <p><samp><span class="option">--with-stabs</span></samp> is meaningful on the ISC system on the 386, also, if
+<samp><span class="option">--with-gas</span></samp> is used. It selects use of stabs debugging
+information embedded in COFF output. This kind of debugging information
+supports C++ well; ordinary COFF debugging information does not.
+ <p><samp><span class="option">--with-stabs</span></samp> is also meaningful on 386 systems running SVR4. It
+selects use of stabs debugging information embedded in ELF output. The
+C++ compiler currently (2.6.0) does not support the DWARF debugging
+information normally used on 386 SVR4 platforms; stabs provide a
+workable alternative. This requires gas and gdb, as the normal SVR4
+tools can not generate or interpret stabs.
+ <br><dt><code>--disable-multilib</code><dd>Specify that multiple target
+libraries to support different target variants, calling
+conventions, etc. should not be built. The default is to build a
+predefined set of them.
+ <p>Some targets provide finer-grained control over which multilibs are built
+(e.g., <samp><span class="option">--disable-softfloat</span></samp>):
+ <dl>
+ <br><dt><code>arm-*-*</code><dd>fpu, 26bit, underscore, interwork, biendian, nofmult.
+ <br><dt><code>m68*-*-*</code><dd>softfloat, m68881, m68000, m68020.
+ <br><dt><code>mips*-*-*</code><dd>single-float, biendian, softfloat.
+ <br><dt><code>powerpc*-*-*, rs6000*-*-*</code><dd>aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
+sysv, aix.
+ </dl>
+ <br><dt><code>--with-multilib-list=</code><var>list</var><dt><code>--without-multilib-list</code><dd>Specify what multilibs to build.
+Currently only implemented for sh*-*-*.
+ <p><var>list</var> is a comma separated list of CPU names. These must be of the
+form <code>sh*</code> or <code>m*</code> (in which case they match the compiler option
+for that processor). The list should not contain any endian options -
+these are handled by <samp><span class="option">--with-endian</span></samp>.
+ <p>If <var>list</var> is empty, then there will be no multilibs for extra
+processors. The multilib for the secondary endian remains enabled.
+ <p>As a special case, if an entry in the list starts with a <code>!</code>
+(exclamation point), then it is added to the list of excluded multilibs.
+Entries of this sort should be compatible with &lsquo;<samp><span class="samp">MULTILIB_EXCLUDES</span></samp>&rsquo;
+(once the leading <code>!</code> has been stripped).
+ <p>If <samp><span class="option">--with-multilib-list</span></samp> is not given, then a default set of
+multilibs is selected based on the value of <samp><span class="option">--target</span></samp>. This is
+usually the complete set of libraries, but some targets imply a more
+specialized subset.
+ <p>Example 1: to configure a compiler for SH4A only, but supporting both
+endians, with little endian being the default:
+ <pre class="smallexample"> --with-cpu=sh4a --with-endian=little,big --with-multilib-list=
+ <p>Example 2: to configure a compiler for both SH4A and SH4AL-DSP, but with
+only little endian SH4AL:
+ <pre class="smallexample"> --with-cpu=sh4a --with-endian=little,big --with-multilib-list=sh4al,!mb/m4al
+ <br><dt><code>--with-endian=</code><var>endians</var><dd>Specify what endians to use.
+Currently only implemented for sh*-*-*.
+ <p><var>endians</var> may be one of the following:
+ <dl>
+<dt><code>big</code><dd>Use big endian exclusively.
+<br><dt><code>little</code><dd>Use little endian exclusively.
+<br><dt><code>big,little</code><dd>Use big endian by default. Provide a multilib for little endian.
+<br><dt><code>little,big</code><dd>Use little endian by default. Provide a multilib for big endian.
+ <br><dt><code>--enable-threads</code><dd>Specify that the target
+supports threads. This affects the Objective-C compiler and runtime
+library, and exception handling for other languages like C++ and Java.
+On some systems, this is the default.
+ <p>In general, the best (and, in many cases, the only known) threading
+model available will be configured for use. Beware that on some
+systems, GCC has not been taught what threading models are generally
+available for the system. In this case, <samp><span class="option">--enable-threads</span></samp> is an
+alias for <samp><span class="option">--enable-threads=single</span></samp>.
+ <br><dt><code>--disable-threads</code><dd>Specify that threading support should be disabled for the system.
+This is an alias for <samp><span class="option">--enable-threads=single</span></samp>.
+ <br><dt><code>--enable-threads=</code><var>lib</var><dd>Specify that
+<var>lib</var> is the thread support library. This affects the Objective-C
+compiler and runtime library, and exception handling for other languages
+like C++ and Java. The possibilities for <var>lib</var> are:
+ <dl>
+<dt><code>aix</code><dd>AIX thread support.
+<br><dt><code>dce</code><dd>DCE thread support.
+<br><dt><code>gnat</code><dd>Ada tasking support. For non-Ada programs, this setting is equivalent
+to &lsquo;<samp><span class="samp">single</span></samp>&rsquo;. When used in conjunction with the Ada run time, it
+causes GCC to use the same thread primitives as Ada uses. This option
+is necessary when using both Ada and the back end exception handling,
+which is the default for most Ada targets.
+<br><dt><code>mach</code><dd>Generic MACH thread support, known to work on NeXTSTEP. (Please note
+that the file needed to support this configuration, <samp><span class="file">gthr-mach.h</span></samp>, is
+missing and thus this setting will cause a known bootstrap failure.)
+<br><dt><code>no</code><dd>This is an alias for &lsquo;<samp><span class="samp">single</span></samp>&rsquo;.
+<br><dt><code>posix</code><dd>Generic POSIX/Unix98 thread support.
+<br><dt><code>posix95</code><dd>Generic POSIX/Unix95 thread support.
+<br><dt><code>rtems</code><dd>RTEMS thread support.
+<br><dt><code>single</code><dd>Disable thread support, should work for all platforms.
+<br><dt><code>solaris</code><dd>Sun Solaris 2/Unix International thread support. Only use this if you
+really need to use this legacy API instead of the default, &lsquo;<samp><span class="samp">posix</span></samp>&rsquo;.
+<br><dt><code>vxworks</code><dd>VxWorks thread support.
+<br><dt><code>win32</code><dd>Microsoft Win32 API thread support.
+<br><dt><code>nks</code><dd>Novell Kernel Services thread support.
+ <br><dt><code>--enable-tls</code><dd>Specify that the target supports TLS (Thread Local Storage). Usually
+configure can correctly determine if TLS is supported. In cases where
+it guesses incorrectly, TLS can be explicitly enabled or disabled with
+<samp><span class="option">--enable-tls</span></samp> or <samp><span class="option">--disable-tls</span></samp>. This can happen if
+the assembler supports TLS but the C library does not, or if the
+assumptions made by the configure test are incorrect.
+ <br><dt><code>--disable-tls</code><dd>Specify that the target does not support TLS.
+This is an alias for <samp><span class="option">--enable-tls=no</span></samp>.
+ <br><dt><code>--with-cpu=</code><var>cpu</var><dt><code>--with-cpu-32=</code><var>cpu</var><dt><code>--with-cpu-64=</code><var>cpu</var><dd>Specify which cpu variant the compiler should generate code for by default.
+<var>cpu</var> will be used as the default value of the <samp><span class="option">-mcpu=</span></samp> switch.
+This option is only supported on some targets, including ARM, i386, M68k,
+PowerPC, and SPARC. The <samp><span class="option">--with-cpu-32</span></samp> and
+<samp><span class="option">--with-cpu-64</span></samp> options specify separate default CPUs for
+32-bit and 64-bit modes; these options are only supported for i386,
+x86-64 and PowerPC.
+ <br><dt><code>--with-schedule=</code><var>cpu</var><dt><code>--with-arch=</code><var>cpu</var><dt><code>--with-arch-32=</code><var>cpu</var><dt><code>--with-arch-64=</code><var>cpu</var><dt><code>--with-tune=</code><var>cpu</var><dt><code>--with-tune-32=</code><var>cpu</var><dt><code>--with-tune-64=</code><var>cpu</var><dt><code>--with-abi=</code><var>abi</var><dt><code>--with-fpu=</code><var>type</var><dt><code>--with-float=</code><var>type</var><dd>These configure options provide default values for the <samp><span class="option">-mschedule=</span></samp>,
+<samp><span class="option">-march=</span></samp>, <samp><span class="option">-mtune=</span></samp>, <samp><span class="option">-mabi=</span></samp>, and <samp><span class="option">-mfpu=</span></samp>
+options and for <samp><span class="option">-mhard-float</span></samp> or <samp><span class="option">-msoft-float</span></samp>. As with
+<samp><span class="option">--with-cpu</span></samp>, which switches will be accepted and acceptable values
+of the arguments depend on the target.
+ <br><dt><code>--with-mode=</code><var>mode</var><dd>Specify if the compiler should default to <samp><span class="option">-marm</span></samp> or <samp><span class="option">-mthumb</span></samp>.
+This option is only supported on ARM targets.
+ <br><dt><code>--with-fpmath=sse</code><dd>Specify if the compiler should default to <samp><span class="option">-msse2</span></samp> and
+<samp><span class="option">-mfpmath=sse</span></samp>. This option is only supported on i386 and
+x86-64 targets.
+ <br><dt><code>--with-divide=</code><var>type</var><dd>Specify how the compiler should generate code for checking for
+division by zero. This option is only supported on the MIPS target.
+The possibilities for <var>type</var> are:
+ <dl>
+<dt><code>traps</code><dd>Division by zero checks use conditional traps (this is the default on
+systems that support conditional traps).
+<br><dt><code>breaks</code><dd>Division by zero checks use the break instruction.
+ <!-- If you make -with-llsc the default for additional targets, -->
+ <!-- update the -with-llsc description in the MIPS section below. -->
+ <br><dt><code>--with-llsc</code><dd>On MIPS targets, make <samp><span class="option">-mllsc</span></samp> the default when no
+<samp><span class="option">-mno-llsc</span></samp> option is passed. This is the default for
+Linux-based targets, as the kernel will emulate them if the ISA does
+not provide them.
+ <br><dt><code>--without-llsc</code><dd>On MIPS targets, make <samp><span class="option">-mno-llsc</span></samp> the default when no
+<samp><span class="option">-mllsc</span></samp> option is passed.
+ <br><dt><code>--with-synci</code><dd>On MIPS targets, make <samp><span class="option">-msynci</span></samp> the default when no
+<samp><span class="option">-mno-synci</span></samp> option is passed.
+ <br><dt><code>--without-synci</code><dd>On MIPS targets, make <samp><span class="option">-mno-synci</span></samp> the default when no
+<samp><span class="option">-msynci</span></samp> option is passed. This is the default.
+ <br><dt><code>--with-mips-plt</code><dd>On MIPS targets, make use of copy relocations and PLTs.
+These features are extensions to the traditional
+SVR4-based MIPS ABIs and require support from GNU binutils
+and the runtime C library.
+ <br><dt><code>--enable-__cxa_atexit</code><dd>Define if you want to use __cxa_atexit, rather than atexit, to
+register C++ destructors for local statics and global objects.
+This is essential for fully standards-compliant handling of
+destructors, but requires __cxa_atexit in libc. This option is currently
+only available on systems with GNU libc. When enabled, this will cause
+<samp><span class="option">-fuse-cxa-atexit</span></samp> to be passed by default.
+ <br><dt><code>--enable-target-optspace</code><dd>Specify that target
+libraries should be optimized for code space instead of code speed.
+This is the default for the m32r platform.
+ <br><dt><code>--with-cpp-install-dir=</code><var>dirname</var><dd>Specify that the user visible <samp><span class="command">cpp</span></samp> program should be installed
+in <samp><var>prefix</var><span class="file">/</span><var>dirname</var><span class="file">/cpp</span></samp>, in addition to <var>bindir</var>.
+ <br><dt><code>--enable-comdat</code><dd>Enable COMDAT group support. This is primarily used to override the
+automatically detected value.
+ <br><dt><code>--enable-initfini-array</code><dd>Force the use of sections <code>.init_array</code> and <code>.fini_array</code>
+(instead of <code>.init</code> and <code>.fini</code>) for constructors and
+destructors. Option <samp><span class="option">--disable-initfini-array</span></samp> has the
+opposite effect. If neither option is specified, the configure script
+will try to guess whether the <code>.init_array</code> and
+<code>.fini_array</code> sections are supported and, if they are, use them.
+ <br><dt><code>--enable-build-with-cxx</code><dd>Build GCC using a C++ compiler rather than a C compiler. This is an
+experimental option which may become the default in a later release.
+ <br><dt><code>--enable-maintainer-mode</code><dd>The build rules that regenerate the Autoconf and Automake output files as
+well as the GCC master message catalog <samp><span class="file">gcc.pot</span></samp> are normally
+disabled. This is because it can only be rebuilt if the complete source
+tree is present. If you have changed the sources and want to rebuild the
+catalog, configuring with <samp><span class="option">--enable-maintainer-mode</span></samp> will enable