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.11.2 (EXPERIMENTAL)"
12 depends on EXPERIMENTAL
17 prompt "0.11.1 (EXPERIMENTAL)"
18 depends on EXPERIMENTAL
23 prompt "0.11 (EXPERIMENTAL)"
24 depends on EXPERIMENTAL
35 # Don't remove next line
36 # CT_INSERT_VERSION_STRING_BELOW
37 default "0.11.2" if PPL_V_0_11_2
38 default "0.11.1" if PPL_V_0_11_1
39 default "0.11" if PPL_V_0_11
40 default "0.10.2" if PPL_V_0_10_2
42 # For PPL 0.11, we need to pull libpwl if configured static
46 select PPL_NEEDS_LIBPWL if ! COMPLIBS_SHARED
48 config PPL_NEEDS_LIBPWL