Bug#874153: FTBFS with Java 9: jre/bin/java

Le 24/11/2017 à 23:37, Dirk Eddelbuettel a écrit : > I (very respectfully) decline. > > I have had enough "fun" keeping this working, and I don't even use Java. If > *you* want to experiment, by all means do. Change debian/{rules,control} for > r-base, then try building r-cran-rjava. I

Bug#874153: FTBFS with Java 9: jre/bin/java

On 24 November 2017 at 23:15, Emmanuel Bourg wrote: | Le 24/11/2017 à 20:10, Dirk Eddelbuettel a écrit : | | > 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

Bug#874153: FTBFS with Java 9: jre/bin/java

Le 24/11/2017 à 20:10, Dirk Eddelbuettel a écrit : > 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. Ideally the package should depend

Bug#874153: FTBFS with Java 9: jre/bin/java

Simon, On 24 November 2017 at 13:56, Simon Urbanek wrote: | Emmanuel, | | | > On Nov 24, 2017, at 11:02 AM, Emmanuel Bourg 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.

Bug#874153: FTBFS with Java 9: jre/bin/java

Emmanuel, > On Nov 24, 2017, at 11:02 AM, Emmanuel Bourg 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

Bug#874153: FTBFS with Java 9: jre/bin/java

Le 24/11/2017 à 16:54, Dirk Eddelbuettel a écrit : >configuring Java ... >*** JAVA_HOME is not a valid path, ignoring > Any concrete tips as to what we should try instead? What about setting JAVA_HOME to /usr/lib/jvm/default-java? Emmanuel Bourg

Bug#874153: FTBFS with Java 9: jre/bin/java

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

Bug#874153: FTBFS with Java 9: jre/bin/java

On 24 November 2017 at 10:30, Simon Urbanek wrote: | 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. Ok. So currently we do openjdk-9-jdk | default-jdk [!arm

Bug#874153: FTBFS with Java 9: jre/bin/java

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. Cheers, Simon > On Nov 24, 2017, at 9:03 AM, Dirk Eddelbuettel wrote: > > > Hi Emmanuel, > >

Bug#874153: FTBFS with Java 9: jre/bin/java

Hi Emmanuel, On 24 November 2017 at 14:40, Emmanuel Bourg wrote: | Hi Dirk, | | Is it possible to simply use the /usr/lib/jvm/default-java/bin/java path | instead of /usr/lib/jvm/default-java/jre/bin/java? Historically jre/bin/ | contained only the JRE executables, and bin/ contained the JDK

Bug#874153: FTBFS with Java 9: jre/bin/java

Hi Dirk, Is it possible to simply use the /usr/lib/jvm/default-java/bin/java path instead of /usr/lib/jvm/default-java/jre/bin/java? Historically jre/bin/ contained only the JRE executables, and bin/ contained the JDK tools (javac, jar, etc). With Java 9 the layout has been simplified and the

Bug#874153: FTBFS with Java 9: jre/bin/java

Simon, On 20 October 2017 at 10:14, Simon Urbanek wrote: | oh, no, rJava does not run javareconf - it only tells the user to do so if the configuration is broken. The R CMD javareconf occurrences in configure are always in the text section printed to the user. As you correctly said, it would

Bug#874153: FTBFS with Java 9: jre/bin/java

Dirk, oh, no, rJava does not run javareconf - it only tells the user to do so if the configuration is broken. The R CMD javareconf occurrences in configure are always in the text section printed to the user. As you correctly said, it would be very bad if a package tried to change the system

Bug#874153: FTBFS with Java 9: jre/bin/java

Simon, On 19 October 2017 at 17:49, Simon Urbanek wrote: | Dirk, | | to clarify - this is about *R* configuration, not about rJava at all. rJava has nothing to do with those settings - it just uses what R was configured with. The only part rJava plays here is that it needs those R settings to

Bug#874153: FTBFS with Java 9: jre/bin/java

Dirk, to clarify - this is about *R* configuration, not about rJava at all. rJava has nothing to do with those settings - it just uses what R was configured with. The only part rJava plays here is that it needs those R settings to be valid - just like other R packages that use Java. As you

Bug#874153: FTBFS with Java 9: jre/bin/java

On 19 October 2017 at 16:31, Simon Urbanek wrote: | | > On Oct 19, 2017, at 4:12 PM, Dirk Eddelbuettel wrote: | > | > | > On 19 October 2017 at 15:47, Simon Urbanek wrote: | > | R CMD javareconf is always needed to register Java support with R (on all unix platforms). | > |

Bug#874153: FTBFS with Java 9: jre/bin/java

> On Oct 19, 2017, at 4:12 PM, Dirk Eddelbuettel wrote: > > > On 19 October 2017 at 15:47, Simon Urbanek wrote: > | R CMD javareconf is always needed to register Java support with R (on all > unix platforms). > > s/always/sometimes/ > > The values get encoded when I build R

Bug#874153: FTBFS with Java 9: jre/bin/java

On 19 October 2017 at 15:47, Simon Urbanek wrote: | R CMD javareconf is always needed to register Java support with R (on all unix platforms). s/always/sometimes/ The values get encoded when I build R binaries. For many years now, that was good enough. | Like I said, I don't know what deb

Bug#874153: FTBFS with Java 9: jre/bin/java

R CMD javareconf is always needed to register Java support with R (on all unix platforms). Like I said, I don't know what deb packages do here - I presume you must do something in your R binary and all I can presume is that whatever the setup is then doesn't match what's there now. Cheers,

Bug#874153: FTBFS with Java 9: jre/bin/java

Simon, On 18 October 2017 at 21:34, Simon Urbanek wrote: | Dirk, | | I don't have the details but this looks like as incorrect Java configuration in R - the Java home is obviously incomplete as it's missing bin/java and/or that path is wrong. Also I'm surprised to the the odd paths

Bug#874153: FTBFS with Java 9: jre/bin/java

Dirk, I don't have the details but this looks like as incorrect Java configuration in R - the Java home is obviously incomplete as it's missing bin/java and/or that path is wrong. Also I'm surprised to the the odd paths "/usr/lib/jvm/default-java/" since at least in my installations I see the

Bug#874153: FTBFS with Java 9: jre/bin/java

Simon, With your new rJava_0.9-9 I tried this against Debian's openjdk-9-jdk -- but with R 3.4.2 as built against openjdk-7 -- and it still fails: checking whether setjmp.h is POSIX.1 compatible... yes checking whether sigsetjmp is declared... yes checking whether siglongjmp is declared... yes

Bug#874153: FTBFS with Java 9: jre/bin/java

Source: rjava Version: 0.9-8 Severity: normal User: debian-j...@lists.debian.org Usertags: default-java9 This package fails to build with default-jdk pointing to openjdk-9-jdk. Please fix it, so that we can start the transition to Java 9. The wiki has some common problems and their solutions: