[MacPorts] #58493: cctools: using clang < 5.0 as default assembler generates assembly errors in some cases

[MacPorts]

#58493: cctools: using clang < 5.0 as default assembler generates assembly errors
in some cases
----------------------+----------------------
  Reporter:  kencu    |      Owner:  jeremyhu
      Type:  defect   |     Status:  assigned
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:
Resolution:           |   Keywords:
      Port:  cctools  |
----------------------+----------------------

Comment (by cjones051073):

 Replying to [comment:27 mouse07410]:
 > > We do want to continue having a method for people using MacPorts to
 test out the new assembler in a new version of {{{clang}}}, though
 >
 > Understood and agreed.
 >
 > However, we're discussing what should be the default, not what should be
 possible. And in my opinion, it should be **possible** to configure
 {{{cctools}}} to use whatever installed version of {{{clang}}} you want to
 point it at - but it should **not** install another version of {{{clang}}}
 unless I **explicitly** ask for it.

 As I have already stated, cctools *never* declares any dependency on any
 clang version, for reasons of doing so would create a circular dependency
 issue. What it does, and will continue to do in the future, is at runtime
 check to see what is installed at that time, and decide what to use based
 on the outcome of this check. The proposal is simply to instead of only
 looking for the specific clang version corresponding to the llvm version
 used to build the port, allow a range of 'good' clang versions. based on
 what I have seen, that list I think would be '[8,7,6,5]' in that order of
 preference. So use the most recent 5+ clang version that is available.

 The devel clang port is an interesting question. My first though was to
 not include this in the list above (where would you put it ? first ? last
 ?) but perhaps it should be a special case, so if the user decides they
 want cctools installed with the devel llvm variant, then force this to be
 the (only) clang version considered, on the basis they are doing this for
 some specific non-standard reason.... Thoughts ?

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