search for: cxx1zflags

...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 = When CXX_STD contains any other unsupported value (e.g. CXX24) R simply falls back on the default CXX configuration. The same should probably happen for e.g. CXX17 when CXX1Z is unset in Makeconf?

...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 Linux. I think the problem is that Makeconf | contains e.g: | | CXX1Z = | CXX1ZFLAGS = | CXX1ZPICFLAGS = | CXX1ZSTD = | | When CXX_STD contains any other unsupported value (e.g. CXX24) R | simply falls back on the default CXX configuration. The same should | probably happen for e.g. CXX17 when CXX1Z is unset in Makeconf? Probably. Dirk -- http://dirk.eddelbuettel.com | @eddelb...

...//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 Linux. I think the problem is that Makeconf | contains e.g: | | CXX1Z = | CXX1ZFLAGS = | CXX1ZPICFLAGS = | CXX1ZSTD = | | When CXX_STD contains any other unsupported value (e.g. CXX24) R | simply falls back on the default CXX configuration. The same should | probably happen for e.g. CXX17 when CXX1Z is unset in Makeconf? Probably. Dirk -- http://dirk.eddelbuettel.com | @eddelbue...