Your message dated Wed, 19 Jun 2019 14:25:01 +0530
with message-id <[email protected]>
and subject line Re: Bug#930720: Dependency "linux-headers-xyz" missing, needed
for BPF compilation
has caused the Debian Bug report #930720,
regarding Dependency "linux-headers-xyz" missing, needed for BPF compilation
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
930720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930720
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bpfcc-tools
Version: 0.8.0-4
Executing execsnoop-bpfcc (and probably any of the other BCC tools) fails due
to a missing directory (/lib/modules/4.19.0-5-amd64/build) on an up-to-date
Buster system.
Installing 'linux-headers-amd64' (on an AMD64 system) resolved the issue.
This is an example of the reported error.
# execsnoop-bpfcc
chdir(/lib/modules/4.19.0-5-amd64/build): No such file or directory
Traceback (most recent call last):
File "/usr/sbin/execsnoop-bpfcc", line 166, in <module>
b = BPF(text=bpf_text)
File "/usr/lib/python2.7/dist-packages/bcc/__init__.py", line 320, in __init__
raise Exception("Failed to compile BPF text")
Exception: Failed to compile BPF text
--- End Message ---
--- Begin Message ---
Hi Silvano,
This is already documented in the README.Debian file. Hence, closing
this bug report.
rrs@priyasi:/usr/share/doc/bpfcc-tools$ cat README.Debian
Kernel package dependency
=========================
Applications linked against libbpfcc will dynamically compile and
load C source code into eBPF byte code at runtime and load the result
into the kernel for various purposes (e.g. socket filtering, tracing,
etc.).
For this to work, it needs the kernel headers of the currently running
kernel. Therefore, to use BCC you need to manually install the
linux-image-*-dbg and linux-header-* packages that match your running
kernel.
-- Ritesh Raj Sarraf <[email protected]> Wed Oct 18 12:24:24 +0545 2017
On Wed, 2019-06-19 at 08:39 +0000, Cirujano Cuesta, Silvano wrote:
> Package: bpfcc-tools
> Version: 0.8.0-4
>
> Executing execsnoop-bpfcc (and probably any of the other BCC tools)
> fails due to a missing directory (/lib/modules/4.19.0-5-amd64/build)
> on an up-to-date Buster system.
> Installing 'linux-headers-amd64' (on an AMD64 system) resolved the
> issue.
>
> This is an example of the reported error.
>
> # execsnoop-bpfcc
> chdir(/lib/modules/4.19.0-5-amd64/build): No such file or directory
> Traceback (most recent call last):
> File "/usr/sbin/execsnoop-bpfcc", line 166, in <module>
> b = BPF(text=bpf_text)
> File "/usr/lib/python2.7/dist-packages/bcc/__init__.py", line 320,
> in __init__
> raise Exception("Failed to compile BPF text")
> Exception: Failed to compile BPF text
>
>
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
signature.asc
Description: This is a digitally signed message part
--- End Message ---
