We have tried to execute /opt/openjdk-bin-11.0.14_p9/bin/java but failed. If you have installed Java in a unusual place you can set JAVA_HOME to the directory containing the Java installation. * ERROR: dev-java/core-specs-alpha-0.2.56::gentoo failed (compile phase): * eant failed * * Call stack: ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop-j4-20220119-205952 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.3.1 [2] x86_64-pc-linux-gnu-11.2.1 * clang/llvm (if any): clang version 13.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/13/bin /usr/lib/llvm/13 13.0.0 Python 3.9.10 Available Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby27 (with Rubygems) [3] ruby30 (with Rubygems) * Available Rust versions: [1] rust-bin-1.58.0 [2] rust-1.58.1 * GENTOO_VM=openjdk-bin-11 CLASSPATH="" JAVA_HOME="/opt/openjdk-bin-11.0.14_p9" JAVACFLAGS="-source 1.8 -target 1.8" COMPILER="javac" The following VMs are available for generation-2: *) AdoptOpenJDK 11.0.14_p9 [openjdk-bin-11] 2) AdoptOpenJDK 8.312_p07 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 [2] openjdk-bin-11 system-vm The Glorious Glasgow Haskell Compilation System, version 8.10.4 php cli: HEAD of ::gentoo commit 9b509092e6b908cfe28a24e9637bcee02b8acbcd Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Sat Jan 22 09:52:07 2022 +0000 2022-01-22 09:52:05 UTC emerge -qpvO dev-java/core-specs-alpha [ebuild N ] dev-java/core-specs-alpha-0.2.56
Created attachment 763168 [details] emerge-info.txt
Created attachment 763169 [details] dev-java:core-specs-alpha-0.2.56:20220122-104348.log
Created attachment 763170 [details] emerge-history.txt
Created attachment 763171 [details] environment
Created attachment 763172 [details] etc.portage.tar.bz2
Created attachment 763173 [details] temp.tar.bz2
So it looks to me like the newest clojure ebuild (1.10.3) no longer uses this ebuild, but instead does some hackery during src_prepare. It is not clear to me that this ebuild is needed anymore as a result. I've cced Sam to see if he has any insights here.