Well for one, new compilers add new warnings, so just because -Werror works on gcc-4.2 doesn't mean it will work on gcc-4.3, 4.4, 4.5, 4.6, llvm-gcc, clang, ...
My guess is that this was specifically motivated by clang, which introduces many new warnings that projects trip over. On Aug 12, 2011, at 2:50 PM, Ryan Schmidt wrote: > I see a lot of disabling -Werror going on in ports lately: > > On Aug 12, 2011, at 16:49, j...@macports.org wrote: > >> Revision: 82353 >> http://trac.macports.org/changeset/82353 >> Author: j...@macports.org >> Date: 2011-08-12 14:49:46 -0700 (Fri, 12 Aug 2011) >> Log Message: >> ----------- >> mips-rtems-binutils: disable -Werror > > What's the problem that having -Werror is causing now that it wasn't causing > before? > > > _______________________________________________ > macports-dev mailing list > macports-dev@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev > _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
