[MacPorts] #55705: adding new clang compilers:: why so painful?
MacPorts
noreply at macports.org
Wed Jan 17 05:51:22 UTC 2018
#55705: adding new clang compilers:: why so painful?
----------------------------+----------------------
Reporter: gaming-hacker | Owner: jeremyhu
Type: enhancement | Status: assigned
Priority: Normal | Milestone:
Component: base | Version: 2.4.2
Resolution: | Keywords:
Port: |
----------------------------+----------------------
Changes (by ryandesign):
* cc: jeremyhu (removed)
* status: new => assigned
* owner: => jeremyhu
* port: macports =>
* keywords: compiler, environment =>
Comment:
What compilers base uses for ports by default is completely separate from
what compilers individual ports such as ld64 might have variants for. Both
need to be updated separately.
Base uses compilers as specified in browser:macports-
base/src/port1.0/portconfigure.tcl. Looks like it hasn't been updated to
include clang-6.0 yet. And neither, as you've noticed, has ld64. I guess
that's because clang-6.0's existence is very recent, having just been
created twelve days ago.
Neither of these are particularly painful to update, someone just has to
do it.
--
Ticket URL: <https://trac.macports.org/ticket/55705#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list