On Wed, Aug 20, 2014 at 01:43:59AM +0200, Andi Kleen wrote: > On Tue, Aug 19, 2014 at 10:11:30PM +0200, Sam Ravnborg wrote: > > On Tue, Aug 19, 2014 at 06:15:07AM -0700, Andi Kleen wrote: > > > Brian Norris <computersforpeace@xxxxxxxxx> writes: > > > > > > > > 4. better ideas? > > > > > > Just send patches to remove -Werror in all architectures > > > as a tree sweep (and anywhere else where someone misguided add it) > > In arch/sparc/ we have -Werror and this has never troubled us. > > In fact more than once people had tried to provide sloppy code that > > failed due to -Werror so it got fixed up front. > > It's a major mistake to not support future gccs for released source. Until now this has not been an issue - for the sparc bits. If newer gcc's turn out to give legit warnings then if someone provides a little help (configure command-line to build gcc) the warnings will be fixed. And that should hold true for any decent maintained piece of SW. If the intent is to use bleeding edge gcc then -Werrror can be annoying and the right fix would be to make it possible to diable it on the command-line. Sam -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
