• using R Under development (unstable) (2024-11-09 r87314)
• using platform: x86_64-pc-linux-gnu
• R was compiled by     clang version 19.1.3     flang-new version 19.1.3
• running under: Fedora Linux 36 (Workstation Edition)
• using session charset: UTF-8
• using option ‘--no-stop-on-test-error’
• checking for file ‘rJava/DESCRIPTION’ ... OK
• this is package ‘rJava’ version ‘1.0-11’
• checking package namespace information ... OK
• checking package dependencies ... OK
• checking if this is a source package ... OK
• checking if there is a namespace ... OK
• checking for executable files ... OK
• checking for hidden files and directories ... OK
• checking for portable file names ... OK
• checking for sufficient/correct file permissions ... OK
• checking whether package ‘rJava’ can be installed ... [22s/39s] OK See the install log for details.
• used C compiler: ‘clang version 19.1.3’
• checking installed package size ... OK
• checking package directory ... OK
• checking DESCRIPTION meta-information ... OK
• checking top-level files ... NOTE Non-standard file/directory found at top level:   ‘jri’
• checking for left-over files ... OK
• checking index information ... OK
• checking package subdirectories ... OK
• checking code files for non-ASCII characters ... OK
• checking R files for syntax errors ... OK
• checking whether the package can be loaded ... OK
• checking whether the package can be loaded with stated dependencies ... OK
• checking whether the package can be unloaded cleanly ... OK
• checking whether the namespace can be loaded with stated dependencies ... OK
• checking whether the namespace can be unloaded cleanly ... OK
• checking loading without being on the library search path ... OK
• checking whether startup messages can be suppressed ... OK
• checking use of S3 registration ... OK
• checking dependencies in R code ... OK
• checking S3 generic/method consistency ... OK
• checking replacement functions ... OK
• checking foreign function calls ... OK
• checking R code for possible problems ... [17s/24s] 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)
• checking Rd files ... OK
• checking Rd metadata ... OK
• checking Rd line widths ... OK
• checking Rd cross-references ... OK
• checking for missing documentation entries ... OK
• checking for code/documentation mismatches ... OK
• checking Rd \usage sections ... OK
• checking Rd contents ... OK
• checking for unstated dependencies in examples ... OK
• checking line endings in shell scripts ... OK
• checking line endings in C/C++/Fortran sources/headers ... OK
• checking line endings in Makefiles ... OK
• checking compilation flags in Makevars ... OK
• checking for GNU extensions in Makefiles ... INFO GNU make is a SystemRequirements.
• checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK
• checking use of PKG_*FLAGS in Makefiles ... OK
• checking use of SHLIB_OPENMP_*FLAGS in Makefiles ... OK
• checking include directives in Makefiles ... 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'.
• checking pragmas in C/C++ headers and code ... OK
• checking compilation flags used ... OK
• checking compiled code ... 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, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points.
• checking examples ... OK
• checking PDF version of manual ... [9s/14s] OK
• checking HTML version of manual ... OK
• checking for non-standard things in the check directory ... OK
• checking for detritus in the temp directory ... OK
• DONE

Status: 4 NOTEs