CRAN Package Check Results for Package osmnxr

Last updated on 2026-07-29 04:55:13 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.1.1 40.00 110.82 150.82 OK
r-devel-linux-x86_64-debian-gcc 0.1.1 33.25 82.32 115.57 NOTE
r-devel-linux-x86_64-fedora-clang 0.1.1 72.00 186.80 258.80 OK
r-devel-linux-x86_64-fedora-gcc 0.1.1 30.00 91.97 121.97 OK
r-devel-windows-x86_64 0.1.1 82.00 138.00 220.00 OK
r-patched-linux-x86_64 0.1.1 43.28 104.91 148.19 OK
r-release-linux-x86_64 0.1.1 40.64 104.56 145.20 OK
r-release-macos-arm64 0.1.1 12.00 47.00 59.00 OK
r-release-macos-x86_64 0.1.1 36.00 138.00 174.00 OK
r-release-windows-x86_64 0.1.1 69.00 147.00 216.00 OK
r-oldrel-macos-arm64 0.1.1 11.00 50.00 61.00 OK
r-oldrel-macos-x86_64 0.1.1 35.00 134.00 169.00 OK
r-oldrel-windows-x86_64 0.1.1 86.00 186.00 272.00 OK

Check Details

Version: 0.1.1
Check: compiled code
Result: NOTE File ‘/home/hornik/tmp/R.check/r-devel-gcc/Work/build/Packages/osmnxr/libs/osmnxr.so’: Found ‘_exit’, possibly from ‘_exit’ (C) Found ‘abort’, possibly from ‘abort’ (C) Found ‘exit’, possibly from ‘exit’ (C) 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. The detected symbols are linked into the code but might come from libraries and not actually be called. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual. Flavor: r-devel-linux-x86_64-debian-gcc