Upgrading windows-targets
from v0.48.1 to v0.48.2 breaks build on pc-windows-gnu
#2642
Labels
question
Further information is requested
Summary
This is a weird one, so sorry if I'm ruining your day just now.
I was performing a routine
cargo update
in my open-source project which resulted in the build pipeline failing on thei686-windows-pc-gnu
andx86_64-windows-pc-gnu
targets. The error is a gigantic trace of the linker flipping its junk over unrecognised.drective --exclude-symbols:
and corrupt.drective
at end of file. You can see the workflow run here, or the full raw logs (Test matrix (stable, x86_64-pc-windows-gnu-nosimd).zip), see12_Build without simd
for the error) . Here's the head and tail of that log:The error is way above my paygrade. It happens during the compilation of
clap
, because that's the path to thewindows-targets
dependency in my project:rsonpath v0.6.1 ├── clap v4.4.2 │ ├── clap_builder v4.4.2 │ │ ├── anstream v0.5.0 │ │ │ ├── anstyle-query v1.0.0 │ │ │ │ └── windows-sys v0.48.0 │ │ │ │ └── windows-targets v0.48.5 │ │ │ │ └── windows_x86_64_gnu v0.48.5 [Test matrix (stable, x86_64-pc-windows-gnu-nosimd).zip](https://github.com/microsoft/windows-rs/files/12502114/Test.matrix.stable.x86_64-pc-windows-gnu-nosimd.zip)
Unfortunately this is about everything I am able to pin down. I wasn't able to replicate this issue independently. Creating a crate that references
clap
and building it, even using the same CLI interface as in my project but with the logic removed, does not reproduce the issue.On my machine and in the GitHub runner, checking out the latest stable commit of https://github.com/V0ldek/rsonpath.git (
62a65f5b085785322c942e5f9e321c29639f1a08
), runningcargo update -p windows-targets
and thencargo build --target
fails with the error above. Note that both me and the host runner are running Windows. On the other hand, when running the same steps in a cleanubuntu:latest
Docker container the issue does not occur.In any case, on a Windows machine the following steps seem to reproduce the issue:
I know that this report is scarce in repro details, but I really am at a stump as to how to find the root cause. Any help is appreciated, please let me know what details I could provide to assist with this.
The text was updated successfully, but these errors were encountered: