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_8.orig/Makefile duma_2_5_8/Makefile
2 --- duma_2_5_8.orig/Makefile 2007-09-07 21:57:45.000000000 +0200
3 +++ duma_2_5_8/Makefile 2007-09-07 21:58:35.000000000 +0200
5 dumatest.c tstheap.c testmt.c dumatestpp.cpp testoperators.cpp \
8 -OBJECTS = dumapp.o duma.o sem_inc.o print.o
9 +OBJECTS = duma.o sem_inc.o print.o
10 +SO_OBJECTS = duma_so.o sem_inc_so.o print_so.o
12 -SO_OBJECTS = dumapp_so.o duma_so.o sem_inc_so.o print_so.o
15 +SO_OBJECTS += dumapp_so.o
18 all: libduma.a tstheap$(EXEPOSTFIX) dumatest$(EXEPOSTFIX) testmt$(EXEPOSTFIX) dumatestpp$(EXEPOSTFIX) testoperators$(EXEPOSTFIX) $(DUMA_DYN_DEPS)