Re: libstdc++/6913: <fstream> totally broken?

Re: libstdc++/6913: <fstream> totally broken?

[David Abrahams]

The following reply was made to PR libstdc++/6913; it has been noted by GNATS.

From: "David Abrahams" <david.abrahams@rcn.com>
To: <pme@gcc.gnu.org>,
	<david.abrahams@rcn.com>,
	<gcc-bugs@gcc.gnu.org>,
	<gcc-prs@gcc.gnu.org>,
	<nobody@gcc.gnu.org>,
	<gcc-gnats@gcc.gnu.org>
Cc:  
Subject: Re: libstdc++/6913: <fstream> totally broken?
Date: Mon, 3 Jun 2002 08:52:19 -0400

 The FAQ says
 
 "Please read the installation instructions for GCC, specifically the
 part about not installing newer versions on top of older versions"
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 So I followed the link trying to find that part, but I can't. Having a
 mention in the FAQ but nothing [sufficiently visible] in the installation
 instructions borders on a cruel joke. How can poor lusers like me recover a
 correct system?
 
 -Dave
 
 ----- Original Message -----
 From: <pme@gcc.gnu.org>
 To: <david.abrahams@rcn.com>; <gcc-bugs@gcc.gnu.org>;
 <gcc-prs@gcc.gnu.org>; <nobody@gcc.gnu.org>
 Sent: Monday, June 03, 2002 12:22 AM
 Subject: Re: libstdc++/6913: <fstream> totally broken?
 
 
 > Synopsis: <fstream> totally broken?
 >
 > State-Changed-From-To: open->closed
 > State-Changed-By: pme
 > State-Changed-When: Sun Jun  2 21:22:45 2002
 > State-Changed-Why:
 >     FAQ:
 >
 >     http://gcc.gnu.org/onlinedocs/libstdc++/faq/index.html#4_0
 >
 >     About two paragraphs down.
 >
 >
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&
 pr=6913
 >
 

Re: libstdc++/6913: <fstream> totally broken?

[David Abrahams]

The following reply was made to PR libstdc++/6913; it has been noted by GNATS.

From: "David Abrahams" <david.abrahams@rcn.com>
To: "Phil Edwards" <phil@jaj.com>
Cc: <gcc-bugs@gcc.gnu.org>,
	<gcc-gnats@gcc.gnu.org>
Subject: Re: libstdc++/6913: <fstream> totally broken?
Date: Mon, 3 Jun 2002 09:34:42 -0400

 From: "Phil Edwards" <phil@jaj.com>
 
 
 > On Mon, Jun 03, 2002 at 08:52:19AM -0400, David Abrahams wrote:
 > > The FAQ says
 > >
 > > "Please read the installation instructions for GCC, specifically the
 > > part about not installing newer versions on top of older versions"
 > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 > >
 > > So I followed the link trying to find that part, but I can't. Having a
 > > mention in the FAQ but nothing [sufficiently visible] in the
 installation
 > > instructions borders on a cruel joke.
 >
 > On the top-level installation page, there's a bit recommending that each
 > GCC get a directory of its own.
 
 The way it's phrased, it sounds like the only reason for that is that you
 might want to un-install it. I won't want to (I have to test against
 multiple versions of GCC) and anyway I assumed that the -V option doesn't
 work to select different versions if you follow that recommendation.
 
 > On one of the pages linked from that page,
 > there should be a paragraph pointing it out in more detail, but I don't
 > recall where offhand.
 
 Yes, there should be. However, I scoured those pages for "version",
 "directory", and "older" and saw nothing relevant.
 
 > If you feel that the existing wording doesn't jump out strongly enough,
 > please do suggest alternates.  Some of us have been reading these pages
 > for so long that we no longer see the words.
 
 This is a no-brainer: in BIG, BOLD letters, on the main installation page
 and on the release pages of the first version which had this problem, and
 several versions thereafter:
 
 <b><font color="#ff0000">CAUTION</font>: installing a new version of GCC
 over another one with a different major or minor version number can cause
 both versions to malfunction. You must pass "--prefix=..." as an argument
 to configure in order to avoid installation conflicts</b>.
 
 Actually, the configure script should take care of detecting this mistake
 and prompting for alternatives.
 
 > > correct system?
 >
 > Easiest way to to just delete the previous installation before running
 > "make install" for the new build.
 
 And how does one do that?
 
 My installation prefix was the default, which appears to have been
 /usr/local. Is there a description somewhere of all the directories and
 files added by a GCC installation? How will I know which files to delete?
 
 > Or, if you don't mind building it again, rebuild with a
 different --prefix.
 
 I don't mind rebuilding at all, so long as I know how to make things work
 correctly.
 
 Thanks for your help,
 Dave
 
 

