CRAN Package Check Results for Package lazy

Last updated on 2024-06-27 08:49:59 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 1.2-18 NOTE
r-devel-linux-x86_64-debian-gcc 1.2-18 2.81 17.47 20.28 NOTE
r-devel-linux-x86_64-fedora-clang 1.2-18 33.18 NOTE
r-devel-linux-x86_64-fedora-gcc 1.2-18 32.82 NOTE
r-devel-windows-x86_64 1.2-18 5.00 39.00 44.00 NOTE
r-patched-linux-x86_64 1.2-18 4.12 21.50 25.62 OK
r-release-linux-x86_64 1.2-18 3.36 20.99 24.35 OK
r-release-macos-arm64 1.2-18 15.00 OK
r-release-macos-x86_64 1.2-18 23.00 OK
r-release-windows-x86_64 1.2-18 6.00 38.00 44.00 OK
r-oldrel-macos-arm64 1.2-18 16.00 OK
r-oldrel-macos-x86_64 1.2-18 21.00 OK
r-oldrel-windows-x86_64 1.2-18 7.00 38.00 45.00 OK

Check Details

Version: 1.2-18
Check: compiled code
Result: NOTE File ‘lazy/libs/lazy.so’: Found non-API call to R: ‘STRING_PTR’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc

Version: 1.2-18
Check: compiled code
Result: NOTE File ‘lazy/libs/lazy.so’: Found non-API call to R: ‘STRING_PTR’ 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-linux-x86_64-debian-gcc

Version: 1.2-18
Check: compiled code
Result: NOTE File 'lazy/libs/x64/lazy.dll': Found non-API call to R: 'STRING_PTR' Compiled code should not call non-API entry points in R. See 'Writing portable packages' in the 'Writing R Extensions' manual. Flavor: r-devel-windows-x86_64