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 reporter_name="Anthony Foiani <anthony.foiani@gmail.com>"
2 reporter_url="http://sourceware.org/ml/crossgcc/2010-09/msg00100.html"
3 reporter_comment="This is a sample config file for Freescale e500v2 processors (e.g., MPC8548,
4 MPC8572). It uses eglibc (for e500/SPE patches) and a recent gcc (4.6.0,
5 for e500v2 DPFP support) and will generate appropriate dual-precision
6 floating point instructions by default.
8 Note: If building a Linux kernel with this toolchain, you will want to make
9 sure -mno-spe AND -mspe=no are passed to gcc to prevent SPE ABI/instructions
10 from getting into the kernel (which is currently unsupported). At this time,
11 the kernel build system properly passes those two options, but older kernels
12 were only passing -mno-spe by default."