https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #16 from Jürgen Reuter <juergen.reuter at desy dot de> --- Yes, after the problem occurred, I did a completely clean new build of gmp, mpfr, mpc, gcc (configured with ../configure --prefix=/usr/local/ --with-gmp=/usr/local/ --with-mpfr=/usr/local/ --with-mpc=/usr/local/ --enable-checking=release --enable-languages=c,c++,fortran,lto), all the tools our software depends, and our software. It turns out that external C++ libraries linked into our (Fortran) project via bind(C) are not a problem if they have been built via libtool, such that a .dylib, a .a and a .la file are present. The two projects that have problem either exist as .dylib and .a produced by hand-written configure and makefiles (i.e. not using autotools), or only as dynamic libraries produced via cmake and make.
