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 Description: correct where ld scripts are installed
2 Author: Chris Chimelis <chris@debian.org>
4 --- binutils-2.16.91.0.1/ld/Makefile.am
5 +++ binutils-2.16.91.0.1/ld/Makefile.am
7 # We put the scripts in the directory $(scriptdir)/ldscripts.
8 # We can't put the scripts in $(datadir) because the SEARCH_DIR
9 # directives need to be different for native and cross linkers.
10 -scriptdir = $(tooldir)/lib
11 +scriptdir = $(libdir)
14 EMULATION_OFILES = @EMULATION_OFILES@
15 --- binutils-2.16.91.0.1/ld/Makefile.in
16 +++ binutils-2.16.91.0.1/ld/Makefile.in
18 # We put the scripts in the directory $(scriptdir)/ldscripts.
19 # We can't put the scripts in $(datadir) because the SEARCH_DIR
20 # directives need to be different for native and cross linkers.
21 -scriptdir = $(tooldir)/lib
22 +scriptdir = $(libdir)
23 BASEDIR = $(srcdir)/..
24 BFDDIR = $(BASEDIR)/bfd
25 INCDIR = $(BASEDIR)/include