CRAN Package Check Results for Package rbm25

Last updated on 2025-04-17 09:49:22 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.0.3 106.31 18.83 125.14 WARN
r-devel-linux-x86_64-debian-gcc 0.0.4 84.50 16.07 100.57 OK
r-devel-linux-x86_64-fedora-clang 0.0.4 208.35 OK
r-devel-linux-x86_64-fedora-gcc 0.0.4 207.65 OK
r-devel-windows-x86_64 0.0.4 116.00 63.00 179.00 OK
r-patched-linux-x86_64 0.0.4 107.94 18.49 126.43 OK
r-release-linux-x86_64 0.0.4 107.71 18.55 126.26 OK
r-release-macos-arm64 0.0.4 57.00 OK
r-release-macos-x86_64 0.0.4 83.00 OK
r-release-windows-x86_64 0.0.4 117.00 62.00 179.00 OK
r-oldrel-macos-arm64 0.0.4 59.00 OK
r-oldrel-macos-x86_64 0.0.4 99.00 OK
r-oldrel-windows-x86_64 0.0.4 109.00 70.00 179.00 OK

Check Details

Version: 0.0.3
Check: compiled code
Result: WARN File ‘rbm25/libs/rbm25.so’: Found ‘_exit’, possibly from ‘_exit’ (C) Object: ‘rust/target/release/librbm25.a’ Found ‘abort’, possibly from ‘abort’ (C) Object: ‘rust/target/release/librbm25.a’ Found ‘exit’, possibly from ‘exit’ (C) Object: ‘rust/target/release/librbm25.a’ File ‘rbm25/libs/rbm25.so’: Found non-API calls to R: ‘BODY’, ‘CLOENV’, ‘DATAPTR’, ‘ENCLOS’, ‘FORMALS’ Compiled code should not call entry points which might terminate R nor write to stdout/stderr instead of to the console, nor use Fortran I/O nor system RNGs nor [v]sprintf. 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-linux-x86_64-debian-clang