Closed
Description
This test is either new or changed recently, it now fails when using -Clinker=lld-link
Example build failure on Chromium CI: https://logs.chromium.org/logs/chromium/buildbucket/cr-buildbucket/8781936910784713969/+/u/package_rust/stdout
diff of stderr:
- error: linking with `link.exe` failed: exit code: 1181
+ error: linking with `C:\b\s\w\ir\cache\builder\src\third_party\rust-toolchain-intermediate\llvm-host-install\bin/lld-link` failed: exit code: 1
2 |
- = note: LINK : fatal error LNK1181: cannot open input file 'märchenhaft.obj'
+ = note: lld-link: error: could not open 'märchenhaft': no such file or directory
4
5
6 error: aborting due to previous error
The test has link.exe error messages hardcoded into it, which are wrong when not using link.exe.
We can disable this test when not using link.exe but it would be much better to make the error checking more flexible or explicitly define an output for ldd-link.
How would one go about the latter?
Metadata
Metadata
Assignees
Labels
No labels