Re: [R-pkg-devel] "non-ASCII input" and "--data-compress" ignored

2020-07-17 Thread Spencer Graves
Hello, Ivan et al.:   I tried escaping "%" every time it occurred without success, but adding "\encoding{UTF-8}" as the 4th line of nuclearWeaponStates.Rd eliminated that problem.   Sadly, I tried "R CMD build --resave-data=best Ecdat", "R CMD build --resave-data Ecdat", "R CMD

Re: [R-pkg-devel] Note: information on .o files is not available / Found '_exit', possibly from '_exit' (C)

2020-07-17 Thread Ivan Krylov
On Fri, 17 Jul 2020 11:25:40 +0200 Fabio Sigrist wrote: > Found '_exit', possibly from '_exit' (C) > Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran) > Found 'exit', possibly from 'exit' (C), 'stop' (Fortran) > Found 'printf', possibly from 'printf' (C) A curious

Re: [R-pkg-devel] Note: information on .o files is not available / Found '_exit', possibly from '_exit' (C)

2020-07-17 Thread Dirk Eddelbuettel
On 17 July 2020 at 14:58, Benjamin Christoffersen wrote: | Quick guess. After changing | > SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++11 -pthread -O3 -Wextra -Wall -Wno-unknown-pragmas -Wno-return-type -Wno-ignored-attributes -Wno-cast-function-type -Wno-error=cast-function-type") | | to

Re: [R-pkg-devel] Note: information on .o files is not available / Found '_exit', possibly from '_exit' (C)

2020-07-17 Thread Benjamin Christoffersen
Quick guess. After changing > SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++11 -pthread -O3 -Wextra -Wall > -Wno-unknown-pragmas -Wno-return-type -Wno-ignored-attributes > -Wno-cast-function-type -Wno-error=cast-function-type") to > SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++11 -pthread

Re: [R-pkg-devel] Note: information on .o files is not available / Found '_exit', possibly from '_exit' (C)

2020-07-17 Thread Dirk Eddelbuettel
On 17 July 2020 at 11:25, Fabio Sigrist wrote: | I am trying to get an R package with C++ code on CRAN and I have one NOTE | remaining, for which I can't find a solution: | | Note: information on .o files for x64 is not available | File |

Re: [R-pkg-devel] Note: information on .o files is not available / Found '_exit', possibly from '_exit' (C)

2020-07-17 Thread Spencer Graves
  Can you run the checks only on the subdirectory containing the compiled code?  If yes, then you can run it only on half of that directory and identify it with a binary search.   Some years ago, I found a particularly difficult bug that way.  If I recall correctly, I made a copy of

Re: [R-pkg-devel] Note: information on .o files is not available / Found '_exit', possibly from '_exit' (C)

2020-07-17 Thread Marcin Jurek
So maybe you tried that already but I noticed that sometimes when I do the check on the package directory rather than on the tarball I get similar errors. I don't know if that's the problem but it should be a quick thing to try. On Fri, Jul 17, 2020 at 5:05 AM Fabio Sigrist wrote: > Dear all, >

[R-pkg-devel] Note: information on .o files is not available / Found '_exit', possibly from '_exit' (C)

2020-07-17 Thread Fabio Sigrist
Dear all, I am trying to get an R package with C++ code on CRAN and I have one NOTE remaining, for which I can't find a solution: Note: information on .o files for x64 is not available File 'd:/RCompile/CRANincoming/R-devel/lib/gpboost/libs/x64/lib_gpboost.dll': Found '_exit', possibly

Re: [R-pkg-devel] "non-ASCII input" and "--data-compress" ignored

2020-07-17 Thread Ivan Krylov
On Fri, 17 Jul 2020 02:02:36 -0500 Spencer Graves wrote: > If I copy this URL into a browser and back out again, I get > the following: > > > https://www.americansecurityproject.org/ASP%20Reports/Ref%200072%20-%20North%20Korea%E2%80%99s%20Nuclear%20Program%20.pdf > > >   However, if I

Re: [R-pkg-devel] Interpret feedback: not write testthat-tests in examples

2020-07-17 Thread Maëlle SALMON via R-package-devel
If you do want to communicate around tests a bit more, without cluttering the manual, you might find the covrpage package interesting  https://yonicd.github.io/covrpage/ It creates a README in the tests folder, with test results, and it can create a vignette with the same content. On dj.,

[R-pkg-devel] "non-ASCII input" and "--data-compress" ignored

2020-07-17 Thread Spencer Graves
Hello:   I'm getting two warnings that I don't know how to fix on both 4.0.2 under macOS 10.15.5 and 4.0.0 under TRAVIS-CI; the email from Travis CI is copied below. NON-ASCII INPUT: * checking Rd files ... WARNING man/nuclearWeaponStates.Rd: non-ASCII input and no declared encoding