* using log directory 'd:/Rcompile/CRANpkg/local/2.15/bipartite.Rcheck'
* 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 'bipartite/DESCRIPTION' ... OK
* checking extension type ... Package
* this is package 'bipartite' version '1.17'
* 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 'bipartite' 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 ... NOTE
File 'bipartite/R/zzz.R':
  .First.lib calls:
    cat(paste("----------------------------------------------------------\nThis is bipartite",     vers, "\nFor latest additions type: ?bipartite.\nFor citation please type: citation(\"bipartite\").\nHave a nice time plotting and analysing two-mode networks.\n----------------------------------------------------------\n\n"))

Package startup functions should use 'packageStartupMessage' to
  generate messages.
See section 'Good practice' in ?.onAttach.

* checking Rd files ... NOTE
prepare_Rd: barrett1987.Rd:18-19: Dropping empty section \format
prepare_Rd: bezerra2009.Rd:26-27: Dropping empty section \format
prepare_Rd: computeModules.Rd:36: Dropping empty section \details
prepare_Rd: computeModules.Rd:46: Dropping empty section \note
prepare_Rd: listModuleInformation.Rd:19: Dropping empty section \details
prepare_Rd: listModuleInformation.Rd:32: Dropping empty section \note
prepare_Rd: listModuleInformation.Rd:28: Dropping empty section \references
prepare_Rd: listModuleInformation.Rd:34: Dropping empty section \seealso
prepare_Rd: memmott1999.Rd:9-10: Dropping empty section \format
prepare_Rd: moduleWeb-class.Rd:36: Dropping empty section \note
prepare_Rd: moduleWeb-class.Rd:34: Dropping empty section \references
prepare_Rd: moduleWeb-class.Rd:37: Dropping empty section \seealso
prepare_Rd: plotModuleWeb.Rd:64: Dropping empty section \details
prepare_Rd: plotModuleWeb.Rd:74: Dropping empty section \note
prepare_Rd: plotModuleWeb.Rd:70: Dropping empty section \references
prepare_Rd: printoutModuleInformation.Rd:24: Dropping empty section \details
prepare_Rd: printoutModuleInformation.Rd:32: Dropping empty section \note
prepare_Rd: printoutModuleInformation.Rd:28: Dropping empty section \references
prepare_Rd: printoutModuleInformation.Rd:34: Dropping empty section \seealso
prepare_Rd: sortweb.Rd:27-28: Dropping empty section \details
prepare_Rd: togetherness.Rd:21-23: Dropping empty section \details
prepare_Rd: visweb.Rd:61-62: Dropping empty section \details
prepare_Rd: PAC.rd:44-45: Dropping empty section \seealso
prepare_Rd: plotweb2.rd:58-59: Dropping empty section \references
prepare_Rd: plotweb2.rd:63-65: Dropping empty section \examples
* 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 'd:/Rcompile/CRANpkg/lib/2.15/bipartite/libs/i386/bipartite.dll':
  Found '_ZSt4cout', possibly from 'std::cout' (C++)
    Object: 'identifyModules.o'
  Found 'exit', possibly from 'exit' (C), 'stop' (Fortran)
    Object: 'bmn5.o'
File 'd:/Rcompile/CRANpkg/lib/2.15/bipartite/libs/x64/bipartite.dll':
  Found '_ZSt4cout', possibly from 'std::cout' (C++)
    Object: 'identifyModules.o'
  Found 'exit', possibly from 'exit' (C), 'stop' (Fortran)
    Object: 'bmn5.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 sizes of PDF files under 'inst/doc' ... OK
* checking installed files from 'inst/doc' ... OK
* checking examples ...
** running examples for arch 'i386' ... OK
** running examples for arch 'x64' ... OK
* checking PDF version of manual ... OK
NOTE: There were 4 notes.
See
  'd:/Rcompile/CRANpkg/local/2.15/bipartite.Rcheck/00check.log'
for details.