config/debug/gdb.in.cross
author "Horst Kronstorfer" <horst.kronstorfer@aon.at>
Sat Jan 08 18:07:02 2011 +0100 (2011-01-08)
branch1.9
changeset 2258 587e1dd6d423
parent 1916 e5b635bb9290
child 2209 cdafca8bdaa8
permissions -rw-r--r--
debug/ltrace: fix building for mips

ltrace 0.5.3 currently fails to build for target mips because MY_TARGET
(introduced by patches/ltrace/0.5.3/150-allow-configurable-arch.patch)
is set to 'mips' via CT_ARCH, while the mips specific stuff in ltrace
(0.5.3) is stored under sysdeps/linux-gnu/mipsel:

result: *** No rule to make target `mips/arch.h', needed by `sysdep.h'.
Stop.

The following patch fixes this issue

Signed-off-by: "Horst Kronstorfer" <horst.kronstorfer@aon.at>
[yann.morin.1998@anciens.enib.fr: reformat commit log]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
(transplanted from 2115901c7f07181d92ddbd7dd7ebeaa72e4fb176)
     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