[MacPorts] #59217: boost, graphite2, possibly other ports use macports-libstdc++ instead of libc++

[MacPorts]

#59217: boost, graphite2, possibly other ports use macports-libstdc++ instead of
libc++
-------------------------------------------+------------------------------
 Reporter:  ryandesign                     |      Owner:  (none)
     Type:  defect                         |     Status:  new
 Priority:  Normal                         |  Milestone:
Component:  ports                          |    Version:  2.6.1
 Keywords:  snowleopard lion mountainlion  |       Port:  boost, graphite2
-------------------------------------------+------------------------------
 At least on 10.8 (e.g.
 boost-1.71.0_0+no_single+no_static+python27.darwin_12.x86_64), boost is
 linked with MacPorts libstdc++, so of course programs that use libc++
 [https://build.macports.org/builders/ports-10.8_x86_64-builder/builds/1982/steps
 /install-port/logs/stdio fail to link with it].

 I don't understand why gcc got anywhere near this build.

 I have seen a similar problem on 10.6-10.8 with graphite2 (e.g.
 graphite2-1.3.13_0.darwin_12.x86_64.tbz2), and I don't understand why that
 happened either.

 It looks like these archives were not identified for deletion and rebuild
 during our switchover to libc++. Josh, do you know why?

-- 
Ticket URL: <https://trac.macports.org/ticket/59217>
MacPorts <https://www.macports.org/>
Ports system for macOS