But in man hardening-check it states: "When an executable was built such that the fortified versions of the glibc functions are not useful (e.g. use is verified as safe at compile time, or use cannot be verified at runtime), this check will lead to false alarms. In an effort to mitigate this, the check will pass if any fortified function is found, and will fail if only unfortified functions are found. Uncheckable conditions also pass (e.g. no functions that c)"
We do nothing special for this file compared to all the others we build and that have no issue.
It is build with -D_FORTIFY_SOURCE=2 and all other usual flags.