scripts/build/tools.sh
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 479 05c62432ec19
child 916 68af6b83ff7e
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 # Wrapper to build the tools facilities
     2 
     3 # List all tools facilities, and parse their scripts
     4 CT_TOOLS_FACILITY_LIST=
     5 for f in "${CT_LIB_DIR}/scripts/build/tools/"*.sh; do
     6     is_enabled=
     7     . "${f}"
     8     f=$(basename "${f}" .sh)
     9     if [ "${is_enabled}" = "y" ]; then
    10         CT_TOOLS_FACILITY_LIST="${CT_TOOLS_FACILITY_LIST} ${f#???-}"
    11     fi
    12 done
    13 
    14 # Download the tools facilities
    15 do_tools_get() {
    16     for f in ${CT_TOOLS_FACILITY_LIST}; do
    17         do_tools_${f}_get
    18     done
    19 }
    20 
    21 # Extract and patch the tools facilities
    22 do_tools_extract() {
    23     for f in ${CT_TOOLS_FACILITY_LIST}; do
    24         do_tools_${f}_extract
    25     done
    26 }
    27 
    28 # Build the tools facilities
    29 do_tools() {
    30     for f in ${CT_TOOLS_FACILITY_LIST}; do
    31         do_tools_${f}_build
    32     done
    33 }
    34