CRAN Package Check Results for Package luajr

Last updated on 2025-04-20 03:50:23 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.1.8 41.60 29.29 70.89 WARN
r-devel-linux-x86_64-debian-gcc 0.1.8 32.53 23.19 55.72 WARN
r-devel-linux-x86_64-fedora-clang 0.1.8 122.27 WARN
r-devel-linux-x86_64-fedora-gcc 0.1.8 149.92 WARN
r-devel-windows-x86_64 0.1.8 66.00 87.00 153.00 WARN
r-patched-linux-x86_64 0.1.8 45.54 29.19 74.73 WARN
r-release-linux-x86_64 0.1.8 43.54 29.21 72.75 WARN
r-release-macos-arm64 0.1.8 55.00 WARN
r-release-macos-x86_64 0.1.8 86.00 WARN
r-release-windows-x86_64 0.1.8 63.00 68.00 131.00 WARN
r-oldrel-macos-arm64 0.1.8 69.00 NOTE
r-oldrel-macos-x86_64 0.1.8 129.00 NOTE
r-oldrel-windows-x86_64 0.1.8 59.00 74.00 133.00 NOTE

Check Details

Version: 0.1.8
Check: compiled code
Result: WARN File ‘luajr/libs/luajr.so’: Found ‘exit’, possibly from ‘exit’ (C) Object: ‘luajit/src/libluajit.a’ Found ‘stderr’, possibly from ‘stderr’ (C) Object: ‘luajit/src/libluajit.a’ Found ‘stdout’, possibly from ‘stdout’ (C) Object: ‘luajit/src/libluajit.a’ File ‘luajr/libs/luajr.so’: Found non-API call to R: ‘DATAPTR’ 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. 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, r-patched-linux-x86_64, r-release-linux-x86_64

Version: 0.1.8
Check: compiled code
Result: WARN File 'luajr/libs/x64/luajr.dll': Found 'exit', possibly from 'exit' (C), 'stop' (Fortran) Object: 'luajit/src/libluajit.a' Found 'putchar', possibly from 'putchar' (C) Object: 'luajit/src/libluajit.a' File 'luajr/libs/x64/luajr.dll': Found non-API call to R: 'DATAPTR' 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. Flavors: r-devel-windows-x86_64, r-release-windows-x86_64

Version: 0.1.8
Check: compiled code
Result: WARN File ‘luajr/libs/luajr.so’: Found ‘___stderrp’, possibly from ‘stderr’ (C) Object: ‘luajit/src/libluajit.a’ Found ‘___stdoutp’, possibly from ‘stdout’ (C) Object: ‘luajit/src/libluajit.a’ Found ‘_exit’, possibly from ‘exit’ (C) Object: ‘luajit/src/libluajit.a’ Found ‘_putchar’, possibly from ‘putchar’ (C) Object: ‘luajit/src/libluajit.a’ File ‘luajr/libs/luajr.so’: Found non-API call to R: ‘DATAPTR’ 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. Flavors: r-release-macos-arm64, r-release-macos-x86_64

Version: 0.1.8
Check: for GNU extensions in Makefiles
Result: NOTE GNU make is a SystemRequirements. Flavors: r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64