cc/gcc: do not print 'core' or 'final'

In gcc-'s core and final passes, do not print 'core' or 'final' in
log messages. We already print it in step messages.

Also, as we use the core backend to build the bare-metal final gcc,
it can be disturbing to read 'core' while we're in fact in 'final'.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
This commit is contained in:
Yann E. MORIN" 2012-11-25 18:22:38 +01:00
parent fdac362da2
commit 4e9c473337

View File

@ -191,7 +191,7 @@ do_cc_core_backend() {
eval "${arg// /\\ }"
done
CT_DoLog EXTRA "Configuring core C compiler"
CT_DoLog EXTRA "Configuring gcc"
case "${mode}" in
static)
@ -444,10 +444,10 @@ do_cc_core_backend() {
core_targets+=( target-libstdc++-v3 )
fi
CT_DoLog EXTRA "Building core C compiler"
CT_DoLog EXTRA "Building gcc"
CT_DoExecLog ALL make ${JOBSFLAGS} "${core_targets[@]/#/all-}"
CT_DoLog EXTRA "Installing core C compiler"
CT_DoLog EXTRA "Installing gcc"
CT_DoExecLog ALL make ${JOBSFLAGS} "${core_targets[@]/#/install-}"
if [ "${build_manuals}" = "yes" ]; then
@ -590,7 +590,7 @@ do_cc_backend() {
eval "${arg// /\\ }"
done
CT_DoLog EXTRA "Configuring final compiler"
CT_DoLog EXTRA "Configuring gcc"
# Enable selected languages
extra_config+=("--enable-languages=${lang_list}")
@ -809,10 +809,10 @@ do_cc_backend() {
CT_DoExecLog ALL make ${JOBSFLAGS} all-build-libiberty
fi
CT_DoLog EXTRA "Building final compiler"
CT_DoLog EXTRA "Building gcc"
CT_DoExecLog ALL make ${JOBSFLAGS} all
CT_DoLog EXTRA "Installing final compiler"
CT_DoLog EXTRA "Installing gcc"
CT_DoExecLog ALL make ${JOBSFLAGS} install
if [ "${build_manuals}" = "yes" ]; then