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)

 syntax: glob

 # Generated files

 Makefile

 ct-ng

 docs/ct-ng.1

 docs/ct-ng.1.gz

 paths.mk

 scripts/crosstool-NG.sh

 scripts/saveSample.sh

 scripts/showTuple.sh

 kconfig/conf

 kconfig/mconf

 kconfig/**.o

 kconfig/**.dep

 config.gen/

 .config

 # Temporaries

 .*.swp

 build.log

 .config.old

 # This is the place where toolchains are built

 .build/

 # .. and the legacy location

 targets/