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 Signed-off-by: dank@kegel.com
3 Raising the size of the hash table is a noticable win when linking
4 at least one large app.
7 http://sources.redhat.com/ml/binutils/2004-06/msg00165.html
8 to do this dynamically. No idea why that didn't make it in.
9 So this tiny change to raise the default size is just
13 --- binutils-2.17/bfd/hash.c.old 2006-03-02 23:01:39.000000000 -0800
14 +++ binutils-2.17/bfd/hash.c 2006-03-02 23:01:58.000000000 -0800
18 /* The default number of entries to use when creating a hash table. */
19 -#define DEFAULT_SIZE 4051
20 +#define DEFAULT_SIZE 32749
21 static size_t bfd_default_hash_table_size = DEFAULT_SIZE;
23 /* Create a new hash table, given a number of entries. */