This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Error report (gcc 3.1)
Here's what I've added to the v3 FAQ on trunk and branch.
2002-05-16 Phil Edwards <pme@gcc.gnu.org>
* docs/html/faq/index.html: Update not-a-bug list with basic_file.h.
* docs/html/faq/index.txt: Regenerate.
Index: docs/html/faq/index.html
===================================================================
RCS file: /cvs/gcc/gcc/libstdc++-v3/docs/html/faq/index.html,v
retrieving revision 1.38
diff -u -3 -p -r1.38 index.html
--- docs/html/faq/index.html 2 May 2002 21:21:16 -0000 1.38
+++ docs/html/faq/index.html 16 May 2002 20:02:42 -0000
@@ -77,7 +77,7 @@
<li><a href="#4_4_interface">The g++-3 headers are
<strong>not ours</strong></a>
<li><a href="#4_4_glibc">compilation errors from streambuf.h</a>
- <li><a href="#4_4_checks">errors about <em>*Cconcept</em> and
+ <li><a href="#4_4_checks">errors about <em>*Concept</em> and
<em>constraints</em> in the STL...</a>
<li><a href="#4_4_dlsym">program crashes when using library code
in a dynamically-loaded library</a>
@@ -487,9 +487,7 @@ which is no longer available, thanks dej
<p>For 3.0.1, the most common "bug" is an apparently missing
"<code>../</code>" in include/Makefile, resulting in files
- like gthr.h and gthr-single.h not being found.
- </p>
- <p>Please read
+ like gthr.h and gthr-single.h not being found. Please read
<a href="http://gcc.gnu.org/install/configure.html";>the configuration
instructions for GCC</a>,
specifically the part about configuring in a separate build directory,
@@ -497,6 +495,18 @@ which is no longer available, thanks dej
is fragile, is rarely tested, and tends to break, as in this case.
This was fixed for 3.0.2.
</p>
+
+ <p>For 3.1, the most common "bug" is a parse error when using
+ <code><fstream></code>, ending with a message,
+ "<code>bits/basic_file.h:52: parse error before `{'
+ token</code>." Please read
+ <a href="http://gcc.gnu.org/install/";>the installation instructions for
+ GCC</a>, specifically the part about not installing newer versions on
+ top of older versions. If you install 3.1 over a 3.0.x release, then
+ the wrong basic_file.h header will be found (its location changed
+ between releases).
+ </p>
+
<p><strong>Please do not report these as bugs. We know about them.</strong>
Reporting this -- or any other problem that's already been fixed --
hinders the development of GCC, because we have to take time to