Closed Jake-Shadle closed 1 month ago
Thanks for your help!
Submodules are checked out on CI, yet the hardcoded file seems to be missing. I checked and it's available locally, strangely enough.
When trying the package commands locally, I also see two failures, both with zlib-ng
and zlib-ng-cc
. The build of zlib-ng-cc
also fails for me, but works for zlib-ng
.
I have a feeling there is a CWD difference between what cargo package
does and what cargo build
does - maybe one should use environment variables to get the manifest-root instead of relying on the CWD.
Here are my logs for completeness.
Opened a PR on cc to fix the issue I found when debugging the packaging, but for now the workaround works. https://github.com/rust-lang/cc-rs/pull/1072
Thank you! It's very strange that CI is now failing, it's probably flakiness due to the nightly GNU compiler, but at least today it reproduces when retrying. Maybe the easiest is to try again tomorrow hoping it's fixed by then.
Maybe it's related to this change? The timing would match: https://blog.rust-lang.org/2024/05/17/enabling-rust-lld-on-linux.html
cc 1.0.98 has released
Unfortunately the documented method of disabling either isn't functioning or there is something else going on. See also https://github.com/cross-rs/cross/issues/1496. It might be related to the LLD change, but if it is there is something wrong as targets other than x86_64-unknown-linux-gnu
are also affected, which shouldn't be the case according to the post.
I see, thanks for letting me know. Maybe a solution arises in the coming days/weeks, so we can finish this fix and finally bring CC-zlib-ng to the people :).
Upstream rust issue https://github.com/rust-lang/rust/issues/125330
The nightly upstream fix works and I removed the cc workaround.
Fantastic, let me create a new build right away, let's see if it works.
Resolves: #194