public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: libstdc++/3619: GCC 3.0 C++ backwards compatibility bug?
@ 2001-07-13 10:11 pme
0 siblings, 0 replies; 6+ messages in thread
From: pme @ 2001-07-13 10:11 UTC (permalink / raw)
To: gcc-bugs, gcc-prs, nobody, us
Synopsis: GCC 3.0 C++ backwards compatibility bug?
State-Changed-From-To: open->closed
State-Changed-By: pme
State-Changed-When: Fri Jul 13 10:11:40 2001
State-Changed-Why:
User installed 3.0 over a previous installation; reports
working after removing old tree and reinstalling.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3619&database=gcc
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: libstdc++/3619: GCC 3.0 C++ backwards compatibility bug?
@ 2001-07-13 10:16 Phil Edwards
0 siblings, 0 replies; 6+ messages in thread
From: Phil Edwards @ 2001-07-13 10:16 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR libstdc++/3619; it has been noted by GNATS.
From: Phil Edwards <pedwards@disaster.jaj.com>
To: us@ooc.de
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/3619: GCC 3.0 C++ backwards compatibility bug?
Date: Fri, 13 Jul 2001 13:09:48 -0400
On Fri, Jul 13, 2001 at 12:42:06PM +0200, Uwe Seimet wrote:
> I have now completely removed my installation of gcc 3.0 and recompiled
> everything. Looks as if something was left from older installations
> (includes that should now have been there anymore) because now everything is
Yeah, that will do it. Unfortunately there's no easy way to detect and warn
about this situation. Advising against it on the installation instructions
page is the best we can do. Good to hear that this works now; I'll close
the PR shortly.
Phil
--
Would I had phrases that are not known, utterances that are strange, in
new language that has not been used, free from repetition, not an utterance
which has grown stale, which men of old have spoken.
- anonymous Egyptian scribe, c.1700 BC
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: libstdc++/3619: GCC 3.0 C++ backwards compatibility bug?
@ 2001-07-13 3:46 Uwe Seimet
0 siblings, 0 replies; 6+ messages in thread
From: Uwe Seimet @ 2001-07-13 3:46 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR libstdc++/3619; it has been noted by GNATS.
From: Uwe Seimet <us@orbacus.com>
To: Phil Edwards <pedwards@disaster.jaj.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/3619: GCC 3.0 C++ backwards compatibility bug?
Date: Fri, 13 Jul 2001 12:42:06 +0200
Hello Phil,
> > duplo>/opt/egcs/bin/c++ test.cpp
> > In file included from test.cpp:1:
> > /opt/egcs/include/g++-v3/strstream:38: syntax error before `:' token
> > /opt/egcs/include/g++-v3/strstream:42: `_Traits' was not declared in this scope
> > /opt/egcs/include/g++-v3/strstream:42: syntax error before `;' token
> > /opt/egcs/include/g++-v3/strstream:48: type specifier omitted for parameter
> > /opt/egcs/include/g++-v3/strstream:48: parse error before `,' token
> > /opt/egcs/include/g++-v3/strstream:49: type specifier omitted for parameter
> > /opt/egcs/include/g++-v3/strstream:49: parse error before `,' token
> > /opt/egcs/include/g++-v3/strstream:50: type specifier omitted for parameter
> > /opt/egcs/include/g++-v3/strstream:50: parse error before `,' token
> > /opt/egcs/include/g++-v3/strstream:52: type specifier omitted for parameter
> > /opt/egcs/include/g++-v3/strstream:52: parse error before `)' token
> > /opt/egcs/include/g++-v3/strstream:53: type specifier omitted for parameter
> > /opt/egcs/include/g++-v3/strstream:53: parse error before `)' token
>
> I still can't reproduce this. Even those line numbers don't make sense.
> And strstream isn't installed into $prefix/include/g++-v3 anyhow; it's
> installed in the backward subdirectory one level deeper. Something is
> seriously wrong here.
I have now completely removed my installation of gcc 3.0 and recompiled
everything. Looks as if something was left from older installations
(includes that should now have been there anymore) because now everything is
fine. I get a warning about the use of deprecated header files now, which is
fine. Thanks a lot for your help.
Best regards, Uwe
--
----------------------------------------------------------------------------
Dr. Uwe Seimet mailto:us@iona.com
IONA Total Business Integration(tm) http://www.orbacus.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: libstdc++/3619: GCC 3.0 C++ backwards compatibility bug?
@ 2001-07-12 19:36 Phil Edwards
0 siblings, 0 replies; 6+ messages in thread
From: Phil Edwards @ 2001-07-12 19:36 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR libstdc++/3619; it has been noted by GNATS.
From: Phil Edwards <pedwards@disaster.jaj.com>
To: us@ooc.de
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/3619: GCC 3.0 C++ backwards compatibility bug?
Date: Thu, 12 Jul 2001 22:31:21 -0400
On Thu, Jul 12, 2001 at 10:03:17AM +0200, Uwe Seimet wrote:
> > > >Description:
> > > Compiling a file with this single line of code:
> > >
> > > #include <strstream>
> > >
> > > does not work but leads to error messages.
> >
> > /Which/ error message?
>
> I'm sorry I forgot to add the message. Here it is:
>
> duplo>/opt/egcs/bin/c++ test.cpp
> In file included from test.cpp:1:
> /opt/egcs/include/g++-v3/strstream:38: syntax error before `:' token
> /opt/egcs/include/g++-v3/strstream:42: `_Traits' was not declared in this scope
> /opt/egcs/include/g++-v3/strstream:42: syntax error before `;' token
> /opt/egcs/include/g++-v3/strstream:48: type specifier omitted for parameter
> /opt/egcs/include/g++-v3/strstream:48: parse error before `,' token
> /opt/egcs/include/g++-v3/strstream:49: type specifier omitted for parameter
> /opt/egcs/include/g++-v3/strstream:49: parse error before `,' token
> /opt/egcs/include/g++-v3/strstream:50: type specifier omitted for parameter
> /opt/egcs/include/g++-v3/strstream:50: parse error before `,' token
> /opt/egcs/include/g++-v3/strstream:52: type specifier omitted for parameter
> /opt/egcs/include/g++-v3/strstream:52: parse error before `)' token
> /opt/egcs/include/g++-v3/strstream:53: type specifier omitted for parameter
> /opt/egcs/include/g++-v3/strstream:53: parse error before `)' token
I still can't reproduce this. Even those line numbers don't make sense.
And strstream isn't installed into $prefix/include/g++-v3 anyhow; it's
installed in the backward subdirectory one level deeper. Something is
seriously wrong here.
Phil
--
Would I had phrases that are not known, utterances that are strange, in
new language that has not been used, free from repetition, not an utterance
which has grown stale, which men of old have spoken.
- anonymous Egyptian scribe, c.1700 BC
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: libstdc++/3619: GCC 3.0 C++ backwards compatibility bug?
@ 2001-07-11 13:36 Phil Edwards
0 siblings, 0 replies; 6+ messages in thread
From: Phil Edwards @ 2001-07-11 13:36 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR libstdc++/3619; it has been noted by GNATS.
From: Phil Edwards <pedwards@disaster.jaj.com>
To: us@ooc.de
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/3619: GCC 3.0 C++ backwards compatibility bug?
Date: Wed, 11 Jul 2001 16:36:06 -0400
On Mon, Jul 09, 2001 at 01:08:32PM -0000, us@ooc.de wrote:
> >Description:
> Compiling a file with this single line of code:
>
> #include <strstream>
>
> does not work but leads to error messages.
/Which/ error message?
> >How-To-Repeat:
> Just compile a one-line program, consisting of this line:
>
> #include <strstream>
This works for me; I cannot reproduce your problem.
^ permalink raw reply [flat|nested] 6+ messages in thread
* libstdc++/3619: GCC 3.0 C++ backwards compatibility bug?
@ 2001-07-09 6:16 us
0 siblings, 0 replies; 6+ messages in thread
From: us @ 2001-07-09 6:16 UTC (permalink / raw)
To: gcc-gnats
>Number: 3619
>Category: libstdc++
>Synopsis: GCC 3.0 C++ backwards compatibility bug?
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Jul 09 06:16:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Uwe Seimet
>Release: gcc version 3.1 20010525 (experimental)
>Organization:
>Environment:
System: Linux duplo 2.4.6 #1 SMP Wed Jul 4 13:42:19 MEST 2001 i686 unknown
Architecture: i686
<machine, os, target, libraries (multiple lines)>
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: /home/us/egcs/gcc/configure --prefix=/opt/egcs --enable-languages=c++ --enable-shared --enable-threads
>Description:
Compiling a file with this single line of code:
#include <strstream>
does not work but leads to error messages.
I'm aware that the file strstream is deprecated, but from
the comments in this file and the ANSI standard it looks as
it should still be usable in order to remain backwards
compatible.
>How-To-Repeat:
Just compile a one-line program, consisting of this line:
#include <strstream>
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2001-07-13 10:16 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-07-13 10:11 libstdc++/3619: GCC 3.0 C++ backwards compatibility bug? pme
-- strict thread matches above, loose matches on Subject: below --
2001-07-13 10:16 Phil Edwards
2001-07-13 3:46 Uwe Seimet
2001-07-12 19:36 Phil Edwards
2001-07-11 13:36 Phil Edwards
2001-07-09 6:16 us
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).