CRAN Package Check Results for Package rJava

Last updated on 2024-06-19 17:54:38 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 1.0-11 38.96 60.72 99.68 NOTE
r-devel-linux-x86_64-debian-gcc 1.0-11 26.95 43.98 70.93 NOTE
r-devel-linux-x86_64-fedora-clang 1.0-11 96.60 NOTE
r-devel-linux-x86_64-fedora-gcc 1.0-11 95.75 NOTE
r-devel-windows-x86_64 1.0-11 43.00 68.00 111.00 NOTE
r-patched-linux-x86_64 1.0-11 36.86 56.42 93.28 NOTE
r-release-linux-x86_64 1.0-11 36.47 57.83 94.30 NOTE
r-release-macos-arm64 1.0-11 13.00 ERROR
r-release-macos-x86_64 1.0-11 83.00 NOTE
r-release-windows-x86_64 1.0-11 43.00 67.00 110.00 NOTE
r-oldrel-macos-arm64 1.0-11 64.00 NOTE
r-oldrel-macos-x86_64 1.0-11 153.00 NOTE
r-oldrel-windows-x86_64 1.0-11 43.00 76.00 119.00 NOTE

Additional issues

rchk

Check Details

Version: 1.0-11
Check: top-level files
Result: NOTE Non-standard file/directory found at top level: ‘jri’ 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: 1.0-11
Check: R code for possible problems
Result: NOTE Found the following possibly unsafe calls: File ‘rJava/R/import.R’: unlockBinding(IMPORTER, env = env) assignInNamespace(IMPORTER, importer, envir = env) File ‘rJava/R/jinit.R’: unlockBinding(x, .env) unlockBinding(x, pe) 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-devel-windows-x86_64, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-x86_64, r-release-windows-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64

Version: 1.0-11
Check: for GNU extensions in Makefiles
Result: NOTE GNU make is a SystemRequirements. 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-devel-windows-x86_64, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-x86_64, r-release-windows-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64

Version: 1.0-11
Check: include directives in Makefiles
Result: NOTE Found the following Makefile(s) with an include directive with a pathname using R_HOME: jri/src/Makefile.win jri/src/win32/Makefile src/jvm-w32/Makefile Even though not recommended, variable R_HOME may contain spaces. Makefile directives use space as a separator and there is no portable way to quote/escape the space in Make rules and directives. However, one can and should quote pathnames when passed from Makefile to the shell, and this can be done specifically when invoking Make recursively. It is therefore recommended to use the Make '-f' option to include files in directories specified using R_HOME. This option can be specified multiple times to include multiple Makefiles. Note that 'Makeconf' is included automatically into top-level makefile of a package. More information can be found in 'Writing R Extensions'. 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-devel-windows-x86_64, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-x86_64, r-release-windows-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64

Version: 1.0-11
Check: compiled code
Result: NOTE Note: information on .o files is not available File ‘/home/hornik/tmp/R.check/r-devel-clang/Work/build/Packages/rJava/libs/rJava.so’: Found ‘_exit’, possibly from ‘_exit’ (C) Found ‘stderr’, possibly from ‘stderr’ (C) Found ‘stdout’, possibly from ‘stdout’ (C) File ‘rJava/libs/rJava.so’: Found non-API calls to R: ‘R_CStackLimit’, ‘R_CStackStart’ 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. Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual. Flavor: r-devel-linux-x86_64-debian-clang

Version: 1.0-11
Check: compiled code
Result: NOTE Note: information on .o files is not available File ‘/home/hornik/tmp/R.check/r-devel-gcc/Work/build/Packages/rJava/libs/rJava.so’: Found ‘_exit’, possibly from ‘_exit’ (C) Found ‘stderr’, possibly from ‘stderr’ (C) Found ‘stdout’, possibly from ‘stdout’ (C) File ‘rJava/libs/rJava.so’: Found non-API calls to R: ‘R_CStackLimit’, ‘R_CStackStart’ 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. Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual. Flavor: r-devel-linux-x86_64-debian-gcc

