Package: blhc X-Debbugs-Cc: car...@debian.org, aquilamac...@riseup.net Version: 0.13-5 Severity: normal
Dear Maintainer, I am writing to report an issue that has been observed during the Salsa CI process for Debian Bookworm and older releases. The problem arises when checking for stack clash protection (-fstack-clash-protection) and branch protection (amd64: -fcf-protection, arm64: -mbranch-protection=standard). These checks were requested by Emanuele Rocca (Debian Bug #1050909 and #1050912). The issue manifests as a compilation error. For instance, you can see the error in this job: https://salsa.debian.org/kernel-team/linux/-/jobs/5496461. The issue was first noticed by @carnil during a routine check. The error message indicates that the CFLAGS are missing (-fstack-clash-protection -fcf-protection). The ${RELEASE} variable in the context of this issue refers to the specific Debian release being used during the Salsa CI process. One potential solution that has been considered is to ensure that blhc:${RELEASE} correctly handles the flags for each release. This approach could alleviate the compilation errors and ensure consistency across different Debian releases. For more details, you can check the issue in the Salsa CI repository at https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/340 Before proceeding with any changes, I would appreciate your input on this matter. Specifically, do you think it would be sensible to use blhc from each release? Your insights would be greatly appreciated. Cheers,
