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
This commit is contained in:
Benjamin Kosnik 2004-05-13 15:14:07 +00:00 committed by Benjamin Kosnik
parent 5c61a86377
commit 4b351c6ee8
2 changed files with 16 additions and 10 deletions

View File

@ -1,3 +1,8 @@
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

View File

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