procyberian/gcc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: Update sourceware->sources in every HTML file.

Browse source 
2000-07-11  Phil Edwards  <pme@sourceware.cygnus.com>

	* docs:  Update sourceware->sources in every HTML file.  Minor updates.

From-SVN: r34967
This commit is contained in:
Phil Edwards 2000-07-11 21:45:08 +00:00 • committed by Phil Edwards
parent 4003801c76
commit c0ed1dea37
25 changed files with 339 additions and 326 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
libstdc++-v3/ChangeLog
View file

@ -1,3 +1,7 @@
2000-07-11 Phil Edwards <pme@sourceware.cygnus.com>
* docs: Update sourceware->sources in every HTML file. Minor updates.
2000-07-07 Benjamin Kosnik <bkoz@soma.redhat.com>
Clean up configure/build longstanding issues.

2
libstdc++-v3/docs/17_intro/contribute.html
View file

@ -87,7 +87,7 @@ response from the maintainers) it would have all of these pieces:
get the latest version of GNU diff.
<li> 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.
</ul>

10
libstdc++-v3/docs/17_intro/howto.html
View file

@ -2,14 +2,14 @@
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sourceware.cygnus.com (Phil Edwards)">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, gcc, g++, libg++, STL">
<META NAME="DESCRIPTION" CONTENT="HOWTO for libstdc++ chapter 17.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 HOWTO: Chapter 17</TITLE>
<LINK REL="home" HREF="http://sourceware.cygnus.com/libstdc++/docs/18_support/">
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/18_support/">
<LINK REL=StyleSheet HREF="../lib3styles.css">
<!-- $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 $ -->
</HEAD>
<BODY>
@ -145,9 +145,9 @@
<HR>
<P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sourceware.cygnus.com">Phil Edwards</A> or
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>.
<BR> $Id: howto.html,v 1.2 2000/04/25 06:39:48 bkoz Exp $
<BR> $Id: howto.html,v 1.3 2000/05/03 16:11:02 pme Exp $
</EM></P>

10
libstdc++-v3/docs/18_support/howto.html
View file

@ -2,14 +2,14 @@
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sourceware.cygnus.com (Phil Edwards)">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, egcs, g++, libg++, STL">
<META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 18.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 HOWTO: Chapter 18</TITLE>
<LINK REL="home" HREF="http://sourceware.cygnus.com/libstdc++/docs/18_support/">
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/18_support/">
<LINK REL=StyleSheet HREF="../lib3styles.css">
<!-- $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 $ -->
</HEAD>
<BODY>
@ -248,9 +248,9 @@
<HR>
<P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sourceware.cygnus.com">Phil Edwards</A> or
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>.
<BR> $Id: howto.html,v 1.1 2000/04/21 20:33:31 bkoz Exp $
<BR> $Id: howto.html,v 1.2 2000/07/07 21:13:28 pme Exp $
</EM></P>

10
libstdc++-v3/docs/19_diagnostics/howto.html
View file

@ -2,14 +2,14 @@
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sourceware.cygnus.com (Phil Edwards)">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, egcs, g++, libg++, STL">
<META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 19.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 HOWTO: Chapter 19</TITLE>
<LINK REL="home" HREF="http://sourceware.cygnus.com/libstdc++/docs/19_diagnostics/">
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/19_diagnostics/">
<LINK REL=StyleSheet HREF="../lib3styles.css">
<!-- $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 $ -->
</HEAD>
<BODY>
@ -98,9 +98,9 @@
<HR>
<P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sourceware.cygnus.com">Phil Edwards</A> or
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>.
<BR> $Id: howto.html,v 1.1 2000/04/21 20:33:31 bkoz Exp $
<BR> $Id: howto.html,v 1.2 2000/07/07 21:13:28 pme Exp $
</EM></P>

10
libstdc++-v3/docs/20_util/howto.html
View file

@ -2,14 +2,14 @@
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sourceware.cygnus.com (Phil Edwards)">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, egcs, g++, libg++, STL">
<META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 20.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 HOWTO: Chapter 20</TITLE>
<LINK REL="home" HREF="http://sourceware.cygnus.com/libstdc++/docs/20_util/">
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/20_util/">
<LINK REL=StyleSheet HREF="../lib3styles.css">
<!-- $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 $ -->
</HEAD>
<BODY>
@ -184,9 +184,9 @@
<HR>
<P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sourceware.cygnus.com">Phil Edwards</A> or
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>.
<BR> $Id: howto.html,v 1.5 2000/03/20 22:16:21 pme Exp $
<BR> $Id: howto.html,v 1.1 2000/04/21 20:33:31 bkoz Exp $
</EM></P>

10
libstdc++-v3/docs/21_strings/howto.html
View file

@ -2,14 +2,14 @@
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sourceware.cygnus.com (Phil Edwards)">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, egcs, g++, libg++, STL">
<META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 21.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 HOWTO: Chapter 21</TITLE>
<LINK REL="home" HREF="http://sourceware.cygnus.com/libstdc++/docs/21_strings/">
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/21_strings/">
<LINK REL=StyleSheet HREF="../lib3styles.css">
<!-- $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 $ -->
</HEAD>
<BODY>
@ -295,9 +295,9 @@
<HR>
<P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sourceware.cygnus.com">Phil Edwards</A> or
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>.
<BR> $Id: howto.html,v 1.1 2000/04/21 20:33:31 bkoz Exp $
<BR> $Id: howto.html,v 1.2 2000/07/07 21:13:28 pme Exp $
</EM></P>

