############################################################################## ############################################################################## ### ### Running command: ### ### C:\Users\biocbuild\bbs-3.20-bioc\R\bin\R.exe CMD check --no-multiarch --install=check:fmcsR.install-out.txt --library=C:\Users\biocbuild\bbs-3.20-bioc\R\library --no-vignettes --timings fmcsR_1.47.0.tar.gz ### ############################################################################## ############################################################################## * using log directory 'C:/Users/biocbuild/bbs-3.20-bioc/meat/fmcsR.Rcheck' * using R version 4.4.1 (2024-06-14 ucrt) * using platform: x86_64-w64-mingw32 * R was compiled by gcc.exe (GCC) 13.2.0 GNU Fortran (GCC) 13.2.0 * running under: Windows Server 2022 x64 (build 20348) * using session charset: UTF-8 * using option '--no-vignettes' * checking for file 'fmcsR/DESCRIPTION' ... OK * checking extension type ... Package * this is package 'fmcsR' version '1.47.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 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 'C:/Users/biocbuild/bbs-3.20-bioc/meat/fmcsR.Rcheck/00install.out' for details. * used C++ compiler: 'G__~1.EXE (GCC) 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 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 for x64 is not available File 'C:/Users/biocbuild/bbs-3.20-bioc/R/library/fmcsR/libs/x64/fmcsR.dll': Found '_exit', possibly from '_exit' (C) Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran) Found 'exit', possibly from 'exit' (C), 'stop' (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 ... OK Examples with CPU (user + system) or elapsed time > 5s user system elapsed fmcsR-package 1.00 0.36 7.78 fmcsBatch 0.04 0.02 6.49 * 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: 1 WARNING, 5 NOTEs See 'C:/Users/biocbuild/bbs-3.20-bioc/meat/fmcsR.Rcheck/00check.log' for details.