On Tue, 8 Jul 2014, John Peterson wrote: > Wait, what? --disable-cxx11 is the same behavior we've had since > forever, so it can't be causing a *new* valgrind error.
No, sadly it's not what our behavior used to be, just what our behavior *should* have been. I think I had a long-open issue about this - we'd been sticking -std=c++0x in our CXXFLAGS for g++ via compiler.m4 Still *very* strange. I wouldn't have been too shocked to see a compile-time error from turning off C++11 support, but I can't imagine what would have caused a runtime error. Googling... there are some libstdc++ ABI changes in STL containers. Are we inadvertently passing lists/pairs/sets/etc between C++98 and C++11 builds? Or... perhaps --disable-cxx11 is being strict enough to turn off unordered_foo, and we have some bug that only manifests in the case of an ordered set/map/multimap? --- Roy ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
