We no longer support the -static-stdlib flag on Darwin, so we should reject attempts to use that flag on Darwin builds and remove support for it from toolchains::Darwin.
Doing this properly will require us to add a way for the ToolChain subclass to examine the arguments during validateArgs() so that Darwin can diagnose an error if it sees OPT_static_stdlib. After that, toolchains::Darwin::constructInvocation(StaticLinkJobAction) should be rewritten to assume OPT_static_stdlib is false, and its sibling methods should be audited to see if they should change too. This shouldn't be very difficult, but it's not trivial enough for me to do right away.
The text was updated successfully, but these errors were encountered:
Additional Detail from JIRA
md5: 00cbbc767c45833f8ad81fcad017d1a2
Issue Description:
We no longer support the
-static-stdlib
flag on Darwin, so we should reject attempts to use that flag on Darwin builds and remove support for it fromtoolchains::Darwin
.Doing this properly will require us to add a way for the
ToolChain
subclass to examine the arguments duringvalidateArgs()
so that Darwin can diagnose an error if it seesOPT_static_stdlib
. After that,toolchains::Darwin::constructInvocation(StaticLinkJobAction)
should be rewritten to assumeOPT_static_stdlib
is false, and its sibling methods should be audited to see if they should change too. This shouldn't be very difficult, but it's not trivial enough for me to do right away.The text was updated successfully, but these errors were encountered: