Bug #3097
openbuild for eBPF programs needs a way to specify Linux header location
Description
We saw that building eBPF programs on Debian unstable does not work reliably because the include path is specified as /usr/include/$(build_cpu)-$(build_os). Instead, /usr/include/<multiarch-triplet> should be used, but there's no easy, portable way to determine that.
Updated by Hilko Bengen almost 6 years ago
I have a patch ready, but a fix for #2789 should be merged first.
Updated by Andreas Herz almost 6 years ago
- Assignee set to Hilko Bengen
- Target version set to TBD
Updated by Andreas Herz almost 6 years ago
Since it's now merged, will you send us the patch :)?
Updated by Victor Julien almost 6 years ago
- Status changed from New to Assigned
- Target version changed from TBD to 70
Updated by Victor Julien almost 5 years ago
- Target version changed from 70 to TBD
Updated by Philippe Antoine 2 days ago
- Status changed from Assigned to Feedback
Is this still an issue nowadays ? (Suri 8 till uses /usr/include/$(build_cpu)-$(build_os). )
Updated by Hilko Bengen 1 day ago
The Suricata package in Debian still contains my patch that adds a way to pass the include path to the configure script.
Updated by Philippe Antoine about 13 hours ago
Cool, should this patch be merged upstream (in Suricata) ? cc @Sascha Steinbiss ?
Updated by Sascha Steinbiss about 7 hours ago
Philippe Antoine wrote in #note-8:
Cool, should this patch be merged upstream (in Suricata) ? cc @Sascha Steinbiss ?
I think so, it would make something configurable which was previously hard-coded.
However, I feel it should then also be documented how to use it (see https://salsa.debian.org/pkg-suricata-team/pkg-suricata/-/blob/master/debian/rules?ref_type=heads#L46 for how it's used in Debian when building the package on eBPF-enabled platforms).