All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org, Qais Yousef <qais.yousef@arm.com>,
	Romain Naour <romain.naour@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/bpftrace: bump version to 0.25.1
Date: Tue, 21 Apr 2026 22:23:44 +0200	[thread overview]
Message-ID: <1e18ca8becb9c20a5e6f2f2e73c0a084@free.fr> (raw)
In-Reply-To: <20260420184450.3781485-1-bernd@kuhls.net>

Hi Bernd,

Thanks for the patch.

On 20/04/2026 20:44, Bernd Kuhls wrote:
> https://github.com/bpftrace/bpftrace/blob/v0.25.1/CHANGELOG.md
> 
> Added configure option USE_SYSTEM_LIBBPF to use our libbpf package,
> needed due to upstream commit
> https://github.com/bpftrace/bpftrace/commit/6d53738627d4f80c83f799f9e042f6bdd373a433
> which was added to version 0.25.0.
> 
> This bump includes upstream commit
> https://github.com/bpftrace/bpftrace/commit/c6442cde6e45945e3cfd72cb2fdbcca590454d0c
> which adds support for LLVM 22 and fixes build errors introduced by
> buildroot commit 25cb3813e7fc6ed3e455f983cf0e09c7bc02fccb.
> 
> Fixes:
> https://autobuild.buildroot.net/results/599/59920f909d808911ea2710938271ecfab48c367f/
> 
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> ---
>  package/bpftrace/bpftrace.hash | 2 +-
>  package/bpftrace/bpftrace.mk   | 5 +++--
>  2 files changed, 4 insertions(+), 3 deletions(-)
[...]
> diff --git a/package/bpftrace/bpftrace.mk 
> b/package/bpftrace/bpftrace.mk
> index 7b1b41781a..e32798cb83 100644
> --- a/package/bpftrace/bpftrace.mk
> +++ b/package/bpftrace/bpftrace.mk
> @@ -4,7 +4,7 @@
>  #
>  
> ################################################################################
> 
> -BPFTRACE_VERSION = 0.24.2
> +BPFTRACE_VERSION = 0.25.1

When trying to compile this new version on a aarch64 config,
the compilation fails with:

/buildroot/output/build/bpftrace-0.25.1/src/bpffeature.cpp:463:41: 
error: ‘BPF_TRACE_KPROBE_SESSION’ was not declared in this scope

So either it should use the definition from the kernel header,
introduced in v6.10:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=535a3692ba7245792e6f23654507865d4293c850

or it should use the definition included from libbpf, and there is
a problem with it. Maybe our libbpf is too old.

Could you have a look please?

>  BPFTRACE_SITE = $(call github,bpftrace,bpftrace,v$(BPFTRACE_VERSION))
>  BPFTRACE_LICENSE = Apache-2.0
>  BPFTRACE_LICENSE_FILES = LICENSE
> @@ -30,6 +30,7 @@ BPFTRACE_CONF_OPTS += \
>  	-DBUILD_TESTING:BOOL=OFF \
>  	-DENABLE_MAN:BOOL=OFF \
>  	-DINSTALL_TOOL_DOCS:BOOL=OFF \
> -	-DUSE_SYSTEM_BPF_BCC:BOOL=ON
> +	-DUSE_SYSTEM_BPF_BCC:BOOL=ON \
> +	-DUSE_SYSTEM_LIBBPF:BOOL=ON
> 
>  $(eval $(cmake-package))
> --
> 2.47.3

Best regards,

Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2026-04-21 20:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-20 18:44 [Buildroot] [PATCH 1/1] package/bpftrace: bump version to 0.25.1 Bernd Kuhls
2026-04-21 20:23 ` Julien Olivain 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=1e18ca8becb9c20a5e6f2f2e73c0a084@free.fr \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=ju.o@free.fr \
    --cc=qais.yousef@arm.com \
    --cc=romain.naour@gmail.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.