https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82141
--- Comment #33 from simon at pushface dot org --- (In reply to Iain Sandoe from comment #32) > it doesn't make any difference if the libstdc++ is statically or dynamically > linked, in fact It’s libgcc that causes the problem; with static libgcc, putting -lSystem before -lgcc gets the proper unwinder (well, a _working_ unwinder, anyway). The problem with a dynamic libstdc++ (up to at least GCC7) is that, in stage 2, the stage 1 compilers try to load against libstdc++ in the to-be-installed location, fail, and try to load against the system libstdc++, which is missing a required symbol.
