------- 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
