[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:
      Type:  defect               |     Status:  new
  Priority:  Normal               |  Milestone:
 Component:  ports                |    Version:
Resolution:                       |   Keywords:
      Port:  clang-4.0 clang-5.0  |
----------------------------------+-----------------

Comment (by RJVB):

 Just to add another thing to consider for those who need extra convincing:
 it's a bit curious that installing clang also causes gcc to be installed.

 > However, I guess we need to rev-bump all orts using the cxx11 port
 group, as this might change the dependencies.

 Would it? I don't think there's a big risk that libgcc will be uninstalled
 automatically just because of this change. It'd be nice too to revbump
 only the ports that set configure.cxx_stdlib to libstdc++ (use `-libstdc
 =macports-libstdc++`).

 FWIW, your patch should probably do this to keep overhead lowest:

 {{{
     depends_build-append port:gcc6
     depends_lib-append port:libgcc
 }}}

 Come to think of it: `port:gccN` is required here only because of the C++
 headers.
 Those could (probably) very well be moved to `port:libgcc`, which would
 remove the need for depending on the full gcc package.

 BTW, is there a patch that makes gcc accept `-stdlib=macports-libstdc++`,
 or should that argument really only be set when using clang?


 (It probably also be a good idea if there were a gcc PG, to avoid having
 to hardcode the current default gcc port "everywhere".)

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