I'd argue that libgcc is safe to statically link though. The only downside of statically linking libgcc, as long as you keep your symbol visibility sane, i.e.

I'd argue that libgcc is safe to statically link though. The only downside of statically linking libgcc, as long as you keep your symbol visibility sane, i.e. not re-exporting everything which is unfortunately the default :(, is C++ exception across shared library boundary is not guaranteed to work. But if you are trying to make your library portable across different distro, having C++ thing in your external interface is never a good idea. Especially when you statically link libstdc++.