* using log directory 'd:/Rcompile/CRANpkg/local/2.10/PhySim.Rcheck'
* using R version 2.10.0 RC (2009-10-20 r50178)
* using session charset: ISO8859-1
* checking for file 'PhySim/DESCRIPTION' ... OK
* this is package 'PhySim' version '1.0'
* checking package dependencies ... OK
* checking if this is a source package ... OK
* checking whether package 'PhySim' can be installed ... WARNING
Found the following significant warnings:
  Warning: ./man/branchingPhySim.times.Rd:10: unexpected '}'
  Warning: ./man/dropPhySim.tip.Rd:10: unexpected '}'
  Warning: ./man/writePhySim.tree.Rd:51: unexpected '}'
See 'd:/Rcompile/CRANpkg/local/2.10/PhySim.Rcheck/00install.out' for details.
* checking package directory ... OK
* checking for portable file names ... WARNING
Found the following file(s) with non-portable file names:
  functions details.txt
These are not fully portable file names
See section 'Package structure' in manual 'Writing R Extensions'.
* 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 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
dropPhySim.tip: no visible global function definition for 'write.tree'
dropPhySim.tip: no visible global function definition for 'clado.build'
dropPhySim.tip: no visible global function definition for 'tree.build'
readPhySim.tree: no visible global function definition for
  'clado.build'
* checking Rd files ... WARNING
prepare_Rd: branchingPhySim.times.Rd:10: unexpected '}'
prepare_Rd: dropPhySim.tip.Rd:10: unexpected '}'
prepare_Rd: writePhySim.tree.Rd:51: unexpected '}'
* 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 examples ... OK
* checking PDF version of manual ... OK