Да есть там фигня. Для спортивного интереса собирал openJDK 1.19 на
x64 . Смутно припоминаю, что при сборке просил указать на JDK
готовый. Проблема курицы и яйца :) Может прокатит если указать 1.8. P.S.
Да попробовал не проходит. Шо за дебилизм. -> "Your Boot JDK version must be one of: 16 17"
P.S.S.
Проверил. У них психическая девиация. Boot JDK должен быть установлен не старший чем 2 версии назад. С версии 1.8 надо компилить 5 версий . 1.8 → 1.10
→ 1.12 →1.14 → 1.16 и наконец → 1.17
.....
checking if packaged modules are kept... enabled, default
checking for version string... 17-internal+0-adhoc.an.jdk
checking for javac... /usr/bin/javac
checking for java... /usr/bin/java
configure: Found potential Boot JDK using java(c) in PATH
configure: Potential Boot JDK found at /usr/lib/jvm/java-8-openjdk-amd64 is inco rrect JDK version (openjdk version "1.8.0_312" OpenJDK Runtime Environment (buil d 1.8.0_312-8u312-b07-0ubuntu1~20.04-b07) OpenJDK 64-Bit Server VM (build 25.312 -b07, mixed mode)); ignoring
configure: (Your Boot JDK version must be one of: 16 17)
configure: Found potential Boot JDK using well-known locations (in /usr/lib/jvm/ java-8-openjdk-amd64)
configure: Potential Boot JDK found at /usr/lib/jvm/java-8-openjdk-amd64 is inco rrect JDK version (openjdk version "1.8.0_312" OpenJDK Runtime Environment (buil d 1.8.0_312-8u312-b07-0ubuntu1~20.04-b07) OpenJDK 64-Bit Server VM (build 25.312 -b07, mixed mode)); ignoring
configure: (Your Boot JDK version must be one of: 16 17)
configure: Found potential Boot JDK using well-known locations (in /usr/lib/jvm/ java-1.8.0-openjdk-amd64)
configure: Potential Boot JDK found at /usr/lib/jvm/java-1.8.0-openjdk-amd64 is incorrect JDK version (openjdk version "1.8.0_312" OpenJDK Runtime Environment ( build 1.8.0_312-8u312-b07-0ubuntu1~20.04-b07) OpenJDK 64-Bit Server VM (build 25 .312-b07, mixed mode)); ignoring
configure: (Your Boot JDK version must be one of: 16 17)
configure: Could not find a valid Boot JDK. OpenJDK distributions are available at http://jdk.java.net/.
configure: This might be fixed by explicitly setting --with-boot-jdk
configure: error: Cannot continue
configure exiting with result code 1