I would like to compile .cpp code based on RcppEigen using R CMD SHLIB.
To test this I have created a "sample" package using:
RcppEigen.package.skeleton( "foobar" )
In the src directory of foobar there is a sample .cpp file which I try to
compile with (I am on Windows 7)
C:\Documents\stat\Rde
On 6/27/12 7:07 AM, Douglas Bates wrote:
On Tue, Jun 26, 2012 at 7:04 PM, Dirk Eddelbuettel wrote:
On 26 June 2012 at 17:21, Jiqiang Guo wrote:
| Dear List,
|
| I am wondering if there is a way to check whether an object created from
Rcpp's
| module is valid or not especially for objects load
On 27 June 2012 at 15:29, ml.lattu...@libero.it wrote:
| Hi,
|
| since last update of Rcpp I have got a segmentation fault in a program that
| uses Rcpp and RInside.
| The backtrace is the following
|
| Program received signal SIGSEGV, Segmentation fault.
| 0x7fffd6ba9df0 in Rf_isEnvironme
On Tue, Jun 26, 2012 at 7:04 PM, Dirk Eddelbuettel wrote:
>
> On 26 June 2012 at 17:21, Jiqiang Guo wrote:
> | Dear List,
> |
> | I am wondering if there is a way to check whether an object created from
> Rcpp's
> | module is valid or not especially for objects loaded in another session.
> |
> |
Hi,
since last update of Rcpp I have got a segmentation fault in a program that
uses Rcpp and RInside.
The backtrace is the following
Program received signal SIGSEGV, Segmentation fault.
0x7fffd6ba9df0 in Rf_isEnvironment () from /usr/lib/libR.so
(gdb) backtrace
#0 0x7fffd6ba9df0 in Rf
On 26 June 2012 21:42, Davor Cubranic wrote:
> Doesn't Rcpp 2.11 require 2.15.1, and the computers on which you had problems
> had 2.15?
>
> Also, you don't say if you tried rebuilding your package, or if you just
> continued using the same binary. It is possible that since Rcpp API changed,
>
