• using R version 4.3.1 (2023-06-16)
• using platform: aarch64-apple-darwin20 (64-bit)
• R was compiled by     Apple clang version 14.0.0 (clang-1400.0.29.202)     GNU Fortran (GCC) 12.2.0
• running under: macOS Ventura 13.4
• using session charset: UTF-8
• 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 ... [25s/30s] OK See the install log for details.
• used C compiler: ‘Apple clang version 14.0.0 (clang-1400.0.29.202)’
• used SDK: ‘MacOSX11.3.sdk’
• checking installed package size ... OK
• checking package directory ... OK
• checking DESCRIPTION meta-information ... OK
• checking top-level files ... OK
• checking for left-over files ... OK
• checking index information ... OK
• checking package subdirectories ... OK
• checking R files for non-ASCII characters ... OK
• checking R files for syntax errors ... OK
• checking whether the package can be loaded ... [0s/0s] OK
• checking whether the package can be loaded with stated dependencies ... [0s/0s] OK
• checking whether the package can be unloaded cleanly ... [0s/0s] OK
• checking whether the namespace can be loaded with stated dependencies ... [0s/0s] OK
• checking whether the namespace can be unloaded cleanly ... [0s/0s] OK
• checking loading without being on the library search path ... [0s/0s] OK
• checking startup messages can be suppressed ... [0s/0s] 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 ... [3s/3s] 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 ... [0s/0s] OK
• checking Rd metadata ... 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 ... NOTE 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 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 compiled code ... 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.
• checking examples ... [1s/1s] OK
• checking PDF version of manual ... [4s/5s] OK
• DONE Status: 4 NOTEs
• using check arguments '--no-clean-on-error '