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(-)
9 libelf lets you read, modify or create ELF files in an
10 architecture-independent way.
12 libelf is BROKEN! If you manage to make it actually _work_,
13 please be so kind as to tell me. (By working, I mean it is
14 useable at least by ltrace.) Thank you!
20 prompt "libelf version"
24 prompt "0.8.8 (OBSOLETE)"
31 config LIBELF_V_0_8_10
35 # CT_INSERT_VERSION_ABOVE
36 # Don't remove above line!
41 default "0.8.8" if LIBELF_V_0_8_8
42 default "0.8.9" if LIBELF_V_0_8_9
43 default "0.8.10" if LIBELF_V_0_8_10
44 # CT_INSERT_VERSION_STRING_ABOVE
45 # Don't remove above line!