-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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 1.30.0's linker flavor inference is a non-backwards compat change to -Clinker #55396
Comments
Oh dear, sorry for the breakage! I think there's probably a few things we can do to help mitigate this:
@jsgf does it work for now for y'all to rename to Also, cc @japaric |
The script is currently called |
@jsgf ah yeah the heuristic includes looking for |
triage: P-high. |
assigning to @nagisa to take point on moving forward on how we're going to address this |
…ension, r=nagisa rustc 1.30.0's linker flavor inference is a non-backwards compat change to -Clinker Part of rust-lang#55396. This commit modifies linker flavor inference to only remove the extension to the linker when performing inference if that extension is a 'exe'. r? @nagisa cc @alexcrichton @japaric
…ension, r=nagisa rustc 1.30.0's linker flavor inference is a non-backwards compat change to -Clinker Part of rust-lang#55396. This commit modifies linker flavor inference to only remove the extension to the linker when performing inference if that extension is a 'exe'. r? @nagisa cc @alexcrichton @japaric
…ension, r=nagisa rustc 1.30.0's linker flavor inference is a non-backwards compat change to -Clinker Part of rust-lang#55396. This commit modifies linker flavor inference to only remove the extension to the linker when performing inference if that extension is a 'exe'. r? @nagisa cc @alexcrichton @japaric
…ker-flavor, r=nagisa Stabilize `linker-flavor` flag. Part of rust-lang#55396. This commit moves the linker-flavor flag from a debugging option to a codegen option, thus stabilizing it. There are no feature flags associated with this flag.
T-compiler triage. PR #56351 landed, so closing this as fixed. |
Thanks everyone! |
In our environment we end up setting
-Clinker
to a script calledld.sh
; this script is implemented in terms ofgcc
asrustc
used to expect. Now it treats it as a direct invocation ofld
.This was introduced in #52101.
I think rather than inferring the linker flavor from the name of the executable, rustc should either:
-Clinker-flavor
option to set it explicitlyThere's an unstable -Zlinker-flavor option, which I think should have been stabilized at the same time as flavor inference. Ideally inference should be opt-in with
-Clinker-flavor=infer
, with the default being the old default of-Clinker-flavor=gcc
(at least for Linux platforms).The text was updated successfully, but these errors were encountered: