From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29693] clang-libs from f37 fails self test with pre-2.3 trunk
Date: Wed, 17 May 2023 15:36:37 +0000 [thread overview]
Message-ID: <bug-29693-9487-jCn4kHEvUd@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29693-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29693
dodji at redhat dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #5 from dodji at redhat dot com ---
This issue should now be solved by commit
https://sourceware.org/git/?p=libabigail.git;a=commit;h=06e8d54d0404ccf2a103804ec568797822152b69,
applied to the master branch. This fix should be available in the 2.4 version
of libabigail.
Thank you for taking the time to file this issue and sorry for the
inconvenience.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-05-17 15:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 22:14 [Bug default/29693] New: clang-libs from f37 fails self test with 2.1 woodard at redhat dot com
2022-10-14 22:15 ` [Bug default/29693] " woodard at redhat dot com
2022-10-25 17:01 ` woodard at redhat dot com
2023-03-23 21:13 ` woodard at redhat dot com
2023-03-23 23:41 ` woodard at redhat dot com
2023-03-24 16:20 ` woodard at redhat dot com
2023-03-31 22:46 ` [Bug default/29693] clang-libs from f37 fails self test with pre-2.3 trunk woodard at redhat dot com
2023-04-11 14:51 ` dodji at redhat dot com
2023-05-17 15:36 ` dodji at redhat dot com [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=bug-29693-9487-jCn4kHEvUd@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--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).