8000 nix 0.30.0 fails to build due to missing target · Issue #2810 · rust-lang/docs.rs · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

nix 0.30.0 fails to build due to missing target #2810

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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy st 8000 atement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
quintuple-lained opened this issue Apr 30, 2025 · 4 comments
Closed

nix 0.30.0 fails to build due to missing target #2810

quintuple-lained opened this issue Apr 30, 2025 · 4 comments

Comments

@quintuple-lained
Copy link

Crate name

nix

Build failure link

https://docs.rs/crate/nix/0.30.0/builds/2054049

Additional details

It looks like the build failed due to a missing target system in rust nightly, that being x86_64-fuchsia
@syphar
Copy link
Member
syphar commented Apr 30, 2025

does it work for you locally?

$ rustc +nightly --print target-list | grep fuchs                                                                                                                                                                         
aarch64-unknown-fuchsia
riscv64gc-unknown-fuchsia
x86_64-unknown-fuchsia

@quintuple-lained
Copy link
Author

Hello, on my local arch machine it seems to work as well, so it might just be an issue with the docs.rs end

❯ rustc +nightly --print target-list | grep fuchsia
aarch64-unknown-fuchsia
riscv64gc-unknown-fuchsia
x86_64-unknown-fuchsia

@syphar
Copy link
Member
syphar commented May 5, 2025

sorry if I wasn't clear enough: to me it looks like you're not using the actual target name (x86_64-unknown-fuchsia), but some other version of it (x86_64-fuchsia)

@syphar
Copy link
Member
syphar commented May 13, 2025

it looks like the latest build was successful, so I'm closing this issue.

Feel free to comment / reopen if you still need help here.

@syphar syphar closed this as completed May 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@syphar @quintuple-lained
0