> On May 24, 2018, at 1:47 PM, Simon Urbanek
> wrote:
>
> You need to configure R to match your Java using R CMD javareconf.
>
> The CRAN machine uses JDK 1.9 which was the default until Java 10 was
> released recently. If you use something else, you have to
Greetings and Salutations Simon,
I appreciate the feedback at long last; but, I fear that a majority of this is
scaremongering at this stage. These installers, clang4 and the _unofficial_
macos rtools, have operated since their inception without incident since almost
a year ago. Their sources
Greetings and Salutations Nigel,
You’re welcome!
Just a word of advice regarding 3.4.x and 3.5.x, make sure the installer
includes packages from the desired version. ALTREP was added in 3.5.x and that
has caused issues with users who opt to copy over the previous installation of
r binaries to
Just for posterity - please note that the installer referenced below is
potentially unsafe and dangerous, because it does NOT actually package the
binary but rather contains just an arbitrary shell script and thus you cannot
be sure that you get the official binaries or something malicious
You need to configure R to match your Java using R CMD javareconf.
The CRAN machine uses JDK 1.9 which was the default until Java 10 was released
recently. If you use something else, you have to configure R accordingly.
Also I strongly recommend using rJava 0.9-10 since it works around some
James,
Thank you for the wonderful response and for making your packaging code
available (and producing this!). Very much appreciated.
I wound up taking an approach where I just modified the CRAN R installer to
include a few more packages (specifically all I had installed). I couldn't
find