Version: 1.0-11
Check: compiled code
Result: NOTE Note: information on .o files is not available File ‘/data/gannet/ripley/R/packages/tests-clang/rJava.Rcheck/rJava/libs/rJava.so’: Found ‘_exit’, possibly from ‘_exit’ (C) Found ‘stderr’, possibly from ‘stderr’ (C) Found ‘stdout’, possibly from ‘stdout’ (C) File ‘rJava/libs/rJava.so’: Found non-API calls to R: ‘R_CStackLimit’, ‘R_CStackStart’ 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. Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual. Flavor: r-devel-linux-x86_64-fedora-clang

Version: 1.0-11
Check: compiled code
Result: NOTE Note: information on .o files is not available File ‘/data/gannet/ripley/R/packages/tests-devel/rJava.Rcheck/rJava/libs/rJava.so’: Found ‘_exit’, possibly from ‘_exit’ (C) Found ‘stderr’, possibly from ‘stderr’ (C) Found ‘stdout’, possibly from ‘stdout’ (C) File ‘rJava/libs/rJava.so’: Found non-API calls to R: ‘R_CStackLimit’, ‘R_CStackStart’ 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. Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual. Flavor: r-devel-linux-x86_64-fedora-gcc

Version: 1.0-11
Check: compiled code
Result: NOTE Note: information on .o files for x64 is not available File 'd:/Rcompile/CRANpkg/lib/4.5/rJava/libs/x64/rJava.dll': Found '_exit', possibly from '_exit' (C) Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran) 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-windows-x86_64

Version: 1.0-11
Check: compiled code
Result: NOTE Note: information on .o files is not available File ‘/home/hornik/tmp/R.check/r-patched-gcc/Work/build/Packages/rJava/libs/rJava.so’: Found ‘_exit’, possibly from ‘_exit’ (C) Found ‘stderr’, possibly from ‘stderr’ (C) Found ‘stdout’, possibly from ‘stdout’ (C) File ‘rJava/libs/rJava.so’: Found non-API calls to R: ‘R_CStackLimit’, ‘R_CStackStart’ 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. Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual. Flavor: r-patched-linux-x86_64

Version: 1.0-11
Check: compiled code
Result: NOTE Note: information on .o files is not available File ‘/home/hornik/tmp/R.check/r-release-gcc/Work/build/Packages/rJava/libs/rJava.so’: Found ‘_exit’, possibly from ‘_exit’ (C) Found ‘stderr’, possibly from ‘stderr’ (C) Found ‘stdout’, possibly from ‘stdout’ (C) File ‘rJava/libs/rJava.so’: Found non-API calls to R: ‘R_CStackLimit’, ‘R_CStackStart’ 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. Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual. Flavor: r-release-linux-x86_64

Version: 1.0-11
Check: whether package can be installed
Result: ERROR Installation failed. Flavor: r-release-macos-arm64

Version: 1.0-11
Check: compiled code
Result: NOTE Note: information on .o files is not available File ‘/Volumes/Builds/packages/big-sur-x86_64/results/4.4/rJava.Rcheck/rJava/libs/rJava.so’: Found ‘___stderrp’, possibly from ‘stderr’ (C) Found ‘___stdoutp’, possibly from ‘stdout’ (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-release-macos-x86_64

Version: 1.0-11
Check: compiled code
Result: NOTE Note: information on .o files for x64 is not available File 'd:/Rcompile/CRANpkg/lib/4.4/rJava/libs/x64/rJava.dll': Found '_exit', possibly from '_exit' (C) Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran) 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-release-windows-x86_64

Version: 1.0-11
Check: compiled code
Result: NOTE Note: information on .o files is not available File ‘/Volumes/Builds/packages/big-sur-arm64/results/4.3/rJava.Rcheck/rJava/libs/rJava.so’: Found ‘___stderrp’, possibly from ‘stderr’ (C) Found ‘___stdoutp’, possibly from ‘stdout’ (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-oldrel-macos-arm64

Version: 1.0-11
Check: compiled code
Result: NOTE Note: information on .o files is not available File ‘/Volumes/Builds/packages/big-sur-x86_64/results/4.3/rJava.Rcheck/rJava/libs/rJava.so’: Found ‘___stderrp’, possibly from ‘stderr’ (C) Found ‘___stdoutp’, possibly from ‘stdout’ (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-oldrel-macos-x86_64

Version: 1.0-11
Check: compiled code
Result: NOTE Note: information on .o files for x64 is not available File 'd:/Rcompile/CRANpkg/lib/4.3/rJava/libs/x64/rJava.dll': Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran) 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-oldrel-windows-x86_64