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 Fix building gfortran for ARM.
2 http://gcc.gnu.org/ml/gcc-patches/2007-05/msg01010.html
5 The patch below fixes a crash building libgfortran on arm-linux-gnueabi.
7 This target doesn't really have a 128-bit integer type, however it does use
8 TImode to represent the return value of certain special ABI defined library
9 functions. This results in type_for_size(TImode) being called.
11 Because TImode deosn't correspond to any gfortran integer kind
12 gfc_type_for_size returns NULL and we segfault shortly after.
14 The patch below fixes this by making gfc_type_for_size handle TImode in the
15 same way as the C frontend.
17 Tested on x86_64-linux and arm-linux-gnueabi.
22 2007-05-15 Paul Brook <paul@codesourcery.com>
25 * trans-types.c (gfc_type_for_size): Handle signed TImode.
27 diff -durN gcc-4.2.3.old/gcc/fortran/trans-types.c gcc-4.2.3/gcc/fortran/trans-types.c
28 --- gcc-4.2.3.old/gcc/fortran/trans-types.c 2007-08-31 10:27:50.000000000 +0200
29 +++ gcc-4.2.3/gcc/fortran/trans-types.c 2008-07-17 09:54:20.000000000 +0200
30 @@ -1799,6 +1799,13 @@
31 if (type && bits == TYPE_PRECISION (type))
35 + /* Handle TImode as a special case because it is used by some backends
36 + (eg. ARM) even though it is not available for normal use. */
37 +#if HOST_BITS_PER_WIDE_INT >= 64
38 + if (bits == TYPE_PRECISION (intTI_type_node))
39 + return intTI_type_node;