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 Give preference to target-optimised functions over glibc's ones,
2 which in turn ahave precedence over generic ones.
4 --- uClibc.orig/libc/Makefile 2005-07-20 08:10:44.000000000 +0200
5 +++ uclibc/libc/Makefile 2005-07-28 13:33:40.000000000 +0200
7 $(AR) dN 2 $(LIBNAME) $$objs && \
8 $(AR) dN 2 $(LIBNAME) $$objs
9 @for objfile in obj.signal \
10 - obj.string.generic obj.string.$(TARGET_ARCH) obj.string \
11 + obj.string obj.string.generic obj.string.$(TARGET_ARCH) \
12 obj.sysdeps.common obj.sysdeps.$(TARGET_ARCH) ; do \
13 if [ -e $$objfile ] ; then \
14 echo $(AR) $(ARFLAGS) $(LIBNAME) $$objfile ; \