[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAP-5=fXX5RUgoXR2v4YPYQWJi=A1LejJ-MfhKqe+es+SR3WyyQ@mail.gmail.com>
Date: Wed, 31 Jul 2024 10:35:12 -0700
From: Ian Rogers <irogers@...gle.com>
To: Namhyung Kim <namhyung@...nel.org>, Arnaldo Carvalho de Melo <acme@...nel.org>,
linux-perf-users <linux-perf-users@...r.kernel.org>
Cc: Song Liu <song@...nel.org>, Adrian Hunter <adrian.hunter@...el.com>,
Jiri Olsa <jolsa@...nel.org>, Kan Liang <kan.liang@...ux.intel.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/1] perf bpf: Move BPF disassembly routines to separate
file to avoid clash with capstone bpf headers
On Wed, Jul 31, 2024 at 10:08 AM Namhyung Kim <namhyung@...nel.org> wrote:
>
> On Wed, Jul 31, 2024 at 8:12 AM Arnaldo Carvalho de Melo
> <acme@...nel.org> wrote:
[snip]
> > +perf-util-y += disasm_bpf.o
>
> I think this can be gated by LIBBFD and LIBBPF config, but not sure
> it can express the both requirements easily.
Should we gate things on libbfd? Given we can't distribute a binary
linked against it, I support deleting all libbfd support. Fixes like
this show the pain in carrying it.
Thanks,
Ian
Powered by blists - more mailing lists