CRAN Package Check Results for Package arcgisutils

Last updated on 2025-03-22 08:53:10 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.3.1 108.43 33.69 142.12 WARN
r-devel-linux-x86_64-debian-gcc 0.3.1 91.29 24.86 116.15 WARN
r-devel-linux-x86_64-fedora-clang 0.3.1 260.30 WARN
r-devel-linux-x86_64-fedora-gcc 0.3.1 246.65 WARN
r-devel-macos-arm64 0.3.1 68.00 OK
r-devel-macos-x86_64 0.3.1 123.00 OK
r-devel-windows-x86_64 0.3.1 116.00 64.00 180.00 OK
r-patched-linux-x86_64 0.3.1 107.56 31.20 138.76 WARN
r-release-linux-x86_64 0.3.1 109.61 30.66 140.27 NOTE
r-release-macos-arm64 0.3.1 70.00 NOTE
r-release-macos-x86_64 0.3.1 111.00 NOTE
r-release-windows-x86_64 0.3.1 123.00 62.00 185.00 NOTE
r-oldrel-macos-arm64 0.3.1 NOTE
r-oldrel-macos-x86_64 0.3.1 116.00 NOTE
r-oldrel-windows-x86_64 0.3.1 146.00 70.00 216.00 NOTE

Check Details

Version: 0.3.1
Check: compiled code
Result: WARN File ‘arcgisutils/libs/arcgisutils.so’: Found ‘abort’, possibly from ‘abort’ (C) Object: ‘rust/target/release/libarcgisutils.a’ File ‘arcgisutils/libs/arcgisutils.so’: Found non-API call to R: ‘DATAPTR’ Compiled code should not call entry points which might terminate R nor write to stdout/stderr instead of to the console, nor use Fortran I/O nor system RNGs nor [v]sprintf. 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. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-patched-linux-x86_64

Version: 0.3.1
Check: package dependencies
Result: NOTE Package suggested but not available for checking: ‘arcgisbinding’ Flavors: r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64, r-release-windows-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64