Skip to content

R
riscv-gcc-1
Commit 1860e6ab by Jonathan Wakely Committed by Phil Edwards
Options

configopts.html, [...]: Conform to HTML 4.01 standard. 

2002-08-19  Jonathan Wakely  <jw@kayari.org>

	* docs/html/configopts.html, docs/html/documentation.html,
	docs/html/install.html, docs/html/22_locale/codecvt.html,
	docs/html/22_locale/ctype.html, docs/html/22_locale/howto.html,
	docs/html/22_locale/locale.html,
	docs/html/22_locale/messages.html: Conform to HTML 4.01 standard.

From-SVN: r56449
parent 3fcd079e
Showing with 112 additions and 85 deletions
libstdc++-v3/ChangeLog
2002-08-19 Jonathan Wakely <jw@kayari.org>
* docs/html/configopts.html, docs/html/documentation.html,
docs/html/install.html, docs/html/22_locale/codecvt.html,
docs/html/22_locale/ctype.html, docs/html/22_locale/howto.html,
docs/html/22_locale/locale.html,
docs/html/22_locale/messages.html: Conform to HTML 4.01 standard.
2002-08-15 Benjamin Kosnik <bkoz@redhat.com> 2002-08-15 Benjamin Kosnik <bkoz@redhat.com>
* include/ext/stdio_filebuf.h (stdio_filebuf): Explicitly set * include/ext/stdio_filebuf.h (stdio_filebuf): Explicitly set
......
libstdc++-v3/docs/html/22_locale/codecvt.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html> <html>
<head> <head>
<title>
Notes on the codecvt implementation.
</title>
</head>
<body>
<h1> <h1>
Notes on the codecvt implementation. Notes on the codecvt implementation.
</h1> </h1>
</head> <p>
<I> <I>
prepared by Benjamin Kosnik (bkoz@redhat.com) on August 28, 2000 prepared by Benjamin Kosnik (bkoz@redhat.com) on August 28, 2000
</I> </I>
<p>
<h2> <h2>
1. Abstract 1. Abstract
</h2> </h2>
...@@ -142,14 +147,14 @@ includes: ...@@ -142,14 +147,14 @@ includes:
<ul> <ul>
<li> <li>
</p> <p>
Identifiers for each of the codesets involved in the conversion. For Identifiers for each of the codesets involved in the conversion. For
example, using the iconv family of functions from the Single Unix example, using the iconv family of functions from the Single Unix
Specification (what used to be called X/Open) hosted on the GNU/Linux Specification (what used to be called X/Open) hosted on the GNU/Linux
operating system allows bi-directional mapping between far more than operating system allows bi-directional mapping between far more than
the following tantalizing possibilities: the following tantalizing possibilities:
</p>
<p>
(An edited list taken from <code>`iconv --list`</code> on a Red Hat 6.2/Intel system: (An edited list taken from <code>`iconv --list`</code> on a Red Hat 6.2/Intel system:
<BLOCKQUOTE> <BLOCKQUOTE>
...@@ -519,4 +524,5 @@ System Interface Definitions, Issue 6 (IEEE Std. 1003.1-200x) ...@@ -519,4 +524,5 @@ System Interface Definitions, Issue 6 (IEEE Std. 1003.1-200x)
The Open Group/The Institute of Electrical and Electronics Engineers, Inc. The Open Group/The Institute of Electrical and Electronics Engineers, Inc.
http://www.opennc.org/austin/docreg.html http://www.opennc.org/austin/docreg.html
</body>
</html>
libstdc++-v3/docs/html/22_locale/ctype.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html> <html>
<head> <head>
<title>
Notes on the ctype implementation.
</title>
</head>
<body>
<h1> <h1>
Notes on the ctype implementation. Notes on the ctype implementation.
</h1> </h1>
</head>
<I> <I>
prepared by Benjamin Kosnik (bkoz@redhat.com) on August 30, 2000 prepared by Benjamin Kosnik (bkoz@redhat.com) on August 30, 2000
</I> </I>
...@@ -60,15 +65,13 @@ to wchar_t and wcsrtombs for conversions between wchar_t and char. ...@@ -60,15 +65,13 @@ to wchar_t and wcsrtombs for conversions between wchar_t and char.
Neither of these two required specializations deals with Unicode Neither of these two required specializations deals with Unicode
characters. As such, libstdc++-v3 implements characters. As such, libstdc++-v3 implements
<p> <p>
<h2> <h2>
5. Examples 5. Examples
</h2> </h2>
<pre> <pre>
typedef ctype<char> cctype; typedef ctype&lt;char&gt; cctype;
</pre> </pre>
More information can be found in the following testcases: More information can be found in the following testcases:
...@@ -98,10 +101,10 @@ More information can be found in the following testcases: ...@@ -98,10 +101,10 @@ More information can be found in the following testcases:
straighten out the configure-time mess that is a by-product of straighten out the configure-time mess that is a by-product of
this class? this class?
<li> get the ctype<wchar_t>::mask stuff under control. Need to <li> get the ctype&lt;wchar_t&gt;::mask stuff under control. Need to
make some kind of static table, and not do lookup evertime make some kind of static table, and not do lookup evertime
somebody hits the do_is... functions. Too bad we can't just somebody hits the do_is... functions. Too bad we can't just
redefine mask for ctype<wchar_t> redefine mask for ctype&lt;wchar_t&gt;
<li> rename abstract base class. See if just smash-overriding <li> rename abstract base class. See if just smash-overriding
is a better approach. Clarify, add sanity to naming. is a better approach. Clarify, add sanity to naming.
...@@ -143,4 +146,5 @@ System Interface Definitions, Issue 6 (IEEE Std. 1003.1-200x) ...@@ -143,4 +146,5 @@ System Interface Definitions, Issue 6 (IEEE Std. 1003.1-200x)
The Open Group/The Institute of Electrical and Electronics Engineers, Inc. The Open Group/The Institute of Electrical and Electronics Engineers, Inc.
http://www.opennc.org/austin/docreg.html http://www.opennc.org/austin/docreg.html
</body>
</html>
libstdc++-v3/docs/html/22_locale/howto.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html> <html>
<head> <head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
...@@ -49,6 +49,7 @@ ...@@ -49,6 +49,7 @@
</p> </p>
<p>The following is the abstract from the implementation notes: <p>The following is the abstract from the implementation notes:
</p>
<blockquote> <blockquote>
The standard class codecvt attempts to address conversions between The standard class codecvt attempts to address conversions between
different character encoding schemes. In particular, the standard different character encoding schemes. In particular, the standard
...@@ -64,7 +65,6 @@ ...@@ -64,7 +65,6 @@
the required specializations for wide and narrow characters and the the required specializations for wide and narrow characters and the
implementation-provided extended functionality are given. implementation-provided extended functionality are given.
</blockquote> </blockquote>
</p>
<hr> <hr>
<h2><a name="3">class ctype</a></h2> <h2><a name="3">class ctype</a></h2>
...@@ -88,13 +88,13 @@ ...@@ -88,13 +88,13 @@
description of locales and how to use them. description of locales and how to use them.
</p> </p>
<p>He also writes: <p>He also writes:
</p>
<blockquote><em> <blockquote><em>
Please note that I still consider this detailed description of Please note that I still consider this detailed description of
locales beyond the needs of most C++ programmers. It is written locales beyond the needs of most C++ programmers. It is written
with experienced programmers in mind and novices will do best to with experienced programmers in mind and novices will do best to
avoid it. avoid it.
</em></blockquote> </em></blockquote>
</p>
<hr> <hr>
<h2><a name="6">Nathan Myers on Locales</a></h2> <h2><a name="6">Nathan Myers on Locales</a></h2>
...@@ -131,6 +131,7 @@ ...@@ -131,6 +131,7 @@
is created. Then member functions of that locale are called to is created. Then member functions of that locale are called to
perform minor tasks. Continuing the example from Chapter 21, we wish perform minor tasks. Continuing the example from Chapter 21, we wish
to use the following convenience functions: to use the following convenience functions:
</p>
<pre> <pre>
namespace std { namespace std {
template &lt;class charT&gt; template &lt;class charT&gt;
...@@ -140,6 +141,7 @@ ...@@ -140,6 +141,7 @@
charT charT
tolower (charT c, const locale&amp; loc) const; tolower (charT c, const locale&amp; loc) const;
}</pre> }</pre>
<p>
This function extracts the appropriate &quot;facet&quot; from the This function extracts the appropriate &quot;facet&quot; from the
locale <em>loc</em> and calls the appropriate member function of that locale <em>loc</em> and calls the appropriate member function of that
facet, passing <em>c</em> as its argument. The resulting character facet, passing <em>c</em> as its argument. The resulting character
...@@ -154,6 +156,7 @@ ...@@ -154,6 +156,7 @@
parameter. So we write simple wrapper structs to handle that. parameter. So we write simple wrapper structs to handle that.
</p> </p>
<p>The next-to-final version of the code started in Chapter 21 looks like: <p>The next-to-final version of the code started in Chapter 21 looks like:
</p>
<pre> <pre>
#include &lt;iterator&gt; // for back_inserter #include &lt;iterator&gt; // for back_inserter
#include &lt;locale&gt; #include &lt;locale&gt;
...@@ -195,7 +198,6 @@ ...@@ -195,7 +198,6 @@
std::string capital_s; std::string capital_s;
std::transform(s.begin(), s.end(), std::back_inserter(capital_s), up); std::transform(s.begin(), s.end(), std::back_inserter(capital_s), up);
}</pre> }</pre>
</p>
<p>The final version of the code uses <code>bind2nd</code> to eliminate <p>The final version of the code uses <code>bind2nd</code> to eliminate
the wrapper structs, but the resulting code is tricky. I have not the wrapper structs, but the resulting code is tricky. I have not
shown it here because no compilers currently available to me will shown it here because no compilers currently available to me will
......
libstdc++-v3/docs/html/22_locale/locale.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html> <html>
<head> <head>
<title>
Notes on the locale implementation.
</title>
</head>
<body>
<h1> <h1>
Notes on the locale implementation. Notes on the locale implementation.
</h1> </h1>
</head>
<I> <I>
prepared by Benjamin Kosnik (bkoz@redhat.com) on August 8, 2001 prepared by Benjamin Kosnik (bkoz@redhat.com) on August 8, 2001
</I> </I>
......
libstdc++-v3/docs/html/22_locale/messages.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html> <html>
<head> <head>
<h1> <title>
Notes on the messages implementation. Notes on the messages implementation.
</h1> </title>
</head> </head>
<body>
<h1>
Notes on the messages implementation.
</h1>
<I> <I>
prepared by Benjamin Kosnik (bkoz@redhat.com) on August 8, 2001 prepared by Benjamin Kosnik (bkoz@redhat.com) on August 8, 2001
</I> </I>
......
libstdc++-v3/docs/html/configopts.html
...@@ -34,6 +34,7 @@ options</a></h1> ...@@ -34,6 +34,7 @@ options</a></h1>
<p>The canonical way to find out the configure options that are <p>The canonical way to find out the configure options that are
available for a given set of libstdc++ sources is to go to the available for a given set of libstdc++ sources is to go to the
source directory and then type:<code> ./configure --help</code> source directory and then type:<code> ./configure --help</code>
</p>
<dl> <dl>
<dt><code>--enable-multilib </code>[default] <dt><code>--enable-multilib </code>[default]
...@@ -156,16 +157,18 @@ options</a></h1> ...@@ -156,16 +157,18 @@ options</a></h1>
the following puts all the libstdc++ headers into a directory the following puts all the libstdc++ headers into a directory
called &quot;2.97-20001008&quot; instead of the usual called &quot;2.97-20001008&quot; instead of the usual
&quot;g++-v3&quot;. &quot;g++-v3&quot;.
</p>
<pre> <pre>
--with-gxx-include-dir=/foo/H-x86-gcc-3-c-gxx-inc/include/2.97-20001008</pre> --with-gxx-include-dir=/foo/H-x86-gcc-3-c-gxx-inc/include/2.97-20001008</pre>
</p>
<dt><code>--enable-cxx-flags=FLAGS</code> <dt><code>--enable-cxx-flags=FLAGS</code>
<dd><p>With this option, you can pass a string of -f (functionality) <dd><p>With this option, you can pass a string of -f (functionality)
flags to the compiler to use when building libstdc++. FLAGS flags to the compiler to use when building libstdc++. FLAGS
is a quoted string of options, like is a quoted string of options, like
</p>
<pre> <pre>
--enable-cxx-flags='-fvtable-gc -fomit-frame-pointer -ansi'</pre> --enable-cxx-flags='-fvtable-gc -fomit-frame-pointer -ansi'</pre>
<p>
Note that the flags don't necessarily have to all be -f flags, Note that the flags don't necessarily have to all be -f flags,
as shown, but usually those are the ones that will make sense as shown, but usually those are the ones that will make sense
for experimentation and configure-time overriding. for experimentation and configure-time overriding.
...@@ -176,12 +179,13 @@ options</a></h1> ...@@ -176,12 +179,13 @@ options</a></h1>
as well, so that everything matches. as well, so that everything matches.
</p> </p>
<p>Fun flags to try might include combinations of <p>Fun flags to try might include combinations of
</p>
<pre> <pre>
-fstrict-aliasing -fstrict-aliasing
-fno-exceptions -fno-exceptions
-ffunction-sections -ffunction-sections
-fvtable-gc</pre> -fvtable-gc</pre>
and opposite forms (-fno-) of the same. Tell us (the libstdc++ <p>and opposite forms (-fno-) of the same. Tell us (the libstdc++
mailing list) if you discover more! mailing list) if you discover more!
</p> </p>
...@@ -211,7 +215,6 @@ options</a></h1> ...@@ -211,7 +215,6 @@ options</a></h1>
on. Hopefully people will volunteer to do other 'style' options. on. Hopefully people will volunteer to do other 'style' options.
</p> </p>
</dl> </dl>
</p>
<p>Return <a href="#top">to the top of the page</a> or <p>Return <a href="#top">to the top of the page</a> or
<a href="http://gcc.gnu.org/libstdc++/">to the libstdc++ homepage</a>. <a href="http://gcc.gnu.org/libstdc++/">to the libstdc++ homepage</a>.
</p> </p>
......
libstdc++-v3/docs/html/documentation.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html> <html>
<head> <head>
<meta name="KEYWORDS" <meta name="KEYWORDS"
...@@ -35,7 +36,6 @@ ...@@ -35,7 +36,6 @@
<li><a href="17_intro/TODO">TODO</a> <li><a href="17_intro/TODO">TODO</a>
- tasks yet undone - tasks yet undone
</ul> </ul>
</p>
<hr /> <hr />
...@@ -65,7 +65,6 @@ ...@@ -65,7 +65,6 @@
<li><a href="latest-doxygen/index.html">&quot;the latest collection&quot;</a> <li><a href="latest-doxygen/index.html">&quot;the latest collection&quot;</a>
(for the snapshot or later; see the date on the first page) (for the snapshot or later; see the date on the first page)
</ul> </ul>
</p>
<p>This generated HTML collection, as above, is also available for download in <p>This generated HTML collection, as above, is also available for download in
the libstdc++ snapshots directory at the libstdc++ snapshots directory at
<code>&lt;URL:ftp://gcc.gnu.org/pub/gcc/libstdc++/doxygen/&gt;</code>. <code>&lt;URL:ftp://gcc.gnu.org/pub/gcc/libstdc++/doxygen/&gt;</code>.
......
libstdc++-v3/docs/html/install.html
...@@ -88,46 +88,45 @@ ...@@ -88,46 +88,45 @@
features if the underlying support is present. features if the underlying support is present.
</p> </p>
<p>Finally, a few system-specific requirements: <p>Finally, a few system-specific requirements: </p>
<dl> <dl>
<dt> linux <dt> linux </dt>
<dd>If you are using gcc 3.1 or later on linux, and are using <dd>If you are using gcc 3.1 or later on linux, and are using
the gnu locale model (enabled by default for sufficient the gnu locale model (enabled by default for sufficient
versions of glibc), the following locales are used and tested versions of glibc), the following locales are used and tested
in the libstdc++ testsuites: en_HK, en_US, fr_FR, fr_FR@euro, in the libstdc++ testsuites: en_HK, en_US, fr_FR, fr_FR@euro,
de_DE, de_DE@euro, ja_JP.eucjp, and it_IT. Failure to have the de_DE, de_DE@euro, ja_JP.eucjp, and it_IT. Failure to have the
underlying "C" library locale information installed will mean underlying "C" library locale information installed will mean
that C++ named locales for the above regions will not work: that C++ named locales for the above regions will not work:
because of this, the libstdc++ testsuite will not pass the because of this, the libstdc++ testsuite will not pass the
named locale tests. If this isn't an issue, don't worry about named locale tests. If this isn't an issue, don't worry about
it. If named locales are needed, the underlying locale it. If named locales are needed, the underlying locale
information must be installed. Note that rebuilding libstdc++ information must be installed. Note that rebuilding libstdc++
after locales are installed is not necessary. after locales are installed is not necessary.
<p> To install <p> To install
support for locales, do only one of the following: </p> support for locales, do only one of the following: </p>
<p> <ul>
<li> install all locales <li> install all locales
<p> <code> export LC_ALL=C </code> </p> <p> <code> export LC_ALL=C </code> </p>
<p> <code> rpm -e glibc-common --nodeps </code> </p> <p> <code> rpm -e glibc-common --nodeps </code> </p>
<p> <code> rpm -i --define "_install_langs all" <p> <code> rpm -i --define "_install_langs all"
glibc-common-2.2.5-34.i386.rpm </code> </p> glibc-common-2.2.5-34.i386.rpm </code> </p>
</li> </li>
<li> install just the necessary locales <li> install just the necessary locales
<p> <code> localedef -i de_DE -f ISO-8859-1 de_DE </code> </p> <p> <code> localedef -i de_DE -f ISO-8859-1 de_DE </code> </p>
</li> </li>
</p> </ul>
</dd> </dd>
</dt>
</dl> </dl>
</p>
<hr> <hr>
<h2><a name="srcsetup">Setting up the source directories</a></h2> <h2><a name="srcsetup">Setting up the source directories</a></h2>
<p>The following definitions will be used throughout the rest of this <p>The following definitions will be used throughout the rest of this
document: document:
</p>
<ul> <ul>
<li><em>gccsrcdir</em>: The directory holding the source of the <li><em>gccsrcdir</em>: The directory holding the source of the
compiler. It should have several subdirectories like compiler. It should have several subdirectories like
...@@ -142,7 +141,7 @@ ...@@ -142,7 +141,7 @@
the compiler/libraries, set with the --prefix option to the compiler/libraries, set with the --prefix option to
the configure script. the configure script.
</ul> </ul>
Note: <p> Note: </p>
<ol> <ol>
<li>The 3.0 version and following are intended to replace the <li>The 3.0 version and following are intended to replace the
library that comes with the compiler, so <em>libsrcdir</em> library that comes with the compiler, so <em>libsrcdir</em>
...@@ -153,28 +152,27 @@ ...@@ -153,28 +152,27 @@
separate directories. Please don't build out of the separate directories. Please don't build out of the
source directory. source directory.
</ol> </ol>
</p>
<p>Check out or download the GCC sources: the resulting source directory <p>Check out or download the GCC sources: the resulting source directory
(<code>gcc</code> or <code>gcc-3.0.3</code>, for example) is (<code>gcc</code> or <code>gcc-3.0.3</code>, for example) is
<em>gccsrcdir</em>. <em>gccsrcdir</em>.
Once in <em>gccsrcdir</em>, you'll need to rename or delete the Once in <em>gccsrcdir</em>, you'll need to rename or delete the
libstdc++-v3 directory which comes with that snapshot: libstdc++-v3 directory which comes with that snapshot:
<pre> </p>
<pre>
mv libstdc++-v3 libstdc++-v3-previous <strong>[OR]</strong> mv libstdc++-v3 libstdc++-v3-previous <strong>[OR]</strong>
rm -r libstdc++-v3</pre> rm -r libstdc++-v3</pre>
</p>
<p>Next, unpack the libstdc++-v3 library tarball into this <p>Next, unpack the libstdc++-v3 library tarball into this
<em>gccsrcdir</em> directory; it will create a <em>gccsrcdir</em> directory; it will create a
<em>libsrcdir</em> called <code>libstdc++-<em>version</em></code>: <em>libsrcdir</em> called <code>libstdc++-<em>version</em></code>:
<pre>
gzip -dc libstdc++-version.tar.gz | tar xf -</pre>
</p> </p>
<pre>
gzip -dc libstdc++-version.tar.gz | tar xf -</pre>
<p>Finally, rename <em>libsrcdir</em> to <code>libstdc++-v3</code> so that <p>Finally, rename <em>libsrcdir</em> to <code>libstdc++-v3</code> so that
gcc's configure flags will be able to deal with the new library. gcc's configure flags will be able to deal with the new library.
<pre>
mv <em>libsrcdir</em> libstdc++-v3</pre>
</p> </p>
<pre>
mv <em>libsrcdir</em> libstdc++-v3</pre>
<hr> <hr>
...@@ -193,10 +191,9 @@ ...@@ -193,10 +191,9 @@
building the C++ language parts. building the C++ language parts.
</p> </p>
<p><pre> <pre>
cd <em>gccbuilddir</em> cd <em>gccbuilddir</em>
<em>gccsrcdir</em>/configure --prefix=<em>destdir</em> --other-opts...</pre> <em>gccsrcdir</em>/configure --prefix=<em>destdir</em> --other-opts...</pre>
</p>
<hr> <hr>
...@@ -214,9 +211,10 @@ ...@@ -214,9 +211,10 @@
</p> </p>
<h3>[re]building only libstdc++</h3> <h3>[re]building only libstdc++</h3>
<p>To rebuild just libstdc++, use: <p>To rebuild just libstdc++, use: </p>
<pre> <pre>
make all-target-libstdc++-v3</pre> make all-target-libstdc++-v3</pre>
<p>
This will configure and build the C++ library in the This will configure and build the C++ library in the
<em>gccbuilddir/cpu-vendor-os/</em>libstdc++ directory. <em>gccbuilddir/cpu-vendor-os/</em>libstdc++ directory.
</p> </p>
...@@ -229,39 +227,38 @@ ...@@ -229,39 +227,38 @@
information is causing problems, you can delete it entirely, or information is causing problems, you can delete it entirely, or
simply edit it and remove lines. simply edit it and remove lines.
</p> </p>
<p>You're done. Now install the rebuilt pieces with <p>You're done. Now install the rebuilt pieces with</p>
<pre> <pre>
make install</pre> make install</pre>
or <p>or</p>
<pre> <pre>
make install-gcc make install-gcc
make install-target-libstdc++-v3</pre> make install-target-libstdc++-v3</pre>
</p>
<hr> <hr>
<h2><a name="postinstall">Post-installation</a></h2> <h2><a name="postinstall">Post-installation</a></h2>
<p>Installation will create the <em>destdir</em> directory and <p>Installation will create the <em>destdir</em> directory and
populate it with subdirectories: populate it with subdirectories:
<pre> </p>
<pre>
lib/ lib/
include/g++-v3/ include/g++-v3/
backward/ backward/
bits/ bits/
<em>cpu-vendor-os</em>/bits/ <em>cpu-vendor-os</em>/bits/
ext/</pre> ext/</pre>
</p>
<p>If you used the version-specific-libs configure option, then most of <p>If you used the version-specific-libs configure option, then most of
the headers and library files will be moved under the headers and library files will be moved under
<code>lib/gcc-lib/</code> instead. <code>lib/gcc-lib/</code> instead.
</p> </p>
<p>You can check the status of the build without installing it using <p>You can check the status of the build without installing it using</p>
<pre> <pre>
make check</pre> make check</pre>
or you can check the status of the installed library using <p>or you can check the status of the installed library using</p>
<pre> <pre>
make check-install</pre> make check-install</pre>
in the <em>libbuilddir</em> directory. <p>in the <em>libbuilddir</em> directory.
These commands will create a 'testsuite' directory underneath These commands will create a 'testsuite' directory underneath
<em>libbuilddir</em> containing the results of the tests. We are <em>libbuilddir</em> containing the results of the tests. We are
interested in any strange failures of the testsuite; please see interested in any strange failures of the testsuite; please see
...@@ -271,7 +268,7 @@ ...@@ -271,7 +268,7 @@
<hr> <hr>
<h2><a name="usage">Using the library</a></h2> <h2><a name="usage">Using the library</a></h2>
<li><B>Find the new library at runtime (shared linking only)</B> <h3>Find the new library at runtime (shared linking only)</h3>
<p>If you only built a static library (libstdc++.a), or if you <p>If you only built a static library (libstdc++.a), or if you
specified static linking, you don't have to worry about this. specified static linking, you don't have to worry about this.
But if you built a shared library (libstdc++.so) and linked But if you built a shared library (libstdc++.so) and linked
...@@ -281,6 +278,7 @@ ...@@ -281,6 +278,7 @@
<p>Methods vary for different platforms and different styles, but <p>Methods vary for different platforms and different styles, but
the usual ones are printed to the screen during installation. the usual ones are printed to the screen during installation.
They include: They include:
</p>
<ul> <ul>
<li>At runtime set LD_LIBRARY_PATH in your environment correctly, <li>At runtime set LD_LIBRARY_PATH in your environment correctly,
so that the shared library for libstdc++ can be found and so that the shared library for libstdc++ can be found and
...@@ -298,7 +296,6 @@ ...@@ -298,7 +296,6 @@
<li>More...? Let us know! <li>More...? Let us know!
</ul> </ul>
</ul> </ul>
</p>
<p>Use the <code>ldd(1)</code> utility to show which library the system <p>Use the <code>ldd(1)</code> utility to show which library the system
thinks it will get at runtime. thinks it will get at runtime.
</p> </p>
...@@ -306,8 +303,6 @@ ...@@ -306,8 +303,6 @@
you use Libtool to create your executables, these details are you use Libtool to create your executables, these details are
taken care of for you. taken care of for you.
</p> </p>
</ol>
</p>
<!-- <!--
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment