https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #25 from Jürgen Reuter <juergen.reuter at desy dot de> --- (In reply to Richard Biener from comment #24) > (In reply to Iain Sandoe from comment #23) > > (In reply to Jürgen Reuter from comment #22) > > Indeed - somehow you didn't get a statically linked executable. Quoting the > full final link command would be interesting. The full link commands can be found here, I believe: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750#c14 Our code generates code for particle physics simulations in the form of dynamic libraries that get linked and loaded. For batch clusters, we attempted to provide static binaries for these simulations, however, we have order 10-15 external libraries that can be linked to our code (which are partially mandatory). There are some of them which only exist as dynamic libraries, so there our approach cannot result in a purely static binary. The static stdc++ library is sucked in via the libtool link mode/flag -static-libtool-libs while the dynamic ones are sucked in via the external C++ libraries that are available only dynamically.