[MacPorts] #58441: "port upgrade libgcc8" pulls libgcc9 instead (and fails, of course). Also affects gcc8 port
MacPorts
noreply at macports.org
Wed May 8 15:09:54 UTC 2019
#58441: "port upgrade libgcc8" pulls libgcc9 instead (and fails, of course). Also
affects gcc8 port
-------------------------+--------------------
Reporter: mouse07410 | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: libgcc8 |
-------------------------+--------------------
Comment (by kencu):
The way this is set up now, the port people should be installing (and the
one that is dependencied in other ports) is `libgcc`.
`libgcc` is a meta-port. It installs the latest version of `libgcc` that
should be installed on a given system (depending on the system's
capabilities), and it also can install certain bits of libgcc6,7,or8 that
are needed for MacPorts but no longer available in the latest `libgcc`
version, which is presently `libgcc9`.
It *is* getting more complicated, to be sure, and there have been some
hiccups in birthing here and there, but Chris is doing a great job at
keeping this all working, for the most part.
The reason you're seeing `libgcc8` having a runtime dep on `libgcc9` is
that `libgcc8` is incomplete on many systems, and needs `libgcc9` to fill
in the rest of the required parts to make a whole `libgcc` installation.
--
Ticket URL: <https://trac.macports.org/ticket/58441#comment:4>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list