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 # Test suite config options
13 prompt "GCC test suite"
14 depends on EXPERIMENTAL
18 Select this option to install the GCC test suite in $CT_PREFIX_DIR/test_suite.
20 The GCC test suite includes a collection of various toolchain tests for GCC -
21 it utilizes the DejaGnu test framework.
23 For some tests a network enabled target with ssh server is required.
25 A helper Makefile is provided for running the tests - please see the included
26 README for information on how to run the test suite.