From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29414] New: darktable fails -self-compare
Date: Wed, 27 Jul 2022 02:27:25 +0000 [thread overview]
Message-ID: <bug-29414-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29414
Bug ID: 29414
Summary: darktable fails -self-compare
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 as of df28c220976f41620b0bd7b22000815e11f66b75
Comparing the ABI of binaries between darktable-3.8.1-1.fc36.aarch64.rpm and
darktable-3.8.1-1.fc36.aarch64.rpm:
======== comparing'libdarktable.so' to itself wrongly yielded result:
===========
Functions changes summary: 0 Removed, 3 Changed (27 filtered out), 0 Added
functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
3 functions with some indirect sub-type change:
[C] 'function int _get_multi_priority(dt_develop_t*, const char*, const
int, const gboolean)' at iop_order.c:1119:1 has some indirect sub-type changes:
parameter 1 of type 'dt_develop_t*' changed:
in pointed to type 'typedef dt_develop_t' at develop.h:343:1:
[C] 'function void dt_dev_exposure_reset_defaults(dt_develop_t*)' at
develop.c:2268:1 has some indirect sub-type changes:
[C] 'function void dt_ioppr_change_iop_order(dt_develop_t*, const int32_t,
GList*)' at iop_order.c:939:1 has some indirect sub-type changes:
parameter 1 of type 'dt_develop_t*' changed:
in pointed to type 'struct dt_develop_t' at develop.h:148:1:
===SELF CHECK FAILED for 'libdarktable.so'
This seems to fail due to confusion between a type and a typedef. This seems to
be a class of problems that recently appeared on the libabigail trunk sometime
in the last week or so of commits.
Other packages which seem to have the same problem are:
enlightenment
gsoap
libcouchbase
lighttpd
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-07-27 2:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 2:27 woodard at redhat dot com [this message]
2022-07-27 2:34 ` [Bug default/29414] " woodard at redhat dot com
2022-07-27 2:37 ` woodard at redhat dot com
2022-07-28 13:45 ` woodard at redhat dot com
2022-10-14 16:35 ` 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-29414-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).