It appears that if you try to merge openjdk-17.0.6_p10 on a machine with glibc-2.33 or older, the internal bootstrap jdk will not run reporting it can't find GLIBC_2.34. I manually forced the glibc update (not sure why it's so late on the dependencies list to update, perhaps some bdeps needed to be built) but after merging glibc-2.36, now openjdk will merge. Reproducible: Always Steps to Reproduce: 1. Have old glibc-2.33 machine 2. merge openjdk-17.0.6_p10 3. Actual Results: In build.log it fails: configure: Output from java -version was: /var/tmp/portage/dev-java/openjdk-17.0.6_p10/work/openjdk-bootstrap-17.0.1_p12/bin/java: /lib/libc.so.6: version `GLIBC_2.34' not found (required by /var/tmp/portage/dev-java/openjdk-17.0.6_p10/work/openjdk-bootstrap-17.0.1_p12/bin/java) Expected Results: openjdk should merge without crashing. workaround is to upgrade glibc manually first regardless of what portage thinks the upgrade order should be.
Internal bootstrap only used on couple of arches, which one you are on? Attach emerge info, please.
This was with x86 (i686). I don't know about other architectures.
BTW, the package merged fine on the system after I merged glibc-2.36, so it no longer is an issue for me, but perhaps this will show up again on someone else's machine.
openjdk-17.0.6_p10 is gone, and glibc-2.33 masked.
