about summary refs log tree commit diff
path: root/compiler/rustc_codegen_llvm/src
diff options
context:
space:
mode:
authorJon Gjengset <jongje@amazon.com>2022-03-09 12:06:12 -0800
committerJon Gjengset <jongje@amazon.com>2022-03-10 18:04:38 -0800
commitca82e6cf18bb0f7765a978229f4899c33c5fdc7d (patch)
treee80839e7e2670212f693880f403edd95b3b78034 /compiler/rustc_codegen_llvm/src
parent352e621368c31d7b4a6362e081586cdb931ba020 (diff)
downloadrust-ca82e6cf18bb0f7765a978229f4899c33c5fdc7d.tar.gz
rust-ca82e6cf18bb0f7765a978229f4899c33c5fdc7d.zip
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