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

2020-07-20 Thread Fabio Sigrist
Many thanks to everybody for the valuable answers. Several people (Benjamin and Ivan) pointed to the lack of portability due to the "-Wno-cast-function-type" flag. I have changed this. Further, as suggested by Benjamin, I also added the " -DNDEBUG" flag. Consequently, there is no assert call

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