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 diff -durN gcc-4.2.3.orig/gcc/config/arm/linux-eabi.h gcc-4.2.3/gcc/config/arm/linux-eabi.h
2 --- gcc-4.2.3.orig/gcc/config/arm/linux-eabi.h 2007-09-01 17:28:30.000000000 +0200
3 +++ gcc-4.2.3/gcc/config/arm/linux-eabi.h 2008-05-25 23:47:36.000000000 +0200
5 #define SUBTARGET_CPU_DEFAULT TARGET_CPU_arm10tdmi
7 #undef SUBTARGET_EXTRA_LINK_SPEC
8 -#define SUBTARGET_EXTRA_LINK_SPEC " -m armelf_linux_eabi"
9 +#define SUBTARGET_EXTRA_LINK_SPEC \
10 + " %{mlittle-endian:-m armelf_linux_eabi} %{mbig-endian:-m armelfb_linux_eabi}"
12 /* Use ld-linux.so.3 so that it will be possible to run "classic"
13 GNU/Linux binaries on an EABI system. */