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 specific to extracting packages
7 prompt "Force extractions"
10 Force extraction of already exctracted tarballs.
12 Usefull if you suspect a previous extract did not complete (eg. broken
13 tarball), or you added a new set of patches for this component.
15 config OVERIDE_CONFIG_GUESS_SUB
17 prompt "Override config.{guess,sub}"
20 Override tools' versions of config.guess and config.sub with the ones
21 from crosstool-NG. This means that all instances of config.guess and
22 config.sub in gcc, binutils, glibc, etc... will be replaced.
24 Most of the time, the versions of those scripts found in packages are old
25 versions, thus lacking some target definitions. This is the case for
26 uClibc-based tuples in old versions of gcc and gdb, for example.
28 Also, doing so will guarantee that all components have the same tuples
29 definitions for your target, and not diverging ones.
31 You can update the ones provided with crosstool-NG by first running:
33 in the directory where you want to run crosstool-NG prior to the build.
37 prompt "Stop after extracting tarballs"
40 Exit after unpacking and patching tarballs.
42 Usefull to look at the code before doing the build itself.