-
Notifications
You must be signed in to change notification settings - Fork 289
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
Failed to compile on windows with ssl-vendored
& cmake-build
combination
#572
Comments
I am fighting with the same on Linux |
Ok, I've investigated this more and it appears to be because So when it compiles the static version of openssl, it does so without the appropriate exports, hence why it's complaining. If you add the following to [build-dependencies]
openssl-src = { version = "111", features = ["force-engine"] } |
Cargo.toml is like follows but I am still getting an issue
Error:
|
Sounds like there are no linux headers installed wherever you're trying to run this. You could try adding Given [package]
name = "rdtest"
version = "0.1.0"
edition = "2021"
[dependencies]
rdkafka = { version = "0.29.0", features = ["cmake-build", "ssl-vendored"]}
[build-dependencies]
openssl-src = { version = "111", features = [ "force-engine" ] } and use rdkafka::Timestamp;
fn main() {
let timestamp = Timestamp::now();
println!("{timestamp:?}");
} The following docker file compiles & runs just fine: FROM clux/muslrust
RUN ln -s /bin/g++ /bin/musl-g++
ADD Cargo.toml .
ADD src src
RUN cargo build --release
CMD ["target/x86_64-unknown-linux-musl/release/rdtest"] |
Morning, after installing |
Removing |
However, in Ubuntu the package you mention doesn't solve the error |
in openssl-sys, they add this:
if you add
these configurations may conflict so I add this:
it works |
Hey, I can't seem to get this to link on windows with a vendored ssl.
I.e, using:
I get the following output:
I am also seeing a lot of these errors:
But I can confirm that
ossl_static.pdb
is in thedebug\build\openssl-sys-63196b440406ab23\out\openssl-build\install\lib
directory alongside the two lib files:The
link.exe
statement does include that lib directory:The text was updated successfully, but these errors were encountered: