• using R version 4.5.2 (2025-10-31)
• using platform: aarch64-apple-darwin20
• R was compiled by     Apple clang version 16.0.0 (clang-1600.0.26.6)     GNU Fortran (GCC) 14.2.0
• running under: macOS Ventura 13.7.8
• using session charset: UTF-8
• checking for file ‘Rserve/DESCRIPTION’ ... OK
• this is package ‘Rserve’ version ‘1.8-16’
• 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 ‘Rserve’ can be installed ... [10s/18s] OK See the install log for details.
• used C compiler: ‘Apple clang version 14.0.3 (clang-1403.0.22.14.1)’
• used SDK: ‘MacOSX11.3.1.sdk’
• checking installed package size ... INFO   installed size is 22.3Mb   sub-directories of 1Mb or more:     libs 22.1Mb
• 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 code 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 whether 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 ... [0s/1s] OK
• 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 ... 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 include directives in Makefiles ... OK
• checking compiled code ... NOTE Note: information on .o files is not available File ‘/Volumes/Builds/packages/big-sur-arm64/results/4.5/Rserve.Rcheck/Rserve/libs/Rserve.so’:   Found ‘___stderrp’, possibly from ‘stderr’ (C)   Found ‘_abort’, possibly from ‘abort’ (C)   Found ‘_exit’, possibly from ‘exit’ (C)   Found ‘_rand’, possibly from ‘rand’ (C)   Found ‘_random’, possibly from ‘random’ (C)   Found ‘_srandom’, possibly from ‘srandom’ (C) File ‘Rserve/libs/Rserve.so’:   Found non-API calls to R: ‘R_Consolefile’, ‘R_Outputfile’,     ‘R_TempDir’, ‘R_Visible’, ‘R_curErrorBuf’, ‘ptr_R_Busy’,     ‘ptr_R_ClearerrConsole’, ‘ptr_R_FlushConsole’, ‘ptr_R_ReadConsole’,     ‘ptr_R_ResetConsole’, ‘ptr_R_ShowMessage’, ‘ptr_R_WriteConsole’,     ‘ptr_R_WriteConsoleEx’ 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 ... [0s/0s] OK
• checking PDF version of manual ... [1s/1s] OK
• DONE Status: 1 NOTE
• using check arguments '--no-clean-on-error '