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 # powerpc specific configuration file
4 select ARCH_SUPPORT_ABI
5 select ARCH_SUPPORT_CPU
6 select ARCH_SUPPORT_TUNE
8 The PowerPC architecture, as defined by:
9 http://www.ibm.com/developerworks/eserver/articles/archguide.html
11 config ARCH_POWERPC_SPE
13 prompt "Enable SPE support"
16 Add support for the Signal Processing Engine. This will set up
17 the toolchain so that it supports the SPE ABI extensions. This
18 mainly targets Freescale e500 processors.
20 Setting this option will append "spe" to the end of your target
21 tuple name (e.g., powerpc-e500v2-linux-gnuspe) so that the gcc
22 configure/build system will know to include SPE ABI support.
23 It will also automatically add "-mabi=spe -mspe" to your
24 TARGET_CFLAGS, and "--enable-e500_double" to your CC_EXTRA_CONFIG,
25 so you do not need to explicitly add them.