This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
libgcc version breakage?
- From: Richard Zidlicky <rz at linux-m68k dot org>
- To: gcc at gcc dot gnu dot org
- Date: Mon, 8 Sep 2003 16:48:04 +0200
- Subject: libgcc version breakage?
Hello,
I recently tried gcc-3.3.1 on my m68k-linux box.
One big problem is that exception handling for
m68k changed from sjlj to eh between 3.2 and 3.3
while libgcc_s version remained the same.
Consequently all old binaries that were compiled
using c++ no longer work:
soelim:
libstdc++.so.3 => /usr/lib/libstdc++.so.3 (0xc001d000)
libm.so.6 => /lib/libm.so.6 (0xc007c000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xc009c000)
libc.so.6 => /lib/libc.so.6 (0xc00a6000)
/lib/ld.so.1 => /lib/ld.so.1 (0xc0000000)
symbol _Unwind_SjLj_Unregister, version GCC_3.0 not defined in file libgcc_s.so.
1 with link time reference (/usr/lib/libstdc++.so.3)
symbol _Unwind_SjLj_Register, version GCC_3.0 not defined in file libgcc_s.so.1
with link time reference (/usr/lib/libstdc++.so.3)
...
...
It appears that even some symbols from libstc++ are dependent on
this, for example __gxx_personality_sj0 is no longer defined.
What would be the best way to fix this?
Richard