I have sent a follow-up here: https://lists.ubuntu.com/archives/kernel- team/2024-August/153006.html
The equivalent debian package ships an empty stub header rather than disabling the package completely, as it's easier to handle for everyone, and can be changed once BTF for armhf starts working: https://salsa.debian.org/kernel-team/linux/-/commit/ac6f7eda4c3e8b0d0db20ad4bb8236371cf8d38e I have used the same approach here for consistency ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2050083 Title: generate and ship vmlinux.h to allow packages to build BPF CO-RE Status in linux package in Ubuntu: In Progress Bug description: A vmlinux.h header generated from a kernel build with bpftool is needed to build and ship BPF CO-RE programs. We are looking to ship these in the next version of systemd. vmlinux.h being generated depends on the kernel version, architecture and kconfig. There are some vague promises of backward compatibility, but it is hard to gauge. We definitely do not want this file to be generated from the kernel running the build machine when building a package though, as very often these are very old and stable kernels building packages for the bleeding edge. In Fedora and now Debian we generate vmlinux.h at kernel package build time, and ship it with the other kernel headers (_not_ UAPI, the internal headers): https://salsa.debian.org/kernel- team/linux/-/commit/ac6f7eda4c3e8b0d0db20ad4bb8236371cf8d38e Please consider doing the same in Ubuntu's linux-headers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2050083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
