-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 27.04.2015 um 16:48 schrieb David Sommerseth: > 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.
The question is who needs what information. I see the dichotomy as follows: - - Whilst operating on known terrain, as a developer, you can often ignore compiler command-lines because you usually are acquainted with what you're doing (and if not, it's time for sleep, sport, or food). That's "make -sj10 V=0" ground. - - Whilst providing end-user builds, perhaps through automated package builders, you do want verbose information, in order to avoid round-trips for asking further questions. Some build frameworks trigger verbose builds automatically, other's don't. (And if you flip the switch for default behaviour, I expect to see other consumers/end users show up and complain.) HTH Matthias -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlU+eM4ACgkQvmGDOQUufZXmeQCfZzULHSU1evIzOvFp+os7Fdro 7wMAoOzFI6g9h9tREL/RgNkWnsypiO6I =3HdT -----END PGP SIGNATURE-----