10
libstdc++-v3/docs/22_locale/howto.html
View file

@ -2,14 +2,14 @@
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sourceware.cygnus.com (Phil Edwards)">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, egcs, g++, libg++, STL">
<META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 22.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 HOWTO: Chapter 22</TITLE>
<LINK REL="home" HREF="http://sourceware.cygnus.com/libstdc++/docs/22_locale/">
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/22_locale/">
<LINK REL=StyleSheet HREF="../lib3styles.css">
<!-- $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 $ -->
</HEAD>
<BODY>
@ -61,9 +61,9 @@
<HR>
<P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sourceware.cygnus.com">Phil Edwards</A> or
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>.
<BR> $Id: howto.html,v 1.5 2000/03/20 22:16:21 pme Exp $
<BR> $Id: howto.html,v 1.1 2000/04/21 20:33:31 bkoz Exp $
</EM></P>

10
libstdc++-v3/docs/23_containers/howto.html
View file

@ -2,14 +2,14 @@
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sourceware.cygnus.com (Phil Edwards)">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, egcs, g++, libg++, STL">
<META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 23.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 HOWTO: Chapter 23</TITLE>
<LINK REL="home" HREF="http://sourceware.cygnus.com/libstdc++/docs/23_containers/">
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/23_containers/">
<LINK REL=StyleSheet HREF="../lib3styles.css">
<!-- $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 $ -->
</HEAD>
<BODY>
@ -236,9 +236,9 @@
<HR>
<P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sourceware.cygnus.com">Phil Edwards</A> or
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>.
<BR> $Id: howto.html,v 1.8 2000/03/23 20:58:38 pme Exp $
<BR> $Id: howto.html,v 1.1 2000/04/21 20:33:31 bkoz Exp $
</EM></P>

10
libstdc++-v3/docs/24_iterators/howto.html
View file

@ -2,14 +2,14 @@
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sourceware.cygnus.com (Phil Edwards)">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, egcs, g++, libg++, STL">
<META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 24.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 HOWTO: Chapter 24</TITLE>
<LINK REL="home" HREF="http://sourceware.cygnus.com/libstdc++/docs/24_iterators/">
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/24_iterators/">
<LINK REL=StyleSheet HREF="../lib3styles.css">
<!-- $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 $ -->
</HEAD>
<BODY>
@ -85,9 +85,9 @@
<HR>
<P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sourceware.cygnus.com">Phil Edwards</A> or
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>.
<BR> $Id: howto.html,v 1.1 2000/04/21 20:33:31 bkoz Exp $
<BR> $Id: howto.html,v 1.2 2000/07/07 21:13:28 pme Exp $
</EM></P>

10
libstdc++-v3/docs/25_algorithms/howto.html
View file

@ -2,14 +2,14 @@
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sourceware.cygnus.com (Phil Edwards)">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, egcs, g++, libg++, STL">
<META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 25.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 HOWTO: Chapter 25</TITLE>
<LINK REL="home" HREF="http://sourceware.cygnus.com/libstdc++/docs/25_algorithms/">
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/25_algorithms/">
<LINK REL=StyleSheet HREF="../lib3styles.css">
<!-- $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 $ -->
</HEAD>
<BODY>
@ -87,9 +87,9 @@
<HR>
<P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sourceware.cygnus.com">Phil Edwards</A> or
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>.
<BR> $Id: howto.html,v 1.1 2000/04/21 20:33:31 bkoz Exp $
<BR> $Id: howto.html,v 1.2 2000/07/07 21:13:28 pme Exp $
</EM></P>

10
libstdc++-v3/docs/26_numerics/howto.html
View file

@ -2,14 +2,14 @@
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sourceware.cygnus.com (Phil Edwards)">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, egcs, g++, libg++, STL">
<META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 26.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 HOWTO: Chapter 26</TITLE>
<LINK REL="home" HREF="http://sourceware.cygnus.com/libstdc++/docs/26_numerics/">
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/26_numerics/">
<LINK REL=StyleSheet HREF="../lib3styles.css">
<!-- $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 $ -->
</HEAD>
<BODY>
@ -133,9 +133,9 @@
<HR>
<P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sourceware.cygnus.com">Phil Edwards</A> or
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>.
<BR> $Id: howto.html,v 1.2 2000/06/28 15:14:39 gdr Exp $
<BR> $Id: howto.html,v 1.3 2000/07/07 21:13:28 pme Exp $
</EM></P>

10
libstdc++-v3/docs/27_io/howto.html
View file

