Hi Guys,
I am getting this strange error:
g++ -m64 -shared -s -static-libgcc -o cme.dll tmp.def RcppExports.o cme.o
misc.o pb.o C:/Users/Kevin/R/win-library/3.1/RcppMLPACK/lib/x64/libRcppMLPACK.a
-LC:/R/R-31~1.1/bin/x64 -lRlapack -LC:/R/R-31~1.1/bin/x64 -lRblas -lgfortran
-Ld:/RCompile/CRA
- Original Message -
> From: "Dirk Eddelbuettel"
> To: "Dan Tenenbaum"
> Cc: "Dirk Eddelbuettel" , "Kevin Ushey"
> ,
> rcpp-devel@lists.r-forge.r-project.org
> Sent: Thursday, February 6, 2014 7:06:26 PM
> Subject: Re: [
Hi,
On Thu, 2014-02-06 at 10:49 -0800, Dan Tenenbaum wrote:
...
> The build system was pulling down a binary version of RcppClassic but it
> needs to be built from source.
Thanks Dan for fixing this.
On Thu, 2014-02-06 at 11:28 -0800, Dan Tenenbaum wrote:
...
> Probably RcppCLassic needs a versi
On 6 February 2014 at 12:01, Dan Tenenbaum wrote:
| 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.
It has always been my understand
- Original Message -
> From: "Dirk Eddelbuettel"
> To: "Dan Tenenbaum"
> Cc: "Kevin Ushey" ,
> rcpp-devel@lists.r-forge.r-project.org, "Dirk Eddelbuettel"
>
> Sent: Thursday, February 6, 2014 11:56:47 AM
> Subject: Re: [
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 T
- Original Message -
> From: "Dan Tenenbaum"
> To: "Kevin Ushey"
> Cc: rcpp-devel@lists.r-forge.r-project.org
> Sent: Thursday, February 6, 2014 10:49:29 AM
> Subject: Re: [Rcpp-devel] Undefined Reference to typeinfo for Rcpp::RObject
> fo
- Original Message -
> From: "Kevin Ushey"
> To: "Dirk Eddelbuettel"
> Cc: rcpp-devel@lists.r-forge.r-project.org
> Sent: Thursday, February 6, 2014 10:43:25 AM
> Subject: Re: [Rcpp-devel] Undefined Reference to typeinfo for Rcpp::RObject
> fo
I wonder if the 'typeid' error could be a red herring and the real
cause could be somehow related to virtual functions. If the compiler
didn't know what 'typeid' meant (ie, had no RTTI) it would have failed
on compilation, not linking, no? E.g.:
http://stackoverflow.com/questions/307352/g-undefined
Apparently this is moot now, because it looks like Rdisop now builds
successfully on BioC for all systems:
http://bioconductor.org/checkResults/2.14/bioc-LATEST/Rdisop/petty-buildsrc.html,
http://bioconductor.org/checkResults/2.13/bioc-LATEST/Rdisop/perceval-buildsrc.html.
Did you have to change s
On 6 February 2014 at 15:15, Steffen Neumann wrote:
| Hi,
|
| On Thu, 2014-02-06 at 07:54 -0600, Dirk Eddelbuettel wrote:
| ...
| > Weird. If it is on the Mac, is that with g++-4.2 or with clang ?
| ...
| > | and llvm-g++-4.2 compiler.
|
| I don't know the terminology in llvm land,
| the BioC s
Hi,
On Thu, 2014-02-06 at 07:54 -0600, Dirk Eddelbuettel wrote:
...
> Weird. If it is on the Mac, is that with g++-4.2 or with clang ?
...
> | and llvm-g++-4.2 compiler.
I don't know the terminology in llvm land,
the BioC system information page says "llvm-g++-4.2",
and there is more about the b
On 6 February 2014 at 13:05, Steffen Neumann wrote:
| Hi list,
|
| I am having issues to build Rdisop on Mac (to which I have no access)
| after the upgrade to Rcpp 0.11.0 / RcppClassic 0.9.5, on both
|
|
http://bioconductor.org/checkResults/2.13/bioc-LATEST/Rdisop/perceval-buildsrc.html
|
ht
Hi list,
I am having issues to build Rdisop on Mac (to which I have no access)
after the upgrade to Rcpp 0.11.0 / RcppClassic 0.9.5, on both
http://bioconductor.org/checkResults/2.13/bioc-LATEST/Rdisop/perceval-buildsrc.html
http://bioconductor.org/checkResults/2.14/bioc-LATEST/Rdisop/petty-buil
14 matches
Mail list logo