• using R version 2.15.0 Patched (2012-03-31 r58888)
• using platform: sparc-sun-solaris2.10 (32-bit)
• using session charset: UTF-8
• checking for file ‘svmpath/DESCRIPTION’ ... OK
• this is package ‘svmpath’ version ‘0.952’
• 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 .dll and .exe files ... OK
• checking whether package ‘svmpath’ 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
  SnapPath: warning in jpeg(file = paste(movie.root, step, ".jpg", sep =
  ""), quality = 90, width = 540, height = 540, bg = "wheat", ...):
  partial argument match of 'file' to 'filename'
• 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 contents of ‘data’ directory ... OK
• checking data for non-ASCII characters ... OK
• checking data for ASCII and uncompressed saves ... 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 ... NOTE
  File ‘/home/ripley/R/Lib32/svmpath/libs/svmpath.so’:
  Found ‘__f90_esfw’, possibly from ‘print’ (Fortran), ‘write’
  (Fortran)
  Objects: ‘mi02lib.o’, ‘mi05funs.o’, ‘mi10unix.o’, ‘mi11sys.o’,
  ‘mi12solv.o’, ‘mi20amat.o’, ‘mi25bfac.o’, ‘mi26bfac.o’,
  ‘mi27lu.o’, ‘mi30spec.o’, ‘mi35mps.o’, ‘mi36mps.o’, ‘mi40bfil.o’,
  ‘mi50lp.o’, ‘mi60srch.o’, ‘mi65rmod.o’, ‘mi70nobj.o’,
  ‘mi80ncon.o’, ‘mi81ncon.o’
  
  Compiled code should not call functions which might terminate R nor
  write to stdout/stderr instead of to the console.
  
  See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual.
• checking examples ... OK
• checking PDF version of manual ... OK
  NOTE: There were 3 notes.
  See
  ‘/home/ripley/R/packages/tests32/svmpath.Rcheck/00check.log’
  for details.