@ -2,14 +2,14 @@
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sourceware.cygnus.com (Phil Edwards)">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, egcs, g++, libg++, STL">
<META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 27.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 HOWTO: Chapter 27</TITLE>
<LINK REL="home" HREF="http://sourceware.cygnus.com/libstdc++/docs/27_io/">
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/27_io/">
<LINK REL=StyleSheet HREF="../lib3styles.css">
<!-- $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 $ -->
</HEAD>
<BODY>
@ -334,9 +334,9 @@
<HR>
<P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sourceware.cygnus.com">Phil Edwards</A> or
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>.
<BR> $Id: howto.html,v 1.7 1999/12/15 16:57:06 pme Exp $
<BR> $Id: howto.html,v 1.1 2000/04/21 20:33:32 bkoz Exp $
</EM></P>

36
libstdc++-v3/docs/configopts.html
View file

@ -2,14 +2,14 @@
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sourceware.cygnus.com (Phil Edwards)">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="libstdc++, libstdc++-v3, egcs, g++">
<META NAME="DESCRIPTION" CONTENT="Configuration options for libstdc++-v3.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 configure options</TITLE>
<LINK REL="home" HREF="http://sourceware.cygnus.com/libstdc++/">
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/">
<LINK REL=StyleSheet HREF="lib3styles.css">
<!-- $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 $ -->
</HEAD>
<BODY>
@ -17,8 +17,8 @@
options</A></H1>
<P>The latest version of this document is always available at
<A HREF="http://sourceware.cygnus.com/libstdc++/configopts.html">
http://sourceware.cygnus.com/libstdc++/configopts.html</A>.
<A HREF="http://sources.redhat.com/libstdc++/configopts.html">
http://sources.redhat.com/libstdc++/configopts.html</A>.
</P>
<P>To the <A HREF="index.html">libstdc++-v3 homepage</A>.
@ -29,17 +29,17 @@ options</A></H1>
<P>Here are some of the non-obvious options to libstdc++'s configure.
Keep in mind that
<!-- This SECnn should be the "Choosing Package Options" section. -->
<A HREF="http://sourceware.cygnus.com/autoconf/autoconf.html#SEC74">they
<A HREF="http://sources.redhat.com/autoconf/autoconf.html#SEC74">they
all have opposite forms as well</A>
(enable/disable and with/without). The defaults are for the latest
snapshot, 2.90.8.
<DL>
<DT><TT>--enable-multilib </TT>[default]
<DD><P>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.
</P>
<DT><TT>--enable-debug </TT>
@ -61,7 +61,7 @@ options</A></H1>
<DD><P>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
<A HREF="http://sourceware.cygnus.com/glibc/">glibc</A>, the
<A HREF="http://sources.redhat.com/glibc/">glibc</A>, 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</A></H1>
at it. It's described in <A HREF="gccrebuild.html">its own
little page</A>. 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 <TT> '../..' </TT>, 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
<TT> '../..' </TT>, 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.
</P>
<DT><TT>--enable-cxx-flags=FLAGS</TT>
@ -149,7 +149,7 @@ options</A></H1>
</P>
</DL>
</P>
<P>Return <A HREF="#top">to the top of the README</A> or
<P>Return <A HREF="#top">to the top of the page</A> or
<A HREF="index.html">to the homepage</A>.
</P>
@ -158,7 +158,7 @@ options</A></H1>
<HR>
<P CLASS="fineprint"><EM>
$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 $
</EM></P>

11
libstdc++-v3/docs/documentation.html
View file

@ -1,7 +1,9 @@
<!--#include virtual="/libstdc++/header.html"-->
<P><B>All of these documents</B> (in fact, this entire homepage set) are
bundled with the library source, under the <TT>docs</TT> subdirectory.
</P>
<H2><A NAME="1">Introductory notes for libstdc++</A></H2>
<P>This is a short list of text files pertaining to this
@ -22,8 +24,9 @@
<LI><A HREF="17_intro/HEADER_POLICY">HEADER_POLICY</A>
- header naming and sub-include structure
<LI><A HREF="17_intro/PROBLEMS">PROBLEMS</A>
<LI> <A HREF="../README">README</a>
- directory structure
<!-- Linking to "../README" doesn't work; we are at the top level
of the web pages. Punt. -->
<LI>README - directory structure
<LI><A HREF="17_intro/RELEASE-NOTES">RELEASE-NOTES</A>
- instructions for building, using
<LI><A HREF="17_intro/TODO">TODO</A>
@ -43,7 +46,7 @@
</UL>
<HR>
<H2><A NAME="3">Chapter-Specific Information and Advice</A></H2>
<H2><A NAME="3">Chapter-Specific Information, Extensions, and Advice</A></H2>
<OL>
<LI><A HREF="17_intro/howto.html">Chapter 17 (Intro)</A>
<LI><A HREF="18_support/howto.html">Chapter 18 (Library Support)</A>

6
libstdc++-v3/docs/download.html
View file

@ -8,9 +8,9 @@
link to the FTP site is given directly, encouraging mirror usage.
-->
<P>Get the snapshot archive via FTP from
<TT>&lt;URL:ftp://sourceware.cygnus.com/pub/libstdc++/&gt;</TT>.
<TT>&lt;URL:ftp://sources.redhat.com/pub/libstdc++/&gt;</TT>.
You will almost certainly need to use one of the
<A HREF="http://sourceware.cygnus.com/mirrors.html">mirror sites</A>
<A HREF="http://sources.redhat.com/mirrors.html">mirror sites</A>
due to the extremely heavy load on the main server.
</P>
@ -27,7 +27,7 @@
Directions are <A HREF="http://gcc.gnu.org/cvswrite.html">here</A>.
</UL>
</P>
<P>One you have the GCC sources checked out over CVS, you can use the
<P>Once you have the GCC sources checked out over CVS, you can use the
<TT>contrib/gcc_update</TT> 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

