The iovisor packages do declare they provide the Ubuntu packages and as such may be used to satisfy dependencies. Should one choose to use Ubuntu's packages instead of the upstream iovisor packages (or vice-versa), the conflicting packages will need to be removed. Note: the Ubuntu packages have different names but the package contents, in most cases, conflict and as such cannot be installed alongside upstream packages. The tools are installed in /sbin ( /usr/sbin in Ubuntu 18.04) with a -bpfcc extension. sudo apt - get install bpfcc - tools linux - headers - $ ( uname - r ) Ubuntu Packages Source packages and the binary packages produced from them can be found at.

iovisor - BCC GitHub Issues Currently, building from source is currently the only way to get up to date packaged version of bcc.bpfcc-tools).Ĭurrently, BCC packages for both the Ubuntu Universe, and the iovisor builds are outdated. bcc-tools), Ubuntu packages use bpfcc (e.g. The Ubuntu packages have slightly different names: where iovisor packages use bcc in the name (e.g. Versions of bcc are available in the standard Ubuntu Universe repository, as well in iovisor's PPA. Packages Debian - Binaryīcc and its tools are available in the standard Debian main repository, from the source package bpfcc under the names bpfcc-tools, python-bpfcc, libbpfcc and libbpfcc-dev. Kernel compile flags can usually be checked by looking at /proc/config.gz or /boot/config. There are a few optional kernel flags needed for running bcc networking examples on vanilla kernel: CONFIG_NET_SCH_SFQ=m # Need kernel headers through /sys/kernel/ In addition, the kernel should have been compiled with the following flags set: CONFIG_BPF=y In general, to use these features, a Linux kernel version 4.1 or newer is required.

Install Build Essential Fedora