• using R version 2.15.0 Patched (2012-05-19 r59366)
  • using platform: x86_64-unknown-linux-gnu (64-bit)
  • using session charset: UTF-8
  • checking for file ‘R4dfp/DESCRIPTION’ ... OK
  • this is package ‘R4dfp’ version ‘0.1-9’
  • 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 for executable files ... OK
  • checking whether package ‘R4dfp’ 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 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 ... OK
  • checking Rd files ... NOTE
    prepare_Rd: blank.4dfp.Rd:40-41: Dropping empty section \details
    prepare_Rd: blank.4dfp.Rd:47-48: Dropping empty section \references
    prepare_Rd: close.R4dfp.Rd:33-34: Dropping empty section \references
    prepare_Rd: coord.to.voxel.4dfp.Rd:31-32: Dropping empty section \references
    prepare_Rd: copy.4dfp.Rd:32-33: Dropping empty section \references
    prepare_Rd: load.4dfp.Rd:100-101: Dropping empty section \references
    prepare_Rd: recycle.4dfp.Rd:44-45: Dropping empty section \references
    prepare_Rd: save.4dfp.Rd:25-26: Dropping empty section \references
    prepare_Rd: voxel.to.coord.4dfp.Rd:31-32: Dropping empty section \references
  • 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 'close.R4dfp':
    ‘close.R4dfp’

    S3 methods shown with full name in documentation object 'load.4dfp':
    ‘print.R4dfp’

    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 compilation flags in Makevars ... OK
  • checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK
  • checking compiled code ... NOTE
    File ‘/home/hornik/tmp/R.check/r-patched/Work/build/Packages/R4dfp/libs/R4dfp.so’:
    Found ‘stderr’, possibly from ‘stderr’ (C)
    Object: ‘R4dfp-object.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 ... [1s/1s] OK
  • checking PDF version of manual ... OK
    NOTE: There were 3 notes.
    See
    ‘/home/hornik/tmp/R.check/r-patched/Work/PKGS/R4dfp.Rcheck/00check.log’
    for details.