Compile Error using Rust 1.95

[RNO-HMRKG]

Hello,
i've just updates rust to version 1.95 stable and am unable to compile any project containing the getrandom crate. I've just set up the default Hello World using cargo init . and added getrandom = "*" to the cargo.toml and get the same error.

Error:

PS C:\##\Code Workspace\rs_test> cargo run   
   Compiling cfg-if v1.0.4
   Compiling getrandom v0.4.2                                                                                                                                                                                             
error: dlltool could not create import library with C:\mingw64\bin\dlltool.exe -d C:\##\Code Workspace\rs_test\target\debug\deps\rustc5J9bR8\bcryptprimitives.dll_imports.def -D bcryptprimitives.dll -l C:\##\Code Workspace\rs_test\target\debug\deps\rustc5J9bR8\bcryptprimitives.dll_imports.lib -m i386:x86-64 -f --64 --no-leading-underscore --temp-prefix C:\##\Code Workspace\rs_test\target\debug\deps\rustc5J9bR8\bcryptprimitives.dll:
       
       Assembler messages:␍
       Error: can't open Workspace\rs_test\target\debug\deps\rustc5J9bR8\bcryptprimitives.dllh.o for reading: No such file or directory␍
       C:\##\Code: Error: can't open Workspace\rs_test\target\debug\deps\rustc5J9bR8\bcryptprimitives.dllh.s for reading: No such file or directory␍
       C:\mingw64\bin\dlltool.exe: C:\mingw64\bin\as exited with status 1␍
       C:\mingw64\bin\dlltool.exe: failed to open temporary head file: C:\##\Code Workspace\rs_test\target\debug\deps\rustc5J9bR8\bcryptprimitives.dllh.o: No such file or directory␍
       
error: could not compile `getrandom` (lib) due to 1 previous error  

The Update was from Rust 1.88 to 1.95. When downgrading back to 1.88 all works fine.

Last working Rust version is 1.93

System:
target x86_64-pc-windows-gnu
Win11 64-bit
Rust 1.95
gcc (mingw) 14.2.0

Thank You

[RNO-HMRKG]

This is likely related to some change in the buildpipeline from Rust 1.93 to 1.94.
rust-lang/rust#155591

[newpavlov]

IIUC we do the linking correctly on our side, so I think it's a toolchain problem and we should wait for resolution of the linked Rust issue. Either way, it's worth to keep this issue open until then to help others who encounter the same issue.