From c0ed1dea3732c4975a249987c0ac7833fc16d48c Mon Sep 17 00:00:00 2001 From: Phil Edwards Date: Tue, 11 Jul 2000 21:45:08 +0000 Subject: [PATCH] docs: Update sourceware->sources in every HTML file. 2000-07-11 Phil Edwards * docs: Update sourceware->sources in every HTML file. Minor updates. From-SVN: r34967 --- libstdc++-v3/ChangeLog | 4 + libstdc++-v3/docs/17_intro/contribute.html | 2 +- libstdc++-v3/docs/17_intro/howto.html | 10 +- libstdc++-v3/docs/18_support/howto.html | 10 +- libstdc++-v3/docs/19_diagnostics/howto.html | 10 +- libstdc++-v3/docs/20_util/howto.html | 10 +- libstdc++-v3/docs/21_strings/howto.html | 10 +- libstdc++-v3/docs/22_locale/howto.html | 10 +- libstdc++-v3/docs/23_containers/howto.html | 10 +- libstdc++-v3/docs/24_iterators/howto.html | 10 +- libstdc++-v3/docs/25_algorithms/howto.html | 10 +- libstdc++-v3/docs/26_numerics/howto.html | 10 +- libstdc++-v3/docs/27_io/howto.html | 10 +- libstdc++-v3/docs/configopts.html | 36 +-- libstdc++-v3/docs/documentation.html | 11 +- libstdc++-v3/docs/download.html | 6 +- libstdc++-v3/docs/faq/index.html | 58 +++-- libstdc++-v3/docs/faq/index.txt | 114 ++++----- libstdc++-v3/docs/gccrebuild.html | 21 +- libstdc++-v3/docs/header.html | 8 +- libstdc++-v3/docs/index.html | 10 +- libstdc++-v3/docs/install.html | 254 ++++++++++---------- libstdc++-v3/docs/mail.html | 14 +- libstdc++-v3/docs/status.html | 15 +- libstdc++-v3/docs/thanks.html | 2 +- 25 files changed, 339 insertions(+), 326 deletions(-) diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index 011196ad052..c52e42dc808 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,7 @@ +2000-07-11 Phil Edwards + + * docs: Update sourceware->sources in every HTML file. Minor updates. + 2000-07-07 Benjamin Kosnik Clean up configure/build longstanding issues. diff --git a/libstdc++-v3/docs/17_intro/contribute.html b/libstdc++-v3/docs/17_intro/contribute.html index 5aafbdcd5ba..86d8b0d00a8 100644 --- a/libstdc++-v3/docs/17_intro/contribute.html +++ b/libstdc++-v3/docs/17_intro/contribute.html @@ -87,7 +87,7 @@ response from the maintainers) it would have all of these pieces: get the latest version of GNU diff.
  • When you have all these pieces, bundle them up in a mail message -and send it to libstdc++@sourceware.cygnus.com. All patches and related +and send it to libstdc++@sources.redhat.com. All patches and related discussion should be sent to the libstdc++ mailinglist. diff --git a/libstdc++-v3/docs/17_intro/howto.html b/libstdc++-v3/docs/17_intro/howto.html index e3b9e26a10c..33153f6a9eb 100644 --- a/libstdc++-v3/docs/17_intro/howto.html +++ b/libstdc++-v3/docs/17_intro/howto.html @@ -2,14 +2,14 @@ - + libstdc++-v3 HOWTO: Chapter 17 - + - + @@ -145,9 +145,9 @@

    Comments and suggestions are welcome, and may be sent to -Phil Edwards or +Phil Edwards or Gabriel Dos Reis. -
    $Id: howto.html,v 1.2 2000/04/25 06:39:48 bkoz Exp $ +
    $Id: howto.html,v 1.3 2000/05/03 16:11:02 pme Exp $

    diff --git a/libstdc++-v3/docs/18_support/howto.html b/libstdc++-v3/docs/18_support/howto.html index 4f8b414bd2d..2147e1fc9ce 100644 --- a/libstdc++-v3/docs/18_support/howto.html +++ b/libstdc++-v3/docs/18_support/howto.html @@ -2,14 +2,14 @@ - + libstdc++-v3 HOWTO: Chapter 18 - + - + @@ -248,9 +248,9 @@

    Comments and suggestions are welcome, and may be sent to -Phil Edwards or +Phil Edwards or Gabriel Dos Reis. -
    $Id: howto.html,v 1.1 2000/04/21 20:33:31 bkoz Exp $ +
    $Id: howto.html,v 1.2 2000/07/07 21:13:28 pme Exp $

    diff --git a/libstdc++-v3/docs/19_diagnostics/howto.html b/libstdc++-v3/docs/19_diagnostics/howto.html index 94ba36064f2..ad03c792ee8 100644 --- a/libstdc++-v3/docs/19_diagnostics/howto.html +++ b/libstdc++-v3/docs/19_diagnostics/howto.html @@ -2,14 +2,14 @@ - + libstdc++-v3 HOWTO: Chapter 19 - + - + @@ -98,9 +98,9 @@

    Comments and suggestions are welcome, and may be sent to -Phil Edwards or +Phil Edwards or Gabriel Dos Reis. -
    $Id: howto.html,v 1.1 2000/04/21 20:33:31 bkoz Exp $ +
    $Id: howto.html,v 1.2 2000/07/07 21:13:28 pme Exp $

    diff --git a/libstdc++-v3/docs/20_util/howto.html b/libstdc++-v3/docs/20_util/howto.html index 21ea55b9cd5..8a487ad0a1c 100644 --- a/libstdc++-v3/docs/20_util/howto.html +++ b/libstdc++-v3/docs/20_util/howto.html @@ -2,14 +2,14 @@ - + libstdc++-v3 HOWTO: Chapter 20 - + - + @@ -184,9 +184,9 @@

    Comments and suggestions are welcome, and may be sent to -Phil Edwards or +Phil Edwards or Gabriel Dos Reis. -
    $Id: howto.html,v 1.5 2000/03/20 22:16:21 pme Exp $ +
    $Id: howto.html,v 1.1 2000/04/21 20:33:31 bkoz Exp $

    diff --git a/libstdc++-v3/docs/21_strings/howto.html b/libstdc++-v3/docs/21_strings/howto.html index ca1f288f3ad..9e64cca9f40 100644 --- a/libstdc++-v3/docs/21_strings/howto.html +++ b/libstdc++-v3/docs/21_strings/howto.html @@ -2,14 +2,14 @@ - + libstdc++-v3 HOWTO: Chapter 21 - + - + @@ -295,9 +295,9 @@

    Comments and suggestions are welcome, and may be sent to -Phil Edwards or +Phil Edwards or Gabriel Dos Reis. -
    $Id: howto.html,v 1.1 2000/04/21 20:33:31 bkoz Exp $ +
    $Id: howto.html,v 1.2 2000/07/07 21:13:28 pme Exp $

    diff --git a/libstdc++-v3/docs/22_locale/howto.html b/libstdc++-v3/docs/22_locale/howto.html index 70d4add93f4..62d0ce88964 100644 --- a/libstdc++-v3/docs/22_locale/howto.html +++ b/libstdc++-v3/docs/22_locale/howto.html @@ -2,14 +2,14 @@ - + libstdc++-v3 HOWTO: Chapter 22 - + - + @@ -61,9 +61,9 @@

    Comments and suggestions are welcome, and may be sent to -Phil Edwards or +Phil Edwards or Gabriel Dos Reis. -
    $Id: howto.html,v 1.5 2000/03/20 22:16:21 pme Exp $ +
    $Id: howto.html,v 1.1 2000/04/21 20:33:31 bkoz Exp $

    diff --git a/libstdc++-v3/docs/23_containers/howto.html b/libstdc++-v3/docs/23_containers/howto.html index f39731b845c..c35b800b2e8 100644 --- a/libstdc++-v3/docs/23_containers/howto.html +++ b/libstdc++-v3/docs/23_containers/howto.html @@ -2,14 +2,14 @@ - + libstdc++-v3 HOWTO: Chapter 23 - + - + @@ -236,9 +236,9 @@

    Comments and suggestions are welcome, and may be sent to -Phil Edwards or +Phil Edwards or Gabriel Dos Reis. -
    $Id: howto.html,v 1.8 2000/03/23 20:58:38 pme Exp $ +
    $Id: howto.html,v 1.1 2000/04/21 20:33:31 bkoz Exp $

    diff --git a/libstdc++-v3/docs/24_iterators/howto.html b/libstdc++-v3/docs/24_iterators/howto.html index f2aef6c803b..0999056906a 100644 --- a/libstdc++-v3/docs/24_iterators/howto.html +++ b/libstdc++-v3/docs/24_iterators/howto.html @@ -2,14 +2,14 @@ - + libstdc++-v3 HOWTO: Chapter 24 - + - + @@ -85,9 +85,9 @@

    Comments and suggestions are welcome, and may be sent to -Phil Edwards or +Phil Edwards or Gabriel Dos Reis. -
    $Id: howto.html,v 1.1 2000/04/21 20:33:31 bkoz Exp $ +
    $Id: howto.html,v 1.2 2000/07/07 21:13:28 pme Exp $

    diff --git a/libstdc++-v3/docs/25_algorithms/howto.html b/libstdc++-v3/docs/25_algorithms/howto.html index d7d0e3523d4..e038b6b4077 100644 --- a/libstdc++-v3/docs/25_algorithms/howto.html +++ b/libstdc++-v3/docs/25_algorithms/howto.html @@ -2,14 +2,14 @@ - + libstdc++-v3 HOWTO: Chapter 25 - + - + @@ -87,9 +87,9 @@

    Comments and suggestions are welcome, and may be sent to -Phil Edwards or +Phil Edwards or Gabriel Dos Reis. -
    $Id: howto.html,v 1.1 2000/04/21 20:33:31 bkoz Exp $ +
    $Id: howto.html,v 1.2 2000/07/07 21:13:28 pme Exp $

    diff --git a/libstdc++-v3/docs/26_numerics/howto.html b/libstdc++-v3/docs/26_numerics/howto.html index c31743b1ee6..51b60a89bbe 100644 --- a/libstdc++-v3/docs/26_numerics/howto.html +++ b/libstdc++-v3/docs/26_numerics/howto.html @@ -2,14 +2,14 @@ - + libstdc++-v3 HOWTO: Chapter 26 - + - + @@ -133,9 +133,9 @@

    Comments and suggestions are welcome, and may be sent to -Phil Edwards or +Phil Edwards or Gabriel Dos Reis. -
    $Id: howto.html,v 1.2 2000/06/28 15:14:39 gdr Exp $ +
    $Id: howto.html,v 1.3 2000/07/07 21:13:28 pme Exp $

    diff --git a/libstdc++-v3/docs/27_io/howto.html b/libstdc++-v3/docs/27_io/howto.html index 1de9a35969e..960156527b7 100644 --- a/libstdc++-v3/docs/27_io/howto.html +++ b/libstdc++-v3/docs/27_io/howto.html @@ -2,14 +2,14 @@ - + libstdc++-v3 HOWTO: Chapter 27 - + - + @@ -334,9 +334,9 @@

    Comments and suggestions are welcome, and may be sent to -Phil Edwards or +Phil Edwards or Gabriel Dos Reis. -
    $Id: howto.html,v 1.7 1999/12/15 16:57:06 pme Exp $ +
    $Id: howto.html,v 1.1 2000/04/21 20:33:32 bkoz Exp $

    diff --git a/libstdc++-v3/docs/configopts.html b/libstdc++-v3/docs/configopts.html index 18d6367961a..4acff06ce8c 100644 --- a/libstdc++-v3/docs/configopts.html +++ b/libstdc++-v3/docs/configopts.html @@ -2,14 +2,14 @@ - + libstdc++-v3 configure options - + - + @@ -17,8 +17,8 @@ options

    The latest version of this document is always available at - - http://sourceware.cygnus.com/libstdc++/configopts.html. + + http://sources.redhat.com/libstdc++/configopts.html.

    To the libstdc++-v3 homepage. @@ -29,17 +29,17 @@ options

    Here are some of the non-obvious options to libstdc++'s configure. Keep in mind that - they + they all have opposite forms as well (enable/disable and with/without). The defaults are for the latest snapshot, 2.90.8.

    --enable-multilib [default]

    This is part of the generic multilib support for building - cross compilers. As such, targets like "powerpc-elf" will be - have libstdc++ built many different ways: "-msoft-float" and - not, etc. A different libstdc++ will be built for each of the - different multilib versions. This option is on by default. + cross compilers. As such, targets like "powerpc-elf" will + have libstdc++ built many different ways: "-msoft-float" and + not, etc. A different libstdc++ will be built for each of the + different multilib versions. This option is on by default.

    --enable-debug @@ -61,7 +61,7 @@ options

    Select a target-specific I/O package. As of libstdc++-v3 snapshot 2.90.8, the choices are 'libio' to specify the GNU I/O package (from - glibc, the + glibc, the GNU C library), or 'wince' to specify the Microsoft Windows CE library. Eventually a generic cstdio interface will be added so that people who want to use libstdc++-v3 with say, the Palm @@ -115,11 +115,11 @@ options at it. It's described in its own little page. Note that other --enable flags will interact with this one. In libstdc++-v3 snapshot 2.90.8, - this is enabled by default, with DIR - set to '../..' , so that building - the complete GCC sources with libstdc++-v3 in place works - transparently. Since then, library sources have been merged - into the compiler sources, and this option has been removed. + this is enabled by default, with DIR set to + '../..' , so that building the complete GCC sources + with libstdc++-v3 in place works transparently. Since then, + library sources have been merged into the compiler sources, + and this option has been removed.

    --enable-cxx-flags=FLAGS @@ -149,7 +149,7 @@ options

    -

    Return to the top of the README or +

    Return to the top of the page or to the homepage.

    @@ -158,7 +158,7 @@ options

    -$Id: configopts.html,v 1.4 2000/05/19 19:55:50 pme Exp $ +$Id: configopts.html,v 1.5 2000/07/07 21:13:27 pme Exp $

    diff --git a/libstdc++-v3/docs/documentation.html b/libstdc++-v3/docs/documentation.html index 338fd39e32e..26fd066f50a 100644 --- a/libstdc++-v3/docs/documentation.html +++ b/libstdc++-v3/docs/documentation.html @@ -1,7 +1,9 @@ - +

    All of these documents (in fact, this entire homepage set) are + bundled with the library source, under the docs subdirectory. +

    Introductory notes for libstdc++

    This is a short list of text files pertaining to this @@ -22,8 +24,9 @@

  • HEADER_POLICY - header naming and sub-include structure
  • PROBLEMS -
  • README - - directory structure + +
  • README - directory structure
  • RELEASE-NOTES - instructions for building, using
  • TODO @@ -43,7 +46,7 @@
    -

    Chapter-Specific Information and Advice

    +

    Chapter-Specific Information, Extensions, and Advice

    1. Chapter 17 (Intro)
    2. Chapter 18 (Library Support) diff --git a/libstdc++-v3/docs/download.html b/libstdc++-v3/docs/download.html index bac2ef5c194..652dd98d9df 100644 --- a/libstdc++-v3/docs/download.html +++ b/libstdc++-v3/docs/download.html @@ -8,9 +8,9 @@ link to the FTP site is given directly, encouraging mirror usage. -->

      Get the snapshot archive via FTP from - <URL:ftp://sourceware.cygnus.com/pub/libstdc++/>. + <URL:ftp://sources.redhat.com/pub/libstdc++/>. You will almost certainly need to use one of the - mirror sites + mirror sites due to the extremely heavy load on the main server.

      @@ -27,7 +27,7 @@ Directions are here.

      -

      One you have the GCC sources checked out over CVS, you can use the +

      Once you have the GCC sources checked out over CVS, you can use the contrib/gcc_update script to retrieve the latest changes, and automatically update the timestamps of certain files. With the timestamps updated, you won't need autoconf or the other tools (unless diff --git a/libstdc++-v3/docs/faq/index.html b/libstdc++-v3/docs/faq/index.html index 2b26466c2a5..5387090fb43 100644 --- a/libstdc++-v3/docs/faq/index.html +++ b/libstdc++-v3/docs/faq/index.html @@ -2,26 +2,26 @@ - + libstdc++-v3 FAQ - + - +

      libstdc++ Frequently Asked Questions

      The latest version of this document is always available at - -http://sourceware.cygnus.com/libstdc++/faq/.

      + +http://sources.redhat.com/libstdc++/faq/.

      To the libstdc++-v3 homepage. @@ -94,7 +94,7 @@ http://sourceware.cygnus.com/libstdc++/faq/.

      as described in chapters 17 through 27 and annex D. As the library reaches stable plateaus, it is captured in a snapshot and released. The current release is the +HREF="ftp://sources.redhat.com/pub/libstdc++/libstdc++-2.90.8.tar.gz">the ninth snapshot. For those who want to see exactly how far the project has come, or just want the latest bleeding-edge code, the up-to-date source is available over @@ -148,7 +148,7 @@ HREF="http://gcc.gnu.org/gcc-2.95/buildstat.html">portability

      1.4 How do I get libstdc++?

      The ninth (and latest) snapshot of libstdc++-v3 is +HREF="ftp://sources.redhat.com/pub/libstdc++/libstdc++-2.90.8.tar.gz"> available via ftp.

      The homepage @@ -165,7 +165,7 @@ HREF="ftp://sourceware.cygnus.com/pub/libstdc++/libstdc++-2.90.8.tar.gz">

      1.5 When is libstdc++ going to be finished?

      Nathan Myers gave the best of all possible answers in a - recent Usenet article.

      + Usenet article.

      1.6 How do I contribute to the effort?

      @@ -225,12 +225,12 @@ HREF="ftp://sourceware.cygnus.com/pub/libstdc++/libstdc++-2.90.8.tar.gz"> At present, you do not need to be subscribed to the list to send a message to it. More information is available on the homepage (including how to browse the list archives); to send - to the list, use - libstdc++@sourceware.cygnus.com. + to the list, use + libstdc++@sources.redhat.com.

      If you have a question that you think should be included here, or if you have a question about a question/answer here, - contact Phil Edwards + contact Phil Edwards or Gabriel Dos Reis.

      @@ -247,8 +247,8 @@ HREF="ftp://sourceware.cygnus.com/pub/libstdc++/libstdc++-2.90.8.tar.gz"> than building the GCC 2.[78] series was.
    3. If you plan on hacking around with the makefiles, you will need the tools autoconfand automake. +HREF="http://sources.redhat.com/autoconf/">autoconfand automake.
    4. GNU Make is the only make that supports these makefiles.

      @@ -283,13 +283,13 @@ HREF="http://sourceware.cygnus.com/automake/">automake.

      2.3 What is this CVS thing that you keep mentioning?

      -

      The Concurrent Versions System is one of several - revision control packages. It was selected for GNU projects - because it's free and very high quality. The The Concurrent Versions System is one of several revision + control packages. It was selected for GNU projects because it's + free (speech), free (beer), and very high quality. The CVS entry in the GNU software catalogue has a better description as - well as a link to the makers - of CVS. + well as a + link to the makers of CVS.

      The "anonymous client checkout" feature of CVS is similar to anonymous FTP in that it allows anyone to retrieve @@ -369,14 +369,12 @@ HREF="http://sourceware.cygnus.com/automake/">automake. occasions when the test does not hang, the zero-division is in fact trapped. That doesn't prevent hanging elsewhere.

      -

      You have two options. - You can wait until the signal-handling in Cygwin is reworked - and released; this is planned to take "a few weeks" - and will result in a fix sometime in late December or early January. +

      You have two options. You can get a newer cygwin1.dll (see the + Cygwin paragraph in the + installation instructions). Or you can get a prebuilt set of bits/std_limits.h and src/limitsMEMBERS.cc files from Mumit Khan's - Cygwin-related - website. + Cygwin-related website.

      @@ -543,10 +541,10 @@ to the list, Nathan Myers announced that he has started a list of instance) will of course be a continuing task.

      This +HREF="http://sources.redhat.com/ml/libstdc++/1999/msg00080.html">This question about the next libstdc++ prompted some brief but interesting speculation. +HREF="http://sources.redhat.com/ml/libstdc++/1999/msg00084.html">speculation.

      @@ -610,10 +608,10 @@ HREF="http://sourceware.cygnus.com/ml/libstdc++/1999/msg00084.html">speculation<

      This is assuming that your idea of "multithreaded" is the same as ours... The general question of multithreading and libstdc++-v3 is addressed in the chapter-specific advice for -Library +Library Introduction. Threadsafe containers are covered in more detail in -the +the Received Wisdom section on containers. @@ -643,9 +641,9 @@ HREF="http://sourceware.cygnus.com/ml/libstdc++/1999/msg00084.html">speculation<

      Comments and suggestions are welcome, and may be sent to -Phil Edwards or +Phil Edwards or Gabriel Dos Reis. -
      $Id: index.html,v 1.3 2000/05/24 18:35:37 pme Exp $ +
      $Id: index.html,v 1.4 2000/06/28 18:57:27 pme Exp $

      diff --git a/libstdc++-v3/docs/faq/index.txt b/libstdc++-v3/docs/faq/index.txt index 6d6fe5669f4..3c47e697baf 100644 --- a/libstdc++-v3/docs/faq/index.txt +++ b/libstdc++-v3/docs/faq/index.txt @@ -4,7 +4,7 @@ libstdc++ Frequently Asked Questions The latest version of this document is always available at - [2]http://sourceware.cygnus.com/libstdc++/faq/. + [2]http://sources.redhat.com/libstdc++/faq/. To the [3]libstdc++-v3 homepage. _________________________________________________________________ @@ -111,8 +111,8 @@ 1.5 When is libstdc++ going to be finished? - Nathan Myers gave the best of all possible answers in [42]a recent - Usenet article. + Nathan Myers gave the best of all possible answers in [42]a Usenet + article. _________________________________________________________________ 1.6 How do I contribute to the effort? @@ -167,7 +167,7 @@ not need to be subscribed to the list to send a message to it. More information is available on the homepage (including how to browse the list archives); to send to the list, use - [46]libstdc++@sourceware.cygnus.com. + [46]libstdc++@sources.redhat.com. If you have a question that you think should be included here, or if you have a question about a question/answer here, contact [47]Phil @@ -218,9 +218,10 @@ 2.3 What is this CVS thing that you keep mentioning? The Concurrent Versions System is one of several revision control - packages. It was selected for GNU projects because it's free and very - high quality. The [53]CVS entry in the GNU software catalogue has a - better description as well as a [54]link to the makers of CVS. + packages. It was selected for GNU projects because it's free (speech), + free (beer), and very high quality. The [53]CVS entry in the GNU + software catalogue has a better description as well as a [54]link to + the makers of CVS. The "anonymous client checkout" feature of CVS is similar to anonymous FTP in that it allows anyone to retrieve the latest libstdc++ sources. @@ -292,12 +293,10 @@ the test does not hang, the zero-division is in fact trapped. That doesn't prevent hanging elsewhere. - You have two options. You can wait until the signal-handling in Cygwin - is reworked and released; this is planned to take "a few weeks" and - will result in a fix sometime in late December or early January. Or - you can get a prebuilt set of bits/std_limits.h and - src/limitsMEMBERS.cc files from Mumit Khan's [55]Cygwin-related - website. + You have two options. You can get a newer cygwin1.dll (see the Cygwin + paragraph in the [55]installation instructions). Or you can get a + prebuilt set of bits/std_limits.h and src/limitsMEMBERS.cc files from + Mumit Khan's [56]Cygwin-related website. _________________________________________________________________ 4.0 Known Bugs and Non-Bugs @@ -367,16 +366,16 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)' 4.3 Bugs in the C++ language/lib specification - Yes, unfortunately, there are some. In a [56]message to the list, + Yes, unfortunately, there are some. In a [57]message to the list, Nathan Myers announced that he has started a list of problems in the ISO C++ Standard itself, especially with regard to the chapters that - concern the library. The list itself is [57]posted on his website. + concern the library. The list itself is [58]posted on his website. Developers who are having problems interpreting the Standard may wish to consult his notes. For those people who are not part of the ISO Library Group (i.e., nearly all of us needing to read this page in the first place :-), a - public list of the library defects is occasionally published [58]here. + public list of the library defects is occasionally published [59]here. _________________________________________________________________ 4.4 Things in libstdc++ that look like bugs @@ -397,16 +396,16 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)' If you have found a bug in the library and you think you have a working fix, then send it in! The main GCC site has a page on - [59]submitting patches that covers the procedure, but for libstdc++ + [60]submitting patches that covers the procedure, but for libstdc++ you should of course send the patch to our mailing list, not the GCC - mailing list. The libstdc++ [60]contributors' page also talks about + mailing list. The libstdc++ [61]contributors' page also talks about how to submit patches. In addition to the description, the patch, and the ChangeLog entry, it is a Good Thing if you can additionally create a small test program to test for the presence of the bug that your patch fixes. Bugs have a way of being reintroduced; if an old bug creeps back in, it will be - caught immediately by the [61]testsuite -- but only if such a test + caught immediately by the [62]testsuite -- but only if such a test exists. _________________________________________________________________ @@ -442,13 +441,13 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)' Bugfixes and rewrites (to improve or fix thread safety, for instance) will of course be a continuing task. - [62]This question about the next libstdc++ prompted some brief but - interesting [63]speculation. + [63]This question about the next libstdc++ prompted some brief but + interesting [64]speculation. _________________________________________________________________ 5.3 What about the STL from SGI? - The [64]STL from SGI is merged into libstdc++-v3 with changes as + The [65]STL from SGI is merged into libstdc++-v3 with changes as necessary. Currently release 3.3 is being used. Changes in the STL usually produce some weird bugs and lots of changes in the rest of the libstd++ source as we scramble to keep up. :-) @@ -484,7 +483,7 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)' your libraries each time you get a new compiler snapshot.) Towards the end of July 1999, this subject was brought up again on the - mailing list under a different name. The related [65]thread (by the + mailing list under a different name. The related [66]thread (by the name HOWTO-honor-std) is very instructive. More info is at the end of RELEASE-NOTES. @@ -498,8 +497,8 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)' This is assuming that your idea of "multithreaded" is the same as ours... The general question of multithreading and libstdc++-v3 is - addressed in the chapter-specific advice for [66]Library Introduction. - Threadsafe containers are covered in more detail in [67]the Received + addressed in the chapter-specific advice for [67]Library Introduction. + Threadsafe containers are covered in more detail in [68]the Received Wisdom section on containers. _________________________________________________________________ @@ -511,22 +510,22 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)' their two-meeting commitment for voting rights, may get a copy of the standard from their respective national standards organization. In the USA, this national standards organization is ANSI and their website is - right [68]here. (And if you've already registered with them, clicking - this link will take you to directly to the place where you can [69]buy + right [69]here. (And if you've already registered with them, clicking + this link will take you to directly to the place where you can [70]buy the standard on-line. - Who is your country's member body? Visit the [70]ISO homepage and find + Who is your country's member body? Visit the [71]ISO homepage and find out! _________________________________________________________________ - Comments and suggestions are welcome, and may be sent to [71]Phil - Edwards or [72]Gabriel Dos Reis. - $Id: index.html,v 1.3 2000/05/24 18:35:37 pme Exp $ + Comments and suggestions are welcome, and may be sent to [72]Phil + Edwards or [73]Gabriel Dos Reis. + $Id: index.html,v 1.4 2000/06/28 18:57:27 pme Exp $ References - 1. http://sourceware.cygnus.com/libstdc++/ - 2. http://sourceware.cygnus.com/libstdc++/faq/index.html + 1. http://sources.redhat.com/libstdc++/ + 2. http://sources.redhat.com/libstdc++/faq/index.html 3. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/index.html 4. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#1_0 5. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#1_1 @@ -559,41 +558,42 @@ References 32. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#5_5 33. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#5_6 34. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#5_7 - 35. ftp://sourceware.cygnus.com/pub/libstdc++/libstdc++-2.90.8.tar.gz + 35. ftp://sources.redhat.com/pub/libstdc++/libstdc++-2.90.8.tar.gz 36. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/17_intro/DESIGN 37. http://gcc.gnu.org/ 38. http://gcc.gnu.org/gcc-2.95/buildstat.html 39. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/index.html - 40. ftp://sourceware.cygnus.com/pub/libstdc++/libstdc++-2.90.8.tar.gz + 40. ftp://sources.redhat.com/pub/libstdc++/libstdc++-2.90.8.tar.gz 41. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/index.html 42. http://www.deja.com/getdoc.xp?AN=469581698&fmt=text 43. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/17_intro/contribute.html 44. http://www.boost.org/ 45. http://gcc.gnu.org/fom_serv/cache/33.html - 46. mailto:libstdc++@sourceware.cygnus.com - 47. mailto:pme@sourceware.cygnus.com + 46. mailto:libstdc++@sources.redhat.com + 47. mailto:pme@sources.redhat.com 48. mailto:gdr@egcs.cygnus.com - 49. http://sourceware.cygnus.com/autoconf/ - 50. http://sourceware.cygnus.com/automake/ + 49. http://sources.redhat.com/autoconf/ + 50. http://sources.redhat.com/automake/ 51. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/documentation.html 52. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/17_intro/RELEASE-NOTES 53. http://www.gnu.org/software/cvs/cvs.html 54. http://www.cyclic.com/ - 55. http://www.xraylith.wisc.edu/~khan/software/gnu-win32/libstdc++-v3.html - 56. file://localhost/ml/libstdc++/1998/msg00006.html - 57. http://www.cantrip.org/draft-bugs.txt - 58. http://anubis.dkuug.dk/jtc1/sc22/wg21/ - 59. http://gcc.gnu.org/contribute.html - 60. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/17_intro/contribute.html - 61. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#2_4 - 62. http://sourceware.cygnus.com/ml/libstdc++/1999/msg00080.html - 63. http://sourceware.cygnus.com/ml/libstdc++/1999/msg00084.html - 64. http://www.sgi.com/Technology/STL/ - 65. file://localhost/ml/libstdc++/1999-q3/msg00066.html - 66. http://sourceware.cygnus.com/libstdc++/17_intro/howto.html#3 - 67. http://sourceware.cygnus.com/libstdc++/23_containers/howto.html - 68. http://www.ansi.org/ - 69. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998 - 70. http://www.iso.ch/ - 71. mailto:pme@sourceware.cygnus.com - 72. mailto:gdr@egcs.cygnus.com + 55. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/install.html + 56. http://www.xraylith.wisc.edu/~khan/software/gnu-win32/libstdc++-v3.html + 57. file://localhost/ml/libstdc++/1998/msg00006.html + 58. http://www.cantrip.org/draft-bugs.txt + 59. http://anubis.dkuug.dk/jtc1/sc22/wg21/ + 60. http://gcc.gnu.org/contribute.html + 61. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/17_intro/contribute.html + 62. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#2_4 + 63. http://sources.redhat.com/ml/libstdc++/1999/msg00080.html + 64. http://sources.redhat.com/ml/libstdc++/1999/msg00084.html + 65. http://www.sgi.com/Technology/STL/ + 66. file://localhost/ml/libstdc++/1999-q3/msg00066.html + 67. http://sources.redhat.com/libstdc++/17_intro/howto.html#3 + 68. http://sources.redhat.com/libstdc++/23_containers/howto.html + 69. http://www.ansi.org/ + 70. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998 + 71. http://www.iso.ch/ + 72. mailto:pme@sources.redhat.com + 73. mailto:gdr@egcs.cygnus.com diff --git a/libstdc++-v3/docs/gccrebuild.html b/libstdc++-v3/docs/gccrebuild.html index b631729afba..3539ae2e0ad 100644 --- a/libstdc++-v3/docs/gccrebuild.html +++ b/libstdc++-v3/docs/gccrebuild.html @@ -2,25 +2,27 @@ - + How to automatically rebuild libgcc.a. - + - +

      --enable-libgcc-rebuild

      -

      NOTE: If using the --enable-libstdcxx-v3 approach to - configuring, the std namespace will be turned on for you, without - going this route. Only use this flag if you'd like to experiment with - yet more binary incompatibilities, as discussed below. +

      NOTA BENE: If using the --enable-libstdcxx-v3 approach + to configuring, the std namespace will be turned on for you, without + going this route. Only use this flag if you'd like to experiment + with yet more binary incompatibilities, as discussed below.

      +
      +

      If you build libstdc++ using certain flags (e.g., -fnew-abi), then programs that use some of the new C++ language features (like namespace std and RTTI) will only link if the compiler's libgcc is built using @@ -42,7 +44,8 @@ as objdir; here it will be called GCCobjdir.

      -

      This was a kludge, and after the library sources were merged into +

      This was required for a few busy months of development, but was + always acknowledged a kludge. After the library sources were merged into the compiler sources, this was commented out. If you must re-enable it, you amy do so by uncommenting the GLIBCPP_ENABLE_RELIBGCC line in configure.in and regenerating. @@ -118,7 +121,7 @@

      -$Id: gccrebuild.html,v 1.3 2000/06/19 22:20:15 bkoz Exp $ +$Id: gccrebuild.html,v 1.4 2000/07/07 21:13:27 pme Exp $

      diff --git a/libstdc++-v3/docs/header.html b/libstdc++-v3/docs/header.html index 467a1fd7d73..b3a01ed532b 100644 --- a/libstdc++-v3/docs/header.html +++ b/libstdc++-v3/docs/header.html @@ -2,14 +2,14 @@ - + Standard C++ Library v3 - + - + @@ -60,7 +60,7 @@
      diff --git a/libstdc++-v3/docs/index.html b/libstdc++-v3/docs/index.html index 86e2f6d9577..44f3fec2010 100644 --- a/libstdc++-v3/docs/index.html +++ b/libstdc++-v3/docs/index.html @@ -10,9 +10,9 @@

      What... is your quest?

      -

      This is an ongoing project - to implement the ISO 14882 Standard C++ Library as described in chapters - 17 through 27 and Annex D. Participation is welcome! +

      This is an ongoing project to implement the ISO 14882 Standard + C++ Library as described in chapters 17 through 27 and Annex D. + Participation is welcome!

      What... is the airspeed velocity of an unladen swallow?

      @@ -28,9 +28,11 @@

      News

      +
      2000-04-21 +
      Officially merged library sources into GCC.
      2000-03-24
      Ninth snapshot release, - + libstdc++-2.90.8.tar.gz.
      1999-12-21
      Eighth snapshot release, libstdc++-2.90.7.tar.gz. diff --git a/libstdc++-v3/docs/install.html b/libstdc++-v3/docs/install.html index 00e0f6d1f77..c6854e7a2ce 100644 --- a/libstdc++-v3/docs/install.html +++ b/libstdc++-v3/docs/install.html @@ -2,22 +2,22 @@ - + libstdc++-v3 Installation Instructions - + - +

      libstdc++-v3 INSTALL

      The latest version of this document is always available at - - http://sourceware.cygnus.com/libstdc++/install.html. + + http://sources.redhat.com/libstdc++/install.html.

      To the libstdc++-v3 homepage. @@ -52,9 +52,9 @@ the configure scripts you'll need the nuevo automake (version 1.4 from Cygnus, not the one on the net. In addition, libtool and autoconf are also required to be installed in the same - location as the new automake: you can get them all in one + location as the new automake: you can get them all in one easy-to-use tarball - here. +here.

      If you don't have bash, and want to run 'make check' to test your build, you'll need to get bash 2.x. Also recommended @@ -63,21 +63,22 @@

      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, and you can get snapshots (as well as releases) of binutils - here. + 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, and you can get snapshots (as + well as releases) of binutils + here.

      -

      Finally, if you are using cygwin to compile libstdc++-v3 on - win32, you'll have to get a version of the cygwin.dll that is - dated on or after February 1, 2000. This is necessary to +

      Finally, if you are using Cygwin to compile libstdc++-v3 on + Win32, you'll have to get a version of the cygwin1.dll that is + dated on or after February 1, 2000. This is necessary to successfully run the script "mknumeric_limits" which probes the - floating-point environment of the host in question--before this - date, Cygwin would freeze when running this script. In addition, + floating-point environment of the host in question -- before this + date, Cygwin would freeze when running this script. In addition, you may want to get a current version of libtool (say libtool-1.3.4 and above) as earlier versions supposedly had problems creating shared libraries. @@ -86,8 +87,8 @@

      Setting up the source directories

      -

      As the libstdc++-v3 sources and the core GCC sources move - towards convergence, more and more effort goes to building the +

      As the libstdc++-v3 sources and the core GCC sources have + converged, more and more effort goes to building the library as the default version to be shipped with g++. With the 2.90.8 snapshot, and especially for CVS versions after this release, this is treated as the usual scenario. If you want to @@ -133,97 +134,94 @@

      -

      -Since the release of libstdc++-2.90.8, configuration patches have gone -into CVS gcc that make the management of the various libstdc++ source -trees a bit easier. Because of this, both libstdc++-v2 and -libstdc++-v3 and live together more or less in peace, without the need -for soft linking. If a CVS gcc source directory after April 5, 2000 is -being used, then the directions are slightly different: please pick -which of the following two scenarios best represents your particular -situation. +

      Since the release of libstdc++-2.90.8, configuration patches have gone + into CVS gcc that make the management of the various libstdc++ source + trees a bit easier. Because of this, both libstdc++-v2 and + libstdc++-v3 and live together more or less in peace, without the need + for soft linking. If a CVS gcc source directory after April 5, 2000 is + being used, then the directions are slightly different: please pick + which of the following two scenarios best represents your particular + situation. +

      -

      -...with gcc-2.95.2 -

      Unpack the gccsrcdir and go into that directory. For - instance, gcc-2.95.2 is a valid gccsrcdir. - Once in gccsrcdir, you'll need to rename the directories - called libstdc++ and libio like so: - 

      -      mv libstdc++ libstdc++-v2
