Skip to content
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

Is x86_64-unknown-linux-musl unsupported for reason or just because of platform detection is lacky? #62

Closed
vi opened this issue Mar 18, 2016 · 2 comments

Comments

@vi
Copy link

vi commented Mar 18, 2016

$ cargo test --target=x86_64-unknown-linux-musl
Build failed, waiting for other jobs to finish...
failed to run custom build command for `fuse v0.2.7`
Process didn't exit successfully: `/home/vi/code/outoforderfs/target/debug/build/fuse-5faebf645a751bfb/build-script-build` (exit code: 101)
--- stderr
thread '<main>' panicked at 'Unsupported target platform', /home/vi/.multirust/toolchains/nightly/cargo/registry/src/github.com-48ad6e4054423464/fuse-0.2.7/build.rs:15
note: Run with `RUST_BACKTRACE=1` for a backtrace.
build.rs>  else if target.ends_with("-unknown-linux-gnu") || target.ends_with("-unknown-freebsd")
@cuviper
Copy link
Contributor

cuviper commented Mar 18, 2016 via email

@zargony
Copy link
Owner

zargony commented Sep 16, 2016

I also think nobody has cared to try yet. In the latest version, the build script was modified to not depend on specific target triples, but to simply use pkg-config. So it should also work with musl now.

I'm closing this since the reported panic condition doesn't exist anymore. Please reopen if this is still an issue (I tried to run rustc on alpine in a Docker container, but couldn't get it to run the easy way)

@zargony zargony closed this as completed Sep 16, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants