CRAN Package Check Results for Package Binarize

Last updated on 2025-11-26 17:49:48 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 1.3.2 8.15 41.38 49.53 OK
r-devel-linux-x86_64-debian-gcc 1.3.2 6.04 32.37 38.41 OK
r-devel-linux-x86_64-fedora-clang 1.3.2 35.00 43.69 78.69 OK
r-devel-linux-x86_64-fedora-gcc 1.3.2 19.00 65.12 84.12 OK
r-devel-windows-x86_64 1.3.1 12.00 74.00 86.00 NOTE
r-patched-linux-x86_64 1.3.1 7.35 38.48 45.83 NOTE
r-release-linux-x86_64 1.3.2 7.78 39.05 46.83 OK
r-release-macos-arm64 1.3.2 3.00 23.00 26.00 OK
r-release-macos-x86_64 1.3.2 16.00 135.00 151.00 OK
r-release-windows-x86_64 1.3.1 13.00 72.00 85.00 NOTE
r-oldrel-macos-arm64 1.3.2 3.00 26.00 29.00 OK
r-oldrel-macos-x86_64 1.3.2 19.00 130.00 149.00 OK
r-oldrel-windows-x86_64 1.3.2 19.00 88.00 107.00 OK

Additional issues

rchk

Check Details

Version: 1.3.1
Check: compiled code
Result: NOTE File 'Binarize/libs/x64/Binarize.dll': Found non-API call to R: 'SET_TYPEOF' 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-windows-x86_64, r-release-windows-x86_64

Version: 1.3.1
Check: compiled code
Result: NOTE File ‘Binarize/libs/Binarize.so’: Found non-API call to R: ‘SET_TYPEOF’ 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-patched-linux-x86_64