public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: fnf@ninemoons.com
To: gcc-gnats@gcc.gnu.org
Cc: fnf@ninemoons.com
Subject: libstdc++/4052: including algobase.h results in error
Date: Fri, 17 Aug 2001 15:26:00 -0000	[thread overview]
Message-ID: <200108172216.f7HMGtf02548@fishpond.ninemoons.com> (raw)

>Number:         4052
>Category:       libstdc++
>Synopsis:       including algobase.h results in syntax error
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Fri Aug 17 15:26:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Fred Fish
>Release:        3.1 20010817 (experimental)
>Organization:
none
>Environment:
System: Linux fishpond.ninemoons.com 2.4.2-2smp #1 SMP Sun Apr 8 20:21:34 EDT 2001 i686 unknown
Architecture: i686

host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: /src/sourceware/gcc/gcc/configure -v --prefix=/usr/sourceware --enable-shared
>Description:

  Including algobase.h results in a syntax error.  Older versions
  of gcc don't exhibit this problem (2.96 for example).
  
>How-To-Repeat:

  Script started on Fri Aug 17 15:10:27 2001
  $ /usr/bin/gcc -v
  Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs
  gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-81)
  $ cat j.cc
  #include <algobase.h>
  $ /usr/bin/gcc -c j.cc
  $ /usr/sourceware/bin/gcc -v
  Reading specs from /usr/sourceware/lib/gcc-lib/i686-pc-linux-gnu/3.1/specs
  Configured with: /src/sourceware/gcc/gcc/configure -v --prefix=/usr/sourceware --enable-shared
  Thread model: single
  gcc version 3.1 20010817 (experimental)
  $ /usr/sourceware/bin/gcc -c j.cc
  In file included from /usr/sourceware/include/g++-v3/backward/algobase.h:58,
                   from j.cc:1:
  /usr/sourceware/include/g++-v3/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.
  In file included from /usr/sourceware/include/g++-v3/backward/algobase.h:60,
                   from j.cc:1:
  /usr/sourceware/include/g++-v3/backward/iterator.h:83: `reverse_bidirectional_iterator'
     not declared
  /usr/sourceware/include/g++-v3/backward/iterator.h:85: `istream_iterator' not 
     declared
  /usr/sourceware/include/g++-v3/backward/iterator.h:86: `ostream_iterator' not 
     declared
  /usr/sourceware/include/g++-v3/backward/iterator.h:108: parse error before `}' 
     token
  $ exit
  exit
  
  Script done on Fri Aug 17 15:11:09 2001

>Fix:
  No fix currently known.  Perhaps it is a simple as needing to
  include another header prior to including algobase.h.

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


                 reply	other threads:[~2001-08-17 15:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200108172216.f7HMGtf02548@fishpond.ninemoons.com \
    --to=fnf@ninemoons.com \
    --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).