[MacPorts] #56093: compiler-blacklist-versions: simplify clang blacklisting by associating Apple clang versions with macports-clang versions

MacPorts noreply at macports.org
Mon Mar 19 14:26:01 UTC 2018


#56093: compiler-blacklist-versions: simplify clang blacklisting by associating
Apple clang versions with macports-clang versions
--------------------------+-----------------
  Reporter:  kencu        |      Owner:
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:
Resolution:               |   Keywords:
      Port:  clang        |
--------------------------+-----------------
Changes (by ryandesign):

 * cc: ryandesign (added)


Comment:

 That could be helpful, but how would you determine which non-Apple clang
 version corresponds to which Apple clang build number? Apple used to
 publish an approximate equivalence in the version string (so for example
 Apple clang 602.0.53 from Xcode 6.4 was "based on LLVM 3.6.0svn"), but
 they stopped doing that in Xcode 7.

 Also, Apple doesn't release Xcode on the same schedule as the developers
 of clang release their versions. So clang 602.0.53 is based on a
 development version of clang sometime after the release of clang 3.5 but
 before the release of 3.6. So if your program requires "clang 3.6 or
 newer", how do you know whether 602.0.53 was far enough along in the
 development cycle of clang 3.6 to have the required feature or not? It
 might vary from program to program, as each program has different reasons
 for requiring newer versions of clang.

--
Ticket URL: <https://trac.macports.org/ticket/56093#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list