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 # Compute powerpc-specific values
4 # The architecture part of the tuple:
5 CT_TARGET_ARCH="${CT_ARCH}"
10 # Add spe in the tuplet if needed
11 case "${CT_LIBC},${CT_ARCH_POWERPC_SPE}" in
12 glibc,|eglibc,) CT_TARGET_SYS=gnu;;
13 glibc,y|eglibc,y) CT_TARGET_SYS=gnuspe;;
16 # Add extra flags for SPE if needed
17 if [ "${CT_ARCH_POWERPC_SPE}" = "y" ]; then
18 CT_ARCH_TARGET_CFLAGS="-mabi=spe -mspe"
19 CT_ARCH_CC_CORE_EXTRA_CONFIG="--enable-e500_double"
20 CT_ARCH_CC_EXTRA_CONFIG="--enable-e500_double"