Check results for 'BoltzMM' (original) (raw)

• using R Under development (unstable) (2024-11-08 r87306)
• using platform: x86_64-pc-linux-gnu
• R was compiled by clang version 19.1.3 flang-new version 19.1.3
• running under: Fedora Linux 36 (Workstation Edition)
• using session charset: UTF-8
• using option ‘--no-stop-on-test-error’
• checking for file ‘BoltzMM/DESCRIPTION’ ... OK
• checking extension type ... Package
• this is package ‘BoltzMM’ version ‘0.1.4’
• package encoding: UTF-8
• 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 executable files ... OK
• checking for hidden files and directories ... OK
• checking for portable file names ... OK
• checking for sufficient/correct file permissions ... OK
• checking whether package ‘BoltzMM’ can be installed ... [49s/46s] OK See the install log for details.
• used C++ compiler: ‘clang version 19.1.3’
• checking C++ specification ... NOTE Specified C++11: please drop specification unless essential
• 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 ... NOTEProblems with news in ‘NEWS.md’: No news entries found.
• 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 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 ... OK
• checking Rd files ... OK
• checking Rd metadata ... OK
• checking Rd line widths ... 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 LazyData ... OK
• checking data for ASCII and uncompressed saves ... OK
• checking line endings in C/C++/Fortran sources/headers ... OK
• checking line endings in Makefiles ... OK
• checking compilation flags in Makevars ... OK
• checking for GNU extensions in Makefiles ... OK
• checking for portable use of (BLASLIBS)and(BLAS_LIBS) and (BLASLIBS)and(LAPACK_LIBS) ... OK
• checking use of PKG_*FLAGS in Makefiles ... OK
• checking use of SHLIB_OPENMP_*FLAGS in Makefiles ... OK
• checking pragmas in C/C++ headers and code ... OK
• checking compilation flags used ... OK
• checking compiled code ... OK
• checking examples ... OK
• checking for unstated dependencies in ‘tests’ ... OK
• checking tests ... OK Running ‘testthat.R’
• checking PDF version of manual ... [7s/12s] OK
• checking HTML version of manual ... OK
• checking for non-standard things in the check directory ... OK
• checking for detritus in the temp directory ... OK
• DONE

Status: 2 NOTEs