-      mv libio libio-v2
      -

      -

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

      +   
      ...with gcc-2.95.2
+      
      Unpack the gccsrcdir and go into that directory.  For
+         instance, gcc-2.95.2 is a valid gccsrcdir.
+         Once in gccsrcdir, you'll need to rename the directories
+         called  libstdc++  and  libio  like so:
+         
      +   mv libstdc++ libstdc++-v2
+   mv libio libio-v2
      
+      
      
+      
      Next, unpack the libstdc++-v3 library tarball into the
+         gccsrcdir directory; it will create a
+         libsrcdir called libstdc++-version:
+         
          gzip -dc libstdc++-version.tar.gz | tar xf -
      
-   
      
-   
      Finally, make a soft link between libsrcdir and
-      libstdc++ so that libstdc++-v3 will be the default C++
-      library used.
-      
      +      
      
+      
      Finally, make a soft link between libsrcdir and
+         libstdc++ so that libstdc++-v3 will be the default C++
+         library used.
+         
          ln -s libsrcdir libstdc++
      
-      This complexity of having two completely separate libstdc++
-      libraries is necessary so that you can unlink libsrcdir
-      and update the compiler sources.  If you're not this adventurous, or
-      would not like to switch between different C++ standard libraries,
-      this extra effort is probably wasted; just remove the v2 sources.
+         This complexity of having two completely separate libstdc++
+         libraries is necessary so that you can unlink libsrcdir
+         and update the compiler sources.  If you're not this adventurous, or
+         would not like to switch between different C++ standard libraries,
+         this extra effort is probably wasted; just remove the v2 sources.
+      
      
    
      
 
-
      
