Hi Jim, * Jim Meyering wrote on Sun, Apr 19, 2009 at 10:53:40AM CEST: > What if a package maintainer wants to enable > automake's silent-rules option by default?
Then you should argue for this; see the arguments against it here: <http://lists.gnu.org/archive/html/automake/2009-04/msg00019.html> <http://lists.gnu.org/archive/html/automake/2009-04/msg00076.html> <http://lists.gnu.org/archive/html/automake/2009-04/msg00081.html> > Currently, even when I use AM_INIT_AUTOMAKE([silent-rules]) it's > disabled, and to get the behavior I want, I have to run ./configure > --enable-silent-rules or "make V=0". Correct. > Is there a recommended way to make the "make V=0" behavior the default? > Of course, I can do this: > --- a/configure.ac > +++ b/configure.ac > @@ -34,6 +34,9 @@ AC_CONFIG_HEADERS([lib/config.h:lib/config.hin]) > > AM_INIT_AUTOMAKE([1.10b dist-xz color-tests parallel-tests silent-rules]) > > +# I prefer --enable-silent-rules, so make that the default. > +test "x$enable_silent_rules" != xno && AM_DEFAULT_VERBOSITY=0 > + > Perhaps give AM_SILENT_RULES a parameter? > Then I wouldn't have to use "$enable_silent_rules" and > AM_DEFAULT_VERBOSITY. Actually, you can do either of this: 1) # remove `silent-rules' from AM_INIT_AUTOMAKE and add : ${enable_silent_rules=yes} AM_SILENT_RULES 2) # remove `silent-rules' from AM_INIT_AUTOMAKE and add AM_SILENT_RULES([yes]) but the latter is still undocumented, as result of the discussion referenced above. Cheers, Ralf