############################################################################## ############################################################################## ### ### Running command: ### ### /Library/Frameworks/R.framework/Resources/bin/R CMD check --install=check:NuPoP.install-out.txt --library=/Library/Frameworks/R.framework/Resources/library --no-vignettes --timings NuPoP_2.2.0.tar.gz ### ############################################################################## ############################################################################## * using log directory ‘/Users/biocbuild/bbs-3.14-bioc/meat/NuPoP.Rcheck’ * using R version 4.1.3 (2022-03-10) * using platform: x86_64-apple-darwin17.0 (64-bit) * using session charset: UTF-8 * using option ‘--no-vignettes’ * checking for file ‘NuPoP/DESCRIPTION’ ... OK * checking extension type ... Package * this is package ‘NuPoP’ version ‘2.2.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 ... OK * checking for sufficient/correct file permissions ... OK * checking whether package ‘NuPoP’ can be installed ... OK * checking installed package size ... NOTE installed size is 7.5Mb sub-directories of 1Mb or more: R 3.8Mb doc 1.3Mb extdata 2.2Mb * 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 R 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 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 R/sysdata.rda ... NOTE Note: significantly better compression could be obtained by using R CMD build --resave-data old_size new_size compress sysdata.rda 4.6Mb 2.9Mb xz * checking line endings in C/C++/Fortran sources/headers ... OK * checking compiled code ... NOTE Note: information on .o files is not available File ‘/Library/Frameworks/R.framework/Versions/4.1/Resources/library/NuPoP/libs/NuPoP.so’: Found ‘__gfortran_st_close’, possibly from ‘close’ (Fortran) Found ‘__gfortran_st_open’, possibly from ‘open’ (Fortran) Found ‘__gfortran_st_read’, possibly from ‘read’ (Fortran) Found ‘__gfortran_st_write’, possibly from ‘write’ (Fortran), ‘print’ (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. 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 installed files from ‘inst/doc’ ... OK * checking files in ‘vignettes’ ... OK * checking examples ... OK * checking for unstated dependencies in vignettes ... OK * checking package vignettes in ‘inst/doc’ ... OK * checking running R code from vignettes ... SKIPPED * checking re-building of vignette outputs ... SKIPPED * checking PDF version of manual ... OK * DONE Status: 3 NOTEs See ‘/Users/biocbuild/bbs-3.14-bioc/meat/NuPoP.Rcheck/00check.log’ for details.