Hi *, from my experience, adding -Werror=* flags causes breakage because way too many configure scripts miss the appropriate headers when probing for symbols, so this wouldn’t lead to build failures but to changed feature sets or the programs using older/fallback APIs (e.g. if probing openat() fails, a program could unconditionally use open in an insecure way as fallback, and the missing header would be there in the site that actually uses it but autoconf generally misses them).
In MirBSD, I’ve worked around this by appending a new flag -Werror-maybe-reset to CFLAGS and CXXFLAGS which has no effect in GCC unless an extra environment variable is set, in which case it does -Wno-error. Then, we set that env during the configure call but not during make all/install. This was achieved with a trivial local GCC patch. I know we already add -Werror=format-security in many cases, but that has less chance to break the configue stage (even so I’d look sceptical at it). bye, //mirabilos -- <hecker> cool ein Ada Lovelace Google-Doodle. aber zum 197. Geburtstag? Hätten die nicht noch 3 Jahre warten können? <mirabilos> bis dahin gibts google nicht mehr <hecker> ja, könnte man meinen. wahrscheinlich ist der angekündigte welt- untergang aus dem maya-kalender die globale abschaltung von google ☺ und darum müssen die die doodles vorher noch raushauen