58
libstdc++-v3/docs/faq/index.html
View file

@ -2,26 +2,26 @@
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sourceware.cygnus.com (Phil Edwards)">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="libstdc++, libstdc++-v3, egcs, g++, libg++, STL">
<META NAME="DESCRIPTION" CONTENT="FAQ for the GNU libstdc++ effort.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 FAQ</TITLE>
<LINK REL="home" HREF="http://sourceware.cygnus.com/libstdc++/">
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/">
<LINK REL=StyleSheet HREF="../lib3styles.css">
<!--
** Locations of "the most recent snapshot is the Nth" text are
** answers 1_1, 1_4, 4_1, 5_6.
-->
<!-- $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 $ -->
</HEAD>
<BODY>
<H1 CLASS="centered">libstdc++ Frequently Asked Questions</H1>
<P>The latest version of this document is always available at
<A HREF="http://sourceware.cygnus.com/libstdc++/faq/index.html">
http://sourceware.cygnus.com/libstdc++/faq/</A>.</P>
<A HREF="http://sources.redhat.com/libstdc++/faq/index.html">
http://sources.redhat.com/libstdc++/faq/</A>.</P>
<P>To the <A HREF="../index.html">libstdc++-v3 homepage</A>.
@ -94,7 +94,7 @@ http://sourceware.cygnus.com/libstdc++/faq/</A>.</P>
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 <A
HREF="ftp://sourceware.cygnus.com/pub/libstdc++/libstdc++-2.90.8.tar.gz">the
HREF="ftp://sources.redhat.com/pub/libstdc++/libstdc++-2.90.8.tar.gz">the
ninth snapshot</A>. 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</A>
<HR>
<H2><A NAME="1_4">1.4 How do I get libstdc++?</A></H2>
<P>The ninth (and latest) snapshot of libstdc++-v3 is <A
HREF="ftp://sourceware.cygnus.com/pub/libstdc++/libstdc++-2.90.8.tar.gz">
HREF="ftp://sources.redhat.com/pub/libstdc++/libstdc++-2.90.8.tar.gz">
available via ftp</A>.
</P>
<P>The <A HREF="../index.html">homepage</A>
@ -165,7 +165,7 @@ HREF="ftp://sourceware.cygnus.com/pub/libstdc++/libstdc++-2.90.8.tar.gz">
<H2><A NAME="1_5">1.5 When is libstdc++ going to be finished?</A></H2>
<P>Nathan Myers gave the best of all possible answers in <A
HREF="http://www.deja.com/getdoc.xp?AN=469581698&fmt=text">a
recent Usenet article</A>.</P>
Usenet article</A>.</P>
<HR>
<H2><A NAME="1_6">1.6 How do I contribute to the effort?</A></H2>
@ -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 <A HREF="mailto:libstdc++@sourceware.cygnus.com">
<TT>libstdc++@sourceware.cygnus.com</TT></A>.
to the list, use <A HREF="mailto:libstdc++@sources.redhat.com">
<TT>libstdc++@sources.redhat.com</TT></A>.
</P>
<P>If you have a question that you think should be included here,
or if you have a question <EM>about</EM> a question/answer here,
contact <A HREF="mailto:pme@sourceware.cygnus.com">Phil Edwards</A>
contact <A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A>
or <A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>.
</P>
@ -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.
<LI> If you plan on hacking around with the makefiles, you
will need the tools <A
HREF="http://sourceware.cygnus.com/autoconf/">autoconf</A>and <A
HREF="http://sourceware.cygnus.com/automake/">automake</A>.
HREF="http://sources.redhat.com/autoconf/">autoconf</A>and <A
HREF="http://sources.redhat.com/automake/">automake</A>.
<LI> GNU Make is the only make that supports these makefiles.
</UL>
</P>
@ -283,13 +283,13 @@ HREF="http://sourceware.cygnus.com/automake/">automake</A>.
<HR>
<H2><A NAME="2_3">2.3 What is this CVS thing that you
keep mentioning?</A></H2>
<P>The <EM>Concurrent Versions System</EM> is one of several
revision control packages. It was selected for GNU projects
because it's free and very high quality. The <A
<P>The <EM>Concurrent Versions System</EM> 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 <A
HREF="http://www.gnu.org/software/cvs/cvs.html">CVS entry in
the GNU software catalogue</A> has a better description as
well as a <A HREF="http://www.cyclic.com/">link to the makers
of CVS</A>.
well as a
<A HREF="http://www.cyclic.com/">link to the makers of CVS</A>.
</P>
<P>The &quot;anonymous client checkout&quot; 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</A>.
occasions when the test does not hang, the zero-division is
in fact trapped. That doesn't prevent hanging elsewhere.
</P>
<P>You have two options.
You can wait until the signal-handling in Cygwin is reworked
and released; this is planned to take &quot;a few weeks&quot;
and will result in a fix sometime in late December or early January.
<P>You have two options. You can get a newer cygwin1.dll (see the
Cygwin paragraph in the
<A HREF="../install.html">installation instructions</A>).
Or you can get a prebuilt set of bits/std_limits.h and
src/limitsMEMBERS.cc files from Mumit Khan's
<A HREF="http://www.xraylith.wisc.edu/~khan/software/gnu-win32/libstdc++-v3.html">Cygwin-related
website</A>.
<A HREF="http://www.xraylith.wisc.edu/~khan/software/gnu-win32/libstdc++-v3.html">Cygwin-related website</A>.
</P>
<HR>
@ -543,10 +541,10 @@ to the list</A>, Nathan Myers announced that he has started a list of
instance) will of course be a continuing task.
</P>
<P><A
HREF="http://sourceware.cygnus.com/ml/libstdc++/1999/msg00080.html">This
HREF="http://sources.redhat.com/ml/libstdc++/1999/msg00080.html">This
question</A> about the next libstdc++ prompted some brief but
interesting <A
HREF="http://sourceware.cygnus.com/ml/libstdc++/1999/msg00084.html">speculation</A>.
HREF="http://sources.redhat.com/ml/libstdc++/1999/msg00084.html">speculation</A>.
</P>
<HR>
@ -610,10 +608,10 @@ HREF="http://sourceware.cygnus.com/ml/libstdc++/1999/msg00084.html">speculation<
<P>This is assuming that your idea of &quot;multithreaded&quot;
is the same as ours... The general question of multithreading
and libstdc++-v3 is addressed in the chapter-specific advice for
<A HREF="http://sourceware.cygnus.com/libstdc++/17_intro/howto.html#3">Library
<A HREF="http://sources.redhat.com/libstdc++/17_intro/howto.html#3">Library
Introduction</A>. Threadsafe containers are covered in
more detail in
<A HREF="http://sourceware.cygnus.com/libstdc++/23_containers/howto.html">the
<A HREF="http://sources.redhat.com/libstdc++/23_containers/howto.html">the
Received Wisdom section on containers</A>.
<!-- I have successfully evaded the topic; my work here is
done- no, wait, I have to write those other sections... -->
@ -643,9 +641,9 @@ HREF="http://sourceware.cygnus.com/ml/libstdc++/1999/msg00084.html">speculation<
<HR>
<P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sourceware.cygnus.com">Phil Edwards</A> or
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>.
<BR> $Id: index.html,v 1.3 2000/05/24 18:35:37 pme Exp $
<BR> $Id: index.html,v 1.4 2000/06/28 18:57:27 pme Exp $
</EM></P>

