Hi,
On Wed, 22 Feb 2017, Dominique Leuenberger / DimStar wrote:
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. I hate to point out the obvious, but:
% egrep 'warning:|error:' logfile
So in fact VERBOSE OFF actually helps you FIND warnings and errors - much better than VERBOSE ON Apart from the dubiosity of having to visually scan log files to find warnings and errors (see above), even if you then find them. What then? You don't have the compiler command line, so you don't know which flags were active and if you want to fix the problem you have to fiddle with the .spec anyway to activate verboseness (in whatever way it needs it). (Well, or of course you randomly do changes and rebuild until the warning/error goes away).
Some build systems get this right and print the compile command line also without verbose if the command resulted in errors or warnings. That's unfortunately the minority. Until that's the rule non-verbose compilation hurts more than it helps.
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. brp works with and without verbosity. If it finds something objectionable you have to do more work when verbose is disabled. Pretty clear what should be the decision in my book.
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. Yeah, sure, and? That's no argument in favor of disabling verbose builds. In fact "it works with both ways" is no argument either way.
Ciao, Michael. I must second the motion, it's nothing to either search for "waiting" in "waiting for unfinished jobs" or "error:" note the colon, to find the reason for the build failure. We're packagers it's part of the (non
On 27/02/2017 15:30, Michael Matz wrote: paying) job. Why have pretty non functional build logs, they are there to be examined. Gcc 7 is due to be released and some of those warnings are going to change to errors. Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org