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)

 diff -durN glibc-2.10.1.orig/sysdeps/sh/sh4/fpu/fpu_control.h glibc-2.10.1/sysdeps/sh/sh4/fpu/fpu_control.h

 --- glibc-2.10.1.orig/sysdeps/sh/sh4/fpu/fpu_control.h	2001-07-06 06:56:04.000000000 +0200

 +++ glibc-2.10.1/sysdeps/sh/sh4/fpu/fpu_control.h	2009-11-13 00:51:26.000000000 +0100

 @@ -45,6 +45,7 @@

  #define _FPU_GETCW(cw) __asm__ ("sts fpscr,%0" : "=r" (cw))

  #if defined __GNUC__

 +extern void __set_fpscr(unsigned long);

  #define _FPU_SETCW(cw) __set_fpscr ((cw))

  #else

  #define _FPU_SETCW(cw) __asm__ ("lds %0,fpscr" : : "r" (cw))