From: Ben Hutchings <ben@decadent.org.uk>
To: Alan Modra <amodra@gmail.com>, Romain Naour <romain.naour@smile.fr>
Cc: Hagen Paul Pfeifer <hagen@jauu.net>,
Matthias Klose <doko@debian.org>,
950414@bugs.debian.org, Stephen Rothwell <sfr@canb.auug.org.au>,
Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
binutils <binutils@sourceware.org>,
gdb@sourceware.org, "H.J. Lu" <hjl.tools@gmail.com>,
Nick Clifton <nickc@redhat.com>
Subject: Re: Bug#950414: binutils-dev: failed to build linux perf (tools/perf) due to missing functions
Date: Tue, 04 Feb 2020 23:48:00 -0000 [thread overview]
Message-ID: <09b7173dcfa66a98b1846f48470db9d0e6884b74.camel@decadent.org.uk> (raw)
In-Reply-To: <20200204232933.GU30118@bubble.grove.modra.org>
[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]
On Wed, 2020-02-05 at 09:59 +1030, Alan Modra wrote:
> The binutils and gdb projects do not even pretend to a stable ABI or
> API for libbfd and libopcodes. Particularly not ABI, that gets broken
> on almost every week. perf and other projects that want to use libbfd
> or libopcodes are of course welcome to do so, but they then need to
> deal with the changing API. Complaints that Nick, Alan, or H.J. Lu
> have broken perf or similar *will be ignored*, except possibly to tell
> you that you may as well stop complaining.
>
> I've said before that the most obvious way to deal with the unstable
> API is to import a snapshot of the libbfd and libopcodes code into
> those projects and merge from upstream as new upstream support becomes
> desirable. That's not hard to do!
Maybe they could also relicense perf to be GPLv3 compatible. :-)
Ben.
--
Ben Hutchings
Life is what happens to you while you're busy making other plans.
- John Lennon
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-02-04 23:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200201095306.GD9786@laniakea>
[not found] ` <005fbdf3-a9c6-36d8-c2e8-0d307de5a40d@debian.org>
[not found] ` <20200203210310.GA217509@virgo>
[not found] ` <d91b6b94-c326-b972-483d-f586fb8a0d4b@debian.org>
2020-02-04 15:36 ` Hagen Paul Pfeifer
2020-02-04 22:04 ` Romain Naour
2020-02-04 23:29 ` Alan Modra
2020-02-04 23:48 ` Ben Hutchings [this message]
2020-02-05 8:35 ` Thomas Backlund
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=09b7173dcfa66a98b1846f48470db9d0e6884b74.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=950414@bugs.debian.org \
--cc=amodra@gmail.com \
--cc=arnaldo.melo@gmail.com \
--cc=binutils@sourceware.org \
--cc=doko@debian.org \
--cc=gdb@sourceware.org \
--cc=hagen@jauu.net \
--cc=hjl.tools@gmail.com \
--cc=nickc@redhat.com \
--cc=romain.naour@smile.fr \
--cc=sfr@canb.auug.org.au \
/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