• using R version 2.15.0 (2012-03-30)
• using platform: x86_64-pc-mingw32 (64-bit)
• using session charset: ISO8859-1
• checking for file 'far/DESCRIPTION' ... OK
• this is package 'far' version '0.6-3'
• 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 whether package 'far' can be installed ... OK
• checking installed package size ... OK
• checking package directory ... OK
• checking for portable file names ... 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
  ** checking whether the namespace can be loaded with stated dependencies ... OK
  ** checking whether the namespace can be unloaded cleanly ... OK
• loading checks for arch 'x64'
  ** 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 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 'far/R/zzz.R':
  .onAttach calls:
  cat("far library : Modelization for Functional AutoRegressive processes\n")
  cat("version 0.6-0 (2005-01-10)\n")
  
  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 ... NOTE
  S3 methods shown with full name in documentation object 'coef.far':
  'coef.far'
  
  S3 methods shown with full name in documentation object 'is.na.fdata':
  'is.na.fdata'
  
  S3 methods shown with full name in documentation object 'multplot':
  'multplot.fdata'
  
  S3 methods shown with full name in documentation object 'plot.fdata':
  'plot.fdata'
  
  S3 methods shown with full name in documentation object 'predict.far':
  'predict.far'
  
  S3 methods shown with full name in documentation object 'predict.kerfon':
  'predict.kerfon'
  
  The \usage entries for S3 methods should use the \method markup and not
  their full name.
  See the chapter 'Writing R documentation files' in the 'Writing R
  Extensions' manual.
• 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 ... OK
• checking examples ...
  ** running examples for arch 'i386' ... OK
  ** running examples for arch 'x64' ... OK
• checking PDF version of manual ... OK
  NOTE: There were 2 notes.
  See
  'd:/Rcompile/CRANpkg/local/2.15/far.Rcheck/00check.log'
  for details.