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 -dur uClibc-0.9.28.orig/Rules.mak uClibc-0.9.28/Rules.mak
2 --- uClibc-0.9.28.orig/Rules.mak 2005-08-18 00:49:49.000000000 +0200
3 +++ uClibc-0.9.28/Rules.mak 2007-01-30 10:53:34.000000000 +0100
5 CPU_CFLAGS-$(CONFIG_MIPS_ISA_4)+=-mips4 -mtune=mips4
6 CPU_CFLAGS-$(CONFIG_MIPS_ISA_MIPS32)+=-mips32 -mtune=mips32
7 CPU_CFLAGS-$(CONFIG_MIPS_ISA_MIPS64)+=-mips64 -mtune=mips32
8 + CPU_CFLAGS-$(CONFIG_MIPS_ISA_CUSTOM)+=-march=$(CONFIG_MIPS_CPU_CFLAGS_CUSTOM)
11 ifeq ($(strip $(TARGET_ARCH)),sh)
12 diff -dur uClibc-0.9.28.orig/extra/Configs/Config.mips uClibc-0.9.28/extra/Configs/Config.mips
13 --- uClibc-0.9.28.orig/extra/Configs/Config.mips 2005-08-18 00:49:41.000000000 +0200
14 +++ uClibc-0.9.28/extra/Configs/Config.mips 2007-01-30 10:52:12.000000000 +0100
16 config CONFIG_MIPS_ISA_MIPS64
19 +config CONFIG_MIPS_ISA_CUSTOM
24 +config CONFIG_MIPS_CPU_CFLAGS_CUSTOM
27 + depends on CONFIG_MIPS_ISA_CUSTOM
30 + Enter your custom ISA here (eg: lx4189!).