toolchain/gcc/INSTALL/old.html

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