hi dirk,
i've got it!
Rst.rhome is assigned here from getenv() (and no copy is made):
https://github.com/eddelbuettel/rinside/blob/d94b999b1f9a5b9a7c1eaefc89abe40ea0d2d4d2/src/RInside.cpp#L164
It makes it's way down inside of R, and is assigned to R_Home:
https://github.com/wch/r-source/blob/
hi dirk,
Might it be that you are shooting the messenger? You see the issue via
RInside as you implemented it via RInside.
But we "merely" give you access to the embedded R instance, and methinks that
the issue may be with ggjoy and/or the pdf() device. Are you really sure RInside
plays any par
hi dirk,
i'm having an issue with grDevices, but the issue only seems to appear
when i using my library with RInside on windows.
one of the packages we use (ggjoy) calls the grDevices::pdf() function,
which tries to load the enc/WinAnsi.enc file from grDevices package.
however, as can be see
hi dirk,
i'm having an issue with grDevices, but the issue only seems to appear
when i using my library with RInside on windows.
one of the packages we use (ggjoy) calls the grDevices::pdf() function,
which tries to load the enc/WinAnsi.enc file from grDevices package.
however, as can be see
hi dirk,
is there a way to gracefully 'interrupt' an analysis run from RInside?
i'll need to send an interrupt from a different thread? (whatever R does
when you hit Ctrl+C)
and can RInside deal from the fallout from that?
with thanks
jonathon
jamovi - stats. open. now.
www.jamovi.org
On 12/02/2016 11:57, Dirk Eddelbuettel wrote:
On 11 February 2016 at 17:42, Dirk Eddelbuettel wrote:
|
| On 11 February 2016 at 15:02, Kevin Ushey wrote:
| | I think this needs to be _WIN32 rather than WIN32. Thanks for pointing this
out!
|
| Could well be. That (IIRC) changed recently so could
hi dirk,
i've been compiling RInside on windows with the new RTools based on GCC
4.9. with stock settings, this all compiles successfully.
however, if i add "-std=c++11" to CXX_FLAGS, then the compilation fails.
it chokes on line 27 of RInside.cpp [1]. what makes this more
interesting is tha
> That sounds more like a genuine bug than something that rears its head only
> on trusty. But without a reproducible example ... there is little to do here.
yeah, i was going to sit down to and write a reproducible example, but
i'm pretty sure it will only reproduce under trusty (i know it doesn
> | > Then I don't care as that is not a current version.
> |
> | an LTS doesn't count? i think it's a *current* version, just not *the
> | latest* version. unfortunately, it represents a chunk of my user base
> | (with the LTS, and the linux mints being based on it)
>
> With all due respect I am
> Then I don't care as that is not a current version.
an LTS doesn't count? i think it's a *current* version, just not *the
latest* version. unfortunately, it represents a chunk of my user base
(with the LTS, and the linux mints being based on it)
> (Which one is trusty again? I only ever use th
> Not really. A minimally reproducible example is always welcome.
what if that minimally reproducible example only happens on ubuntu trusty?
jonathon
--
JASP - A Fresh Way to Do Statistics
http://jasp-stats.org/
--
How happy is he born and taught,
That serveth not another's will;
Whose armo
://launchpad.net/~jonathon-love/+archive/ubuntu/jasp/+packages
any clues?
with thanks
jonathon
On 8/09/2015 4:29 pm, Dirk Eddelbuettel wrote:
>
> On 8 September 2015 at 09:28, Jonathon Love wrote:
> | hi dirk,
> |
> | my application JASP makes use of RInside, and has for about two years
hi dirk,
my application JASP makes use of RInside, and has for about two years
now (https://jasp-stats.org). however, i've just found the most bizare
bug. it only seems to occur under R 3.2.2 (from CRAN) under Ubuntu
Trusty. the issue does not occur under R 3.0.2 (from the standard ubuntu
repos),
awesome. thanks again.
jonathon
> To me it seems that you figured out what you needed for a local build, and we
> are not really in a situation that warrants this for the overall case.
>
> If we thought otherwise would add a configure script -- but adding one makes
> the build longer and slower
hi,
i'm building RInside on debian, and am interested in the hardening
arguments to g++
building RInside results in the following calls:
g++ -I/usr/share/R/include -DNDEBUG -I. -I../inst/include/
-I"/usr/lib/R/site-library/Rcpp/include" -fpic -g -O2
-fstack-protector-strong -Wformat -Wer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
thanks dirk,
i appreciate you taking the time to respond; and this makes things
clearer for me going forward.
cheers
jonathon
> | what is the future of rcpp?
>
> Rcpp is being actively developed by several of us, and we plan on
> adding lots mo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
>> That makes sense, but if you search the list archives (which is
>> generally requested of folks writing to the list) you would
>> notice some context which makes your original questions look a
>> little bit like trolling---having seen previous ex
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
thanks for your response romain,
> If you want to have a private conversation with Dirk, just email
> him directly
sure, but i expect i'm not the only one interested in his response.
> Just use whatever version is best for your needs.
sure, i ge
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
hey dirk,
i was wondering if you could let us know your thoughts about Rcpp11.
i've found it a little bit confusing, because at first i thought people
were just talking about Rcpp (which happens to be at version 0.11). then
i thought it was a newer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
> Almost always an issue related to binary mismatch from components.
ok, ok, you were right again dirk. R was loading libraries from the
user directory, and these were linking back to the system R
installation, and not my curated private installatio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
cheers hadley,
yeah, it's a private R install, and we don't ship the means to install
or update packages. in order for them to change the Rcpp version, they
would need to be opening up the programs directory structure, and
manually copying stuff in,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
hi dirk, thanks for your quick response as always.
> Almost always an issue related to binary mismatch from components.
> Have them recompile.
the application is distributed as a compiled binary (which is known to
work on other machines, including
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
hi all,
it just occurs to me that this is an RInside query rather than Rcpp,
but i still think this is the right place to post (sorry if it isn't!)
OS X 10.9.4
R 3.0.3
Rcpp 0.10.6
RInside 0.2.10
we are shipping a piece of software which embeds R u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
yup, building under a clean VM has solved the problem. thanks for your
help dirk, i have been battling with this one on and off for about 12
months now! feels good to have it sorted!
jonathon
> I surmise that you have your versions mixed up, and p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
thanks for your speedy response dirk!
> | I have an R install which I can link my application against, and
> that | all works fine, but whenever I try and use a new R
> installation, | linking against Rcpp always fails. (I guess I
> fluked it the fi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
I'm just trying to get my head around linking with Rcpp, because I
often have difficulties with this step. I'm developing an application
that embeds R using RInside and Rcpp (shout out to dirk for making these!)
I have an R install which I can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Dirk,
Thanks for your speedy response.
> That sounds suspiciously like something Kevin fixed shortly after
> the release.
>
> Could you try the version in the GitHub repo at
>
> https://github.com/RcppCore/Rcpp
>
> and see if that works?
It
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
We've been using Rcpp in a project for some time now, and have found
it invaluable. However, we've just updated to 0.11 and when we try and
compile our project including the Rcpp header files, we get errors
(seems to work fine under clang++ on O
28 matches
Mail list logo
