CRAN Package Check Results for Package MPCR

Last updated on 2026-04-02 17:52:41 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 2.1.1 54.36 68.30 122.66 NOTE
r-devel-linux-x86_64-debian-gcc 2.1.1 44.68 47.25 91.93 NOTE
r-devel-linux-x86_64-fedora-clang 2.1.1 87.00 101.67 188.67 NOTE
r-devel-linux-x86_64-fedora-gcc 2.1.1 135.00 127.30 262.30 OK
r-devel-macos-arm64 2.1.1 14.00 17.00 31.00 OK
r-patched-linux-x86_64 2.1.1 61.20 64.60 125.80 NOTE
r-release-linux-x86_64 2.1.1 60.89 62.12 123.01 OK
r-release-macos-arm64 2.1.1 1.00 5.00 6.00 ERROR
r-release-macos-x86_64 2.1.1 3.00 8.00 11.00 ERROR
r-oldrel-macos-arm64 2.1.1 1.00 11.00 12.00 ERROR
r-oldrel-macos-x86_64 2.1.1 3.00 16.00 19.00 ERROR

Check Details

Version: 2.1.1
Check: compiled code
Result: NOTE File ‘MPCR/libs/MPCR.so’: Found non-API calls to R: ‘R_MissingArg’, ‘R_UnboundValue’ 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-patched-linux-x86_64

Version: 2.1.1
Check: compiled code
Result: NOTE File ‘MPCR/libs/MPCR.so’: Found non-API call to R: ‘R_UnboundValue’ 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-gcc, r-devel-linux-x86_64-fedora-clang

Version: 2.1.1
Check: whether package can be installed
Result: ERROR Installation failed. Flavors: r-release-macos-arm64, r-release-macos-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64