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)

Original patch from Gentoo.

-= BEGIN original header =-

-= END original header =-

diff -durN uClibc-0.9.30.orig/Rules.mak uClibc-0.9.30/Rules.mak

--- uClibc-0.9.30.orig/Rules.mak	2008-11-12 13:24:16.000000000 +0100

+++ uClibc-0.9.30/Rules.mak	2009-02-07 09:57:59.000000000 +0100

@@ -519,6 +519,7 @@

 endif

 CFLAGS += $(call check_gcc,-std=gnu99,)

+CFLAGS += $(call check_gcc,-fgnu89-inline,)

 LDFLAGS_NOSTRIP:=$(CPU_LDFLAGS-y) -shared \

 	-Wl,--warn-common -Wl,--warn-once -Wl,-z,combreloc