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