* using log directory ‘/srv/hornik/tmp/CRAN_pretest/RadEro.Rcheck’ * using R Under development (unstable) (2024-09-28 r87201) * using platform: x86_64-pc-linux-gnu * R was compiled by Debian clang version 18.1.8 (9) Debian flang-new version 18.1.8 (9) * running under: Debian GNU/Linux trixie/sid * using session charset: UTF-8 * checking for file ‘RadEro/DESCRIPTION’ ... OK * checking extension type ... Package * this is package ‘RadEro’ version ‘1.0.3’ * package encoding: UTF-8 * checking CRAN incoming feasibility ... [3s/3s] NOTE Maintainer: ‘Arturo Catala ’ New submission * checking package namespace information ... OK * checking package dependencies ... OK * checking if this is a source package ... WARNING Subdirectory ‘RadEro/src’ contains apparent object files/libraries radimod.dll Object files/libraries should not be included in a source package. Subdirectory ‘src’ contains: radimod.dll These are unlikely file names for src files. * checking if there is a namespace ... OK * checking for executable files ... WARNING Found the following executable file: src/radimod.dll Source packages should not contain undeclared executable files. See section ‘Package structure’ in the ‘Writing R Extensions’ manual. * checking for hidden files and directories ... OK * checking for portable file names ... OK * checking for sufficient/correct file permissions ... OK * checking whether package ‘RadEro’ can be installed ... [8s/8s] OK * used C compiler: ‘Debian clang version 18.1.8 (11)’ * used C++ compiler: ‘Debian clang version 18.1.8 (11)’ * checking package directory ... OK * checking for future file timestamps ... OK * checking DESCRIPTION meta-information ... OK * checking top-level files ... NOTE Non-standard file/directory found at top level: ‘RadEro.Rproj’ * 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 ... [1s/1s] OK * checking whether the package can be loaded with stated dependencies ... [1s/1s] OK * checking whether the package can be unloaded cleanly ... [1s/1s] OK * checking whether the namespace can be loaded with stated dependencies ... [1s/1s] OK * checking whether the namespace can be unloaded cleanly ... [1s/1s] OK * checking loading without being on the library search path ... [1s/1s] 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 ... [6s/6s] NOTE plot: no visible binding for global variable ‘depth1’ Undefined global functions or variables: depth1 * checking Rd files ... [0s/0s] 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 C/C++/Fortran sources/headers ... OK * checking pragmas in C/C++ headers and code ... OK * checking compilation flags used ... OK * checking compiled code ... WARNING File ‘RadEro/libs/RadEro.so’: Found ‘__vprintf_chk’, possibly from ‘vprintf’ (C) Object: ‘model.o’ Found ‘__vsprintf_chk’, possibly from ‘vsprintf’ (C) Objects: ‘cJSON.o’, ‘model.o’ Found ‘stderr’, possibly from ‘stderr’ (C) Object: ‘model.o’ 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. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual. * checking examples ... [8s/8s] NOTE Examples with CPU (user + system) or elapsed time > 5s user system elapsed RadEro 6.387 0.075 6.465 * checking PDF version of manual ... [2s/2s] OK * checking HTML version of manual ... [0s/0s] OK * checking for non-standard things in the check directory ... NOTE Found the following files/directories: ‘input-config_example.js’ ‘input-data_example.csv’ ‘results’ ‘temp’ * checking for detritus in the temp directory ... OK * DONE Status: 3 WARNINGs, 5 NOTEs