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.1 --- a/scripts/build/libc/glibc.sh Tue Sep 23 07:28:20 2008 +0000
1.2 +++ b/scripts/build/libc/glibc.sh Tue Sep 23 14:48:10 2008 +0000
1.3 @@ -489,13 +489,7 @@
1.4
1.5 # Fix problems in linker scripts.
1.6 #
1.7 - # 1. Remove absolute paths
1.8 - # Any file in a list of known suspects that isn't a symlink is assumed to be a linker script.
1.9 - # FIXME: test -h is not portable
1.10 - # FIXME: probably need to check more files than just these three...
1.11 - # Need to use sed instead of just assuming we know what's in libc.so because otherwise alpha breaks
1.12 - #
1.13 - # 2. Remove lines containing BUG per http://sources.redhat.com/ml/bug-glibc/2003-05/msg00055.html,
1.14 + # Remove lines containing BUG per http://sources.redhat.com/ml/bug-glibc/2003-05/msg00055.html,
1.15 # needed to fix gcc-3.2.3/glibc-2.3.2 targeting arm
1.16 #
1.17 # To make "strip *.so.*" not fail (ptxdist does this), rename to .so_orig rather than .so.orig
1.18 @@ -505,11 +499,7 @@
1.19 if [ -f "${CT_SYSROOT_DIR}/${dir}/${file}" -a ! -L ${CT_SYSROOT_DIR}/$lib/$file ]; then
1.20 CT_DoExecLog ALL cp -v "${CT_SYSROOT_DIR}/${dir}/${file}" "${CT_SYSROOT_DIR}/${dir}/${file}_orig"
1.21 CT_DoLog DEBUG "Fixing '${CT_SYS_ROOT_DIR}/${dir}/${file}'"
1.22 - CT_DoExecLog ALL sed -i -r -e 's,/usr/lib/,,g;
1.23 - s,/usr/lib64/,,g;
1.24 - s,/lib/,,g;
1.25 - s,/lib64/,,g;
1.26 - /BUG in libc.scripts.output-format.sed/d' "${CT_SYSROOT_DIR}/${dir}/${file}"
1.27 + CT_DoExecLog ALL sed -i -r -e '/BUG in libc.scripts.output-format.sed/d' "${CT_SYSROOT_DIR}/${dir}/${file}"
1.28 fi
1.29 done
1.30 done