--- Robert Collins <[EMAIL PROTECTED]> wrote: > > > > -----Original Message----- > > From: Danny Smith [mailto:[EMAIL PROTECTED]] > > Sent: Saturday, May 11, 2002 12:03 PM > > > Known problem which will not be solved until the exception > > handling mechansim > > of libgcc.a lives in a .dll What happens is that there are > > too copies of the exception handling code. > > So, if I understand this correctly: > > fully static builds (such as cygwin's setup.exe) will need a libgcc.a > exception handling code, but dynamically linked builds will need to link > against a cyggcc-3.dll that all the C++ .dll's link against, that has > the exception handling code. > > Rob > Something like. The app that catches a dll-thrown exception will of course also need to link against cyggcc-3.dll
If a dll catches its own exceptions, can use a static libgcc.a. libgcc.a contains the generic EH code. My tests with gcc-3 indicates that I probably also need a part of libsupc++.a (a convenience lib when building libstdc++.a. ) for C++ Likewise, for ObjC, need libobjc.dll. Danny http://messenger.yahoo.com.au - Yahoo! Messenger - A great way to communicate long-distance for FREE! _______________________________________________ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
