Package Details: bcc 0.5.0-2

Git Clone URL: (read-only)
Package Base: bcc
Description: BPF Compiler Collection - C library and examples
Upstream URL:
Keywords: control eBPF kernel performance tracing
Licenses: Apache
Provides: bcc, libbcc
Submitter: troyengel
Maintainer: edh (eklausmeier)
Last Packager: edh
Votes: 21
Popularity: 1.489149
First Submitted: 2016-01-01 18:37
Last Updated: 2018-02-24 17:56

Latest Comments

edh commented on 2018-02-24 18:01

@cmsigler Thanks!

The checksum was still the one of the original file which was previously shipped with the PKGBUILD and I forgot to update it to reflect the new source of the patch.

I think it is wrong and too cumbersome to rename man pages which clash with other packages. Considering that I introduced the change in the PKGBUILD and upstream explicitly installs them elsewhere I will in this case simply stick to how it was intended to be installed hence I will stop moving man pages around.

cmsigler commented on 2018-02-24 17:27

Sorry, maybe pastebin is less broken:


cmsigler commented on 2018-02-24 17:19

Hi again,

After a little digging, it seems to me like the postfix manpage should probably be trace(5), not trace(8), since trace is a queue subdirectory, not a command. Should an upstream bug be filed? Perhaps that's beyond the scope of this AUR. I mean, human naming collisions happen all the time even if one tries to be careful.

Here's a PKGBUILD patch, WFM, YMMV:

--- PKGBUILD.orig 2018-02-23 06:59:20.000000000 -0500 +++ PKGBUILD 2018-02-24 12:11:10.413947263 -0500 @@ -14,7 +14,7 @@ source=("${pkgname}/archive/v${pkgver}.tar.gz" 'fix_build_issue_for_llvm_5.0.1.patch::') sha512sums=('12de5ef04185dccd0847fc97ae855b386e0c81b545ae497af797667925ebedf97164c17fb99468abae3f87fb3ddfdba5200070f80b3bbcad63c2355497012f0e' - '1c4a453a0663237b1ebebd4fdc60e7f6add8380bf624cfa6dd28e57a73d6db89b0a562c8bcaa788d8d59f69240b574b123d07e1eeb63da3a255d3b5e40c6221b') + 'f518f32584b1f828af5df00972c33e6efc7f4327fd65505156e6dec96e4e2f6e7fafb50fb0855693d586223dce4f6cbf7db34ae252358636decc5dbe7f6121a7')

prepare() { cd "${srcdir}/${pkgbase}-${pkgver}" @@ -69,6 +69,10 @@

cd "${srcdir}/${pkgbase}-${pkgver}/build/man"
make DESTDIR="${pkgdir}" install

+ + # Stupidly rename man page that clashes with trace(8) from extra/postfix + mv -f "${pkgdir}"/usr/share/bcc/man/man8/trace.8 "${pkgdir}"/usr/share/bcc/man/man8/trace-bcc.8 + mv "${pkgdir}"/usr/share/{bcc/man,} }




cmsigler commented on 2018-02-24 16:19


sha512sum is incorrect for fix_build_issue_for_llvm_5.0.1.patch. As of this moment I find it to be:


There's also a problem with bcc-tools. A man page /usr/share/man/man8/trace.8.gz installed by postfix 3.3.0-1 clashes with an identical name in the .pkg.tar.xz generated for bcc-tools. I'll try to patch this locally and if I have success I'll post my patch.



edh commented on 2018-02-15 23:10

I recently adopted the package and will try to maintain it in the future as good as possible. The very recent commit first of all update the package to v0.5.0 and basically overhauls the entire PKGBUILD. In addition to slight cosmetic changes I altered the following:

  • Patch cmake configuration using a git-commit from master

  • Move man pages into the "correct" place (but not the binaries)

  • Adjust architecture field for arch-independent packages like python bindings and scripting tools

  • Cleanup build directory handling

  • Add dependencies required for checking the package to checkdepends (checking is done while building; there is no separate check task)

  • Remove outdated patch concerning cppex

Please let me know whether you have any addition request or recommendations!

cippaciong commented on 2018-02-15 15:47

I have used v0.4.0 and now I'm using v0.5.0 without particular problems on arch. There is an open issue at with PKGBUILDs for both versions.

P.S. thanks edh for stepping up maintaining this package

cramaker commented on 2018-02-15 15:40

Any chance we could get this updated to the v0.5.0 release?

troyengel commented on 2017-08-10 18:37

Heya all, I just lack time and effort to maintain these packages - I'm going to disown them so another can pick up next. Be careful pushing a new release, apparently there's a clang/llvm bug (according to upstream) that causes everything to segfault - if you have an older compiled version installed, don't upgrade until that's fixed. (

cc: bcc, bcc-git packages

lilydjwg commented on 2017-08-08 15:08

The manpages are in the wrong place: it's under /usr/share/bcc/man/ and man can't find them. They should be in /usr/share/man/.

troyengel commented on 2017-08-01 23:01

@edrex thanks for the heads up, I have subscribed to the Github issue. Let's see what happens - maybe a patch, maybe a new version release...

All comments