* using log directory 'd:/Rcompile/CRANpkg/local/3.4/multxpert.Rcheck' * using R version 3.4.4 (2018-03-15) * using platform: x86_64-w64-mingw32 (64-bit) * using session charset: ISO8859-1 * checking for file 'multxpert/DESCRIPTION' ... OK * this is package 'multxpert' version '0.1' * 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 'multxpert' can be installed ... OK * checking installed package size ... OK * checking package 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 loading without being on the library search path ... 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 ... [8s] NOTE File 'multxpert/R/zzz.R': .onLoad calls: cat("multxpert: Implementation of commonly used p-value based and parametric\n", "multiple testing procedures and parallel gatekeeping procedures.\n", "For more information visit http://multxpert.com/wiki/MultXpert_package\n", sep = "") Package startup functions should use 'packageStartupMessage' to generate messages. See section 'Good practice' in '?.onAttach'. paradjp: no visible global function definition for 'pt' parci: no visible global function definition for 'qt' pdunnett: no visible global function definition for 'GenzBretz' pvalci: no visible global function definition for 'qnorm' qdunnett: no visible global function definition for 'GenzBretz' Undefined global functions or variables: GenzBretz pt qnorm qt Consider adding importFrom("stats", "pt", "qnorm", "qt") 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 examples ... [5s] OK * checking PDF version of manual ... OK * DONE Status: 1 NOTE