Package Details: bcc-tools 0.12.0-1

Git Clone URL: (read-only, click to copy)
Package Base: bcc
Description: BPF Compiler Collection - Tools
Upstream URL:
Keywords: control eBPF kernel performance tracing
Licenses: Apache
Submitter: troyengel
Maintainer: edh (eklausmeier)
Last Packager: edh
Votes: 34
Popularity: 4.31
First Submitted: 2016-01-01 18:37
Last Updated: 2020-01-11 12:34

Dependencies (13)

Required by (1)

  • bcc (optional)

Sources (2)

Latest Comments

1 2 3 4 5 6 Next › Last »

edh commented on 2019-11-07 13:33

@sam-lunt Fixed. Thanks! However, I think there once was a package with this name but the installation guide as of now just references netaddr so either way dropping the 2 is correct.

sam-lunt commented on 2019-11-07 04:15

Looks like there's a typo in one of the optional dependencies: it should be python-netaddr, not python-netaddr2

edh commented on 2019-10-23 19:30

@hexchain Seems like a reasonable suggestion. Done.

hexchain commented on 2019-10-23 11:30

Is it better to make this package optionally depend on linux-headers? For those who don't have the vanilla kernel, there is no point in having the vanilla headers installed.

edh commented on 2019-06-08 08:10


Please see the Pacman documentation to get a list of files which are installed by a package. Hint, you will have to use -Ql and will find that they are in usr/share/bcc/tools. athe functionality and usage of the tools is described in the GitHub repository.

kbumsik commented on 2019-06-08 07:27

So where are bcc-tools located? How can I call those?

edh commented on 2019-05-29 14:50


I was just blindly pushing an update. I will fix it very soon. Sorry!

egrupled commented on 2019-05-29 11:52

@edh build fails to me with:

==> Starting prepare()...

mv: cannot stat '/build/bcc/src/libbpf-59a6415/*': No such file or directory

The problem is that you used short commit here: but after unpacking libbpf archive the directory has full commit in name.

egrupled commented on 2019-03-15 12:48


edh commented on 2019-03-15 12:47

@egrupled Sure, good catch! I happen to do this for libbpf in the very next line but apparently never bothered to fix the name of the main source file. Thanks! Btw. I refrained from increasing the pacakge-release pkgrel as the package itself will not change.