libstdc++-v3/doc/html/manual/setup.html

   1 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml"><head><title>Chapter 2. Setup</title><meta name="generator" content="DocBook XSL-NS Stylesheets V1.76.1"/><meta name="keywords" content="&#10;      ISO C++&#10;    , &#10;      library&#10;    "/><meta name="keywords" content="&#10;      ISO C++&#10;    , &#10;      runtime&#10;    , &#10;      library&#10;    "/><link rel="home" href="../index.html" title="The GNU C++ Library"/><link rel="up" href="intro.html" title="Part I.  Introduction"/><link rel="prev" href="bugs.html" title="Bugs"/><link rel="next" href="configure.html" title="Configure"/></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 2. Setup</th></tr><tr><td align="left"><a accesskey="p" href="bugs.html">Prev</a> </td><th width="60%" align="center">Part I.
   4   Introduction
   5
   6 </th><td align="right"> <a accesskey="n" href="configure.html">Next</a></td></tr></table><hr/></div><div class="chapter" title="Chapter 2. Setup"><div class="titlepage"><div><div><h2 class="title"><a id="manual.intro.setup"/>Chapter 2. Setup</h2></div></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl><dt><span class="section"><a href="setup.html#manual.intro.setup.prereq">Prerequisites</a></span></dt><dt><span class="section"><a href="configure.html">Configure</a></span></dt><dt><span class="section"><a href="make.html">Make</a></span></dt></dl></div><p>To transform libstdc++ sources into installed include files
   7    and properly built binaries useful for linking to other software is
   8    a multi-step process. Steps include getting the sources,
   9    configuring and building the sources, testing, and installation.
  10    </p><p>The general outline of commands is something like:
  11    </p><pre class="programlisting">
  12    <span class="emphasis"><em>get gcc sources</em></span>
  13    <span class="emphasis"><em>extract into gccsrcdir</em></span>
  14    mkdir <span class="emphasis"><em>gccbuilddir</em></span>
  15    cd <span class="emphasis"><em>gccbuilddir</em></span>
  16    <span class="emphasis"><em>gccsrcdir</em></span>/configure --prefix=<span class="emphasis"><em>destdir</em></span> --other-opts...
  17    make
  18    make check
  19    make install
  20    </pre><p>
  21      Each step is described in more detail in the following sections.
  22    </p><div class="section" title="Prerequisites"><div class="titlepage"><div><div><h2 class="title"><a id="manual.intro.setup.prereq"/>Prerequisites</h2></div></div></div><p>
  23   Because libstdc++ is part of GCC, the primary source for
  24    installation instructions is
  25    <a class="link" href="http://gcc.gnu.org/install/">the GCC install page</a>.
  26    In particular, list of prerequisite software needed to build the library
  27    <a class="link" href="http://gcc.gnu.org/install/prerequisites.html">
  28    starts with those requirements.</a> The same pages also list
  29    the tools you will need if you wish to modify the source.
  30 </p><p>
  31    Additional data is given here only where it applies to libstdc++.
  32   </p><p>As of GCC 4.0.1 the minimum version of binutils required to build
  33       libstdc++ is <code class="code">2.15.90.0.1.1</code>. You can get snapshots
  34       (as well as releases) of binutils from
  35       <a class="link" href="ftp://sources.redhat.com/pub/binutils/">
  36       ftp://sources.redhat.com/pub/binutils</a>.
  37       Older releases of libstdc++ do not require such a recent version,
  38       but to take full advantage of useful space-saving features and
  39       bug-fixes you should use a recent binutils whenever possible.
  40       The configure process will automatically detect and use these
  41       features if the underlying support is present.
  42    </p><p>
  43      To generate the API documentation from the sources you will need
  44      Doxygen, see <a class="link" href="documentation_hacking.html" title="Writing and Generating Documentation">Documentation
  45      Hacking</a> in the appendix for full details.
  46    </p><p>
  47    Finally, a few system-specific requirements:
  48    </p><div class="variablelist"><dl><dt><span class="term">linux</span></dt><dd><p>
  49           If GCC 3.1.0 or later on is being used on GNU/Linux, an attempt
  50           will be made to use "C" library functionality necessary for
  51           C++ named locale support.  For GCC 4.6.0 and later, this
  52           means that glibc 2.3 or later is required.
  53         </p><p>
  54           If the 'gnu' locale model is being used, the following
  55           locales are used and tested in the libstdc++ testsuites.
  56           The first column is the name of the locale, the second is
  57           the character set it is expected to use.
  58         </p><pre class="programlisting">
  59 de_DE               ISO-8859-1
  60 de_DE@euro          ISO-8859-15
  61 en_GB               ISO-8859-1
  62 en_HK               ISO-8859-1
  63 en_PH               ISO-8859-1
  64 en_US               ISO-8859-1
  65 en_US.ISO-8859-1    ISO-8859-1
  66 en_US.ISO-8859-15   ISO-8859-15
  67 en_US.UTF-8         UTF-8
  68 es_ES               ISO-8859-1
  69 es_MX               ISO-8859-1
  70 fr_FR               ISO-8859-1
  71 fr_FR@euro          ISO-8859-15
  72 is_IS               UTF-8
  73 it_IT               ISO-8859-1
  74 ja_JP.eucjp         EUC-JP
  75 ru_RU.ISO-8859-5    ISO-8859-5
  76 ru_RU.UTF-8         UTF-8
  77 se_NO.UTF-8         UTF-8
  78 ta_IN               UTF-8
  79 zh_TW               BIG5
  80 </pre><p>Failure to have installed the underlying "C" library
  81       locale information for any of the above regions means that
  82       the corresponding C++ named locale will not work:  because of
  83       this, the libstdc++ testsuite will skip named locale tests
  84       which need missing information.  If this isn't an issue, don't
  85       worry about it.  If a named locale is needed, the underlying
  86       locale information must be installed.  Note that rebuilding
  87       libstdc++ after "C" locales are installed is not necessary.
  88       </p><p>
  89         To install support for locales, do only one of the following:
  90       </p><div class="itemizedlist"><ul class="itemizedlist"><li class="listitem"><p>install all locales</p></li><li class="listitem"><p>install just the necessary locales</p><div class="itemizedlist"><ul class="itemizedlist"><li class="listitem"><p>with Debian GNU/Linux:</p><p> Add the above list, as shown, to the file
  91               <code class="code">/etc/locale.gen</code> </p><p> run <code class="code">/usr/sbin/locale-gen</code> </p></li><li class="listitem"><p>on most Unix-like operating systems:</p><p><code class="code"> localedef -i de_DE -f ISO-8859-1 de_DE </code></p><p>(repeat for each entry in the above list) </p></li><li class="listitem"><p>
  92                Instructions for other operating systems solicited.
  93             </p></li></ul></div></li></ul></div></dd></dl></div></div></div><div class="navfooter"><hr/><table width="100%" summary="Navigation footer"><tr><td align="left"><a accesskey="p" href="bugs.html">Prev</a> </td><td align="center"><a accesskey="u" href="intro.html">Up</a></td><td align="right"> <a accesskey="n" href="configure.html">Next</a></td></tr><tr><td align="left" valign="top">Bugs </td><td align="center"><a accesskey="h" href="../index.html">Home</a></td><td align="right" valign="top"> Configure</td></tr></table></div></body></html>