multiple ports with stdlibc++ mismatches (all on 10.13)...

[Ryan Schmidt]

On May 31, 2018, at 00:39, Ken Cunningham wrote:

> pbzip2 is using libstdc++ (this installation is configured to use libc++)
> dylibbundler is using libstdc++ (this installation is configured to use libc++)
> lzma is using libstdc++ (this installation is configured to use libc++)
> SuiteSparse is using libstdc++ (this installation is configured to use libc++)
> starfighter is using libstdc++ (this installation is configured to use libc++)
> darwinbuild is using libstdc++ (this installation is configured to use libc++)
> pdftk is using libstdc++ (this installation is configured to use libc++)
> 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++)


Each port is going to need to be investigated and fixed in its own unique way, so an individual ticket should be filed for each port (or each group of ports). It may be quicker just to try to fix them and commit them without tickets. pdftk already has a ticket.