[MacPorts] #69446: gcc13-libcxx cumbersomeness

[MacPorts]

#69446: gcc13-libcxx cumbersomeness
-------------------------+--------------------
 Reporter:  RJVB         |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  Normal       |  Milestone:
Component:  ports        |    Version:
 Keywords:               |       Port:  gcc13
-------------------------+--------------------
 Checking in on port:GCC developments I am pleased to see that a patch very
 similar to the one I wrote to add `-stdlib=` functionality to GCC7 made it
 into the offical sources. (I have yet to check if it also makes libc++ the
 default on new-enough OS X.)

 I have to wonder though why there's such a cumbersome libc++ header file
 construct. Why make another copy of the headers from a derived clang
 compiler (it seems to me the reproducible-build principle is thrown
 overboard with the way that subport currently works) if there's already
 `port:libcxx`? Why not simply point GCC (and its build process) to that
 directory so it will see any upgrades of that libc++ version as one would
 expect?

 /methinks it should also be possible to configure GCC to use the system
 libc++ headers by default on new-enough OS versions - my old custom
 port:gcc7 found them with `file dir [exec xcrun --find
 clang]]/../include/c++/v1` .

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