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 http://mirror.sh-linux.org/rpm-2003/SRPMS/gcc-3.2.3-3.src.rpm contains the following patches:
3 gcc-20030210-sh-linux-1.patch
4 gcc-3.2.3-libffi-1.patch
5 gcc-3.2.3-sh-linux-dwarf2-1.patch (*not* applied by the spec file, it's in there by accident)
7 gcc-3.2.3-libffi-1.patch was needed just to build, I think.
9 After that was applied, sh4 gcc seemed to compile fine, but c++ programs
10 failed to execute because libstdc++.so.5 was built without version
11 info. This was caused directly by libstdc++-v3/configure setting
12 SYMVER_MAP=config/linker-map.dummy because it sees that
13 no libgcc_s.so was generated; configure says
14 checking for shared libgcc... no.
16 Applying gcc-20030210-sh-linux-1.patch in hopes it makes those problems go away.