old.html 10 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202
  1. <html lang="en">
  2. <head>
  3. <title>Installing GCC: Old documentation</title>
  4. <meta http-equiv="Content-Type" content="text/html">
  5. <meta name="description" content="Installing GCC: Old documentation">
  6. <meta name="generator" content="makeinfo 4.12">
  7. <link title="Top" rel="top" href="#Top">
  8. <link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
  9. <!--
  10. Copyright (C) 1988-2015 Free Software Foundation, Inc.
  11. Permission is granted to copy, distribute and/or modify this document
  12. under the terms of the GNU Free Documentation License, Version 1.3 or
  13. any later version published by the Free Software Foundation; with no
  14. Invariant Sections, the Front-Cover texts being (a) (see below), and
  15. with the Back-Cover Texts being (b) (see below). A copy of the
  16. license is included in the section entitled "GNU Free Documentation License".
  17. (a) The FSF's Front-Cover Text is:
  18. A GNU Manual
  19. (b) The FSF's Back-Cover Text is:
  20. You have freedom to copy and modify this GNU Manual, like GNU
  21. software. Copies published by the Free Software Foundation raise
  22. funds for GNU development.-->
  23. <meta http-equiv="Content-Style-Type" content="text/css">
  24. <style type="text/css"><!--
  25. pre.display { font-family:inherit }
  26. pre.format { font-family:inherit }
  27. pre.smalldisplay { font-family:inherit; font-size:smaller }
  28. pre.smallformat { font-family:inherit; font-size:smaller }
  29. pre.smallexample { font-size:smaller }
  30. pre.smalllisp { font-size:smaller }
  31. span.sc { font-variant:small-caps }
  32. span.roman { font-family:serif; font-weight:normal; }
  33. span.sansserif { font-family:sans-serif; font-weight:normal; }
  34. --></style>
  35. </head>
  36. <body>
  37. <h1 class="settitle">Installing GCC: Old documentation</h1>
  38. <h1 align="center">Old installation documentation</h1>
  39. <p>Note most of this information is out of date and superseded by the
  40. previous chapters of this manual. It is provided for historical
  41. reference only, because of a lack of volunteers to merge it into the
  42. main manual.
  43. <p>Here is the procedure for installing GCC on a GNU or Unix system.
  44. <ol type=1 start=1>
  45. <li>If you have chosen a configuration for GCC which requires other GNU
  46. tools (such as GAS or the GNU linker) instead of the standard system
  47. tools, install the required tools in the build directory under the names
  48. <samp><span class="file">as</span></samp>, <samp><span class="file">ld</span></samp> or whatever is appropriate.
  49. <p>Alternatively, you can do subsequent compilation using a value of the
  50. <code>PATH</code> environment variable such that the necessary GNU tools come
  51. before the standard system tools.
  52. <li>Specify the host, build and target machine configurations. You do this
  53. when you run the <samp><span class="file">configure</span></samp> script.
  54. <p>The <dfn>build</dfn> machine is the system which you are using, the
  55. <dfn>host</dfn> machine is the system where you want to run the resulting
  56. compiler (normally the build machine), and the <dfn>target</dfn> machine is
  57. the system for which you want the compiler to generate code.
  58. <p>If you are building a compiler to produce code for the machine it runs
  59. on (a native compiler), you normally do not need to specify any operands
  60. to <samp><span class="file">configure</span></samp>; it will try to guess the type of machine you are on
  61. and use that as the build, host and target machines. So you don't need
  62. to specify a configuration when building a native compiler unless
  63. <samp><span class="file">configure</span></samp> cannot figure out what your configuration is or guesses
  64. wrong.
  65. <p>In those cases, specify the build machine's <dfn>configuration name</dfn>
  66. with the <samp><span class="option">--host</span></samp> option; the host and target will default to be
  67. the same as the host machine.
  68. <p>Here is an example:
  69. <pre class="smallexample"> ./configure --host=sparc-sun-sunos4.1
  70. </pre>
  71. <p>A configuration name may be canonical or it may be more or less
  72. abbreviated.
  73. <p>A canonical configuration name has three parts, separated by dashes.
  74. It looks like this: &lsquo;<samp><var>cpu</var><span class="samp">-</span><var>company</var><span class="samp">-</span><var>system</var></samp>&rsquo;.
  75. (The three parts may themselves contain dashes; <samp><span class="file">configure</span></samp>
  76. can figure out which dashes serve which purpose.) For example,
  77. &lsquo;<samp><span class="samp">m68k-sun-sunos4.1</span></samp>&rsquo; specifies a Sun 3.
  78. <p>You can also replace parts of the configuration by nicknames or aliases.
  79. For example, &lsquo;<samp><span class="samp">sun3</span></samp>&rsquo; stands for &lsquo;<samp><span class="samp">m68k-sun</span></samp>&rsquo;, so
  80. &lsquo;<samp><span class="samp">sun3-sunos4.1</span></samp>&rsquo; is another way to specify a Sun 3.
  81. <p>You can specify a version number after any of the system types, and some
  82. of the CPU types. In most cases, the version is irrelevant, and will be
  83. ignored. So you might as well specify the version if you know it.
  84. <p>See <a href="#Configurations">Configurations</a>, for a list of supported configuration names and
  85. notes on many of the configurations. You should check the notes in that
  86. section before proceeding any further with the installation of GCC.
  87. </ol>
  88. <p><h2><a name="Configurations"></a>Configurations Supported by GCC</h2><a name="index-configurations-supported-by-GCC-1"></a>
  89. Here are the possible CPU types:
  90. <blockquote>
  91. <!-- gmicro, fx80, spur and tahoe omitted since they don't work. -->
  92. 1750a, a29k, alpha, arm, avr, c<var>n</var>, clipper, dsp16xx, elxsi, fr30, h8300,
  93. hppa1.0, hppa1.1, i370, i386, i486, i586, i686, i786, i860, i960, ip2k, m32r,
  94. m68000, m68k, m88k, mcore, mips, mipsel, mips64, mips64el,
  95. mn10200, mn10300, ns32k, pdp11, powerpc, powerpcle, romp, rs6000, sh, sparc,
  96. sparclite, sparc64, v850, vax, we32k.
  97. </blockquote>
  98. <p>Here are the recognized company names. As you can see, customary
  99. abbreviations are used rather than the longer official names.
  100. <!-- What should be done about merlin, tek*, dolphin? -->
  101. <blockquote>
  102. acorn, alliant, altos, apollo, apple, att, bull,
  103. cbm, convergent, convex, crds, dec, dg, dolphin,
  104. elxsi, encore, harris, hitachi, hp, ibm, intergraph, isi,
  105. mips, motorola, ncr, next, ns, omron, plexus,
  106. sequent, sgi, sony, sun, tti, unicom, wrs.
  107. </blockquote>
  108. <p>The company name is meaningful only to disambiguate when the rest of
  109. the information supplied is insufficient. You can omit it, writing
  110. just &lsquo;<samp><var>cpu</var><span class="samp">-</span><var>system</var></samp>&rsquo;, if it is not needed. For example,
  111. &lsquo;<samp><span class="samp">vax-ultrix4.2</span></samp>&rsquo; is equivalent to &lsquo;<samp><span class="samp">vax-dec-ultrix4.2</span></samp>&rsquo;.
  112. <p>Here is a list of system types:
  113. <blockquote>
  114. 386bsd, aix, acis, amigaos, aos, aout, aux, bosx, bsd, clix, coff, ctix, cxux,
  115. dgux, dynix, ebmon, ecoff, elf, esix, freebsd, hms, genix, gnu, linux,
  116. linux-gnu, hiux, hpux, iris, irix, isc, luna, lynxos, mach, minix, msdos, mvs,
  117. netbsd, newsos, nindy, ns, osf, osfrose, ptx, riscix, riscos, rtu, sco, sim,
  118. solaris, sunos, sym, sysv, udi, ultrix, unicos, uniplus, unos, vms, vsta,
  119. vxworks, winnt, xenix.
  120. </blockquote>
  121. <p class="noindent">You can omit the system type; then <samp><span class="file">configure</span></samp> guesses the
  122. operating system from the CPU and company.
  123. <p>You can add a version number to the system type; this may or may not
  124. make a difference. For example, you can write &lsquo;<samp><span class="samp">bsd4.3</span></samp>&rsquo; or
  125. &lsquo;<samp><span class="samp">bsd4.4</span></samp>&rsquo; to distinguish versions of BSD. In practice, the version
  126. number is most needed for &lsquo;<samp><span class="samp">sysv3</span></samp>&rsquo; and &lsquo;<samp><span class="samp">sysv4</span></samp>&rsquo;, which are often
  127. treated differently.
  128. <p>&lsquo;<samp><span class="samp">linux-gnu</span></samp>&rsquo; is the canonical name for the GNU/Linux target; however
  129. GCC will also accept &lsquo;<samp><span class="samp">linux</span></samp>&rsquo;. The version of the kernel in use is
  130. not relevant on these systems. A suffix such as &lsquo;<samp><span class="samp">libc1</span></samp>&rsquo; or &lsquo;<samp><span class="samp">aout</span></samp>&rsquo;
  131. distinguishes major versions of the C library; all of the suffixed versions
  132. are obsolete.
  133. <p>If you specify an impossible combination such as &lsquo;<samp><span class="samp">i860-dg-vms</span></samp>&rsquo;,
  134. then you may get an error message from <samp><span class="file">configure</span></samp>, or it may
  135. ignore part of the information and do the best it can with the rest.
  136. <samp><span class="file">configure</span></samp> always prints the canonical name for the alternative
  137. that it used. GCC does not support all possible alternatives.
  138. <p>Often a particular model of machine has a name. Many machine names are
  139. recognized as aliases for CPU/company combinations. Thus, the machine
  140. name &lsquo;<samp><span class="samp">sun3</span></samp>&rsquo;, mentioned above, is an alias for &lsquo;<samp><span class="samp">m68k-sun</span></samp>&rsquo;.
  141. Sometimes we accept a company name as a machine name, when the name is
  142. popularly used for a particular machine. Here is a table of the known
  143. machine names:
  144. <blockquote>
  145. 3300, 3b1, 3b<var>n</var>, 7300, altos3068, altos,
  146. apollo68, att-7300, balance,
  147. convex-c<var>n</var>, crds, decstation-3100,
  148. decstation, delta, encore,
  149. fx2800, gmicro, hp7<var>nn</var>, hp8<var>nn</var>,
  150. hp9k2<var>nn</var>, hp9k3<var>nn</var>, hp9k7<var>nn</var>,
  151. hp9k8<var>nn</var>, iris4d, iris, isi68,
  152. m3230, magnum, merlin, miniframe,
  153. mmax, news-3600, news800, news, next,
  154. pbd, pc532, pmax, powerpc, powerpcle, ps2, risc-news,
  155. rtpc, sun2, sun386i, sun386, sun3,
  156. sun4, symmetry, tower-32, tower.
  157. </blockquote>
  158. <p class="noindent">Remember that a machine name specifies both the cpu type and the company
  159. name.
  160. <hr />
  161. <p><a href="./index.html">Return to the GCC Installation page</a>
  162. <!-- ***GFDL******************************************************************** -->
  163. <!-- *************************************************************************** -->
  164. <!-- Part 6 The End of the Document -->
  165. </body></html>