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 Index: binutils-2.19.51.0.5/ld/ld.texinfo
2 ===================================================================
3 --- binutils-2.19.51.0.5.orig/ld/ld.texinfo
4 +++ binutils-2.19.51.0.5/ld/ld.texinfo
5 @@ -2036,8 +2036,9 @@ This linker can create the new dynamic t
6 systems may not understand them. If you specify
7 @option{--enable-new-dtags}, the dynamic tags will be created as needed.
8 If you specify @option{--disable-new-dtags}, no new dynamic tags will be
9 -created. By default, the new dynamic tags are not created. Note that
10 -those options are only available for ELF systems.
11 +created. On Gentoo, by default, the new dynamic tags are created (this
12 +differs from upstream behaviour). Note that those options are only
13 +available for ELF systems.
15 @kindex --hash-size=@var{number}
16 @item --hash-size=@var{number}