• using R Under development (unstable) (2012-08-11 r60235)
• using platform: x86_64-unknown-linux-gnu (64-bit)
• using session charset: UTF-8
• checking for file ‘mixer/DESCRIPTION’ ... OK
• checking extension type ... Package
• this is package ‘mixer’ version ‘1.5’
• package encoding: UTF-8
• 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 executable files ... OK
• checking for hidden files and directories ... OK
• checking whether package ‘mixer’ can be installed ... OK
• checking installed package size ... OK
• 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 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 loading without being on the library search path ... 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 ‘mixer/R/init.R’:
  .onLoad calls:
  cat("\n")
  cat(" 'mixer' package\n")
  cat(" SSB group (http://ssbgroup.fr)\n")
  cat(" mixer page (http://ssbgroup.fr/mixnet/mixer.html)\n")
  cat("\n")
  
  Package startup functions should use ‘packageStartupMessage’ to
  generate messages.
  See section ‘Good practice’ in ?.onAttach.
  
• 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 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 compilation flags in Makevars ... OK
• checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK
• checking compiled code ... WARNING
  File ‘/home/hornik/tmp/R.check/r-devel/Work/build/Packages/mixer/libs/mixer.so’:
  Found ‘_ZSt4cerr’, possibly from ‘std::cerr’ (C++)
  Objects: ‘Ermg.o’, ‘Graph.o’, ‘ModelImprover.o’
  Found ‘_ZSt4cout’, possibly from ‘std::cout’ (C++)
  Objects: ‘ModelDesigner.o’, ‘ModelImprover.o’, ‘matrix.o’
  Found ‘_gfortran_st_write’, possibly from ‘write’ (Fortran), ‘print’
  (Fortran)
  Objects: ‘dlamch.o’, ‘dmout.o’, ‘dnaupd.o’, ‘dvout.o’, ‘ivout.o’,
  ‘xerbla.o’
  Found ‘_gfortran_stop_string’, possibly from ‘stop’ (Fortran)
  Object: ‘xerbla.o’
  Found ‘exit’, possibly from ‘exit’ (C)
  Objects: ‘Ermg.o’, ‘Graph.o’, ‘ermg_R.o’, ‘ermgo_R.o’,
  ‘init_ermg_R.o’
  Found ‘printf’, possibly from ‘printf’ (C)
  Objects: ‘ermg_R.o’, ‘ermgo_R.o’, ‘init_ermg_R.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 ... [10s/10s] OK
• checking PDF version of manual ... OK
  WARNING: There was 1 warning.
  NOTE: There was 1 note.
  See
  ‘/home/hornik/tmp/R.check/r-devel/Work/PKGS/mixer.Rcheck/00check.log’
  for details.