From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/28774] New: libclang.so.13.0.0 fails self check when run on aarch64
Date: Wed, 12 Jan 2022 21:54:23 +0000 [thread overview]
Message-ID: <bug-28774-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28774
Bug ID: 28774
Summary: libclang.so.13.0.0 fails self check when run on
aarch64
Product: libabigail
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: woodard at redhat dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
With the latest trunk of libabigail doing a self check with an aarch64 version
of abidw fails self check but when the same test is run on x86_64 it works. In
both casers the library being compared is the same one from the aarch64
package.
[aarch64] $ abidw --abidiff /lib64/libclang.so.13.0.0
Functions changes summary: 0 Removed, 0 Changed (12 filtered out), 0 Added
functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
[x86_64] $ abidw --abidiff libclang.so.13.0.0
[x86_64] $ echo $?
0
[aarch64] $ sum /lib64/libclang.so.13.0.0
07787 32962
[x86_64] $ sum libclang.so.13.0.0
07787 32962
[aarch64] $ rpm -qf /lib64/libclang.so.13.0.0
clang-libs-13.0.0-3.fc35.aarch64
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-01-12 21:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 21:54 woodard at redhat dot com [this message]
2022-01-12 21:54 ` [Bug default/28774] " woodard at redhat dot com
2022-06-29 19:51 ` woodard at redhat dot com
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-28774-9487@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).