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)

 # Options specific to crosstool-NG acting as a backend

 config IS_A_BACKEND

     string

     option env="CT_IS_A_BACKEND"

 config BACKEND

     bool

     default y if IS_A_BACKEND =  "y" || IS_A_BACKEND =  "Y"

     default n if IS_A_BACKEND != "y" && IS_A_BACKEND != "Y"

 config BACKEND_ARCH

     string

     option env="CT_BACKEND_ARCH"

 config BACKEND_KERNEL

     string

     option env="CT_BACKEND_KERNEL"

 config BACKEND_LIBC

     string

     option env="CT_BACKEND_LIBC"