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 --- gcc-4.2.1-stock/gcc/config/alpha/linux-unwind.h 2005-06-24 20:22:41.000000000 -0500
2 +++ gcc-4.2.1/gcc/config/alpha/linux-unwind.h 2007-09-01 20:21:34.000000000 -0500
3 @@ -29,6 +29,9 @@ Boston, MA 02110-1301, USA. */
4 /* Do code reading to identify a signal frame, and set the frame
5 state data appropriately. See unwind-dw2.c for the structs. */
7 +/* Don't use this if inhibit_libc is set
8 + The build for this target will fail trying to include missing headers */
11 #include <sys/ucontext.h>
13 @@ -80,3 +83,4 @@ alpha_fallback_frame_state (struct _Unwi
14 fs->retaddr_column = 64;
15 return _URC_NO_REASON;
17 +#endif /* inhibit_libc */