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 This is the README for crosstool-NG
3 Crosstool-NG follows the autoconf dance. So, to get you
4 kick-started, just run:
7 You will find the documentation in the directory 'docs'.
8 Here is a quick overview of what you'll find there:
11 2 - Installing crosstool-NG
12 3 - Configuring a toolchain
13 4 - Building the toolchain
14 5 - Using the toolchain
22 You can also point your browser at:
23 http://ymorin.is-a-geek.org/projects/crosstool