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)
1 Correctly check for g++ existence.
3 Copyright 2007 Yann E. MORIN <yann.morin.1998@anciens.enib.fr>
4 Licensed to you as dmalloc-5.5.2 is.
6 diff -dur dmalloc-5.5.2.orig/configure dmalloc-5.5.2/configure
7 --- dmalloc-5.5.2.orig/configure 2007-05-18 11:40:31.000000000 +0200
8 +++ dmalloc-5.5.2/configure 2007-05-18 11:42:02.000000000 +0200
12 # see if we actually have a CXX program
13 -if test "$ac_cv_prog_CXX" = "" -o ! -x "$ac_cv_prog_CXX"; then
14 +if test "$ac_cv_prog_CXX" = "" -o ! -x `which "$ac_cv_prog_CXX"`; then
15 { echo "$as_me:$LINENO: WARNING: could not find C++ compiler $ac_cv_prog_CXX" >&5
16 echo "$as_me: WARNING: could not find C++ compiler $ac_cv_prog_CXX" >&2;}