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 debug facilities
3 # List all debug facilities, and parse their scripts
4 CT_DEBUG_FACILITY_LIST=
5 for f in "${CT_LIB_DIR}/scripts/build/debug/"*.sh; do
8 f=$(basename "${f}" .sh)
9 if [ "${is_enabled}" = "y" ]; then
10 CT_DEBUG_FACILITY_LIST="${CT_DEBUG_FACILITY_LIST} ${f#???-}"
14 # Download the debug facilities
16 for f in ${CT_DEBUG_FACILITY_LIST}; do
21 # Extract and patch the debug facilities
23 for f in ${CT_DEBUG_FACILITY_LIST}; do
28 # Build the debug facilities
30 for f in ${CT_DEBUG_FACILITY_LIST}; do