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 --- gcc-4.2.1-stock/gcc/config/alpha/linux-unwind.h 2005-06-24 20:22:41.000000000 -0500
2 +++ gcc-4.2.1/gcc/config/alpha/linux-unwind.h 2007-09-01 20:21:34.000000000 -0500
3 @@ -29,6 +29,9 @@ Boston, MA 02110-1301, USA. */
4 /* Do code reading to identify a signal frame, and set the frame
5 state data appropriately. See unwind-dw2.c for the structs. */
7 +/* Don't use this if inhibit_libc is set
8 + The build for this target will fail trying to include missing headers */
11 #include <sys/ucontext.h>
13 @@ -80,3 +83,4 @@ alpha_fallback_frame_state (struct _Unwi
14 fs->retaddr_column = 64;
15 return _URC_NO_REASON;
17 +#endif /* inhibit_libc */