[MacPorts] #62426: libc++: using a newer libc++ to build software on older macos systems
MacPorts
noreply at macports.org
Sat Apr 24 18:25:12 UTC 2021
#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 mascguy):
Replying to [comment:30 kencu]:
> you should not need to use any reexporting symbols tricks with this, and
no proxy libraries. Just change the clang++ includes and default libc++
with the minor flag tweaks, and have at 'er. Your mame port is probably an
early candidate, perhaps.
Well, my concern relates to ensuring that every library a port depends on,
all utilize the same libc++. Memory allocation, for example, would be at
the top of the list. (If everything ultimately utilizes malloc() and
free() provided by `/usr/lib/libSystem.dylib`, then no problem. But if
library A allocates memory one way, passes a structure to library B, and
the latter frees it... oye! Perhaps not a very likely scenario, but you
get the idea.)
And as you mentioned in one of your earlier comments, if certain
classes/structures aren't the same between the system and replacement
libc++... that would also be a bit... problematic.
So the idea of mixing-and-matching libc++ implementations between
libraries, scares the daylights out of me. But perhaps I'm simply getting
old, and with it, risk-averse. :-)
--
Ticket URL: <https://trac.macports.org/ticket/62426#comment:31>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list