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/libc/inet/resolv.c uClibc-0.9.30/libc/inet/resolv.c

--- uClibc-0.9.30.orig/libc/inet/resolv.c	2008-11-02 01:25:33.000000000 +0100

+++ uClibc-0.9.30/libc/inet/resolv.c	2009-02-07 09:57:59.000000000 +0100

@@ -1788,7 +1788,7 @@

 int gethostent_r(struct hostent *result_buf, char *buf, size_t buflen,

 	struct hostent **result, int *h_errnop)

 {

-	int ret;

+	int ret = HOST_NOT_FOUND;

 	__UCLIBC_MUTEX_LOCK(mylock);

 	if (__gethostent_fp == NULL) {