114
libstdc++-v3/docs/faq/index.txt
View file

@ -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

21
libstdc++-v3/docs/gccrebuild.html
View file

@ -2,25 +2,27 @@
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sourceware.cygnus.com (Phil Edwards)">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="libgcc.a, rebuild">
<META NAME="DESCRIPTION" CONTENT="How to automatically rebuild libgcc.a.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>How to automatically rebuild libgcc.a.</TITLE>
<LINK REL="home" HREF="http://sourceware.cygnus.com/libstdc++/">
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/">
<LINK REL=StyleSheet HREF="lib3styles.css">
<!-- $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 $ -->
</HEAD>
<BODY>
<H2 CLASS="centered"><TT>--enable-libgcc-rebuild</TT></H2>
<P> NOTE: If using the <TT> --enable-libstdcxx-v3</TT> 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.
<P><B>NOTA BENE</B>: If using the <TT>--enable-libstdcxx-v3</TT> 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.
</P>
<HR>
<P>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 <EM>objdir</EM>; here it will be called <EM>GCCobjdir</EM>.
</P>
<P>This was a kludge, and after the library sources were merged into
<P>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 @@
<HR>
<P CLASS="fineprint"><EM>
$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 $
</EM></P>

8
libstdc++-v3/docs/header.html
View file

@ -2,14 +2,14 @@
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sourceware.cygnus.com (Phil Edwards)">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="libstdc++, homepage, home, g++, libg++, STL">
<META NAME="DESCRIPTION" CONTENT="GNU libstdc++-v3 homepage.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>Standard C++ Library v3</TITLE>
<LINK REL="home" HREF="http://sourceware.cygnus.com/libstdc++/">
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/">
<LINK REL=StyleSheet HREF="lib3styles.css">
<!-- $Id: header.html,v 1.1 2000/03/09 22:19:39 pme Exp $ -->
<!-- $Id: header.html,v 1.1 2000/04/21 20:33:30 bkoz Exp $ -->
</HEAD>
<!-- This does the BODY tag and that funky imagemap. -->
@ -60,7 +60,7 @@
</TABLE></TD><TD></TD><TD>
<!-- Why another table for the actual stuff? See JSM's insightful
comments in the source of sourceware.cygnus.com.
comments in the source of sources.redhat.com.
-->
<TABLE><TR><TD>

10
libstdc++-v3/docs/index.html
View file

