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 Correctly check for g++ existence.
3 Copyright 2007 Yann E. MORIN <yann.morin.1998@anciens.enib.fr>
4 Licensed to you as dmalloc-5.5.2 is.
6 diff -dur dmalloc-5.5.2.orig/configure dmalloc-5.5.2/configure
7 --- dmalloc-5.5.2.orig/configure 2007-05-18 11:40:31.000000000 +0200
8 +++ dmalloc-5.5.2/configure 2007-05-18 11:42:02.000000000 +0200
12 # see if we actually have a CXX program
13 -if test "$ac_cv_prog_CXX" = "" -o ! -x "$ac_cv_prog_CXX"; then
14 +if test "$ac_cv_prog_CXX" = "" -o ! -x `which "$ac_cv_prog_CXX"`; then
15 { echo "$as_me:$LINENO: WARNING: could not find C++ compiler $ac_cv_prog_CXX" >&5
16 echo "$as_me: WARNING: could not find C++ compiler $ac_cv_prog_CXX" >&2;}