----- Original Message ----- > From: "Dirk Eddelbuettel" <e...@debian.org> > To: "Dan Tenenbaum" <dtene...@fhcrc.org> > Cc: "Kevin Ushey" <kevinus...@gmail.com>, > rcpp-devel@lists.r-forge.r-project.org, "Dirk Eddelbuettel" > <e...@debian.org> > Sent: Thursday, February 6, 2014 11:56:47 AM > Subject: Re: [Rcpp-devel] Undefined Reference to typeinfo for Rcpp::RObject > for Rdisop on Mac after Rcpp/RcppClassic > update > > > On 6 February 2014 at 10:49, Dan Tenenbaum wrote: > | The build system was pulling down a binary version of RcppClassic > | but it needs to be built from source. > > *Every* package built against Rcpp needs to be rebuilt this time. > > *Every* one. See the release notes. > > > On 6 February 2014 at 11:28, Dan Tenenbaum wrote: > | Probably RcppCLassic needs a version bump? It was last updated > | 1/26, before the Rcpp update. > > That *was* a pre-release built, but I didn't add (didn't need?) > importFrom(Rcpp, evalCpp). If it needs a fix we'll make a release, > but it has > not yet been determined that it needs fix. > > But *every* reverse dependency of Rcpp does not a rebuild this time. > We're sorry for the inconvenience but we were also very clear and > upfront > about it. >
If every reverse dependency of Rcpp needs a rebuild, and that includes RcppClassic, does it not follow that RcppClassic needs a rebuild on CRAN? Otherwise Mac or windows users without compilers are out of luck. Dan > Dirk > > -- > Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com > _______________________________________________ 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