https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80658
--- Comment #11 from Bernd Paysan <bernd at net2o dot de> --- (In reply to Jonathan Wakely from comment #10) > > which he need to disable first > > (after a coworker had enabled it somewhere in the source code): > > Where did you get that information? The blog post says nothing about a > coworker enabling mt_allocator, it strongly implies that the mt allocator > pooling is on by default and is why libstdc++ is "broken". My guess. He mentions that he's not a lone wolf coder, and since he didn't understand why mt_allocator was active, I guessed that a coworker had enabled it ;-). There's no trace at all of ext/mt_allocator in the source code on github, but in a crappy project, you never know if they build from the sources they released to github. However, with the CPP/CXX change of the environment variable: The minimal GCC version that builds this project is GCC 4.9... or clang 3.9, which it prefers to use on build if both gcc and clang are available. So it can't use a too old libstdc++.
