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 gcc-4.4.0.orig/boehm-gc/include/gc.h gcc-4.4.0/boehm-gc/include/gc.h

--- gcc-4.4.0.orig/boehm-gc/include/gc.h	2007-04-23 23:10:09.000000000 +0200

+++ gcc-4.4.0/boehm-gc/include/gc.h	2009-05-27 21:38:55.000000000 +0200

@@ -503,7 +503,7 @@

 #if defined(__linux__) || defined(__GLIBC__)

 # include <features.h>

 # if (__GLIBC__ == 2 && __GLIBC_MINOR__ >= 1 || __GLIBC__ > 2) \

-     && !defined(__ia64__)

+     && !defined(__ia64__) && !defined(__UCLIBC__)

 #   ifndef GC_HAVE_BUILTIN_BACKTRACE

 #     define GC_HAVE_BUILTIN_BACKTRACE

 #   endif