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(-)
4 local cur prev samples show_samples actions steps start_steps stop_steps ct_ng_opts vars
7 prev=${COMP_WORDS[COMP_CWORD-1]}
9 samples=$(${COMP_WORDS[0]} list-samples)
10 show_samples=$(echo "${samples}" |sed -r -e 's/(^| )/\1show-/g;')
12 steps=$(${COMP_WORDS[0]} list-steps |awk '$1 == "-" { print $2; }')
13 start_steps=$(echo "${steps}" |sed -r -e 's/(^| )/\1+/;')
14 stop_steps=$(echo "${steps}" |sed -r -e 's/(^| )/+\1/;')
16 actions='config menuconfig oldconfig saveconfig extractconfig
17 list-samples build list-steps regtest regtest-local
18 regtest-global clean distclean wiki-samples updatetools
23 ct_ng_opts="${samples} ${show_samples}
24 ${steps} ${start_steps} ${stop_steps}
27 COMPREPLY=($(compgen -W "${ct_ng_opts}" -- "${cur}"))
30 complete -F _ct-ng ct-ng