CRAN Package Check Results for Package vetr

Last updated on 2025-03-26 21:55:39 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.2.18 10.08 67.40 77.48 NOTE
r-devel-linux-x86_64-debian-gcc 0.2.18 8.46 48.14 56.60 NOTE
r-devel-linux-x86_64-fedora-clang 0.2.18 126.11 NOTE
r-devel-linux-x86_64-fedora-gcc 0.2.18 137.19 NOTE
r-devel-macos-arm64 0.2.18 47.00 NOTE
r-devel-macos-x86_64 0.2.18 116.00 NOTE
r-devel-windows-x86_64 0.2.18 20.00 89.00 109.00 NOTE
r-patched-linux-x86_64 0.2.18 10.37 66.87 77.24 NOTE
r-release-linux-x86_64 0.2.18 9.68 65.61 75.29 OK
r-release-macos-arm64 0.2.18 72.00 OK
r-release-macos-x86_64 0.2.18 156.00 OK
r-release-windows-x86_64 0.2.18 21.00 86.00 107.00 OK
r-oldrel-macos-arm64 0.2.18 OK
r-oldrel-macos-x86_64 0.2.18 86.00 OK
r-oldrel-windows-x86_64 0.2.18 22.00 105.00 127.00 OK

Check Details

Version: 0.2.18
Check: compiled code
Result: NOTE File ‘vetr/libs/vetr.so’: Found non-API calls to R: ‘ENCLOS’, ‘FORMALS’, ‘IS_S4_OBJECT’, ‘R_lsInternal’, ‘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. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-patched-linux-x86_64

Version: 0.2.18
Check: compiled code
Result: NOTE File ‘vetr/libs/vetr.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. Flavors: r-devel-macos-arm64, r-devel-macos-x86_64

Version: 0.2.18
Check: compiled code
Result: NOTE File 'vetr/libs/x64/vetr.dll': Found non-API calls to R: 'ENCLOS', 'FORMALS', 'IS_S4_OBJECT', 'R_lsInternal', '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-windows-x86_64