diff options
author | Benjamin Kosnik <bkoz@redhat.com> | 2004-05-13 15:14:07 +0000 |
---|---|---|
committer | Benjamin Kosnik <bkoz@gcc.gnu.org> | 2004-05-13 15:14:07 +0000 |
commit | 4b351c6ee882549651730baaaab38bd803b34770 (patch) | |
tree | 531ead475ff7a8725c1ecadae9de28aaf975accc | |
parent | 5c61a8637793dd25f01d7e58f775d19f0ade7493 (diff) | |
download | gcc-4b351c6ee882549651730baaaab38bd803b34770.zip gcc-4b351c6ee882549651730baaaab38bd803b34770.tar.gz gcc-4b351c6ee882549651730baaaab38bd803b34770.tar.bz2 |
re PR libstdc++/15074 (g++ -lsupc++ still links against libstdc++)
2004-05-13 Benjamin Kosnik <bkoz@redhat.com>
PR libstdc++/15074
* docs/html/faq/index.html: Update docs for libsupc++ usage.
From-SVN: r81786
-rw-r--r-- | libstdc++-v3/ChangeLog | 5 | ||||
-rw-r--r-- | libstdc++-v3/docs/html/faq/index.html | 21 |
2 files changed, 16 insertions, 10 deletions
diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index 56da7b3..4412daa 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,5 +1,10 @@ 2004-05-13 Benjamin Kosnik <bkoz@redhat.com> + PR libstdc++/15074 + * docs/html/faq/index.html: Update docs for libsupc++ usage. + +2004-05-13 Benjamin Kosnik <bkoz@redhat.com> + PR libstdc++/15412 * include/bits/stl_threads.h (_GLIBCXX_mutex): Move to namespace __gnu_internal. diff --git a/libstdc++-v3/docs/html/faq/index.html b/libstdc++-v3/docs/html/faq/index.html index 4bfc6d4..9a8bbaf 100644 --- a/libstdc++-v3/docs/html/faq/index.html +++ b/libstdc++-v3/docs/html/faq/index.html @@ -395,16 +395,17 @@ which is no longer available, thanks deja...--> <p>It's not a bug, and it's not really a problem. Nevertheless, some people don't like it, so here are two pseudo-solutions: </p> - <p>If the only functions from libstdc++.a which you need are language - support functions (those listed in - <a href="../18_support/howto.html">clause 18</a> of the standard, - e.g., <code>new</code> and <code>delete</code>), then try linking - against <code>libsupc++.a</code> (usually specifying - <code>-lsupc++</code> when calling g++ for the final link step will - do it). This library contains only those support routines, one per - object file. But if you are using anything from the rest of the - library, such as IOStreams or vectors, then you'll still need - pieces from <code>libstdc++.a</code>. + <p>If the only functions from libstdc++.a which you need are + language support functions (those listed in <a + href="../18_support/howto.html">clause 18</a> of the + standard, e.g., <code>new</code> and <code>delete</code>), + then try linking against <code>libsupc++.a</code> (Using + <code>gcc</code> instead of <code>g++</code> and explicitly + linking in <code>-lsupc++</code> for the final link step will + do it). This library contains only those support routines, + one per object file. But if you are using anything from the + rest of the library, such as IOStreams or vectors, then + you'll still need pieces from <code>libstdc++.a</code>. </p> <p>The second method is one we hope to incorporate into the library build process. Some platforms can place each function and variable |