-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,
>> 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 fresh OS installs), so i don't think
> it can be that; they don't compile anything.
This may
-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
On 22 August 2014 at 11:45, Jonathon Love wrote:
| we are shipping a piece of software which embeds R using RInside and
| Rcpp. we've avoided the difficulty of locating, and using the R
| install on the users machine by shipping the complete R install as
| part of the installation. R lives in the
-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
