From: Dodji Seketeli <dodji@redhat.com>
To: Dodji Seketeli <dodji@redhat.com>
Cc: libabigail@sourceware.org
Subject: [PATCH 4/4, applied] Bump LIBABIGAIL_SO_CURRENT version to 4
Date: Fri, 01 Dec 2023 16:57:34 +0100 [thread overview]
Message-ID: <87edg5ncep.fsf@redhat.com> (raw)
In-Reply-To: <87v89hncoo.fsf@redhat.com> (Dodji Seketeli's message of "Fri, 01 Dec 2023 16:51:35 +0100")
Hello,
Recent patches change the ABI of the library, namely, by adding
parameters to functions like is_pointer_type or adding virtual member
functions to classes in the IR. Thus the LIBABIGAIL_SO_CURRENT
version has to be bumped from 3 to 4.
* configure.ac: Set LIBABIGAIL_SO_CURRENT to 4.
Signed-off-by: Dodji Seketeli <dodji@redhat.com>
Applied to master.
---
configure.ac | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure.ac b/configure.ac
index 2da4d152..65b738d8 100644
--- a/configure.ac
+++ b/configure.ac
@@ -25,7 +25,7 @@ dnl then increment LIBABIGAIL_SO_AGE.
dnl
dnl 4. If any interfaces have been removed or changed since the last
dnl public release, then set LIBABIGAIL_SO_AGE to 0.
-m4_define([libabigail_so_current], [3])
+m4_define([libabigail_so_current], [4])
m4_define([libabigail_so_revision], [0])
m4_define([libabigail_so_age], [0])
--
2.39.3
--
Dodji
prev parent reply other threads:[~2023-12-01 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 15:51 [PATCH 0/4] Support C++ pointer-to-member types Dodji Seketeli
2023-12-01 15:54 ` [PATCH 1/4, applied] Improve type naming Dodji Seketeli
2023-12-01 15:54 ` [PATCH 2/4, applied] Bug 30260 - Support pointer-to-member type Dodji Seketeli
2023-12-01 15:55 ` [PATCH 3/4, applied] Bump abixml version to 2.3 Dodji Seketeli
2023-12-01 15:57 ` Dodji Seketeli [this message]
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=87edg5ncep.fsf@redhat.com \
--to=dodji@redhat.com \
--cc=libabigail@sourceware.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).