public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Peter Schmid <schmid@snake.iap.physik.tu-darmstadt.de>
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/7230: <strstream> header file is missing (trunk)
Date: Sun, 07 Jul 2002 15:46:00 -0000 [thread overview]
Message-ID: <200207072239.AAA26482@snake.iap.physik.tu-darmstadt.de> (raw)
>Number: 7230
>Category: libstdc++
>Synopsis: <strstream> header file is missing (trunk)
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Jul 07 15:46:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Peter Schmid
>Release: 3.2 20020707 (experimental)
>Organization:
TU Darmstadt
>Environment:
System: Linux kiste 2.4.18 #8 Sat Mar 9 15:33:15 CET 2002 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc/configure --enable-shared --disable-nls --enable-threads=posix --enable-languages=c,c++,f77,objc,treelang
>Description:
The header file <strstream> was removed from the libstdc++ sources that are
shipped with gcc 3.2. Is this an oversight or was it deliberate? This
removal breaks blitz, boost, etc. According to my understanding of the
standard, <strstream> is required for a conforming libstdc++ implementation,
though it is retained only for backward compatibility.
>How-To-Repeat:
tstrstream.C
#include <strstream>
g++ -v tstrstream.C
Reading specs from /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.2/specs
Configured with: ../gcc/configure --enable-shared --disable-nls --enable-threads=posix --enable-languages=c,c++,f77,objc,treelang
Thread model: posix
gcc version 3.2 20020707 (experimental)
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.2/cc1plus -quiet -v -D__GNUC__=3 -D__GNUC_MINOR__=2 -D__GNUC_PATCHLEVEL__=0 -D_GNU_SOURCE tstrstream.C -D__GNUG__=3 -D__DEPRECATED -D__EXCEPTIONS -D__GXX_ABI_VERSION=100 -quiet -dumpbase tstrstream.C -version -o /tmp/cc3ZdR3H.s
GNU C++ version 3.2 20020707 (experimental) (i686-pc-linux-gnu)
compiled by GNU C version 3.2 20020707 (experimental).
ignoring nonexistent directory "NONE/include"
ignoring nonexistent directory "/usr/local/i686-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
/usr/local/include/c++/3.2
/usr/local/include/c++/3.2/i686-pc-linux-gnu
/usr/local/include/c++/3.2/backward
/usr/local/include
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.2/include
/usr/include
End of search list.
tstrstream.C:1:21: strstream: No such file or directory
Compilation exited abnormally with code 1 at Mon Jul 8 00:28:19
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-07-07 22:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-07 15:46 Peter Schmid [this message]
2002-07-07 22:56 Gabriel Dos Reis
2002-07-24 16:02 bkoz
2002-07-27 14:56 bkoz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200207072239.AAA26482@snake.iap.physik.tu-darmstadt.de \
--to=schmid@snake.iap.physik.tu-darmstadt.de \
--cc=gcc-gnats@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).