@ -10,9 +10,9 @@
<H2>What... is your quest?</H2>
<P>This is an ongoing project
to implement the ISO 14882 Standard C++ Library as described in chapters
17 through 27 and Annex D. <B>Participation is welcome!</B>
<P>This is an ongoing project to implement the ISO 14882 Standard
C++ Library as described in chapters 17 through 27 and Annex D.
<B>Participation is welcome!</B>
</P>
<H2>What... is the airspeed velocity of an unladen swallow?</H2>
@ -28,9 +28,11 @@
<H3>News</H3>
<P>
<DL>
<DT>2000-04-21
<DD> Officially merged library sources into GCC.
<DT>2000-03-24
<DD> Ninth snapshot release,
<A HREF="ftp://sourceware.cygnus.com/pub/libstdc++/libstdc++-2.90.8.tar.gz">
<A HREF="ftp://sources.redhat.com/pub/libstdc++/libstdc++-2.90.8.tar.gz">
libstdc++-2.90.8.tar.gz</A>.
<DT>1999-12-21
<DD> Eighth snapshot release, libstdc++-2.90.7.tar.gz.

254
libstdc++-v3/docs/install.html
View file

@ -2,22 +2,22 @@
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sourceware.cygnus.com (Phil Edwards)">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="libstdc++, libstdc++-v3, egcs, g++">
<META NAME="DESCRIPTION" CONTENT="README for the GNU libstdc++ effort.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 Installation Instructions</TITLE>
<LINK REL="home" HREF="http://sourceware.cygnus.com/libstdc++/">
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/">
<LINK REL=StyleSheet HREF="lib3styles.css">
<!-- $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 $ -->
</HEAD>
<BODY>
<H1 CLASS="centered"><A NAME="top">libstdc++-v3 INSTALL</A></H1>
<P>The latest version of this document is always available at
<A HREF="http://sourceware.cygnus.com/libstdc++/install.html">
http://sourceware.cygnus.com/libstdc++/install.html</A>.
<A HREF="http://sources.redhat.com/libstdc++/install.html">
http://sources.redhat.com/libstdc++/install.html</A>.
</P>
<P>To the <A HREF="index.html">libstdc++-v3 homepage</A>.
@ -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
<A HREF="ftp://sourceware.cygnus.com/pub/libstdc++/20000619-maintainer-tools.tar.gz"> here</A>.
<A HREF="ftp://sources.redhat.com/pub/libstdc++/20000619-maintainer-tools.tar.gz">here</A>.
</P>
<P>If you don't have bash, and want to run <TT>'make check'</TT> to
test your build, you'll need to get bash 2.x. Also recommended
@ -63,21 +63,22 @@
</P>
<P>As of June 19, 2000, libstdc++ attempts to use tricky and
space-saving features of the GNU toolchain, enabled with
<TT>-ffunction-sections -fdata-sections -Wl,--gc-sections</TT>. 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: <TT>2.10.90</TT>, and you can get snapshots (as well as releases) of binutils
<A HREF="ftp://sourceware.cygnus.com/pub/binutils"> here</A>.
space-saving features of the GNU toolchain, enabled with
<TT>-ffunction-sections -fdata-sections -Wl,--gc-sections</TT>.
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 <TT>2.10.90</TT>, and you can get snapshots (as
well as releases) of binutils
<A HREF="ftp://sources.redhat.com/pub/binutils">here</A>.
</P>
<P>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
<P>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 @@
<HR>
<H2><A NAME="srcsetup">Setting up the source directories</A></H2>
<P><EM>As the libstdc++-v3 sources and the core GCC sources move
towards convergence, more and more effort goes to building the
<P><EM>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 @@
</OL>
</P>
<p>
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.
<P>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.
</P>
<P>
<B>...with gcc-2.95.2</B>
<P>Unpack the <EM>gccsrcdir</EM> and go into that directory. For
instance, <TT>gcc-2.95.2</TT> is a valid <EM>gccsrcdir</EM>.
Once in <EM>gccsrcdir</EM>, you'll need to rename the directories
called <TT> libstdc++ </TT> and <TT> libio </TT> like so:
<PRE>
mv libstdc++ libstdc++-v2
mv libio libio-v2</PRE>
</P>
<P>Next, unpack the libstdc++-v3 library tarball into the
<EM>gccsrcdir</EM> directory; it will create a
<EM>libsrcdir</EM> called <TT>libstdc++-<EM>version</EM></TT>:
<PRE>
<P><B>...with gcc-2.95.2</B>
<P>Unpack the <EM>gccsrcdir</EM> and go into that directory. For
instance, <TT>gcc-2.95.2</TT> is a valid <EM>gccsrcdir</EM>.
Once in <EM>gccsrcdir</EM>, you'll need to rename the directories
called <TT> libstdc++ </TT> and <TT> libio </TT> like so:
<PRE>
mv libstdc++ libstdc++-v2
mv libio libio-v2</PRE>
</P>
<P>Next, unpack the libstdc++-v3 library tarball into the
<EM>gccsrcdir</EM> directory; it will create a
<EM>libsrcdir</EM> called <TT>libstdc++-<EM>version</EM></TT>:
<PRE>
gzip -dc libstdc++-version.tar.gz | tar xf -</PRE>
</P>
<P>Finally, make a soft link between <EM>libsrcdir</EM> and
<TT>libstdc++</TT> so that libstdc++-v3 will be the default C++
library used.
<PRE>
</P>
<P>Finally, make a soft link between <EM>libsrcdir</EM> and
<TT>libstdc++</TT> so that libstdc++-v3 will be the default C++
library used.
<PRE>
ln -s <EM>libsrcdir</EM> libstdc++</PRE>
This complexity of having two completely separate libstdc++
libraries is necessary so that you can unlink <EM>libsrcdir</EM>
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 <EM>libsrcdir</EM>
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.
</P>
</P>
<P>
<B>...with CVS gcc</B>
<P> Check out or download the gcc sources: the
resulting source director is <EM>gccsrcdir</EM>.
</P>
<P>Next, unpack the libstdc++-v3 library tarball into this
<EM>gccsrcdir</EM> directory; it will create a
<EM>libsrcdir</EM> called <TT>libstdc++-<EM>version</EM></TT>:
<PRE>
<P><B>...with CVS gcc</B>
<P>Check out or download the gcc sources: the resulting source
directory is <EM>gccsrcdir</EM>.
</P>
<P>Next, unpack the libstdc++-v3 library tarball into this
<EM>gccsrcdir</EM> directory; it will create a
<EM>libsrcdir</EM> called <TT>libstdc++-<EM>version</EM></TT>:
<PRE>
gzip -dc libstdc++-version.tar.gz | tar xf -</PRE>
</P>
<P> If CVS libstdc++-v3 is being used instead of a snapshot's
tarball, then move the source directory from the cvs checkout into
the <EM>gccsrcdir</EM> directory.
<P>Finally, rename <EM>libsrcdir</EM> to
<TT>libstdc++-v3</TT> so that gcc's configure flags will be able
to deal with the new library.
<PRE>
</P>
<P>If CVS libstdc++-v3 is being used instead of a snapshot's tarball,
then move the source directory from the CVS checkout into the
<EM>gccsrcdir</EM> directory.
<P>Finally, rename <EM>libsrcdir</EM> to <TT>libstdc++-v3</TT> so that
gcc's configure flags will be able to deal with the new library.
<PRE>
mv <EM>libsrcdir</EM> libstdc++-v3</PRE>
</P>
</P>
<HR>
<H2><A NAME="config">Configuring</A></H2>
<P>Due to namespaces, when building libstdc++-v3 you'll have to configure
the entire <EM>gccsrcdir</EM> directory. The full list of libstdc++-v3
specific configuration options, not dependent on the specific compiler
release being used, can be found <A HREF="configopts.html">here</A>.
</P>
<P>Consider possibly using --enable-languages=c++ to save time by only
building the C++ language parts.
</P>
Due to namespaces, when building libstdc++-v3 you'll have to configure
the entire <EM>gccsrcdir</EM> directory. The full list of
libstdc++-v3 specific configuration options, not dependent on the
specific compiler release being used, can be found <A
HREF="configopts.html"> here </A>
<P>
[Consider possibly using
--enable-languages=c++ to save time by only building the C++ language
parts]
<P><B>...with gcc-2.95.2</B>
<PRE>
<EM>gccsrcdir</EM>/configure --prefix=<EM>destdir</EM></PRE>
</P>
<P><B>...with CVS gcc</B>
<PRE>
<EM>gccsrcdir</EM>/configure --prefix=<EM>destdir</EM> --enable-libstdcxx-v3</PRE>
</P>
<P>Adding <TT>--enable-libstdcxx-v3</TT> 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.
</P>
<P>
<B>...with gcc-2.95.2</B>
<P>
<EM>gccsrcdir</EM>/configure --prefix=<EM>destdir</EM>
</PRE>
<P>
<P>
<B>...with CVS gcc</B>
<P>
<EM>gccsrcdir</EM>/configure --prefix=<EM>destdir</EM> --enable-libstdcxx-v3
<P>
[Adding <TT> --enable-libstdcxx-v3</TT> 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] </P>
<HR>
<H2><A NAME="install">Building and installing the library</A></H2>
@ -240,28 +238,31 @@ being built, and also enables -fhonor-std by default. This option is not availab
</P>
<H3>[re]building only libstdc++</H3>
Due to differences in the configure process, the resulting Makefiles
in the<EM>gccbuilddir</EM> will have different rules depending on
the source base being used.
<P>
<B>...with gcc-2.95.2</B>
<P>
<EM>libstdc++-rule</EM> is <TT>libstdc++</TT>
<P>Due to differences in the configure process, the resulting Makefiles
in the<EM>gccbuilddir</EM> will have different rules depending on
the source base being used.
</P>
<P>
<P>
<B>...with CVS gcc</B>
<P>
<EM>libstdc++-rule</EM> is <TT>libstdc++-v3</TT>
<P>
To rebuild just libstdc++, use:
<P>
<PRE>make all-target-<EM>libstdc++-rule</EM></PRE>
<P><B>...with gcc-2.95.2</B>
<BLOCKQUOTE>
<EM>libstdc++-rule</EM> is <TT>libstdc++</TT>
</BLOCKQUOTE>
</P>
<P><B>...with CVS gcc</B>
<BLOCKQUOTE>
<EM>libstdc++-rule</EM> is <TT>libstdc++-v3</TT>
</BLOCKQUOTE>
</P>
<P>To rebuild just libstdc++, use:
<PRE>
make all-target-<EM>libstdc++-rule</EM></PRE>
This will configure and build the C++ library in the
<EM>gccbuilddir/cpu-vendor-OS/</EM>libstdc++ directory.
As en example, for CVS gcc this would be <TT>make all-target-libstdc++-v3</TT>, and for gcc-2.95.2 it would be <TT>make all-target-libstdc++</TT>
As en example, for CVS gcc this would be
<TT>make all-target-libstdc++-v3</TT>, and for gcc-2.95.2 it would be
<TT>make all-target-libstdc++</TT>
</P>
<P>If the build fails with a &quot;warning: can't inline call&quot;
message when compiling stringMAIN.cc, see <A HREF="#Werror">the
@ -269,12 +270,13 @@ To rebuild just libstdc++, use:
</P>
<P>You're done. Now install the rebuilt pieces with
<PRE>
make install
or
make install</PRE>
or
<PRE>
make install-gcc
make install-target-<EM>libstdc++-rule</EM></PRE>
</P>
<HR>
<H2><A NAME="postinstall">Post-installation</A></H2>
@ -333,7 +335,7 @@ To rebuild just libstdc++, use:
<P>Use the <TT>ldd(1)</TT> utility to show which library the system
thinks it will get at runtime.
</P>
</OL
</OL>
</P>
@ -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
<A HREF="http://sourceware.cygnus.com/ml/libstdc++/2000-q1/msg00420.html">here</A>.
<A HREF="http://sources.redhat.com/ml/libstdc++/2000-q1/msg00420.html">here</A>.
</P>
<P>This has been patched in current CVS sources.
</P>
@ -379,9 +381,9 @@ To rebuild just libstdc++, use:
<HR>
<P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sourceware.cygnus.com">Phil Edwards</A> or
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>.
<BR> $Id: install.html,v 1.3 2000/06/20 23:14:37 bkoz Exp $
<BR> $Id: install.html,v 1.4 2000/06/27 15:56:17 pme Exp $
</EM></P>

