config/debug/gdb.in.gdbserver
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Tue Jul 12 23:52:24 2011 +0200 (2011-07-12)
branch1.11
changeset 2558 b7317d2fe0e9
parent 1844 4d6a56579d9d
child 2484 d1a8c2ae7946
permissions -rw-r--r--
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)
yann@1849
     1
# Menu for the native gdbserver
yann@622
     2
yann@583
     3
config GDB_GDBSERVER
yann@583
     4
    bool
yann@583
     5
    prompt "gdbserver"
yann@583
     6
    default n
yann@850
     7
    depends on ! BARE_METAL
yann@583
     8
    help
yann@583
     9
      Build and install a gdbserver for the target, to run on the target.
yann@583
    10
yann@1849
    11
if GDB_GDBSERVER
yann@1849
    12
yann@583
    13
config GDB_GDBSERVER_STATIC
yann@175
    14
    bool
yann@175
    15
    prompt "Build a static gdbserver"
yann@622
    16
    default y
yann@175
    17
    help
yann@175
    18
      In case you have trouble with dynamic loading of shared libraries,
yann@175
    19
      you will find that a static gdbserver comes in handy.
yann@175
    20
yann@1849
    21
endif # GDB_GDBSERVER
yann@1849
    22
yann@1269
    23
if BARE_METAL
yann@1269
    24
comment "In bare-metal, you'll need to   "
yann@1269
    25
comment "provide your own gdbserver stub."
yann@1269
    26
endif # BARE_METAL