search for: r8gg703oqsq5

...E}/etc/Makeconf" (rather than falling back on default CXX). Therefore specifying e.g CXX_STD= CXX14 will fail build with cryptic errors (due to compiling with CXX="") I don't think this is intended? Some examples from r-devel on Windows: CXX11: https://win-builder.r-project.org/R8gg703OQSq5/ CXX98: https://win-builder.r-project.org/mpVfXxk79FaN/ CXX14: https://win-builder.r-project.org/L3BSMgAk4cQ7/ CXX17: https://win-builder.r-project.org/3ETZXrgkg77I/ Similar problems appear on Linux. I think the problem is that Makeconf contains e.g: CXX1Z = CXX1ZFLAGS = CXX1ZPICFLAGS = CXX1ZSTD...

...at depends of course on the compiler found on the system. On my box (with g++ being g++-6.2 which _defaults_ to C++14) all is well up to CXX1Y. But I also have CXX1Z empty. | I don't think this is intended? Some examples from r-devel on Windows: | | CXX11: https://win-builder.r-project.org/R8gg703OQSq5/ | CXX98: https://win-builder.r-project.org/mpVfXxk79FaN/ | CXX14: https://win-builder.r-project.org/L3BSMgAk4cQ7/ | CXX17: https://win-builder.r-project.org/3ETZXrgkg77I/ You can't expect CXX14 and CXX17 to work with the only available compiler there, g++-4.9.3. | Similar problems appear on...

...That depends of course on the compiler found on the system. On my box (with g++ being g++-6.2 which _defaults_ to C++14) all is well up to CXX1Y. But I also have CXX1Z empty. | I don't think this is intended? Some examples from r-devel on Windows: | | CXX11: https://win-builder.r-project.org/R8gg703OQSq5/ | CXX98: https://win-builder.r-project.org/mpVfXxk79FaN/ | CXX14: https://win-builder.r-project.org/L3BSMgAk4cQ7/ | CXX17: https://win-builder.r-project.org/3ETZXrgkg77I/ You can't expect CXX14 and CXX17 to work with the only available compiler there, g++-4.9.3. | Similar problems appear on...