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 --- dmalloc-5.5.2.orig/configure 2008-06-17 13:10:09.000000000 +0200
2 +++ dmalloc-5.5.2/configure 2008-06-17 13:11:25.000000000 +0200
4 echo "$as_me:$LINENO: checking strdup macro" >&5
5 echo $ECHO_N "checking strdup macro... $ECHO_C" >&6
6 if test "$cross_compiling" = yes; then
7 - ac_cv_strdup_macro=no
8 + cat >conftest.$ac_ext <<_ACEOF
11 +cat confdefs.h >>conftest.$ac_ext
12 +cat >>conftest.$ac_ext <<_ACEOF
13 +/* end confdefs.h. */
26 +rm -f conftest.o conftest.obj
27 +if { (eval echo "$as_me:$LINENO: \"$ac_compile\"") >&5
28 + (eval $ac_compile) 2>&5
30 + echo "$as_me:$LINENO: \$? = $ac_status" >&5
31 + (exit $ac_status); }; then
32 + ac_cv_strdup_macro=yes
34 + ac_cv_strdup_macro=no
38 cat >conftest.$ac_ext <<_ACEOF