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.7.orig/Makerules glibc-2.7/Makerules

 --- glibc-2.7.orig/Makerules	2007-08-26 04:18:03.000000000 +0200

 +++ glibc-2.7/Makerules	2008-07-28 15:17:27.000000000 +0200

 @@ -1203,6 +1203,9 @@

  # The include magic above causes those files to use this variable for flags.

  CPPFLAGS-nonlib = -DNOT_IN_libc=1

 +ifneq ($(OBJDUMP_FOR_HOST),)

 +OBJDUMP = $(OBJDUMP_FOR_HOST)

 +endif

  ifeq ($(versioning),yes)

  # Generate normalized lists of symbols, versions, and data sizes.