• using R version 2.11.1 (2010-05-31)
  • using session charset: ISO8859-1
  • checking for file 'RNetCDF/DESCRIPTION' ... OK
  • this is package 'RNetCDF' version '1.2-1.1'
  • checking package dependencies ... OK
  • checking if this is a source package ... OK
  • checking whether package 'RNetCDF' can be installed ... WARNING
    Found the following significant warnings:
    Warning: ./man/att.inq.nc.Rd:11: unexpected '}'
    See http://www.r-project.org/nosvn/R.check/r-patched-windows64-x86_64/RNetCDF-00install.html for details.
  • 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
  • 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 ... WARNING
    dim:
    function(x)
    dim.def.nc:
    function(ncfile, dimname, dimlength, unlim)

    dim:
    function(x)
    dim.inq.nc:
    function(ncfile, dimension)

    dim:
    function(x)
    dim.rename.nc:
    function(ncfile, dimension, newname)

    See section 'Generic functions and methods' of the 'Writing R Extensions'
    manual.
  • checking replacement functions ... OK
  • checking foreign function calls ... OK
  • checking R code for possible problems ... NOTE
    att.delete.nc: no visible binding for global variable 'ncfile.in'
    att.delete.nc: no visible binding for global variable 'variable.in'
  • checking Rd files ... WARNING
    prepare_Rd: att.copy.nc.Rd:21: Dropping empty section \value
    prepare_Rd: att.delete.nc.Rd:19: Dropping empty section \value
    prepare_Rd: att.inq.nc.Rd:11: unexpected '}'
    prepare_Rd: att.put.nc.Rd:21: Dropping empty section \value
    prepare_Rd: att.rename.nc.Rd:20: Dropping empty section \value
    prepare_Rd: close.nc.Rd:18: Dropping empty section \value
    prepare_Rd: dim.def.nc.Rd:20: Dropping empty section \value
    prepare_Rd: dim.rename.nc.Rd:19: Dropping empty section \value
    prepare_Rd: print.nc.Rd:21: Dropping empty section \value
    prepare_Rd: sync.nc.Rd:17: Dropping empty section \value
    prepare_Rd: utinit.nc.Rd:20: Dropping empty section \value
    prepare_Rd: var.def.nc.Rd:26: Dropping empty section \value
    prepare_Rd: var.put.nc.Rd:30: Dropping empty section \value
    prepare_Rd: var.rename.nc.Rd:19: Dropping empty section \value
  • 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.nc':
    close.nc

    S3 methods shown with full name in documentation object 'dim.def.nc':
    dim.def.nc

    S3 methods shown with full name in documentation object 'dim.inq.nc':
    dim.inq.nc

    S3 methods shown with full name in documentation object 'dim.rename.nc':
    dim.rename.nc

    S3 methods shown with full name in documentation object 'open.nc':
    open.nc

    S3 methods shown with full name in documentation object 'print.nc':
    print.nc

    The \usage entries for S3 methods should use the \method markup and not
    their full name.
    See the chapter 'Writing R documentation files' in manual 'Writing R
    Extensions'.
  • checking Rd contents ... 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 ... OK
  • checking examples ... OK
  • checking PDF version of manual ... OK