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)
9 prompt "elf2flt version"
10 # Don't remove next line
11 # CT_INSERT_VERSION_BELOW
13 config ELF2FLT_CVSHEAD
17 Grab the latest version of elf2flt from the CVS repository
19 config ELF2FLT_CVS_SNAPSHOT
25 config ELF2FLT_CVS_SNAPSHOT_SPEC
27 depends on ELF2FLT_CVS_SNAPSHOT
29 prompt "CVS refspec for elf2flt"
31 What you enter here will be passed verbatim to the cvs checkout command
34 config ELF2FLT_VERSION
36 default "head" if ELF2FLT_CVSHEAD
37 # Don't remove next line
38 # CT_INSERT_VERSION_STRING_BELOW
40 config ELF2FLT_EXTRA_CONFIG
42 prompt "elf2flt extra config"
45 Extra flags passed onto ./configure when configuring