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-3.4.6.orig/gcc/config/sh/lib1funcs.asm gcc-3.4.6/gcc/config/sh/lib1funcs.asm
2 --- gcc-3.4.6.orig/gcc/config/sh/lib1funcs.asm 2003-08-12 03:25:07.000000000 +0200
3 +++ gcc-3.4.6/gcc/config/sh/lib1funcs.asm 2007-08-15 23:04:26.000000000 +0200
5 ELF local label prefixes by J"orn Rennecke
8 +#define ALIAS(X,Y) .global GLOBAL(X); .set GLOBAL(X),GLOBAL(Y)
11 #define LOCAL(X) .L_##X
12 -#define FUNC(X) .type X,@function
14 +#if 1 /* ??? The export list mechanism is broken, everything that is not
15 + hidden is exported. */
17 +#define FUNC(X) .type X,@function; .hidden X
19 +#define ALIAS(X,Y) .global GLOBAL(X); .set GLOBAL(X),GLOBAL(Y); .hidden GLOBAL(X)
22 #define ENDFUNC0(X) .Lfe_##X: .size X,.Lfe_##X-X
23 #define ENDFUNC(X) ENDFUNC0(X)