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 Message-ID: <000801c48f60$cec16630$9103a8c0@ULOC5012>
2 From: "Michael Geiger" <mcgege@gmx.de>
4 Subject: Patch for cross compiling s/390 kernel on linux host
5 Date: Tue, 31 Aug 2004 15:45:41 +0200
9 I had big problems compiling a kernel for s/390 on my linux host - I tried
10 different chains from crosstool-0.28-rc34 and finally succeded with
11 gcc-3.3.4-glibc-2.3.2 after applying another patch to binutils-2.15
13 All compilations of the different kernel versions I tried stopped with
14 "Invalid .insn format" somewhere. I checked the recent cvs version of
15 binutils and applied the latest diff to gas/config/tc-s390.c and that solved
24 --- src/gas/config/tc-s390.c 2004/05/06 11:01:48 1.39
25 +++ src/gas/config/tc-s390.c 2004/06/15 12:38:08 1.40
26 @@ -1596,13 +1596,13 @@
27 if (exp.X_op == O_constant)
29 if ( ( opformat->oplen == 6
30 - && exp.X_add_number >= 0
31 + && (addressT) exp.X_add_number >= 0
32 && (addressT) exp.X_add_number < (1ULL << 48))
33 || ( opformat->oplen == 4
34 - && exp.X_add_number >= 0
35 + && (addressT) exp.X_add_number >= 0
36 && (addressT) exp.X_add_number < (1ULL << 32))
37 || ( opformat->oplen == 2
38 - && exp.X_add_number >= 0
39 + && (addressT) exp.X_add_number >= 0
40 && (addressT) exp.X_add_number < (1ULL << 16)))
41 md_number_to_chars (insn, exp.X_add_number, opformat->oplen);