https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: dev-java/openjfx-11.0.11_p1-r3 fails to compile. Discovered on: amd64 (internal ref: ci) Info about the issue: https://wiki.gentoo.org/wiki/Project:Tinderbox/Common_Issues_Helper#CF0014
Created attachment 897028 [details] build.log build log and emerge --info
Error(s) that match a know pattern in addition to what has been reported in the summary: * JDK Docs not found, terminating build early * [[ -r ${jdk_doc}/element-list ]] || die "JDK Docs not found, terminating build early";
The ebuild looks for "${EPREFIX}/usr/share/doc/openjdk-${SLOT}/html/api/element-list", and aborts if it is not found (in this code-path controlled by USE=doc) but for the JDK my build selected this file is actually installed at /usr/share/doc/openjdk-11.0.23_p9/html/api/element-list. Docs for openjdk are installed in a path including its full $PF, not just its $SLOT.
I just happened to notice a "QA notice" in a build log of =dev-java/openjdk-11.0.23_p9: "/var/tmp/portage/dev-java/openjdk-11.0.23_p9/temp/environment: line 4114: dosym8: command not found". In that environment file, line 4114 is at the end of src_install(), which indeed has "dosym8". Since the ebuild is in EAPI=8, surely that should be just "dosym"? I think that will (once openjdk is reinstalled) put (a symlink to) the JDK documentation where the openjfx ebuild expects to find it.
(In reply to Jonathan Lovelace from comment #4) > I just happened to notice a "QA notice" in a build log of > =dev-java/openjdk-11.0.23_p9: > "/var/tmp/portage/dev-java/openjdk-11.0.23_p9/temp/environment: line 4114: > dosym8: command not found". In that environment file, line 4114 is at the > end of src_install(), which indeed has "dosym8". Since the ebuild is in > EAPI=8, surely that should be just "dosym"? [...] https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=89d074b527118d9a790fa20d6b1d1c7639ed3bef
