##############################################################################
##############################################################################
###
### Running command:
###
###   /home/biocbuild/bbs-3.20-bioc/R/bin/R CMD check --install=check:trigger.install-out.txt --library=/home/biocbuild/bbs-3.20-bioc/R/site-library --timings trigger_1.52.0.tar.gz
###
##############################################################################
##############################################################################


* using log directory ‘/home/biocbuild/bbs-3.20-bioc/meat/trigger.Rcheck’
* using R version 4.4.2 (2024-10-31)
* using platform: x86_64-pc-linux-gnu
* R was compiled by
    gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0
    GNU Fortran (Ubuntu 13.2.0-23ubuntu4) 13.2.0
* running under: Ubuntu 24.04.1 LTS
* using session charset: UTF-8
* checking for file ‘trigger/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘trigger’ version ‘1.52.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 for sufficient/correct file permissions ... OK
* checking whether package ‘trigger’ can be installed ... OK
* used C compiler: ‘gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0’
* checking installed package size ... OK
* checking package directory ... OK
* checking ‘build’ 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 ... 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 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 ... NOTE
initialize,trigger: no visible global function definition for
  ‘callNextMethod’
Undefined global functions or variables:
  callNextMethod
Consider adding
  importFrom("methods", "callNextMethod")
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 C/C++/Fortran sources/headers ... OK
* checking compiled code ... NOTE
Note: information on .o files is not available
* checking files in ‘vignettes’ ... OK
* checking examples ... OK
Examples with CPU (user + system) or elapsed time > 5s
                       user system elapsed
trigger-export2cross 23.862  0.587  24.451
* checking for unstated dependencies in vignettes ... OK
* checking package vignettes ... OK
* checking re-building of vignette outputs ... OK
* checking PDF version of manual ... OK
* DONE

Status: 2 NOTEs
See
  ‘/home/biocbuild/bbs-3.20-bioc/meat/trigger.Rcheck/00check.log’
for details.

##############################################################################
##############################################################################
###
### Running command:
###
###   /home/biocbuild/bbs-3.20-bioc/R/bin/R CMD INSTALL trigger
###
##############################################################################
##############################################################################


* installing to library ‘/home/biocbuild/bbs-3.20-bioc/R/site-library’
* installing *source* package ‘trigger’ ...
** using staged installation
** libs
using C compiler: ‘gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0’
gcc -I"/home/biocbuild/bbs-3.20-bioc/R/include" -DNDEBUG   -I/usr/local/include    -fpic  -g -O2  -Wall -c trigger.c -o trigger.o
trigger.c: In function ‘mergeorder’:
trigger.c:25:20: warning: variable ‘n3’ set but not used [-Wunused-but-set-variable]
   25 | int i1,i2,i3,n1,n2,n3;
      |                    ^~
trigger.c: In function ‘sec_link_stat’:
trigger.c:81:10: warning: variable ‘nct’ set but not used [-Wunused-but-set-variable]
   81 | int ntr, nct, i, j;
      |          ^~~
trigger.c: In function ‘sec_link_stat_x’:
trigger.c:153:10: warning: variable ‘nct’ set but not used [-Wunused-but-set-variable]
  153 | int ntr, nct, i, j, k, nk;
      |          ^~~
trigger.c: In function ‘condi_indep_stat’:
trigger.c:233:10: warning: variable ‘nct’ set but not used [-Wunused-but-set-variable]
  233 | int ntr, nct, i, j;
      |          ^~~
trigger.c: In function ‘condi_indep_stat_x’:
trigger.c:310:10: warning: variable ‘nct’ set but not used [-Wunused-but-set-variable]
  310 | int ntr, nct, i, j, k, nk;
      |          ^~~
trigger.c: In function ‘condi_indep_stat_rx’:
trigger.c:393:10: warning: variable ‘nct’ set but not used [-Wunused-but-set-variable]
  393 | int ntr, nct, i, j, k, nk;
      |          ^~~
gcc -shared -L/home/biocbuild/bbs-3.20-bioc/R/lib -L/usr/local/lib -o trigger.so trigger.o -L/home/biocbuild/bbs-3.20-bioc/R/lib -lR
installing to /home/biocbuild/bbs-3.20-bioc/R/site-library/00LOCK-trigger/00new/trigger/libs
** R
** data
** inst
** byte-compile and prepare package for lazy loading
** help
*** installing help indices
** building package indices
** installing vignettes
** testing if installed package can be loaded from temporary location
** checking absolute paths in shared objects and dynamic libraries
** testing if installed package can be loaded from final location
** testing if installed package keeps a record of temporary installation path
* DONE (trigger)