multiple ports with stdlibc++ mismatches (all on 10.13)...
jmr at macports.org
Fri Jun 1 21:44:14 UTC 2018
On 2018-6-2 06:09 , Rainer Müller wrote:
> On 2018-05-31 17:39, Rainer Müller wrote:
>> On 2018-05-31 16:49, Ken Cunningham wrote:
>>> On 2018-05-30, at 11:04 PM, Joshua Root wrote:
>>>> On 2018-5-31 15:39 , Ken Cunningham wrote:
>>>>> gcc5 is using libstdc++ (this installation is configured to use libc++)
>>>>> gcc6 is using libstdc++ (this installation is configured to use libc++)
>>>>> gcc7 is using libstdc++ (this installation is configured to use libc++)
>>>> Did cxx_stdlib_overridden.tcl not set these up right for you?
>>> It appears it should have...
>>> I may have some inconsistency in my local MacPorts' database.
>> Were you running master at some point on this installation? This might
>> be what I described in the following ticket, but was subsequently fixed
>> on master. However, any installation that was converted with master
>> before the fix will be left in this state.
> Hm, have the gcc* ports been rev-bumped after the release of 2.5.0?
> The problem could be that the archives do not contain any cxx_stdlib.
> The cxx_stdlib_overridden.tcl script helps upgrading users, but those
> that install the port from the archive will experience the same problem
> I reported in that ticket.
Ah, that's true. That was an unfortunate oversight, as
cxx_stdlib_overridden can be derived from the Portfile when installing.
More information about the macports-dev