mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Quentin Monnet <quentin@isovalent.com>
To: Ian Rogers <irogers@google.com>,
	Anders Roxell <anders.roxell@linaro.org>
Cc: stable@vger.kernel.org, acme@redhat.com, andres@anarazel.de,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	Alexei Starovoitov <ast@kernel.org>,
	Ben Hutchings <benh@debian.org>, Jiri Olsa <jolsa@kernel.org>,
	Sedat Dilek <sedat.dilek@gmail.com>,
	bpf@vger.kernel.org
Subject: Re: [backport PATCH 1/2] tools perf: Fix compilation error with new binutils
Date: Tue, 18 Apr 2023 17:43:01 +0100	[thread overview]
Message-ID: <d940f802-8aab-140d-7a87-9cf0b3a8ac9f@isovalent.com> (raw)
In-Reply-To: <CAP-5=fWUevSnyn5MtVO1p6cEVE8MvBTq4Qgth7RcPYueRERQKA@mail.gmail.com>

2023-04-17 10:14 UTC-0700 ~ Ian Rogers <irogers@google.com>
> On Mon, Apr 17, 2023 at 5:30 AM Anders Roxell <anders.roxell@linaro.org> wrote:
>>
>> From: Andres Freund <andres@anarazel.de>
>>
>> binutils changed the signature of init_disassemble_info(), which now causes
>> compilation failures for tools/perf/util/annotate.c, e.g. on debian
>> unstable.
> 
> Thanks, I believe the compilation issue may well be resolved by:
> https://lore.kernel.org/lkml/20230311065753.3012826-8-irogers@google.com/
> where binutils is made opt-in rather than opt-out.

Hi,
These commits are to make it possible to build against recent binutils,
without having to leave it out at compile time, so as I understand they
address a different issue?

> 
>> Relevant binutils commit:
>>
>>   https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=60a3da00bd5407f07
>>
>> Wire up the feature test and switch to init_disassemble_info_compat(),
>> which were introduced in prior commits, fixing the compilation failure.
> 
> I was kind of surprised to see no version check ifdef. Is
> init_disassemble_info_compat is supported in older binutils?

It is not part of binutils, it was introduced in commit a45b3d692623
("tools include: add dis-asm-compat.h to handle version differences"),
which should likely be backported alongside these ones if it hasn't been
already. Possibly the others from the same series [0], as well?

I think all 5 patches from Andres' series were backported to 5.15 [1].

[0]
https://lore.kernel.org/all/20220703212551.1114923-1-andres@anarazel.de/t/#m999a44663894e235b523ffc41ce87e956019ea72
[1]
https://lore.kernel.org/all/e6e2df31-6327-f2ad-3049-0cbfa214ae5c@hauke-m.de/t/#u

Best regards,
Quentin

  reply	other threads:[~2023-04-18 16:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-17 12:29 [backport PATCH 0/2] stable v5.15, v5.10 and v5.4: fix perf build errors Anders Roxell
2023-04-17 12:29 ` [backport PATCH 1/2] tools perf: Fix compilation error with new binutils Anders Roxell
2023-04-17 17:14   ` Ian Rogers
2023-04-18 16:43     ` Quentin Monnet [this message]
2023-04-18 18:04       ` Ian Rogers
2023-04-17 12:29 ` [backport PATCH 2/2] tools build: Add feature test for init_disassemble_info API changes Anders Roxell
2023-04-17 17:18 ` [backport PATCH 0/2] stable v5.15, v5.10 and v5.4: fix perf build errors Ian Rogers
2023-04-18  9:04 ` Greg KH
2023-04-20 18:24   ` Anders Roxell
2023-04-20 20:34     ` Ian Rogers

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=d940f802-8aab-140d-7a87-9cf0b3a8ac9f@isovalent.com \
    --to=quentin@isovalent.com \
    --cc=acme@redhat.com \
    --cc=anders.roxell@linaro.org \
    --cc=andres@anarazel.de \
    --cc=ast@kernel.org \
    --cc=benh@debian.org \
    --cc=bpf@vger.kernel.org \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=sedat.dilek@gmail.com \
    --cc=stable@vger.kernel.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

all inboxes | Powered by JetHome®