[GH-ISSUE #1326] Build failures caused by nasm #606

Open
opened 2026-02-27 19:31:33 +03:00 by kerem · 9 comments
Owner

Originally created by @x528491x on GitHub (Sep 6, 2024).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/1326

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

Originally created by @x528491x on GitHub (Sep 6, 2024). Original GitHub issue: https://github.com/librespot-org/librespot/issues/1326 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
Author
Owner

@x528491x commented on GitHub (Sep 6, 2024):

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?

<!-- gh-comment-id:2333192724 --> @x528491x commented on GitHub (Sep 6, 2024): 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?
Author
Owner

@roderickvd commented on GitHub (Sep 6, 2024):

@yubiuser

<!-- gh-comment-id:2333266169 --> @roderickvd commented on GitHub (Sep 6, 2024): @yubiuser
Author
Owner

@x528491x commented on GitHub (Sep 6, 2024):

Issue reported upstream

https://github.com/aws/aws-lc-rs/issues/514

<!-- gh-comment-id:2333547381 --> @x528491x commented on GitHub (Sep 6, 2024): Issue reported upstream https://github.com/aws/aws-lc-rs/issues/514
Author
Owner

@x528491x commented on GitHub (Sep 6, 2024):

Issue probably fixed upstream:

https://github.com/aws/aws-lc-rs/issues/514#issuecomment-2333908415

<!-- gh-comment-id:2333918923 --> @x528491x commented on GitHub (Sep 6, 2024): Issue probably fixed upstream: https://github.com/aws/aws-lc-rs/issues/514#issuecomment-2333908415
Author
Owner

@yubiuser commented on GitHub (Sep 6, 2024):

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....

<!-- gh-comment-id:2333983270 --> @yubiuser commented on GitHub (Sep 6, 2024): 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....
Author
Owner

@roderickvd commented on GitHub (Sep 16, 2024):

Fixed now?

<!-- gh-comment-id:2353539915 --> @roderickvd commented on GitHub (Sep 16, 2024): Fixed now?
Author
Owner

@fivebanger commented on GitHub (Sep 20, 2024):

Edit:
Moved to https://github.com/librespot-org/librespot/issues/1346

<!-- gh-comment-id:2364138297 --> @fivebanger commented on GitHub (Sep 20, 2024): Edit: Moved to https://github.com/librespot-org/librespot/issues/1346
Author
Owner

@yubiuser commented on GitHub (Sep 20, 2024):

@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.

<!-- gh-comment-id:2364309575 --> @yubiuser commented on GitHub (Sep 20, 2024): @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.
Author
Owner

@fivebanger commented on GitHub (Sep 20, 2024):

I have created a new issue.

<!-- gh-comment-id:2364558451 --> @fivebanger commented on GitHub (Sep 20, 2024): I have created a new issue.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/librespot#606
No description provided.