CRAN Package Check Results for Package dauphin

Last updated on 2024-06-27 08:49:54 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.3.1 NOTE
r-devel-linux-x86_64-debian-gcc 0.3.1 2.60 17.04 19.64 NOTE
r-devel-linux-x86_64-fedora-clang 0.3.1 32.75 NOTE
r-devel-linux-x86_64-fedora-gcc 0.3.1 33.30 NOTE
r-devel-windows-x86_64 0.3.1 7.00 40.00 47.00 NOTE
r-patched-linux-x86_64 0.3.1 3.25 21.27 24.52 OK
r-release-linux-x86_64 0.3.1 3.13 21.15 24.28 OK
r-release-macos-arm64 0.3.1 16.00 OK
r-release-macos-x86_64 0.3.1 30.00 OK
r-release-windows-x86_64 0.3.1 6.00 40.00 46.00 OK
r-oldrel-macos-arm64 0.3.1 22.00 OK
r-oldrel-macos-x86_64 0.3.1 39.00 OK
r-oldrel-windows-x86_64 0.3.1 8.00 41.00 49.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. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc

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. See section ‘Moving into C API compliance’ in the ‘Writing R Extensions’ manual for issues with use of non-API entry points. Flavor: r-devel-linux-x86_64-debian-gcc

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. Flavor: r-devel-windows-x86_64