From 00fd31d1d22defb8305d8ef113d9b0afb1a5a847 Mon Sep 17 00:00:00 2001 From: Phil Edwards Date: Mon, 30 Aug 2004 21:18:09 +0000 Subject: [PATCH] install.html: Update locales list (from Paolo). 2004-08-30 Phil Edwards * docs/html/install.html: Update locales list (from Paolo). Remove other redundant information and point to the GCC install documentation. From-SVN: r86800 --- libstdc++-v3/ChangeLog | 6 ++ libstdc++-v3/docs/html/install.html | 182 +++++------------------------------- 2 files changed, 28 insertions(+), 160 deletions(-) diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index 2146613..1dae1a4 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,9 @@ +2004-08-30 Phil Edwards + + * docs/html/install.html: Update locales list (from Paolo). + Remove other redundant information and point to the GCC install + documentation. + 2004-08-30 Benjamin Kosnik * include/ext/pool_allocator.h: Rename __pool_base to diff --git a/libstdc++-v3/docs/html/install.html b/libstdc++-v3/docs/html/install.html index 0ef1dbf..8ae4ad1 100644 --- a/libstdc++-v3/docs/html/install.html +++ b/libstdc++-v3/docs/html/install.html @@ -31,12 +31,16 @@

Contents

+ +

Because libstdc++-v3 is part of GCC, the primary source for + installation instructions is + the GCC install page. + Additional data is given here only where it applies to libstdc++-v3. +

+ @@ -45,52 +49,24 @@

Tools you will need beforehand

-

You will need a recent version of g++ to compile the snapshot of - libstdc++, such as one of the GCC 3.x snapshots (insert standard - caveat about using snapshots rather than formal releases). You will - need the full source distribution to whatever compiler release you are - using. The GCC snapshots can be had from one of the sites on their - mirror list. -

- -

In addition, if you plan to modify the makefiles or regenerate the - configure scripts you'll need recent versions of the GNU Autotools: - autoconf (version 2.57 or later) and - automake (version 1.7.6 or later), - in order to rebuild the files. Libtool is built from special sources - in the GCC source tree. - These tools are all required to be installed in the same location - (most linux distributions install these tools by default, so no - worries as long as the versions are correct). -

- -

To test your build, you will need either DejaGNU 1.4 (to run - 'make check' like - the rest of GCC), - or Bash 2.x (to run 'make check-script'). +

The list of software needed to build the library is kept with the + rest of the compiler, at + + http://gcc.gnu.org/install/prerequisites.html. The same page + also lists the tools you will need if you wish to modify the source.

