https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123220
--- Comment #2 from Pierre Ossman <ossman at cendio dot se> --- Thanks. Unfortunately, that doesn't give us the type of robustness we'd like. We generally try to make sure we don't depend on "special" builds of the build tools, as it can make it easier to overlook things and make it difficult to change things. Another flag that affects just the build of gcc itself, not the output of gcc, would be what we'd like. That said, how does the flag --enable-default-ssp actually work when it comes to the build of libstdc++? I would assume it would run in to the same issues as when setting LDFLAGS_FOR_TARGET?
