[Rcpp-devel] Making R package with Rcpp Issue: Found '_ZSt4cout'

[Dirk Eddelbuettel]

On 24 August 2015 at 10:19, Daniel McCarthy wrote:
| 
| I am attempting to push a package to CRAN but am having the following issue
| with the CRAN checks:
| 
| * using R version 3.1.3 (2015-03-09)
| * using platform: x86_64-w64-mingw32 (64-bit)
| ....
| * checking compiled code ... NOTE
| File 'perccal/libs/i386/perccal.dll':
|   Found '_ZSt4cout', possibly from 'std::cout' (C++)
|     Object: 'dboot_multi.o'
| File 'perccal/libs/x64/perccal.dll':
|   Found '_ZSt4cout', possibly from 'std::cout' (C++)
|     Object: 'dboot_multi.o'

See "Writing R Extensions"; this is not a Rcpp issue (though Rcpp offers you
the Rcpp::Rcout "device" to send output to in order to have it synced with
the R standard output).

| This post referenced a similar issue: http://comments.gmane.org/
| gmane.comp.lang.r.rcpp/3071
| 
| A Google search seems to indicate many packages have similar notes:https://
| www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=Found+
| '_ZSt4cout'+note+package
| 
| For example, bayes-tree: http://www2.uaem.mx/r-mirror/bin/windows/contrib/3.1/
| check/BayesTree-check.log
| 
| This is the only note remaining -- everything else went through without issue
| and '_ZSt4cout' was not part of any code that I had written. I am importing
| Rcpp and RcppArmadillo for 2 functions used in the package. I am stumped, but

By default we take care of this:

  // Rcpp has its own stream object which cooperates more nicely with R's i/o
  // And as of Armadillo 2.4.3, we can use this stream object as well 
  #if !defined(ARMA_DEFAULT_OSTREAM)
  #define ARMA_DEFAULT_OSTREAM Rcpp::Rcout
  #endif

Maybe you accidentally undefined this...

| assume that I would not be allowed to push a package to CRAN which has this
| note. Any help would be most appreciated!

The message is rather explicit, something in the object code dboot_multi.o
refers to std::cout.   You need to clean that up.

(I think some folks have some clever macros in their headers to automate
this.  I have in the past resorted to explicitly alterting code, or to macro
use to switch to our Rcout as above.)

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org