On 19/03/15 18:44, Michael Dickens wrote:
On Thu, Mar 19, 2015, at 02:06 PM, Lawrence Velázquez wrote:
On Mar 19, 2015, at 1:56 PM, Michael Dickens <[email protected]>
wrote:
Exactly. If we key off of {${configure.cxx_stdlib} eq "libstdc++"}, then
I think this can be made to work; er, mostly.
I believe this is only safe if you're absolutely sure that all the C++
objects your code uses or links with uses MacPorts' libstdc++ /
libc++.
I know it is possible to select configure.stdlib on a per-port basis ...
but, it's certainly not wise in general & how many folks or ports really
-try- to do this? I know it fails for me (on 10.8 and 10.10:
cross-linking libc++ and libstdc++ from Apple and MacPorts) way more
often than it works, so I just don't do it. I don't really see this as a
major issue, given how well it doesn't work. - MLD
Using Macports gcc you will still have the problem of mixing different
C++ runtimes, the macports stdlibc++ used by the gcc ports, and the
system one. They are not the same and if you try use at the same time
ports built with the normal compiler, to yours, problems can happen.
_______________________________________________
macports-dev mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-dev
