Build static MUSL target with vendored openssl #8
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.
Rust is capable of building binaries which carry their own MUSL
libc internally for operation on almost any userspace provided that
the kernel ABI (signals and such) is compatible with the platform
target selected.
This project runs into OpenSSL dependency problems when building a
MUSL target as the host libraries are generally built for GNU.
Address the concern by providing a vendored openssl, which permits
building for the target via
cargo build --features vendored
withthe relevant release and target/toolchain invocation.
Testing:
This patch is applied to our internal PKGBUILD, producing working
binaries.