config/debug/ltrace.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Tue Sep 23 14:48:10 2008 +0000 (2008-09-23)
changeset 872 fd4bf138f08f
parent 245 134ac2c35c49
child 914 0b164a321177
permissions -rw-r--r--
Bart De VOS pointed out that removing absolute paths from the libc linker scripts is plainly wrong.
It dates from dawn ages of the original crosstool code, and is not well explained. At that time, binutils might not understand the sysroot stuff, and it was necessary to remove absolute paths in that case.

/trunk/scripts/build/libc/glibc.sh | 14 2 12 0 ++------------
1 file changed, 2 insertions(+), 12 deletions(-)
     1 # ltrace
     2 
     3 menuconfig LTRACE
     4     bool
     5     prompt "ltrace"
     6     default n
     7     depends on BROKEN
     8     select LIBELF
     9     help
    10       ltrace is currently BROKEN! It depends on libelf, and I don't
    11       know how to configure/compile that so that ltrace can successfully
    12       use it. I you manage to build ltrace (and libelf!), please be so
    13       kind as to tell me! Thank you!
    14 
    15 if LTRACE
    16 
    17 choice
    18     bool
    19     prompt "ltrace version"
    20 
    21 config LTRACE_V_0_3_36
    22     bool
    23     prompt "0.3.36 (OBSOLETE)"
    24     depends on OBSOLETE
    25 
    26 config LTRACE_V_0_4
    27     bool
    28     prompt "0.4"
    29 
    30 # CT_INSERT_VERSION_ABOVE
    31 # Don't remove above line!
    32 endchoice
    33 
    34 config LTRACE_VERSION
    35     string
    36     default "0.3.36" if LTRACE_V_0_3_36
    37     default "0.4" if LTRACE_V_0_4
    38 # CT_INSERT_VERSION_STRING_ABOVE
    39 # # Don't remove above line!
    40 
    41 endif