On Tue, Jan 13, 2015 at 05:11:38PM +0100, Jean-Marc Lasgouttes wrote: > Le 13/01/2015 17:09, Enrico Forestieri a écrit : > >I don't think so, provided that you have a way to override the default > >settings. In any case, the same set of configure options should not > >change the default settings, in general, and this is now almost the case. > >Almost, because previoulsy I was not getting the -Wxxx options and now > >I am getting them. However, I think that this is a corner case, because > >I use --enable-warnings and the meaning of this option seems to have > >changed. It was once used for enabling the "#warning" directives in > >the sources, while now it is used for enabling those options. However, > >I have now switched to --disable-warnings and the output is exactly > >as before ;) > > You don't like warnings?
Recent compilers tend to be too much verbose and anyway give more warnings by default, without the need of encouraging them ;) Most of the time, the warnings are harmless and simply clutter the output with the only result that you risk to not pay attention to the ones that are really dangerous. Typically, this kind of warnings cannot be disabled, so, when I see a warning, I pay attention to it. > Do you have many on cygwin and friends? No, the only irritating one with gcc 4.9 is the unused-local-typedefs one, but that is silenced easily. There are a couple of irritating (and useless) warnings about the redefinition of WINVER when compiling os_win32.ccp with a mingw (cross)compiler, but I do not compile a native Windows version of LyX often enough to feel the need of silencing it ;) -- Enrico
