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 ../sysdeps/generic/wordexp.c: In function 'exec_comm':
2 ../sysdeps/generic/wordexp.c:815: sorry, unimplemented: inlining failed in call to 'exec_comm_child': function body not available
3 ../sysdeps/generic/wordexp.c:900: sorry, unimplemented: called from here
4 make[2]: *** [/home/dank/queue/jobdir.fast2/crosstool-dev/build/i686-unknown-linux-gnu/gcc-4.0-20050305-glibc-2.3-20050307/build-glibc/posix/wordexp.o] Error
6 I had to add the keyword 'inline' to get it to compile:
8 --- glibc-2.3-20050307/sysdeps/generic/wordexp.c.old 2005-03-12 08:54:15.709253928 -0800
9 +++ glibc-2.3-20050307/sysdeps/generic/wordexp.c 2005-03-12 08:54:51.242852000 -0800
13 /* Function called by child process in exec_comm() */
16 internal_function __attribute__ ((always_inline))
17 exec_comm_child (char *comm, int *fildes, int showerr, int noexec)
21 Signed-off-by: Robert P. J. Day <rpjday@mindspring.com>