* using log directory 'd:/Rcompile/CRANpkg/local/2.10/ncdf.Rcheck' * using R version 2.10.1 (2009-12-14) * using session charset: ISO8859-1 * checking for file 'ncdf/DESCRIPTION' ... OK * this is package 'ncdf' version '1.6.3' * checking package dependencies ... OK * checking if this is a source package ... OK * checking whether package 'ncdf' can be installed ... 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 * checking whether the package can be loaded ... OK * checking whether the package can be loaded with stated dependencies ... OK * checking for unstated dependencies in R code ... OK * checking S3 generic/method consistency ... WARNING dim: function(x) dim.create.ncdf: function(nc, d, verbose) dim: function(x) dim.def.ncdf: function(name, units, vals, unlim, create_dimvar) dim: function(x) dim.inq.ncdf: function(nc, dimid) dim: function(x) dim.same.ncdf: function(d1, d2) 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 ... OK * 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 'close.ncdf': close.ncdf S3 methods shown with full name in documentation object 'dim.def.ncdf': dim.def.ncdf S3 methods shown with full name in documentation object 'open.ncdf': open.ncdf 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 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