Closed drahnr closed 4 years ago
~So it seems I made a mistake and missed the fact that rustup default nightly-x86_64-unknown-linux-musl
updates the toolchain to the latest~ does not update the toolchain, but the dates did not match up, as such another toolchain was installed instead.
As such that one was used, including cargo, which now depends on libunwind.
Actually the issue persists, even after assuring only one toolchain (the tagged one is present).
Thank you for the bug report!
Before we release images, we run the scripts hooks/build and hooks/test. The test script compiles and links examples/using-diesel.
Please try taking a fresh rust-musl-builder
image and compiling using-diesel
as shown in hooks/test
. Be careful not to upgrade the Rust toolchain. This should work, but if it doesn't, we'll learn more about the problem.
I've also scheduled two builds of nightly-2020-01-26
(one with OpenSSL 1.0 and one with OpenSSL 1.1). This should allow us to see if using-diesel
still links correctly with the latest nightly.
Thank you for your help debugging this!
I tested as requested and the root cause here was my own fault, I accidentally mapped $HOME/.cargo
into the container rather than the registry
/git
subdir.
My apologies for the noise.
How could this project be improved?
Add libunwind.
Some nightly versions and cargo require it (tested with: