scripts, cc/gcc: do not fail on existing symlinks or build.log

If the user builds a toolchain over an existing one, so, without removing
CT_PREFIX_DIR, the build fails as the symlinks already exist, as does the
build.log.

This can also happen (for build.log) if the user first ran in download-
or extract-only.

Patch (with no SoB) originally from:
Phil Wilshire <phil.wilshire@overturenetworks.com>

Modified by me as it did not apply cleanly.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
(transplanted from 1ebc2248cc60230cd53ff94ae8f8f1e3261461a3)

source "config/backend.in"

source "config/global.in"

source "config/target.in"

source "config/toolchain.in"

source "config/kernel.in"

source "config/binutils.in"

source "config/cc.in"

source "config/libc.in"

source "config/debug.in"

source "config/companion_libs.in"

source "config/companion_tools.in"

source "config/test_suite.in"