public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: libstdc++/5826: g++ cannot compile its own fstream header file
@ 2002-03-04 8:47 pme
0 siblings, 0 replies; 2+ messages in thread
From: pme @ 2002-03-04 8:47 UTC (permalink / raw)
To: gcc-bugs, gcc-prs, nobody, us
Synopsis: g++ cannot compile its own fstream header file
State-Changed-From-To: open->closed
State-Changed-By: pme
State-Changed-When: Mon Mar 4 08:47:29 2002
State-Changed-Why:
Closed on request of submitter.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5826
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: libstdc++/5826: g++ cannot compile its own fstream header file
@ 2002-03-04 8:26 Uwe Seimet
0 siblings, 0 replies; 2+ messages in thread
From: Uwe Seimet @ 2002-03-04 8:26 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR libstdc++/5826; it has been noted by GNATS.
From: Uwe Seimet <us__nospam__@seimet.de>
To: us@ooc.de, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org?Subject=Re:,
libstdc++/582@ooc.de
Cc:
Subject: Re: libstdc++/5826: g++ cannot compile its own fstream header file
Date: Mon, 04 Mar 2002 17:16:36 +0100
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5826
Looks as if this problem was caused by old header files that were lying
around. I'm sorry for that and think this issue can be closed.
Best regards, Uwe
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-03-04 16:47 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-03-04 8:47 libstdc++/5826: g++ cannot compile its own fstream header file pme
-- strict thread matches above, loose matches on Subject: below --
2002-03-04 8:26 Uwe Seimet
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).