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 Correctly check for g++ existence.
3 Copyright 2007 Yann E. MORIN <yann.morin.1998@anciens.enib.fr>
4 Licensed to you as dmalloc-5.5.2 is.
6 diff -dur dmalloc-5.5.2.orig/configure dmalloc-5.5.2/configure
7 --- dmalloc-5.5.2.orig/configure 2007-05-18 11:40:31.000000000 +0200
8 +++ dmalloc-5.5.2/configure 2007-05-18 11:42:02.000000000 +0200
12 # see if we actually have a CXX program
13 -if test "$ac_cv_prog_CXX" = "" -o ! -x "$ac_cv_prog_CXX"; then
14 +if test "$ac_cv_prog_CXX" = "" -o ! -x `which "$ac_cv_prog_CXX"`; then
15 { echo "$as_me:$LINENO: WARNING: could not find C++ compiler $ac_cv_prog_CXX" >&5
16 echo "$as_me: WARNING: could not find C++ compiler $ac_cv_prog_CXX" >&2;}