[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: --quiet option not carried through to config.status
From: |
Eric Blake |
Subject: |
Re: --quiet option not carried through to config.status |
Date: |
Fri, 02 Jan 2009 06:18:38 -0700 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.19) Gecko/20081209 Thunderbird/2.0.0.19 Mnenhy/0.7.5.666 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Ben Elliston on 1/1/2009 9:20 PM:
> If I configured this tree at the outset with --quiet, this will never be
> recorded in the config.status output and I must remember to append it
> when reconstructing the configure command line. This may well also
> apply to other configure options.
>
> A bug?
Thanks for the report. However, the current behavior is intentional.
While all of the other options are cached (they affect configure results),
we intentionally filter out --quiet (or --silent) because it does not
affect configure results and makes more sense as a per-run option. In
other words, we are catering to the ability to attempt a silent
configuration, but allow the user to rerun a verbose attempt in order to
determine why the silent run misbehaved.
If you truly always want silent runs, then you should write a shell alias
or shell script wrapper.
- --
Don't work too hard, make some time for fun as well!
Eric Blake address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkleFC4ACgkQ84KuGfSFAYAg2ACeOmv0AV9Y+lYMCcsYHTOdgujz
kA0AoM1qzHywGoB3aP/DzqT9tp0Xn73M
=a/OA
-----END PGP SIGNATURE-----