This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/41605] Static linking of libgcc/libgfortran/libstdc++ can cause inconsistent symbol resolution.
- From: "developer at sandoe-acoustics dot co dot uk" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 14 Oct 2009 11:20:04 -0000
- Subject: [Bug target/41605] Static linking of libgcc/libgfortran/libstdc++ can cause inconsistent symbol resolution.
- References: <bug-41605-17110@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #5 from developer at sandoe-acoustics dot co dot uk 2009-10-14 11:20 -------
(In reply to comment #4)
> Oh, if one wanted to, one could have libgcc_s forward the EH calls into
> /usr/lib/libgcc_s.1.dylib by dlopening it and then doing dlsym on the symbols
> and calling them. This would `fix' the programs that linked against a gcc
> libgcc_s file that uses EH when run on a system that has EH on the system.
> With that technology, I think all the mismatching here, just goes away.
note1: the dependent fixes for static-libstdc++ are 41594/41596.
Would you accept the solution proposed here as suitable at present?
Noting that eh forwarding could be a useful enhancement at some future time?
Even with potential forwarding of eh it is still desirable to enable a
statically linked executable for those cases where such is useful [excepting
that libSystem is always dynamic].
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41605