From 6672410d04e47b3b455b1ca40b7320e65af8fb2c Mon Sep 17 00:00:00 2001 From: Saya Andy Date: Sun, 6 Sep 2026 17:23:50 +0700 Subject: initial commit --- config/no-debug-info.config | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 config/no-debug-info.config (limited to 'config/no-debug-info.config') diff --git a/config/no-debug-info.config b/config/no-debug-info.config new file mode 100644 index 0000000..502fa50 --- /dev/null +++ b/config/no-debug-info.config @@ -0,0 +1,21 @@ +# Config fragment that turns off DWARF and BTF generation. +# +# The package throws the debug info away anyway: the spec sets +# `%global debug_package %{nil}` and installs modules with +# INSTALL_MOD_STRIP=1, so no -debuginfo subpackage is ever produced. +# Compiling it only costs build RAM, disk and time, which is what constrains +# the 6 CPU / 8 GB arm64 builder. +# +# What this gives up: BTF is the one part of the debug info that would have +# shipped, in vmlinux and in the modules. Without it there is no +# /sys/kernel/btf/vmlinux, so eBPF CO-RE tooling (bpftrace, libbpf programs) +# does not work, and CONFIG_BPF_LSM turns itself off because it depends on +# CONFIG_DEBUG_INFO_BTF - which in turn disables systemd unit settings built +# on the BPF LSM, such as RestrictFileSystems=. +CONFIG_DEBUG_INFO_NONE=y +# CONFIG_DEBUG_INFO is not set +# CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT is not set +# CONFIG_DEBUG_INFO_DWARF4 is not set +# CONFIG_DEBUG_INFO_DWARF5 is not set +# CONFIG_DEBUG_INFO_BTF is not set +# CONFIG_DEBUG_INFO_BTF_MODULES is not set -- cgit v1.3.1+17