This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/21277] Runtime error with C++ shared library and --disable-shared
- From: "info at yourkit dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 2 May 2005 11:10:16 -0000
- Subject: [Bug target/21277] Runtime error with C++ shared library and --disable-shared
- References: <20050429073316.21277.info@yourkit.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From info at yourkit dot com 2005-05-02 11:10 -------
> > Thanks a lot, Eric!
> Andrew deserves them too.
No doubt :) I'm sorry.
> And, again, not using a shared libgcc on
Solaris means that exceptions cannot be propagated across shared libraries;
that's why g++ automatically passes -shared-libgcc on Solaris.
Just curious: where can I get more information about this issue? We were linking
our shared library statically with libgcc_eh.a in the past with no problems,
and many people on different machines successfully used it. Should there be any
problems? By the way, all these tricks were found googling reports of other
people who wanted to link statically.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21277