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 diff -durN duma_2_5_14.orig/Makefile duma_2_5_14/Makefile
2 --- duma_2_5_14.orig/Makefile 2008-03-13 00:54:10.000000000 +0100
3 +++ duma_2_5_14/Makefile 2008-06-17 10:28:45.000000000 +0200
17 createconf$(EXEPOSTFIX): createconf.o
18 - $(RMFORCE) createconf$(EXEPOSTFIX)
19 - $(CC) $(CFLAGS) $(DUMA_OPTIONS) createconf.o -o createconf$(EXEPOSTFIX)
20 + $(HOSTCC) $(HOSTCFLAGS) $(DUMA_OPTIONS) createconf.o -o createconf$(EXEPOSTFIX)
22 tstheap$(EXEPOSTFIX): libduma.a tstheap.o
23 - $(RMFORCE) tstheap$(EXEPOSTFIX)
25 # define rules how to build objects for createconf
28 - $(CC) $(CFLAGS) $(DUMA_OPTIONS) -c createconf.c -o $@
29 + $(HOSTCC) $(HOSTCFLAGS) $(DUMA_OPTIONS) -c createconf.c -o $@