• using R version 2.15.0 (2012-03-30)
• using platform: i686-pc-linux-gnu (32-bit)
• using session charset: UTF-8
• checking for file ‘BPHO/DESCRIPTION’ ... OK
• this is package ‘BPHO’ version ‘1.3-0’
• 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 ‘BPHO’ 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 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 ‘BPHO/R/firstlib.r’:
  .First.lib calls:
  cat("Bayesian Prediction with High-order Models(BPHO) loaded\n", "COPYRIGHT 2007-2009 (c) Longhai Li (http://math.usask.ca/~longhai)\n", "Type ?begin.BPHO for help to this package\n", sep = "")
  
  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 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 ... NOTE
  File ‘/home/hornik/tmp/R.check/r-release/Work/build/Packages/BPHO/libs/BPHO.so’:
  Found ‘exit’, possibly from ‘exit’ (C)
  Object: ‘all.o’
  Found ‘printf’, possibly from ‘printf’ (C)
  Object: ‘all.o’
  Found ‘putchar’, possibly from ‘putchar’ (C)
  Object: ‘all.o’
  Found ‘puts’, possibly from ‘printf’ (C), ‘puts’ (C)
  Object: ‘all.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 ... [68s/68s] OK
• checking PDF version of manual ... OK
  NOTE: There were 3 notes.
  See
  ‘/home/hornik/tmp/R.check/r-release/Work/PKGS/BPHO.Rcheck/00check.log’
  for details.