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(-)

 diff -dur duma_2_5_1.orig/Makefile duma_2_5_1/Makefile

 --- duma_2_5_1.orig/Makefile	2007-07-11 17:49:43.000000000 +0200

 +++ duma_2_5_1/Makefile	2007-07-11 17:50:46.000000000 +0200

 @@ -115,9 +115,14 @@

  	dumatest.c tstheap.c dumatestpp.cpp testoperators.cpp \

  	createconf.c

 -OBJECTS = dumapp.o duma.o sem_inc.o print.o

 +OBJECTS = duma.o sem_inc.o print.o

 +SO_OBJECTS = duma_so.o sem_inc_so.o print_so.o

 +

 +ifeq ($(DUMA_CPP),1)

 +OBJECTS += dumapp.o

 +SO_OBJECTS += dumapp_so.o

 +endif

 -SO_OBJECTS = dumapp_so.o duma_so.o sem_inc_so.o print_so.o

  all:	libduma.a $(DUMASO) tstheap dumatest dumatestpp testoperators tstheap_so dumatestpp_so

  	@ echo "Testing DUMA."