Open x528491x opened 2 months ago
I just read https://github.com/librespot-org/librespot/pull/1318.
So will cross not work going forward and all cross builds have to be done only with cargo?
@yubiuser
Issue reported upstream
Issue probably fixed upstream:
https://github.com/aws/aws-lc-rs/issues/514#issuecomment-2333908415
The issue likely is with cross
: it setups a docker container to actually do the build and it uses a fairly outdated base image (esp. if you use the tagged version and not installing from github directly). All dependencies that can't be downloaded as pre-build crates need to find their way into the image used. This can be quite a challenge (this is why I removed cross
from librespot). But I see there might be some nasm
pre-build crates soon....
Fixed now?
Edit: Moved to https://github.com/librespot-org/librespot/issues/1346
@fivebanger
The error message indicates that your issue is not dircetly related to the issue reported by the OP (and you're not using cross
). I would advice to open a new issue to not derail the thread.
I have created a new issue.
Ever since the version bump for hyper-rustls, nasm becomes a dependency and it creates trouble while building.
Building with
cargo build --release
works, whereas when using cross, it does not work.I see that you've also replaced cross with cargo in your build tests.
Would really like a fix for these build errors and the tagging of a new release as simply using the "latest" has become unpredictable