Get rid of CT_LIBC_FILE, remove useless CT_MakeAbsolutePath.

CT_LIBC_FILE:
- that one was not easy, as it had sneaked into CT_ExtractAndPatch
- which in turn made CT_ExtractAndPatch have references to C library addons
- which in turn relieved the C library _extract functions from doing their own job
- which in turn imposed some nasty tricks in CT_ExtractAndPatch
- which in turn made life easier for the DUMA _get and _extract functions
- which unveiled some bizare behavior for pushd and popd:
- if using smthg ike: 'pushd foo |bar':
- the directory is *neither* changed
- *nor* is it pushed onto the stack
- which made popd fail

CT_MakeAbsolutePath:
- used only to make CT_LOCAL_TARBALLS_DIR canonical
- which is ((almost) useless:
- hopefully, the user entered a full path already
- if it's not the case, too bad...

/trunk/scripts/build/debug/200-duma.sh | 5 1 4 0 +--
/trunk/scripts/build/libc/glibc.sh | 61 32 29 0 +++++++++++++++++---------------
/trunk/scripts/build/libc/uClibc.sh | 16 10 6 0 +++++---
/trunk/scripts/build/libc/eglibc.sh | 48 26 22 0 ++++++++++++++-----------
/trunk/scripts/crosstool.sh | 8 0 8 0 ----
/trunk/scripts/functions | 77 15 62 0 ++++++++--------------------------------
6 files changed, 84 insertions(+), 131 deletions(-)

# ltrace

config DEBUG_ltrace

    select TOOL_libelf

    help

      ltrace is a program that simply runs the specified command until it exits.

      It intercepts and records the dynamic library calls which are called by

      the executed process and the signals which are received by that process.

      It can also intercept and print the system calls executed by the program.

choice

    bool

    prompt "ltrace version"

config LTRACE_V_0_4

    bool

    prompt "0.4"

config LTRACE_V_0_5

    bool

    prompt "0.5"

# CT_INSERT_VERSION_ABOVE

# Don't remove above line!

endchoice

config LTRACE_VERSION

    string

    default "0.4" if LTRACE_V_0_4

    default "0.5" if LTRACE_V_0_5

# CT_INSERT_VERSION_STRING_ABOVE

# # Don't remove above line!