diff mbox

[RFA,doc] libstdc++ FAQ and bug reporting

Message ID alpine.LFD.2.02.1102140018510.13812@ybpnyubfg6.ybpnyqbznva6
State New
Headers show

Commit Message

Gerald Pfeifer Feb. 13, 2011, 11:21 p.m. UTC
On Mon, 7 Feb 2011, Jonathan Wakely wrote:
> Yes.  Thanks for making these improvements.

Thanks for looking into this.

For the record, this is the version I applied to the GCC 4.5 branch;
exactly the same contents, just the markup had changed so I needed to
accomodate for that.

Gerald


2011-02-13  Gerald Pfeifer  <gerald@pfeifer.com>

	* doc/xml/faq.xml: Adjust link to bug database.
	Remove old item on broken header files.
diff mbox

Patch

Index: doc/xml/faq.xml
===================================================================
--- doc/xml/faq.xml	(revision 170111)
+++ doc/xml/faq.xml	(working copy)
@@ -745,7 +745,7 @@ 
     </para> 
     <para> 
     Before reporting a bug, please examine the
-    <ulink url="http://gcc.gnu.org/bugs.html">bugs database</ulink> with the
+    <ulink url="http://gcc.gnu.org/bugs/">bugs database</ulink> with the
     category set to <quote>g++</quote>. 
     </para> 
   </answer>
@@ -848,17 +848,9 @@ 
   </question>
   <answer id="a-v2_headers">
       <para>
-	If you have found an extremely broken header file which is
-	causing problems for you, look carefully before submitting a
-	&quot;high&quot; priority bug report (which you probably
-	shouldn't do anyhow; see the last paragraph of the page
-	describing <ulink url="http://gcc.gnu.org/bugs.html">the GCC
-	bug database</ulink>).
-      </para>
-      <para>
-	If the headers are in <filename>${prefix}/include/g++-3</filename>, or
-	if the installed library's name looks like
-	<filename>libstdc++-2.10.a</filename> or
+	If you are using headers in
+	<filename>${prefix}/include/g++-3</filename>, or if the installed
+	library's name looks like <filename>libstdc++-2.10.a</filename> or
 	<filename>libstdc++-libc6-2.10.so</filename>, then you are using the
 	old libstdc++-v2 library, which is nonstandard and
 	unmaintained.  Do not report problems with -v2 to the -v3