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 # mingw32 config options
2 # depends on EXPERIMENTAL && ( ARCH_x86 && ARCH_32 )
7 Build a toolchain targeting systems running Windows as host
11 prompt "Windows api version"
13 # Don't remove next line
14 # CT_INSERT_VERSION_BELOW
19 config W32API_V_select
21 prompt "Other version"
27 prompt "W32 api version" if W32API_V_select
28 # Don't remove next line
29 # CT_INSERT_VERSION_STRING_BELOW
30 default "3.14" if W32API_V_3_14
32 Enter the version number of the windows api files to use