* using log directory 'd:/Rcompile/CRANpkg/local/3.0/RWinEdt.Rcheck' * using R version 3.0.3 (2014-03-06) * using platform: x86_64-w64-mingw32 (64-bit) * using session charset: ISO8859-1 * using option '--install=fake' * checking for file 'RWinEdt/DESCRIPTION' ... OK * this is package 'RWinEdt' version '2.0-2' * 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 hidden files and directories ... OK * checking for portable file names ... OK * checking whether package 'RWinEdt' can be installed ... OK * checking installed package size ... OK * checking package directory ... OK * checking DESCRIPTION meta-information ... OK * checking top-level files ... OK * checking for left-over 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 loading without being on the library search path ... OK * checking 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 'RWinEdt/R/zzz.R': .onAttach calls: message(" You are running R in MDI mode which is *not*\n", " supported for non-english translations of RGui.\n", " It is recommended to use R in SDI mode which can be\n", " set in the command line or by clicking in the Menu:\n", " Edit - GUI Preferences: SDI, then Save and restart R.") writeLines(edtFile, con = send2RedtLoc) writeLines(edtFile, con = send2RedtLoc) 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 ... OK * 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 sizes of PDF files under 'inst/doc' ... OK * checking files in 'vignettes' ... OK * checking examples ... SKIPPED * checking package vignettes in 'inst/doc' ... OK * checking running R code from vignettes ... SKIPPED * checking re-building of vignette outputs ... SKIPPED * checking PDF version of manual ... OK NOTE: There was 1 note. * using check arguments '--install=fake'