• using R Under development (unstable) (2024-12-28 r87474)
• using platform: x86_64-pc-linux-gnu
• R was compiled by     gcc-14 (Debian 14.2.0-8) 14.2.0     GNU Fortran (Debian 14.2.0-8) 14.2.0
• running under: Debian GNU/Linux trixie/sid
• using session charset: UTF-8
• checking for file ‘BRugs/DESCRIPTION’ ... OK
• this is package ‘BRugs’ version ‘0.9-2.1’
• 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 serialization versions ... OK
• checking whether package ‘BRugs’ can be installed ... OK See the install log for details.
• used C compiler: ‘gcc-14 (Debian 14.2.0-8) 14.2.0’
• checking package directory ... OK
• checking for future file timestamps ... OK
• checking DESCRIPTION meta-information ... OK
• 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 ... [0s/1s] OK
• checking whether the package can be loaded with stated dependencies ... [0s/0s] OK
• checking whether the package can be unloaded cleanly ... [0s/0s] OK
• checking whether the namespace can be loaded with stated dependencies ... [0s/0s] OK
• checking whether the namespace can be unloaded cleanly ... [0s/0s] OK
• checking loading without being on the library search path ... [0s/0s] OK
• checking whether startup messages can be suppressed ... [0s/1s] 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 ... [5s/8s] OK
• checking Rd files ... [0s/1s] 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 ... [0s/0s] 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 ... OK
• 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 ... NOTE Found the following Makefile(s) with an include directive with a pathname using R_HOME:   src/Makefile.win Even though not recommended, variable R_HOME may contain spaces. Makefile directives use space as a separator and there is no portable way to quote/escape the space in Make rules and directives. However, one can and should quote pathnames when passed from Makefile to the shell, and this can be done specifically when invoking Make recursively. It is therefore recommended to use the Make '-f' option to include files in directories specified using R_HOME. This option can be specified multiple times to include multiple Makefiles. Note that 'Makeconf' is included automatically into top-level makefile of a package. More information can be found in 'Writing R Extensions'.
• checking pragmas in C/C++ headers and code ... OK
• checking compilation flags used ... OK
• checking compiled code ... OK
• checking examples ... [0s/1s] OK
• checking for unstated dependencies in ‘tests’ ... OK
• checking tests ... [29s/48s] NOTE   Running ‘BRugs.R’ [3s/5s]   Comparing ‘BRugs.Rout’ to ‘BRugs.Rout.save’ ...65c65 < Welcome to BRugs connected to OpenBUGS version 3.2.2 --- > Welcome to BRugs connected to OpenBUGS version 3.2.3   Running ‘examples.R’ [18s/27s]   Comparing ‘examples.Rout’ to ‘examples.Rout.save’ ...55c55 < Welcome to BRugs connected to OpenBUGS version 3.2.2 --- > Welcome to BRugs connected to OpenBUGS version 3.2.3 106c106 < 20000 updates took 1 s --- > 20000 updates took 2 s 205c205 < 20000 updates took 1 s --- > 20000 updates took 3 s 218c218 < 20000 updates took 1 s --- > 20000 updates took 2 s   Running ‘examples.stats.R’ [0s/1s]   Running ‘functions.R’ [8s/15s]   Comparing ‘functions.Rout’ to ‘functions.Rout.save’ ...138c138 < Welcome to BRugs connected to OpenBUGS version 3.2.2 --- > Welcome to BRugs connected to OpenBUGS version 3.2.3   Running ‘local.R’ [0s/0s]
• checking PDF version of manual ... [5s/6s] OK
• checking HTML version of manual ... [1s/2s] OK
• checking for non-standard things in the check directory ... OK
• DONE

Status: 2 NOTEs