Statically link libpython into interpreter (but keep building libpython3.x.so) #592
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
geofft
force-pushed
the
interp-static-libpython
branch
3 times, most recently
from
a5b9b77 to
d8838a7
Compare
geofft
force-pushed
the
interp-static-libpython
branch
from
d8838a7 to
2af08c0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Opening PR just to see how far CI gets. I've done some very minimal testing locally (in a CPython tree, not using the p-b-s infrastructure) and it seems to do what I want.
We can probably make some changes to patchelf as a result.
The added patch here is geofft/cpython branch static-interpreter. I'll open a PR to CPython and link it once CI looks good.