That file is specially compiled using a different set of flags. This
is done deliberately, and is not an issue. You can squelch the false
positive using an appropriate stanza in debian/rules, to issue a
command in the log that tells blhc to stand down. Like this:
execute_before_dh_auto_build:
On Wed, Aug 18, 2021 at 2:08 AM Hideki Yamane wrote:
> blhc test on salsa-ci fails as below but it seems that blhc's fault
> to me. How can I avoid this failure?
It looks correct to me, -D_FORTIFY_SOURCE=2 is indeed missing from the
c++ command-line. The standard build command for C++ programs
2 matches
Mail list logo
