• using R version 2.15.0 (2012-03-30)
• using platform: x86_64-pc-mingw32 (64-bit)
• using session charset: ISO8859-1
• checking for file 'polspline/DESCRIPTION' ... OK
• this is package 'polspline' version '1.1.5'
• 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 whether package 'polspline' can be installed ... OK
• checking installed package size ... 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
• loading checks for arch 'i386'
  ** 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
• loading checks for arch 'x64'
  ** 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 ... 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 ... 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 compilation flags in Makevars ... OK
• checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK
• checking compiled code ... NOTE
  File 'd:/Rcompile/CRANpkg/lib/2.15/polspline/libs/i386/polspline.dll':
  Found 'exit', possibly from 'exit' (C), 'stop' (Fortran)
  Objects: 'hareall.o', 'heftall.o', 'lspecall.o'
  File 'd:/Rcompile/CRANpkg/lib/2.15/polspline/libs/x64/polspline.dll':
  Found 'exit', possibly from 'exit' (C), 'stop' (Fortran)
  Objects: 'hareall.o', 'heftall.o', 'lspecall.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 ...
  ** running examples for arch 'i386' ... OK
  ** running examples for arch 'x64' ... OK
• checking PDF version of manual ... OK
  NOTE: There were 2 notes.
  See
  'd:/Rcompile/CRANpkg/local/2.15/polspline.Rcheck/00check.log'
  for details.