Something is killing my Koji build

[Simo Sorce]

On Sat, 2013-01-12 at 18:14 +0100, Kevin Kofler wrote:
> Ralf Corsepius wrote:
> > Well, I am very opposed to silent makerules.
> 
> I like them. :-) By the way, CMake has had them for way longer than the 
> autotools and they have always been the default in CMake (but we default RPM 
> builds (and only RPM builds, in the %cmake and %cmake_kde4 RPM macros) to 
> enable verbose mode by default now).
> 
> > All silent-makerules are doing is to span a hidden mine-field of bugs to
> > trap users into.
> > 
> > E.g. are you sure your include paths and the defines your packages are
> > using are correct? With silent makerules, you and your users won't
> > notice them being wrong - building only appears to be working, while you
> > package actually is totally misconfigured.
> 
> Those automatically generated compiler command lines tend to be very long, I 
> doubt most developers actually read them, ever. All they do is burying 
> important warnings (e.g. "cast to pointer from integer of different size") 
> under a flood of non-error/warning lines, thus increasing the chance of the 
> warnings getting missed. In fact, I dislike even the fact that we're 
> required to use verbose mode for package builds, exactly for that reason. It 
> makes build.log a lot larger (multiple MiB!) and a lot less useful.

+1
verbose mode should be used only when debugging a build privately

Simo.

-- 
Simo Sorce * Red Hat, Inc * New York