-
Notifications
You must be signed in to change notification settings - Fork 989
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
Cannot compile with musl as target #316
Comments
I ran into this same error for a project I have which depends on tera. I think the specific crate that needed updating was |
@Keats yes we're now seeing this failure on Homebrew's CI as well. |
Doing a 0.3.4 release after |
@nbigaouette can you try to run the Dockerfile on nightly? If it compiles fine than we can leave it as is and I'll just release a 0.3.4 version |
I tried with the Dockerfile using nightly rust but the issue is still there. Root issue: rust-lang/rust#36710 |
In the meantime I published 0.3.4 which is a cargo updated version only |
Awesome! Thank you @Keats. 0.3.4 shipped in Homebrew Homebrew/homebrew-core#29331 |
So I believe the issue is only with https://github.com/compass-rs/sass-rs as libsass uses global, which Rust seems to have issues with. Should we move this issue there? |
Closing in favour of the issue in sass-rs linked above |
I'm trying to build a docker image providing a statically linked musl binary of gutenberg (v0.3.3). This way the final docker image could contain only the static binary by using
FROM scratch
.Here's the dockerfile:
Built and ran like this:
docker build . -t gutenberg:v0.3.3 && docker run -it --rm gutenberg:v0.3.3
Right now it does not work. I've facing some issues.
First issue is the following:
I'm not sure to understand this error. I was able to bypass it by running
cargo update
. Here's the resulting lock file: Cargo.lock.txtCould a release be done with updated dependencies? I guess that should fix this problem.
Secondly, I get a linking error if I try to link to musl (
cargo build --release --target=x86_64-unknown-linux-musl
):Could rust-lang/rust#50105 be related?
Thanks!
The text was updated successfully, but these errors were encountered: