CRAN Package Check Results for Package LTRCforests

Last updated on 2024-12-02 09:49:15 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.7.0 28.07 94.03 122.10 NOTE
r-devel-linux-x86_64-debian-gcc 0.7.0 20.71 64.79 85.50 NOTE
r-devel-linux-x86_64-fedora-clang 0.7.0 201.24 NOTE
r-devel-linux-x86_64-fedora-gcc 0.7.0 209.55 NOTE
r-devel-windows-x86_64 0.7.0 34.00 101.00 135.00 NOTE
r-patched-linux-x86_64 0.7.0 29.24 88.69 117.93 OK
r-release-linux-x86_64 0.7.0 29.67 87.84 117.51 OK
r-release-macos-arm64 0.7.0 53.00 OK
r-release-macos-x86_64 0.7.0 87.00 OK
r-release-windows-x86_64 0.7.0 35.00 103.00 138.00 OK
r-oldrel-macos-arm64 0.7.0 57.00 OK
r-oldrel-macos-x86_64 0.7.0 123.00 OK
r-oldrel-windows-x86_64 0.7.0 42.00 125.00 167.00 OK

Check Details

Version: 0.7.0
Check: Rd cross-references
Result: NOTE Found the following Rd file(s) with Rd \link{} targets missing package anchors: pbcsample.Rd: pbcseq, survival Please provide package anchors for all Rd \link{} targets not in the package itself and the base packages. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-windows-x86_64

Version: 0.7.0
Check: compiled code
Result: NOTE File ‘LTRCforests/libs/LTRCforests.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, 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

Version: 0.7.0
Check: compiled code
Result: NOTE File 'LTRCforests/libs/x64/LTRCforests.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, and section 'Moving into C API compliance' for issues with the use of non-API entry points. Flavor: r-devel-windows-x86_64