gccinstall: Final install

1 
1 7 Installing GCC: Final installation
1 ************************************
1 
1 Now that GCC has been built (and optionally tested), you can install it
1 with
1      cd OBJDIR && make install
1 
1    We strongly recommend to install into a target directory where there
1 is no previous version of GCC present.  Also, the GNAT runtime should
1 not be stripped, as this would break certain features of the debugger
1 that depend on this debugging information (catching Ada exceptions for
1 instance).
1 
1    That step completes the installation of GCC; user level binaries can
1 be found in 'PREFIX/bin' where PREFIX is the value you specified with
1 the '--prefix' to configure (or '/usr/local' by default).  (If you
1 specified '--bindir', that directory will be used instead; otherwise, if
1 you specified '--exec-prefix', 'EXEC-PREFIX/bin' will be used.)  Headers
1 for the C++ library are installed in 'PREFIX/include'; libraries in
1 'LIBDIR' (normally 'PREFIX/lib'); internal parts of the compiler in
1 'LIBDIR/gcc' and 'LIBEXECDIR/gcc'; documentation in info format in
1 'INFODIR' (normally 'PREFIX/info').
1 
1    When installing cross-compilers, GCC's executables are not only
1 installed into 'BINDIR', that is, 'EXEC-PREFIX/bin', but additionally
1 into 'EXEC-PREFIX/TARGET-ALIAS/bin', if that directory exists.
1 Typically, such "tooldirs" hold target-specific binutils, including
1 assembler and linker.
1 
1    Installation into a temporary staging area or into a 'chroot' jail
1 can be achieved with the command
1 
1      make DESTDIR=PATH-TO-ROOTDIR install
1 
1 where PATH-TO-ROOTDIR is the absolute path of a directory relative to
1 which all installation paths will be interpreted.  Note that the
1 directory specified by 'DESTDIR' need not exist yet; it will be created
1 if necessary.
1 
1    There is a subtle point with tooldirs and 'DESTDIR': If you relocate
1 a cross-compiler installation with e.g. 'DESTDIR=ROOTDIR', then the
1 directory 'ROOTDIR/EXEC-PREFIX/TARGET-ALIAS/bin' will be filled with
1 duplicated GCC executables only if it already exists, it will not be
1 created otherwise.  This is regarded as a feature, not as a bug, because
1 it gives slightly more control to the packagers using the 'DESTDIR'
1 feature.
1 
1    You can install stripped programs and libraries with
1 
1      make install-strip
1 
1    If you are bootstrapping a released version of GCC then please
1 quickly review the build status page for your release, available from
1 <http://gcc.gnu.org/buildstat.html>.  If your system is not listed for
1 the version of GCC that you built, send a note to <gcc@gcc.gnu.org>
1 indicating that you successfully built and installed GCC.  Include the
1 following information:
1 
1    * Output from running 'SRCDIR/config.guess'.  Do not send that file
1      itself, just the one-line output from running it.
1 
1    * The output of 'gcc -v' for your newly installed 'gcc'.  This tells
1      us which version of GCC you built and the options you passed to
1      configure.
1 
1    * Whether you enabled all languages or a subset of them.  If you used
1      a full distribution then this information is part of the configure
1      options in the output of 'gcc -v', but if you downloaded the "core"
1      compiler plus additional front ends then it isn't apparent which
1      ones you built unless you tell us about it.
1 
1    * If the build was for GNU/Linux, also include:
1         * The distribution name and version (e.g., Red Hat 7.1 or Debian
1           2.2.3); this information should be available from
1           '/etc/issue'.
1 
1         * The version of the Linux kernel, available from 'uname
1           --version' or 'uname -a'.
1 
1         * The version of glibc you used; for RPM-based systems like Red
1           Hat, Mandrake, and SuSE type 'rpm -q glibc' to get the glibc
1           version, and on systems like Debian and Progeny use 'dpkg -l
1           libc6'.
1      For other systems, you can include similar information if you think
1      it is relevant.
1 
1    * Any other information that you think would be useful to people
1      building GCC on the same configuration.  The new entry in the build
1      status list will include a link to the archived copy of your
1      message.
1 
11    We'd also like to know if the ⇒host/target specific installation
 notes Specific. didn't include your host/target information or if that
1 information is incomplete or out of date.  Send a note to
1 <gcc@gcc.gnu.org> detailing how the information should be changed.
1 
1    If you find a bug, please report it following the bug reporting
1 guidelines.
1 
1    If you want to print the GCC manuals, do 'cd OBJDIR; make dvi'.  You
1 will need to have 'texi2dvi' (version at least 4.7) and TeX installed.
1 This creates a number of '.dvi' files in subdirectories of 'OBJDIR';
1 these may be converted for printing with programs such as 'dvips'.
1 Alternately, by using 'make pdf' in place of 'make dvi', you can create
1 documentation in the form of '.pdf' files; this requires 'texi2pdf',
1 which is included with Texinfo version 4.8 and later.  You can also buy
1 printed manuals from the Free Software Foundation, though such manuals
1 may not be for the most recent version of GCC.
1 
1    If you would like to generate online HTML documentation, do 'cd
1 OBJDIR; make html' and HTML will be generated for the gcc manuals in
1 'OBJDIR/gcc/HTML'.
1