On Thu, Apr 05, 2012, Jonathan Ben Avraham wrote about "Re: [YBA] kernel compile errors with GCC >= 4.6": > I don't know how long it has been a default flag in the kernel, but > I understand why it is. You really do want the compilation to stop > and to take a look at what is going on.
When "you" == "Linus Torvalds", I agree. When "you" == "kernel user" or even "developer working on one particular part of the kernel", I don't agree: I don't think that knowing that some obscure part of the kernel which you know nothing about has a variable which is set but not used (!) helps you one iota. It only slows you down - and makes compiling a kernel appear to be a task not to be attempted by mere mortals. > For other projects I think that the Makefile or build system that is > distributed with the project should only use -Werror after checking > that the GCC version is the same as the version used by the > developers for the release. Then why distribute then -Werror at all? Let the developers use -Wall -Werror as part of their tests, and let users compile normally, without -Werror... Just my view... -- Nadav Har'El | Thursday, Apr 5 2012, [email protected] |----------------------------------------- Phone +972-523-790466, ICQ 13349191 |Why do we drive on a parkway and park on http://nadav.harel.org.il |a driveway? _______________________________________________ Linux-il mailing list [email protected] http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
