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(-)
3 comment "glibc specific options"
11 prompt "2.3.6 (OBSOLETE)"
34 # CT_INSERT_VERSION_ABOVE
35 # Don't remove above line!
39 prompt "'latest' snapshot (EXPERIMENTAL)"
40 depends on EXPERIMENTAL
44 prompt "<specific date> (EXPERIMENTAL)"
45 depends on EXPERIMENTAL
51 prompt "Enter date (YYYYMMDD)" if LIBC_V_date
52 default "latest" if LIBC_V_LATEST
53 default "2.3.6" if LIBC_V_2_3_6
54 default "2.4" if LIBC_V_2_4
55 default "2.5" if LIBC_V_2_5
56 default "2.5.1" if LIBC_V_2_5_1
57 default "2.6" if LIBC_V_2_6
58 default "2.6.1" if LIBC_V_2_6_1
59 default "2.7" if LIBC_V_2_7
60 # CT_INSERT_VERSION_STRING_ABOVE
61 # Don't remove above line!
63 # Please note: This is not used for now (no sh support).
64 config LIBC_GLIBC_CONFIGPARMS
66 # prompt "Extra config params (READ HELP)"
67 default "" if ARCH != "sh3" && ARCH != "sh4"
68 default "no-z-defs=yes" if ARCH = "sh3" || ARCH = "sh4"
70 Some architectures need to set options in the file configparms.
71 This is the case for sh3/4, which really need to set configparms as of
74 Unless you are building a toolchain for sh3/4, you should leave that empty.
76 Note: this is awkward, doesn't work well if you need more than one