-...with CVS gcc 
-   
       Check out or download the gcc sources: the
-   resulting source director is gccsrcdir.
-   
      
-   
      Next, unpack the libstdc++-v3 library tarball into this
-      gccsrcdir directory; it will create a
-      libsrcdir called libstdc++-version:
-      
      +   
      ...with CVS gcc 
+      
      Check out or download the gcc sources: the resulting source
+         directory is gccsrcdir.
+      
      
+      
      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 -
      
-   
      
-
-   
       If CVS libstdc++-v3 is being used instead of a snapshot's
-   tarball, then move the source directory from the cvs checkout into
-   the gccsrcdir directory.
-
-   
      Finally, rename libsrcdir to
-      libstdc++-v3 so that gcc's configure flags will be able
-      to deal with the new library.
-      
      +      
      
+   
+      
      If CVS libstdc++-v3 is being used instead of a snapshot's tarball,
+         then move the source directory from the CVS checkout into the
+         gccsrcdir directory.
+   
+      
      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
      
+   
      Due to namespaces, when building libstdc++-v3 you'll have to configure
+      the entire gccsrcdir directory.  The full list of libstdc++-v3
+      specific configuration options, not dependent on the specific compiler
+      release being used, can be found here.
+   
      
+   
      Consider possibly using --enable-languages=c++ to save time by only
