Re: libtool 1.4.1 build failed on solaris 2.6

[Tim Van Holder]

On 07 Sep 2001 00:07:18 +0100, Gary V. Vaughan wrote:
> Thanks.  I believe I have fixed this now... although I am worried
> about unforseen conequences of linking libgcc.a into every
> -no-undefined tagged library.  Please torture it as much as you can,
> and I'll release 1.4.2 at the weekend.
IIRC from my efforts fiddling with a dynamic-loading system for DJGPP,
linking in libgcc.a with both module & executable results in two
separate exception stacks, so a C++ exception thrown in the loaded
module won't propagate into the main executable (and so will often
result in an abort()).
There may be other instances of libgcc.a containing data that should not
be duplicated; again, this may only affect C++ code.  gcc3 probably
solves this as you can now build a shared libgcc.so as well.