-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 15/04/15 14:07, Gert Doering wrote:
> Hi,
> 
> On Wed, Apr 15, 2015 at 09:19:45AM +0200, Matthias Andree wrote:
>> - it changes policy through the [yes] argument to
>> AM_SILENT_RULES(). This flips the switch for the default without
>> good reason, and that makes debugging harder - this is a policy
>> decision, not mechanism.
> 
> Indeed, this we don't want.
> 
> Having "V=0" or "--enable-silent-rules" is fine for me, but
> changing the defaults to hide even more detail is not (annoying
> enough that recent autoconfs hide the detailed results from "make
> test")

Just tested a ./configure (used automake 1.13.4 on RHEL7) with
- --enable-silent-rules.  That worked like a charm out-of-the-box
without any patching.

I do understand people wanting less output when compiling (which has
been a Linux kernel compile feature for a very long time too, and many
other projects as well).  And I don't think that we loose that much
information building it this way.  In fact we can actually more easily
see compiler warnings - which I would say is a good thing.  If you
need the full compile command line, it is available using 'V=1'.

But I don't think we should make this behaviour the default yet, and
at least not if that require dependencies to specific automake
versions, especially when we know that RHEL5 (the oldest supported
distro) runs a far older automake.  I think it is best if the default
behaviour is consistent across all distributions.

Having this said, if you do builds on systems with a more modern
automake, I do want to encourage people to run 'make V=0' or use
./configure --enable-silent-rules.  This will ensure we can capture
compiler warnings far easier.  For now I do consider this fine, as you
do this explicitly - a different behaviour should be expected when
using explicit options.

When the oldest distro we need to support have a modern enough
automake, we should revisit this topic of making the 'silent rules'
the default behaviour - being consistent across all distros.


- -- 
kind regards,

David Sommerseth
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEARECAAYFAlU+TEYACgkQDC186MBRfroooACgrl7YapqCtq4NbtNAGRogEHpn
2zUAnRnyLDgDVMYzXF5DCXEy/ds583yL
=QNhv
-----END PGP SIGNATURE-----

Reply via email to