There has been plenty of times where I've been forced to mangle Makefiles because the developer had -Wall -Werror in their Makefiles, and built with an older/different/odder version of GCC/compiler-of-choice than what we did, and thereby causing a ton of failures.
Compilers become pickier. When you release a piece of software to the wild, -Wall and -Werror do not belong in the sources, as two months later, your tarball will fail to build against the current cvs version of GCC, because it suddenly warns in -Wall that you don't have your commas aligned vertically with your paranthesis, so the smileys turn the wrong way.
( Or similar . )
The point is, be strict when debugging and developing, be lenient to downstream, don't force downstream to patch Makefiles, configure files and similar just because you ship with -Wall -Werror -D_FAIL_ON_GLIBC22
Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds