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 Enable using a shell other than bash.
2 Courtesy "Martin Guy" <martinwguy@yahoo.it>
3 http://sourceware.org/ml/crossgcc/2008-08/msg00037.html
5 --- binutils-2.18.orig/ld/genscripts.sh 2007-08-12 20:00:07.000000000 +0100
6 +++ binutils-2.18/ld/genscripts.sh 2008-08-25 16:09:54.000000000 +0100
9 em_script=$current_script
13 + alias fragment='em_lineno=$LINENO; fragment_em'
16 - local lineno=$[${BASH_LINENO[0]} + 1]
17 + local lineno=$[$em_lineno + 1]
18 echo >> e${EMULATION_NAME}.c "#line $lineno \"$em_script\""
19 cat >> e${EMULATION_NAME}.c