CRAN Package Check Results for Package nlme

Last updated on 2026-10-17 00:51:05 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 3.1-171 28.68 253.40 282.08 OK
r-devel-linux-x86_64-debian-gcc 3.1-171 20.01 172.64 192.65 OK
r-devel-linux-x86_64-fedora-clang 3.1-171 18.00 158.17 176.17 OK
r-devel-linux-x86_64-fedora-gcc 3.1-171 19.00 158.18 177.18 OK
r-devel-windows-x86_64 3.1-171 40.00 344.00 384.00 NOTE
r-patched-linux-x86_64 3.1-171 38.09 233.86 271.95 OK
r-release-linux-x86_64 3.1-171 27.13 232.04 259.17 OK
r-release-macos-arm64 3.1-171 7.00 50.00 57.00 OK
r-release-macos-x86_64 3.1-171 22.00 225.00 247.00 OK
r-release-windows-x86_64 3.1-171 45.00 310.00 355.00 OK
r-oldrel-macos-arm64 3.1-171 6.00 60.00 66.00 OK
r-oldrel-macos-x86_64 3.1-171 20.00 210.00 230.00 OK
r-oldrel-windows-x86_64 3.1-171 50.00 372.00 422.00 OK

Check Details

Version: 3.1-171
Check: compiled code
Result: NOTE Note: information on .o files for x64 is not available File 'd:/Rcompile/CRANpkg/lib/4.7/nlme/libs/x64/nlme.dll': Found '_exit', possibly from '_exit' (C) Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran) 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. The detected symbols are linked into the code but might come from libraries and not actually be called. See 'Writing portable packages' in the 'Writing R Extensions' manual. Flavor: r-devel-windows-x86_64