From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: James Clark <james.clark@linaro.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>, Leo Yan <leo.yan@arm.com>,
Justin Stitt <justinstitt@google.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Roberto Sassu <roberto.sassu@huawei.com>,
Alexei Starovoitov <ast@kernel.org>,
Andres Freund <andres@anarazel.de>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Nick Terrell <terrelln@fb.com>, Song Liu <song@kernel.org>,
bpf@vger.kernel.org, llvm@lists.linux.dev,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Quentin Monnet <qmo@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>
Subject: Re: [PATCH 0/5] perf build: nondistro build tidyups
Date: Tue, 6 Jan 2026 19:18:27 -0300 [thread overview]
Message-ID: <aV2KM5yEAoLWT8rx@x1> (raw)
In-Reply-To: <20251223-james-libbfd-feat-check-v1-0-0e901ba32ed9@linaro.org>
On Tue, Dec 23, 2025 at 05:00:23PM +0000, James Clark wrote:
> nondistro builds now require a specific version of libbfd, so this adds
> an error when doing an explicit BUILD_NONDISTRO build and some other
> related tidyups.
>
> I'm not sure if the intention is to skip build-tests if something is
> missing, but I see it was done for libbpf versions, so I added the same
> for libbfd. This is the main thing that I hit, that build-test all of a
> sudden stopped working for me.
>
> The first commit is also a cherry pick of an old commit that seemed to
> have been accidentally reverted in the unrelated change linked in the
> trailers.
Thanks, applied to perf-tools-next,
- Arnaldo
> ---
> James Clark (4):
> perf build: Do all non-distro feature checks in one go
> perf build: Remove unused libbfd-buildid feature test
> perf build: Feature test for libbfd thread safety API
> perf build: Skip nondistro build test if libbfd is old
>
> Roberto Sassu (1):
> perf build: Remove FEATURE_CHECK_LDFLAGS-disassembler-{four-args,init-styled} setting
>
> tools/build/Makefile.feature | 2 +-
> tools/build/feature/Makefile | 4 +--
> tools/build/feature/test-libbfd-buildid.c | 8 -----
> tools/build/feature/test-libbfd-threadsafe.c | 18 ++++++++++
> tools/perf/Makefile.config | 54 ++++++++++------------------
> tools/perf/tests/make | 5 +++
> 6 files changed, 45 insertions(+), 46 deletions(-)
> ---
> base-commit: cbd41c6d4c26c161a2b0e70ad411d3885ff13507
> change-id: 20251223-james-libbfd-feat-check-e0cd09d2c1e1
>
> Best regards,
> --
> James Clark <james.clark@linaro.org>
prev parent reply other threads:[~2026-01-06 22:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 17:00 [PATCH 0/5] perf build: nondistro build tidyups James Clark
2025-12-23 17:00 ` [PATCH 1/5] perf build: Remove FEATURE_CHECK_LDFLAGS-disassembler-{four-args,init-styled} setting James Clark
2025-12-23 17:00 ` [PATCH 2/5] perf build: Do all non-distro feature checks in one go James Clark
2025-12-23 17:00 ` [PATCH 3/5] perf build: Remove unused libbfd-buildid feature test James Clark
2025-12-23 17:00 ` [PATCH 4/5] perf build: Feature test for libbfd thread safety API James Clark
2025-12-23 17:00 ` [PATCH 5/5] perf build: Skip nondistro build test if libbfd is old James Clark
2026-01-06 22:18 ` Arnaldo Carvalho de Melo [this message]
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=aV2KM5yEAoLWT8rx@x1 \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=andres@anarazel.de \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=justinstitt@google.com \
--cc=kpsingh@kernel.org \
--cc=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=martin.lau@linux.dev \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=namhyung@kernel.org \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=peterz@infradead.org \
--cc=qmo@kernel.org \
--cc=roberto.sassu@huawei.com \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=terrelln@fb.com \
/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