Re: libstdc++/6913: <fstream> totally broken?

[Phil Edwards]

The following reply was made to PR libstdc++/6913; it has been noted by GNATS.

From: Phil Edwards <phil@jaj.com>
To: David Abrahams <david.abrahams@rcn.com>
Cc: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/6913: <fstream> totally broken?
Date: Mon, 3 Jun 2002 09:06:31 -0400

 On Mon, Jun 03, 2002 at 08:52:19AM -0400, David Abrahams wrote:
 > The FAQ says
 > 
 > "Please read the installation instructions for GCC, specifically the
 > part about not installing newer versions on top of older versions"
 > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 > 
 > So I followed the link trying to find that part, but I can't. Having a
 > mention in the FAQ but nothing [sufficiently visible] in the installation
 > instructions borders on a cruel joke.
 
 On the top-level installation page, there's a bit recommending that each
 GCC get a directory of its own.  On one of the pages linked from that page,
 there should be a paragraph pointing it out in more detail, but I don't
 recall where offhand.
 
 If you feel that the existing wording doesn't jump out strongly enough,
 please do suggest alternates.  Some of us have been reading these pages
 for so long that we no longer see the words.
 
 
 > correct system?
 
 Easiest way to to just delete the previous installation before running
 "make install" for the new build.  Or, if you don't mind building it again,
 rebuild with a different --prefix.
 
 -- 
 If ye love wealth greater than liberty, the tranquility of servitude greater
 than the animating contest for freedom, go home and leave us in peace.  We seek
 not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
 and may posterity forget that ye were our countrymen.            - Samuel Adams

Re: libstdc++/6913: <fstream> totally broken?

[pme]

Synopsis: <fstream> totally broken?

State-Changed-From-To: open->closed
State-Changed-By: pme
State-Changed-When: Sun Jun  2 21:22:45 2002
State-Changed-Why:
    FAQ:
    
    http://gcc.gnu.org/onlinedocs/libstdc++/faq/index.html#4_0
    
    About two paragraphs down.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6913

libstdc++/6913: <fstream> totally broken?

[david.abrahams]

>Number:         6913
>Category:       libstdc++
>Synopsis:       <fstream> totally broken?
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Jun 02 18:16:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     david.abrahams@rcn.com
>Release:        unknown-1.0
>Organization:
>Environment:
Linux/Cygwin
>Description:
A definition for __c_file_type seems to be entirely missing!

Errors:
--------

In file included from /usr/local/include/g++-v3/fstream:48,
                 from foo.cpp:1:
/usr/local/include/g++-v3/bits/basic_file.h:52: parse error before `{' token
/usr/local/include/g++-v3/bits/basic_file.h:57: virtual outside class 
   declaration
/usr/local/include/g++-v3/bits/basic_file.h:57: function `int std::overflow(int 
   = -1)' is initialized like a variable
/usr/local/include/g++-v3/bits/basic_file.h:60: virtual outside class 
   declaration
/usr/local/include/g++-v3/bits/basic_file.h:60: function `int std::underflow()' 
   is initialized like a variable
/usr/local/include/g++-v3/bits/basic_file.h:63: virtual outside class 
   declaration
/usr/local/include/g++-v3/bits/basic_file.h:63: function `int std::uflow()' is 
   initialized like a variable
/usr/local/include/g++-v3/bits/basic_file.h:66: virtual outside class 
   declaration
/usr/local/include/g++-v3/bits/basic_file.h:66: function `int 
...
>How-To-Repeat:
Compile this program:
--------
#include <fstream>
int main() { return 0; }
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: