Bug#897417: openmpi: v3.0.1.real-1 FTBFS on most architectures

[Graham Inggs]

Hi Alastair

It appears this is already fixed upstream [1] :

configury: use javac vs javah whenever possible

javah is no more available from Java 10, so try
javac -h first (available since Java 8) and fallback on javah

Regards
Graham


[1] 
https://github.com/open-mpi/ompi/commit/5370586d98b880d3e14659252620bebca92022af

Bug#897417: openmpi: v3.0.1.real-1 FTBFS on most architectures

[Boyuan Yang]

Source: openmpi
Version: 2.1.1-8
Severity: grave
Justification: renders package unusable

According to https://buildd.debian.org/status/package.php?p=openmpi=sid ,
it fails to build on all release architectures except amd64 (I think it should
also FTBFS on amd64 if a source-only upload is made).

Retrieved from arm64 buildlog:

[...]
*** Java compiler
checking --with-jdk-bindir value... sanity check ok (/usr/lib/jvm/default-
java/bin)
checking --with-jdk-headers value... sanity check ok (/usr/lib/jvm/default-
java/include)
checking for javac... /usr/lib/jvm/default-java/bin/javac
checking for javah... no
checking for jar... /usr/lib/jvm/default-java/bin/jar
checking Java support available... no

*** Java MPI bindings
checking if want Java bindings... yes
configure: WARNING: Java bindings requested but no Java support found
configure: error: cannot continue
tail -v -n \+0 config.log
[...]

I haven't dig into it, but it might be related to recent changes around default
Java implementation.

--
Regards,
Boyuan Yang



-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE=zh_CN 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled