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>
6 # Parse the tools' paths configuration
7 . "${CT_LIB_DIR}/paths.mk"
9 # We'll need the stdout later, save it
12 # Parse the common functions
13 . "${CT_LIB_DIR}/scripts/functions"
15 # Don't care about any log file
17 rm -f "${tmp_log_file}"
19 # Parse the configuration file
22 # Parse architecture and kernel specific functions
23 . "${CT_LIB_DIR}/scripts/build/arch/${CT_ARCH}.sh"
24 . "${CT_LIB_DIR}/scripts/build/kernel/${CT_KERNEL}.sh"
29 # All this for this single echo... :-( Sigh, I'll have to re-arrange things...
30 echo "${CT_TARGET}" >&7