[MacPorts] #56577: Broken gcc7 port?
MacPorts
noreply at macports.org
Sat Jun 2 01:33:24 UTC 2018
#56577: Broken gcc7 port?
---------------------------+--------------------
Reporter: thiagoveloso | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: base | Version: 2.5.0
Resolution: | Keywords:
Port: gcc7 |
---------------------------+--------------------
Changes (by ryandesign):
* component: ports => base
Comment:
You don't need to worry about the error. MacPorts 2.5.0 introduced a new
feature that checks for C++ standard library mismatches. Ports that
display this error are no more broken than they were before: the mismatch
always existed, but MacPorts wasn't checking for it before.
gcc7 does intentionally use a different C++ standard library, and it
indicates that in the Portfile, so in fact there is no mismatch. But our
binary archive of gcc7 dates from before the release of MacPorts 2.5.0 and
therefore does not contain that information, so MacPorts doesn't know that
the use of the different C++ standard library in this port is intentional.
If gcc7 had already been installed when you upgraded to MacPorts 2.5.0,
you would not have seen this error, because the MacPorts 2.5.0 upgrade
process fixes up the values of any of your installed ports that are known
to use a different C++ standard library. But installing or upgrading gcc7
after upgrading to MacPorts 2.5.0 will cause the problem to appear.
See: https://lists.macports.org/pipermail/macports-
dev/2018-June/039046.html
This bug will be fixed in MacPorts 2.5.1. The problem would also disappear
if we happened to make a new version or revision of gcc7 available.
--
Ticket URL: <https://trac.macports.org/ticket/56577#comment:4>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list