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 # D.U.M.A. - Detect Unintended Memory Access - Memory checker
7 depends on ! BARE_METAL
9 D.U.M.A. - Detect Unintended Memory Access
10 A memory bound checker, with additional features.
11 Formerly known as Electric Fence.
17 prompt "Build a static library"
22 prompt "Build a shared library"
23 default y if SHARED_LIBS
24 default n if ! SHARED_LIBS
28 prompt "D.U.M.A. version"
46 # CT_INSERT_VERSION_ABOVE
47 # Don't remove above line!
52 default "2_5_1" if DUMA_V_2_5_1
53 default "2_5_8" if DUMA_V_2_5_8
54 default "2_5_12" if DUMA_V_2_5_12
55 default "2_5_14" if DUMA_V_2_5_14
56 # CT_INSERT_VERSION_STRING_ABOVE
57 # Don't remove above line!