CRAN Package Check Results for Package dauphin

Last updated on 2024-07-26 23:53:24 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.3.1 3.24 21.92 25.16 NOTE
r-devel-linux-x86_64-debian-gcc 0.3.2 2.42 16.93 19.35 OK
r-devel-linux-x86_64-fedora-clang 0.3.2 32.63 OK
r-devel-linux-x86_64-fedora-gcc 0.3.2 31.77 OK
r-devel-windows-x86_64 0.3.1 7.00 41.00 48.00 NOTE
r-patched-linux-x86_64 0.3.1 OK
r-release-linux-x86_64 0.3.1 3.42 21.11 24.53 OK
r-release-macos-arm64 0.3.1 16.00 OK
r-release-macos-x86_64 0.3.2 42.00 OK
r-release-windows-x86_64 0.3.2 10.00 48.00 58.00 OK
r-oldrel-macos-arm64 0.3.1 22.00 OK
r-oldrel-macos-x86_64 0.3.2 38.00 OK
r-oldrel-windows-x86_64 0.3.2 11.00 47.00 58.00 OK

Check Details

Version: 0.3.1
Check: compiled code
Result: NOTE File ‘dauphin/libs/dauphin.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: 0.3.1
Check: compiled code
Result: NOTE File 'dauphin/libs/x64/dauphin.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