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 Original patch from gentoo: gentoo/src/patchsets/gcc/4.3.1/gentoo/66_all_gcc43-pr25343.patch
2 http://gcc.gnu.org/PR25343
6 2008-04-27 Roman Zippel <zippel@linux-m68k.org>
8 * config/host-linux.c (TRY_EMPTY_VM_SPACE): Define for __mc68000__.
10 diff -durN gcc-4.3.1.orig/gcc/config/host-linux.c gcc-4.3.1/gcc/config/host-linux.c
11 --- gcc-4.3.1.orig/gcc/config/host-linux.c 2007-08-02 12:49:31.000000000 +0200
12 +++ gcc-4.3.1/gcc/config/host-linux.c 2008-06-10 14:58:28.000000000 +0200
14 # define TRY_EMPTY_VM_SPACE 0x8000000000
15 #elif defined(__sparc__)
16 # define TRY_EMPTY_VM_SPACE 0x60000000
17 +#elif defined(__mc68000__)
18 +# define TRY_EMPTY_VM_SPACE 0x40000000
20 # define TRY_EMPTY_VM_SPACE 0