-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't build BPF program on Fedora 40 and Debian 13 (Linux 6.10) #50
Comments
Interesting, I'll test it on Debian 13 and see what's up. Does Debian 13 have 6.10 kernel as a default or did you upgrade the kernel separately? There's a chance that since BCC is somewhat deprecated (in favor to libbpf approach), maybe there's some header/kernel incompatibility, like what I saw on Ubuntu 22.04. My next step is to build v3 based on libbpf (using BTF/CO-RE), this should avoid future kernel/header incompatibility issues, in addition to all the other benefits. |
|
It took a while, but I finally attempted to test on Debian 13. I didn't realize that it's not a GA release yet... there's a good chance that you'd need to separately download & build the latest I saw various issues on Ubuntu 22.04 too (24.04 works ok) - given that Once that's out, it should not have any issues with missing or incompatible headers (even if people are using non-standard kernels that usually come with the distro, etc). I did demo some absolute basics of the new approach (BPF task_iterator, etc) at my talk with Liz Rice a few months ago (the last 10 mins of the video or so): I'm leaving this issue open, in case anyone else with a similar issue ends up coming here. Thanks! |
Just a heads-up, since someone else might run into this:
You can ignore the warnings (
biolatency
shows them too), but I don't understand the problem with the missing struct. It's defined in/usr/src/kernels/6.10.6-200.fc40.x86_64/include/uapi/linux/bpf.h
:Which
/usr/src/kernels/6.10.6-200.fc40.x86_64/include/linux/bpf.h
includes:TL;DR: this fails to build on 6.10:
The text was updated successfully, but these errors were encountered: