############################################################################## ############################################################################## ### ### Running command: ### ### E:\biocbuild\bbs-3.21-bioc\R\bin\R.exe CMD check --no-multiarch --install=check:rGADEM.install-out.txt --library=E:\biocbuild\bbs-3.21-bioc\R\library --no-vignettes --timings rGADEM_2.55.0.tar.gz ### ############################################################################## ############################################################################## * using log directory 'E:/biocbuild/bbs-3.21-bioc/meat/rGADEM.Rcheck' * using R Under development (unstable) (2024-10-26 r87273 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 'rGADEM/DESCRIPTION' ... OK * checking extension type ... Package * this is package 'rGADEM' version '2.55.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 'rGADEM' can be installed ... WARNING Found the following significant warnings: Gadem_Analysis.c:1415:16: warning: zero-length gnu_printf format string [-Wformat-zero-length] evalue_meme.h:153:11: warning: zero-length gnu_printf format string [-Wformat-zero-length] See 'E:/biocbuild/bbs-3.21-bioc/meat/rGADEM.Rcheck/00install.out' for details. * used C compiler: 'gcc.exe (GCC) 13.3.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: 'Biostrings' 'methods' 'seqLogo' 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 whether startup messages can be suppressed ... OK * checking dependencies in R code ... NOTE 'library' or 'require' call to 'methods' which was already attached by Depends. Please remove these calls from your code. Namespace in Imports field not imported from: 'GenomicRanges' All declared Imports should be used. * checking S3 generic/method consistency ... OK * checking replacement functions ... OK * checking foreign function calls ... OK * checking R code for possible problems ... NOTE File 'rGADEM/R/zzz.R': .onLoad calls: require(methods) Package startup functions should not change the search path. See section 'Good practice' in '?.onAttach'. GADEM: no visible global function definition for 'seqlevels' readGademPWMFile: no visible global function definition for 'read.csv' readPWMfile: no visible global function definition for 'read.table' readTransfacFile: no visible global function definition for 'read.table' [,gadem-ANY-ANY-ANY: no visible binding for global variable 'ANY' [,gadem-ANY-ANY-ANY : : no visible binding for global variable 'gadem' plot,gadem-ANY : : no visible global function definition for 'makePWM' plot,motif-ANY: no visible global function definition for 'makePWM' Undefined global functions or variables: ANY gadem makePWM read.csv read.table seqlevels Consider adding importFrom("utils", "read.csv", "read.table") 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 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 'E:/biocbuild/bbs-3.21-bioc/R/library/rGADEM/libs/x64/rGADEM.dll': Found '_exit', possibly from '_exit' (C) Found 'abort', possibly from 'abort' (C), 'runtime' (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 sizes of PDF files under 'inst/doc' ... OK * checking files in 'vignettes' ... OK * checking examples ... OK Examples with CPU (user + system) or elapsed time > 5s user system elapsed GADEM 79.52 0.03 79.58 * 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 'E:/biocbuild/bbs-3.21-bioc/meat/rGADEM.Rcheck/00check.log' for details.