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 # Taken from http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/config.gcc.diff?r1=1.91&r2=1.92
3 # Configuration x86_64-host_unknown-linux-gnu not supported
4 # when configuring gcc-2.95 on x86_64 build for i686 target
5 # It's a bit silly, since tm_file refers to files that don't exist,
6 # but as long as x86_64 is just the build machine, that doesn't matter.
8 --- gcc-2.95.3/gcc/configure.old 2004-03-24 12:17:44.000000000 -0800
9 +++ gcc-2.95.3/gcc/configure 2004-03-24 12:19:30.000000000 -0800
20 @@ -3643,6 +3646,19 @@
26 + tm_file="i386/biarch64.h i386/i386.h i386/att.h linux.h i386/x86-64.h \
28 + tmake_file="t-slibgcc-elf-ver t-linux i386/t-crtstuff"
29 + extra_parts="crtbegin.o crtbeginS.o crtend.o crtendS.o"
32 + if test x$enable_threads = xyes; then