Re: [R-pkg-devel] Writing to files without altering working directory in R package

2019-05-03 Thread Duncan Murdoch
On 03/05/2019 6:33 p.m., Jarrett Phillips wrote: Hello, My R package has a function with an argument to specify whether numerical results should be outputted to a CSV file. CRAN policy stipulates verbatim that Packages should not write in the user’s home filespace (including clipboards), nor a

Re: [R-pkg-devel] Writing to files without altering working directory in R package

2019-05-03 Thread Uwe Ligges
On 04.05.2019 00:33, Jarrett Phillips wrote: Hello, My R package has a function with an argument to specify whether numerical results should be outputted to a CSV file. CRAN policy stipulates verbatim that Packages should not write in the user’s home filespace (including clipboards), nor an

[R-pkg-devel] Writing to files without altering working directory in R package

2019-05-03 Thread Jarrett Phillips
Hello, My R package has a function with an argument to specify whether numerical results should be outputted to a CSV file. CRAN policy stipulates verbatim that Packages should not write in the user’s home filespace (including clipboards), nor anywhere else on the file system apart from the R se

[R-pkg-devel] CRAN modifications of packages

2019-05-03 Thread Max Kuhn
I've noticed a trend in the last year of a CRAN maintainer making modifications to packages without notification to the package authors or the community. Some times these have been made during a submission [1] and, in other cases, for existing packages [2]. In the latter case, we intuit that ther

Re: [R-pkg-devel] False Positive WARNING in devtools::check_built

2019-05-03 Thread Duncan Murdoch
On 03/05/2019 10:02 a.m., Jarrett Phillips wrote: Hello, I have run devtools::check_built() on my package tarball to ensure the presence of no ERRORS/WARNINGS or NOTES. The below WARNING was found: That appears to be similar to this bug, which has been fixed in R-devel: https://bugs.r-projec

Re: [R-pkg-devel] clang: error: unsupported option '-fopenmp'

2019-05-03 Thread Peter Carbonetto
Have you seen this note (from https://cran.r-project.org/bin/macosx/)? Important: this release uses Clang 7.0.0 and GNU Fortran 6.1, neither of which is supplied by Apple. If you wish to compile R packages from sources, you will need to download and install those tools - see the tools directory.

Re: [R-pkg-devel] clang: error: unsupported option '-fopenmp'

2019-05-03 Thread Maxime Turgeon
Hi Spencer, I remember having a similar error a few years ago when trying to compile R (and its recommended packages, e.g. mgcv) from source. I was using clang as a compiler (this is what Hadley recommends in his book "R packages"), and I solved the issue by going back to g++. This can be done

[R-pkg-devel] clang: error: unsupported option '-fopenmp'

2019-05-03 Thread Spencer Graves
Hello, All:   I'm getting "clang: error: unsupported option '-fopenmp'" when trying to build "https://github.com/helske/bssm"; under macOS 10.14.14 with R 3.6.0;  see below.   What do you suggest?   Thanks,   Spencer Graves p.s.  I assume I have to install compiler(s). 

Re: [R-pkg-devel] False Positive WARNING in devtools::check_built

2019-05-03 Thread Michael Dewey
Dear Jarrett Not clear what is going on here but that seems to be an error in your source code not the documentation file as you hint. Michael On 03/05/2019 15:02, Jarrett Phillips wrote: Hello, I have run devtools::check_built() on my package tarball to ensure the presence of no ERRORS/WA

[R-pkg-devel] False Positive WARNING in devtools::check_built

2019-05-03 Thread Jarrett Phillips
Hello, I have run devtools::check_built() on my package tarball to ensure the presence of no ERRORS/WARNINGS or NOTES. The below WARNING was found: W checking for unstated dependencies in examples ... Warning: parse error in file 'HACSim-Ex.R': 197:17: unexpected symbol 196: # user