############################################################################## ############################################################################## ### ### Running command: ### ### F:\biocbuild\bbs-3.20-bioc\R\bin\R.exe CMD check --no-multiarch --install=check:RProtoBufLib.install-out.txt --library=F:\biocbuild\bbs-3.20-bioc\R\library --no-vignettes --timings RProtoBufLib_2.18.0.tar.gz ### ############################################################################## ############################################################################## * using log directory 'F:/biocbuild/bbs-3.20-bioc/meat/RProtoBufLib.Rcheck' * using R version 4.4.2 (2024-10-31 ucrt) * using platform: x86_64-w64-mingw32 * R was compiled by gcc.exe (GCC) 13.3.0 GNU Fortran (GCC) 13.3.0 * running under: Windows Server 2022 x64 (build 20348) * using session charset: UTF-8 * using option '--no-vignettes' * checking for file 'RProtoBufLib/DESCRIPTION' ... OK * checking extension type ... Package * this is package 'RProtoBufLib' version '2.18.0' * 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 ... NOTE Found the following non-portable file path: RProtoBufLib/windows/protobuf-3.8.0/include/google/protobuf/compiler/objectivec/objectivec_generator.h Tarballs are only required to store paths of up to 100 bytes and cannot store those of more than 256 bytes, with restrictions including to 100 bytes for the final component. See section 'Package structure' in the 'Writing R Extensions' manual. * checking whether package 'RProtoBufLib' can be installed ... OK * used C++ compiler: 'G__~1.EXE (GCC) 13.3.0' * checking C++ specification ... NOTE Specified C++11: please drop specification unless essential * checking installed package size ... NOTE installed size is 9.4Mb sub-directories of 1Mb or more: include 2.9Mb lib 6.4Mb * checking package directory ... OK * checking 'build' directory ... OK * checking DESCRIPTION meta-information ... NOTE License components which are templates and need '+ file LICENSE': BSD_3_clause * checking top-level files ... NOTE File LICENSE is not mentioned in the DESCRIPTION file. * 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 whether startup messages can be suppressed ... 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 ... OK * checking Rd files ... 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 ... OK * checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK * checking use of PKG_*FLAGS in Makefiles ... OK * checking compiled code ... NOTE Note: information on .o files for x64 is not available File 'F:/biocbuild/bbs-3.20-bioc/R/library/RProtoBufLib/libs/x64/RProtoBufLib.dll': Found '_exit', possibly from '_exit' (C) Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran) 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 files in 'vignettes' ... OK * checking examples ... NONE * checking for unstated dependencies in vignettes ... OK * checking package vignettes ... OK * checking running R code from vignettes ... SKIPPED * checking re-building of vignette outputs ... SKIPPED * checking PDF version of manual ... OK * DONE Status: 6 NOTEs See 'F:/biocbuild/bbs-3.20-bioc/meat/RProtoBufLib.Rcheck/00check.log' for details.