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)

 # dmalloc debug facility

 # depends on ! BACKEND

 config DEBUG_dmalloc

     bool

 choice

     bool

     prompt "dmalloc version"

 # Don't remove next line

 # CT_INSERT_VERSION_BELOW

 config DMALLOC_V_5_5_2

     bool

     prompt "5.5.2"

 endchoice

 config DMALLOC_VERSION

     string

 # Don't remove next line

 # CT_INSERT_VERSION_STRING_BELOW

     default "5.5.2" if DMALLOC_V_5_5_2