On Sat, 11 May 2002, Robert Collins wrote:
> > Robert -- what's the deal with C++ and exceptions under cygwin, again?
>
> Single thread C++ programs should work fine. Exceptions from .dll's
> -may- be problematic. Danny knows more about this aspect than I do. He
> posted a summary message about gc
> -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 .dllWhat happens is that there are
> too copies of the exception
--- Robert Collins <[EMAIL PROTECTED]> wrote: > Danny, I hope you
don't object to being copied in...
>
> > -Original Message-
> > From: Charles Wilson [mailto:[EMAIL PROTECTED]]
> > Sent: Saturday, May 11, 2002 7:49 AM
> > To: Bob Friesenhahn
> > Cc: [EMAIL PROTECTED]; Robert Collins
>
Danny, I hope you don't object to being copied in...
> -Original Message-
> From: Charles Wilson [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, May 11, 2002 7:49 AM
> To: Bob Friesenhahn
> Cc: [EMAIL PROTECTED]; Robert Collins
> Subject: Re: C++ exceptions don't work from Cygwin DLLs?
>
>
Libtool has been driving me nuts. I tried to cross compile a package which
uses libtool. For some reason, libtool wanted libgdbm.so from /usr/lib:
/bin/sh ../libtool --mode=link mipsel-linux-gcc -Wall -W -O2 -mips2 -fPIC -o
libsasl.la -rpath /usr/lib -version-info 8:8:1 common.lo saslutil.lo s
Bob Friesenhahn wrote:
> I am attempting to get ImageMagick to work properly using Cygwin DLLs.
> The C++ component is built as a DLL using the binutils auto-import
> feature and CVS libtool. The library works fine with the glaring
> exception that any C++ exception thrown from the library cause
Charles,
I am attempting to get ImageMagick to work properly using Cygwin DLLs.
The C++ component is built as a DLL using the binutils auto-import
feature and CVS libtool. The library works fine with the glaring
exception that any C++ exception thrown from the library causes an
immediate core du
Hi there,
I have aproject where I would like to use AC_DISABLE_SHARED so that
not building shared libraries is the default. Of course, this is ideal
for development and debugging but there is a problem: the `make check'
target in one of the project's subdirectories requires building a shared
li