Search Criteria
Package Details: bcc-tools-git 0.11.0.dev0+r1564.g3d21000a-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/bcc-git.git (read-only, click to copy) |
---|---|
Package Base: | bcc-git |
Description: | BPF Compiler Collection - Tools - latest git code |
Upstream URL: | https://github.com/iovisor/bcc |
Licenses: | Apache |
Conflicts: | bcc-tools |
Provides: | bcc-tools |
Submitter: | mmlb |
Maintainer: | edh |
Last Packager: | edh |
Votes: | 8 |
Popularity: | 0.87 |
First Submitted: | 2015-09-29 15:09 (UTC) |
Last Updated: | 2024-01-14 18:15 (UTC) |
Dependencies (14)
- bcc-gitAUR
- ethtool (ethtool-gitAUR)
- libedit
- bison (byacc-bisonAUR, bison-gitAUR) (make)
- clang (llvm-rocm-gitAUR, llvm-gitAUR, clang-minimal-gitAUR, clang17-binAUR) (make)
- cmake (cmake-gitAUR) (make)
- flex (flex-gitAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- llvm (llvm-rocm-gitAUR, llvm-gitAUR, llvm-minimal-gitAUR) (make)
- python (python37AUR, python311AUR, python310AUR) (make)
- iperf (iperf-gitAUR) (check)
- netperf (netperf-gitAUR) (check)
- luajit (luajit-2.1-lua52-gitAUR, luajit-gitAUR, luajit-openrestyAUR) (optional) – Lua bindings for BCC
- python-bcc-gitAUR (optional) – Python bindings for BCC
Required by (3)
- bcc-git (requires bcc-tools) (optional)
- pyroscope-bin (requires bcc-tools) (optional)
- system76-scheduler-git (requires bcc-tools)
Latest Comments
1 2 Next › Last »
dmitter commented on 2024-01-15 10:40 (UTC)
Thanks for the quick fix! I can confirm that the new version works fine now on my system.
edh commented on 2024-01-14 18:15 (UTC)
@dmitter Thanks for the report! This should be fixed now :)
dmitter commented on 2024-01-11 07:36 (UTC)
I have Python 3.11 installed on my system. It seems that version checking in Python is stricter now as the installation of this package failed for me with the following message:
i.e. Python rejects the version identifier "0.11.0.r1561.gd272c0b7" as invalid as per their spec (see https://packaging.python.org/en/latest/specifications/version-specifiers/). I could make it work with the following diff:
edh commented on 2019-10-13 10:23 (UTC)
@emanuele-f The C bindings should work just fine in the bcc package. Hence, it is separate from python-bcc.
I agree that not having the tools in the PATH is kind of awkward but there are a number of names which would clash with standard Linux tools. Defining a sensible ordering in the PATH IMHO does not make sense and hence I just stick to what upstream has decided to do.
emanuele-f commented on 2019-10-13 09:58 (UTC)
Why python-bcc-git is optional? Tools will fail with "No module named 'bcc'" if that is not installed. It would also be useful to have the tools in the PATH, I had to check the .pkg.tar.gz contents to locate where the tools are installed.
osandov commented on 2019-08-28 19:02 (UTC)
The provides/conflicts directives should be fixed now. Let me know if anyone runs into issues.
gamanakis commented on 2019-08-28 03:21 (UTC)
Please fix the "provides" directive. Instead of bcc-git it should say bcc, otherwise other packages depending on bcc are broken (e.g. bpftrace).
iamazat commented on 2019-05-11 13:32 (UTC)
Maybe this package should provides bcc?
renyuneyun commented on 2018-07-10 08:47 (UTC)
There is a file clash with postfix because of /usr/share/man/man8/trace.8.gz . Probably this should be handled... (Though I can uninstall postfix for me case.)
edh commented on 2018-02-16 08:29 (UTC)
Thanks for the note. That was just a plain mistake, I indeed meant to direct the message at @osandov.
1 2 Next › Last »