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 # Menu for the native gdbserver
7 depends on ! BARE_METAL
9 Build and install a gdbserver for the target, to run on the target.
13 config GDB_GDBSERVER_STATIC
15 prompt "Build a static gdbserver"
18 In case you have trouble with dynamic loading of shared libraries,
19 you will find that a static gdbserver comes in handy.
24 comment "In bare-metal, you'll need to "
25 comment "provide your own gdbserver stub."