############################################################################## ############################################################################## ### ### Running command: ### ### /home/biocbuild/bbs-3.20-bioc/R/bin/R CMD check --install=check:fmcsR.install-out.txt --library=/home/biocbuild/bbs-3.20-bioc/R/site-library --timings fmcsR_1.48.0.tar.gz ### ############################################################################## ############################################################################## * using log directory ‘/media/volume/teran2_disk/biocbuild/bbs-3.20-bioc/meat/fmcsR.Rcheck’ * using R version 4.4.2 (2024-10-31) * using platform: x86_64-pc-linux-gnu * R was compiled by gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0 GNU Fortran (Ubuntu 13.2.0-23ubuntu4) 13.2.0 * running under: Ubuntu 24.04.1 LTS * using session charset: UTF-8 * checking for file ‘fmcsR/DESCRIPTION’ ... OK * checking extension type ... Package * this is package ‘fmcsR’ version ‘1.48.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 ‘fmcsR’ can be installed ... WARNING Found the following significant warnings: MCSCompound.cpp:87:23: warning: ‘void* memcpy(void*, const void*, size_t)’ writing to an object of type ‘struct FMCS::MCSCompound::Atom’ with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess] MCSCompound.cpp:123:19: warning: ‘void* memcpy(void*, const void*, size_t)’ writing to an object of type ‘struct FMCS::MCSCompound::Atom’ with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess] See ‘/media/volume/teran2_disk/biocbuild/bbs-3.20-bioc/meat/fmcsR.Rcheck/00install.out’ for details. * used C++ compiler: ‘g++ (Ubuntu 13.2.0-23ubuntu4) 13.2.0’ * checking installed package size ... OK * checking package directory ... OK * checking ‘build’ directory ... OK * checking DESCRIPTION meta-information ... NOTE Packages listed in more than one of Depends, Imports, Suggests, Enhances: ‘methods’ ‘ChemmineR’ A package should be listed in only one of these fields. * checking top-level files ... OK * 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 loading without being on the library search path ... OK * checking dependencies in R code ... NOTE 'library' or 'require' call to ‘ChemmineR’ which was already attached by Depends. Please remove these calls from your code. Namespaces in Imports field not imported from: ‘BiocGenerics’ ‘RUnit’ ‘methods’ All declared Imports should be used. Package in Depends field not imported from: ‘methods’ 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 fmcs: no visible global function definition for ‘as’ fmcs: no visible global function definition for ‘new’ fmcsBatch: no visible global function definition for ‘as’ fmcsBatch : score: no visible global function definition for ‘as’ plotMCS: no visible global function definition for ‘par’ coerce,list-MCS: no visible global function definition for ‘new’ Undefined global functions or variables: as new par Consider adding importFrom("graphics", "par") importFrom("methods", "as", "new") to your NAMESPACE file (and ensure that your DESCRIPTION Imports field contains 'methods'). * 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 shell scripts ... OK * checking line endings in C/C++/Fortran sources/headers ... OK * checking line endings in Makefiles ... OK * checking compilation flags in Makevars ... NOTE Package has both ‘src/Makevars.in’ and ‘src/Makevars’. Installation with --no-configure' is unlikely to work. If you intended ‘src/Makevars’ to be used on Windows, rename it to ‘src/Makevars.win’ otherwise remove it. If ‘configure’ created ‘src/Makevars’, you need a ‘cleanup’ script. * 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 is not available * checking files in ‘vignettes’ ... OK * checking examples ... OK Examples with CPU (user + system) or elapsed time > 5s user system elapsed fmcsR-package 0.777 0.046 9.490 fmcsBatch 0.034 0.010 7.573 * checking for unstated dependencies in vignettes ... OK * checking package vignettes ... OK * checking re-building of vignette outputs ... OK * checking PDF version of manual ... OK * DONE Status: 1 WARNING, 5 NOTEs See ‘/media/volume/teran2_disk/biocbuild/bbs-3.20-bioc/meat/fmcsR.Rcheck/00check.log’ for details.