[MacPorts] #61967: cctools @927.0.2: not fully compatible with llvm11 Unknown command line argument '-macho'.

[MacPorts]

#61967: cctools @927.0.2: not fully compatible with llvm11  Unknown command line
argument '-macho'.
----------------------+----------------------
  Reporter:  blair    |      Owner:  jeremyhu
      Type:  defect   |     Status:  closed
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:
Resolution:  fixed    |   Keywords:
      Port:  cctools  |
----------------------+----------------------

Comment (by kencu):

 So -- why?

 a lot of scripts, and people, use otool. otool is binary driver for llvm-
 objdump. otool has compiled into it the flags for llvm-objdump that map to
 the old otool flags. It translates the flags, then calls llvm-objdump.

 but the flags that llvm-objdump accepts have changed, and otools now adds
 flags that llvm-objdump in llvm11 does not support, ergo the errors.

 It's not just one -- there are a whole bunch of them.

 And, perhaps more such issues, in other parts of cctools. This is the only
 one we've found so far. The newer version of cctools that is out there,
 949, has the same issues, and it has not been fixed there yet either. No
 doubt some newer open source version of cctools will be coming out
 eventually that does support the newer llvm calling conventions.

 Now sure, I could take a stab at patching otool to accept all the new
 flags. One or two, easy -- but there are lots. And maybe more? And maybe
 in other tools?

 There is no good reason to cause this grief upon our users. AFAIK, llvm-10
 was OK, and that makes sense, timeline wise... cctools is about that
 vintage.

 So we will have most users on newer systems using cctools +xcode, as they
 should be using. And we'll make available llvm10, as that was not visibly
 broken.

 And for those few users out there who really want the newest, know what
 they are doing, and can hack in on it -- cctools +llvmdev is still
 available.

 I'll re-enable cctools +llvm11 when it works properly.

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