-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Fix passing MACOSX_DEPLOYMENT_TARGET to the linker #105123
Fix passing MACOSX_DEPLOYMENT_TARGET to the linker #105123
Conversation
r? @oli-obk (rustbot has picked a reviewer for you, use r? to override) |
These commits modify compiler targets. |
This comment has been minimized.
This comment has been minimized.
6af3f42
to
fde09c1
Compare
@rustbot label O-macos |
@thomcc @petrochenkov do you want to have a look at this considering you reviewed the original PR? |
fde09c1
to
b5fa9af
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple concerns with the regression test but otherwise looks good. Sorry that I missed this issue initially.
b5fa9af
to
56592d3
Compare
@bors r+ |
…iaskrgr Rollup of 4 pull requests Successful merges: - rust-lang#104856 (Don't suggest associated function call for associated const.) - rust-lang#105123 (Fix passing MACOSX_DEPLOYMENT_TARGET to the linker) - rust-lang#105142 (Make inline const block `ExprWithBlock`) - rust-lang#105237 (Add regression test for rust-lang#79450) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
I messed up in #103929 when merging the two base files together and as a result, started ignoring
MACOSX_DEPLOYMENT_TARGET
at the linker level. This ended up being the cause of nighty builds not running on older macOS versions.My original hope with the previous PR was that CI would have caught something like that but there were only tests checking the compiler target definitions in codegen tests. Because of how badly this sucks to break, I put together a new test via
run-make
that actually confirms the deployment target set makes it to the linker instead of just LLVM.Closes #104570 (for real this time)