+      building the C++ language parts.
+   
      
 
-Due to namespaces, when building libstdc++-v3 you'll have to configure
-the entire gccsrcdir directory. The full list of
-libstdc++-v3 specific configuration options, not dependent on the
-specific compiler release being used, can be found  here  
-
      
-[Consider possibly using
---enable-languages=c++ to save time by only building the C++ language
-parts]
+   
      ...with gcc-2.95.2
+      
      +   gccsrcdir/configure --prefix=destdir
      
+   
      
+   
+   
      ...with CVS gcc 
+      
      +   gccsrcdir/configure --prefix=destdir --enable-libstdcxx-v3
      
+   
      
+   
+   
      Adding --enable-libstdcxx-v3 automatically selects libstdc++-v3
+      as the C++ library to be used alongside the C++ compiler being built,
+      and also enables -fhonor-std by default.  This option is not available
+      with gcc-2.95.2.
+   
      
 
-
      
-...with gcc-2.95.2
-
      
-   gccsrcdir/configure --prefix=destdir
-       
      
-
      
-
-
      
-...with CVS gcc 
-
      
-
-   gccsrcdir/configure --prefix=destdir --enable-libstdcxx-v3
-
-
      
-[Adding  --enable-libstdcxx-v3 automatically selects
-libstdc++-v3 as the C++ library to be used alongside the C++ compiler
-being built, and also enables -fhonor-std by default. This option is not available with gcc-2.95.2] 
      
 
 
      
 
      Building and installing the library
      
