-
Notifications
You must be signed in to change notification settings - Fork 192
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
Link error while building libsodium-ffi #84
Comments
Even with: [dependencies.openssl]
version = "*"
features = ["vendored"] This still fails |
Thank you for the bug report! This looks like the same error as sfackler/rust-openssl#1198. I think this might be a problem in This might be a host vs. target problem. The "host" is the Ubuntu image that provides the Rust toolchain, and the "target" is the
Unfortunately, these issues can be frustrating to fix. |
I'm experiencing the same issue trying to compile a project that depends on diesel. Is there a quick fix for this? |
Unfortunately, no, there are no easy fixes for adding new C libraries. Somebody will have to take a look at |
Seeing what seems to be the same problem when using openssl in a build script. fn main() {
native_tls::Identity::from_pkcs12(b"", "").unwrap();
} In a build script fails, but the same code in a crate works just fine. |
@Marwes If you have a problem with |
My understanding is this:
Since we have no way to configure how Am I getting this right? |
@promethe42 I'm not actually sure what the underlying problem is, but that seems like a reasonable hypothesis. In general, rust-musl-builder aims to support a small number of essential C libraries. To do this, it needs to configure everything for cross-compilation and static linking. This can be a complicated and frustrating process, because:
I choose to take on this work for PostgreSQL and OpenSSL and their supporting libraries, because they're extremely common dependencies (and because I need them personally). For less common C libraries, and libraries that I don't use myself, I simply don't have enough time to investigate and write the necessary PRs against other people's code. |
Please note that I have recently updated See sfackler/rust-openssl#1337 for more details. |
I have migrated my build script to build with other docker mirrors. So I am not quite sure about whether this issue have been fixed. It is ok to be closed, btw. |
What did you try to do?
Build my project (
libsodium-ffi
) that depends onopenssl v0.10.26
.What happened?
Does
./test-image
work?Don't know,
./test-image
blocks onUpdating crates.io index
(Network issue).The text was updated successfully, but these errors were encountered: