Re: -static-libgcc, static libstdc++.a, dynamically loaded so files and exception handling.

[Ian Lance Taylor <iant at google dot com>]

Bob Rossi <bob@brasko.net> writes:

> So, we've described how static linking isn't always safe for libgcc. I've
> also described how I have shared objectcs that I load at run time. These
> libraries depend on libgcc as well. I build the software on an old linux
> machine, with a new version of GCC. So I've got a relative new version
> of libgcc. I'm thinking about distributing my libgcc_so using the linker
> rpath solution, using ORIGIN to make it relative to the executable.
>
> Does it make sense to distribute my newer version of libgcc with my
> executables in this way?

Yes.

Ian