CRAN Package Check Results for Package nlme

Last updated on 2026-09-02 13:50:56 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 3.1-170 26.92 250.80 277.72 OK
r-devel-linux-x86_64-debian-gcc 3.1-170 19.41 173.03 192.44 OK
r-devel-linux-x86_64-fedora-clang 3.1-171 21.00 180.38 201.38 OK
r-devel-linux-x86_64-fedora-gcc 3.1-171 20.00 171.00 191.00 OK
r-devel-windows-x86_64 3.1-170 42.00 352.00 394.00 NOTE
r-patched-linux-x86_64 3.1-170 37.41 233.36 270.77 OK
r-release-linux-x86_64 3.1-170 27.82 233.32 261.14 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 56.00 332.00 388.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-170 52.00 380.00 432.00 OK

Check Details

Version: 3.1-170
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