public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/64956] [5 Regression] __GXX_ABI_VERSION needs a proper definition for the 5.x releases
Date: Tue, 10 Feb 2015 00:43:00 -0000	[thread overview]
Message-ID: <bug-64956-4-xAAT3cz4Ml@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64956-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64956

--- Comment #3 from Matthias Klose <doko at gcc dot gnu.org> ---
I found this snippet in one of the xapian headers.

#ifdef __GNUC__
#if __GNUC__ < 3 || (__GNUC__ == 3 && __GNUC_MINOR__ == 0)
#error Xapian no longer supports GCC < 3.1
#else
#if !defined(__GXX_ABI_VERSION) || __GXX_ABI_VERSION != 1002
#error The C++ ABI version of compiler you are using does not match
#error that of the compiler used to build the library. The versions
#error must match or your program will not work correctly.
#error The Xapian library was built with g++ 4.9.1
#endif

my impression was that a value of 999999 means something like
"unstable"/"newest". Assuming that there will be another version, which value
should be chosen for that one?


  parent reply	other threads:[~2015-02-10  0:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-05 23:32 [Bug c++/64956] New: " doko at gcc dot gnu.org
2015-02-09 14:32 ` [Bug c++/64956] [5 Regression] " rguenth at gcc dot gnu.org
2015-02-09 14:34 ` jakub at gcc dot gnu.org
2015-02-10  0:43 ` doko at gcc dot gnu.org [this message]
2015-02-12 21:30 ` jason at gcc dot gnu.org
2015-02-13  5:27 ` jason at gcc dot gnu.org
2015-02-13  8:43 ` trippels at gcc dot gnu.org
2015-02-13 14:48 ` jason 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-64956-4-xAAT3cz4Ml@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).