CRAN Package Check Results for Package epm

Last updated on 2024-07-19 06:50:13 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 1.1.2 37.12 123.06 160.18 NOTE
r-devel-linux-x86_64-debian-gcc 1.1.2 21.42 85.39 106.81 OK
r-devel-linux-x86_64-fedora-clang 1.1.2 203.74 OK
r-devel-linux-x86_64-fedora-gcc 1.1.2 194.95 OK
r-devel-windows-x86_64 1.1.2 28.00 124.00 152.00 NOTE
r-patched-linux-x86_64 1.1.2 35.49 117.08 152.57 OK
r-release-linux-x86_64 1.1.2 27.74 116.34 144.08 OK
r-release-macos-arm64 1.1.2 51.00 OK
r-release-macos-x86_64 1.1.2 77.00 OK
r-release-windows-x86_64 1.1.2 31.00 125.00 156.00 OK
r-oldrel-macos-arm64 1.1.2 54.00 OK
r-oldrel-macos-x86_64 1.1.2 117.00 OK
r-oldrel-windows-x86_64 1.1.2 37.00 151.00 188.00 OK

Check Details

Version: 1.1.2
Check: compiled code
Result: NOTE File ‘epm/libs/epm.so’: Found non-API call to R: ‘STRING_PTR’ 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.1.2
Check: compiled code
Result: NOTE File 'epm/libs/x64/epm.dll': Found non-API call to R: 'STRING_PTR' 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