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 -uNpr gcc-4.2.1_orig/gcc/config/rs6000/darwin-ldouble.c gcc-4.2.1/gcc/config/rs6000/darwin-ldouble.c
2 --- gcc-4.2.1_orig/gcc/config/rs6000/darwin-ldouble.c 2007-03-05 11:54:00.000000000 -0500
3 +++ gcc-4.2.1/gcc/config/rs6000/darwin-ldouble.c 2008-01-31 17:51:24.000000000 -0500
4 @@ -70,6 +70,8 @@ Software Foundation, 51 Franklin Street,
5 but GCC currently generates poor code when a union is used to turn
6 a long double into a pair of doubles. */
8 +#if defined (_SOFT_FLOAT) && defined (__LONG_DOUBLE_128__)
10 long double __gcc_qadd (double, double, double, double);
11 long double __gcc_qsub (double, double, double, double);
12 long double __gcc_qmul (double, double, double, double);
13 @@ -219,8 +221,6 @@ __gcc_qdiv (double a, double b, double c
17 -#if defined (_SOFT_FLOAT) && defined (__LONG_DOUBLE_128__)
19 long double __gcc_qneg (double, double);
20 int __gcc_qeq (double, double, double, double);
21 int __gcc_qne (double, double, double, double);