Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
GLIBC issue
See original GitHub issueI am running centos 7 and its default GLibc is 2.17. I wonder if there is any possible to rebuild a pip version based on that. The error is as follow when importing jax in ipython.
ImportError: /lib64/libm.so.6: version `GLIBC_2.23' not found (required by lib/python3.7/site-packages/jaxlib/xla_extension.so)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:5
- Comments:11 (5 by maintainers)
Top Results From Across the Web
GLIBC version problem - Red Hat Customer Portal
This error happens because the software expects a glibc version number later than what that RHEL release ships with. The software vendor hasn't ......
Read more >Reporting a glibc bug? - GNU.org
Reporting a glibc bug? Please review the bug filing procedures. Jump directly to filling a bug. A GNU Project.
Read more >What is Glibc bug: Things To Know About It - IBM
It is a bug known as glibc bug which can distress hundreds of devices, applications and softwares which are internet connected. It allows...
Read more >Linux glibc security fix created a nastier Linux bug - ZDNET
Sometimes a programming cure is worse than the disease. That's the case with this Linux glibc security bug.
Read more >Valve dev understandably not happy about ... - GamingOnLinux
Recently it was noticed that users on more bleeding-edge Linux distributions that updated saw Easy Anti-Cheat no longer working on Linux, ...
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
To frame Peter’s last comment another way: if you get TF / XLA to support building on a platform, we’ll likely inherit that for free. The best place to push on that might be the TF issue tracker.
I should also add: from the point of view of JAX, our support levels are at least somewhat based on what TensorFlow supports. JAX depends heavily on XLA, which is distributed as part of TensorFlow. The JAX team is quite small and we don’t have resources ourselves to target things older than TensorFlow’s code base can target. We’re not opposed to it, but we only have finite time and many things we would like to make progress on (e.g., making an amazing machine learning toolkit!) Contributions are always welcome.