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 On 20081011, Khem RAJ writes:
2 You have to bar gcc trying to build unwinding at stage 1. Try the
3 attached patch and see if it helps.
5 gcc/config/sh/linux-unwind.h | 3 +++
6 1 file changed, 3 insertions(+)
8 Index: gcc-4_2-branch/gcc/config/sh/linux-unwind.h
9 ===================================================================
10 --- gcc-4_2-branch.orig/gcc/config/sh/linux-unwind.h 2008-07-01 17:24:40.000000000 -0700
11 +++ gcc-4_2-branch/gcc/config/sh/linux-unwind.h 2008-07-01 17:25:47.000000000 -0700
12 @@ -26,6 +26,8 @@ along with this program; see the file CO
13 the Free Software Foundation, 51 Franklin Street, Fifth Floor,
14 Boston, MA 02110-1301, USA. */
18 /* Do code reading to identify a signal frame, and set the frame
19 state data appropriately. See unwind-dw2.c for the structs. */
21 @@ -251,3 +253,4 @@ sh_fallback_frame_state (struct _Unwind_
22 return _URC_NO_REASON;
24 #endif /* defined (__SH5__) */
25 +#endif /* ifndef inhibit_libc */