@@ -240,28 +238,31 @@ being built, and also enables -fhonor-std by default. This option is not availab
    
      
 
    
      [re]building only libstdc++
      
-  Due to differences in the configure process, the resulting Makefiles
-  in thegccbuilddir will have different rules depending on
-  the source base being used.
-
      
-...with gcc-2.95.2
-
      
-   libstdc++-rule is libstdc++
+   
      Due to differences in the configure process, the resulting Makefiles
+      in thegccbuilddir will have different rules depending on
+      the source base being used.
+   
      
 
-
      
-
-
      
-...with CVS gcc 
-
      
-   libstdc++-rule is libstdc++-v3
-
      
-
-To rebuild just libstdc++, use:
-
      
-   
      make all-target-libstdc++-rule
      
+   
      ...with gcc-2.95.2
+      
      
+      libstdc++-rule is libstdc++
+      
      
+   
      
+   
+   
      ...with CVS gcc 
+      
      
+      libstdc++-rule is libstdc++-v3
+      
      
+   
      
+   
+   
      To rebuild just libstdc++, use:
+      
      +   make all-target-libstdc++-rule
      
       This will configure and build the C++ library in the
       gccbuilddir/cpu-vendor-OS/libstdc++ directory.
-      As en example, for CVS gcc this would be make all-target-libstdc++-v3, and for gcc-2.95.2 it would be make all-target-libstdc++  
+      As en example, for CVS gcc this would be
+      make all-target-libstdc++-v3, and for gcc-2.95.2 it would be
+      make all-target-libstdc++
    
      
    
      If the build fails with a "warning: can't inline call"
       message when compiling stringMAIN.cc, see the
