[MacPorts] #55351: Build libgccjit library as part of GCC port(s) or as separate port(s).
MacPorts
noreply at macports.org
Mon Nov 20 22:53:51 UTC 2017
#55351: Build libgccjit library as part of GCC port(s) or as separate port(s).
-----------------------------------+-----------------
Reporter: kstephens | Owner:
Type: enhancement | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: libgcc, libgcc-devel |
-----------------------------------+-----------------
Comment (by kstephens):
If it's in trunk, is that good enough for libcc-devel? The caveat emptor
is documented. Are there other GCC backends in trunk that are explicitly
excluded?
Maybe these are good reasons for a separate port dependent on the libgcc-
devel port?
--
Ticket URL: <https://trac.macports.org/ticket/55351#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list