[MacPorts] #62426: libc++: using a newer libc++ to build software on older macos systems

[MacPorts]

#62426: libc++: using a newer libc++ to build software on older macos systems
-------------------------------------+----------------------
  Reporter:  kencu                   |      Owner:  kencu
      Type:  enhancement             |     Status:  assigned
  Priority:  Normal                  |  Milestone:
 Component:  ports                   |    Version:
Resolution:                          |   Keywords:
      Port:  libcxx macports-libcxx  |
-------------------------------------+----------------------

Comment (by kencu):

 Replying to [comment:21 Wowfunhappy]:
 > Replying to [comment:16 kencu]:
 > > I will start by saying I'm still learning too.

 > Is this something two-level name-spacing can help with, or would that be
 too large a change?

 As an example of the "I'm still learning too." I have recently come across
 information that suggests that two libraries with the same name but with
 different install names (paths) might indeed be separated by the system
 via two-level namespaces.

 If so, that could turn out to be helpful for us here, and make the chances
 of confusion (crashes) a bit lower.

 We still see crashes in the libstdc++.dylib world mixing dylibs, so it's
 still open for experimentation/validation just where it might be an issue.

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