From: Michael Tretter <m.tretter@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Michael Tretter <m.tretter@pengutronix.de>
Subject: [ptxdist] [PATCH 2/2] kernel/perf: enable zstd support
Date: Mon, 17 Mar 2025 12:31:46 +0100 [thread overview]
Message-ID: <20250317113146.1862763-2-m.tretter@pengutronix.de> (raw)
In-Reply-To: <20250317113146.1862763-1-m.tretter@pengutronix.de>
The Linux kernel Commit 44b44ffd5dce ("perf build: Minor improvement for
linking libzstd") adds a test if libzstd is installed and uses this as
heuristic if libelf is build with zstd support. Thus, if zstd is
installed, perf cannot be built without zstd support anymore.
Always build perf with zstd support and make sure that libelf is built
with zstd, too.
Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
---
rules/kernel.in | 1 +
rules/kernel.make | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/rules/kernel.in b/rules/kernel.in
index 46c2267b6df3..488b08e25016 100644
--- a/rules/kernel.in
+++ b/rules/kernel.in
@@ -3,6 +3,7 @@
menuconfig KERNEL
bool "kernel tools "
select LIBELF if KERNEL_TOOL_PERF
+ select LIBELF_ZSTD if KERNEL_TOOL_PERF
select LIBELF_LIBDW if KERNEL_TOOL_PERF
select SLANG if KERNEL_TOOL_PERF
select BINUTILS if KERNEL_TOOL_PERF
diff --git a/rules/kernel.make b/rules/kernel.make
index f38661301d91..19b05811def2 100644
--- a/rules/kernel.make
+++ b/rules/kernel.make
@@ -229,7 +229,7 @@ KERNEL_TOOL_PERF_OPTS := \
NO_ZLIB= \
NO_LIBBABELTRACE=1 \
NO_LZMA=1 \
- NO_LIBZSTD=1 \
+ NO_LIBZSTD= \
NO_AUXTRACE= \
NO_LIBBPF=1 \
NO_SDT=1 \
--
2.39.5
prev parent reply other threads:[~2025-03-17 11:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 11:31 [ptxdist] [PATCH 1/2] libelf: add option for " Michael Tretter
2025-03-17 11:31 ` Michael Tretter [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=20250317113146.1862763-2-m.tretter@pengutronix.de \
--to=m.tretter@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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