That’s fair, I’m responding more to the general aversion to using -Werror at all than the specific case of the OP. If I were writing open source software expected to be used by a wide variety of compilers and platforms I’d probably also not want to make -Werror the default.
As an anecdote, there may be one or two packages in openwrt that won't build by default because of a strange interaction between certain glibc headers and the behavior of _FORTIFY_SOURCE on some embedded platforms, but only on some versions of gcc.
Werror tends to be placed eagerly pass the buck along to anyone building it, not just CI or developers. I used to feel that Werror was a good thing, but nowadays anything with CI on merge requests will tell me about any warnings, and someone wanting to build the software shouldn't get penalized for having a different build environment: there's a reason they aren't thrown as errors to begin with. Does this make sense?
