• using R version 2.14.0 (2011-10-31)
  • using platform: i386-apple-darwin9.8.0 (32-bit)
  • using session charset: ASCII
  • using option '--install=fake'
  • checking for file 'JGR/DESCRIPTION' ... OK
  • this is package 'JGR' version '1.7-9'
  • 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 'JGR' 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 'JGR/R/JGR.R':
    .First.lib calls:
    library(utils)
    library(rJava)
    cat("\nPlease type JGR() to download/launch console. Launchers can also be obtained at http://www.rforge.net/JGR/files/.\n\n")
    cat("\n\n *** WARNING *** Your R contains old GOMP library which does NOT work with other threads!\n This will lead to random crashes in R!\n Please update R to the latest patched version from http://R.research.att.com/\n\n")

    Package startup functions should not change the search path.
    Package startup functions should use 'packageStartupMessage' to
    generate messages.
    See section 'Good practice' in ?.onAttach.

    .generate.run.script: no visible binding for global variable
    '.jgr.pkg.path'
    .refresh: no visible binding for global variable '.jgr.works'
    installPackages: no visible binding for global variable '.jgr.works'
    JGR: no visible binding for global variable '.jgr.works'
    JGR: no visible binding for global variable '.jgr.pkg.path'
    jgr.addMenu: no visible binding for global variable '.jgr.works'
    jgr.addMenuItem: no visible binding for global variable '.jgr.works'
    jgr.addMenuSeparator: no visible binding for global variable
    '.jgr.works'
    jgr.addSubMenu: no visible binding for global variable '.jgr.works'
    jgr.browser: no visible binding for global variable '.jgr.works'
    jgr.getMenuItemNames: no visible binding for global variable
    '.jgr.works'
    jgr.getMenuNames: no visible binding for global variable '.jgr.works'
    jgr.insertMenu: no visible binding for global variable '.jgr.works'
    jgr.insertMenuItem: no visible binding for global variable '.jgr.works'
    jgr.insertMenuSeparator: no visible binding for global variable
    '.jgr.works'
    jgr.insertSubMenu: no visible binding for global variable '.jgr.works'
    jgr.pager: no visible binding for global variable '.jgr.works'
    jgr.removeMenu: no visible binding for global variable '.jgr.works'
    jgr.removeMenuItem: no visible binding for global variable '.jgr.works'
    jgr.set.options: no visible binding for global variable '.jgr.works'
    object.browser: no visible binding for global variable '.jgr.works'
    package.manager: no visible binding for global variable '.jgr.works'
  • 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 'jgr.supplements':
    'print.hsearch'

    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 examples ... SKIPPED
  • checking PDF version of manual ... OK
  • using check arguments '--install=fake'
  • elapsed time (check, wall clock): 0:29