From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29299] New: binutils does not self compare properly
Date: Wed, 29 Jun 2022 19:16:39 +0000 [thread overview]
Message-ID: <bug-29299-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29299
Bug ID: 29299
Summary: binutils does not self compare properly
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: ---
Created attachment 14183
--> https://sourceware.org/bugzilla/attachment.cgi?id=14183&action=edit
huge list of errors
This is with the latest trunk as of: 7006c5f3c49b92f066a8f415e87b35a5c2afd32c
$ abidw --abidiff /usr/lib64/libbfd-2.37-27.fc36.so
from binutils-2.37-27.fc36.x86_64
There are many errors and so I just attached a file with them.
This was not a problem in 2.0.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-06-29 19:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 19:16 woodard at redhat dot com [this message]
2022-06-29 19:17 ` [Bug default/29299] " woodard at redhat dot com
2022-06-29 20:10 ` woodard at redhat dot com
2022-06-29 20:16 ` woodard at redhat dot com
2022-06-29 20:23 ` woodard at redhat dot com
2022-06-29 20:39 ` woodard at redhat dot com
2022-06-29 20:45 ` woodard at redhat dot com
2022-06-29 20:52 ` woodard at redhat dot com
2022-07-05 20:10 ` woodard at redhat dot com
2022-07-25 21:26 ` woodard at redhat dot com
2022-07-26 20:04 ` woodard at redhat dot com
2022-07-26 20:07 ` woodard at redhat dot com
2022-07-26 20:11 ` woodard at redhat dot com
2022-10-14 16:00 ` woodard at redhat dot com
2022-10-14 16:03 ` 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-29299-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).