diff options
| author | bors <bors@rust-lang.org> | 2022-03-13 23:06:14 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2022-03-13 23:06:14 +0000 |
| commit | 737ef08ea066cbdc9f4b93373b1a1a108e6691ab (patch) | |
| tree | 9586a01dca3120c02f47131874d31bcb06a2776c /compiler/rustc_codegen_llvm/src | |
| parent | e95b10ba4ac4564ed25f7eef143e3182c33b3902 (diff) | |
| parent | ca82e6cf18bb0f7765a978229f4899c33c5fdc7d (diff) | |
| download | rust-737ef08ea066cbdc9f4b93373b1a1a108e6691ab.tar.gz rust-737ef08ea066cbdc9f4b93373b1a1a108e6691ab.zip | |
Auto merge of #94832 - jonhoo:default-static, r=Mark-Simulacrum
bootstrap: untangle static-libstdcpp & llvm-tools Previously, the static-libstdcpp setting was tied to llvm-tools such that enabling the latter always enabled the latter. This seems unfortunate, since it is entirely reasonable for someone to want to _not_ statically link stdc++, but _also_ want to build the llvm-tools. This patch therefore separates the two settings such that neither implies the other. On its own, that would change the default behavior in a way that's likely to surprise users. Specifically, users who build llvm-tools _likely_ want those tools to be statically compiled against libstdc++, since otherwise users with older GLIBCXX will be unable to run the vended tools. So, we also flip the default for the `static-libstdcpp` setting such that builds always link statically against libstdc++ by default, but it's _possible_ to opt out. See also #94719.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions
