• using R version 2.10.0 alpha (2009-10-01 r49916)
  • using session charset: ASCII
  • checking for file 'geometry/DESCRIPTION' ... OK
  • this is package 'geometry' version '0.1-4'
  • checking package name space information ... OK
  • checking package dependencies ... OK
  • checking if this is a source package ... OK
  • checking for executable files ... OK
  • checking whether package 'geometry' can be installed ... WARNING
    Found the following significant warnings:
    Warning: bad markup (extra space?) at entry.value.Rd:19:15
    See http://www.r-project.org/nosvn/R.check/r-release-macosx-ix86/geometry-00install.html for details.
  • 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 name space can be loaded with stated dependencies ... 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 ... WARNING
    prepare_Rd: bad markup (extra space?) at entry.value.Rd:19:15
  • checking Rd metadata ... OK
  • checking Rd cross-references ... WARNING
    Suspect link(s) in documentation object './man/tetramesh.Rd':
    '[rgl]{rgl}'

    See the information in section 'Cross-references' of the 'Writing R
    Extensions' manual.

    'Suspect' links are those of the form \link[pkg]{a} where 'a' exists as
    an alias but not as a filename -- such links will not work in R <
    2.10.0, and only in HTML (not PDF) help in current versions.
  • checking for missing documentation entries ... OK
  • checking for code/documentation mismatches ... OK
  • checking Rd \usage sections ... 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 ... OK
  • checking examples ... OK
  • checking PDF version of manual ... OK
  • elapsed time (check, wall clock): 0:33