CRAN Package Check Results for Package spatialsample

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

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.5.1 50.18 627.12 677.30 NOTE
r-devel-linux-x86_64-debian-gcc 0.5.1 34.71 461.37 496.08 NOTE
r-devel-linux-x86_64-fedora-clang 0.5.1 1188.09 NOTE
r-devel-linux-x86_64-fedora-gcc 0.5.1 736.77 NOTE
r-devel-windows-x86_64 0.5.1 49.00 408.00 457.00 NOTE
r-patched-linux-x86_64 0.5.1 42.02 634.00 676.02 OK
r-release-linux-x86_64 0.5.1 31.58 636.41 667.99 OK
r-release-macos-arm64 0.5.1 179.00 OK
r-release-macos-x86_64 0.5.1 307.00 OK
r-release-windows-x86_64 0.5.1 50.00 407.00 457.00 OK
r-oldrel-macos-arm64 0.5.1 171.00 OK
r-oldrel-macos-x86_64 0.5.1 440.00 OK
r-oldrel-windows-x86_64 0.5.1 62.00 539.00 601.00 OK

Check Details

Version: 0.5.1
Check: compiled code
Result: NOTE File ‘spatialsample/libs/spatialsample.so’: Found non-API calls to R: ‘SETLENGTH’, ‘SET_GROWABLE_BIT’, ‘SET_TRUELENGTH’ 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, r-devel-linux-x86_64-fedora-gcc

Version: 0.5.1
Check: compiled code
Result: NOTE File ‘spatialsample/libs/spatialsample.so’: Found non-API calls to R: ‘SETLENGTH’, ‘SET_GROWABLE_BIT’, ‘SET_TRUELENGTH’ 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.5.1
Check: compiled code
Result: NOTE File 'spatialsample/libs/x64/spatialsample.dll': Found non-API calls to R: 'SETLENGTH', 'SET_GROWABLE_BIT', 'SET_TRUELENGTH' 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