From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/linux-tools: perf: explicitly disable BPF skeletons
Date: Sun, 1 Nov 2026 23:43:07 +0100 [thread overview]
Message-ID: <aufAd2rZ3prNBYhi@windsurf> (raw)
In-Reply-To: <20261030222648.270223-1-yegorslists@gmail.com>
On Fri, Oct 30, 2026 at 11:26:48PM +0100, Yegor Yefremov via buildroot wrote:
> From: Yegor Yefremov <yegorslists@googlemail.com>
>
> perf builds its BPF skeletons by default whenever libelf, zlib, libbpf
> and openssl support are enabled and a clang >= 12.0.1 is found in the
> PATH. That clang is the host's one, and it compiles the BPF programs
> against the host's system headers, so the build fails (here with
> linux 7.2.6 on ARM and Ubuntu's clang 21.1.8):
>
> /usr/include/linux/ioctl.h:5:10: fatal error: 'asm/ioctl.h' file not found
> make[6]: *** [.../tools/perf/bpf_skel.mak:87: .../tools/perf/util/bpf_skel/.tmp/bpf_prog_profiler.bpf.o] Error 1
>
> Without clang on the host, perf silently disables them, so whether the
> build works depends on the build machine.
>
> The perf tool does not depend on host-clang, so always pass
> BUILD_BPF_SKEL=0 rather than let the host's clang be picked up.
>
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
Applied to master, thanks!
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-11-01 22:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 22:26 [Buildroot] [PATCH] package/linux-tools: perf: explicitly disable BPF skeletons Yegor Yefremov via buildroot
2026-11-01 22:43 ` Thomas Petazzoni via buildroot [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=aufAd2rZ3prNBYhi@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=yegorslists@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.