• using R Under development (unstable) (2012-08-14 r60253)
• using platform: x86_64-unknown-linux-gnu (64-bit)
• using session charset: UTF-8
• checking for file ‘AnalyzeFMRI/DESCRIPTION’ ... OK
• this is package ‘AnalyzeFMRI’ version ‘1.1-14’
• checking package dependencies ... OK
• checking if this is a source package ... OK
• checking if there is a namespace ... NOTE
  As from R 2.14.0 all packages need a namespace.
  One will be generated on installation, but it is better to handcraft a
  NAMESPACE file: R CMD build will produce a suitable starting point.
  CRAN requires a NAMESPACE file for all submissions.
• checking for executable files ... OK
• checking for hidden files and directories ... OK
• checking whether package ‘AnalyzeFMRI’ can be installed ... OK
• checking installed package size ... OK
• checking package directory ... OK
• checking for portable file names ... OK
• checking for sufficient/correct file permissions ... OK
• checking DESCRIPTION meta-information ... OK
• checking top-level 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 loading without being on the library search path ... OK
• checking for unstated 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 ... NOTE
  prepare_Rd: eigenvalues.Rd:12-13: Dropping empty section \seealso
  prepare_Rd: fourDto2D.Rd:17-20: Dropping empty section \examples
  prepare_Rd: twoDto4D.Rd:16-19: Dropping empty section \examples
• 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 C/C++/Fortran sources/headers ... OK
• checking line endings in Makefiles ... OK
• checking for portable compilation flags in Makevars ... OK
• checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK
• checking compiled code ... NOTE
  File ‘/data/blackswan/ripley/R/packages/tests-devel/AnalyzeFMRI.Rcheck/AnalyzeFMRI/libs/AnalyzeFMRI.so’:
  Found ‘_gfortran_st_write’, possibly from ‘write’ (Fortran), ‘print’
  (Fortran)
  Object: ‘slamc.o’
  
  Compiled code should not call functions which might terminate R nor
  write to stdout/stderr instead of to the console.
  
  See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual.
• checking examples ... [37s/37s] OK
• checking for unstated dependencies in tests ... OK
• checking tests ... OK
  Running ‘test.R’
  Comparing ‘test.Rout’ to ‘test.Rout.save’ ...8,29d7
  < Loading Tcl/Tk interface ... done
  < R.methodsS3 v1.4.2 (2012-06-22) successfully loaded. See ?R.methodsS3 for help.
  < R.oo v1.9.8 (2012-06-22) successfully loaded. See ?R.oo for help.
  <
  < Attaching package: 'R.oo'
  <
  < The following object(s) are masked from 'package:methods':
  <
  < getClasses, getMethods
  <
  < The following object(s) are masked from 'package:base':
  <
  < attach, detach, gc, load, save
  <
  < R.matlab v1.6.1 (2012-06-30) successfully loaded. See ?R.matlab for help.
  <
  < Attaching package: 'R.matlab'
  <
  < The following object(s) are masked from 'package:base':
  <
  < getOption, isOpen
  <
• checking PDF version of manual ... OK
  NOTE: There were 3 notes.
  See
  ‘/data/blackswan/ripley/R/packages/tests-devel/AnalyzeFMRI.Rcheck/00check.log’
  for details.