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 x86-specific values
3 # This one really need a little love! :-(
6 # The architecture part of the tuple:
8 [ -z "${arch}" ] && arch="${CT_ARCH_TUNE}"
10 nocona|athlon*64|k8|athlon-fx|opteron)
11 CT_DoError "Architecture is x86 (32-bit) but selected processor is \"${arch}\" (64-bit)";;
12 "") CT_TARGET_ARCH=i386;;
13 i386|i486|i586|i686) CT_TARGET_ARCH="${arch}";;
14 winchip*) CT_TARGET_ARCH=i486;;
15 pentium|pentium-mmx|c3*) CT_TARGET_ARCH=i586;;
16 pentiumpro|pentium*|athlon*) CT_TARGET_ARCH=i686;;
17 *) CT_TARGET_ARCH=i586;;