diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index 206d7729b18d..92f9ecb07d81 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,11 @@ +2002-08-19 Jonathan Wakely + + * docs/html/configopts.html, docs/html/documentation.html, + docs/html/install.html, docs/html/22_locale/codecvt.html, + docs/html/22_locale/ctype.html, docs/html/22_locale/howto.html, + docs/html/22_locale/locale.html, + docs/html/22_locale/messages.html: Conform to HTML 4.01 standard. + 2002-08-15 Benjamin Kosnik * include/ext/stdio_filebuf.h (stdio_filebuf): Explicitly set diff --git a/libstdc++-v3/docs/html/22_locale/codecvt.html b/libstdc++-v3/docs/html/22_locale/codecvt.html index 46147d905562..a841c35fbce0 100644 --- a/libstdc++-v3/docs/html/22_locale/codecvt.html +++ b/libstdc++-v3/docs/html/22_locale/codecvt.html @@ -1,14 +1,19 @@ + + + Notes on the codecvt implementation. + + +

Notes on the codecvt implementation.

- +

prepared by Benjamin Kosnik (bkoz@redhat.com) on August 28, 2000 -

1. Abstract

@@ -142,14 +147,14 @@ includes: -

@@ -65,7 +65,6 @@
  • "the latest collection" (for the snapshot or later; see the date on the first page) -

    This generated HTML collection, as above, is also available for download in the libstdc++ snapshots directory at <URL:ftp://gcc.gnu.org/pub/gcc/libstdc++/doxygen/>. diff --git a/libstdc++-v3/docs/html/install.html b/libstdc++-v3/docs/html/install.html index a76a932d92e1..6c2f6668d924 100644 --- a/libstdc++-v3/docs/html/install.html +++ b/libstdc++-v3/docs/html/install.html @@ -88,46 +88,45 @@ features if the underlying support is present.

    -

    Finally, a few system-specific requirements: -

    -
    linux +

    Finally, a few system-specific requirements:

    +
    +
    linux
    -
    If you are using gcc 3.1 or later on linux, and are using - the gnu locale model (enabled by default for sufficient - versions of glibc), the following locales are used and tested - in the libstdc++ testsuites: en_HK, en_US, fr_FR, fr_FR@euro, - de_DE, de_DE@euro, ja_JP.eucjp, and it_IT. Failure to have the - underlying "C" library locale information installed will mean - that C++ named locales for the above regions will not work: - because of this, the libstdc++ testsuite will not pass the - named locale tests. If this isn't an issue, don't worry about - it. If named locales are needed, the underlying locale - information must be installed. Note that rebuilding libstdc++ - after locales are installed is not necessary. +
    If you are using gcc 3.1 or later on linux, and are using + the gnu locale model (enabled by default for sufficient + versions of glibc), the following locales are used and tested + in the libstdc++ testsuites: en_HK, en_US, fr_FR, fr_FR@euro, + de_DE, de_DE@euro, ja_JP.eucjp, and it_IT. Failure to have the + underlying "C" library locale information installed will mean + that C++ named locales for the above regions will not work: + because of this, the libstdc++ testsuite will not pass the + named locale tests. If this isn't an issue, don't worry about + it. If named locales are needed, the underlying locale + information must be installed. Note that rebuilding libstdc++ + after locales are installed is not necessary. -

    To install - support for locales, do only one of the following:

    -

    -

  • install all locales -

    export LC_ALL=C

    -

    rpm -e glibc-common --nodeps

    -

    rpm -i --define "_install_langs all" - glibc-common-2.2.5-34.i386.rpm

    -
    • -
  • install just the necessary locales -

    localedef -i de_DE -f ISO-8859-1 de_DE

    -
    • -

    -
    -
    +

    To install + support for locales, do only one of the following:

    +
      +
    • install all locales +

      export LC_ALL=C

      +

      rpm -e glibc-common --nodeps

      +

      rpm -i --define "_install_langs all" + glibc-common-2.2.5-34.i386.rpm

      +
      • +
    • install just the necessary locales +

      localedef -i de_DE -f ISO-8859-1 de_DE

      +
      • +
    +
    -

    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 @@ -142,7 +141,7 @@ the compiler/libraries, set with the --prefix option to the configure script.
    - Note: +

    Note:

    1. The 3.0 version and following are intended to replace the library that comes with the compiler, so libsrcdir @@ -153,28 +152,27 @@ separate directories. Please don't build out of the source directory.
    -

    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 -
    
    
    
+   
    +   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
    
    
    
+   
    +   mv libsrcdir libstdc++-v3
    
 
 
 
    
@@ -193,10 +191,9 @@
       building the C++ language parts.
    
    
 
-   
    +   
        cd gccbuilddir
    gccsrcdir/configure --prefix=destdir --other-opts...
    
-   
    
 
 
 
    
@@ -214,9 +211,10 @@
    
    
 
    
    [re]building only libstdc++
    
-   
    To rebuild just libstdc++, use:
-      
    +   
    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.
    
    
@@ -229,39 +227,38 @@
       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
-      
    +   
    You're done.  Now install the rebuilt pieces with
    
+   
        make install
    
-      or
-      
    +   
    or
    
+   
        make install-gcc
    make install-target-libstdc++-v3
    
-   
    
 
 
 
    
 
    Post-installation
    
    
    Installation will create the destdir directory and
       populate it with subdirectories:
-      
    +   
    
+   
        lib/
    include/g++-v3/
       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.
    
    
-   
    You can check the status of the build without installing it using
-      
    +   
    You can check the status of the build without installing it using
    
+   
        make check
    
-      or you can check the status of the installed library using
-      
    +   
    or you can check the status of the installed library using
    
+   
        make check-install
    
-      in the libbuilddir directory.
+   
    in the libbuilddir directory.
       These commands will create a 'testsuite' directory underneath
       libbuilddir containing the results of the tests.  We are
       interested in any strange failures of the testsuite; please see
@@ -271,7 +268,7 @@
 
 
    
 
    Using the library
    
-   
  • Find the new library at runtime (shared linking only)
+   
    Find the new library at runtime (shared linking only)
    
        
    If you only built a static library (libstdc++.a), or if you
           specified static linking, you don't have to worry about this.
           But if you built a shared library (libstdc++.so) and linked
@@ -281,6 +278,7 @@
        
    Methods vary for different platforms and different styles, but
           the usual ones are printed to the screen during installation.
           They include:
+       
    
           
      
           
    • At runtime set LD_LIBRARY_PATH in your environment correctly,
               so that the shared library for libstdc++ can be found and
@@ -298,7 +296,6 @@
   
    • More...?  Let us know!
               
    
           
-       
    
        
    Use the ldd(1) utility to show which library the system
           thinks it will get at runtime.
        
    
@@ -306,8 +303,6 @@
           you use Libtool to create your executables, these details are
           taken care of for you.
        
    
-   
-