orcv
About orcv
|
Version: 1.1
Result: WARNING Check time: 2023-11-18 22:51 * using log directory ‘’ * using R Under development (unstable) (2022-11-28 r83388) * using platform: x86_64-pc-linux-gnu (64-bit) * using session charset: UTF-8 * using option ‘--as-cran’ * checking for file ‘orcv/DESCRIPTION’ ... OK * checking extension type ... Package * this is package ‘orcv’ version ‘1.1’ * checking package namespace information ... OK * checking package dependencies ... OK * checking if this is a source package ... WARNING Subdirectory ‘src’ contains: Doxyfile These are unlikely file names for src files. * 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 serialization versions ... OK * checking whether package ‘orcv’ can be installed ... WARNING Found the following significant warnings: comms.c:131:39: warning: pointer of type ‘void *’ used in arithmetic [-Wpointer-arith] comms.c:219:39: warning: pointer of type ‘void *’ used in arithmetic [-Wpointer-arith] See ‘00install.out’ for details. * checking installed package size ... OK * checking package directory ... OK * checking for future file timestamps ... OK * checking DESCRIPTION meta-information ... NOTE License components which are templates and need '+ file LICENSE': MIT * checking top-level files ... NOTE Non-standard file/directory found at top level: ‘makefile’ * 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 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 ... WARNING Undocumented code objects: ‘address’ ‘as.FD’ ‘as.Location’ ‘fd’ ‘header’ ‘is.FD’ ‘is.Location’ ‘location’ ‘payload’ ‘port’ All user-level objects in a package should have documentation entries. See chapter ‘Writing R documentation files’ in the ‘Writing R Extensions’ manual. * checking for code/documentation mismatches ... OK * checking Rd \usage sections ... WARNING Objects in \usage without \alias in documentation object 'receive': ‘receive.FD’ Undocumented arguments in documentation object 'send' ‘header’ ‘payload’ ‘keep_conn’ ‘port’ Objects in \usage without \alias in documentation object 'send': ‘send.Message’ ‘send.FD’ ‘send.character’ Functions with \usage entries need to have the appropriate \alias entries, and all their arguments documented. The \usage entries must correspond to syntactically valid R code. See chapter ‘Writing R documentation files’ in the ‘Writing R Extensions’ manual. S3 methods shown with full name in documentation object 'receive': ‘receive.FD’ S3 methods shown with full name in documentation object 'send': ‘send.Message’ ‘send.FD’ ‘send.character’ The \usage entries for S3 methods should use the \method markup and not their full name. See chapter ‘Writing R documentation files’ in the ‘Writing R Extensions’ manual. * checking Rd contents ... OK * checking for unstated dependencies in examples ... OK * checking line endings in C/C++/Fortran sources/headers ... OK * checking line endings in Makefiles ... OK * checking compilation flags in Makevars ... WARNING Non-portable flags in variable 'PKG_CFLAGS': -g -Wall * 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 use of SHLIB_OPENMP_*FLAGS in Makefiles ... OK * checking include directives in Makefiles ... OK * checking pragmas in C/C++ headers and code ... OK * checking compilation flags used ... OK * checking compiled code ... NOTE File ‘orcv/libs/orcv.so’: Found ‘printf’, possibly from ‘printf’ (C) Object: ‘start.o’ Found ‘stderr’, possibly from ‘stderr’ (C) Object: ‘comms.o’ File ‘orcv/libs/orcv.so’: Found no calls to: ‘R_registerRoutines’, ‘R_useDynamicSymbols’ 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. It is good practice to register native routines and to disable symbol search. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual. * checking examples ... OK * checking PDF version of manual ... 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: 5 WARNINGs, 3 NOTEs See ‘/00check.log’ for details. Installation log: 00install.out
|