-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rustc --verbose does not print linker invocation #36175
Comments
It does not on Linux either. |
AFAIK this has never been the behavior, so I'm not sure this is a bug but rather a feature request? |
@alexcrichton Hm, I kind of assumed that it should be already the case, since cargo as well as basically every other compiler toolchain in existence respects this convention. But I guess this is a feature request, yes. |
FWIW, you can use |
I haven't been able to figure out how to get the ld linker to be verbose when using Cargo. Any ideas? |
@ctaggart use
|
I'm going to close this in favor of #38206 which suggests we print both invocations and output. |
Note that the |
@wez rustc doesn't invoke the linker when producing a staticlib, at least not on Linux. (libfoo.a is just an archive of object files; rustc uses the built-in LLVM |
Right... my point is that it is impossible to see what is being run. It’s super frustrating on macOS where dtrace is hobbled; there’s no easy way to snoop this sort of thing at a system level |
And -Z only works on the nightly compiler, not on stable. |
To reproduce:
This might be an OS X-specific bug, I have not tried 1.13 on any other OS.
The text was updated successfully, but these errors were encountered: