Centos build: Create symlinks for ssl libs #52
Merged
Conversation
This file contains 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
build was missing libssl.1.1.so and libcrypto.1.1.so symlinks needed by the executable itself, because python is now explicitly build with OpenSSL 1.1.1
iLLiCiTiT
changed the title
iLLiCiTiT
approved these changes
Sep 19, 2023
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.
Changelog Description
Docker build was missing
libssl.1.1.soandlibcrypto.1.1.sosymlinks needed by the executable itself, because Python is now explicitly built with OpenSSL 1.1.1. This is similar to ynput/OpenPype#5633Additional info
This just creating symlinks, but to already copied libraries, but it should be probably handled more gracefuly.
Testing notes: