On Oct 22, 2012, at 11:05 AM, Cody Permann <codyperm...@gmail.com> wrote:
> > I like the "include both, selectable at configure-time" option best, > if it's not too much work for Cody. In exchange I can finally get > around to reproducing/fixing that Nemesis regression he found... > > Sounds good to me! Based on my result table that I sent a few minutes ago I > think we're all ready to be done with this issue. For us, using the release > package will fix all of these issues. Only the truly hardcore will want to > mess with the development version anyway. I hate to bring this up, but fparser is broken with gcc-4.7 using -std=c++0x. On trunk, in m4/configure.m4 we add -std=c++0x only for gcc-4.3 (erroneously?). if you update that switch statement to add the flag for gcc-4.7, fparser breaks. Cody, could you verify on your system? This gets to the larger question of when we will require C++11, which in my mind is probably a good year or so from now. In the meantime, should we bother trying to track partially implemented subsets? -Ben ------------------------------------------------------------------------------ The Windows 8 Center - In partnership with Sourceforge Your idea - your app - 30 days. Get started! http://windows8center.sourceforge.net/ what-html-developers-need-to-know-about-coding-windows-8-metro-style-apps/ _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