@@ -269,12 +270,13 @@ To rebuild just libstdc++, use:
    
      
    
      You're done.  Now install the rebuilt pieces with
       
      -   make install
-
-   or 
-
+   make install
      
+      or 
+      
          make install-gcc
    make install-target-libstdc++-rule
      
+   
      
+
 
 
      
 
      Post-installation
      
@@ -333,7 +335,7 @@ To rebuild just libstdc++, use:
        
      Use the ldd(1) utility to show which library the system
           thinks it will get at runtime.
        
      
-   
    
      
 
 
@@ -360,7 +362,7 @@ To rebuild just libstdc++, use:
       of something else.  The compiler in CVS could inline more than what
       2.95.2 does, and the libstdc++ changes were made with that
       compiler.  One of the libstdc++ maintainers explains this
-here.
+here.
    
      
    
      This has been patched in current CVS sources.
    
      
@@ -379,9 +381,9 @@ To rebuild just libstdc++, use:
 
      
 
      
 Comments and suggestions are welcome, and may be sent to
-Phil Edwards or
+Phil Edwards or
 Gabriel Dos Reis.
-
       $Id: install.html,v 1.3 2000/06/20 23:14:37 bkoz Exp $
+
       $Id: install.html,v 1.4 2000/06/27 15:56:17 pme Exp $
 
      
 
 
