public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "peturr02 at ru dot is" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/13189] New: <ext/enc_filebuf.h> fails to compile
Date: Tue, 25 Nov 2003 16:23:00 -0000	[thread overview]
Message-ID: <20031125162319.13189.peturr02@ru.is> (raw)

This file has an extreme case of bitrot. It currently fails because it
hasn't been updated to compile with the new parser. Fixing that is not
likely to help though, since enc_char_traits::state_type and
enc_char_traits::pos_type don't meet the requirements for basic_filebuf.

enc_filebuf doesn't work with 3.2.3 or 3.3.2 either, it causes linker
errors.

-- 
           Summary: <ext/enc_filebuf.h> fails to compile
           Product: gcc
           Version: 3.4
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libstdc++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: peturr02 at ru dot is
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13189


             reply	other threads:[~2003-11-25 16:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-25 16:23 peturr02 at ru dot is [this message]
2003-11-25 16:25 ` [Bug libstdc++/13189] " peturr02 at ru dot is
2003-11-26 16:48 ` pinskia at gcc dot gnu dot org
2003-12-01  1:43 ` pinskia at gcc dot gnu dot org
2003-12-05  6:54 ` cvs-commit at gcc dot gnu dot org
2003-12-05 17:20 ` bkoz at gcc dot gnu dot org
2003-12-05 17:36 ` bangerth at dealii dot org
2003-12-09 18:42 ` dhazeghi at yahoo dot com

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=20031125162319.13189.peturr02@ru.is \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).