CRAN Package Check Results for Package bamlss

Last updated on 2024-10-15 07:49:11 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 1.2-4 73.19 352.03 425.22 NOTE
r-devel-linux-x86_64-debian-gcc 1.2-5 45.63 214.34 259.97 OK
r-devel-linux-x86_64-fedora-clang 1.2-5 716.85 OK
r-devel-linux-x86_64-fedora-gcc 1.2-5 729.03 OK
r-devel-windows-x86_64 1.2-5 69.00 307.00 376.00 OK
r-patched-linux-x86_64 1.2-4 73.76 319.05 392.81 OK
r-release-linux-x86_64 1.2-5 67.72 321.24 388.96 OK
r-release-macos-arm64 1.2-5 127.00 NOTE
r-release-macos-x86_64 1.2-5 338.00 NOTE
r-release-windows-x86_64 1.2-5 77.00 304.00 381.00 OK
r-oldrel-macos-arm64 1.2-5 145.00 NOTE
r-oldrel-macos-x86_64 1.2-5 348.00 NOTE
r-oldrel-windows-x86_64 1.2-5 96.00 398.00 494.00 OK

Check Details

Version: 1.2-4
Check: Rd cross-references
Result: NOTE Found the following Rd file(s) with Rd \link{} targets missing package anchors: bamlss-package.Rd: mgcv bamlss.Rd: mgcv bamlss.frame.Rd: mgcv Please provide package anchors for all Rd \link{} targets not in the package itself and the base packages. Flavor: r-devel-linux-x86_64-debian-clang

Version: 1.2-4
Check: compiled code
Result: NOTE File ‘bamlss/libs/bamlss.so’: Found non-API call to R: ‘SET_TYPEOF’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points. Flavor: r-devel-linux-x86_64-debian-clang

Version: 1.2-5
Check: installed package size
Result: NOTE installed size is 5.2Mb sub-directories of 1Mb or more: R 3.0Mb Flavors: r-release-macos-arm64, r-release-macos-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64