Have the glibc build use the cross-objdump, rather than the host one.
On some distros (eg. Fedora), the native objdump can not interpret objects not for the native system, and thus fail.
This commit adds a new patch against glibc-2.7 that introduces OBJDUMP_FOR_HOST, wich, if set, overides the detected objdump.
Note: bizarely enough, glibc already has code to detect the cross-objdump, but that does not work for an unknown reason... :-(
/trunk/patches/glibc/2.7/220-objdump_for_host.patch | 13 13 0 0 +++++++++
/trunk/scripts/build/libc_glibc.sh | 37 21 16 0 +++++++++++++++------------
2 files changed, 34 insertions(+), 16 deletions(-)
1 # Options related to how the build behaves
3 comment "Build behavior"
7 prompt "Number of parallel jobs"
10 Number of jobs make will be allowed to run concurently.
11 Set this higher than the number of processors you have, but not too high.
12 A good rule of thumb is twice the number of processors you have.
14 Enter 1 (or 0) to have only one job at a time.
18 prompt "Maximum allowed load"
21 Specifies that no new jobs should be started if there are others jobs
22 running and the load average is at least this value.
24 Makes sense on SMP machines only.
26 Enter 0 to have no limit on the load average.
28 Note: only the integer part of the load is allowed here (you can't enter
37 Renices the build process up.
44 Use gcc's option -pipe to use pipes rather than temp files when building