[MacPorts] #52424: Ports that depend on old llvm versions should be updated

MacPorts noreply at macports.org
Tue Sep 27 22:32:43 CEST 2016


#52424: Ports that depend on old llvm versions should be updated
-------------------------------------------------+-------------------------
  Reporter:  mf2k@…                              |      Owner:  macports-
      Type:  enhancement                         |  tickets@…
  Priority:  Normal                              |     Status:  new
 Component:  ports                               |  Milestone:
Resolution:                                      |    Version:
      Port:  faust2-devel ghc julia pure py-     |   Keywords:
  llvmlite py-llvmpy                             |
-------------------------------------------------+-------------------------

Comment (by ryandesign@…):

 Replying to [comment:6 aggraef@…]:
 > Pure certainly isn't dead, I just haven't gotten around porting it to
 LLVM 3.6+ yet. It should work fine with LLVM 3.5, though.
 >
 > This will also affect all LLVM applications which still rely on the old
 JIT rather than the new MCJIT of LLVM (of which there are still a few at
 least in Linux, not so sure about macOS). That's also why LLVM 3.5 ist
 still supported, e.g., on Arch Linux, along with the latest LLVM version.
 I'd suggest that MacPorts do the same, if possible. Otherwise supporting
 Pure on macOS will become *very* hard until it's ported to LLVM 3.6+
 (which isn't trivial because of architectural changes in the LLVM JIT,
 otherwise I would have done it long ago).
 >
 > Anyway, the executive summary is: I will try to port Pure to LLVM 3.6+
 asap, but I'd appreciate it if MacPorts could have LLVM 3.5 stick around a
 little while until it's done.

 The reason for this ticket is probably the fact that llvm < 3.7 does not
 build on macOS Sierra. I don't imagine there are any plans to remove llvm
 < 3.7 for previous verisons of OS X, but also probably no plans to make
 llvm < 3.7 work on Sierra.

 I think the reason why I did not update the port to llvm 3.5 is that that
 llvm 3.5 and later requires libc++, which is a bit problematic on OS X <
 10.9 where libc++ is not the default and much more problematic on Mac OS X
 < 10.7 where libc++ is not present. Perhaps by now support for older OS
 versions is less important.

-- 
Ticket URL: <https://trac.macports.org/ticket/52424#comment:8>
MacPorts <https://www.macports.org/>
Ports system for the Mac operating system


More information about the macports-tickets mailing list