This may already be common knowledge (apologies if it is), but a quick scan of the (recent) email exchanges did not suggest so, and I have come across a number of partial questions and answers on this same topic.
I have been struggling with an annoying lambda/template bug in gcc 4.6.3 : https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53741 so decided to try to update the gcc that is packaged with Rtools to 4.8.1. This may assist with Windows users "internal Rcpp projects" - I appreciate package authoring/distribution and CRAN upload concern are more "delicate". I did not initially post to Rcpp-devel, as Rtools is a R-devel concern. But in case anyone may find this useful for their Rcpp efforts, here is my post with the method I used: http://stackoverflow.com/questions/25455829/using-a-different-gcc-version-from-that-included-with-rtools-with-rcpp-on-window/25456836#25456836 [http://cdn.sstatic.net/stackoverflow/img/apple-touch-i...@2.png?v=fde65a5a78c6]<http://stackoverflow.com/questions/25455829/using-a-different-gcc-version-from-that-included-with-rtools-with-rcpp-on-window/25456836#25456836> c++ - Using a different gcc version from that included with Rtools with Rcpp on Windows - Stack Overflow Before I embark on updating gcc, has anyone actually attempted this, and can they confirm building R from source is required to update the gcc version one uses to compile c++ code with Rcpp (i.e. not Read more...<http://stackoverflow.com/questions/25455829/using-a-different-gcc-version-from-that-included-with-rtools-with-rcpp-on-window/25456836#25456836>
_______________________________________________ Rcpp-devel mailing list Rcpp-devel@lists.r-forge.r-project.org https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
