Uplift windows Cygwin DLL import libraries

[Berrysoft]

• needed to link std correctly

Related: rust-lang/rust#134999

[rustbot]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @weihanglo (or someone else) some time within the next two weeks.

Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (S-waiting-on-review and S-waiting-on-author) stays updated, invoking these commands when appropriate:

• @rustbot author: the review is finished, PR author should check the comments and take action accordingly
• @rustbot review: the author is ready for a review, this PR will be queued again in the reviewer's queue

[Berrysoft]

I don't think the CI failure is related to this PR's changes...

[weihanglo]

It looks like a regression in rustdoc in xcompile nightly feature (or a behavior change if that is intended).

This test::cargo_test_doctest_xcompile_ignores is affected:

• rustdoc 1.87.0-nightly (b48576b4d 2025-03-22) failed
• rustdoc 1.87.0-nightly (be73c1f46 2025-03-21) succeeded

And probably this PR rust-lang/rust#138535.

[weihanglo]

@Berrysoft could you rebase onto master so we can merge it?

[Berrysoft]

Rebased.

[Berrysoft]

A CI fails, because of stack overflow?

[weihanglo]

We had that in the past: #14312 (comment). No idea how. Let me re-run.

---- freshness::same_build_dir_cached_packages stdout ----
running `D:\a\cargo\cargo\target\debug\cargo.exe build`

thread 'freshness::same_build_dir_cached_packages' panicked at tests\testsuite\freshness.rs:818:10:

test failed running `D:\a\cargo\cargo\target\debug\cargo.exe build`
error: process exited with code 101 (expected 0)
--- stdout

--- stderr
     Locking 3 packages to latest compatible versions
   Compiling d v0.0.1 (D:\a\cargo\cargo\target\tmp\cit\t1713\foo\d)
   Compiling c v0.0.1 (D:\a\cargo\cargo\target\tmp\cit\t1713\foo\c)
   Compiling b v0.0.1 (D:\a\cargo\cargo\target\tmp\cit\t1713\foo\b)
   Compiling a1 v0.0.1 (D:\a\cargo\cargo\target\tmp\cit\t1713\foo\a1)

thread 'main' has overflowed its stack
error: could not compile `c` (lib)

Caused by:
  process didn't exit successfully: `rustc --crate-name c --edition=2015 D:\a\cargo\cargo\target\tmp\cit\t1713\foo\c\src\lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debuginfo=2 --check-cfg cfg(docsrs,test) --check-cfg "cfg(feature, values())" -C metadata=c5428bb539fd3662 -C extra-filename=-4a7368518b97c39c --out-dir D:\a\cargo\cargo\target\tmp\cit\t1713\foo\./target\debug\deps -L dependency=D:\a\cargo\cargo\target\tmp\cit\t1713\foo\./target\debug\deps --extern d=D:\a\cargo\cargo\target\tmp\cit\t1713\foo\./target\debug\deps\libd-4905d440739651d9.rmeta` (exit code: 0xc00000fd, STATUS_STACK_OVERFLOW)

[ehuss]

@weihanglo Do you happen to know what job that was? Was it msvc or gnu?

[weihanglo]

It was gnu: https://github.com/rust-lang/cargo/actions/runs/14074590524/job/39415190848?pr=15193#step:13:4455.