[Breaking change] Glibc version changed in 3.7.1
See original GitHub issueVersion 3.7.1
was build for glibc 2.29+ and version 3.7.0
(and lower) works with glibc lower than 2.29 (e.g. on Amazon Linux)
Exception in thread "main" java.lang.UnsatisfiedLinkError: /mnt/tmp/libh3-java8981121668568062484.so: /lib64/libm.so.6: version `GLIBC_2.29' not found
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:8
Top Results From Across the Web
Linux and glibc API changes - man7.org
Linux 5.14 (29 August 2021) API changes include the following: The futex() system call adds a new operation, FUTEX_LOCK_PI2.
Read more >[SOLVED] How do I rollback my glibc version in Slackware 15.0?
What is the proper way to roll back the glibc version without this ... You might want to switch to 15.0 to avoid...
Read more >What's New In Python 3.8 — Python 3.11.1 documentation
This article explains the new features in Python 3.8, compared to 3.7. Python 3.8 was released on October 14, 2019. For full details,...
Read more >How exactly a system might break by updating glibc?
In case of semantics changes to function calls, glibc will include two versions, one for the old semantics and another for the new...
Read more >Release/2.27 - glibc wiki - sourceware.org
setjmp changes? commit f81ddabffd also breaks software like vlc or amarok, they crash with a segmentation fault during startup.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
As of #92 we should no longer have unexpected glibc upgrades
@isaacbrodsky The code is running on a graviton instance (c6g.metal) using the
Amazon Linux 2022.0.20220202
AMI, withcorretto 11
andmaven 3.8.4
, not using docker.3.7.0
works without error,3.7.2
errors as mentioned above.As a sidenote, in contrary, on Mac M1 Max,
3.7.2
works and3.7.0
fails with an error mentioned in #73