search for: cxxstd

...flag as well (although that should be reserved for C++14) and it did not help. I can probably force it by adding it to the CXXFLAGS and CXX1XFLAGS in Makeconf, but that seems to be somewhat overkill and may have downstream effects of which I am unaware. Am I correct in my assumption that the new CXXSTD macro as discussed in the changelogs is automatically setting GCC 4.9.3 to C++98, and if so, is there a similar way to R-3.3 to have GCC default to gnu++11 outside of forcing it in the general flags? If I am incorrect, I would appreciate being pointed in the proper direction. Thank you, Avi

...for an external LAPACK has been reduced to 3.9.0. * No default C++ compiler is set if no C++17 compiler is detected: there is no longer an automatic fallback to C++14 or C++11. Compilers from the last five years should have sufficient support: for others macros CXX and CXXSTD can be set in file config.site to provide a fallback if needed. The Objective-C++ compiler now by default uses the standard selected by R for C++ (currently C++17) rather than the default standard for the C++ compiler (which on macOS is still C++98). INSTALLATION on macO...

...for an external LAPACK has been reduced to 3.9.0. * No default C++ compiler is set if no C++17 compiler is detected: there is no longer an automatic fallback to C++14 or C++11. Compilers from the last five years should have sufficient support: for others macros CXX and CXXSTD can be set in file config.site to provide a fallback if needed. The Objective-C++ compiler now by default uses the standard selected by R for C++ (currently C++17) rather than the default standard for the C++ compiler (which on macOS is still C++98). INSTALLATION on macO...