• using R version 2.15.0 beta (2012-03-15 r58760)
• using platform: i386-apple-darwin9.8.0 (32-bit)
• using session charset: ASCII
• checking for file 'BCBCSF/DESCRIPTION' ... OK
• this is package 'BCBCSF' version '0.0-1'
• 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 whether package 'BCBCSF' 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
• loading checks for arch 'i386'
  ** 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
• loading checks for arch 'x86_64'
  ** 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 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 ... NOTE
  File 'BCBCSF/R/loadpkg.r':
  .First.lib calls:
  cat(sprintf("Package 'BCBCSF' loaded, type ?bcbcsfexamples to start\n"))
  library("abind")
  
  Package startup functions should not change the search path.
  Package startup functions should use 'packageStartupMessage' to
  generate messages.
  See section 'Good practice' in ?.onAttach.
  
• 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 line endings in Makefiles ... OK
• checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK
• checking compiled code ... OK
• checking examples ...
  ** running examples for arch 'i386' ... OK
  ** running examples for arch 'x86_64' ... OK
• checking PDF version of manual ... OK
  NOTE: There were 2 notes.
  See
  '/Volumes/Tiger/Builds/Rdev-web/QA/Simon/packages/leopard-universal/results/2.15/BCBCSF.Rcheck/00check.log'
  for details.
• elapsed time (check, wall clock): 0:52