14
libstdc++-v3/docs/mail.html
View file

@ -7,13 +7,15 @@
<P>There are three main mailing lists for this project:
<UL>
<LI>libstdc++@sourceware.cygnus.com: the main discussion and
<LI>libstdc++@sources.redhat.com: the main discussion and
development list
<LI>libstdc++-cvs@sourceware.cygnus.com: a mailing list of
<LI>libstdc++-cvs@sources.redhat.com: a mailing list of
CVS-produced messages (exciting reading!)
<LI>libstdc++-prs@sourceware.cygnus.com: a mailing list for problem
<LI>libstdc++-prs@sources.redhat.com: a mailing list for problem
reports and bugs
</UL>
These used to be <EM>@sourceware.cygnus.com</EM> but have been renamed;
the old names will continue to work for a while.
</P>
<P>Use this handy little form to subscribe or unsubscribe from any of
@ -52,13 +54,13 @@
</P>
<P>You can also ftp mbox formatted archives from the
<A HREF="ftp://sourceware.cygnus.com/pub/libstdc++/mail-archives/">ftp
<A HREF="ftp://sources.redhat.com/pub/libstdc++/mail-archives/">ftp
archives</A>.
</P>
<P>For more info, and features of the mailing list software, please consult
<A HREF="http://sourceware.cygnus.com/ml/index.html#faqs">the
documentation page for sourceware mailing lists</A>.
<A HREF="http://sources.redhat.com/ml/index.html#faqs">the
documentation page for sources.redhat mailing lists</A>.
</P>

