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 -dur duma_2_5_1/Makefile duma_2_5_1.orig/Makefile
2 --- duma_2_5_1/Makefile 2006-06-18 06:02:13.000000000 +0200
3 +++ duma_2_5_1.orig/Makefile 2007-07-11 17:49:43.000000000 +0200
14 ############################################################
17 createconf: createconf.o
19 - $(CC) $(CFLAGS) $(DUMA_OPTIONS) createconf.o -o createconf
20 + $(HOSTCC) $(HOSTCFLAGS) $(DUMA_OPTIONS) createconf.o -o createconf
22 tstheap: libduma.a tstheap.o
25 # define rules how to build objects for createconf
28 - $(CC) $(CFLAGS) $(DUMA_OPTIONS) -c createconf.c -o $@
29 + $(HOSTCC) $(HOSTCFLAGS) $(DUMA_OPTIONS) -c createconf.c -o $@