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 the tools/ sub-directory
3 # Here, we can update the config.* scripts.
4 # If we're in CT_LIB_DIR, then CT_LIB_DIR == CT_TOP_DIR, and we can update those
5 # scripts for later inclusion mainline. If CT_LIB_DIR != CT_TOP_DIR, then those
6 # scripts are downloaded only for use in CT_TOP_DIR.
8 CONFIG_SUB_SRC="http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.sub;hb=HEAD"
9 CONFIG_SUB_DEST="$(CT_TOP_DIR)/tools/config.sub"
10 CONFIG_GUESS_SRC="http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD"
11 CONFIG_GUESS_DEST="$(CT_TOP_DIR)/tools/config.guess"
14 @mkdir -p $(CT_TOP_DIR)/tools
17 updatetools: $(CT_TOP_DIR)/tools $(CONFIG_SUB_DEST) $(CONFIG_GUESS_DEST)
20 @wget $(CONFIG_SUB_SRC) -O $@
21 @chmod u+rwx,go+rx-w $@
24 @wget $(CONFIG_GUESS_SRC) -O $@
25 @chmod u+rwx,go+rx-w $@
28 @echo ' updatetools - Update the config tools'
31 @[ $(CT_TOP_DIR) = $(CT_LIB_DIR) ] || rm -rf $(CT_TOP_DIR)/tools