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

[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 anymore when compiling with gcc under
Linux.

Ivan suggested that the forbidden exit/abort calls might be caused by
linking the R package with -static-libstdc+. I have now removed this but I
am still getting the " Found '_exit'" etc. notes. It is also unclear to me
why these exit / abort symbols are only found under Windows / MinGW and not
under Linux.

I agree with Dirks assessment. It seems that the bottom line is that it is
very difficult to find the exit / abort calls. Very unfortunate...

On Fri, Jul 17, 2020 at 11:25 AM Fabio Sigrist <fabiosigrist using gmail.com>
wrote:

> 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 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)
>
> As much as I search through my code, I can't find the place / headers
> where these calls / symbols originate. Also, I have no idea how to add
> information on .o files (apart from the shared library, there are no .o
> files). The .tar.gz file for the package can be found on
> https://github.com/fabsig/GPBoost/blob/master/gpboost_0.2.0.tar.gz. Note
> that the shared library is compiled using install.libs.R (this is a
> deliberate choice) and the flag "GPB_R_BUILD" is set when compiling for the
> R package (I have tried to put "#ifndef GPB_R_BUILD" around all headers
> that could cause the problems with exit / abort calls, but apparently I
> have not been able to find all).
>
> Any help is greatly appreciated.
>
> Best regards,
> Fabio Sigrist
>
>

	[[alternative HTML version deleted]]