15
libstdc++-v3/docs/status.html
View file

@ -7,7 +7,9 @@
gcc 2-95 works well.) In addition, <A HREF="/autoconf/">autoconf</A>
versions 2.13 and above and <A HREF="/automake/">automake</A> 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
<A HREF="install.html">the installation page</A>.
</P>
<P>New things that work are in the latest
@ -129,15 +131,12 @@
AIX. The initial bug report is
<a href="http://gcc.gnu.org/ml/gcc-bugs/2000-03/msg00574.html"> here </a>
<p>And the
response from one of the powerpc port maintainers:
<p>
<i>
<P>And the response from one of the powerpc port maintainers:
<BLOCKQUOTE><EM>
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.</i>
</p>
and don't think I have time to work on it right now.
</EM></BLOCKQUOTE>
</P>

2
libstdc++-v3/docs/thanks.html
View file

@ -12,7 +12,7 @@
and in many different capacities. Any omissions -- and there probably
are many --
in this list are accidental. <B>Feel free</B> to contact <A
HREF="mailto:pme@sourceware.cygnus.com">pme@sourceware.cygnus.com</A>
HREF="mailto:pme@sources.redhat.com">pme@sources.redhat.com</A>
if you have been left out or some of your contributions are not listed.
Please keep this list in alphabetical order.