• using R version 2.15.0 (2012-03-30)
• using platform: i686-pc-linux-gnu (32-bit)
• using session charset: UTF-8
• checking for file ‘optimbase/DESCRIPTION’ ... OK
• checking extension type ... Package
• this is package ‘optimbase’ version ‘1.0-7’
• 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.
  CRAN requires a NAMESPACE file for all submissions.
• checking for executable files ... OK
• checking whether package ‘optimbase’ 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
  optimbase.checkcostfun: no visible binding for global variable ‘f’
  optimbase.checkcostfun: no visible binding for global variable ‘g’
• 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 sizes of PDF files under ‘inst/doc’ ... OK
• checking installed files from ‘inst/doc’ ... NOTE
  The following files should probably not be installed:
  ‘asserts.tex’, ‘ones.tex’, ‘optimbase-package.tex’,
  ‘optimbase.checkbounds.tex’, ‘optimbase.checkcostfun.tex’,
  ‘optimbase.checkshape.tex’, ‘optimbase.checkx0.tex’,
  ‘optimbase.configure.tex’, ‘optimbase.destroy.tex’,
  ‘optimbase.function.tex’, ‘optimbase.get.tex’,
  ‘optimbase.gridsearch.tex’, ‘optimbase.hasbounds.tex’,
  ‘optimbase.incriter.tex’, ‘optimbase.isfeasible.tex’,
  ‘optimbase.isinbounds.tex’, ‘optimbase.log.tex’, ‘optimbase.new.tex’,
  ‘optimbase.outputcmd.tex’, ‘optimbase.outstruct.tex’,
  ‘optimbase.proj2bnds.tex’, ‘optimbase.terminate.tex’,
  ‘optimtypeof.tex’, ‘size.tex’, ‘strvec.tex’, ‘transpose.tex’,
  ‘vec2matrix.tex’
  
  Consider the use of a .Rinstignore file: see ‘Writing R Extensions’,
  or move the vignette sources from ‘inst/doc’ to ‘vignettes’.
• checking examples ... [2s/2s] OK
• checking for unstated dependencies in vignettes ... OK
• checking package vignettes in ‘inst/doc’ ... OK
• checking running R code from vignettes ... [0s/0s] OK
• checking re-building of vignette PDFs ... [2s/2s] OK
• checking PDF version of manual ... OK
  NOTE: There were 3 notes.
  See
  ‘/home/hornik/tmp/R.check/r-release/Work/PKGS/optimbase.Rcheck/00check.log’
  for details.