CRAN Package Check Results for Package unnest

Last updated on 2024-07-01 03:49:32 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.0.5 16.01 44.34 60.35 NOTE
r-devel-linux-x86_64-debian-gcc 0.0.5 13.15 33.88 47.03 NOTE
r-devel-linux-x86_64-fedora-clang 0.0.5 84.49 NOTE
r-devel-linux-x86_64-fedora-gcc 0.0.5 96.09 NOTE
r-devel-windows-x86_64 0.0.5 16.00 76.00 92.00 NOTE
r-patched-linux-x86_64 0.0.5 15.05 40.69 55.74 OK
r-release-linux-x86_64 0.0.5 13.65 38.47 52.12 OK
r-release-macos-arm64 0.0.5 32.00 OK
r-release-macos-x86_64 0.0.5 47.00 OK
r-release-windows-x86_64 0.0.5 16.00 74.00 90.00 OK
r-oldrel-macos-arm64 0.0.5 41.00 OK
r-oldrel-macos-x86_64 0.0.5 88.00 OK
r-oldrel-windows-x86_64 0.0.5 17.00 83.00 100.00 OK

Additional issues

noRemap

Check Details

Version: 0.0.5
Check: compiled code
Result: NOTE File ‘unnest/libs/unnest.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. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc

Version: 0.0.5
Check: compiled code
Result: NOTE File ‘unnest/libs/unnest.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-fedora-clang

Version: 0.0.5
Check: compiled code
Result: NOTE File ‘unnest/libs/unnest.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. Flavor: r-devel-linux-x86_64-fedora-gcc

Version: 0.0.5
Check: compiled code
Result: NOTE File 'unnest/libs/x64/unnest.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. 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-windows-x86_64