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 # Makefile for each steps
2 # Copyright 2006 Yann E. MORIN <yann.morin.1998@anciens.enib.fr>
4 CT_STEPS := libc_check_config \
25 @$(CT_NG) RESTART=$@ STOP=$@ build
27 $(patsubst %,+%,$(CT_STEPS)):
28 @$(CT_NG) STOP=$(patsubst +%,%,$@) build
30 $(patsubst %,%+,$(CT_STEPS)):
31 @$(CT_NG) RESTART=$(patsubst %+,%,$@) build
34 @echo ' list-steps - List all build steps'
37 @echo 'Available build steps, in order:'
38 @for step in $(CT_STEPS); do \
41 @echo 'Use "$(CT_NG) <step>" to execute only that step.'
42 @echo 'Use "$(CT_NG) +<step>" to execute up to that step.'
43 @echo 'Use "$(CT_NG) <step>+" to execute from that step onward.'