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 # Taken from http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/config.gcc.diff?r1=1.91&r2=1.92
3 # Configuration x86_64-host_unknown-linux-gnu not supported
4 # when configuring gcc-2.95 on x86_64 build for i686 target
5 # It's a bit silly, since tm_file refers to files that don't exist,
6 # but as long as x86_64 is just the build machine, that doesn't matter.
8 --- gcc-2.95.3/gcc/configure.old 2004-03-24 12:17:44.000000000 -0800
9 +++ gcc-2.95.3/gcc/configure 2004-03-24 12:19:30.000000000 -0800
20 @@ -3643,6 +3646,19 @@
26 + tm_file="i386/biarch64.h i386/i386.h i386/att.h linux.h i386/x86-64.h \
28 + tmake_file="t-slibgcc-elf-ver t-linux i386/t-crtstuff"
29 + extra_parts="crtbegin.o crtbeginS.o crtend.o crtendS.o"
32 + if test x$enable_threads = xyes; then