CRAN Package Check Results for Package base64enc

Last updated on 2024-11-21 19:52:31 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.1-3 2.45 16.15 18.60 NOTE
r-devel-linux-x86_64-debian-gcc 0.1-3 1.88 13.63 15.51 NOTE
r-devel-linux-x86_64-fedora-clang 0.1-3 30.51 NOTE
r-devel-linux-x86_64-fedora-gcc 0.1-3 29.02 NOTE
r-devel-windows-x86_64 0.1-3 9.00 40.00 49.00 NOTE
r-patched-linux-x86_64 0.1-3 2.31 15.58 17.89 OK
r-release-linux-x86_64 0.1-3 2.06 16.06 18.12 OK
r-release-macos-arm64 0.1-3 16.00 OK
r-release-macos-x86_64 0.1-3 22.00 OK
r-release-windows-x86_64 0.1-3 9.00 38.00 47.00 OK
r-oldrel-macos-arm64 0.1-3 16.00 OK
r-oldrel-macos-x86_64 0.1-3 21.00 OK
r-oldrel-windows-x86_64 0.1-3 6.00 39.00 45.00 OK

Check Details

Version: 0.1-3
Check: compiled code
Result: NOTE File ‘base64enc/libs/base64enc.so’: Found non-API call to R: ‘SETLENGTH’ 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

Version: 0.1-3
Check: compiled code
Result: NOTE File ‘base64enc/libs/base64enc.so’: Found non-API call to R: ‘SETLENGTH’ File ‘base64enc/libs/base64enc.so’: Found no calls to: ‘R_registerRoutines’, ‘R_useDynamicSymbols’ Compiled code should not call non-API entry points in R. It is good practice to register native routines and to disable symbol search. 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-fedora-clang, r-devel-linux-x86_64-fedora-gcc

Version: 0.1-3
Check: compiled code
Result: NOTE File 'base64enc/libs/x64/base64enc.dll': Found non-API call to R: 'SETLENGTH' 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-windows-x86_64

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.