Thanks! That looks relevant. I think I have found the relevant source code in pandoc, and it seems it just calls Rscript without path. So it will probably call the dummy Rscript. Hmm, I'll have to think how to fix that. It is probably good that R CMD check checks this as this could cause weird errors when people have multiple versions of R on their system. Best, Jan
On 30-09-2021 18:59, Ivan Krylov wrote:
On Fri, 24 Sep 2021 21:48:12 +0200 Jan van der Laan <rhelp at eoos.dds.nl> wrote:
my tests run fine when run with R CMD check, but not with R CMD check --as-cran
<...>
pandoc then calls R again with a script which is part of the package
Part of R CMD check --as-cran is placing fake R and Rscript executables on the PATH (but currently not on Windows): https://github.com/r-devel/r-svn/blob/98f33a2a7b22f400d51220162cf400a0cfdc9aaf/src/library/tools/R/check.R#L279 https://github.com/r-devel/r-svn/blob/98f33a2a7b22f400d51220162cf400a0cfdc9aaf/src/library/tools/R/check.R#L6297-L6323 Does the pandoc script use the R_HOME variable to call the correct R executable?