Search Archives

Note that the Sys.setenv technique described by Dirk will work for Rcpp from SVN but not (yet) for the version of Rcpp on CRAN. JJ

This most likely means you don't have Rtools installed. If that's not the problem try passing showOutput=TRUE to get more diagnostics. JJ

Fixed in rev 4273 -- thanks for the detailed and reproducible bug report! J.J. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.r-forge.r-project.org/pipermail/rcpp-devel/attachments/20130227/4853a984/attachment.html>

Walter, Are you running Terminal, R GUI, or RStudio? (there might be a difference in the way dynamic libraries are located in each which could cause this). Also, what's the value of the environment variable DYLD_LIBRARY_PATH? Thanks...

To run RStudio as root on Ubuntu you would just do: sudo rstudio The packages in /usr/lib/R/library are the ones that came with the base install of R. J.J. Allaire -- View this message in context: http...

> What would make clang _not_ get used for both phases? My Makevars shows > > CC="clang" > CXX="clang++" > CPP="clang-cpp" All we do is call R CMD SHLIB (we don't explicitly invoke the compiler or linker) so I think...

> > This would still bypass the dror for the RNGscope object automatically added by Rcpp::export right ? > Indeed it would. I think Dirk's example is really just an illustration of how we handle exceptions internally via the BEGIN/END macros...

Hi Ivan, We are in the process of creating an R mode for highlight.js -- will send you a pull request as soon as its ready. Cheers, J.J. Allaire jj at rstudio.org -- View this message in context: http...

> > The name of the macro should in my view giev an idea that this is meant > for vectors, e.g. DISPATCH_VECTOR_METHOD or something > +1 I was actually asking whether we should include your RcppScript as an extra utility...

On Thu, Apr 30, 2015 at 6:09 AM, Sean O'Riordain <seoriord at tcd.ie> wrote: > I am curious about the phrase "distribute internally" - surely under GPL, > that is still distribution and all modifications should thus be made public...

On Thu, Jun 5, 2014 at 6:05 AM, Gabor Grothendieck <ggrothendieck at gmail.com> wrote: > I am using "R version 3.1.0 Patched (2014-05-09 r65562)" but its > working now so perhaps you changed more than described...

> > But maybe it is not worth the trouble. Maybe this is simply a > documentation issue on hiw to dispatch. > Yes, I think creating an automatic dispatch system that's general enough to matter might not be worth the effort. Documentation...

> I am happy to share my experience with Solaris. I have been meaning to > write a step-by-step guide to setting up a Solaris testing platform for > R on a VirtualBox VM, so this gives me some impetus to...

> Maybe you could follow the example of Rcpp.package.skeleton() and just drop > an empty yet amply commented file there? By "being there" users have a > better chance of stumbling over it :) > Since this would involve creating a new directory...

> > Actually, I already looked at the code in rmarkdown and tried exactly this. On my Mac under R.app, where the default path is > >> Sys.getenv("PATH") > [1] "/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin" > > I get > >> rmarkdown...

> > Am I correct in noting that > > // [[Rcpp::export]] > void test(void) > { > // do something > } > > does not generate any code in RcppExports.R? > The problem occurs because the attributes parser doesn't know what to do with the void argument specification. If...

> > dispatching could also happen in attributes. Why not having something like > this: > > // [[Rcpp::export]] > void foo( NumericVector x) { > // do some stuff > } > > // [[Rcpp::export]] > void foo( IntegerVector x) { > // do some other stuff > } > > This would involve some work in the way attributes...

On Sun, Jun 14, 2015 at 3:46 PM, Alex Chubaty <alex.chubaty at gmail.com> wrote: > JJ, do you have an estimated timeframe for when this fix will appear? > There's still the issue of RStudio users not updating...

> > The constructor of Vector based in iterator takes care of the business. So > you don't need to write a dispatch. > > I like the idea of DISPATCH_METHOD, we would need extras at least for > RAWSXP, CPLXSXP and VECSXP . > This...

The error appears to be occurring in the call to RcppLdPath (made by both sourceCpp and RStan). Here's the source code for that function: RcppLdPath <- function() { if (nzchar(.Platform$r_arch)) { ## eg amd64, ia64, mips path <- Rcpp.system.file...