* using log directory 'd:/Rcompile/CRANpkg/local/4.4/EcoEnsemble.Rcheck' * using R version 4.4.0 (2024-04-24 ucrt) * using platform: x86_64-w64-mingw32 * R was compiled by gcc.exe (GCC) 13.2.0 GNU Fortran (GCC) 13.2.0 * running under: Windows Server 2022 x64 (build 20348) * using session charset: UTF-8 * checking for file 'EcoEnsemble/DESCRIPTION' ... OK * this is package 'EcoEnsemble' version '1.0.5' * package encoding: UTF-8 * 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 hidden files and directories ... OK * checking for portable file names ... OK * checking whether package 'EcoEnsemble' can be installed ... OK * used C++ compiler: 'g++.exe (GCC) 13.2.0' * checking C++ specification ... OK Not all R platforms support C++17 * checking installed package size ... NOTE installed size is 7.0Mb sub-directories of 1Mb or more: libs 6.0Mb * checking package directory ... OK * checking 'build' 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 ... [3s] OK * checking whether the package can be loaded with stated dependencies ... [3s] OK * checking whether the package can be unloaded cleanly ... [3s] OK * checking whether the namespace can be loaded with stated dependencies ... [4s] OK * checking whether the namespace can be unloaded cleanly ... [4s] OK * checking loading without being on the library search path ... [3s] WARNING InternalError: out of memory Error: package or namespace load failed for 'EcoEnsemble': .onLoad failed in loadNamespace() for 'rstan', details: call: NULL error: Evaluating JS code failed, see message above! Execution halted It looks like this package has a loading problem when not on .libPaths: see the messages for details. * checking use of S3 registration ... OK * checking dependencies in R code ... OK * checking S3 generic/method consistency ... OK * checking replacement functions ... WARNING Error: unable to load shared object 'D:/RCompile/CRANpkg/lib/4.4/EcoEnsemble/libs/x64/EcoEnsemble.dll': LoadLibrary failure: Eine DLL-Initialisierungsroutine ist fehlgeschlagen. Call sequence: 4: inDL(x, as.logical(local), as.logical(now), ...) 3: dyn.load(file, DLLpath = DLLpath, ...) 2: library.dynam(lib, package, package.lib) 1: loadNamespace(package, lib.loc) Execution halted The argument of a replacement function which corresponds to the right hand side must be named 'value'. * checking foreign function calls ... NOTE Error: .onLoad failed in loadNamespace() for 'rstan', details: call: paste(str, collapse = "\n") error: could not allocate memory (0 Mb) in C function 'R_AllocStringBuffer' Call sequence: 6: stop(gettextf("%s failed in %s() for '%s', details:\n call: %s\n error: %s", hookname, "loadNamespace", pkgname, deparse(conditionCall(res))[1L], conditionMessage(res)), call. = FALSE, domain = NA) 5: runHook(".onLoad", env, package.lib, package) 4: loadNamespace(j <- i[[1L]], c(lib.loc, .libPaths()), versionCheck = vI[[j]]) 3: asNamespace(ns) 2: namespaceImportFrom(ns, loadNamespace(j <- i[[1L]], c(lib.loc, .libPaths()), versionCheck = vI[[j]]), i[[2L]], from = package) 1: loadNamespace(package, lib.loc) Execution halted See chapter 'System and foreign language interfaces' in the 'Writing R Extensions' manual. * checking R code for possible problems ... [5s] NOTE Error in readRDS(mapfile) : error reading from connection During startup - Warning message: package "methods" in options("defaultPackages") was not found Error in readRDS(nsInfoFilePath) : error reading from connection Calls: getNamespace -> %||% -> loadNamespace -> readRDS Execution halted * checking Rd files ... [1s] 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 contents of 'data' directory ... OK * checking data for non-ASCII characters ... [0s] OK * checking LazyData ... OK * checking data for ASCII and uncompressed saves ... OK * checking line endings in shell scripts ... OK * checking line endings in C/C++/Fortran sources/headers ... OK * checking pragmas in C/C++ headers and code ... OK * checking compiled code ... OK * checking installed files from 'inst/doc' ... OK * checking files in 'vignettes' ...