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 Original patch from gentoo: ../../dev/crosstool-NG/ct-ng.trunk/patches/strace/4.5.17/120-fix-arm-bad-syscall.patch
2 -= BEGIN original header =-
3 diff -dur strace-4.5.16.orig/syscall.c strace-4.5.16/syscall.c
4 -= END original header =-
5 diff -durN strace-4.5.17.orig/syscall.c strace-4.5.17/syscall.c
6 --- strace-4.5.17.orig/syscall.c 2008-05-28 01:18:29.000000000 +0200
7 +++ strace-4.5.17/syscall.c 2008-10-24 21:30:13.000000000 +0200
10 * Note: we only deal with only 32-bit CPUs here.
13 + if (!(tcp->flags & TCB_INSYSCALL) &&
14 + (tcp->flags & TCB_WAITEXECVE)) {
15 + /* caught a fake syscall from the execve's exit */
16 + tcp->flags &= ~TCB_WAITEXECVE;
21 if (regs.ARM_cpsr & 0x20) {
23 * Get the Thumb-mode system call number