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)
     1 # Menu for the cross GDB
     2 
     3 config GDB_CROSS
     4     bool
     5     prompt "Cross-gdb"
     6     default y
     7     select GDB_GDBSERVER if ! BARE_METAL
     8     help
     9       Build and install a cross-gdb for the target, to run on host.
    10 
    11 if GDB_CROSS
    12 
    13 config GDB_CROSS_STATIC
    14     bool
    15     prompt "Build a static cross gdb"
    16     default n
    17     help
    18       A static cross gdb can be usefull if you debug on a machine that is
    19       not the one that is used to compile the toolchain.
    20       
    21       That way, you can share the cross-gdb without installing a toolchain
    22       on every machine that will be used to debug target programs.
    23 
    24 endif # GDB_CROSS