You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That however is bad news because that means Swift prefers the clang that is first on $PATH instead of just using its own clang. So if somebody installs clang using their system package manager, Swift will use the wrong and possibly incompatible clang, probably breaking the sanitizers and god knows what else in the process.
The text was updated successfully, but these errors were encountered:
Additional Detail from JIRA
md5: 8b4a3fc63dd815917cf0b5a8884152d7
Issue Description:
Here's a one-shot command to use the official ubuntu18.04 docker image, install Swift and try to compile swift-nio-ssl:
Instead of succeeding, the build fails with
because Swift can't its own
clang
that it ships. This problem can be easily resolved by doingThat however is bad news because that means Swift prefers the clang that is first on
$PATH
instead of just using its own clang. So if somebody installsclang
using their system package manager, Swift will use the wrong and possibly incompatible clang, probably breaking the sanitizers and god knows what else in the process.The text was updated successfully, but these errors were encountered: