In reply to @emilazy:matrix.org
looks like a temporary hack. hopefully we can get rid of it. but it looks like it might be conditioning on a non-libgcc_s runtime library maybe

In reply to @emilazy:matrix.org
well, still. you can throw Clang + libstdc++, Clang + libc++, etc. at them and narrow it down. (I forget if GCC + libc++ is possible)

In reply to @rosscomputerguy:matrix.org
Gotcha, so we can narrow it to the rtlib option instead of needing toolchain for this specific case?

In reply to @emilazy:matrix.org
but we should probably also wire up the variables we're adding... :)

Tristan Ross: if you want to land this incrementally, my recommendation is:

• add the new variables solely as output-only, i.e., derive them from the existing useLLVM etc. and assert that they are not set to anything contradicting those
• get rid of everything that looks at useLLVM and so on in-tree, making them use the more precise variables instead
• make sure the bootstrap respects them and everything is wired up correctly (this should mostly be a matter of fixing existing conditionals on things like useLLVM to determine what C++ library to set up and so on, I think; the various Clang stdenvs should help there)
• then, allow the variables to vary freely and start the deprecation of useLLVM etc.