about summary refs log tree commit diff
path: root/compiler/rustc_interface/src
diff options
context:
space:
mode:
authorStuart Cook <Zalathar@users.noreply.github.com>2024-09-14 11:53:11 +1000
committerGitHub <noreply@github.com>2024-09-14 11:53:11 +1000
commit2bf0dd2735d0165a95036594f5f900a12217f6a0 (patch)
tree2cb76432232ae104195dc7281989fc47c0b7b197 /compiler/rustc_interface/src
parent507c05bead4026ed8841512095b4218119eb479f (diff)
parenta21f39522c8d5776f5baa6ead22c1dbb13e56820 (diff)
downloadrust-2bf0dd2735d0165a95036594f5f900a12217f6a0.tar.gz
rust-2bf0dd2735d0165a95036594f5f900a12217f6a0.zip
Rollup merge of #130138 - Zalathar:initial-libdir, r=albertlarsan68
bootstrap: Print more debug info when `find_initial_libdir` fails

From looking at the failure messages printed by #129775, my hypothesis is that `rustc --print=sysroot` sometimes prints the wrong path when the rustc executable is hardlinked in multiple places, at least on my macOS system.

However, currently I don't have any concrete evidence of this actually happening. This PR therefore expands on #129775 by printing even more information on failure (including the actual rustc path), in the hope that when the failure next occurs we can confirm or reject the hypothesis that `rustc --print=sysroot` is printing the wrong path.
Diffstat (limited to 'compiler/rustc_interface/src')
0 files changed, 0 insertions, 0 deletions