On Tuesday, October 04, 2011 03:20:10 Ulrich Drepper wrote: > If it's not tested it shouldn't be released. Your thinking is > completely backward.
you missed the point completely. there's no way you're going to build
elfutils across gcc-4.{4,5,6,7,+} and glibc-2.{11,12,13,14,+} over a variety
of architectures, compiler optimizations, and configure options. expecting
that kind of coverage is completely unrealistic, and i already know there are
a bunch of architectures you'd refuse to bother with.
distributions however do build over these array of configurations, and the
vast majority of warnings arising from the build are simply irrelevant noise.
applying patches to distros to address new warnings is a complete waste of
time. e.x. gcc-4.6 includes much better warnings like -Wunused-but-set-
variable which have absolutely no bearing on the generated code.
if your logic were actually true, i would wonder why significantly more
relevant projects like binutils or gdb or gcc include --disable-werror
configure flags.
-mike
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ elfutils-devel mailing list [email protected] https://fedorahosted.org/mailman/listinfo/elfutils-devel
