From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/23705] abidiff issue with harfbuzz
Date: Mon, 01 Jan 2018 00:00:00 -0000 [thread overview]
Message-ID: <bug-23705-9487-HiSZJ2Cp5F@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23705-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23705
dodji at redhat dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from dodji at redhat dot com ---
After the recent fixes hit the master git branch, it seems I cannot reproduce
this issue anymore, even with the tarball that you attached. Here is what I am
getting as a result:
$ abidiff --no-added-syms --drop-private-types --headers-dir1
harfbuzz-1.8.4/usr/include --headers-dir2 harfbuzz-1.9.0/usr/include
--debug-info-dir1 harfbuzz-1.8.4/usr/lib/debug --debug-info-dir2
harfbuzz-1.9.0/usr/lib/debug harfbuzz-1.8.\
4/usr/lib/x86_64-linux-gnu/libharfbuzz.so.0.10800.4
harfbuzz-1.9.0/usr/lib/x86_64-linux-gnu/libharfbuzz.so.0.10900.0
Functions changes summary: 0 Removed, 0 Changed (83 filtered out), 0 Added (11
filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
$
I am thus tentatively closing this issue as solved.
Thanks for filing it!
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2018-10-02 13:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 0:00 [Bug default/23705] New: " bochecha at daitauha dot fr
2018-01-01 0:00 ` [Bug default/23705] " bochecha at daitauha dot fr
2018-01-01 0:00 ` 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-23705-9487-HiSZJ2Cp5F@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).