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 # Compute ARM-specific values
4 # The architecture part of the tuple:
5 CT_TARGET_ARCH="${CT_ARCH}${target_endian_eb}"
7 # The system part of the tuple:
8 case "${CT_LIBC},${CT_ARCH_ARM_EABI}" in
9 *glibc,y) CT_TARGET_SYS=gnueabi;;
10 uClibc,y) CT_TARGET_SYS=uclibcgnueabi;;
11 none,y) CT_TARGET_SYS=eabi;;
14 # In case we're EABI, do *not* specify any ABI!
15 # which means, either we do not have an ABI specified, or we're not EABI.
16 CT_TestOrAbort "Internal error: CT_ARCH_ABI should not be set for EABI build." -z "${CT_ARCH_ABI}" -o -z "${CT_ARCH_ARM_EABI}"