Dear maintainer,
Please see the problems shown on
<https://cran.r-project.org/web/checks/check_results_fs.html>.
Specifically, please see the WARNINGs about calling bad entry points in
the "compiled code" check.
These are from fixing PR#18789 ("R CMD check does not report symbols in
linked static libraries",
<https://bugs.r-project.org/show_bug.cgi?id=18789>) so that R CMD check
now also reports bad symbols in package shared objects linked in from
local static libraries.
Please correct before 2025-04-14 to safely retain your package on CRAN.
Version: 1.6.5
Check: compiled code
Result: WARN
File ‘fs/libs/fs.so’:
Found ‘_exit’, possibly from ‘_exit’ (C)
Object: ‘libuv-1.44.2/.libs/libuv.a’
Found ‘abort’, possibly from ‘abort’ (C)
Object: ‘libuv-1.44.2/.libs/libuv.a’
Found ‘sprintf’, possibly from ‘sprintf’ (C)
Object: ‘libuv-1.44.2/.libs/libuv.a’
Found ‘stderr’, possibly from ‘stderr’ (C)
Object: ‘libuv-1.44.2/.libs/libuv.a’
Compiled code should not call entry points which might terminate R nor
write to stdout/stderr instead of to the console, nor use Fortran I/O
nor system RNGs nor [v]sprintf.
See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual.
Flavors: [r-devel-linux-x86_64-debian-clang](https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-debian-clang/fs-00check.html), [r-devel-linux-x86_64-debian-gcc](https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-debian-gcc/fs-00check.html), [r-patched-linux-x86_64](https://www.r-project.org/nosvn/R.check/r-patched-linux-x86_64/fs-00check.html)