As of June 19, 2000, libstdc++ attempts to use tricky and space-saving features of the GNU toolchain, enabled with - -ffunction-sections -fdata-sections - -Wl,--gc-sections. To obtain maximum benefit from this, - binutils after this date should also be used (bugs were fixed - with C++ exception handling related to this change in - libstdc++-v3). The version of these tools should be - 2.10.90, or later, and you can get snapshots (as + -ffunction-sections -fdata-sections -Wl,--gc-sections. + To obtain maximum benefit from this, binutils after this date should + also be used (bugs were fixed with C++ exception handling related + to this change in libstdc++-v3). The version of these tools should + be 2.10.90, or later, and you can get snapshots (as well as releases) of binutils here. The - configure process will automatically detect and use these - features if the underlying support is present. -

- -

If you are using a 3.1-series libstdc++ snapshot, then the - requirements are slightly more stringent: the compiler sources - must also be 3.1 or later (for both technical and licensing - reasons), and your binutils must be 2.11.95 or later if you want - to use symbol versioning in shared libraries. Again, the - configure process will automatically detect and use these - features if the underlying support is present. + configure process will automatically detect and use these features + if the underlying support is present.

Finally, a few system-specific requirements:

@@ -125,9 +101,12 @@ en_US.UTF-8 UTF-8 es_MX ISO-8859-1 fr_FR ISO-8859-1 fr_FR@euro ISO-8859-15 +is_IS UTF-8 it_IT ISO-8859-1 ja_JP.eucjp EUC-JP se_NO.UTF-8 UTF-8 +ta_IN UTF-8 +zh_TW BIG5

Failure to have the underlying "C" library locale information installed will mean that C++ named locales for the @@ -174,66 +153,6 @@ se_NO.UTF-8 UTF-8

-

Setting up the source directories

-

The following definitions will be used throughout the rest of this - document: -

-
    -
  • gccsrcdir: The directory holding the source of the - compiler. It should have several subdirectories like - gccsrcdir/libiberty and gccsrcdir/gcc. -
    • -
  • libsrcdir: The directory holding the source of the - C++ library. -
    • -
  • gccbuilddir: The build directory for the compiler - in gccsrcdir. GCC requires that it be built in - a different directory than its sources. -
    • -
  • libbuilddir: The build directory for libstdc++. -
    • -
  • destdir: The eventual installation directory for - the compiler/libraries, set with the --prefix option to - the configure script. -
    • -
-

Note:

-
    -
  1. The 3.0 version and following are intended to replace the - library that comes with the compiler, so libsrcdir - and libbuilddir must be contained under - gccsrcdir and gccbuilddir, respectively. -
    2. -
  2. The source, build, and installation directories should - not be parents of one another; i.e., these should all be - separate directories. Please don't build out of the - source directory. -
    3. -
- -

Check out or download the GCC sources: the resulting source directory - (gcc or gcc-3.0.3, for example) is - gccsrcdir. - Once in gccsrcdir, you'll need to rename or delete the - libstdc++-v3 directory which comes with that snapshot: -

- 
-   mv libstdc++-v3 libstdc++-v3-previous  [OR]
-   rm -r libstdc++-v3
-

Next, unpack the libstdc++-v3 library tarball into this - gccsrcdir directory; it will create a - libsrcdir called libstdc++-version: -

- 
-   gzip -dc libstdc++-version.tar.gz | tar xf -
-

Finally, rename libsrcdir to libstdc++-v3 so that - gcc's configure flags will be able to deal with the new library. -

- 
-   mv libsrcdir libstdc++-v3
- - -

Configuring

If you have never done this before, you should read the basic GCC Installation @@ -255,63 +174,6 @@ se_NO.UTF-8 UTF-8

-

Building and installing the library

-

Now you have a few options:

-

[re]building everything

-

If you're building GCC from scratch, you can do the usual - 'make bootstrap' here, and libstdc++-v3 will be built - as its default C++ library. The generated g++ will magically - use the correct headers, link against the correct library - binary, and in general using libstdc++-v3 will be a piece of - cake. You're done; run 'make install' (see the GCC - installation instructions) to put the new compiler and libraries - into place. -

- -

[re]building only libstdc++

-

To rebuild just libstdc++, use:

- 
-   make all-target-libstdc++-v3
-

- This will configure and build the C++ library in the - gccbuilddir/cpu-vendor-os/libstdc++ directory. -

-

If you are rebuilding from a previous build [attempt], some - information is kept in a cache file. This is stored in - gccbuilddir/cpu-vendor-os/ if you are building with - multilibs (the default), or in - gccbuilddir/cpu-vendor-os/libstdc++-v3 if you have - multilibs disabled. The filename is config.cache; if previous - information is causing problems, you can delete it entirely, or - simply edit it and remove lines. -

-

You're done. Now install the rebuilt pieces with

- 
-   make install
-

or

- 
-   make install-gcc
-   make install-target-libstdc++-v3
- - -
-

Post-installation

-

Installation will create the destdir directory and - populate it with subdirectories: -

- 
-   lib/
-   include/c++/gcc-version
-      backward/
-      bits/
-      cpu-vendor-os/bits/
-      ext/
-

If you used the version-specific-libs configure option, then most of - the headers and library files will be moved under - lib/gcc-lib/ instead. -

- -

Using the library

Find the new library at runtime (shared linking only)

If you only built a static library (libstdc++.a), or if you -- 2.7.4