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 comment "eglibc specific options"
7 prompt "eglibc version"
25 # CT_INSERT_VERSION_ABOVE
26 # Don't remove above line!
32 Selecting this will export the trunk of the eglibc subversion repository.
38 default "trunk" if EGLIBC_V_TRUNK
39 default "2_5" if EGLIBC_V_2_5
40 default "2_6" if EGLIBC_V_2_6
41 default "2_7" if EGLIBC_V_2_7
42 default "2_8" if EGLIBC_V_2_8
43 # CT_INSERT_VERSION_STRING_ABOVE
44 # Don't remove above line!
46 config EGLIBC_REVISION
48 prompt "Revision to use"
51 Enter the revision of trunk you want to use.
54 A revision argument can be one of:
55 NUMBER revision number
56 '{' DATE '}' revision at start of the date (*)
57 'HEAD' latest in repository
59 (*) If you want to use a date, please use ISO-8601 formats if
62 config EGLIBC_CHECKOUT
64 prompt "checkout instead of export"
65 default y if EGLIBC_V_TRUNK
66 default n if ! EGLIBC_V_TRUNK
68 By default, the eglibc download will be an export of the subversion
69 repository. If you say 'y' here, then the repository will instead be
70 checked-out, so that you can update it later.
72 Note that crosstool-NG will *not* update your working copy, you will
73 have to do that yourself.