On Wed, 22 Feb 2017, Dominique Leuenberger / DimStar wrote:
On Wed, 2017-02-22 at 15:44 +0100, Michael Matz wrote:
Hi,
On Wed, 22 Feb 2017, İsmail Dönmez wrote:
Some people rightly complain they don't want verbose logs because it makes reading log files much more complicated.
If people can't be bothered to read long lines then they should perhaps, ..., well, ... not read log files? Log files are a mean to analyze things after the fact, they are not primarily meant to look pretty.
The 'fun' thing: with verbose disable you can actually SEE Warnings in between the wild pool of characters... and Warnings (and Errors) are still printed without VERBOSE.
So in fact VERBOSE OFF actually helps you FIND warnings and errors - much better than VERBOSE ON
brp for example uses said warnings to raised 'portability-issues 64bit', which most commonly is 'implcit declaration'; as WARNINGS are still shown, even on 'silent build', it can still work.
There is, to my knowledge, only one test that fails to operate properly, and that is "build does not use optflags" - The other log scan test work.
Well, then at least for errors the "pretty" machinery should output the verbose command-line as well. It's very annoying and a PITA to not have those when looking to fix stuff in the compiler. You have to figure out _how_ to enable verboseness which differs wildly from package to package. Richard.
Cheers Dominique
--
Richard Biener