config/debug/gdb.in.cross
author Anthony Foiani <anthony.foiani@gmail.com>
Thu Oct 07 22:37:06 2010 +0200 (2010-10-07)
changeset 2138 2242d87c5404
parent 1916 e5b635bb9290
child 2209 cdafca8bdaa8
permissions -rw-r--r--
scripts: always create lib32 and lib64 symlinks

Unconditionally create the lib32 -> lib/ and lib64 -> lib/ symlinks.

This is reportedly a fix to build a toolchain for a 32-bit target on
a 'pure' 64-bit host (eg. on Fedora FC12, host libs are in lib64/,
and there is no lib -> lib64 symlink, as we can see on other distors,
as Debian). As gcc only puts static host lib in lib64/ (along with
target files in subdirs), we can safely create the symlinks.

Also note that the symlinks are summarily removed at the end
of the build.

Signed-off-by: Anthony Foiani <anthony.foiani@gmail.com>
[Yann E. MORIN: fix a comment, rephrase the commit log]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
     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