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 do not bother running ldconfig on DESTDIR. it wants to write the temp cache
2 file outside of the chroot. doesnt matter anyways as we wont use the cache
3 results (portage will rebuild cache), so running ldconfig is simply a waste
6 diff -durN glibc-2.10.1.orig/Makefile glibc-2.10.1/Makefile
7 --- glibc-2.10.1.orig/Makefile 2009-04-23 20:23:03.000000000 +0200
8 +++ glibc-2.10.1/Makefile 2009-11-13 00:49:49.000000000 +0100
10 rm -f $(symbolic-link-list)
13 +dont-bother-with-destdir:
14 -test ! -x $(common-objpfx)elf/ldconfig || LC_ALL=C LANGUAGE=C \
15 $(common-objpfx)elf/ldconfig $(addprefix -r ,$(install_root)) \