public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mathieu.malaterre at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/49387] t.cxx:140: error: too many initializers for ‘const __class_type_info_pseudo’
Date: Mon, 13 Jun 2011 09:50:00 -0000	[thread overview]
Message-ID: <bug-49387-4-TGFC6Ur74S@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49387-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Mathieu Malaterre <mathieu.malaterre at gmail dot com> 2011-06-13 09:49:41 UTC ---
Test was done a on a debian/squeeze system:

$ g++ --version
g++ (Debian 4.4.5-8) 4.4.5


$ apt-cache policy libboost1.42-dev
libboost1.42-dev:
  Installed: 1.42.0-4
  Candidate: 1.42.0-4
  Version table:
     1.42.0-4+b1 0
        200 http://ftp.fr.debian.org/debian/ testing/main amd64 Packages
        100 http://ftp.fr.debian.org/debian/ unstable/main amd64 Packages
 *** 1.42.0-4 0
        500 http://ftp.fr.debian.org/debian/ squeeze/main amd64 Packages
        100 /var/lib/dpkg/status


  parent reply	other threads:[~2011-06-13  9:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-13  7:25 [Bug c++/49387] New: " mathieu.malaterre at gmail dot com
2011-06-13  9:07 ` [Bug c++/49387] " redi at gcc dot gnu.org
2011-06-13  9:09 ` mathieu.malaterre at gmail dot com
2011-06-13  9:46 ` redi at gcc dot gnu.org
2011-06-13  9:50 ` mathieu.malaterre at gmail dot com [this message]
2011-06-13 11:54 ` redi at gcc dot gnu.org
2011-06-13 12:40 ` redi at gcc dot gnu.org
2011-06-30 22:51 ` jason at gcc dot gnu.org
2011-07-01  0:53 ` jason at gcc dot gnu.org
2011-07-01  0:54 ` jason at gcc dot gnu.org
2022-04-29  3:00 ` cvs-commit at gcc dot gnu.org
2022-05-15 16:29 ` cvs-commit at gcc dot gnu.org

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=bug-49387-4-TGFC6Ur74S@http.gcc.gnu.org/bugzilla/ \
    --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).