[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:  closed
  Priority:  Normal                  |  Milestone:
 Component:  ports                   |    Version:
Resolution:  fixed                   |   Keywords:
      Port:  libcxx macports-libcxx  |
-------------------------------------+--------------------

Comment (by kencu):

 Replying to [comment:50 RJVB]:

 > Either you missed what I wrote

 I did have trouble following it, probably my fault.

 You are saying if you have executable A linked against
 {{{${prefix}/lib/newlibc++.dylib}}} and
 {{{${prefix}/lib/libMyLib.dylib}}}, and

 {{{${prefix}/lib/libMyLib.dylib}}} is linked against
 {{{/usr/lib/libc++.dylib}}}

 then you see that {{{${prefix}/lib/libMyLib.dylib}}} never brings
 {{{/usr/lib/libc++.dylib}}} into play.... ?

 I just can't follow how that would be, so would have to verify that
 myself. Kinda doubt it, though, without proving it wrong. Goes against the
 laws of physics.

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