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 Make psignal prototype in libiberty match that in glibc.
5 gcc-2.95.3-glibc-2.1.3/binutils-2.15/libiberty/strsignal.c: In function `psignal':
6 gcc-2.95.3-glibc-2.1.3/binutils-2.15/libiberty/strsignal.c:563: argument `signo' doesn't match prototype
7 /usr/include/signal.h:131: prototype declaration
8 gcc-2.95.3-glibc-2.1.3/binutils-2.15/libiberty/strsignal.c:563: argument `message' doesn't match prototype
9 /usr/include/signal.h:131: prototype declaration
10 gcc-2.95.3-glibc-2.1.3/binutils-2.15/libiberty/strsignal.c:568: warning: comparison between signed and unsigned
11 mprotect... make[1]: *** [strsignal.o] Error 1
12 make[1]: Leaving directory `/export/hda3/dkegel/queue/jobdir.produser_cpsm17/crosstool-0.32/build/i686-unknown-linux-gnu/gcc-2.95.3-glibc-2.1.3/build-binutils/libiberty'
13 make: *** [all-libiberty] Error 2
15 when building on red hat 7.1
16 though it's a bit of a mystery why libiberty's psignal is being compiled at
17 all, since red hat 7.1's glibc supports psignal (hence the error message)
19 --- binutils-2.17/libiberty/strsignal.c.old 2005-04-18 13:57:40.000000000 -0700
20 +++ binutils-2.17/libiberty/strsignal.c 2005-04-18 13:59:09.000000000 -0700
25 -@deftypefn Supplemental void psignal (unsigned @var{signo}, char *@var{message})
26 +@deftypefn Supplemental void psignal (int @var{signo}, const char *@var{message})
28 Print @var{message} to the standard error, followed by a colon,
29 followed by the description of the signal specified by @var{signo},