diff --git a/libstdc++-v3/docs/mail.html b/libstdc++-v3/docs/mail.html
index 2753484a4c0..2fa2cdda5ba 100644
--- a/libstdc++-v3/docs/mail.html
+++ b/libstdc++-v3/docs/mail.html
@@ -7,13 +7,15 @@
 
 
      There are three main mailing lists for this project:
   
        
-  
      • libstdc++@sourceware.cygnus.com:  the main discussion and
+  
      • libstdc++@sources.redhat.com:  the main discussion and
       development list
-  
      • libstdc++-cvs@sourceware.cygnus.com:  a mailing list of 
+  
      • libstdc++-cvs@sources.redhat.com:  a mailing list of 
       CVS-produced messages (exciting reading!)
-  
      • libstdc++-prs@sourceware.cygnus.com:  a mailing list for problem
+  
      • libstdc++-prs@sources.redhat.com:  a mailing list for problem
       reports and bugs
   
      
+  These used to be @sourceware.cygnus.com but have been renamed;
+  the old names will continue to work for a while.
 
      
 
 
      Use this handy little form to subscribe or unsubscribe from any of
@@ -52,13 +54,13 @@
 
      
 
 
      You can also ftp mbox formatted archives from the 
-   ftp
+   ftp
    archives.
 
      
 
 
      For more info, and features of the mailing list software, please consult
