Simon, On 24 November 2017 at 13:56, Simon Urbanek wrote: | Emmanuel, | | | > On Nov 24, 2017, at 11:02 AM, Emmanuel Bourg <emmanuel.bo...@gmail.com> wrote: | > | > Le 24/11/2017 à 16:30, Simon Urbanek a écrit : | >> Absolutely - mixing jre and non-jre paths doesn't sound like a good idea. It was somewhat odd idiosyncrasy of the Debian configuration - I have not seen it on any other system. | > | > Actually there is nothing Debian specific here, the jre/bin/ and bin/ | > directories have been there for ~20 years in all Java distributions. It | > just changed two months ago with the release of Java 9. | > | > If you are referring to the fact that Debian installs both the JRE and | > the JDK in the same directory (/usr/lib/jvm/default-java) that's also | > true for Fedora and Arch Linux. | > | | Ah, sorry for the confusion, I was referring to JAVA being set to jre/bin while JAVAC was set to bin since most commonly bin did include tools in jre/bin. | | I think in your case you may possibly want to use | JAVA=/usr/lib/jvm/default-java/bin/java JAVA_HOME=/usr/lib/jvm/default-java | when configuring R to make sure it uses default-java that works both for Java 1.8 and 1.9 (please double-check, though).
So we should do this when configuring R itself, correct? I may do another RC build before R 3.4.3 is out later next week. Not entirely sure how to test it because actual Depends: result from this. So if I start with java 9 it may be be java 9 and nothing else. Dirk | | R doesn't actually care as long as the paths for JAVA and JAVAC actually exist and I see now that the issue was that jvm/default-java is pointing directly inside the Java installation, so if they change how Java ship things it breaks. | | One way around it is to point both JAVA and JAVAC to the symlinks managed by the distribution so it's not susceptible so changes in the Java distribution. | | Cheers, | Simon | -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
