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(-)
3 In file included from gthr-default.h:1,
4 from /build/arm-unknown-linux-gnu/gcc-2.95.3-glibc-2.2.2/gcc-2.95.3/gcc/gthr.h:98,
5 from /build/arm-unknown-linux-gnu/gcc-2.95.3-glibc-2.2.2/gcc-2.95.3/gcc/libgcc2.c:3034:
6 /build/arm-unknown-linux-gnu/gcc-2.95.3-glibc-2.2.2/gcc-2.95.3/gcc/gthr-posix.h:37: pthread.h: No such file or directory
7 make[3]: *** [libgcc2.a] Error 1
8 make[3]: Leaving directory `/build/arm-unknown-linux-gnu/gcc-2.95.3-glibc-2.2.2/build-gcc-core/gcc'
10 in what I think is a nicer way than the patch used by the arm team,
11 i.e. "perl -pi -e 's/^(TARGET_LIBGCC2_CFLAGS.*)/$1 -Dinhibit_libc -D__gthr_posix_h/' gcc/config/arm/t-linux"
12 which seems a bit of a kludge.
14 --- gcc-2.95.3/gcc/configure.old Fri Mar 16 06:13:48 2001
15 +++ gcc-2.95.3/gcc/configure Sun Jun 8 13:02:20 2003
17 # Check whether --enable-threads or --disable-threads was given.
18 if test "${enable_threads+set}" = set; then
19 enableval="$enable_threads"
20 - if test x$enable_threads = xno; then
23 + #if test x$enable_threads = xno; then