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)
1 # Configuration file for sstrip tool facility
3 if OBSOLETE && ! BACKEND && ARCH_BINFMT_ELF
9 prompt "sstrip (OBSOLETE)"
11 The sstrip utility, to maximise the striping of ELF binaries
12 (executables and libraries).
14 Buildroot version, forked off the original from ELFkickers.
15 This one is somewhat maintained by the buildroot guys.
16 Supports big-endian systems.
19 sstrip is now deprecated in crosstool-NG, as it has a few
20 shortcomings. For example: it breaks for PPC targets, it
21 does not build on non-ELF hosts (eg. mingw32, MacOS-X...).