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 (C) 2007 Yann E. MORIN <yann.morin.1998@anciens.enib.fr>
4 Shut off a stupid warning: preffered-stack-boundary must be between 4 ad 12,
7 diff -dur glibc-2.5.orig/sysdeps/i386/Makefile glibc-2.5/sysdeps/i386/Makefile
8 --- glibc-2.5.orig/sysdeps/i386/Makefile 2005-03-06 01:18:16.000000000 +0100
9 +++ glibc-2.5/sysdeps/i386/Makefile 2007-05-27 17:49:37.000000000 +0200
12 sysdep-CFLAGS += -mpreferred-stack-boundary=4
14 -sysdep-CFLAGS += -mpreferred-stack-boundary=2
15 +sysdep-CFLAGS += -mpreferred-stack-boundary=4
16 # Likewise, any function which calls user callbacks
17 uses-callbacks += -mpreferred-stack-boundary=4
18 # Likewise, any stack alignment tests