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 !hppa !kfreebsd-i386 !kfreebsd-amd64 
!hurd-i386]

and nothing else.  Per yesterday's build this seems to result in

   Selecting previously unselected package openjdk-9-jre-headless:amd64.

   Preparing to unpack .../073-openjdk-9-jre-headless_9.0.1+11-1_amd64.deb ...

   Unpacking openjdk-9-jre-headless:amd64 (9.0.1+11-1) ...

   Selecting previously unselected package ca-certificates-java.


   [...]

   Setting up openjdk-9-jre-headless:amd64 (9.0.1+11-1) ...

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/rmid to 
provide /usr/bin/rmid (rmid) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/java to 
provide /usr/bin/java (java) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/keytool to 
provide /usr/bin/keytool (keytool) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jjs to 
provide /usr/bin/jjs (jjs) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/pack200 to 
provide /usr/bin/pack200 (pack200) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/rmiregistry 
to provide /usr/bin/rmiregistry (rmiregistry) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/unpack200 
to provide /usr/bin/unpack200 (unpack200) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/orbd to 
provide /usr/bin/orbd (orbd) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/servertool 
to provide /usr/bin/servertool (servertool) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/tnameserv 
to provide /usr/bin/tnameserv (tnameserv) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/lib/jexec to 
provide /usr/bin/jexec (jexec) in auto mode


   [...]

   Setting up openjdk-9-jdk-headless:amd64 (9.0.1+11-1) ...

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/idlj to 
provide /usr/bin/idlj (idlj) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jdeps to 
provide /usr/bin/jdeps (jdeps) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/wsimport to 
provide /usr/bin/wsimport (wsimport) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jinfo to 
provide /usr/bin/jinfo (jinfo) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jstat to 
provide /usr/bin/jstat (jstat) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jlink to 
provide /usr/bin/jlink (jlink) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/javah to 
provide /usr/bin/javah (javah) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jhsdb to 
provide /usr/bin/jhsdb (jhsdb) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jps to 
provide /usr/bin/jps (jps) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jstack to 
provide /usr/bin/jstack (jstack) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jrunscript 
to provide /usr/bin/jrunscript (jrunscript) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/javac to 
provide /usr/bin/javac (javac) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jmod to 
provide /usr/bin/jmod (jmod) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/javap to 
provide /usr/bin/javap (javap) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jar to 
provide /usr/bin/jar (jar) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jaotc to 
provide /usr/bin/jaotc (jaotc) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/policytool 
to provide /usr/bin/policytool (policytool) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/javadoc to 
provide /usr/bin/javadoc (javadoc) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/schemagen 
to provide /usr/bin/schemagen (schemagen) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jshell to 
provide /usr/bin/jshell (jshell) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/xjc to 
provide /usr/bin/xjc (xjc) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/rmic to 
provide /usr/bin/rmic (rmic) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jdeprscan 
to provide /usr/bin/jdeprscan (jdeprscan) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jimage to 
provide /usr/bin/jimage (jimage) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jstatd to 
provide /usr/bin/jstatd (jstatd) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jmap to 
provide /usr/bin/jmap (jmap) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jdb to 
provide /usr/bin/jdb (jdb) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/serialver 
to provide /usr/bin/serialver (serialver) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/wsgen to 
provide /usr/bin/wsgen (wsgen) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jcmd to 
provide /usr/bin/jcmd (jcmd) in auto mode

   update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jarsigner 
to provide /usr/bin/jarsigner (jarsigner) in auto mode


   [...]
   
   configuring Java ...
   *** JAVA_HOME is not a valid path, ignoring
   Java interpreter : /usr/bin/java
   Java version     : 9.0.1
   Java home path   : /usr/lib/jvm/java-9-openjdk-amd64
   Java compiler    : /usr/bin/javac
   Java headers gen.: /usr/bin/javah
   Java archive tool: /usr/bin/jar
   
   trying to compile and link a JNI program 
   detected JNI cpp flags    : -I$(JAVA_HOME)/include 
-I$(JAVA_HOME)/include/linux
   detected JNI linker flags : -L$(JAVA_HOME)/lib/server -ljvm
   make[3]: Entering directory '/tmp/Rjavareconf.D1cWqu'
   gcc -std=gnu99 -I/build/r-base-3.4.2.20171123/include -DNDEBUG
   -I/usr/lib/jvm/java-9-openjdk-amd64/include
   -I/usr/lib/jvm/java-9-openjdk-amd64/include/linux     -fpic  -g -O2
   -fdebug-prefix-map=/build/r-base   -3.4.2.20171123=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -g  -c conftest.c -o conftest.o
   gcc -std=gnu99 -shared -L/build/r-base-3.4.2.20171123/lib -Wl,-z,relro -o 
conftest.so conftest.o -L/usr/lib/jvm/java-9-openjdk-amd64/lib/server -ljvm 
-L/build/r-base-3.4.2.20171123/lib -lR
   make[3]: Leaving directory '/tmp/Rjavareconf.D1cWqu'
   
   
   JAVA_HOME        : /usr/lib/jvm/java-9-openjdk-amd64
   Java library path: $(JAVA_HOME)/lib/server
   JNI cpp flags    : -I$(JAVA_HOME)/include -I$(JAVA_HOME)/include/linux
   JNI linker flags : -L$(JAVA_HOME)/lib/server -ljvm
   Updating Java configuration in /build/r-base-3.4.2.20171123
   Done.

Any concrete tips as to what we should try instead?

Dirk

| Cheers,
| Simon
| 
| 
| 
| > On Nov 24, 2017, at 9:03 AM, Dirk Eddelbuettel <e...@debian.org> wrote:
| > 
| > 
| > 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 tools
| > | (javac, jar, etc). With Java 9 the layout has been simplified and the
| > | executables are all in the bin/ directory. If you only use the java
| > | interpreter you can point to bin/java since it exists in both OpenJDK 8
| > | and OpenJDK 9 packages.
| > 
| > I think that is a question for Simon (CC'ed) who controls both the rJava 
(aka
| > r-cran-rjava) side as well as how r-base provides.  Might be a question of
| > path ordering.  I am not sure. I don't my side of things sets anything.
| > 
| > Dirk
| > 
| > | 
| > | Emmanuel Bourg
| > | 
| > 
| > -- 
| > http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
| > 
| 

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Reply via email to