Supporting C++11 on old OS X (Was: kdevelop 4.7 and beyond (was: clang++-mp-3.4 doesn't find initializer_list on OS X 10.6))
Lawrence Velázquez
larryv at macports.org
Mon Sep 8 11:35:21 PDT 2014
> On Mon, Sep 8, 2014 at 2:22 PM, Lawrence Velázquez <larryv at macports.org> wrote:
>> - My first assertion is that MacPorts' libstdc++ is broken on OS X because it doesn't use the system C++ runtime, libc++abi. This assertion, strictly speaking, is not about C++11 support.
>
> It strictly IS about C++11 support, because *that support defines the runtime ABI*. You have no options; if you insist on the system provided runtime, then either it provides the C++11 ABI or it does not, and that defines what level of C++ support you provide.
>
> That is precisely why this problem exists, and why it will continue to exist unless we provide viable support for other than the system's C++ runtime.
Okay, I wasn't aware of that.
So if we start using our own libc++abi on older OS X, wouldn't C++ binaries built with Xcode's compilers be unable to interoperate with binaries built with MacPorts compilers?
vq
More information about the macports-dev
mailing list