[MacPorts] #60108: clang-devel is outdated.

MacPorts noreply at macports.org
Wed Feb 19 05:34:51 UTC 2020


#60108: clang-devel is outdated.
--------------------------+----------------------
  Reporter:  marka63      |      Owner:  jeremyhu
      Type:  update       |     Status:  assigned
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:
Resolution:               |   Keywords:
      Port:  clang-devel  |
--------------------------+----------------------

Comment (by kencu):

 the previous `llvm` `svn` access is now dead and gone, as I trust a good
 many of you might already know. The `*-devel` versions of `llvm`, `clang`,
 and `lldb` will therefore need a wholesale reconfiguration.

 It's probably time to build them all directly from the monorepo, all at
 once.

 We should now start to do the two-stage build as well, so we are not using
 a crippled clang/llvm setup built with the ancient clang-3.7 or something
 of a similar ilk.

 I received an email from the `libc++` lead indicating their new floor for
 building `libc++` will soon be 10.12, and that has to be built as part of
 llvm/clang at present, so that will need a workaround using parts of
 `legacysupport` I think, or at least borrowing the `gettime`
 implementation from there to get the build going.

 And finally, we have to sort out properly the name change from `macports-
 clang-N.0` to `macports-clang-N`, which sound trivial, but is unlikely to
 be so given how many ports I have seen that have tweaked compiler
 blacklisting based on certain tcl structures like:

 `compiler.blacklist-append {macports-clang-[3-8].0}` and such.

 Jeremy will possibly want to be involved in such a wholesale
 reconfiguration -- he's very busy these days. It will need plenty of
 testing.

 Long story short -- this will take some time.

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


More information about the macports-tickets mailing list