Closed SparkyBluefang closed 1 week ago
The context here is https://clang.llvm.org/docs/AttributeReference.html#format and note that clang handles format functions a bit differently. It checks to see whether your function matches up with the function your function calls.
Also, to be clear, in light of the previous build flag issue I filed, and the kerfuffle it triggered:
-Werror=format-nonliteral
is not a Gentoo default, nor is it planned to be, and would only come from an end-user customizing their build configurations.
More particularly, it can happen if the user compiles with CC=clang and meson setup -Dbuildtype=release -Dwerror=true
.
The werror=true is important because while the muffin meson.build
adds format-nonliteral as a default warning it is just that: a warning.
Closed as not planned.
Distribution
Gentoo
Package version
6.2.0
Graphics hardware in use
No response
Frequency
Always
Bug description
Downstream build failure reported on clang builds using
-Werror=format-nonliteral
, going all the way back to mutter 5.4.0 and still reproducible on 6.2.0.https://bugs.gentoo.org/832474
Full 5.4.0 build log muffin-5.2.0-build.log
Excerpt from 6.2.0 build log
I don't have a clang system, so I can't reproduce or provide a complete modern build log. I also don't know if this is reproducible with mutter, but I don't see any Gentoo or Gnome bug reports.
Steps to reproduce
Build with clang and
-Werror=format-nonliteral
Expected behavior
Build completes successfully.
Additional information
No response