From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12694 invoked by alias); 2 May 2005 11:10:22 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 12642 invoked by uid 48); 2 May 2005 11:10:16 -0000 Date: Mon, 02 May 2005 11:10:00 -0000 Message-ID: <20050502111016.12640.qmail@sourceware.org> From: "info at yourkit dot com" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20050429073316.21277.info@yourkit.com> References: <20050429073316.21277.info@yourkit.com> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug target/21277] Runtime error with C++ shared library and --disable-shared X-Bugzilla-Reason: CC X-SW-Source: 2005-05/txt/msg00230.txt.bz2 List-Id: ------- 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