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
Apple Clang version numbering doesn't match the open source project. Typically it's a full major version ahead. This is why the configure script currently allows for 4.1* and 4.2*. However, this isn't particularly future-proof. The configure script should instead learn to use the "based on" version when present, because this describes what the open source version is. For example, the version string looks something like "Apple LLVM version 4.2 (clang-421.2.1) (based on LLVM 3.2svn)".
The text was updated successfully, but these errors were encountered:
Here's a new version of the sed command that should produce the "based on" version when the version string contains it: sed 's/.*\(version .*\)/\1/; s/.*based on \(LLVM .*\))/\1/'
lilyball
added a commit
to lilyball/rust
that referenced
this issue
May 25, 2013
Apple Clang uses different version numbering than "regular" clang, but
it also provides the "regular" version it's based on. Update the sed
pattern to pull out this "regular" version number instead of the Apple
version number.
Apple Clang version numbering doesn't match the open source project. Typically it's a full major version ahead. This is why the configure script currently allows for
4.1*
and4.2*
. However, this isn't particularly future-proof. The configure script should instead learn to use the "based on" version when present, because this describes what the open source version is. For example, the version string looks something like "Apple LLVM version 4.2 (clang-421.2.1) (based on LLVM 3.2svn)".The text was updated successfully, but these errors were encountered: