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)
6 # Don't remove next line
7 # CT_INSERT_VERSION_BELOW
11 prompt "0.9 (EXPERIMENTAL)"
12 depends on EXPERIMENTAL
16 prompt "0.8.2 (EXPERIMENTAL)"
17 depends on EXPERIMENTAL
29 prompt "0.6 (OBSOLETE)"
36 # Don't remove next line
37 # CT_INSERT_VERSION_STRING_BELOW
38 default "0.9" if MPC_V_0_9
39 default "0.8.2" if MPC_V_0_8_2
40 default "0.8.1" if MPC_V_0_8_1
41 default "0.7" if MPC_V_0_7
42 default "0.6" if MPC_V_0_6