• using R Under development (unstable) (2012-02-06 r58287)
• using platform: i686-pc-linux-gnu (32-bit)
• using session charset: UTF-8
• checking for file ‘locfit/DESCRIPTION’ ... OK
• this is package ‘locfit’ version ‘1.5-6’
• 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.
• checking for executable files ... OK
• checking whether package ‘locfit’ 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 ‘locfit/R/firstlib.r’:
  .First.lib calls:
  cat(paste(pkgname, ver[1], "\t", ver[2], "\n"))
  
  Package startup functions should use ‘packageStartupMessage’ to
  generate messages.
  See section ‘Good practice’ in ?.onAttach.
  
  lfbas: no visible global function definition for ‘basis’
  locfit: no visible binding for global variable ‘response’
  locfit.matrix: no visible binding for global variable ‘response’
  locfit.matrix: no visible binding for global variable ‘cens’
  plot.scb.2d : plot.tl: no visible binding for global variable ‘v’
• 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 ... WARNING
  Assignments in \usage in documentation object 'rva':
  rv(fit) <- 1.2345
  
  Functions with \usage entries need to have the appropriate \alias
  entries, and all their arguments documented.
  The \usage entries must correspond to syntactically valid R code.
  See the chapter ‘Writing R documentation files’ in the ‘Writing R
  Extensions’ manual.
  S3 methods shown with full name in documentation object 'density.lf':
  ‘density.lf’
  
  S3 methods shown with full name in documentation object 'plot.eval':
  ‘plot.eval’
  
  S3 methods shown with full name in documentation object 'plot.locfit.1d':
  ‘plot.locfit.1d’
  
  S3 methods shown with full name in documentation object 'plot.locfit.2d':
  ‘plot.locfit.2d’
  
  S3 methods shown with full name in documentation object 'plot.locfit.3d':
  ‘plot.locfit.3d’
  
  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 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 ... NOTE
  File ‘/home/hornik/tmp/R.check/r-devel/Work/build/Packages/locfit/libs/locfit.so’:
  Found ‘printf’, possibly from ‘printf’ (C)
  Found ‘puts’, possibly from ‘printf’ (C), ‘puts’ (C)
  
  Compiled code should not call functions which might terminate R nor
  write to stdout/stderr instead of to the console. The detected symbols
  are linked into the code but might come from libraries and not actually
  be called.
  
  See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual.
• checking examples ... [2s/2s] OK
• checking PDF version of manual ... OK
  WARNING: There was 1 warning.
  NOTE: There were 3 notes.
  See
  ‘/home/hornik/tmp/R.check/r-devel/Work/PKGS/locfit.Rcheck/00check.log’
  for details.