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(-)
2 # Yes, this intends to be a true POSIX script file.
8 Usage: ${myname} <dir> <base> <inc>
9 Will renumber all patches found in <dir>, starting at <base>, and with
11 Eg.: patch-renumber patches/gcc/4.3.1 100 10
15 [ $# -eq 3 ] || { doUsage; exit 1; }
16 [ -d "${1}" ] || { doUsage; exit 1; }
22 case $(LC_ALL=C svnversion 2>/dev/null) in
23 exported) CMD="mv -v";;
27 for p in "${dir}"/*.patch; do
28 [ -e "${p}" ] || { echo "No such file '${p}'"; exit 1; }
29 newname="$(printf "%03d" ${cpt})-$(basename "${p}" |sed -r -e 's/^[[:digit:]]{3}-//')"
30 [ "${p}" = "${dir}/${newname}" ] || ${CMD} "${p}" "${dir}/${newname}"