finalinstall.html revision 1.1.1.1
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.2"> 7<link href="http://www.gnu.org/software/texinfo/" rel=generator-home> 8<!-- 9Copyright © 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 101999, 2000, 2001, 2002, 2003 Free Software Foundation, Inc. 11<br><p> 12<p>Permission is granted to copy, distribute and/or modify this document 13under the terms of the GNU Free Documentation License, Version 1.2 or 14any later version published by the Free Software Foundation; with no 15Invariant Sections, the Front-Cover texts being (a) (see below), and 16with the Back-Cover Texts being (b) (see below). A copy of the 17license is included in the section entitled "<a href="./gfdl.html">GNU Free Documentation License</a>". 18 19<p>(a) The FSF's Front-Cover Text is: 20 21<p>A GNU Manual 22 23<p>(b) The FSF's Back-Cover Text is: 24 25<p>You have freedom to copy and modify this GNU Manual, like GNU 26 software. Copies published by the Free Software Foundation raise 27 funds for GNU development.--> 28</head> 29<body> 30<h1>Installing GCC: Final installation</h1> 31Now that GCC has been built (and optionally tested), you can install it with 32<br><pre>cd <var>objdir</var>; make install 33</pre> 34 35<p>We strongly recommend to install into a target directory where there is 36no previous version of GCC present. 37 38<p>That step completes the installation of GCC; user level binaries can 39be found in <code><var>prefix</var>/bin</code> where <var>prefix</var> is the value you 40specified with the <code>--prefix</code> to configure (or <code>/usr/local</code> 41by default). (If you specified <code>--bindir</code>, that directory will 42be used instead; otherwise, if you specified <code>--exec-prefix</code>, 43<code><var>exec-prefix</var>/bin</code> will be used.) Headers for the C++ and 44Java libraries are installed in <code><var>prefix</var>/include</code>; libraries 45in <code><var>libdir</var></code> (normally <code><var>prefix</var>/lib</code>); internal 46parts of the compiler in <code><var>libdir</var>/gcc-lib</code>; documentation in 47info format in <code><var>infodir</var></code> (normally <code><var>prefix</var>/info</code>). 48 49<p>When installing cross-compilers, GCC's executables 50are not only installed into <code><var>bindir</var></code>, that 51is, <code><var>exec-prefix</var>/bin</code>, but additionally into 52<code><var>exec-prefix</var>/<var>target-alias</var>/bin</code>, if that directory 53exists. Typically, such <dfn>tooldirs</dfn> hold target-specific 54binutils, including assembler and linker. 55 56<p>Installation into a temporary staging area or into a <code>chroot</code> 57jail can be achieved with the command 58 59<br><pre>make DESTDIR=<var>path-to-rootdir</var> install 60</pre> 61 62<p>where <var>path-to-rootdir</var> is the absolute path of 63a directory relative to which all installation paths will be 64interpreted. Note that the directory specified by <code>DESTDIR</code> 65need not exist yet; it will be created if necessary. 66 67<p>There is a subtle point with tooldirs and <code>DESTDIR</code>: 68If you relocate a cross-compiler installation with 69e.g. <code>DESTDIR=<var>rootdir</var></code>, then the directory 70<code><var>rootdir</var>/<var>exec-prefix</var>/<var>target-alias</var>/bin</code> will 71be filled with duplicated GCC executables only if it already exists, 72it will not be created otherwise. This is regarded as a feature, 73not as a bug, because it gives slightly more control to the packagers 74using the <code>DESTDIR</code> feature. 75 76<p>If you built a released version of GCC using <code>make bootstrap</code> then please 77quickly review the build status page for your release, available from 78<a href="http://gcc.gnu.org/buildstat.html">http://gcc.gnu.org/buildstat.html</a>. 79If your system is not listed for the version of GCC that you built, 80send a note to 81<a href="mailto:gcc@gcc.gnu.org">gcc@gcc.gnu.org</a> indicating 82that you successfully built and installed GCC. 83Include the following information: 84 85<ul> 86<li>Output from running <code><var>srcdir</var>/config.guess</code>. Do not send us 87that file itself, just the one-line output from running it. 88 89<li>The output of <code>gcc -v</code> for your newly installed gcc. 90This tells us which version of GCC you built and the options you passed to 91configure. 92 93<li>Whether you enabled all languages or a subset of them. If you used a 94full distribution then this information is part of the configure 95options in the output of <code>gcc -v</code>, but if you downloaded the 96"core" compiler plus additional front ends then it isn't apparent 97which ones you built unless you tell us about it. 98 99<li>If the build was for GNU/Linux, also include: 100<ul> 101<li>The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3); 102this information should be available from <code>/etc/issue</code>. 103 104<li>The version of the Linux kernel, available from <code>uname --version</code> 105or <code>uname -a</code>. 106 107<li>The version of glibc you used; for RPM-based systems like Red Hat, 108Mandrake, and SuSE type <code>rpm -q glibc</code> to get the glibc version, 109and on systems like Debian and Progeny use <code>dpkg -l libc6</code>. 110</ul> 111For other systems, you can include similar information if you think it is 112relevant. 113 114<li>Any other information that you think would be useful to people building 115GCC on the same configuration. The new entry in the build status list 116will include a link to the archived copy of your message. 117</ul> 118 119<p>We'd also like to know if the 120<a href="specific.html">host/target specific installation notes</a> 121didn't include your host/target information or if that information is 122incomplete or out of date. Send a note to 123<a href="mailto:gcc@gcc.gnu.org">gcc@gcc.gnu.org</a> telling us how the information should be changed. 124 125<p>If you find a bug, please report it following our 126<a href="../bugs.html">bug reporting guidelines</a>. 127 128<p>If you want to print the GCC manuals, do <code>cd <var>objdir</var>; make 129dvi</code>. You will need to have <code>texi2dvi</code> (version at least 4.2) 130and TeX installed. This creates a number of <code>.dvi</code> files in 131subdirectories of <code><var>objdir</var></code>; these may be converted for 132printing with programs such as <code>dvips</code>. You can also 133<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 134recent version of GCC. 135 136<hr /> 137<p> 138<a href="./index.html">Return to the GCC Installation page</a> 139 140</body></html> 141 142