[MacPorts] #54766: Does port:clang*'s libstdcxx have to be default?

[MacPorts]

#54766: Does port:clang*'s libstdcxx have to be default?
----------------------------------+---------------------------------
  Reporter:  RJVB                 |      Owner:  MarcusCalhoun-Lopez
      Type:  defect               |     Status:  assigned
  Priority:  Normal               |  Milestone:
 Component:  ports                |    Version:
Resolution:                       |   Keywords:
      Port:  clang-4.0 clang-5.0  |
----------------------------------+---------------------------------

Comment (by RJVB):

 Replying to [comment:18 MarcusCalhoun-Lopez]:

 > There are a few things, however, that I need to look into before making
 the change.
 > 1. If GCC is **not** installed, does {{{-stdlib=macports-libstdc++}}}
 cause a compile-time error or silently do the wrong thing?

 As far as I can tell your patch uses a hardcoded full path to the MacPorts
 libstdc++ . That should fail if the library isn't there.

 > 1. To avoid multiple recompilations of clang, can {{{-stdlib=macports-
 libstdc++}}} now use gcc7 header files?

 It looks like gcc7 was finally bumped to the current 7.2 release which
 means that libgcc is now also at 7.2.0 . I think that means you *have* to
 use those.

 Let me reiterate my suggestion to move the libstdc++ headerfiles into
 libgcc - what do you think Jeremy?

 That's a separate ticket of course and shouldn't require clang rebuilds. I
 can try to look into that as part of my tinkering with the gcc7 port.

--
Ticket URL: <https://trac.macports.org/ticket/54766#comment:19>
MacPorts <https://www.macports.org/>
Ports system for macOS