-
Notifications
You must be signed in to change notification settings - Fork 77
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
Failed to build zlib-ng with gnullvm target. #153
Comments
CI doesn't seem to reproduce the issue in particular as it can't find the toolchain in the first place: https://github.com/rust-lang/libz-sys/actions/runs/6062781035/job/16449371625?pr=154. Do you have any hints on how to reproduce this issue? The toolchain isn't tested here BTW, and once CI can reproduce the failure there is a chance for a fix, too. It would probably have to be contributed though. |
I build my project via
The x86_64-pc-windows-gnullvm target is in Tier 3 and no std is prebuilt. |
And I use https://github.com/mstorsjo/llvm-mingw as cross compile toolchains, it should be available via MSYS2 also. |
Thanks! This seems to be the explanation why CI can't get ahold of this toolchain (and that I have never seen it). I don't know if there is any policy of which tiers this crate aims to support, but I think none of the supported targets are not prebuilt. With that said, I am happy to keep this open as tracking ticket, but would hope that CI support for it could be added so potential fixes can be validated. Reproducing this on CI seems expensive, maybe even prohibitive, on a 2 core VM so supporting this toolchain while in tier 3 might not be feasible for that reason alone. |
I will try to fix it by myself but I have no idea how to fix it... |
This issue should no longer happen in latest version of this crate due to an upstream fix: zlib-ng/zlib-ng@1c1e728 |
The text was updated successfully, but these errors were encountered: