From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29912] smesh fails self compare on x86_64
Date: Tue, 21 Mar 2023 10:36:08 +0000 [thread overview]
Message-ID: <bug-29912-9487-bYTEWXB9PP@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29912-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29912
dodji at redhat dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|ASSIGNED |RESOLVED
--- Comment #4 from dodji at redhat dot com ---
(In reply to dodji from comment #3)
> (In reply to Ben Woodard from comment #1)
> > I think that qgis has the seme problem even with the latest trunk through
> > 5d97da97
> >
> > Comparing the ABI of binaries between qgis-3.26.1-2.fc37.aarch64.rpm and
> > qgis-3.26.1-2.fc37.aarch64.rpm:
> >
> > ==== SELF CHECK SUCCEEDED for 'libqgis_core.so.3.26.1' ====
> > ==== SELF CHECK SUCCEEDED for 'libqgis_gui.so.3.26.1' ====
> > ======== comparing'libqgis_app.so.3.26.1' to itself wrongly yielded result:
> > ===========
> > Functions changes summary: 0 Removed, 2 Changed, 0 Added functions
> > Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
> >
> > 2 functions with some indirect sub-type change:
> >
OK, so this is also fixed by the commit above. What I was seeing was an issue
related to my own environment.
So I am closing this report as fixed.
Thanks!
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-03-21 10:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 21:27 [Bug default/29912] New: " woodard at redhat dot com
2022-12-16 21:28 ` [Bug default/29912] " woodard at redhat dot com
2023-01-07 0:56 ` woodard at redhat dot com
2023-03-20 21:16 ` dodji at redhat dot com
2023-03-20 21:18 ` dodji at redhat dot com
2023-03-21 10: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-29912-9487-bYTEWXB9PP@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).