public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bkoz@gcc.gnu.org To: bkoz@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, ilic@thetausa.com, nobody@gcc.gnu.org Subject: Re: libstdc++/6736: g++ 3.1 does not compile source code with istrstream Date: Thu, 23 May 2002 08:34:00 -0000 [thread overview] Message-ID: <20020523153437.28338.qmail@sources.redhat.com> (raw) Synopsis: g++ 3.1 does not compile source code with istrstream Responsible-Changed-From-To: unassigned->bkoz Responsible-Changed-By: bkoz Responsible-Changed-When: Thu May 23 08:34:35 2002 Responsible-Changed-Why: Mine. State-Changed-From-To: open->feedback State-Changed-By: bkoz State-Changed-When: Thu May 23 08:34:35 2002 State-Changed-Why: Can't reproduce. I get: In file included from /mnt/hd/bld/bld-x86-gcc/i686-pc-linux-gnu/libstdc++-v3/include/backward/strstream:51, from 6736.cc:12: /mnt/hd/bld/bld-x86-gcc/i686-pc-linux-gnu/libstdc++-v3/include/backward/backward_warning.h:32:2: warning: #warning This file includes at least one deprecated or antiquated header. Please consider using one of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples include substituting the <X> header for the <X.h> header for C++ includes, or <sstream> instead of the deprecated header <strstream.h>. To disable this warning use -Wno-deprecated. It's just a warning though, and the compilation is fine. -benjamin http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6736
next reply other threads:[~2002-05-23 15:34 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-23 8:34 bkoz [this message] 2002-05-23 8:46 Jovan Ilic 2002-05-23 8:56 Benjamin Kosnik 2002-06-03 2:41 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=20020523153437.28338.qmail@sources.redhat.com \ --to=bkoz@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=ilic@thetausa.com \ --cc=nobody@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: linkBe 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).