This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
a contentious configure idea: --quiet
- From: Ben Elliston <bje at au1 dot ibm dot com>
- To: gcc at gcc dot gnu dot org
- Date: 02 Apr 2004 15:53:54 +1000
- Subject: a contentious configure idea: --quiet
At present, top-level configure.in has:
baseargs="$baseargs --program-transform-name='${gcc_transform_name}'"
build_configargs="--cache-file=../config.cache --build=${build_alias} --host=${build_alias} ${baseargs}"
host_configargs="--cache-file=./config.cache --build=${build_alias} --host=${host_alias} --target=${target_alias} ${extra_host_args} ${baseargs}"
target_configargs=${baseargs}
When building the compiler with make -j, configure output is
effectively useless: the messages are interleaved and fly by much too
fast to read. If configure ever fails, one always consults
config.log, not the terminal output, for details.
In my local tree, I've added --quiet to `baseargs' above and it seems
to be a useful change. Is this something that might be universally
accepted? At the very least, adding --quiet to $target_configargs
means that configuring the target libraries won't generate reams of
noise on multilib targets. Opinions?
Ben