BayesPeak 1.14.0
Jonathan Cairns
| Snapshot Date: 2014-04-04 16:20:29 -0700 (Fri, 04 Apr 2014) | | URL: https://hedgehog.fhcrc.org/bioconductor/branches/RELEASE_2_13/madman/Rpacks/BayesPeak | | Last Changed Rev: 81642 / Revision: 88450 | | Last Changed Date: 2013-10-14 14:29:21 -0700 (Mon, 14 Oct 2013) |
| zin1 | Linux (Ubuntu 12.04.4 LTS) / x86_64 | OK | OK | |
| moscato1 | Windows Server 2008 R2 Enterprise SP1 (64-bit) / x64 | OK | OK | OK |
| perceval | Mac OS X Snow Leopard (10.6.8) / x86_64 | OK | [ OK ] | OK |
* using log directory ‘/Users/biocbuild/bbs-2.13-bioc/meat/BayesPeak.Rcheck’
* using R version 3.0.3 (2014-03-06)
* using platform: x86_64-apple-darwin10.8.0 (64-bit)
* using session charset: UTF-8
* using option ‘--no-vignettes’
* checking for file ‘BayesPeak/DESCRIPTION’ ... OK
* this is package ‘BayesPeak’ version ‘1.14.0’
* checking package namespace information ... OK
* checking package dependencies ... OK
* checking if this is a source package ... OK
* checking if there is a namespace ... OK
* checking for hidden files and directories ... OK
* checking for portable file names ... OK
* checking for sufficient/correct file permissions ... OK
* checking whether package ‘BayesPeak’ can be installed ... [10s/12s] OK
* checking installed package size ... NOTE
installed size is 6.7Mb
sub-directories of 1Mb or more:
data 1.0Mb
extdata 5.0Mb
* checking package directory ... OK
* checking ‘build’ directory ... OK
* checking DESCRIPTION meta-information ... NOTE
Package listed in more than one of Depends, Imports, Suggests, Enhances:
‘IRanges’
A package should be listed in only one of these fields.
* checking top-level files ... OK
* checking for left-over 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 whether the namespace can be loaded with stated dependencies ... OK
* checking whether the namespace can be unloaded cleanly ... OK
* checking 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 ... NOTE
S3 methods shown with full name in documentation object 'overfittingDiagnostics':
‘plot.overfitdiag’ ‘identify.overfitdiag’
S3 methods shown with full name in documentation object 'plot.PP':
‘plot.PP’
S3 methods shown with full name in documentation object 'plot.bed':
‘plot.bed’
S3 methods shown with full name in documentation object 'plot.job':
‘plot.job’
The \usage entries for S3 methods should use the \method markup and not
their full name.
See the chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.
* 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 ‘/Users/biocbuild/bbs-2.13-bioc/meat/BayesPeak.Rcheck/BayesPeak/libs/BayesPeak.so’:
Found ‘___stdoutp’, possibly from ‘stdout’ (C)
Object: ‘bayespeak.o’
Compiled code should not call entry points 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 sizes of PDF files under ‘inst/doc’ ... OK
* checking installed files from ‘inst/doc’ ... OK
* checking for old-style vignette sources ... NOTE
Vignette sources only in ‘inst/doc’:
‘BayesPeak.Rnw’
A ‘vignettes’ directory will be required as from R 3.1.0
* checking examples ... [264s/272s] OK
Examples with CPU or elapsed time > 5s
user system elapsed
bayespeak 126.512 0.561 129.323
summarise.peaks 120.807 0.621 127.104
plot.job 7.278 0.210 7.620
* checking for unstated dependencies in vignettes ... OK
* checking package vignettes in ‘inst/doc’ ... OK
* checking running R code from vignettes ... SKIPPED
* checking re-building of vignette outputs ... SKIPPED
* checking PDF version of manual ... OK
NOTE: There were 5 notes.
See
‘/Users/biocbuild/bbs-2.13-bioc/meat/BayesPeak.Rcheck/00check.log’
for details.
* installing *source* package ‘BayesPeak’ ...
** libs
llvm-gcc-4.2 -arch x86_64 -std=gnu99 -I/Library/Frameworks/R.framework/Resources/include -DNDEBUG -I/usr/local/include -fPIC -mtune=core2 -g -O2 -Wall -c bayespeak.c -o bayespeak.o
llvm-gcc-4.2 -arch x86_64 -std=gnu99 -dynamiclib -Wl,-headerpad_max_install_names -undefined dynamic_lookup -single_module -multiply_defined suppress -L/usr/local/lib -L/usr/local/lib -o BayesPeak.so bayespeak.o -F/Library/Frameworks/R.framework/.. -framework R -Wl,-framework -Wl,CoreFoundation
installing to /Users/biocbuild/bbs-2.13-bioc/meat/BayesPeak.Rcheck/BayesPeak/libs
** R
** data
** inst
** preparing package for lazy loading
** help
*** installing help indices
** building package indices
** installing vignettes
** testing if installed package can be loaded
* DONE (BayesPeak)