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.2.1.orig/libstdc++-v3/configure gcc-4.2.1/libstdc++-v3/configure

 --- gcc-4.2.1.orig/libstdc++-v3/configure	2007-08-03 20:30:21.000000000 +0200

 +++ gcc-4.2.1/libstdc++-v3/configure	2007-08-03 20:33:56.000000000 +0200

 @@ -7514,6 +7514,9 @@

  cat >>conftest.$ac_ext <<_ACEOF

  /* end confdefs.h.  */

  #include <complex.h>

 +#ifdef __UCLIBC__

 +#error ugly hack to make sure configure test fails here for cross until uClibc supports the complex funcs

 +#endif

  int

  main ()

  {