config/debug/gdb.in.cross
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Thu Feb 17 21:54:07 2011 +0100 (2011-02-17)
branch1.10
changeset 2389 1cf50fe7c418
parent 2098 9a8f0e3fe605
child 2484 d1a8c2ae7946
permissions -rw-r--r--
internals: fix stripping host binaries

The gcc used by linaro has a version number specific to Linaro, but
identifies itself with its upstream version numbering scheme.

This breaks the strip in the finish step, because the actual gcc version
is not the same as the configured one (eg. 4.5.2 vs. linaro-4.5-2011.02-0).

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
(transplanted from a3818c3b03e053adb8f6b7e6cf326f16a7f0c4aa)
     1 # Menu for the cross GDB
     2 
     3 config STATIC_TOOLCHAIN
     4     select GDB_CROSS_STATIC if GDB_CROSS
     5 
     6 config GDB_CROSS
     7     bool
     8     prompt "Cross-gdb"
     9     default y
    10     select GDB_GDBSERVER if ! BARE_METAL
    11     help
    12       Build and install a cross-gdb for the target, to run on host.
    13 
    14 if GDB_CROSS
    15 
    16 config GDB_CROSS_STATIC
    17     bool
    18     prompt "Build a static cross gdb"
    19     default n
    20     help
    21       A static cross gdb can be usefull if you debug on a machine that is
    22       not the one that is used to compile the toolchain.
    23       
    24       That way, you can share the cross-gdb without installing a toolchain
    25       on every machine that will be used to debug target programs.
    26 
    27 endif # GDB_CROSS