config/debug/gdb.in.cross
author Bryan Hundven <bryanhundven@gmail.com>
Wed Dec 22 22:42:11 2010 +0100 (2010-12-22)
branch1.9
changeset 2232 f0318bba39bc
parent 1916 e5b635bb9290
child 2209 cdafca8bdaa8
permissions -rw-r--r--
libc/eglibc: fix installed scripts

Like rev 2002, eglibc installs some bash scripts, but use the path to the
buildtool bash as the interpreter (on the shebang line). This is only a
symlink to the real bash, and thus is not available at runtime.

Fix that by assuming that shell on the target *will* be /bin/bash.

Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
(transplanted from 6884dcb80121ebc8ce17deee62716ed75fc29393)
yann@1849
     1
# Menu for the cross GDB
yann@96
     2
yann@96
     3
config GDB_CROSS
yann@96
     4
    bool
yann@96
     5
    prompt "Cross-gdb"
yann@96
     6
    default y
yann@850
     7
    select GDB_GDBSERVER if ! BARE_METAL
yann@96
     8
    help
yann@583
     9
      Build and install a cross-gdb for the target, to run on host.
yann@96
    10
yann@1849
    11
if GDB_CROSS
yann@1849
    12
yann@1915
    13
config GDB_CROSS_STATIC
yann@1915
    14
    bool
yann@1915
    15
    prompt "Build a static cross gdb"
yann@1915
    16
    default n
yann@1915
    17
    help
yann@1915
    18
      A static cross gdb can be usefull if you debug on a machine that is
yann@1915
    19
      not the one that is used to compile the toolchain.
yann@1915
    20
      
yann@1915
    21
      That way, you can share the cross-gdb without installing a toolchain
yann@1915
    22
      on every machine that will be used to debug target programs.
yann@1915
    23
yann@1849
    24
endif # GDB_CROSS