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 # powerpc specific configuration file
3 config ARCH_POWERPC_SPE
5 prompt "Enable SPE support"
8 Add support for the Signal Processing Engine. This will set up
9 the toolchain so that it supports the SPE ABI extensions. This
10 mainly targets Freescale e500 processors.
12 Setting this option will append "spe" to the end of your target
13 tuple name (e.g., powerpc-e500v2-linux-gnuspe) so that the gcc
14 configure/build system will know to include SPE ABI support.
15 It will also automatically add "-mabi=spe -mspe" to your
16 TARGET_CFLAGS, and "--enable-e500_double" to your CC_EXTRA_CONFIG,
17 so you do not need to explicitly add them.