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 diff -u binutils-2.20.orig/configure binutils-2.20/configure
2 --- binutils-2.20.orig/configure 2010-01-05 11:15:44.000000000 +0100
3 +++ binutils-2.20/configure 2010-01-05 12:25:41.000000000 +0100
5 noconfigdirs="$noconfigdirs target-libffi target-qthreads"
8 - arm*-*-linux-gnueabi)
9 + arm*-*-linux-*gnueabi)
10 noconfigdirs="$noconfigdirs target-qthreads"
11 case ${with_newlib} in
12 no) noconfigdirs="$noconfigdirs target-newlib target-libgloss"
13 diff -u binutils-2.20.orig/configure.ac binutils-2.20/configure.ac
14 --- binutils-2.20.orig/configure.ac 2010-01-05 11:15:44.000000000 +0100
15 +++ binutils-2.20/configure.ac 2010-01-05 12:25:51.000000000 +0100
17 noconfigdirs="$noconfigdirs target-libffi target-qthreads"
20 - arm*-*-linux-gnueabi)
21 + arm*-*-linux-*gnueabi)
22 noconfigdirs="$noconfigdirs target-qthreads"
23 case ${with_newlib} in
24 no) noconfigdirs="$noconfigdirs target-newlib target-libgloss"