From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 114490 invoked by alias); 5 Feb 2020 08:35:57 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 114464 invoked by uid 89); 5 Feb 2020 08:35:57 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy= X-HELO: mx1.yrkesakademin.fi Received: from mx1.yrkesakademin.fi (HELO mx1.yrkesakademin.fi) (85.134.45.194) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 05 Feb 2020 08:35:54 +0000 Subject: Re: Bug#950414: binutils-dev: failed to build linux perf (tools/perf) due to missing functions To: Alan Modra , Romain Naour CC: Hagen Paul Pfeifer , Matthias Klose , <950414@bugs.debian.org>, Ben Hutchings , Stephen Rothwell , Arnaldo Carvalho de Melo , binutils , , "H.J. Lu" , Nick Clifton References: <20200201095306.GD9786@laniakea> <005fbdf3-a9c6-36d8-c2e8-0d307de5a40d@debian.org> <20200203210310.GA217509@virgo> <20200204153557.GA280113@virgo> <20200204232933.GU30118@bubble.grove.modra.org> From: Thomas Backlund Message-ID: <823b4aa7-c638-e3b7-33a7-beff29467c88@mageia.org> Date: Wed, 05 Feb 2020 08:35:00 -0000 MIME-Version: 1.0 In-Reply-To: <20200204232933.GU30118@bubble.grove.modra.org> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2020-02/txt/msg00019.txt.bz2 Den 5.2.2020 kl. 01:29, skrev Alan Modra: > 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! > Yeah, it broke various bits for us too, but then again ... The breakage is basically a variant of: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/Documentation/process/stable-api-nonsense.rst What goes around comes around :) Now we just need fixes all over :) -- Thomas