Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 898104 - dev-java/openjdk-17.0.6_p10 internal bootstrap jdk requires glibc-2.34
Summary: dev-java/openjdk-17.0.6_p10 internal bootstrap jdk requires glibc-2.34
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: Normal normal (vote)
Assignee: Georgy Yakovlev
Depends on:
Reported: 2023-02-27 10:05 UTC by Ben
Modified: 2023-02-28 00:54 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Ben 2023-02-27 10:05:23 UTC
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
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/ 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.
Comment 1 Georgy Yakovlev archtester gentoo-dev 2023-02-28 00:42:52 UTC
Internal bootstrap only used on couple of arches, which one you are on?
Attach emerge info, please.
Comment 2 Ben 2023-02-28 00:52:13 UTC
This was with x86 (i686).  I don't know about other architectures.
Comment 3 Ben 2023-02-28 00:54:23 UTC
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.