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 --- binutils/bfd/elf64-ppc.c.jj 2004-09-27 16:46:06.000000000 -0400
2 +++ binutils/bfd/elf64-ppc.c 2004-10-04 09:09:50.000000000 -0400
3 @@ -9681,7 +9681,12 @@ ppc64_elf_relocate_section (bfd *output_
4 else if (!SYMBOL_REFERENCES_LOCAL (info, &h->elf)
6 && r_type != R_PPC64_TOC)
7 - outrel.r_info = ELF64_R_INFO (h->elf.dynindx, r_type);
9 + outrel.r_info = ELF64_R_INFO (h->elf.dynindx, r_type);
10 + if (h->elf.dynindx == -1
11 + && h->elf.root.type == bfd_link_hash_undefweak)
12 + memset (&outrel, 0, sizeof outrel);
16 /* This symbol is local, or marked to become local,