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/libgomp/configure gcc-4.4.0/libgomp/configure

 --- gcc-4.4.0.orig/libgomp/configure	2009-04-21 11:08:08.000000000 +0200

 +++ gcc-4.4.0/libgomp/configure	2009-05-27 21:38:19.000000000 +0200

 @@ -3334,7 +3334,7 @@

  # Add -Wall -Werror if we are using GCC.

  if test "x$GCC" = "xyes"; then

 -  XCFLAGS="$XCFLAGS -Wall -Werror"

 +  XCFLAGS="$XCFLAGS -Wall"

  fi

  # Find other programs we need.