############################################################################## ############################################################################## ### ### Running command: ### ### /Library/Frameworks/R.framework/Versions/Current/Resources/bin/R CMD check --install=check:bridge.install-out.txt --library=/Library/Frameworks/R.framework/Versions/Current/Resources/library --no-vignettes --timings bridge_1.56.0.tar.gz ### ############################################################################## ############################################################################## * using log directory ‘/Users/biocbuild/bbs-3.13-bioc/meat/bridge.Rcheck’ * using R version 4.1.1 (2021-08-10) * using platform: x86_64-apple-darwin17.0 (64-bit) * using session charset: UTF-8 * using option ‘--no-vignettes’ * checking for file ‘bridge/DESCRIPTION’ ... OK * this is package ‘bridge’ version ‘1.56.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 ... NOTE Found the following hidden files and directories: .git_fetch_output.txt .git_merge_output.txt These were most likely included in error. See section ‘Package structure’ in the ‘Writing R Extensions’ manual. * checking for portable file names ... OK * checking for sufficient/correct file permissions ... OK * checking whether package ‘bridge’ can be installed ... OK * checking installed package size ... OK * 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 ... NOTE 'library' or 'require' call to ‘rama’ which was already attached by Depends. Please remove these calls from your code. Package in Depends field not imported from: ‘rama’ These packages need to be imported from (in the NAMESPACE file) for when this namespace is loaded but not attached. * checking S3 generic/method consistency ... OK * checking replacement functions ... OK * checking foreign function calls ... OK * checking R code for possible problems ... NOTE File ‘bridge/R/zzz.R’: .onLoad calls: require("rama", quietly = TRUE) Package startup functions should not change the search path. See section ‘Good practice’ in '?.onAttach'. bridge.2samples: no visible global function definition for ‘var’ bridge.2samples: no visible global function definition for ‘median’ bridge.2samples: no visible global function definition for ‘mad’ bridge.3samples: no visible global function definition for ‘median’ bridge.3samples: no visible global function definition for ‘mad’ Undefined global functions or variables: mad median var Consider adding importFrom("stats", "mad", "median", "var") to your NAMESPACE file. * 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 contents of ‘data’ directory ... OK * checking data for non-ASCII characters ... OK * checking data for ASCII and uncompressed saves ... OK * 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/bridge/libs/bridge.so’: Found ‘_printf’, possibly from ‘printf’ (C) 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 sizes of PDF files under ‘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: 4 NOTEs See ‘/Users/biocbuild/bbs-3.13-bioc/meat/bridge.Rcheck/00check.log’ for details.