-   the
-   documentation page for sourceware mailing lists.
+   the
+   documentation page for sources.redhat mailing lists.
 
      
 
 
diff --git a/libstdc++-v3/docs/status.html b/libstdc++-v3/docs/status.html
index bb097f8004a..22a52da155b 100644
--- a/libstdc++-v3/docs/status.html
+++ b/libstdc++-v3/docs/status.html
@@ -7,7 +7,9 @@
    gcc 2-95 works well.)  In addition, autoconf
    versions 2.13 and above and automake versions
    1.3b and above are required and essential ingredients for those mucking
-   about in the Makefiles and trying to configure on new targets.
+   about in the Makefiles and trying to configure on new targets.  Other
+   tools and complete installation instructions can be found in
+   the installation page.
 
      
 
 
      New things that work are in the latest
@@ -129,15 +131,12 @@
    AIX. The initial bug report is 
     here 
 
-
      And the
-   response from one of the powerpc port maintainers:
-
-
      
-
+
      And the response from one of the powerpc port maintainers:
+   
      
    I opposed the original solution (involving weak symbols) on ELF, as
    it seemed to be the wrong idea.  I'm not sure what the right fix is,
-   and don't think I have time to work on it right now.
-
      
+   and don't think I have time to work on it right now.
+   
      
 
      
 
 
diff --git a/libstdc++-v3/docs/thanks.html b/libstdc++-v3/docs/thanks.html
index b2750885dad..5699f354140 100644
--- a/libstdc++-v3/docs/thanks.html
+++ b/libstdc++-v3/docs/thanks.html
@@ -12,7 +12,7 @@
    and in many different capacities.  Any omissions -- and there probably
    are many --
    in this list are accidental.  Feel free to contact pme@sourceware.cygnus.com
+   HREF="mailto:pme@sources.redhat.com">pme@sources.redhat.com
    if you have been left out or some of your contributions are not listed.
    Please keep this list in alphabetical order.