Package Details: bpftrace-git v0.24.rc0.r180.g57c2b5863-1

Git Clone URL: https://aur.archlinux.org/bpftrace-git.git (read-only, click to copy)
Package Base: bpftrace-git
Description: High-level tracing language for Linux eBPF
Upstream URL: https://github.com/bpftrace/bpftrace
Keywords: bpf tracing
Licenses: Apache-2.0
Conflicts: bpftrace
Provides: bpftrace
Submitter: cippaciong
Maintainer: VorpalWay
Last Packager: VorpalWay
Votes: 4
Popularity: 1.13
First Submitted: 2018-10-10 13:41 (UTC)
Last Updated: 2025-10-19 10:01 (UTC)

Latest Comments

1 2 Next › Last »

VorpalWay commented on 2025-09-03 09:59 (UTC) (edited on 2025-09-03 18:02 (UTC) by VorpalWay)

Well, since nobody else stepped up, I will adopt this. I'll start updating this this weekend. Thanks @cippciaong for your previous maintenance.

One issue is that the current git needs a static libbpf.a, while Arch only packages a shared library currently. I will have to think about how to solve that.

EDIT: I have now updated the package. For now this depends on libbpf-git to work around the missing static library in the official package.

cippaciong commented on 2025-08-24 12:52 (UTC) (edited on 2025-08-24 12:53 (UTC) by cippaciong)

Thanks for the report VorpalWay.

I'm not even sure the dependencies and build scripts are still up to date since I don't use this package anymore. I will disown it so that someone else can step up as maintainer and take proper care of it.

VorpalWay commented on 2025-08-10 06:53 (UTC)

The URL is outdated, it is https://github.com/bpftrace/bpftrace nowadays.

arenm commented on 2022-07-09 18:53 (UTC)

It looks like bpftrace needs gtest as a make dependency

SPYFF commented on 2021-12-28 23:13 (UTC)

Hi! Thanks for the package.

The bpftrace --info show the following:

  libbpf btf dump: no
  libbpf btf dump type decl: no
  btf (depends on Build:libbpf): no

I suggest add libbpf as a dependency and recompile it with that.

tuxsavvy commented on 2021-08-16 15:48 (UTC)

Hi, thanks for maintaining this package. The latest version appears to require asciidoctor, here is a patch for PKGBUILD which rectifies that:

--- PKGBUILD.orig
+++ PKGBUILD
@@ -1,14 +1,14 @@
 # Maintainer: Tommaso Sardelli <lacapannadelloziotom at gmail dot com>
 pkgname=bpftrace-git
 _pkgname=bpftrace
-pkgver=r2315.fd0461dc
+pkgver=r2356.24e1ca2f
 pkgrel=1
 pkgdesc='High-level tracing language for Linux eBPF'
 arch=('i686' 'x86_64')
 url="https://github.com/iovisor/bpftrace"
 license=('Apache')
 depends=('libelf' 'zlib' 'llvm-libs' 'clang' 'bcc')
-makedepends=('cmake' 'git' 'llvm' 'cereal')
+makedepends=('cmake' 'git' 'llvm' 'cereal' 'asciidoctor')
 conflicts=('bpftrace')
 provides=('bpftrace')
 source=("git+https://github.com/iovisor/bpftrace.git")

cippaciong commented on 2021-07-17 20:39 (UTC)

@ludat: updated, thanks :)

ludat commented on 2021-07-15 04:17 (UTC)

bpftrace now needs cereal to build.

ulidtko commented on 2020-07-01 14:36 (UTC)

Cross-posting from the non-git package (which doesn't compile for me atm):

This PKGBUILD needs to disable stripping of the built bpftrace binary.

Because stripping breaks BEGIN/END probes, testcase:

sudo bpftrace -e 'BEGIN { @++ }'
Attaching 1 probe...
Could not resolve symbol: /proc/self/exe:BEGIN_trigger

Patch:

diff --git i/PKGBUILD w/PKGBUILD
index 8529b18..70bb65b 100644
--- i/PKGBUILD
+++ w/PKGBUILD
@@ -13,6 +13,7 @@ conflicts=('bpftrace')
 provides=('bpftrace')
 source=("git+https://github.com/iovisor/bpftrace.git")
 sha512sums=('SKIP')
+options=('!strip') #-- https://github.com/iovisor/bpftrace/issues/954

 pkgver() {
   cd "$srcdir/$_pkgname"

cippaciong commented on 2019-10-27 23:06 (UTC) (edited on 2019-10-27 23:08 (UTC) by cippaciong)

@Jonhoo: thanks for reporting, I can reproduce the issue also for the non -git version of bpftrace but I'm not quite sure what is causing it. My guess is that it might be related to some changes in recent versions of kernel/llvm/bcc since at least the latest release, used to build correctly when I created the PKGBUILD. I will report the issue upstream and see if they can help.

@k3a: Which versions of linux/llvm/bcc do you have on your system? Did you install libbpf as well?

1 2 Next › Last »