patches/gcc/3.2.3/README-sh
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Thu Jul 31 09:08:33 2008 +0000 (2008-07-31)
changeset 752 b037a5643e04
permissions -rw-r--r--
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(-)
yann@1
     1
http://mirror.sh-linux.org/rpm-2003/SRPMS/gcc-3.2.3-3.src.rpm contains the following patches:
yann@1
     2
yann@1
     3
gcc-20030210-sh-linux-1.patch
yann@1
     4
gcc-3.2.3-libffi-1.patch
yann@1
     5
gcc-3.2.3-sh-linux-dwarf2-1.patch (*not* applied by the spec file, it's in there by accident)
yann@1
     6
yann@1
     7
gcc-3.2.3-libffi-1.patch was needed just to build, I think.
yann@1
     8
yann@1
     9
After that was applied, sh4 gcc seemed to compile fine, but c++ programs
yann@1
    10
failed to execute because libstdc++.so.5 was built without version
yann@1
    11
info.  This was caused directly by libstdc++-v3/configure setting
yann@1
    12
SYMVER_MAP=config/linker-map.dummy because it sees that 
yann@1
    13
no libgcc_s.so was generated; configure says
yann@1
    14
  checking for shared libgcc... no.
yann@1
    15
yann@1
    16
Applying gcc-20030210-sh-linux-1.patch in hopes it makes those problems go away.