toolchain/gcc/INSTALL/finalinstall.html

   1 <html lang="en">
   2 <head>
   3 <title>Installing GCC: Final installation</title>
   4 <meta http-equiv="Content-Type" content="text/html">
   5 <meta name="description" content="Installing GCC: Final installation">
   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: Final installation</h1>
  43 Now that GCC has been built (and optionally tested), you can install it with
  44 <pre class="smallexample">     cd <var>objdir</var>; make install
  45 </pre>
  46    <p>We strongly recommend to install into a target directory where there is
  47 no previous version of GCC present.
  48
  49    <p>That step completes the installation of GCC; user level binaries can
  50 be found in <var>prefix</var><span class="file">/bin</span> where <var>prefix</var> is the value
  51 you specified with the <span class="option">--prefix</span> to configure (or
  52 <span class="file">/usr/local</span> by default).  (If you specified <span class="option">--bindir</span>,
  53 that directory will be used instead; otherwise, if you specified
  54 <span class="option">--exec-prefix</span>, <var>exec-prefix</var><span class="file">/bin</span> will be used.)
  55 Headers for the C++ and Java libraries are installed in
  56 <var>prefix</var><span class="file">/include</span>; libraries in <var>libdir</var>
  57 (normally <var>prefix</var><span class="file">/lib</span>); internal parts of the compiler in
  58 <var>libdir</var><span class="file">/gcc</span> and <var>libexecdir</var><span class="file">/gcc</span>; documentation
  59 in info format in <var>infodir</var> (normally
  60 <var>prefix</var><span class="file">/info</span>).
  61
  62    <p>When installing cross-compilers, GCC's executables
  63 are not only installed into <var>bindir</var>, that
  64 is, <var>exec-prefix</var><span class="file">/bin</span>, but additionally into
  65 <var>exec-prefix</var><span class="file">/</span><var>target-alias</var><span class="file">/bin</span>, if that directory
  66 exists.  Typically, such <dfn>tooldirs</dfn> hold target-specific
  67 binutils, including assembler and linker.
  68
  69    <p>Installation into a temporary staging area or into a <span class="command">chroot</span>
  70 jail can be achieved with the command
  71
  72 <pre class="smallexample">     make DESTDIR=<var>path-to-rootdir</var> install
  73 </pre>
  74    <p class="noindent">where <var>path-to-rootdir</var> is the absolute path of
  75 a directory relative to which all installation paths will be
  76 interpreted.  Note that the directory specified by <code>DESTDIR</code>
  77 need not exist yet; it will be created if necessary.
  78
  79    <p>There is a subtle point with tooldirs and <code>DESTDIR</code>:
  80 If you relocate a cross-compiler installation with
  81 e.g. <span class="samp">DESTDIR=</span><var>rootdir</var>, then the directory
  82 <var>rootdir</var><span class="file">/</span><var>exec-prefix</var><span class="file">/</span><var>target-alias</var><span class="file">/bin</span> will
  83 be filled with duplicated GCC executables only if it already exists,
  84 it will not be created otherwise.  This is regarded as a feature,
  85 not as a bug, because it gives slightly more control to the packagers
  86 using the <code>DESTDIR</code> feature.
  87
  88    <p>If you built a released version of GCC using <span class="samp">make bootstrap</span> then please
  89 quickly review the build status page for your release, available from
  90 <a href="http://gcc.gnu.org/buildstat.html">http://gcc.gnu.org/buildstat.html</a>.
  91 If your system is not listed for the version of GCC that you built,
  92 send a note to
  93 <a href="mailto:gcc@gcc.gnu.org">gcc@gcc.gnu.org</a> indicating
  94 that you successfully built and installed GCC.
  95 Include the following information:
  96
  97      <ul>
  98 <li>Output from running <var>srcdir</var><span class="file">/config.guess</span>.  Do not send
  99 that file itself, just the one-line output from running it.
 100
 101      <li>The output of <span class="samp">gcc -v</span> for your newly installed <span class="command">gcc</span>.
 102 This tells us which version of GCC you built and the options you passed to
 103 configure.
 104
 105      <li>Whether you enabled all languages or a subset of them.  If you used a
 106 full distribution then this information is part of the configure
 107 options in the output of <span class="samp">gcc -v</span>, but if you downloaded the
 108 &ldquo;core&rdquo; compiler plus additional front ends then it isn't apparent
 109 which ones you built unless you tell us about it.
 110
 111      <li>If the build was for GNU/Linux, also include:
 112           <ul>
 113 <li>The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
 114 this information should be available from <span class="file">/etc/issue</span>.
 115
 116           <li>The version of the Linux kernel, available from <span class="samp">uname --version</span>
 117 or <span class="samp">uname -a</span>.
 118
 119           <li>The version of glibc you used; for RPM-based systems like Red Hat,
 120 Mandrake, and SuSE type <span class="samp">rpm -q glibc</span> to get the glibc version,
 121 and on systems like Debian and Progeny use <span class="samp">dpkg -l libc6</span>.
 122 </ul>
 123      For other systems, you can include similar information if you think it is
 124 relevant.
 125
 126      <li>Any other information that you think would be useful to people building
 127 GCC on the same configuration.  The new entry in the build status list
 128 will include a link to the archived copy of your message.
 129 </ul>
 130
 131    <p>We'd also like to know if the
 132 <a href="specific.html">host/target specific installation notes</a>
 133 didn't include your host/target information or if that information is
 134 incomplete or out of date.  Send a note to
 135 <a href="mailto:gcc@gcc.gnu.org">gcc@gcc.gnu.org</a> detailing how the information should be changed.
 136
 137    <p>If you find a bug, please report it following the
 138 <a href="../bugs.html">bug reporting guidelines</a>.
 139
 140    <p>If you want to print the GCC manuals, do <span class="samp">cd </span><var>objdir</var><span class="samp">; make
 141 dvi</span>.  You will need to have <span class="command">texi2dvi</span> (version at least 4.2)
 142 and TeX installed.  This creates a number of <span class="file">.dvi</span> files in
 143 subdirectories of <var>objdir</var>; these may be converted for
 144 printing with programs such as <span class="command">dvips</span>.  You can also
 145 <a href="http://www.gnu.org/order/order.html">buy printed manuals from the Free Software Foundation</a>, though such manuals may not be for the most
 146 recent version of GCC.
 147
 148    <p><hr />
 149 <p><a href="./index.html">Return to the GCC Installation page</a>
 150
 151 <!-- ***Binaries**************************************************************** -->
 152 <!-- ***Specific**************************************************************** -->
 153 <!-- ***Old documentation****************************************************** -->
 154 <!-- ***GFDL******************************************************************** -->
 155 <!-- *************************************************************************** -->
 156 <!-- Part 6 The End of the Document -->
 157 </body></html>
 158