-
-
Notifications
You must be signed in to change notification settings - Fork 454
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong zlib library might be loaded #23122
Labels
Milestone
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:3
Who is requiring the system libz? Maybe run with |
comment:4
Replying to @vbraun:
|
This comment has been minimized.
This comment has been minimized.
New commits:
|
Commit: |
Reviewer: Erik Bray |
comment:7
I think this is fine. I've run into this problem before, for example, with libxml. |
comment:8
Hmm strange, I get
|
Changed branch from u/jdemeyer/wrong_zlib_library_might_be_loaded to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After the zlib upgrade, I cannot no longer run Sage under plain Python:
This is because there is some kind of race condition: certain system libraries (OpenSSL for example) link against
/lib64/libz.so.1
while Sage components link against the Sage-built libz.In turns out that the first libz library which is loaded "wins": that one will be used by anything linking against
libz
. When starting IPython, the correct libz library is loaded because some IPython component uses libz. When running plain Python, this is not the case and the wrong libz is loaded. The easiest fix is to explicitlyimport libz
when Sage starts up.Component: build
Author: Jeroen Demeyer
Branch/Commit:
d59afe3
Reviewer: Erik Bray
Issue created by migration from https://trac.sagemath.org/ticket/23122
The text was updated successfully, but these errors were encountered: